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 <suneel.mar...@gmail.com> wrote: > One other thing we need to figure out for next release. You shouldn't have > to specify the <distributionManagement> 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 Sat, Aug 13, 2016 at 8:57 AM, Suneel Marthi <suneel.mar...@gmail.com> > 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 -Psigned_release release:clean >> >> and then git tag -d <tagname> ----> delete the local tag >> >> Following ^^^^, the next time u run >> >> mvn -Psigned_release release:prepare -> u will be prompted for version >> info. >> >> On Sat, Aug 13, 2016 at 8:42 AM, Ellison Anne Williams < >> eawilliamsp...@gmail.com> wrote: >> >>> Oops! Well, at least the pom is straightened out now. :) >>> >>> We do need to remove the artifacts from Nexus2 repo (they are incorrectly >>> named anyway as we must use the <version>-incubating naming convention). >>> >>> Now I will proceed with cutting the release branch 0.1.0 for vote and send >>> the email. >>> >>> To test the new pom, I did the following: >>> >>> - mvn clean release:clean >>> - mvn release:prepare -Darguments="-DskipTests" (new version: >>> 0.1.0-incubating; SCM: apache-pirk-0.1.0-incubating; new dev version: >>> 0.1.1-SNAPSHOT) >>> - mvn -Psigned_release release:perform -DdryRun=true >>> -Darguments="-DskipTests" >>> >>> where 'signed_release' is defined in the settings.xml file. (All of this >>> info will be posted to the website once we have it down). >>> >>> It seems best not to use the ' -Psigned_release' arg when using 'mvn >>> release:prepare' as you are not prompted for the versioning information. >>> >>> >>> >>> On Sat, Aug 13, 2016 at 1:47 AM, Suneel Marthi <smar...@apache.org> >>> wrote: >>> >>> > ...and here is the Infra jira with the setup for Pirk >>> > >>> > https://issues.apache.org/jira/browse/INFRA-12383 >>> > >>> > On Sat, Aug 13, 2016 at 1:23 AM, Suneel Marthi <smar...@apache.org> >>> wrote: >>> > >>> > > So the release process works and its now repeatable. >>> > > >>> > > I had the repository URL (in POM) as https://repository.apache. >>> > > org/content/repositories/releases >>> > > and that completely bypassed the staging process and (we have a Pirk >>> > > release - Mehhh, sorry! :-). >>> > > >>> > > See https://repository.apache.org/content/groups/public/org/ >>> > > apache/pirk/apache-pirk/0.0.1/ >>> > > >>> > > We'll have to revert that ^^^, its not valid. >>> > > >>> > > Things to do next: >>> > > >>> > > 1. Figure out how to purge the artifacts from https://repository. >>> > > apache.org/content/groups/public/org/apache/pirk/apache-pirk/0.0.1/ >>> > > >>> > > 2. Check out the latest code from master >>> > > >>> > > 3. Perform the release >>> > > >>> > > a) mvn -Psigned_release release:prepare release:perform >>> > > b) Check Nexus staging for the release artifacts. >>> > > >>> > > Sorry about the botch, shuld have remembered that Infra had created >>> the >>> > > staging repositories for this project and updated POM accordingly. >>> > > >>> > > Suneel >>> > > >>> > > On Sat, Aug 13, 2016 at 12:13 AM, Suneel Marthi <smar...@apache.org> >>> > > wrote: >>> > > >>> > >> Since Pirk project is a single module we don't need to include >>> > >> 'apache-release' profile for the release. >>> > >> >>> > >> Specifying -Papache-release mandates that the project have a >>> > >> /distribution module (which Pirk does not today). >>> > >> >>> > >> I am gonna add the <repository> from ur PR, commit that to master and >>> > try >>> > >> creating a staging artifact. >>> > >> >>> > >> On Fri, Aug 12, 2016 at 8:21 PM, Ellison Anne Williams < >>> > >> eawilliamsp...@gmail.com> wrote: >>> > >> >>> > >>> With the added repo in the pom file and the updated settings.xml >>> file, >>> > >>> the >>> > >>> error was the same for 'mvn release:perform' (and 'mvn >>> > >>> -Psigned_release,apache-release release:perform'). >>> > >>> >>> > >>> Failed to execute goal org.apache.maven.plugins:maven >>> > >>> -deploy-plugin:2.7:deploy >>> > >>> (default-deploy) on project apache-pirk: Deployment failed: >>> repository >>> > >>> element was not specified in the POM inside distributionManagement >>> > >>> element >>> > >>> or in -DaltDeploymentRepository=id::layout::url parameter >>> > >>> >>> > >>> Do you have a 'distributionManagement' tag that you are setting in >>> the >>> > >>> pom? >>> > >>> >>> > >>> On Fri, Aug 12, 2016 at 7:47 PM, Suneel Marthi < >>> > suneel.mar...@gmail.com> >>> > >>> wrote: >>> > >>> >>> > >>> > 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 < >>> > >>> > eawilliamsp...@gmail.com> wrote: >>> > >>> > >>> > >>> > > Thanks - I will give it another whirl >>> > >>> > > >>> > >>> > > On Fri, Aug 12, 2016 at 7:36 PM, Suneel Marthi < >>> > >>> suneel.mar...@gmail.com> >>> > >>> > > 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/ac1b5058f05ab17d2f84862940ec >>> 4eba >>> > >>> > > > >>> > >>> > > > >>> > >>> > > > >>> > >>> > > > >>> > >>> > > > >>> > >>> > > > On Fri, Aug 12, 2016 at 7:23 PM, Ellison Anne Williams < >>> > >>> > > > eawilliamsp...@gmail.com> 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 < >>> > >>> smar...@apache.org> >>> > >>> > > > 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 < >>> > >>> > > > > > eawilliamsp...@gmail.com> 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 >>> > >>> > > > > > > >>> > >>> > > > > > >>> > >>> > > > > >>> > >>> > > > >>> > >>> > > >>> > >>> > >>> > >>> >>> > >> >>> > >> >>> > > >>> > >>> >> >>
