On 19 July 2011 21:33, Henri Yandell <flame...@gmail.com> wrote: > On Tue, Jul 19, 2011 at 1:16 PM, sebb <seb...@gmail.com> wrote: >> On 19 July 2011 20:12, Phil Steitz <phil.ste...@gmail.com> wrote: >>> On 7/19/11 11:39 AM, Matt Benson wrote: >>>> On Tue, Jul 19, 2011 at 1:22 PM, Henri Yandell <flame...@gmail.com> wrote: >>>>> On Tue, Jul 19, 2011 at 10:04 AM, Phil Steitz <phil.ste...@gmail.com> >>>>> wrote: >>>>>> On 7/19/11 9:32 AM, Henri Yandell wrote: >>>>>>> On Tue, Jul 19, 2011 at 1:52 AM, Henri Yandell <flame...@gmail.com> >>>>>>> wrote: >>>>>>>> On Mon, Jul 18, 2011 at 6:37 PM, Henri Yandell <flame...@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? >>>>>> Unfortunately, I think you have no choice but to use nexus. I think >>>>>> the whole tree, org.apache.commons is now forced to use nexus. You >>>>>> can try asking on repository@. >>>>> Looks that way, and it looks like you can't upload artifacts to nexus >>>>> but instead have to either write Ivy code or put Maven in charge of >>>>> your release management, doing all the staging through nexus. >>>>> >>>> So at this point we're better off ULing through Ivy? Among us, either >>>> Stefan or I would probably be best suited to attempt this. >>> >>> Personally, I would greatly appreciate this. I was planning to try >>> to imitate the tomcat setup that Mark referred to [1] earlier for >>> the upcoming [pool] and [dbcp] releases. Unfortunately, in order >>> for that to work, we have to agree to move back to ibiblio-rysnch >>> for all of o.a.c. As it stands now, we are stuck with nexus for all >>> but the old separate groupId components. >> >> I managed to use Nexus to upload the Daemon artifacts. >> >> IIRC, I created a bundle first, but I think one can upload files separately. >> >> However, it's easier to use "mvn deploy" in the first place. > > It's LDAP based right? ie) I should be seeing the same upload features > that you're seeing in the UI?
Nexus uses LDAP.for login; I assume it uses LDAP groups for access rights once logged in. e.g. I can see Mina, BSF, HttpComponents and Commons entries. > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
