You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Steve Cohen <sc...@javactivity.org> on 2004/04/22 06:55:39 UTC
[net] commons-net.1.2.0-rc1
okay, I've pushed the site and built the candidate release.
I have followed the instructions here:
http://jakarta.apache.org/commons/releases/prepare.html
about uploading the candidate release:
Now tag (for example FOO_1_2_RC1) and build distributions from that tag (as
per full release). For commons components, it's usually unnecessary to post
the release candidate on the main release site. (It's usually good enough to
upload it into the public folder ~/public_html in your home directory on
cvs.apache.org.)
I have done this. It's unclear to me that anyone else can access the release
there, so let me know. This may once again be a case of stale instructions.
Once I have a clear sense of "uploading the candidate release" I will propose
a vote on releasing 1.2.0.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] commons-net.1.2.0-rc1
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
This does seem ridiculous. Recreating the entire jar & dist plugin (
approximately 280 lines ) in each project just to get a two line file
(NOTICE.txt) included in the jar and distributions?
I don't see an issue logged against the dist plugin or the jar plugin
in maven's jira ( although I am jira challenged ).
We should just write a commons-dist plugin or something if the
standard stuff won't do. Or better yet, lets just put the two lines
from the NOTICE.txt into the README.txt.
>>>>> On Thu, 22 Apr 2004 20:25:28 +0200, Dirk Verbeeck <di...@pandora.be> said:
> I have made the changes needed to net/maven.xml. When I did this to
> commons-build someone remarked that there was an easier way but it
> was never implemented... Anyway this works.
> -- Dirk
> Steve Cohen wrote:
>> Thanks, Dirk. I'm not familiar enough with Maven to grok what
>> changes I would need to make to project.xml to make the inclusion
>> of NOTICE.txt happen. Or does your wondering about whether there
>> is a better way indicate that I shouldn't do anything about it just
>> yet? Steve
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] commons-net.1.2.0-rc1
Posted by Dirk Verbeeck <di...@pandora.be>.
I have made the changes needed to net/maven.xml.
When I did this to commons-build someone remarked that there was an
easier way but it was never implemented...
Anyway this works.
-- Dirk
Steve Cohen wrote:
> Thanks, Dirk. I'm not familiar enough with Maven to grok what changes I would
> need to make to project.xml to make the inclusion of NOTICE.txt happen.
>
> Or does your wondering about whether there is a better way indicate that I
> shouldn't do anything about it just yet?
>
> Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] commons-net.1.2.0-rc1
Posted by Steve Cohen <sc...@javactivity.org>.
Thanks, Dirk. I'm not familiar enough with Maven to grok what changes I would
need to make to project.xml to make the inclusion of NOTICE.txt happen.
Or does your wondering about whether there is a better way indicate that I
shouldn't do anything about it just yet?
Steve
On Thursday 22 April 2004 12:54 am, Dirk Verbeeck wrote:
> Ok, I can download your release candidate from
> http://cvs.apache.org/~scohen/
>
> One remark, the NOTICE.txt is missing from the root directory and also
> from the META-INF dir in the jar inside the binary distribution.
>
> I changed some goals in here to fix that:
> http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-commons/commons-build/
>maven.xml
>
> Note: Since the components don't extend the global project.xml anymore
> this fix isn't applied anymore.
> (and should be copied to each component?)
>
> But maybe there is a better way?
>
> -- Dirk
>
> Steve Cohen wrote:
> > okay, I've pushed the site and built the candidate release.
> > I have followed the instructions here:
> >
> > http://jakarta.apache.org/commons/releases/prepare.html
> >
> > about uploading the candidate release:
> >
> > Now tag (for example FOO_1_2_RC1) and build distributions from that tag
> > (as per full release). For commons components, it's usually unnecessary
> > to post the release candidate on the main release site. (It's usually
> > good enough to upload it into the public folder ~/public_html in your
> > home directory on cvs.apache.org.)
> >
> > I have done this. It's unclear to me that anyone else can access the
> > release there, so let me know. This may once again be a case of stale
> > instructions.
> >
> > Once I have a clear sense of "uploading the candidate release" I will
> > propose a vote on releasing 1.2.0.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] commons-net.1.2.0-rc1
Posted by Dirk Verbeeck <di...@pandora.be>.
Ok, I can download your release candidate from
http://cvs.apache.org/~scohen/
One remark, the NOTICE.txt is missing from the root directory and also
from the META-INF dir in the jar inside the binary distribution.
I changed some goals in here to fix that:
http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-commons/commons-build/maven.xml
Note: Since the components don't extend the global project.xml anymore
this fix isn't applied anymore.
(and should be copied to each component?)
But maybe there is a better way?
-- Dirk
Steve Cohen wrote:
> okay, I've pushed the site and built the candidate release.
> I have followed the instructions here:
>
> http://jakarta.apache.org/commons/releases/prepare.html
>
> about uploading the candidate release:
>
> Now tag (for example FOO_1_2_RC1) and build distributions from that tag (as
> per full release). For commons components, it's usually unnecessary to post
> the release candidate on the main release site. (It's usually good enough to
> upload it into the public folder ~/public_html in your home directory on
> cvs.apache.org.)
>
> I have done this. It's unclear to me that anyone else can access the release
> there, so let me know. This may once again be a case of stale instructions.
>
> Once I have a clear sense of "uploading the candidate release" I will propose
> a vote on releasing 1.2.0.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org