the Tobago plugin instatiates the apt classes (if fork=true then it uses apt
from command line), and then invokes the compile method, so the classpath
must be the same classpath that the plugin is running under.
Here is a link to the mojo class, in case you want to check it out:
http://svn.apache.org/viewvc/myfaces/tobago/trunk/tobago-tool/maven-apt-plugin/src/main/java/org/apache/myfaces/maven/plugin/AbstractAPTMojo.java?view=annotate
the invoke is on line 428.
thanks
musachy
On 1/20/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 1/20/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Under core:
> $ mvn -Dmaven.test.skip=true compile
...
> [INFO] [compiler:compile]
> Compiling 401 source files to
/home/musachy/dev/struts/core/target/classes
> [INFO] [apt:execute {execution: default}]
> warning: Specified AnnotationProcessorFactory, '
> org.apache.struts.annotations.taglib.apt.TLDAnnotationProcessorFactory',
not
> found on search path.
> warning: No annotation processors found but annotations present.
> 2 warnings
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
Oops... I just noted that the build was successful and moved on. I
get the same thing.
I tried it with struts-annotations as a dependency of the Tobago
maven-apt-plugin, but that didn't work either. I don't know what the
"search path" for the plugin is, someone who is more familiar with it
will have to comment. How is Tobago using it?
As a workaround, we can move the dependency on struts-annotations back
to <dependencies>, but mark it 'optional'. That will put it on the
compile time classpath, but stop Maven from adding it as a transitive
dependency.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
