Yeah as long as the branch is checked out with Git, Maven should work as intended.
-- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On Jan 23, 2017, at 10:32 AM, Arvind Surve <ac...@yahoo.com.INVALID> wrote: > > I have reverted the changes on master branch on Friday. > Investigating the maven changes > > ------------------ Arvind Surve Spark Technology Center > http://www.spark.tc/ > > From: Luciano Resende <luckbr1...@gmail.com> > To: dev@systemml.incubator.apache.org > Sent: Friday, January 20, 2017 5:00 PM > Subject: Re: Building releases now that we have branches > >> On Fri, Jan 20, 2017 at 4:51 PM, <fschue...@posteo.de> wrote: >> >> Yes, this commit probably shouldn't have gone to master... >> Can one of the commiters revert it? >> >> > I would leave for the Release manager to revert it > > >> Now, for the RC2, we will probably need to make the RC based on the commit >>> hash from the top of the 0.12 branch and do a little >>> investigation/research >>> if there is any other changes to make the release prepare to modify the >>> pom >>> from the branch and google is probably your friend here. >>> >> >> Not sure what you mean here - can't we tag a new release candidate on the >> branch-0.12? What (except for the tag) would have to change in the pom? >> >> -Felix >> >> > We currently use a script to create the release, and it will call maven > release:prepare which change the pom version to release version, and them > modify to the new development version. I just want to make sure it will > make these changes on the branch and not on master. Not sure if maven needs > any additional magic for that, it will be our first time running the script > on a branch. > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > >
