Factory generation mixups when more than 1 factory in same package with implementing interface about auto HOT 6 OPEN

That is very definitely a problem. I'm on it.

from auto.

A workaround is to explicitely state that the other factories don't need to implement any interface like this: @AutoFactory(implementing = {})

from auto.

@cypressious I don't think that's a work around...

If you have two classes like

home package
Person.java -> PersonFactoryImpl implements PersonFactory
Dog.java -> DogFactoryImpl implements DogFactory

The only way to fix the problem it is to move Person / Dog into separate packages if you need to use DI on each factory, pretty hacky work around in my opinion, not really scalable also if you need to generate a factory for each item in a package potentially.....

This really should be fixed ASAP, almost a blocking adoption of this library.

This also applies to extending = ...

from auto.

Hey, I don't know if this is strictly related, but I'm noticing that if I have 2 classes, in different packages, both using the same @AutoFactory(implementing = Foo.class), the second factory to be generated contains the interface's method twice. (and one of those has the signature of the other type)

from auto.

Eh, in fact, both generated factories have the problem. So it goes like this: in my sources:

package foo
public interface Foo {}
public interface FooFactory {
Foo heyDoMe();
}

package foo.bar
@AutoFactory(implementing = FooFactory.class)
public class Bar implements Foo {}

package foo.qux
@AutoFactory(implementing = FooFactory.class)
public class Qux implements Foo {}

Both resulting factories like this, both have these 2 methods, which makes the compiler rather unhappy obviously.

[...]
  @Override
  public foo.bar.Bar heyDoMe() {
    return create(p);
  }
  @Override
  public Qux heyDoMe() {
    return create(p);
  }

from auto.

Sorry for being impatient with an issue opened Feb 2014... but do we already know when this bug will be fixed (and a new version of autofactory will be published)?
This bug makes it autofactory practically unusable... creating for each factory with it's classes (which implements an interface) a separate package results in almost more time lost than saved due to the factory autogeneration.

from auto.