Maven dependencyManagement

[Anton Tanasenko]

Hi all,

It seems that maven project plugin does not link projects dependencies together when downstream project includes an upstream dependency whose version is specified

in dependencyManagement section. At least not with default clean installation of jenkins. Is there a way to enable that?

--

Regards,

Anton.

[Anton Tanasenko]

Ok, I think I got it, it picks up upstream managed depdendency only if it is directly referenced from 

downstream project (in dependencies section), which, I guess, is the right thing to do.

The problem arises when you have a single transitive dependency changed and you want it 

to be included in a webapp. In this case there is now direct dependency chain leading from webapp

to this dependency.

A good solution would require rebuilding all of the intermediate artifacts to ensure the stability of 

the whole build, but for some commonly used dependencies there might be hundreds of such artifacts.

Did anyone have any luck with such a setup in jenkins?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/s5w6R5SkIDU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Anton.

[Anton Tanasenko]

In previous message there should be '..there is NO direct dependency chain leading from webapp..'

--

Regards,

Anton.

[Anton Tanasenko]

Ok, to finish my own thread, we decided to generate a custom pom with transitive snapshot dependencies included directly in a separate profile.

This can be done for certain projects only (wars, etc.) in a pre-build step and the build itself would use that generated pom.

--

Regards,

Anton.