aheritier baerrach bentmann brett brianf carlos dennisl dfabulich dkulp evenisse hboutemy jdcasey kenney krosenvold ltheussl mkleint oching olamy pgier rgoers snicoll stephenc vmassol vsiveton wfay
2011/1/28 Arnaud Héritier <arnaud.herit...@exoplatform.com>: > ok, > It's annoying to not have a mapping between LDAP/SVN groups and Jira. > It could be easier to manage > > On Fri, Jan 28, 2011 at 2:53 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> I've added you. We should get a full list of the PMC's apache jira >> user id's and then any/all of the three of us can add the PMC to the >> project role >> >> 2011/1/28 Arnaud Héritier <arnaud.herit...@exoplatform.com>: >> > you can add me olivier (aheritier) >> > >> > On Fri, Jan 28, 2011 at 12:41 PM, Olivier Lamy <ol...@apache.org> wrote: >> > >> >> Hello, >> >> I have changed the subject. >> >> As asked by Benson, it's probably better to move MPOM from codehaus >> >> jira to ASF jira. >> >> >> >> So I have created a jira entry : >> >> https://issues.apache.org/jira/browse/INFRA-3397 >> >> >> >> I'd like maven dev give me or add in the jira entry their id. >> >> >> >> Thanks ! >> >> -- >> >> Olivier Lamy >> >> http://twitter.com/olamy >> >> http://www.linkedin.com/in/olamy >> >> >> >> 2011/1/28 Olivier Lamy <ol...@apache.org>: >> >> > 2011/1/28 John Casey <jdca...@commonjava.org>: >> >> >> >> >> >> >> >> >> On 1/27/11 4:22 PM, Benson Margulies wrote: >> >> >>> >> >> >>> I want to just put a bit of emphasis on the global impact of this >> POM. >> >> >>> This POM gets advertised as the appropriate parent for \any/ Apache >> >> >>> project building with Maven. As such, I submit to you, it should >> >> >>> supply all of the necessary settings (e.g. repository locations, >> >> >>> deployment) and no surprising extra behavior. If the Land Of Maven >> >> >>> wants a policy of running a full build on prepare, I'd respectfully >> >> >>> ask you to embody that policy in a POM that isn't the one advertised >> >> >>> to the complete Apache community. >> >> >> >> >> >> ...which is why I said in another branch of this thread, that I'm >> okay >> >> with >> >> >> pulling this setting down into the maven parent POM(s). >> >> > >> >> > and document for others AFSERs having this in your pom is RECOMMENDED. >> >> > >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html looks to be >> >> > the appropriate place >> >> > >> >> >> >> >> >>> >> >> >>> On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theussl<ltheu...@apache.org> >> >> >>> wrote: >> >> >>>> >> >> >>>> >> >> >>>> Brian Fox wrote: >> >> >>>>>> >> >> >>>>>> FWIW, if the code-signing step fails due to some POM >> >> misconfiguration, >> >> >>>>>> and >> >> >>>>>> only runs in the perform step, then you've got to rollback the >> >> release >> >> >>>>>> and >> >> >>>>>> try it again...either that, or muck around with manually shifting >> >> the >> >> >>>>>> tag >> >> >>>>>> in >> >> >>>>>> the SCM, which is probably as ugly. >> >> >>>>>> >> >> >>>>>> I'm not as concerned about spending a little extra time to reduce >> >> the >> >> >>>>>> chances of things going wrong in the release process, since this >> >> seems >> >> >>>>>> to >> >> >>>>>> happen often enough already...and causes a HUGE waste of time in >> >> some >> >> >>>>>> cases. >> >> >>>>>> If we were releasing a 100+ module project structure, then I'd be >> >> >>>>>> willing >> >> >>>>>> enough to give on this point and say that accepting a little >> extra >> >> risk >> >> >>>>>> in >> >> >>>>>> the 'perform' phase isn't that big of a deal. But, at least in >> >> Maven, >> >> >>>>>> the >> >> >>>>>> releases aren't that big. >> >> >>>>>> >> >> >>>>> >> >> >>>>> For Lukas: I agree with John here. >> >> >>>>> >> >> >>>>> For everyone else: +1 >> >> >>>> >> >> >>>> >> >> >>>> For everyone: I agree too. Especially with the part about things >> going >> >> >>>> wrong >> >> >>>> often enough. >> >> >>>> >> >> >>>> -Lukas >> >> >>>> >> >> >>>> >> >> >>>>> >> >> >>>>> ;p >> >> >>>>> >> >> >>>>> >> --------------------------------------------------------------------- >> >> >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> >>>>> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >>>>> >> >> >>>> >> >> >>>> >> --------------------------------------------------------------------- >> >> >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> >>>> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >>>> >> >> >>>> >> >> >>> >> >> >>> >> --------------------------------------------------------------------- >> >> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> >>> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >>> >> >> >> >> >> >> -- >> >> >> John Casey >> >> >> Developer, PMC Member - Apache Maven (http://maven.apache.org) >> >> >> Blog: http://www.johnofalltrades.name/ >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >> >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Olivier Lamy >> >> > http://twitter.com/olamy >> >> > http://www.linkedin.com/in/olamy >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
