commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [vote] Release commons-net 2.0
Date Sat, 04 Oct 2008 12:31:00 GMT
Also, it would help to know what Maven command-line was used to build
the release (and on which OS), so it can readily be checked on other
systems / OSes.

The README file could perhaps be updated with this information - at
the moment it only describes how to build the site.

On 04/10/2008, sebb <sebbaz@gmail.com> wrote:
> The source and javadoc jars don't have LICENSE and NOTICE files.
>
>  The NET_2_0 tag does not agree with the source file archive - the pom
>  files differ.
>
>  Which pom was actually used to generate the release?
>
>
>  On 04/10/2008, Rory Winston <rory.winston@gmail.com> wrote:
>  > Guys
>  >
>  >  I know commons has been dying a slow death due to inactivity, but binding
>  > votes (either +-1) would be appreciated. I want to get this out finally...
>  >
>  >
>  >  Rory Winston wrote:
>  >
>  > > Ah, yes, you're right.... -Prc does actually generate them automatically.
>  > That explains the discrepancy.
>  > >
>  > > I have uploaded the distribution again, based on the build with a -Prc
>  > switch. It's exactly the same, just the javadoc/src jar is generated by the
>  > parent pom automagically.
>  > >
>  > > James Carman wrote:
>  > >
>  > > > Does Net's pom not extend the proper parent pom?  For Proxy, most of
>  > > > the proper build stuff was taken care of for me by the hard work that
>  > > > others put into the parent pom (thanks to those folks).  Did you try
>  > > > using the "rc" profile when cutting your release candidates?
>  > > >
>  > > > On Thu, Oct 2, 2008 at 2:23 AM, Jörg Schaible
>  > > > <Joerg.Schaible@scalaris.com> wrote:
>  > > >
>  > > >
>  > > > > jcarman@carmanconsulting.com wrote:
>  > > > >
>  > > > >
>  > > > > > On 10/1/08, Rory Winston <rory.winston@gmail.com> wrote:
>  > > > > >
>  > > > > >
>  > > > > > > Thanks for the feedback. I have changed the pom (needed
to add
>  > some
>  > > > > > > plugins) to generate sources and javadoc jars. I have
uploaded the
>  > > > > > > signed jars to the site. I dont see an issue with the
javadocs
>  > > > > > > containing the examples classes (its always been like
that).
>  > > > > > >
>  > > > > > > Rory
>  > > > > > >
>  > > > > > >
>  > > > > > Shouldn't the Parent pom take care of this?
>  > > > > >
>  > > > > >
>  > > > > That was my impression also ...
>  > > > >
>  > > > > - Jörg
>  > > > >
>  > > > >
>  > ---------------------------------------------------------------------
>  > > > > To unsubscribe, e-mail:
>  > dev-unsubscribe@commons.apache.org
>  > > > > For additional commands, e-mail: dev-help@commons.apache.org
>  > > > >
>  > > > >
>  > > > >
>  > > > >
>  > > >
>  > > >
>  > ---------------------------------------------------------------------
>  > > > To unsubscribe, e-mail:
>  > dev-unsubscribe@commons.apache.org
>  > > > For additional commands, e-mail: dev-help@commons.apache.org
>  > > >
>  > > >
>  > > >
>  > > >
>  > > >
>  > > >
>  > >
>  > >
>  > >
>  > ---------------------------------------------------------------------
>  > > To unsubscribe, e-mail:
>  > dev-unsubscribe@commons.apache.org
>  > > For additional commands, e-mail: dev-help@commons.apache.org
>  > >
>  > >
>  > >
>  > >
>  > >
>  >
>  >
>  > ---------------------------------------------------------------------
>  >  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  >  For additional commands, e-mail: dev-help@commons.apache.org
>  >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message