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?
greg kick
http://kickstyle.net/
On Aug 8, 2006, at 9:09 am, Kohsuke Kawaguchi wrote:
> Gregory Kick wrote:
>> Kohsuke,
>> I looked over the poms that you pointed out and found that there
>> is a difference in how the different artifacts are versioned. I
>> just used 2.0.2 for everything, but you seemed to keep things
>> like the api on a separate track. That seems to be the only
>> thing that really needs to be resolved. Otherwise, feel free to
>> update your poms with what I sent.
>
> This is because APIs are rev-ed differently from the RI. For
> example, when the RI 2.0.2 shipped, it still uses API 2.0. API is
> owned by the JCP, whereas the RI is owned by this project.
>
>> As far as improving the build script, I'd think that the best
>> first step towards updating the build script would be to convert
>> to maven for builds... I know that it's a lot of work (I'd
>> certainly be willing to help), but the rewards are tremendous
>> when the entire process is simplified down to "mvn deploy".
>> Otherwise, a lot of energy is spent trying to recreate a lot of
>> the functionality provided by wagon.
>
> Yeah. I see what you mean. It's just that between all the code
> generators, custom document formatter, strange re-jarring, and
> samples generators that we use, I wonder how many maven plugins we
> need to write...
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com