subject:"Jenkins builds"

Re: Jenkins builds

2017-05-19 Thread Karl Heinz Marbaise

Hi Greg,

On 19/05/17 23:55, Greg Parker wrote:

Thanks for the reply ,

>
Although having a separate .m2 folder is quite possible and would 
address my issue,

>  it’s something I’m trying to avoid for performance reasons.
> Pulling down all the external dependencies from Archiva,
> or central repository, for each project takes too long
>  and takes up too much space.

Archiva should proxy central repository and you should never directly 
pick dependencies from Maven Central only via a proxies repositores...

The time is an issue but only for the first time ...you can use updates 
in version control so it's not necessary to download the deps for each 
build (I don't know how long your builds take? We have build about max 
15 minutes release build and ci build takes 6 minutes)

Disk space ? Is that really a question? disk space is cheap...currently 
each of our builds takes 15 GiB of disk space for CI and our release 
build take 54 GiB...currently having 5 branches in parallel having some 
other builds as well..in total we are talking about approx 1.5 TiB...

It's important to check how long the downloads really take it might be a 
task to improve your infrastructure...

>
Our builds have a customer implementation
>  component which means we have many
>  builds for many customers.

what does "many " builds mean? 10, 100, 1000 ? different builds?

>
What I would like to have is a common .m2 folder for external dependencies,
> > and a build specific .m2 folder with just the build output.

In Maven only a single location for the cache exists..

Apart from that I really don't understand your concerns having your own 
artifacts separated from those others? They are separated by 
groupId/artifactId/version etc.

What kind of problem are you trying to solve?

Furthermore in the minute you are using a single cache part for several 
build all those builds are coupled via this cache...

Another thing is important here. This means you are coupling those 
builds to a particular build node if this cache does not exist your node 
can't run the build there...That's why the build cache in the workspace 
is the best option...

Kind regards
Karl Heinz Marbaise

Something like:

~/.m2/repository
/log4j
/commons-io
/…

$WORKSPACE1/.m2/repository
   /customer1-lib
   /build-lib
   /...

$WORKSPACE2/.m2/repository
   /customer2-lib
   /build-lib
  /...

That way I don’t have to pull down all the common stuff into a fresh .m2 for 
each build.

On May 19, 2017, at 5:36 PM, Karl Heinz Marbaise  wrote:

Hi Greg,

On 19/05/17 19:12, Greg Parker wrote:

I’m looking for a way to isolate builds from one another on our Jenkins server.
What I would like to do is have a common .m2 folder
for external dependencies.

For my own artifacts I’d like to install/retrieve
 them to/from a separate local repository.

I suspect that this capability does not exist, but I thought I would check.

The first thing what you need to understand is that the $HOME/.m2/repository is 
a cache location where the artifacts which are downloaded only cached to 
prevent repeated downloads from remote repositories..

The first step is to separate build jobs in Jenkins means that each job has 
it's own local cache directory which means having the local cache in the 
workspace ($WORKSPACE/.repository)...

The second step is having a repository manager (like Nexus, Artifactory or 
Archiva) which handles the separation between the artifacts which are created 
by your own and the ones you are consuming from outside (for example from Maven 
Central)..

There I would suggest to make this difference for your own artifacts and the artifacts 
which you call "external"...

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Jenkins builds

2017-05-19 Thread Greg Parker

Thanks for the reply ,

I understand the concept of the .m2 folder and generally how maven works.  We 
run an Archiva server where we cache dependencies and publish our released 
artifacts etc etc.  Although having a separate .m2 folder is quite possible and 
would address my issue, it’s something I’m trying to avoid for performance 
reasons.   Pulling down all the external dependencies from Archiva, or central 
repository, for each project takes too long and takes up too much space.  Our 
builds have a customer implementation component which means we have many builds 
for many customers.  What I would like to have is a common .m2 folder for 
external dependencies, and a build specific .m2 folder with just the build 
output.  Something like:

~/.m2/repository
/log4j
/commons-io
/…

$WORKSPACE1/.m2/repository
   /customer1-lib
   /build-lib
   /...

