www-release-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: Separating distribution and maven artifacts in Nexus staging repo?
Date Mon, 09 Aug 2010 19:23:10 GMT


On 8/9/2010 3:13 PM, Brian Fox wrote:
> Well, we define a project like ^/org/apache/foo/.* so we could do
> something like ^/org/apache/foo/.*-dist.* for these other artifacts.
> Its not great but it would work.
>

Our projects to build distributions already all end in "-distr" which is almost
a perfect match :-).

-Marshall
> On Mon, Aug 9, 2010 at 3:08 PM, Marshall Schor <msa@schor.com> wrote:
>> Hi Brian, thanks for thinking about this.
>>
>>
>> On 8/9/2010 2:27 PM, Brian Fox wrote:
>>> If these artifacts had a well defined set of coordinates, I could
>>> configure Nexus to trap them into a separate staging repo, which could
>>> be promoted somewhere else...ie a repo that got rsyncd to dist.a.o.
>> What kind of thing are you thinking of here, when you say a "well defined set of
>> coordinates"?
>>
>>> This would be relatively easy to do, it would just make a separate
>>> repo for you to close and promote at the end.
>> We can with the current setup, do some "mvn release:perform"s and then close a
>> Nexus staging repo, and then do some more "mvn release:performs"s, and close
>> another staging repo.   Then we could call for the vote(s), and then if they
>> passed, promote one to maven-central, and the other to p.a.o/dist/proj-name.
>>
>> It would be better, though, not to have to do so much by hand, and to have
>> something where it could be set up once, debugged, and then be reproducable,
>> with less chance for human error... :-)
>>> If we wanted to go
>>> further later and have a single repo but selectively promote certain
>>> files to one repo and others somewhere else, that would require new
>>> code.
>> That would be better, I think.
>>
>> -Marshall
>>> On Mon, Aug 9, 2010 at 2:20 PM, Marshall Schor <msa@schor.com> wrote:
>>>>  We are in the same boat - We have artifacts which are "Maven artifacts"
that
>>>> release nicely with the Nexus release process, but also have release things
that
>>>> are big and not maven objects, but are, instead built from them.  Included
in
>>>> this is our eclipse-update-site, for instance, as well as our binary distribution.
>>>>
>>>> It seems wrong to put these into Maven, and instead they should go into the
>>>> other Apache distribution mechanism.
>>>>
>>>> We can of course do this "manually", which is what we've been doing, but
I agree
>>>> it would be nice to put them under the control of one release process, but
be
>>>> able to designate where the different "targets" should go, when they are
finally
>>>> voted / approved.
>>>>
>>>> Any thoughts on the best way to do this would be appreciated.
>>>>
>>>> -Marshall Schor
>>>>
>>>> On 7/27/2010 3:51 AM, ant elder wrote:
>>>>> I'd asked this on infrastructure@ but now found this list so i'll ask
here too:
>>>>>
>>>>> Is there an easy way to separate out the distribution artifacts and
>>>>> maven artifacts when staging a release to Nexus so that when the
>>>>> release is promoted to the maven central repo the distribution
>>>>> artifacts don't also end up in there?
>>>>>
>>>>> Looking at a few other projects they don't seem to do anything special
>>>>> so everything goes into the maven central repo, so maybe it doesn't
>>>>> matter. Is this something i need to worry about? I'm asking related to
>>>>> Tuscany and the distributions can be quite large, eg bin tar and zip
>>>>> each about 70 Meg  -
>>>>> https://repository.apache.org/content/repositories/orgapachetuscany-027/org/apache/tuscany/sca/tuscany-distribution-all/2.0-Beta1/
>>>>>
>>>>> I'm looking for a release process with a single command does all the
>>>>> signing and uploading of all the artifacts so i can kick it off and go
>>>>> away while it happens.
>>>>>
>>>>>   ...ant
>>>>>
>>>>>
>

Mime
View raw message