Re: [maven-scm-api] Looking to perform svn remote move

Le vendredi 18 mai 2018, 22:36:20 CEST Rob Tompkins a écrit : > > On May 18, 2018, at 3:30 PM, Michael Osipov wrote: > > > > Am 2018-05-17 um 15:12 schrieb Rob Tompkins: > > > Hello maven guys, > > > > > > Over on commons we’ve been writing our own release-plugin > > > >

Re: [maven-scm-api] Looking to perform svn remote move

On Fri, May 18, 2018 at 2:36 PM, Rob Tompkins wrote: > > > > On May 18, 2018, at 3:30 PM, Michael Osipov wrote: > > > > Am 2018-05-17 um 15:12 schrieb Rob Tompkins: > > > Hello maven guys, > > > > > > Over on commons we’ve been writing our own

Re: [maven-scm-api] Looking to perform svn remote move

> On May 18, 2018, at 3:30 PM, Michael Osipov wrote: > > Am 2018-05-17 um 15:12 schrieb Rob Tompkins: > > Hello maven guys, > > > > Over on commons we’ve been writing our own release-plugin > > What is wrong with the current Maven Release Plugin and why are you writing >

Re: [maven-release-plugin] Passing additional parameters

Hi Robert, Thanks for your response. After a lot of trial-error, I figured to just what said here: https://github.com/nswamy/incubator-mxnet/blob/v1.2.0/Makefile#L599 -Naveen On Fri, May 18, 2018 at 12:27 PM, Robert Scholte wrote: > Hi, > > this is the important part of

Re: [maven-scm-api] Looking to perform svn remote move

On Fri, May 18, 2018 at 1:30 PM, Michael Osipov wrote: > Am 2018-05-17 um 15:12 schrieb Rob Tompkins: > > Hello maven guys, > > > > Over on commons we’ve been writing our own release-plugin > > What is wrong with the current Maven Release Plugin and why are you > writing

Re: [maven-scm-api] Looking to perform svn remote move

Am 2018-05-17 um 15:12 schrieb Rob Tompkins: > Hello maven guys, > > Over on commons we’ve been writing our own release-plugin What is wrong with the current Maven Release Plugin and why are you writing your own whereas we could improve the current one, can't we? Michael

Re: [maven-release-plugin] Passing additional parameters

Hi, this is the important part of the commandline that tricked you: -Darguments=-DskipTests so -DskipTests is the only argument being passed. If you want to add more, you need to quote them, e.g -Darguments="-DskipTests -Dkey=value" I noticed -Dcxx="$(CXX)" already has quotes, so you need

Re: Accessing licenses/license as POM properties?

On 2018-05-18T16:50:56 +0100 org.apache.maven.u...@io7m.com wrote: > On 2018-05-18T17:01:52 +0200 > Andreas Sewe wrote: > > > here's what I use as an for the maven-bundle-plugin to > > generate a Bundle-License line in my MANIFEST.MF: > > > > >

Re: Accessing licenses/license as POM properties?

On 2018-05-18T17:01:52 +0200 Andreas Sewe wrote: > Hi, > > > Is there a way to access the contents of the element as POM > > properties? I'd like to reference the URL of the first license element > > in a plugin execution, but there doesn't appear to be a >

Re: Accessing licenses/license as POM properties?

Hi, > Is there a way to access the contents of the element as POM > properties? I'd like to reference the URL of the first license element > in a plugin execution, but there doesn't appear to be a > ${pom.license.url} or anything similar. here's what I use as an for the maven-bundle-plugin to

Problem with exec-maven-plugin

Hello all, I have a problem running exec-maven-plugin in a multi-module project _without_ installing snapshots to my local repository. What happens is that Maven seems to require that dependencies are "resolved" during the "generate-sources" phase so if I run "mvn generate-sources" it complains

Accessing licenses/license as POM properties?

Hello. Is there a way to access the contents of the element as POM properties? I'd like to reference the URL of the first license element in a plugin execution, but there doesn't appear to be a ${pom.license.url} or anything similar. -- Mark Raynsford | http://www.io7m.com pgppgAgtlZLqn.pgp