date:20170508

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-08 Thread Karl Heinz Marbaise


Hi to all,

I think it is needed to explain that in more detail (means also to 
improve the ci documentation).



Let me start with the following:

You can only use those three names "revision", "changelist" and "sha1" 
in a version tag of the pom file cause they are handled special (the 
foundation of its handling is given by the explanation of Bernd 
Eckenfeld Thanks to Bernd).


This means in consequence the given part will not work as expected (at 
the moment):


com.soebes.examples.j2ee parent
${revision}
pom

  1.2.1-${buildNumber}
  SNAPSHOT



If you like to make combinations you can do it like this for example:
(https://github.com/khmarbaise/javaee/tree/maven350-properties):

  com.soebes.examples.j2ee
  parent
  ${revision}${sha1}${changelist}
  pom

  
1.6
1.6
1.3.1
-SNAPSHOT

  

or to pickup the previous example which should look like this:

com.soebes.examples.j2ee parent
${revision}${changelist}
pom

  1.2.1
  -SNAPSHOT


So now your build will work as expected.

If you like to switch to release you simply do that by using the following:

mvn -Dchangelist= clean package (This will define changelist as empty).

Or if you like to give a buildNumber from commandline:

mvn -Dchangelist=-23-SNAPSHOT clean package

So to make it more convenient you can define the versions like this:

  com.soebes.examples.j2ee
  parent
  ${revision}${sha1}${changelist}
  pom

  
1.6
1.6
1.3.1
-SNAPSHOT

  

So now I can build via (be carefull with the separator between version 
and buildnumber "-"):


mvn -Dsha1=-123 clean package

By the above you can now define many combinatations on the command line:

mvn -Dchangelist= clean package

This means the command line overwrites the values of the properties 
which are defined in the pom file (properties section).


You can of course remove the properties (properties section) from the 
pom file at all and only define the information on command line (works 
in Eclipse). But you can also define those things in ".mvn/maven.config" 
via the appropriate "-D...".



So now lets come to the point about flatten-maven-plugin:

Assume you are using above proerties in kind of flavour...now you are 
using my example( 
https://github.com/khmarbaise/javaee/tree/maven350-properties) without 
the flatten-maven-plugin in the build:


mvn install

The result of that would be having a folder in your local cache like 
etc. where you find a jar file and of course a pom file: (I just picked 
up two files as example):


$HOME/.m2/repository/com/soebes/examples/j2ee/parent/1.3.1-SNAPSHOT/parent-1.3.1-SNAPSHOT.pom
$HOME//.m2/repository/com/soebes/examples/j2ee/domain/1.3.1-SNAPSHOT/domain-1.3.1-SNAPSHOT.jar

Looks Ok so far? But let us take a look into the pom file:

The pom file will look like this:


  com.soebes.examples.j2ee
  parent
  ${revision}${sha1}${changelist}
  pom

  
1.6
1.6
1.3.1
-SNAPSHOT

  

This looks ok so far (on the first glance)

But now I have given mvn -Drevision=2.0.0 install

There will produced also files like this:

$HOME/.m2/repository/com/soebes/examples/j2ee/parent/2.0.0-SNAPSHOT/parent-2.0.0-SNAPSHOT.pom

The pom file will look like exactly the same:


  com.soebes.examples.j2ee
  parent
  ${revision}${sha1}${changelist}
  pom

  
1.6
1.6
1.3.1
-SNAPSHOT

  

which is obviouly wrong(the same is if you omit the revision, 
changelist and sha1 from properties part).


If you like to consume this pom file it will fail cause this can't be 
correctly solve (where is the -Drevision=2.0.0 gone?)



That is the reason you need the flatten-maven-plugin cause it replace 
the propreties in the version tag with it's current version (can do more 
but that's a different story) and produce a correct pom file:


http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd; 
xmlns="http://maven.apache.org/POM/4.0.0;

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  4.0.0
  com.soebes.examples.j2ee
  parent
  2.0.0-SNAPSHOT
  pom
  

  Apache License 2.0
  http://www.apache.org/licenses/LICENSE-2.0.txt
  repo

  

which is now consumeable by any kind of tool etc. also Maven itself for 
example as a dependency


I hope it makes this more clear...

If not please ask/suggest improvements about the docs or what you need 
to know


Kind regards
Karl Heinz Marbaise







On 08/05/17 14:29, Stephen Connolly wrote:

On Mon 8 May 2017 at 03:58, Eric Benzacar  wrote:


Hi,

Interesting.  Would something like this be functional then?  It seems to
work, but I don't know if it is working as expected, or by fluke:

com.soebes.examples.j2ee parent
${revision} pom .. 

1.2.1-${buildNumber}
SNAPSHOT



Then at the command line, I can either set the buildNumber in the case of a
build:
mvn installl -DbuildNumber=12345

This works, but I don't know if I am using this as designed/expected.



Nope it only *appears to work*

If you dig

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-08 Thread Karl Heinz Marbaise


Hi Dan,

On 08/05/17 18:48, Dan Tran wrote:

Hi Karl

I think you already made changes to the the plugin,  but will file ticket
to make it official


https://github.com/mojohaus/flatten-maven-plugin/issues/41

Already done by your ticket..

Kind regards
Karl Heinz




-D

On Thu, May 4, 2017 at 10:09 PM, Karl Heinz Marbaise 
wrote:


Hi Dan,

On 05/05/17 02:30, Dan Tran wrote:


is flatten-maven-plugin threadsafe?   if not, we have a problem with large
project where multhreaded build is a must have

maven 3.5 displays a warning on flatten-maven-plugin not thread safe



I need to take a look...can you file in a ticket on flatten-maven-plugin..

Thanks.

Kind regards
Karl Heinz Marbaise



Thanks

-D

On Thu, May 4, 2017 at 2:52 PM, Karl Heinz Marbaise 
wrote:

Hi,


On 04/05/17 22:52, Justin Georgeson wrote:

Also I believe the partial reactor switches don't work for Tycho builds.




You mean -pl ..option I suppose?

As far as I know Tycho is handling that at the wrong time of the maven
build and furthermore handles in this relationship some other things
wrong
which results in not working things like this..


Kind regards
Karl Heinz Marbaise


-Original Message-

From: Robert Patrick [mailto:robert.patr...@oracle.com]
Sent: Thursday, May 4, 2017 3:18 PM
To: Maven Users List ; i...@soebes.de
Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

External Sender: Use caution with links/attachments.



Hard to train developers to break old habits but thanks... :-)



-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Thursday, May 04, 2017 3:16 PM
To: Robert Patrick; Maven Users List; i...@soebes.de
Subject: Re: Continuous Delivery with Maven now possible?

Hi Robert,

Ah now I see the issue.

If you have a multi module build you should use

mvn -pl moduleToBuild clean install

but from root location and don't change into the module directory cause
this can't work like this.

Kind regards
Karl Heinz Marbaise

On 04/05/17 22:08, Robert Patrick wrote:

Hi Karl,


If I define the revision property in the top-level POM, I cannot refer
to it in the module POMs'  elements *and* still retain the
ability
to build from the module directory, right?  I tried this and it failed
because it was unable to resolve the revision property variable.

C:\rpatrick\work\projects\jcs-las\util>mvn clean install [INFO]
Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the
POMs:
[FATAL] Non-resolvable parent POM for
oracle.jcs.lifecycle:util:[unknown-version
]: Failure to find oracle.jcs.lifecycle:app-to-cloud:pom:${revision}
in
https://urldefense.proofpoint.com/v2/url?u=http-3A__a=DwIDaQ=RoP1Y
umCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr
_pt_OzwdxJosG0=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=by9ucii
pxSZU0-Wn16t7grG7a5Djk4ZH9440pGIayRE=
https://urldefense.proofpoint.com/v2/url?u=http-3A__rtifactory-2Dslc.o
raclecorp.com_artifactory_repo1=DwIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYB
RbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=mQrJO
CEKXlLF5VNECH6aqvyAu4kATrZgYUsiitvnfwY=oPO-3-7EEwzSMAr8-re0YxZdReMu1
5_A4OMXDtdtFyA=  was cached in the local reposito ry, resolution will
not be reattempted until the update interval of repo1 has el apsed or
updates are forced and 'parent.relativePath' points at wrong local POM
@
line 7, column 13  @ [ERROR] The build could not read 1 project ->
[Help 1]
[ERROR]
[ERROR]   The project oracle.jcs.lifecycle:util:[unknown-version]
(C:\rpatrick\w
ork\projects\jcs-las\util\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for
oracle.jcs.lifecycle:util:[unk
nown-ver
sion]: Failure to find
oracle.jcs.lifecycle:app-to-cloud:pom:${revision} in http
://artifactory-slc.oraclecorp.com/artifactory/repo1 was cached in the
local repo sitory, resolution will not be reattempted until the update
interval of repo1 ha s elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 7, column 13 ->
[Help 2] [ERROR] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e swit ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea d the following articles:
[ERROR] [Help 1]
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
onfluence_display_MAVEN_ProjectBuildin=DwIDaQ=RoP1YumCXCgaWHvlZYR8
PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=Gpqh8tXn87EJPGvORYVRoH
s2ncTiyaZSJWc3AEyEsUQ=
gException
[ERROR] [Help 2]
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
onfluence_display_MAVEN_UnresolvableMo=DwIDaQ=RoP1YumCXCgaWHvlZYR8
PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=kjqcy_wD0H5qwfISMGTZrq

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-08 Thread Dan Tran

Hi Karl

I think you already made changes to the the plugin,  but will file ticket
to make it official

-D

On Thu, May 4, 2017 at 10:09 PM, Karl Heinz Marbaise 
wrote:

> Hi Dan,
>
> On 05/05/17 02:30, Dan Tran wrote:
>
>> is flatten-maven-plugin threadsafe?   if not, we have a problem with large
>> project where multhreaded build is a must have
>>
>> maven 3.5 displays a warning on flatten-maven-plugin not thread safe
>>
>
> I need to take a look...can you file in a ticket on flatten-maven-plugin..
>
> Thanks.
>
> Kind regards
> Karl Heinz Marbaise
>
>
>> Thanks
>>
>> -D
>>
>> On Thu, May 4, 2017 at 2:52 PM, Karl Heinz Marbaise 
>> wrote:
>>
>> Hi,
>>>
>>> On 04/05/17 22:52, Justin Georgeson wrote:
>>>
>>> Also I believe the partial reactor switches don't work for Tycho builds.


>>> You mean -pl ..option I suppose?
>>>
>>> As far as I know Tycho is handling that at the wrong time of the maven
>>> build and furthermore handles in this relationship some other things
>>> wrong
>>> which results in not working things like this..
>>>
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
>>> -Original Message-
 From: Robert Patrick [mailto:robert.patr...@oracle.com]
 Sent: Thursday, May 4, 2017 3:18 PM
 To: Maven Users List ; i...@soebes.de
 Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

 External Sender: Use caution with links/attachments.



 Hard to train developers to break old habits but thanks... :-)



 -Original Message-
 From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
 Sent: Thursday, May 04, 2017 3:16 PM
 To: Robert Patrick; Maven Users List; i...@soebes.de
 Subject: Re: Continuous Delivery with Maven now possible?

 Hi Robert,

 Ah now I see the issue.

 If you have a multi module build you should use

 mvn -pl moduleToBuild clean install

 but from root location and don't change into the module directory cause
 this can't work like this.

 Kind regards
 Karl Heinz Marbaise

 On 04/05/17 22:08, Robert Patrick wrote:

 Hi Karl,
>
> If I define the revision property in the top-level POM, I cannot refer
> to it in the module POMs'  elements *and* still retain the
> ability
> to build from the module directory, right?  I tried this and it failed
> because it was unable to resolve the revision property variable.
>
> C:\rpatrick\work\projects\jcs-las\util>mvn clean install [INFO]
> Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the
> POMs:
> [FATAL] Non-resolvable parent POM for
> oracle.jcs.lifecycle:util:[unknown-version
> ]: Failure to find oracle.jcs.lifecycle:app-to-cloud:pom:${revision}
> in
> https://urldefense.proofpoint.com/v2/url?u=http-3A__a=DwIDaQ=RoP1Y
> umCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr
> _pt_OzwdxJosG0=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=by9ucii
> pxSZU0-Wn16t7grG7a5Djk4ZH9440pGIayRE=
> https://urldefense.proofpoint.com/v2/url?u=http-3A__rtifactory-2Dslc.o
> raclecorp.com_artifactory_repo1=DwIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYB
> RbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=mQrJO
> CEKXlLF5VNECH6aqvyAu4kATrZgYUsiitvnfwY=oPO-3-7EEwzSMAr8-re0YxZdReMu1
> 5_A4OMXDtdtFyA=  was cached in the local reposito ry, resolution will
> not be reattempted until the update interval of repo1 has el apsed or
> updates are forced and 'parent.relativePath' points at wrong local POM
> @
> line 7, column 13  @ [ERROR] The build could not read 1 project ->
> [Help 1]
> [ERROR]
> [ERROR]   The project oracle.jcs.lifecycle:util:[unknown-version]
> (C:\rpatrick\w
> ork\projects\jcs-las\util\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for
> oracle.jcs.lifecycle:util:[unk
> nown-ver
> sion]: Failure to find
> oracle.jcs.lifecycle:app-to-cloud:pom:${revision} in http
> ://artifactory-slc.oraclecorp.com/artifactory/repo1 was cached in the
> local repo sitory, resolution will not be reattempted until the update
> interval of repo1 ha s elapsed or updates are forced and
> 'parent.relativePath' points at wrong local POM @ line 7, column 13 ->
> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e swit ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please rea d the following articles:
> [ERROR] [Help 1]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
> onfluence_display_MAVEN_ProjectBuildin=DwIDaQ=RoP1YumCXCgaWHvlZYR8
>

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-08 Thread Karl Heinz Marbaise


Hi Dan,

On 05/05/17 02:30, Dan Tran wrote:

is flatten-maven-plugin threadsafe?   if not, we have a problem with large
project where multhreaded build is a must have

maven 3.5 displays a warning on flatten-maven-plugin not thread safe


I need to take a look...can you file in a ticket on flatten-maven-plugin..

Thanks.
Kind regards
Karl Heinz Marbaise



Thanks

-D

On Thu, May 4, 2017 at 2:52 PM, Karl Heinz Marbaise 
wrote:


Hi,

On 04/05/17 22:52, Justin Georgeson wrote:


Also I believe the partial reactor switches don't work for Tycho builds.



You mean -pl ..option I suppose?

As far as I know Tycho is handling that at the wrong time of the maven
build and furthermore handles in this relationship some other things wrong
which results in not working things like this..


Kind regards
Karl Heinz Marbaise



-Original Message-
From: Robert Patrick [mailto:robert.patr...@oracle.com]
Sent: Thursday, May 4, 2017 3:18 PM
To: Maven Users List ; i...@soebes.de
Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

External Sender: Use caution with links/attachments.



Hard to train developers to break old habits but thanks... :-)



-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Thursday, May 04, 2017 3:16 PM
To: Robert Patrick; Maven Users List; i...@soebes.de
Subject: Re: Continuous Delivery with Maven now possible?

Hi Robert,

Ah now I see the issue.

If you have a multi module build you should use

mvn -pl moduleToBuild clean install

but from root location and don't change into the module directory cause
this can't work like this.

Kind regards
Karl Heinz Marbaise

On 04/05/17 22:08, Robert Patrick wrote:


Hi Karl,

If I define the revision property in the top-level POM, I cannot refer
to it in the module POMs'  elements *and* still retain the ability
to build from the module directory, right?  I tried this and it failed
because it was unable to resolve the revision property variable.

C:\rpatrick\work\projects\jcs-las\util>mvn clean install [INFO]
Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for
oracle.jcs.lifecycle:util:[unknown-version
]: Failure to find oracle.jcs.lifecycle:app-to-cloud:pom:${revision}
in
https://urldefense.proofpoint.com/v2/url?u=http-3A__a=DwIDaQ=RoP1Y
umCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr
_pt_OzwdxJosG0=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=by9ucii
pxSZU0-Wn16t7grG7a5Djk4ZH9440pGIayRE=
https://urldefense.proofpoint.com/v2/url?u=http-3A__rtifactory-2Dslc.o
raclecorp.com_artifactory_repo1=DwIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYB
RbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=mQrJO
CEKXlLF5VNECH6aqvyAu4kATrZgYUsiitvnfwY=oPO-3-7EEwzSMAr8-re0YxZdReMu1
5_A4OMXDtdtFyA=  was cached in the local reposito ry, resolution will
not be reattempted until the update interval of repo1 has el apsed or
updates are forced and 'parent.relativePath' points at wrong local POM @
line 7, column 13  @ [ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project oracle.jcs.lifecycle:util:[unknown-version]
(C:\rpatrick\w
ork\projects\jcs-las\util\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for oracle.jcs.lifecycle:util:[unk
nown-ver
sion]: Failure to find
oracle.jcs.lifecycle:app-to-cloud:pom:${revision} in http
://artifactory-slc.oraclecorp.com/artifactory/repo1 was cached in the
local repo sitory, resolution will not be reattempted until the update
interval of repo1 ha s elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 7, column 13 ->
[Help 2] [ERROR] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e swit ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea d the following articles:
[ERROR] [Help 1]
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
onfluence_display_MAVEN_ProjectBuildin=DwIDaQ=RoP1YumCXCgaWHvlZYR8
PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=Gpqh8tXn87EJPGvORYVRoH
s2ncTiyaZSJWc3AEyEsUQ=
gException
[ERROR] [Help 2]
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
onfluence_display_MAVEN_UnresolvableMo=DwIDaQ=RoP1YumCXCgaWHvlZYR8
PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=kjqcy_wD0H5qwfISMGTZrq
XoHWM-jV5GAbTtEvug-bc=
delException


Did I miss something?

Thanks,
Robert

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Thursday, May 04, 2017 3:02 PM
To: Maven Users List
Subject: Re: Continuous Delivery with Maven now possible?

Hi Robert,


On 04/05/17 21:55, Robert Patrick wrote:

With 3.5, you can now use a variable

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-08 Thread Stephen Connolly

On Mon 8 May 2017 at 03:58, Eric Benzacar  wrote:

> Hi,
>
> Interesting.  Would something like this be functional then?  It seems to
> work, but I don't know if it is working as expected, or by fluke:
>
> com.soebes.examples.j2ee parent
> ${revision} pom .. 
> 
> 1.2.1-${buildNumber}
> SNAPSHOT
> 
>
>
> Then at the command line, I can either set the buildNumber in the case of a
> build:
> mvn installl -DbuildNumber=12345
>
> This works, but I don't know if I am using this as designed/expected.


Nope it only *appears to work*

If you dig deeper you will see it is not working.

The properties *must* be provided either on the CLI or by an extension. At
least as I understand it


>
> Thanks,
>
> Eric
>
>
> On Sun, May 7, 2017 at 9:59 PM, Bernd Eckenfels 
> wrote:
>
> > Hello,
> >
> > Only those specific properties are allowed. If I remember correctly the
> > reason for it is a mixture between it is not possible to support full
> > property resolving in this stage of the model builder and the intention
> to
> > harmonize/restrict to familiarly named usecases.
> >
> > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=
> > blobdiff;f=maven-model-builder/src/main/java/org/apache/maven/model/
> > interpolation/AbstractStringBasedModelInterpolator.java;h=
> >
> b47edbe9898b42e25e53afdfb0447ba59183f6a5;hp=cee376f1134db6d78a8bd78ff9f0c7
> > 108d86e448;hb=51cc76c32625be2f807dcf2ffbeb085984729b57;hpb=
> > 181b0215aa1199e152db9d2c08b1a01436547805
> >
> > Gruss
> > Bernd
> > --
> > http://bernd.eckenfels.net
> > 
> > From: Eric Benzacar 
> > Sent: Monday, May 8, 2017 3:35:46 AM
> > To: Maven Users List
> > Cc: i...@soebes.de
> > Subject: Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?
> >
> > I'm confused by something in Karl's blog as well as the instructions for
> > the flatten-maven-plugin and the actual release notes for Maven 3.5.
> >
> > In all the above, they talk about the ${revision}, ${sha1}, ${changelist}
> > parameters.  But what is so special about those particular parameters?
> Can
> > I not use any parameter named of my choosing?
> >
> > Afterall, the ${revision} value is being set by an environment property,
> so
> > can I not just call it ${buildNumber} instead?
> >
> > Ex:
> >
> > com.soebes.examples.j2ee parent > artifactId>
> > 1.2.1-${buildNumber} pom ..
> >  ... SNAPSHOT 
> >
> >
> > Why do I need to use ${revision}?
> > https://maven.apache.org/maven-ci-friendly.html specifically mentions
> the
> > above parameters.  Why?
> >
> >
> > Thanks,
> >
> > Eric
> >
> >
> > On Thu, May 4, 2017 at 9:40 PM, Justin Georgeson 
> > wrote:
> >
> > > Yup :)
> > >
> > > -Original Message-
> > > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> > > Sent: Thursday, May 4, 2017 4:52 PM
> > > To: Justin Georgeson ; Maven Users List <
> > > users@maven.apache.org>; i...@soebes.de
> > > Subject: Re: [EXTERNAL] RE: Continuous Delivery with Maven now
> possible?
> > >
> > > External Sender: Use caution with links/attachments.
> > >
> > >
> > >
> > > Hi,
> > >
> > > On 04/05/17 22:52, Justin Georgeson wrote:
> > > > Also I believe the partial reactor switches don't work for Tycho
> > builds.
> > >
> > > You mean -pl ..option I suppose?
> > >
> > > As far as I know Tycho is handling that at the wrong time of the maven
> > > build and furthermore handles in this relationship some other things
> > wrong
> > > which results in not working things like this..
> > >
> > > Kind regards
> > > Karl Heinz Marbaise
> > >
> > > >
> > > > -Original Message-
> > > > From: Robert Patrick [mailto:robert.patr...@oracle.com]
> > > > Sent: Thursday, May 4, 2017 3:18 PM
> > > > To: Maven Users List ; i...@soebes.de
> > > > Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?
> > > >
> > > > External Sender: Use caution with links/attachments.
> > > >
> > > >
> > > >
> > > > Hard to train developers to break old habits but thanks... :-)
> > > >
> > > >
> > > >
> > > > -Original Message-
> > > > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> > > > Sent: Thursday, May 04, 2017 3:16 PM
> > > > To: Robert Patrick; Maven Users List; i...@soebes.de
> > > > Subject: Re: Continuous Delivery with Maven now possible?
> > > >
> > > > Hi Robert,
> > > >
> > > > Ah now I see the issue.
> > > >
> > > > If you have a multi module build you should use
> > > >
> > > > mvn -pl moduleToBuild clean install
> > > >
> > > > but from root location and don't change into the module directory
> cause
> > > this can't work like this.
> > > >
> > > > Kind regards
> > > > Karl Heinz Marbaise
> > > >
> > > > On 04/05/17 22:08, Robert Patrick wrote:
> > > >> Hi Karl,
> > > >>
> > > >> If I define the revision property in the top-level POM, I cannot
> refer
> > > to it in the module POMs'  elements *and* still retain the
> > ability
> > > to build

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

5 matches

Site Navigation

Mail list logo

Footer information