commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [RESULT] [LANG] Release Commons Lang 3.0 (based on RC4)
Date Wed, 20 Jul 2011 10:14:05 GMT
On 20 July 2011 07:04, Henri Yandell <flamefew@gmail.com> wrote:
> On Tue, Jul 19, 2011 at 9:32 AM, Henri Yandell <flamefew@gmail.com> wrote:
>> On Tue, Jul 19, 2011 at 1:52 AM, Henri Yandell <flamefew@gmail.com> wrote:
>>> On Mon, Jul 18, 2011 at 6:37 PM, Henri Yandell <flamefew@gmail.com> wrote:
>>>> Vote passes [!!!!!!!!!]
>>>>
>>>> 6 +1s.
>>>>
>>>> Gary Gregory
>>>> Matt Benson
>>>> Oliver Heger
>>>> Jörg Schaible
>>>> Stephen Colebourne
>>>> and my own implicit +1.
>>>>
>>>> I'll start dredging up the 'how to push a release' knowledge tonight :)
>>>
>>> Status:
>>>
>>>    Tag copied over.
>>>    Distributions uploaded. Synced on Apache machines, propagating out
>>> to mirrors.
>>>    Maven contents in the sync directory, waiting to show up on maven.org.
>>>    Website updated (including Jörg's suggestions). Sync pending.
>>>    Released in JIRA.
>>>
>>> Waiting on maven.org and the mirrors before announcing.
>>
>> It's showing on mirrors now. The Website is synced.
>>
>> Nothing on maven.org though. This is a new addition to the
>> org.apache.commons groupId; do we need to ping someone to make the
>> sync happen?
>
> I think it's good in Nexus now:
>
> https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/
>
> Hopefully that means it'll be heading off to maven.central at some point.
>
> The upload is different from the documentation I was pointed to - but
> fairly easy once you've done it. It should be very scriptable. What I
> did was:
>
> svn export the code
> Run 'mvn source:jar javadoc:jar repository:bundle-create'
> Discover that that wasn't good enough as I didn't have the PGP ascs.
> Fair enough. Start again.
>
> Take the maven repo our current release instructions say to use. Copy
> *.jar, *.pom and *.asc into a directory. Go in there and zip the files
> up into the bundle jar. I used zip and the existing bundle jar from
> step 1, but there's no reason why you couldn't just make it. I doubt
> the manifest is important (and using jar to create the jar rather than
> my habit of zip would help there).
>
> Next login to Nexus and go to the Staging Upload. Choose resource
> bundle (ignore the pom + artifacts as that seems to get confused with
> poms and asc files). Add the bundle. That should work and will point
> you to the location in the staging repo.
>
> Go to staging and hit release.
>
> So ideally this can be pretty easy. Do the current build process. Run
> a script (ant, shell, whatever) to take the jar, pom and asc files and
> stick them in a jar. Then upload that to Nexus and hit release.

Or just use "mvn deploy -Prelease" in the first place, as this creates
and packages the jars for you.

> Fingers crossed that I got this in the right place for this to head to
> the right place :)
>
> Hen
>
> ---------------------------------------------------------------------
> 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