Hello,
I wonder if there is any easy way to do the equivalent of Velocity quiet
references with Maven poms ... ?
Here is my use-case (in a corporate pom):
- I set a property label containing some versions and reference to
${buildNumber}
- This property ${buildNumber} is optionally set by the
Just define the default value in the properties section of the parent
pom...
On 24 September 2014 10:34, JeremieB. jeremie.bousq...@gemalto.com wrote:
Hello,
I wonder if there is any easy way to do the equivalent of Velocity quiet
references with Maven poms ... ?
Here is my use-case (in a
On 23 September 2014 18:37, Curtis Rueden ctrue...@wisc.edu wrote:
Hi James,
I can no longer see Deploy artifacts to Maven repository
as a post-build action.
Just add a build step that does mvn deploy or similar.
See this for me is a post-build action. I guess Jenkins doesn't see it
I've got a project where (a) we went to a lot of trouble to make sure
that log4j was scoped to test, (b) dependency:list shows it as
scope=test, (c) dependency:tree shows it as scope=compile, using the
most recent dependency plugin and maven 3.0.5.
The path to log4j is through slf4j-log4j, which
Hi,
We have project that use ant script and build ear. I have created pom
and setting.xml to deploy at nexus snapshot repository. It's working, but it
deploy/copy only META-INF folder to nexus repo. It doesn't deploy/copy war
folder. The ear is 18 MB, but in nexus snapshot repo has 2.2 kb.
I have always understood this to mean it is the scope relative to the
parent. So if the parent is in test scope its compile dependecies are only
dragged into your dependencies of the test scope. So basically the list is
resolving that, the tree gives you the full picture to resolve yourself