$WORKSPACE2/.m2/repository
   /customer2-lib
   /build-lib
  /...

That way I don’t have to pull down all the common stuff into a fresh .m2 for 
each build.

> On May 19, 2017, at 5:36 PM, Karl Heinz Marbaise  wrote:
> 
> Hi Greg,
> 
> On 19/05/17 19:12, Greg Parker wrote:
>> I’m looking for a way to isolate builds from one another on our Jenkins 
>> server.
> > What I would like to do is have a common .m2 folder
> > for external dependencies.
> 
> > For my own artifacts I’d like to install/retrieve
> >  them to/from a separate local repository.
> 
> > I suspect that this capability does not exist, but I thought I would check.
> 
> The first thing what you need to understand is that the $HOME/.m2/repository 
> is a cache location where the artifacts which are downloaded only cached to 
> prevent repeated downloads from remote repositories..
> 
> The first step is to separate build jobs in Jenkins means that each job has 
> it's own local cache directory which means having the local cache in the 
> workspace ($WORKSPACE/.repository)...
> 
> The second step is having a repository manager (like Nexus, Artifactory or 
> Archiva) which handles the separation between the artifacts which are created 
> by your own and the ones you are consuming from outside (for example from 
> Maven Central)..
> 
> There I would suggest to make this difference for your own artifacts and the 
> artifacts which you call "external"...
> 
> 
> Kind regards
> Karl Heinz Marbaise
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Jenkins builds

2017-05-19 Thread Karl Heinz Marbaise

Hi Greg,

On 19/05/17 19:12, Greg Parker wrote:

I’m looking for a way to isolate builds from one another on our Jenkins server.

> What I would like to do is have a common .m2 folder
> for external dependencies.

> For my own artifacts I’d like to install/retrieve
>  them to/from a separate local repository.

> I suspect that this capability does not exist, but I thought I would 
check.

The first thing what you need to understand is that the 
$HOME/.m2/repository is a cache location where the artifacts which are 
downloaded only cached to prevent repeated downloads from remote 
repositories..

The first step is to separate build jobs in Jenkins means that each job 
has it's own local cache directory which means having the local cache in 
the workspace ($WORKSPACE/.repository)...

The second step is having a repository manager (like Nexus, Artifactory 
or Archiva) which handles the separation between the artifacts which are 
created by your own and the ones you are consuming from outside (for 
example from Maven Central)..

There I would suggest to make this difference for your own artifacts and 
the artifacts which you call "external"...

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Jenkins builds

2017-05-19 Thread Greg Parker

I’m looking for a way to isolate builds from one another on our Jenkins server. 
 What I would like to do is have a common .m2 folder for external dependencies. 
 For my own artifacts I’d like to install/retrieve them to/from a separate 
local repository.  I suspect that this capability does not exist, but I thought 
I would check.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-11-04 Thread Irfan Sayed

thanks. i am thinking of writing Jenkins plugin which reports the deltas of
maven dependencies between two builds
i searched , but did not find anyone
do you have any idea if such plugin exist OR how we can achieve this ?

regards,

