Sebastian--
Yes -- you're right. I started taking a look at Maven2 last night,
and pure Java plugins are what generally observed as well. The trick
is that it seems like Maven2 doesn't support "apt.exe" as a compiler
executable. Tweaking the pom.xml settings to configure the compiler
as "apt" threw an exception about an unsupported comiler option out
of:
org.codehaus.plexus.compiler.Compiler
That and:
org.apache.maven.plugin.AbstractCompilerMojo
are the right starting place for building annotation processor support
in Maven2 as it could be done as an extension of the usual "javac"
behavior. "apt" (a new tool in $JAVA_HOME/bin) is just a superset of
the functionality in "javac" that supports annotation processors.
I haven't dug deeper into Maven2 support for annotation processing
yet, so I'm not sure if there's something that I'm missing there.
As an interim solution, it seems like it would be possible to use
Adam's Maven1 type plugins in Maven2 like:
http://maven.apache.org/guides/mini/guide-using-ant.html
More later once I can look deeper into annotation processing support in M2.
Eddie
On 2/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Maven1 is much diffrent than Maven2. For example you don't define goals in
> maven.xml or project.xml. In fact there is no maven.xml file and
> project.xml is replace with pom.xml. You define goles in plugins and than
> you can execute them from project.xml or commandline. I need artifacts for
> both controls and page flow. I'm going to use maven2 in more then one
> project so it would be very usefull to have a beehive plugin than using
> ant plugin.
>
> Plugins are pure java classes. If i knew method or class from witch i
> could start the build process i could write simple maven plugin with
> parameters. Excecuting AptTask will not help. I need a class and method
> that is excecuted after AptTask. I need to create Maven2 version of
> AptTask. Maven2 plugins are very similar to ant's tasks. The problem in
> this case is that AptTask extends Javac.java and not Task.java.
>
> The main proble is:
>
> //
> // Select the executable (apt) and set fork = true
> //
> setExecutable("apt");
> setFork(true);
>
> Cause of this i have no idea what method in what class form beehive is
> executed after compile();
>
> Pozdrawiam
> Sebastian Błoch
>
>
>
> Eddie O'Neil <[EMAIL PROTECTED]>
> 2006-02-10 02:44
> Please respond to
> "Beehive Users" <[email protected]>
>
>
> To
> Beehive Users <[email protected]>
> cc
>
> Subject
> Re: Help needed - Maven2 plugin and BeeHive
>
>
>
>
>
>
> Sebastian--
>
> Sure, though I'm not super familiar with Maven2 (mostly with Maven
> 1). It might be helpful to take a look at the work Adam Jenkins did
> with Maven 1 support in building Beehive applications. This is in a
> .zip file here:
>
> https://issues.apache.org/jira/browse/BEEHIVE-1016
>
> Also, it would help to know what specific artifacts you're trying to
> build -- Controls, Page Flows, etc. ?
>
> Eddie
>
>
>
>
> On 2/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I'd like to understande the code but i don't know where to start. Could
> > you tell me which class is the starting point. (Beside AptTask.java).
> >
> > I need to make maven2 plugin for beeHive and i have only 2 weeks to
> finish
> >
> > it.
> >
> > Please help!!!
> >
> > Pozdrawiam
> > Sebastian Błoch
> >
>
>
>
