Re: Mentor Question -- Release and Pom File

Ok, each project does it a little different. Cool, we'll leave POM as it now. Filing an Infra ticket now to purge the release artifacts. On Sat, Aug 13, 2016 at 9:27 AM, Joe Witt wrote: > i don't believe that would be necessary. Here is the entirety of my > maven settings

Re: Mentor Question -- Release and Pom File

I had the real apache repo URL in POM as opposed to the staging URL. So that completely bypassed staging. If I am understanding correctly, we need to add the Parent POM and remove from POM - the later should be specified in settings.xml. Agree? On Sat, Aug 13, 2016 at 9:16 AM, Joe Witt

Re: Mentor Question -- Release and Pom File

Yep - that did it - thanks! On Sat, Aug 13, 2016 at 8:57 AM, Suneel Marthi wrote: > You should use -Psigned_release. > > Once u r past release:prepare and release:perform and u need to rollback. > > -- run mvn -Psigned_release release:rollback > mvn

Re: Mentor Question -- Release and Pom File

One quick thing I noticed is it doesn't look like we're using the apache parent pom. That helps a lot. On Sat, Aug 13, 2016 at 9:03 AM, Suneel Marthi wrote: > One other thing we need to figure out for next release. You shouldn't have > to specify the repository info in

Re: Mentor Question -- Release and Pom File

One other thing we need to figure out for next release. You shouldn't have to specify the repository info in POM, its best done in settings.xml (that's how we do it on Mahout). I tried doing it that way but it didn't work for whatever reason and I ended up explicitly declaring that in POM. On