Now, if surefile would stop failing with:
[ERROR] Failed to execute goal
(default-test) on project rosapi-front-end-anvils-transport: Execution
default-test of goal
For pipeline you want to use the mavenLocalRepo property of the withMaven
step in the
On 13 October 2016 at 16:41, Benson Margulies wrote:
> So, here's a specific puzzle. I want to enable multiple branches
When they work, they work... when they don't work they blow up in your
face... and they break how maven is supposed to work... so anyone that
actually has a good understanding of Maven will be surprised by the evil
things the evil one does...
Having been a Jenkins committer since 2006, and given
I wasn't attacking your opinion or your credentials. The lack of detailed
justification for statements simply made me question how applicable they were
to me (and others). As such, I wanted to provide another point of view.
Granted, the Maven jobs hide a lot of what they are doing so if
To make concurrent Jenkins builds work, simply enable the "Use private Maven
repository" option in the Jenkins Maven build jobs and select the appropriate
"Strategy" (e.g., "Local to the workspace" or "Local to the executor"). This
works fine for us...
Or fix the bug from, like, 2007 ?
On Thu, Oct 13, 2016 at 4:41 PM, Benson Margulies
> So, here's a specific puzzle. I want to enable multiple branches in
Well... Some of us, my team included, are using the Maven jobs in Jenkins and
they generally works fine for our projects (and is much simpler to configure).
Be warned that Maven 3.3 support is still busted for projects that use
.mvn/maven.config waiting on
So, here's a specific puzzle. I want to enable multiple branches in
the Jenkins job and concurrent builds. How do I avoid two jobs trying
to write the same local repo at the same time?
To unsubscribe, e-mail:
I’m not sure I fully follow what’s going on, however I’m not sure what you want
to do can be easily done in a single reactor build. It can possibly be done,
but you’d need break things into a lot of modules.
My first question is are you building features that are OS specific or
You could create your own safe-batik-bridge which is empty and has both
dependencies and then just ask everyone to use that instead...
Or deploy to your proxy of central a batik-bridge:1.8-yourcompany-1 and use
depMgmt to pin that version
On Thursday 13 October 2016, Curtis Rueden
I agree with Stephen .. avoid the Maven job type. In fact I would install
I have spent many hours trying to fix broken builds with the Maven job type
only to switch to Freestyle jobs and they just work. There is a reason why
I have a project  which depends on
org.apache.xmlgraphics:batik-bridge:1.8, which in turn requires
org.apache.xmlgraphics:xmlgraphics-commons:2.1 at runtime.
Unfortunately, the POM for batik-bridge somehow does not declare the
xmlgraphics-commons dependency , even though it
I am currently developing an eclipse RCP application and one of my features
includes a few platform specific plugins.
In other words some of those plugins have o/s flag equal to "win32" and some
Having this flag breaks my maven build because when building the feature on
Thanks Benson to put some coins in the troll machine :-)
Well if evil is really ease the user's life so this plugin can be
considered evil :-)
You have some very convenient features such building dependent projects,
So it's just a matter of not spending too long on configuring
➜ tests git:(master) ls -l
-rw-r--r-- 1 benson staff 5 Oct 13 20:47 port
-rw-r--r-- 1 benson staff 7 Oct 13 20:47 rosette-usage.yaml
-rw-r--r-- 1 benson staff 7 Oct 13 20:47
Are you sure you need xmldsig?
has been part of JDK since 1.6, and the OpenJDK includes the
You can also look at the Apache Santuario implementation which is
Excuse me, do you know the license of xmldsig-1.0.jar?
View this message in context:
Sent from the Maven - Users mailing list archive at Nabble.com.
if you are using artifactory then you can by using license-check. Its
available in commercial version.
On Wed, Oct 12, 2016 at 11:02 PM, Libby_li wrote:
> Excuse me, do you know the license of xmldsig-1.0.jar?
> View this message in context:
We've about had it with bamboo, and are dusting off our old Jenkins instance.
I recall some messages here about things _not_ to do with Jenkins and
Maven. Do we avoid the 'maven build type' altogether and just run
Maven from the shell, or is my memory faulty? Anything else.
is the message from your friendly neighbourhood Apache Maven PMC member and
1. (oldschool) Freestyle Job with a Maven build step
2. (coolkids) Multibranch Pipeline Job with a
+1 for pipeline build.
On Thu, Oct 13, 2016 at 10:15 AM, Stephen Connolly <
> is the message from your friendly neighbourhood Apache Maven PMC member and
Mail list logo