Re: [all] Commons Parent - detach src/bin artifacts?

Did this thread start out about distribution artifacts and end up about asc.md5 and asc.sha1? AFAIK the latter problem is now taken care of by Nexus, which is why the recent [weaver] RC was not affected by it. Most likely [weaver] will differ from other candidates regarding the distribution

Re: [all] Commons Parent - detach src/bin artifacts?

An alternative approach might be to leave the POM as is, and create a separate script to download the source/binary bundles from Nexus to the dist/dev area, and then delete them from Nexus. On 22 December 2015 at 08:39, Pascal Schumacher wrote: > Thanks for the

Re: [all] Commons Parent - detach src/bin artifacts?

Le 5/01/2016 18:56, Phil Steitz a écrit : > That could probably be scripted in maven somehow, like it is rigged > for the site build. I'm experimenting with this idea currently. I use the antrun plugin to create a target/dist.apache.org directory with the bin/src archives and the release notes

Re: [all] Commons Parent - detach src/bin artifacts?

On 1/5/16 10:14 AM, sebb wrote: > An alternative approach might be to leave the POM as is, and create a > separate script to download the source/binary bundles from Nexus to > the dist/dev area, and then delete them from Nexus. Seems roundabout to me. As RM, I prefer to just commit artifacts

Re: [all] Commons Parent - detach src/bin artifacts?

On 1/5/16 1:24 PM, sebb wrote: > On 5 January 2016 at 17:56, Phil Steitz wrote: >> On 1/5/16 10:14 AM, sebb wrote: >>> An alternative approach might be to leave the POM as is, and create a >>> separate script to download the source/binary bundles from Nexus to >>> the

Re: [all] Commons Parent - detach src/bin artifacts?

On 5 January 2016 at 17:56, Phil Steitz wrote: > On 1/5/16 10:14 AM, sebb wrote: >> An alternative approach might be to leave the POM as is, and create a >> separate script to download the source/binary bundles from Nexus to >> the dist/dev area, and then delete them from

Re: [all] Commons Parent - detach src/bin artifacts?

Le 05/01/2016 22:26, Emmanuel Bourg a écrit : > Le 5/01/2016 21:42, Phil Steitz a écrit : > >> Can you add file specs at the end to specify the .asc.md5 and >> other cruft > > I didn't see any .asc.md5 file when releasing JEXL, I guess this issue > has been solved now? I noticed the same thing

Re: [all] Commons Parent - detach src/bin artifacts?

Le 5/01/2016 21:42, Phil Steitz a écrit : > Can you add file specs at the end to specify the .asc.md5 and > other cruft I didn't see any .asc.md5 file when releasing JEXL, I guess this issue has been solved now? Emmanuel Bourg

Re: [all] Commons Parent - detach src/bin artifacts?

On 5 January 2016 at 20:42, Phil Steitz wrote: > On 1/5/16 1:24 PM, sebb wrote: >> On 5 January 2016 at 17:56, Phil Steitz wrote: >>> On 1/5/16 10:14 AM, sebb wrote: An alternative approach might be to leave the POM as is, and create a

Re: [all] Commons Parent - detach src/bin artifacts?

On 5 January 2016 at 21:30, Luc Maisonobe wrote: > Le 05/01/2016 22:26, Emmanuel Bourg a écrit : >> Le 5/01/2016 21:42, Phil Steitz a écrit : >> >>> Can you add file specs at the end to specify the .asc.md5 and >>> other cruft >> >> I didn't see any .asc.md5 file when

Re: [all] Commons Parent - detach src/bin artifacts?

I agree. Maybe I misunderstand the issue, but please continue to attach sources to maven central releases. It's very helpful when the IDE can automatically download the source of jar and display it. Thanks, Pascal Am 21.12.2015 um 23:24 schrieb Christopher: Why detach them at all? Why not

Re: [all] Commons Parent - detach src/bin artifacts?

Le 22/12/2015 09:14, Pascal Schumacher a écrit : > I agree. > > Maybe I misunderstand the issue, but please continue to attach sources > to maven central releases. It's very helpful when the IDE can > automatically download the source of jar and display it. This is already done. There is a

Re: [all] Commons Parent - detach src/bin artifacts?

Thanks for the explanation and sorry for the noise. Cheers, Pascal Am 22.12.2015 um 09:28 schrieb Luc Maisonobe: Le 22/12/2015 09:14, Pascal Schumacher a écrit : I agree. Maybe I misunderstand the issue, but please continue to attach sources to maven central releases. It's very helpful when

Re: [all] Commons Parent - detach src/bin artifacts?

Why detach them at all? Why not permit them to be uploaded to Maven Central? It may not be as useful for Java builds, but Maven repository isn't designed to hold only jars. It can hold any type of artifact. On Mon, Dec 21, 2015 at 3:30 AM Emmanuel Bourg wrote: > Le 20/12/2015

Re: [all] Commons Parent - detach src/bin artifacts?

Le 20/12/2015 23:06, Emmanuel Bourg a écrit : > I've tested with JEXL and it seems to work > fine, I haven't noticed undesirable side effects. Actually there is one side effect: the .sha1 and .md5 files for the src/bin archives no longer come for free (they are currently generated when the

Re: [all] Commons Parent - detach src/bin artifacts?

On 12/20/15 3:06 PM, Emmanuel Bourg wrote: > Hi all, > > Our release procedure includes an annoying step consisting in the > manual removal of the -src and -bin artifacts from the Nexus staging > repository [1]. > > If I'm not mistaken there is are easy solution to avoid this operation: > these

Re: [all] Commons Parent - detach src/bin artifacts?

+1 2015-12-20 23:30 GMT+01:00 Phil Steitz : > On 12/20/15 3:06 PM, Emmanuel Bourg wrote: > > Hi all, > > > > Our release procedure includes an annoying step consisting in the > > manual removal of the -src and -bin artifacts from the Nexus staging > > repository [1]. > > >

[all] Commons Parent - detach src/bin artifacts?

Hi all, Our release procedure includes an annoying step consisting in the manual removal of the -src and -bin artifacts from the Nexus staging repository [1]. If I'm not mistaken there is are easy solution to avoid this operation: these artifacts are deployed because the assembly plugin attaches

Re: [all] Commons Parent - detach src/bin artifacts?

Anything to make the release process less onerous, I'm all for it! :-) Gary On Sun, Dec 20, 2015 at 2:06 PM, Emmanuel Bourg wrote: > Hi all, > > Our release procedure includes an annoying step consisting in the > manual removal of the -src and -bin artifacts from the Nexus