what other choice do we have?
We always do that way, and it does not prevent users to grab a tag and
rebuild as the second staging will be promoted as well, so binaries will be
available on apache public repo.

JLouis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Jun 17, 2014 at 3:19 PM, Romain Manni-Bucau <[email protected]>
wrote:

> Hi Andy
> We released several times with staging repo references and each time we got
> issues cause of it so i m for not doing it anymore, it bothers too much
> users trying to build tags
>
> Le mardi 17 juin 2014, Andy Gumbrecht <[email protected]> a écrit :
> > Hi Devs,
> >
> > The conundrum, run a 1.7.0 roll vote on TomEE with a staged dependency
> (in this case org.apache.openejb.patch:openjpa:2.4.0-nonfinal-1598334).
> >
> > I know now, after IRC feedback, we 'usually' do this by using the same
> staging repository for the TomEE roll and leave the pom as is. What I don't
> like about that is that 'after' a successful roll we publish a pom that
> still references the then deleted staging repository - This is not an issue
> as such, but leads to resolution warnings in the Maven build on the final
> released version (we can't modify the pom after a successful roll). This is
> trivial I guess, but deserves a second look at ways we could improve this.
> >
> > I was wrongly assuming that the way we 'would' do this is to publish
> (vote) the item being staged first, remove staging from the pom and then
> run the TomEE vote roll. This just seemed logical to me to do it that way.
> > Before I completely give up on this path I'd just like to get some
> feedback as to why this is not practical and or allowed, or get some
> suggestions on how we could do this in a more clean fashion?
> >
> > Andy.
> >
> > --
> >   Andy Gumbrecht
> >
> >   http://www.tomitribe.com
> >   [email protected]
> >   https://twitter.com/AndyGeeDe
> >
> >   TomEE treibt Tomitribe! | http://tomee.apache.org
> >
> >
>
> --
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>

Reply via email to