In implementing a continuous deployment pipeline I would like to update my
configuration tool with the specific SNAPSHOT version produced during the
'deploy' phase of the build.
Ideally, I'd like to set an environment variable so that in Jenkins I can
use it to trigger the downstream build.
I should clarify that I want to find the specific SNAPSHOT version assigned
by Nexus (or other maven repository manager applications) after the deploy.
So after I deploy 'myapp.jar' to Nexus with GAV:
groupID: mycompany.com
artifactID: myapp
version: 1.0-SNAPSHOT
Nexus assigns it to something
It is hard to understand your example.
Can you define child and grandchild and clarify where the
dependencies are coming from (Third parties? Other children?)
In general, you use the parent to define properties and define the exact
versions of dependencies in a dependency management section.
Not possible at this moment, I ended up to download the maven-metadata.xml
and extract the info after deploy.
However, I do believe this is a good enhancement for maven-deploy-plugin,
please file enhancement request for it
-Dan
On Fri, Aug 21, 2015 at 8:08 AM, Jeff predato...@gmail.com wrote:
Hello Jeff
I also wanted to do something similar a while ago. But in my attempt in
a multi-modules project, each modules got a slightly different
timestamp. Building from the root of a project having modules A, B and C
gave me the following timestamps:
A: 20150702.165421-17
B:
Hi Jeff,
Jeff wrote:
I should clarify that I want to find the specific SNAPSHOT version
assigned by Nexus (or other maven repository manager applications) after
the deploy.
So after I deploy 'myapp.jar' to Nexus with GAV:
groupID: mycompany.com
artifactID: myapp
version: 1.0-SNAPSHOT
That could be a backup option but I'd definitely prefer to have it done as
part of the same build step. Thanks for the suggestion.
On Fri, Aug 21, 2015 at 11:15 AM, Jörg Schaible
joerg.schai...@swisspost.com wrote:
Hi Jeff,
Jeff wrote:
I should clarify that I want to find the specific
Hello,
Any best practices on how to arrange dependency in multi module maven
project.
Let me give an example
Parent Project
Child1
GrandChild1 ( Depedency1, Dependency2, Dependency3)
GrandChild2 ( Depedency1, Dependency2, Dependency, 4)