Here's the steps and we can validate each of these as we go thru the process:
1. Update settings.xml 2. mvn -Psigned-release,apache-release package 3. mvn -Psigned-release,apache-release release:prepare 4. mvn -Psigned-release,apache-release release:perform Successful completion of Step 4 should deploy the projects artifacts on Nexus staging. >From browser, go to https://repository.apache.org/ and log in with Apache credentials. 1. Click the Staging Repositories in left menu 2. Click the staging repo for Pirk. 3. Click Close in the toolbar This last step should put the artifacts in staging area for testing. Post the link for the staging artifacts to dev@ for Voting on the release. On Fri, Aug 12, 2016 at 7:39 PM, Ellison Anne Williams < [email protected]> wrote: > Thanks - I will give it another whirl > > On Fri, Aug 12, 2016 at 7:36 PM, Suneel Marthi <[email protected]> > wrote: > > > Ok, yes we need to add this to repositories in POM - we can copy from > > what's available in NiFi. > > > > Here's the gist of my settings.xml - > > https://gist.github.com/smarthi/ac1b5058f05ab17d2f84862940ec4eba > > > > > > > > > > > > On Fri, Aug 12, 2016 at 7:23 PM, Ellison Anne Williams < > > [email protected]> wrote: > > > > > Can you email your settings.xml file (masking out the key info, etc)? > > > > > > After adding the apache-release profile to the pom, mvn release would > > > function but perform failed as it did not know the repo to which to > > > 'publish' the release. > > > > > > Would rather stay on email for the benefit of others. > > > > > > On Fri, Aug 12, 2016 at 7:19 PM, Suneel Marthi <[email protected]> > > wrote: > > > > > > > I think u need to add a 'signed-release' profile to ur local > > settings.xml > > > > (not needed in the POM). > > > > > > > > That's how I tested release-prepare. > > > > > > > > It would be easier if we met on the project slack channel as we work > > thru > > > > the release - pirk.slack.com, u can login with ur apache.org email. > > > > > > > > On Fri, Aug 12, 2016 at 7:15 PM, Ellison Anne Williams < > > > > [email protected]> wrote: > > > > > > > > > Hi, > > > > > > > > > > In order to have mvn release function, I had to update the POM file > > as > > > > per > > > > > PIRK-50; a PR is in the queue. There are still more items that > could > > be > > > > > added (as per > > > > > https://svn.apache.org/viewvc/maven/pom/tags/apache-18/pom. > > > > xml?view=markup > > > > > ), > > > > > but it's a basic step in the right direction (at least mvn > > > > release:prepare > > > > > works now). > > > > > > > > > > An additional question for getting 'mvn release:perform' to > function: > > > It > > > > > appears that we need to include an additional repo in the pom for > > > > releasing > > > > > in order for 'mvn release:perform' to function correctly. NiFi > seems > > to > > > > use > > > > > https://repository.apache.org/content/repositories/releases. > Should > > we > > > > do > > > > > the same? > > > > > > > > > > I will wait to cut the release branch until we can get the POM > > correct > > > > for > > > > > releasing (i.e. accept the PIRK-50 PR, adding in the info dictated > by > > > the > > > > > answer for the question above ). > > > > > > > > > > Thanks, > > > > > > > > > > Ellison Anne > > > > > > > > > > > > > > >
