On Aug 14, 2006, at 11:45 am, Kohsuke Kawaguchi wrote:
> Gregory Kick wrote:
>> I took a look at a few of the build scripts and although there's
>> a lot going on, it's certainly not insurmountable. Also,
>> although plugins would probably be the best way to go, there is
>> an alternative. The maven-antrun-plugin allows maven to run ant
>> tasks. The example from maven is:
>> <build>
>> <plugins>
>> <plugin>
>> <artifactId>maven-antrun-plugin</artifactId>
>> <executions>
>> <execution>
>> <phase>generate-sources</phase>
>> <configuration>
>> <tasks>
>> <!--
>> Place any ant task here. You can add anything
>> you can add between <target> and </target> in a
>> build.xml.
>> -->
>> </tasks>
>> </configuration>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> </execution>
>> </executions>
>> </plugin>
>> </plugins>
>> </build>
>> This seems like it would suit a lot of the tasks that the current
>> build system uses. Thoughts?
>
> Oh, yes. Yeah, that would be a good enough hack. Although it would
> be fun and the right thing to write Maven plugins for some of those
> codegen tasks --- for example, the annotation writer compiler in
> codemodel is something useful outside the JAXB RI, so it makes
> sense to write a maven plugin for that. I thought it's supposed to
> be not too hard to write a maven plugin.
You're right. They're pretty easy. So, if there's human bandwidth,
I'm all for it, but copying and pasting ant tasks would be a quick
transition.
>
> There are other codegen that are quickly put together just for the
> JAXB RI, and those thing could be done by maven-antrun-plugin.
>
> The other concern that I have is the packaging. We have a rather
> complicated re-jaring scheme and I really don't want to change it
> to avoid affecting our users.
Well, on the one hand, complicated re-jaring is never something I
want to hold on to. :-) But, I think that the assembly plugin (I've
never used it, but I know it can re-jar things) can accomplish
whatever tasks are lurking in the build files.
>
>
> Would you be interested in becoming a committer and drive this
> effort? We can work on Maven build configurations while we still
> retain Ant ones for a while. When everything looks good, we can
> make a switch and be happier :-)
Sure. This aligns itself perfectly with the work I'm doing with the
maven2-repository and maven-archetypes projects.
>
> We can start with smaller libraries that the JAXB RI relies on,
> like XSOM, codemodel, etc.
>
> I have a feeling (or rather I'm hoping) that Kostis might be
> interested in this, too, since maven-ized JAXB would mean easier
> posting to the repository.
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com
greg kick
http://kickstyle.net/