On Tue, Nov 4, 2014 at 1:06 PM, domi d...@fortysix.ch wrote:

 Please be aware, changing the code of a released library (not SNAPSHOT) is
 not allowed and maven can not take any responsibility for any errors this
 will cause.
 Thats why nexus/artifactory do not allow to change the artifact of a
 released version once its uploaded.
 Only SNAPSHOT versions are allowed to be changed.
 Domi

 On 04.11.2014, at 08:10, Irfan Sayed irfu.sa...@gmail.com wrote:

  thanks.
  what i figured out is , nexus / artifactory will not download the
  dependency unless there is change in the version.
  if dependency x  refers version 1.1 , then maven will see if
  nexus/artifactory has this version along with local maben repo of build
  machine
  if it does both, maven will not download the dependency even if developer
  changes the code keeping the version same
 
  regards
 
 
  On Mon, Oct 20, 2014 at 5:55 AM, Bernd Eckenfels e...@zusammenkunft.net
 
  wrote:
 
  Hello,
 
  I was looking a bit deeper into making the dependency plugin to print
  out the resolved timestamps. I noticed there is already an option
  -DoutputAbsoluteArtifactFilename=true which would give me the path of
  the files in the local directory. This is all good for released
  versions, but it still points to the non-unique snapshot version files.
 
  I am not wondering, is there a way to configure the maven
  resolver/dependency management to actually not do that. When I look at
  the build output, it does download the meta data and a specific
  timestamped version:
 
  Downloaded: https://.../2.1-SNAPSHOT/maven-metadata.xml (2 KB at 0.6
  KB/sec)
  Downloaded:
  https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.pom (12
 KB
  at 22.1 KB/sec)
  Downloading:
  https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.jar
  Downloaded:
  https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.jar
  (423 KB at 209.7 KB/sec)
 
  But it still creates a copy of that version without timestamp.
 
  I can imagine this is not really the best situation, why does it not
  stick to the uniquely named file?
 
  BTW: whats the best API way to get the snapshot timestamp from a
  Artifact object after it was resolved? I tried getDownloadURL(), but it
  is null for the Artifacts which are present in the list of
 
 
 
 org.apache.maven.plugin.dependency.utils.DependencyStatusSets.buildArtifactListOutput(SetArtifact,
  boolean, boolean, boolean)
 
  Gruss
  Bernd
 
  Am Sun, 19 Oct 2014 19:11:50 +0200
  schrieb Bernd Eckenfels e...@zusammenkunft.net:
 
  Ah another thing, I always wished there is an option to archive the
  effective POM instead of the tear downed POM with the
  maven-archiver (addMavenDesciptor).
 
  Especially when the effective pom also contains the resolved snapshot
  timestamps (which it currently not does).
 
  Speaking of effective pom, you can create and archive it, then you
  have at least all expressions and profiles locked down.
 
  Gruss
  Bernd
 
  Am Sun, 19 Oct 2014 22:17:45 +0530
  schrieb Irfan Sayed irfu.sa...@gmail.com:
 
  thanks bernd.
  anyone has any other suggestions please?
 
  regards
 
 
  On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
  e...@zusammenkunft.net wrote:
 
  Hello,
 
  I dont have a good method for that (especially not if all
  dependencies arent fully version-specified. You can use and add
  dependencies:list as a target to the maven build, then the
  resolved list will be printed in the build log. This list can
  change depending on what is available at build time.
 
  Gruss
  Bernd
 
   Am Sun, 19 Oct 2014 20:57:29 +0530
  schrieb Irfan Sayed irfu.sa...@gmail.com:
 
  hello,
 
  we have java project and using maven to build the same. we are
  using Jenkins. in Jenkins ,  we can generate the delta of source
  code changes between two builds.
  in the same way, do we have any way wherein , we can generate
  the delta of maven dependencies changed between two builds.
 
  please suggest
 
  regards
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-11-03 Thread Irfan Sayed

thanks.
what i figured out is , nexus / artifactory will not download the
dependency unless there is change in the version.
if dependency x refers version 1.1 , then maven will see if
nexus/artifactory has this version along with local maben repo of build
machine
if it does both, maven will not download the dependency even if developer
changes the code keeping the version same

regards

On Mon, Oct 20, 2014 at 5:55 AM, Bernd Eckenfels e...@zusammenkunft.net
wrote:

Hello,

I was looking a bit deeper into making the dependency plugin to print
out the resolved timestamps. I noticed there is already an option
-DoutputAbsoluteArtifactFilename=true which would give me the path of
the files in the local directory. This is all good for released
versions, but it still points to the non-unique snapshot version files.

I am not wondering, is there a way to configure the maven
resolver/dependency management to actually not do that. When I look at
the build output, it does download the meta data and a specific
timestamped version:

Downloaded: https://.../2.1-SNAPSHOT/maven-metadata.xml (2 KB at 0.6
KB/sec)
Downloaded:
https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.pom (12 KB
at 22.1 KB/sec)
Downloading:
https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.jar
Downloaded:
https://.../2.1-SNAPSHOT/commons-vfs2-2.1-20141016.153538-385.jar
(423 KB at 209.7 KB/sec)

