Right now, the plugin supports only one source directory. It would be interesting to add an arbitrary number of directories to the processor, to include, for example, other generated-sources that need to be processed.

<additionalSourceDirectories> <additionalSourceDirectory>${basedir}/generated-sources/jelly</additionalSourceDirectory> </additionalSourceDirectories>

This is a patch to implement this feature :)

Hi, thx for support

I'll apply an deploy new release soon

Hi,

Before adding new feature coming with your patch, i've preferred to get paths information directly from maven project using methods : getCompileSourceRoots & getTestCompileSourceRoots.

This should solve also your issue using the build-helper-maven-plugin ( see http://mojo.codehaus.org/build-helper-maven-plugin/usage.html ).

I've deployed this stuff in release 2.0.7-SNAPSHOT

Hi,

yes, that's a nice addition. However, sometimes it is still very useful to make APT process sources from a completely different source tree without having to involve that source in the rest of the maven compile/package lifecycle. For example, I use APT-Jelly to generate source code using web-like templates (for example, to generate GWT RequestFactory proxies from JPA entities into a separate Maven project). For this I'm using the apt-maven-plugin, which provides this functionality (and support for the APT --factory option), but it'd be nice if I could depend on just on one plugin.

Completely agree

I'd already planned to apply your patch .... But while was working on it, i've identified and fixed a lack of my implementation

Stay tuned ... I'll deploy it very soon

Deployed a new 2.0.7-SNAPSHOT with your patch.

Please test it and let me know

to be verified