Ok - got it. I will merge and then re-do the release with these settings. On Thu, Aug 25, 2016 at 11:30 AM, Suneel Marthi <[email protected]> wrote:
> We are not changing the Nexus staging at all - the new URL would be the > Nexus staging repo. > > This was the first comment that Justin had made asking to avoid using > maven2 as staging repo and instead use the one in the PR. > > If we had to update the artifacts like we are doing now, with the maven2 > URL there's no way to update them unless the whole process was rolled back; > its easier to do that with new URL since it would be a simple SVN checkout; > svn commit. > > We don't really need <dependencyManagement> when there's Parent POM, the > deploy URL could be part of settings.xml and that seems to be the preferred > way across many other projects. > > > > > > On Thu, Aug 25, 2016 at 11:10 AM, ellisonanne <[email protected]> wrote: > > > Github user ellisonanne commented on the issue: > > > > https://github.com/apache/incubator-pirk/pull/79 > > > > Why are we making this change? It seems to be reasonable to keep the > > deploy location as our Nexus staging repo and then to move the artifacts > > over to the dist repo once everything passes, especially since we would > > like to have a Pirk maven dependency. Please let me know if this is not > the > > correct protocol... > > > > > > --- > > If your project is set up for it, you can reply to this email and have > your > > reply appear on GitHub as well. If your project does not have this > feature > > enabled and wishes so, or if the feature is enabled but not working, > please > > contact infrastructure at [email protected] or file a JIRA > ticket > > with INFRA. > > --- > > >