But it still creates a copy of that version without timestamp.

I can imagine this is not really the best situation, why does it not
stick to the uniquely named file?

BTW: whats the best API way to get the snapshot timestamp from a
Artifact object after it was resolved? I tried getDownloadURL(), but it
is null for the Artifacts which are present in the list of

org.apache.maven.plugin.dependency.utils.DependencyStatusSets.buildArtifactListOutput(SetArtifact,
boolean, boolean, boolean)

Gruss
Bernd

Am Sun, 19 Oct 2014 19:11:50 +0200
schrieb Bernd Eckenfels e...@zusammenkunft.net:

Ah another thing, I always wished there is an option to archive the
effective POM instead of the tear downed POM with the
maven-archiver (addMavenDesciptor).

Especially when the effective pom also contains the resolved snapshot
timestamps (which it currently not does).

Speaking of effective pom, you can create and archive it, then you
have at least all expressions and profiles locked down.

Gruss
Bernd

Am Sun, 19 Oct 2014 22:17:45 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

thanks bernd.
anyone has any other suggestions please?

regards

On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
e...@zusammenkunft.net wrote:

Hello,

I dont have a good method for that (especially not if all
dependencies arent fully version-specified. You can use and add
dependencies:list as a target to the maven build, then the
resolved list will be printed in the build log. This list can
change depending on what is available at build time.

Gruss
Bernd

Am Sun, 19 Oct 2014 20:57:29 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

hello,

we have java project and using maven to build the same. we are
using Jenkins. in Jenkins , we can generate the delta of source
code changes between two builds.
in the same way, do we have any way wherein , we can generate
the delta of maven dependencies changed between two builds.

please suggest

regards

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-11-03 Thread domi

Please be aware, changing the code of a released library (not SNAPSHOT) is not
allowed and maven can not take any responsibility for any errors this will
cause.
Thats why nexus/artifactory do not allow to change the artifact of a released
version once its uploaded.
Only SNAPSHOT versions are allowed to be changed.
Domi

On 04.11.2014, at 08:10, Irfan Sayed irfu.sa...@gmail.com wrote:

regards

On Mon, Oct 20, 2014 at 5:55 AM, Bernd Eckenfels e...@zusammenkunft.net
wrote:

Hello,

But it still creates a copy of that version without timestamp.

I can imagine this is not really the best situation, why does it not
stick to the uniquely named file?

BTW: whats the best API way to get the snapshot timestamp from a
Artifact object after it was resolved? I tried getDownloadURL(), but it
is null for the Artifacts which are present in the list of

org.apache.maven.plugin.dependency.utils.DependencyStatusSets.buildArtifactListOutput(SetArtifact,
boolean, boolean, boolean)

Gruss
Bernd

Am Sun, 19 Oct 2014 19:11:50 +0200
schrieb Bernd Eckenfels e...@zusammenkunft.net:

Ah another thing, I always wished there is an option to archive the
effective POM instead of the tear downed POM with the
maven-archiver (addMavenDesciptor).

Especially when the effective pom also contains the resolved snapshot
timestamps (which it currently not does).

Speaking of effective pom, you can create and archive it, then you
have at least all expressions and profiles locked down.

Gruss
Bernd

Am Sun, 19 Oct 2014 22:17:45 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

thanks bernd.
anyone has any other suggestions please?

regards

On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
e...@zusammenkunft.net wrote:

Hello,

Gruss
Bernd

Am Sun, 19 Oct 2014 20:57:29 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

hello,

please suggest

regards

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Irfan Sayed

hello,

we have java project and using maven to build the same. we are using
Jenkins. in Jenkins ,  we can generate the delta of source code changes
between two builds.
in the same way, do we have any way wherein , we can generate the delta of
maven dependencies changed between two builds.

please suggest

regards

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Bernd Eckenfels

Hello,

I dont have a good method for that (especially not if all dependencies
arent fully version-specified. You can use and add dependencies:list as
a target to the maven build, then the resolved list will be printed in
the build log. This list can change depending on what is available at
build time.

Gruss
Bernd

  Am Sun, 19 Oct 2014 20:57:29 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

 hello,
 
 we have java project and using maven to build the same. we are using
 Jenkins. in Jenkins ,  we can generate the delta of source code
 changes between two builds.
 in the same way, do we have any way wherein , we can generate the
 delta of maven dependencies changed between two builds.
 
 please suggest
 
 regards
 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Irfan Sayed

thanks bernd.
anyone has any other suggestions please?

regards


On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels e...@zusammenkunft.net
wrote:

 Hello,

 I dont have a good method for that (especially not if all dependencies
 arent fully version-specified. You can use and add dependencies:list as
 a target to the maven build, then the resolved list will be printed in
 the build log. This list can change depending on what is available at
 build time.

 Gruss
 Bernd

   Am Sun, 19 Oct 2014 20:57:29 +0530
 schrieb Irfan Sayed irfu.sa...@gmail.com:

  hello,
 
  we have java project and using maven to build the same. we are using
  Jenkins. in Jenkins ,  we can generate the delta of source code
  changes between two builds.
  in the same way, do we have any way wherein , we can generate the
  delta of maven dependencies changed between two builds.
 
  please suggest
 
  regards
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Bernd Eckenfels

Ah another thing, I always wished there is an option to archive the
effective POM instead of the tear downed POM with the
maven-archiver (addMavenDesciptor).

Especially when the effective pom also contains the resolved snapshot
timestamps (which it currently not does).

Speaking of effective pom, you can create and archive it, then you have
at least all expressions and profiles locked down.

Gruss
Bernd

Am Sun, 19 Oct 2014 22:17:45 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

 thanks bernd.
 anyone has any other suggestions please?
 
 regards
 
 
 On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
 e...@zusammenkunft.net wrote:
 
  Hello,
 
  I dont have a good method for that (especially not if all
  dependencies arent fully version-specified. You can use and add
  dependencies:list as a target to the maven build, then the resolved
  list will be printed in the build log. This list can change
  depending on what is available at build time.
 
  Gruss
  Bernd
 
Am Sun, 19 Oct 2014 20:57:29 +0530
  schrieb Irfan Sayed irfu.sa...@gmail.com:
 
   hello,
  
   we have java project and using maven to build the same. we are
   using Jenkins. in Jenkins ,  we can generate the delta of source
   code changes between two builds.
   in the same way, do we have any way wherein , we can generate the
   delta of maven dependencies changed between two builds.
  
   please suggest
  
   regards
  
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Irfan Sayed

thanks bernd.
can you please explain in detail . i am sorry but haven't got much
if u can give me steps then that wud be great

regards


On Sun, Oct 19, 2014 at 10:41 PM, Bernd Eckenfels e...@zusammenkunft.net
wrote:

 Ah another thing, I always wished there is an option to archive the
 effective POM instead of the tear downed POM with the
 maven-archiver (addMavenDesciptor).

 Especially when the effective pom also contains the resolved snapshot
 timestamps (which it currently not does).

 Speaking of effective pom, you can create and archive it, then you have
 at least all expressions and profiles locked down.

 Gruss
 Bernd

 Am Sun, 19 Oct 2014 22:17:45 +0530
 schrieb Irfan Sayed irfu.sa...@gmail.com:

  thanks bernd.
  anyone has any other suggestions please?
 
  regards
 
 
  On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
  e...@zusammenkunft.net wrote:
 
   Hello,
  
   I dont have a good method for that (especially not if all
   dependencies arent fully version-specified. You can use and add
   dependencies:list as a target to the maven build, then the resolved
   list will be printed in the build log. This list can change
   depending on what is available at build time.
  
   Gruss
   Bernd
  
 Am Sun, 19 Oct 2014 20:57:29 +0530
   schrieb Irfan Sayed irfu.sa...@gmail.com:
  
hello,
   
we have java project and using maven to build the same. we are
using Jenkins. in Jenkins ,  we can generate the delta of source
code changes between two builds.
in the same way, do we have any way wherein , we can generate the
delta of maven dependencies changed between two builds.
   
please suggest
   
regards
   
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Ben Podgursky

With regards to Jenkins, it's not exactly what you're asking  about, but if
you have your project set up as a Maven build and configure builds trigger
downstream builds, it will tell you the difference between the last
upstream build version and the current one, ex you'll get something like

No changes. Changes in dependency

upstream_project Success#1208 →  Success#1209 (detail) 

in your view of the build.  Which made it really easy for us to track what
changes got picked up in a build.

Re: snapshot versions, we got annoyed as well that it was very difficult to
tell what snapshot version a build used just looking at maven output, so we
wrote a small plugin to a least log it for debugging.  General idea / code
here:
http://blog.liveramp.com/2014/09/29/identifying-maven-snapshot-artifacts-by-git-revision/
to plug my own blog post.


Ben


On Sun, Oct 19, 2014 at 10:20 AM, Irfan Sayed irfu.sa...@gmail.com wrote:

 thanks bernd.
 can you please explain in detail . i am sorry but haven't got much
 if u can give me steps then that wud be great

 regards


 On Sun, Oct 19, 2014 at 10:41 PM, Bernd Eckenfels e...@zusammenkunft.net
 wrote:

  Ah another thing, I always wished there is an option to archive the
  effective POM instead of the tear downed POM with the
  maven-archiver (addMavenDesciptor).
 
  Especially when the effective pom also contains the resolved snapshot
  timestamps (which it currently not does).
 
  Speaking of effective pom, you can create and archive it, then you have
  at least all expressions and profiles locked down.
 
  Gruss
  Bernd
 
  Am Sun, 19 Oct 2014 22:17:45 +0530
  schrieb Irfan Sayed irfu.sa...@gmail.com:
 
   thanks bernd.
   anyone has any other suggestions please?
  
   regards
  
  
   On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
   e...@zusammenkunft.net wrote:
  
Hello,
   
I dont have a good method for that (especially not if all
dependencies arent fully version-specified. You can use and add
dependencies:list as a target to the maven build, then the resolved
list will be printed in the build log. This list can change
depending on what is available at build time.
   
Gruss
Bernd
   
  Am Sun, 19 Oct 2014 20:57:29 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:
   
 hello,

 we have java project and using maven to build the same. we are
 using Jenkins. in Jenkins ,  we can generate the delta of source
 code changes between two builds.
 in the same way, do we have any way wherein , we can generate the
 delta of maven dependencies changed between two builds.

 please suggest

 regards

   
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
   
   
  
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

Re: generate maven dependency difference between two Jenkins builds

2014-10-19 Thread Bernd Eckenfels

Hello,

But it still creates a copy of that version without timestamp.

I can imagine this is not really the best situation, why does it not
stick to the uniquely named file?

BTW: whats the best API way to get the snapshot timestamp from a
Artifact object after it was resolved? I tried getDownloadURL(), but it
is null for the Artifacts which are present in the list of

org.apache.maven.plugin.dependency.utils.DependencyStatusSets.buildArtifactListOutput(SetArtifact,
boolean, boolean, boolean)

Gruss
Bernd

Am Sun, 19 Oct 2014 19:11:50 +0200
schrieb Bernd Eckenfels e...@zusammenkunft.net:

Ah another thing, I always wished there is an option to archive the
effective POM instead of the tear downed POM with the
maven-archiver (addMavenDesciptor).

Especially when the effective pom also contains the resolved snapshot
timestamps (which it currently not does).

Speaking of effective pom, you can create and archive it, then you
have at least all expressions and profiles locked down.

Gruss
Bernd

Am Sun, 19 Oct 2014 22:17:45 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

thanks bernd.
anyone has any other suggestions please?

regards

On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels
e...@zusammenkunft.net wrote:

Hello,

Gruss
Bernd

Am Sun, 19 Oct 2014 20:57:29 +0530
schrieb Irfan Sayed irfu.sa...@gmail.com:

hello,

please suggest

regards

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Jenkins builds

Re: Jenkins builds

Re: Jenkins builds

Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

Re: generate maven dependency difference between two Jenkins builds

14 matches

Site Navigation

Mail list logo

Footer information