Hi,
I don't know if it was the original motivation, but at least this gives us
kind of a feature. Releasing is a particular milestone in a project
lifecycle. So having to think twice abt it is not totally bad imo.
For example, passing -DskipTests during a release would be plain nonsense
to me. An
Am 04.09.2011 20:43 schrieb "Benson Margulies" :
>
> On Sun, Sep 4, 2011 at 2:34 PM, Ansgar Konermann
> wrote:
> > Am 04.09.2011 20:29 schrieb "Brian Fox" :
> >>
> >> Release forks the build and therefore not all the parameters are
> >> passed through. There is a parameter for the plugin though to
On Sun, Sep 4, 2011 at 2:34 PM, Ansgar Konermann
wrote:
> Am 04.09.2011 20:29 schrieb "Brian Fox" :
>>
>> Release forks the build and therefore not all the parameters are
>> passed through. There is a parameter for the plugin though to specify
>> which agurments to pass, I forget what it is, but I
Am 04.09.2011 20:29 schrieb "Brian Fox" :
>
> Release forks the build and therefore not all the parameters are
> passed through. There is a parameter for the plugin though to specify
> which agurments to pass, I forget what it is, but I'm sure you know
> how to find it ;-)
-Darguments="..."
>
> O
Release forks the build and therefore not all the parameters are
passed through. There is a parameter for the plugin though to specify
which agurments to pass, I forget what it is, but I'm sure you know
how to find it ;-)
On Sun, Sep 4, 2011 at 1:48 PM, Benson Margulies wrote:
> I was a bit taken
I was a bit taken aback when a run of the maven release plugin failed
because I ran
mvn -gs my_settings.xml release:prepare
and then the build couldn't find the repositories from the global settings?
Is there really on purpose, or should I write up a JIRA?
---
