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.
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.
For non-maven projects, I'm looking at maven's repository plugins and
the artifact bundles it creates so that those bundles can be
validated and force poms to maintain a minimum quality standard.
(exactly like ibiblio)
greg kick
http://kickstyle.net/
On Aug 4, 2006, at 2:46 pm, Kohsuke Kawaguchi wrote:
>
> Hi, we have a few POMs written for JAXB 2.0 jars, which I used for
> the current push to java.net maven repository. See
>
> http://fisheye5.cenqua.com/browse/jaxb2-sources/jaxb-ri/tools/poms
>
> None of those POMs are as complete as yours. I wonder if we can
> update those POMs with yours and also perhaps can you help us
> improve our build script so that we can also push nightlies and
> what not into the maven repository automatically?
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com