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 > > >
