Refactoring Combustibles.java and Combustible.java

Centralice toda la logica de combustibles en Combustibles.java, y refactorice Combustible.java.

De Combustibles.java he eliminado la funcion de buscar el historico de precios por el momento ya que la pagina de la SEIC con los historicos no incluye la fecha de publicacion de los mismos en un formato estandar y facilmente parseable.
I do agree with your logic, but for readability/organization I never chose
that path. At the end it's gonna be two units anyway... Mainly because this
is a library and somebody gonna write code around it.

It doesn't hurt to keep it like that.
On Oct 7, 2014 9:29 PM, "George Aristy" <notifications@github.com> wrote:

> In src/main/java/org/devdom/commons/Combustible.java:
>
> > + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
> > + * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> > + * THE SOFTWARE.
> > + */
> > +/**
> > + * Entidad para expresar los precios variantes de los combustibles expresados por
> > + * semana.
> > + *
> > + * @author Carlos Vásquez Polanco
> > + * @since 0.7.8
> > + */
> > +public class Combustible {
> > +    private final double price;
> > +    private final Tipos type;
> > +
> > +    public enum Tipos {
>
> Well I guess whatever floats your boat.
>
> My personal philosophy is that if two types are tightly bound to each
> other, such as these, then one is a good candidate to be declared inside
> the other, otherwise both should be placed in their own package.
>
> What do you think?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/developersdo/commons-do/pull/16/files#r18560349>.
>