Hi,
On 3/11/15 7:00 AM, Baptiste Mathus wrote:
[Don't talk tool loud about the Jenkins Maven Project Plugin, you're gonna
draw Stephen here ;-).]
IMO, this is not a Maven issue, it should be discussed on the jenkinsci
lists since as you say yourself in your last mail, this does only happen in
Jenkins not in CLI or in your IDE.
Beware that that Jenkins plugin runs Maven quite differently than on the
CLI, and thus can lead to unexpected issues (at least different ones).
Some people even argue that that plugin should indeed not be used because
of this notable difference.
Cheers
2015-03-11 0:48 GMT+01:00 Charles Chan <[email protected]>:
Thanks for the pointers, here are my reply.
On Tue, Mar 10, 2015 at 8:43 AM, Karl Heinz Marbaise wrote:
Hi,
Do you have other warnings in your build? About missing artifacts etc. ?
Other than this particular message. There are no other warnings in the
console log.
The class is part ofr maven-sources-plugin which is weird, cause a single
class can't be access if the plugin has been loaded...?
Not sure what to look for to answer this question.
Check the log output of your build ...in particular start a clean
build...remove the local repository from your jenkins build...and check
the
logging output carefully....usually this is caused by not correctly
downloaded or missing artifacts in corporate repository managers...
Tried:
1. Delete the Jenkins workspace (clean checkout)
2. Remove .m2 from Jenkins slave
3. Rebuild .... same warning
BTW: How is Maven called ? Which Maven version do you use?
Maven 3.0.5 is called by Jenkins via Maven project plugin (
https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin).
The configuration:
* Root POM: pom.xml
* Goals and options: source:jar
* Maven validation level: default
* Settings file: Use default maven settings
* Global settings file: Use default maven global settings
I also tried to add '--debug' to the MAVEN_OPTS, but it didn't show any
more details regarding the warning.
I also try to change validation level (default, minimal, 2.0, 3.0, 3.1,
strict) and they all show the same error.
I assume you are using a single local repository on your slave for all
your jenkins jobs? If so change the job configuration to use a
repository localy to the workspace of Jenkins...
Please check your log file very carefully..for warnings "[WARNING]..."
Note: We only see this problem when compiling on Jenkin. There are no
problem when building the project from NetBeans or command line.
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
