You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Wendy Smoak <ws...@gmail.com> on 2007/01/20 18:56:17 UTC
Tobago APT plugin question
We're using the maven-apt-plugin over at Struts, and are having
trouble with it not finding the configured factory.
We have a struts-annotations jar that contains
TLDAnnotationProcessorFactory. When this jar is in compile scope, all
is well.
However, I think I should be able to define this dependency either in
<build><extensions> or else in <plugin><dependencies>. If I try that,
I get:
warning: Specified AnnotationProcessorFactory, 'org.apache.struts.annotations.ta
glib.apt.TLDAnnotationProcessorFactory', not found on search path.
warning: No annotation processors found but annotations present.
What is the 'search path' here, and why would the plugin not see the
class in a build extension or a dependency of the plugin itself?
(For now I'll put the jar back in compile scope and mark it optional.)
Thanks,
Wendy
Re: Tobago APT plugin question
Posted by Bernd Bohmann <be...@atanion.com>.
Hello Wendy,
this is on my wish list.
See:
https://issues.apache.org/jira/browse/TOBAGO-130
I try to implement this but this works only if fork is enabled
(Classloader).
Regards
Bernd
Wendy Smoak wrote:
> We're using the maven-apt-plugin over at Struts, and are having
> trouble with it not finding the configured factory.
>
> We have a struts-annotations jar that contains
> TLDAnnotationProcessorFactory. When this jar is in compile scope, all
> is well.
>
> However, I think I should be able to define this dependency either in
> <build><extensions> or else in <plugin><dependencies>. If I try that,
> I get:
>
> warning: Specified AnnotationProcessorFactory,
> 'org.apache.struts.annotations.ta
> glib.apt.TLDAnnotationProcessorFactory', not found on search path.
> warning: No annotation processors found but annotations present.
>
> What is the 'search path' here, and why would the plugin not see the
> class in a build extension or a dependency of the plugin itself?
>
> (For now I'll put the jar back in compile scope and mark it optional.)
>
> Thanks,
> Wendy
>