You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Christian Grobmeier <gr...@gmail.com> on 2010/08/16 16:42:32 UTC
[nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
On Mon, Aug 16, 2010 at 11:17 AM, sebb <se...@gmail.com> wrote:
>> The -bin and -src files need to be moved to the commons/dist directory
>> tree (and removed from Nexus) *before* the Maven artifacts are
>> released from Nexus.
>>
>> This is an error-prone operation, so I don't think any future Commons
>> releases should use Nexus for non-Maven archives - unless and until
>> Nexus supports releasing both Maven and non-Maven archives from the
>> same directory.
>>
>> Otherwise, the release looks OK.
> From: Jochen Wiedmann <jo...@gmail.com>
I> followed the same procedure without any of the restrictions you
i> mpose with a multitude of projects, including FileUpload, RAT, or
> XML-RPC in the past. It was never considered to be a problem. Neither
> would I consider it now.
I am unsure of what you are discussing... I would have followed these
steps for compress. I have copied this from Apache felix Please advice
if there is something wrong.
1) copy the released artifacts to the dist directory
(/x1/www/www.apache.org/dist/commons) on people.apache.org
2) delete the old release from the dist directory (it's archived)
3) login to https://repository.apache.org with your Apache SVN
credentials. Click on Staging. Find your closed staging repository,
right click on it and choose Promote. Select the Releases repository
from the drop-down list and click Promote.
4) next click on Repositories, select the Releases repository and
validate that your artifacts are all there
5) update the website with site:deploy
Question: I need to copy the artifacts to dist - were can I get them
now, as they are in Nexus?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Aug 18, 2010 at 12:19 PM, Phil Steitz <ph...@gmail.com> wrote:
>> You're free to do so. My personal procedure is to use "wget -np -r
>> <disturl>" to copy the files from the repository to the dist folder on
>> people.apache.org. Some shifting and removing of empty directories
>> required afterwards, but it's relatively simple.
>>
>
> We should release the bits that we voted on and what goes to /dist
> *is* the release. Therefore if we are going to vote on bits staged
> somewhere other than people.apache.org, we need to do something like
> what sebb describes above. If wget is used, RMs should re-verify
> hashes on p.a.o before placing the files into /dist. How do the
> other ASF projects using nexus handle this?
I can see no contradiction, Phil. When asking for a vote, I usually
point to repository.apache.org as the place from where to download the
proposed binary and source distributions. As they are deployed by
Maven, hash files and signatures (.asc-files) are automatically
included.
Likewise (note that I proposed "wget -np -r", they are being
downloaded from repository.apache.org and simply being moved to the
dist directory. Again, hash files and signatures are conserved.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Phil Steitz <ph...@gmail.com>.
Christian Grobmeier wrote:
>>> We should release the bits that we voted on and what goes to /dist
>>> *is* the release. Therefore if we are going to vote on bits staged
>>> somewhere other than people.apache.org, we need to do something like
>>> what sebb describes above. If wget is used, RMs should re-verify
>>> hashes on p.a.o before placing the files into /dist. How do the
>>> other ASF projects using nexus handle this?
>> I used Nexus for Jakarta BSF, but the non-Maven archives were uploaded
>> separately (to my pao directory). They were not part of the Maven
>> deploy, probably because the POM does not attach the package goal.
>>
>> So the vote was on two separate directories.
>
> I think it should be possible to perform a wget and then check if the
> hashes still work. That would be easy and if hashes are ok, the files
> we voted on are the same as the ones the RM checked
Yes. That is what I meant. If we use wget to transfer files over
the Internet, we should verify the hashes before pushing the
downloaded copies of the files that we voted on to /dist.
Phil
>
> The other question is: delete non-maven stuff out or not.
> Compress 1.0 has everything:
> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
> I like it, to be honest. Everything I need on one place.
>
> some other components have this too:
> http://repo1.maven.org/maven2/org/apache/commons/commons-email/1.2/
> http://repo1.maven.org/maven2/org/apache/commons/commons-exec/1.0.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-jexl/2.0.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-jci-core/1.0/
>
> some not:
> http://repo1.maven.org/maven2/org/apache/commons/commons-math/2.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/
> http://repo1.maven.org/maven2/commons-betwixt/commons-betwixt/1.0-alpha-1/
> http://repo1.maven.org/maven2/commons-attributes/commons-attributes/2.1/
> http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils-core/1.8.3/
> http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/
> http://repo1.maven.org/maven2/commons-cli/commons-cli/1.2/
>
> From these components which do not have the -bin and -src folders
> inside i found out that some even don't have -sources.jar or
> -javadoc.jar (for example beanutils-core). This is inconsistent. I
> already had a project were I was forced to include all source files
> (medical devices) and then I had to download sources manually.
>
> Here is my +1 to release all the files with nexus without deleting anything out
> and here is my +1 for using wget and ask the RM to check the hashes
> before he goes to dist
>
> Christian
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 16:45, Jochen Wiedmann <jo...@gmail.com> wrote:
> I am sorry, but IMO we are just complicating a simple issue in order
> to prevent problems that some *think* possible to occur. Please let's
> limit our work on fixing problems that *are* present.
Until we have confirmed with Infra that it is OK to copy non-Maven
archives to the Maven repo, we don't know if it is a problem or not.
> Jochen
>
>
> On Wed, Aug 18, 2010 at 5:24 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
>
>> - remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
>> - hit nexus release button
>
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
I am sorry, but IMO we are just complicating a simple issue in order
to prevent problems that some *think* possible to occur. Please let's
limit our work on fixing problems that *are* present.
Jochen
On Wed, Aug 18, 2010 at 5:24 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> - remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
> - hit nexus release button
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
> The javadoc and source JARs are expected to be in the Maven repo.
> I'm not saying we should delete those.
>
> However the bin and src zip and tar.gz archives are not supposed to be
> in the Maven repo.
> These at least triple the storage space required. For releases that
> include bz2 archives as well it will be 4 times.
Well OK i think you are right. I go ahead with deleting unnecessary
files and have reflected this in the UsingNexus document
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 16:24, Christian Grobmeier <gr...@gmail.com> wrote:
>>> Noone ever proposed using something different.
>>
>> Huh?
>>
>> Christian wrote:
>>
>>>>> Compress 1.0 has everything:
>>>>> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
>>>>> I like it, to be honest. Everything I need on one place.
>>
>> which I take to mean that he would like to be able to download src and
>> bin from there.
>
>
> Well, I didn't want it as a replacement for a download-server. But I
> like javadocs and sources there.
The javadoc and source JARs are expected to be in the Maven repo.
I'm not saying we should delete those.
However the bin and src zip and tar.gz archives are not supposed to be
in the Maven repo.
These at least triple the storage space required. For releases that
include bz2 archives as well it will be 4 times.
> I just thought, it would not hurt -
> if I need to download something manually, I will usually go to the
> download-page of the project. But hey, if there are infra-limitations
> - ok.
>
> But i still think that the risk is low (without being in infra team)
> and the risk is higher to delete out something. This is why each
> project looks somehow different.
>
>>> Admitted, the technical possibility to download from the Maven mirrors
>>> exists. But that's not different from the technical possibility to use
>>> www.apache.org directly and circumventing the mirrors.
>>
>> Of course, but I still think it's a bad idea to upload files to the
>> Maven repos that are not supposed to be there.
>> [Yes, I know there are .asc.md5 files sometimes, but these are very
>> small, and no-one is likely to need them]
>
> I cannot speak for infra - you know more. If following your path I would:
>
> - wget the stuff to people
Only the -bin and -src files.
> - check the hashes
> - copy stuff to dist
> - remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
> - hit nexus release button
>
> Then the following artifacts are released:
> commons-compress-1.1-sources.jar*
> commons-compress-1.1-javadoc.jar*
> commons-compress-1.1.jar*
> commons-compress-1.1.pom*
>
> Is that correct? I have no problems with doing it like this but would
> like to find some consens on the commons project.
Yes, that looks fine to me.
> Christian
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus
Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-08-18, Christian Grobmeier wrote:
> Is that correct? I have no problems with doing it like this but would
> like to find some consens on the commons project.
I should add that this discussion shouldn't stop you from just doing it.
"it" being
> - wget the stuff to people
> - check the hashes
> - copy stuff to dist
> - remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
> - hit nexus release button
and finally announce the release.
I have an Antlib eagerly waiting for compress 1.1 to become available so
it can be released as well ;-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus
Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-08-18, Christian Grobmeier wrote:
> I cannot speak for infra - you know more. If following your path I would:
> - wget the stuff to people
> - check the hashes
> - copy stuff to dist
> - remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
> - hit nexus release button
> Then the following artifacts are released:
> commons-compress-1.1-sources.jar*
> commons-compress-1.1-javadoc.jar*
> commons-compress-1.1.jar*
> commons-compress-1.1.pom*
> Is that correct?
I think so.
While I agree with sebb that we shouldn't be putting things into the
Maven repository that don't belong there, I don't think the ASF infra
team is responsible for the Maven repo at all, so they probably don't
care.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
>> Noone ever proposed using something different.
>
> Huh?
>
> Christian wrote:
>
>>>> Compress 1.0 has everything:
>>>> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
>>>> I like it, to be honest. Everything I need on one place.
>
> which I take to mean that he would like to be able to download src and
> bin from there.
Well, I didn't want it as a replacement for a download-server. But I
like javadocs and sources there. I just thought, it would not hurt -
if I need to download something manually, I will usually go to the
download-page of the project. But hey, if there are infra-limitations
- ok.
But i still think that the risk is low (without being in infra team)
and the risk is higher to delete out something. This is why each
project looks somehow different.
>> Admitted, the technical possibility to download from the Maven mirrors
>> exists. But that's not different from the technical possibility to use
>> www.apache.org directly and circumventing the mirrors.
>
> Of course, but I still think it's a bad idea to upload files to the
> Maven repos that are not supposed to be there.
> [Yes, I know there are .asc.md5 files sometimes, but these are very
> small, and no-one is likely to need them]
I cannot speak for infra - you know more. If following your path I would:
- wget the stuff to people
- check the hashes
- copy stuff to dist
- remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus
- hit nexus release button
Then the following artifacts are released:
commons-compress-1.1-sources.jar*
commons-compress-1.1-javadoc.jar*
commons-compress-1.1.jar*
commons-compress-1.1.pom*
Is that correct? I have no problems with doing it like this but would
like to find some consens on the commons project.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 13:57, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Wed, Aug 18, 2010 at 2:27 PM, sebb <se...@gmail.com> wrote:
>
>> The mirror system derived from /dist should be used for the non-Maven downloads
>
> Noone ever proposed using something different.
Huh?
Christian wrote:
>>> Compress 1.0 has everything:
>>> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
>>> I like it, to be honest. Everything I need on one place.
which I take to mean that he would like to be able to download src and
bin from there.
> We expose the /dist
> directory (aka the mirrors) on our download pages, in our
> announcements, and so on, just like we did before.
Yes.
> Admitted, the technical possibility to download from the Maven mirrors
> exists. But that's not different from the technical possibility to use
> www.apache.org directly and circumventing the mirrors.
Of course, but I still think it's a bad idea to upload files to the
Maven repos that are not supposed to be there.
[Yes, I know there are .asc.md5 files sometimes, but these are very
small, and no-one is likely to need them]
> Jochen
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Aug 18, 2010 at 2:27 PM, sebb <se...@gmail.com> wrote:
> The mirror system derived from /dist should be used for the non-Maven downloads
Noone ever proposed using something different. We expose the /dist
directory (aka the mirrors) on our download pages, in our
announcements, and so on, just like we did before.
Admitted, the technical possibility to download from the Maven mirrors
exists. But that's not different from the technical possibility to use
www.apache.org directly and circumventing the mirrors.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 13:19, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Wed, Aug 18, 2010 at 1:56 PM, sebb <se...@gmail.com> wrote:
You snipped the following:
>>> Compress 1.0 has everything:
>>> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
>>> I like it, to be honest. Everything I need on one place.
which is why I wrote:
>> But that is not how the mirroring system is currently designed to work.
i.e. users should *not* be downloading non-Maven archives from Maven repos.
>
> That's why we are copying to /dist. Noone's questioning that necessity.
Nor was I.
I am saying that the Maven repo should be used for Maven artifacts only.
The mirror system derived from /dist should be used for the non-Maven downloads
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Aug 18, 2010 at 1:56 PM, sebb <se...@gmail.com> wrote:
> But that is not how the mirroring system is currently designed to work.
That's why we are copying to /dist. Noone's questioning that necessity.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 12:19, Christian Grobmeier <gr...@gmail.com> wrote:
>>> We should release the bits that we voted on and what goes to /dist
>>> *is* the release. Therefore if we are going to vote on bits staged
>>> somewhere other than people.apache.org, we need to do something like
>>> what sebb describes above. If wget is used, RMs should re-verify
>>> hashes on p.a.o before placing the files into /dist. How do the
>>> other ASF projects using nexus handle this?
>>
>> I used Nexus for Jakarta BSF, but the non-Maven archives were uploaded
>> separately (to my pao directory). They were not part of the Maven
>> deploy, probably because the POM does not attach the package goal.
>>
>> So the vote was on two separate directories.
>
> I think it should be possible to perform a wget and then check if the
> hashes still work. That would be easy and if hashes are ok, the files
> we voted on are the same as the ones the RM checked
>
> The other question is: delete non-maven stuff out or not.
> Compress 1.0 has everything:
> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
> I like it, to be honest. Everything I need on one place.
But that is not how the mirroring system is currently designed to work.
> some other components have this too:
> http://repo1.maven.org/maven2/org/apache/commons/commons-email/1.2/
> http://repo1.maven.org/maven2/org/apache/commons/commons-exec/1.0.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-jexl/2.0.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-jci-core/1.0/
>
> some not:
> http://repo1.maven.org/maven2/org/apache/commons/commons-math/2.1/
> http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/
> http://repo1.maven.org/maven2/commons-betwixt/commons-betwixt/1.0-alpha-1/
> http://repo1.maven.org/maven2/commons-attributes/commons-attributes/2.1/
> http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils-core/1.8.3/
> http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/
> http://repo1.maven.org/maven2/commons-cli/commons-cli/1.2/
>
> From these components which do not have the -bin and -src folders
> inside i found out that some even don't have -sources.jar or
> -javadoc.jar (for example beanutils-core). This is inconsistent.
It's probably because the poms were not set up properly.
Also, I think the source and javadoc jars were not originally
considered part of the Maven release.
We need to ensure that future Maven releases include these (which is
very easy to do with Nexus).
> I already had a project were I was forced to include all source files
> (medical devices) and then I had to download sources manually.
>
> Here is my +1 to release all the files with nexus without deleting anything out
I think this is at least partly an infrastructure issue.
If we don't remove the additional files, there will be a bigger load
on the Maven repo systems.
> and here is my +1 for using wget and ask the RM to check the hashes
> before he goes to dist
Agreed here.
>
> Christian
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
>> We should release the bits that we voted on and what goes to /dist
>> *is* the release. Therefore if we are going to vote on bits staged
>> somewhere other than people.apache.org, we need to do something like
>> what sebb describes above. If wget is used, RMs should re-verify
>> hashes on p.a.o before placing the files into /dist. How do the
>> other ASF projects using nexus handle this?
>
> I used Nexus for Jakarta BSF, but the non-Maven archives were uploaded
> separately (to my pao directory). They were not part of the Maven
> deploy, probably because the POM does not attach the package goal.
>
> So the vote was on two separate directories.
I think it should be possible to perform a wget and then check if the
hashes still work. That would be easy and if hashes are ok, the files
we voted on are the same as the ones the RM checked
The other question is: delete non-maven stuff out or not.
Compress 1.0 has everything:
http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
I like it, to be honest. Everything I need on one place.
some other components have this too:
http://repo1.maven.org/maven2/org/apache/commons/commons-email/1.2/
http://repo1.maven.org/maven2/org/apache/commons/commons-exec/1.0.1/
http://repo1.maven.org/maven2/org/apache/commons/commons-jexl/2.0.1/
http://repo1.maven.org/maven2/org/apache/commons/commons-jci-core/1.0/
some not:
http://repo1.maven.org/maven2/org/apache/commons/commons-math/2.1/
http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/
http://repo1.maven.org/maven2/commons-betwixt/commons-betwixt/1.0-alpha-1/
http://repo1.maven.org/maven2/commons-attributes/commons-attributes/2.1/
http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils-core/1.8.3/
http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/
http://repo1.maven.org/maven2/commons-cli/commons-cli/1.2/
>From these components which do not have the -bin and -src folders
inside i found out that some even don't have -sources.jar or
-javadoc.jar (for example beanutils-core). This is inconsistent. I
already had a project were I was forced to include all source files
(medical devices) and then I had to download sources manually.
Here is my +1 to release all the files with nexus without deleting anything out
and here is my +1 for using wget and ask the RM to check the hashes
before he goes to dist
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 18 August 2010 11:19, Phil Steitz <ph...@gmail.com> wrote:
> Jochen Wiedmann wrote:
>> On Tue, Aug 17, 2010 at 12:43 PM, Christian Grobmeier
>> <gr...@gmail.com> wrote:
>>
>>> Which means:
>>> 1) I will copy it to apache dist from my local box to people
>>> 2) push the release button on nexus
>>
>> You're free to do so. My personal procedure is to use "wget -np -r
>> <disturl>" to copy the files from the repository to the dist folder on
>> people.apache.org. Some shifting and removing of empty directories
>> required afterwards, but it's relatively simple.
>>
>
> We should release the bits that we voted on and what goes to /dist
> *is* the release. Therefore if we are going to vote on bits staged
> somewhere other than people.apache.org, we need to do something like
> what sebb describes above. If wget is used, RMs should re-verify
> hashes on p.a.o before placing the files into /dist. How do the
> other ASF projects using nexus handle this?
I used Nexus for Jakarta BSF, but the non-Maven archives were uploaded
separately (to my pao directory). They were not part of the Maven
deploy, probably because the POM does not attach the package goal.
So the vote was on two separate directories.
[The ideal would be if Nexus could release the Maven and non-Maven
archives directly, but that is not mplemented.]
> Phil
>> Jochen
>>
>>
>
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Phil Steitz <ph...@gmail.com>.
Jochen Wiedmann wrote:
> On Tue, Aug 17, 2010 at 12:43 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
>
>> Which means:
>> 1) I will copy it to apache dist from my local box to people
>> 2) push the release button on nexus
>
> You're free to do so. My personal procedure is to use "wget -np -r
> <disturl>" to copy the files from the repository to the dist folder on
> people.apache.org. Some shifting and removing of empty directories
> required afterwards, but it's relatively simple.
>
We should release the bits that we voted on and what goes to /dist
*is* the release. Therefore if we are going to vote on bits staged
somewhere other than people.apache.org, we need to do something like
what sebb describes above. If wget is used, RMs should re-verify
hashes on p.a.o before placing the files into /dist. How do the
other ASF projects using nexus handle this?
Phil
> Jochen
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 17 August 2010 12:27, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 1:10 PM, sebb <se...@gmail.com> wrote:
>
>> BTW, I note that fileupload [1] does not contain the bin and src
>> archives, whereas compress 1.0 [2] does.
>
> That's coincidentally because I wasn't able to use Nexus at the time.
That cannot be the only reason, because compress 1.0 did not use Nexus either.
Besides, Nexus only acts as a proxy for the upload, and cannot affect
what is uploaded.
> Jochen
>
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 17 August 2010 12:27, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 1:10 PM, sebb <se...@gmail.com> wrote:
>
>> BTW, I note that fileupload [1] does not contain the bin and src
>> archives, whereas compress 1.0 [2] does.
>
> That's coincidentally because I wasn't able to use Nexus at the time.
That cannot be the only reason, because compress 1.0 did not use Nexus either.
> Jochen
>
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Aug 17, 2010 at 1:10 PM, sebb <se...@gmail.com> wrote:
> BTW, I note that fileupload [1] does not contain the bin and src
> archives, whereas compress 1.0 [2] does.
That's coincidentally because I wasn't able to use Nexus at the time.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 17 August 2010 12:03, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 1:00 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
>
>> My preference is currently not to remove the unnecessary files and let
>> stay complete
>
> I wouldn't even bet that's possible. In particular, I never tried.
Yes, you can remove files from Nexus before the directory is released/promoted.
BTW, I note that fileupload [1] does not contain the bin and src
archives, whereas compress 1.0 [2] does.
[1] http://repo1.maven.org/maven2/commons-fileupload/commons-fileupload/1.2.2/
[2] http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
Compress 1.0 used the old (pre-Nexus) method.
How come fileupload does not have the unwanted files?
It seems wrong to me to add files to the Maven repo that do not belong
there, especially when they double the space used.
> Jochen
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Aug 17, 2010 at 1:00 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> My preference is currently not to remove the unnecessary files and let
> stay complete
I wouldn't even bet that's possible. In particular, I never tried.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
>> Which means:
>> 1) I will copy it to apache dist from my local box to people
>> 2) push the release button on nexus
>
> You're free to do so. My personal procedure is to use "wget -np -r
> <disturl>" to copy the files from the repository to the dist folder on
> people.apache.org. Some shifting and removing of empty directories
> required afterwards, but it's relatively simple.
Ah now I got you.- thanks!
I will follow your wget tip
One thing left - Sebb mentioned to remove unnecessary files before releasing.
Looking at:
https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-compress/1.0/
it seems that this has not been done before.
My preference is currently not to remove the unnecessary files and let
stay complete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Aug 17, 2010 at 12:43 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> Which means:
> 1) I will copy it to apache dist from my local box to people
> 2) push the release button on nexus
You're free to do so. My personal procedure is to use "wget -np -r
<disturl>" to copy the files from the repository to the dist folder on
people.apache.org. Some shifting and removing of empty directories
required afterwards, but it's relatively simple.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Aug 17, 2010 at 12:52 PM, sebb <se...@gmail.com> wrote:
> I'm surprised that the non-Maven archives end up in Nexus.
> Is there some pom magic that somehow attaches them to the deploy target?
In the case of commons-parent, search for "maven-assembly-plugin" on
http://repo2.maven.org/maven2/org/apache/commons/commons-parent/17/commons-parent-17.pom
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by sebb <se...@gmail.com>.
On 17 August 2010 11:43, Christian Grobmeier <gr...@gmail.com> wrote:
>> On Tue, Aug 17, 2010 at 12:06 PM, Christian Grobmeier
>> <gr...@gmail.com> wrote:
>>
>>> Interesting... were is this content from? Has this been grabbed by
>>> nexus automatically?
>>
>> That's what we had been discussing initially. The projects I am aware
>> of are building the source and binary distributions as part of the
>> Maven build. In particular, they are also deploying them as a part of
>> the Maven deployment.
>
I'm surprised that the non-Maven archives end up in Nexus.
Is there some pom magic that somehow attaches them to the deploy target?
> Which means:
> 1) I will copy it to apache dist from my local box to people
Or from Nexus, which is what was voted on.
> 2) push the release button on nexus
Unless you delete the -bin* and -src* files from Nexus first, then I
think they will end up in the Maven repo, where they will just take up
extra space (AIUI they serve no purpose for Maven). They will at least
double the size of the directory (unlike the spurious .asc.md5 files
which are very small).
> ?
>
> Christian
>
> ---------------------------------------------------------------------
> 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
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
> On Tue, Aug 17, 2010 at 12:06 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
>
>> Interesting... were is this content from? Has this been grabbed by
>> nexus automatically?
>
> That's what we had been discussing initially. The projects I am aware
> of are building the source and binary distributions as part of the
> Maven build. In particular, they are also deploying them as a part of
> the Maven deployment.
Which means:
1) I will copy it to apache dist from my local box to people
2) push the release button on nexus
?
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Aug 17, 2010 at 12:06 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> Interesting... were is this content from? Has this been grabbed by
> nexus automatically?
That's what we had been discussing initially. The projects I am aware
of are building the source and binary distributions as part of the
Maven build. In particular, they are also deploying them as a part of
the Maven deployment.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Christian Grobmeier <gr...@gmail.com>.
>> 1) copy the released artifacts to the dist directory
>> (/x1/www/www.apache.org/dist/commons) on people.apache.org
> Wasn't that step 1 in your list?
Yes but I cannot find the place from which I can copy from Nexus to
the dist folder.
I searched whole people server... so, where are the nexus artifacts?
Or do I need to copy from my local box to the dist folder? If you
could help me here, that would be good
> Apart from that, look at
> https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-compress/1.0/
Interesting... were is this content from? Has this been grabbed by
nexus automatically?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [nexus] Releasing with nexus (was: Fwd: [VOTE] Release Commons
Compress based on RC2)
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Mon, Aug 16, 2010 at 4:42 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> 1) copy the released artifacts to the dist directory
> (/x1/www/www.apache.org/dist/commons) on people.apache.org
> 2) delete the old release from the dist directory (it's archived)
> 3) login to https://repository.apache.org with your Apache SVN
> credentials. Click on Staging. Find your closed staging repository,
> right click on it and choose Promote. Select the Releases repository
> from the drop-down list and click Promote.
> 4) next click on Repositories, select the Releases repository and
> validate that your artifacts are all there
> 5) update the website with site:deploy
>
> Question: I need to copy the artifacts to dist - were can I get them
> now, as they are in Nexus?
Wasn't that step 1 in your list?
Apart from that, look at
https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-compress/1.0/
--
I Am What I Am And That's All What I Yam (Popeye)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org