[JIRA] [extended-choice-parameter-plugin] (JENKINS-29982) jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur
Title: Message Title alexis oliot created an issue Jenkins / JENKINS-29982 jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur Issue Type: Bug Assignee: vimil Components: extended-choice-parameter-plugin Created: 17/Aug/15 2:37 PM Environment: Jenkins 1.609 Labels: jenkins plugin url parameter Priority: Major Reporter: alexis oliot Hello, I have a Jenkins' job in which one of the parameters is an 'Extended Choice Parameter' (https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin) which is submitted as a selection of comma separated values when invoking the build from the build webpage. However, I also need to invoke the build using wget + URL. I saw someone encountered this issue too (https://issues.jenkins-ci.org/browse/JENKINS-16639), and it's marked as resolved but the problem still happen whereas I updated the Extended Choice Plugin to the 0.52 version on my Jen
[JIRA] [extended-choice-parameter-plugin] (JENKINS-29982) jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur
Title: Message Title alexis oliot commented on JENKINS-29982 Re: jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur In fact after somes researches we find out that it's our SOAPUI servicer which has a bug while sendind multiparameters trhough an URL ! So i'll closed this post Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-29982) jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur
Title: Message Title alexis oliot closed an issue as Not A Defect Jenkins / JENKINS-29982 jenkins: pass multiple “Extended Choice Parameter” values using a URL problem still occur Change By: alexis oliot Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-29166) Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository
Title: Message Title alexis oliot created an issue Jenkins / JENKINS-29166 Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository Issue Type: Bug Assignee: Unassigned Components: repository-connector-plugin Created: 01/Jul/15 1:05 PM Environment: Jenkins 1.596, Nexus 2.11.0-2, maven 3.2.5 Labels: plugin jenkins maven nexus Priority: Major Reporter: alexis oliot I'm using this plugin to choose some artifacts versions which are stored on Maven repository. The problem is that the list provided by the Maven Artifact Resolver parameter doesn't get refreshed whereas new versions of my artfiacts are stored on Maven Repository. Is there a way to refresh this list automatically ? Like settings a timer or something else ?
[JIRA] [repository-connector-plugin] (JENKINS-29166) Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository
Title: Message Title alexis oliot assigned an issue to Michael Rumpf Jenkins / JENKINS-29166 Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository Change By: alexis oliot Assignee: Michael Rumpf Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven-release-plugin issue
alexis olior created JENKINS-27009 Default versioning mode maven-release-plugin issue Issue Type: Bug Assignee: Peter Hayes Attachments: Problème default versioning mode maven release plugin JENKINS 1.jpg Components: release-plugin Created: 18/Feb/15 2:33 PM Description: I encountered an issue that is obstructing my development on Jenkins. After installing the maven-release-plugin on Jenkins I've tested it. The fact is that for a project without any dependencies, the plugin works well. But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save the configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !! Does exist any tips to get around this problem ? an other way to do ? or a fix of the maven-release-plugin ? Thanks for the help Jenkins 1.596 maven-release-plugin 0.14 Environment: Jenkins 1.596 maven release plugin 0.14 Project: Jenkins Labels: jenkins release-plugin default mode versioning Priority: Blocker Reporter: alexis olior This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven-release-plugin issue
alexis olior updated JENKINS-27009 Default versioning mode maven-release-plugin issue Change By: alexis olior (18/Feb/15 2:38 PM) Description: I encountered an issue that is obstructing my development on Jenkins. After installing the maven-release-plugin on Jenkins I've tested it. The fact is that for a project without any dependencies, the plugin works well. But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save the he configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !! Does exist any tips to get around this problem ? an other way to do ? or a fix of the maven-release-plugin ? Thanks for the help Jenkins 1.596 maven-release-plugin 0.14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (18/Feb/15 2:51 PM) Summary: Default versioning mode maven - release - plugin issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot assigned JENKINS-27009 to alexis oliot Default versioning mode maven release plugin issue Change By: alexis oliot (18/Feb/15 2:53 PM) Assignee: Peter Hayes alexis oliot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-15298) Default versioning mode is not getting picked while invoking the maven release build
alexis oliot assigned JENKINS-15298 to alexis oliot Default versioning mode is not getting picked while invoking the maven release build Change By: alexis oliot (18/Feb/15 2:52 PM) Assignee: James Nord alexis oliot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (19/Feb/15 9:11 AM) Description: I need some help about the maven release plugin !FIRSTI encountered an issue that is obstructing my development on Jenkins. After installing the maven-release-plugin on Jenkins I've tested it. The fact is that for a project without any dependencies, the plugin works well. But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save he configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !! Does exist any tips SECONDLYFinally to get around solve this problem ? an other way I downgraded the maven release plugin to do ? or the 0.7.1 version and now I can select the default versioning mode :D.But the second issue I faced is that I want to release a job which depends on other one. fix Project B -> Project A depends onThe fact is I released the Project A in a 0.0.X version. Now I would like to use/implement this Project A release during the release of the Project B because I don't want any SNAPSHOT dependencies in my released projects !!I also tried using versions- maven- release- plugin ? but the use of both those plugin seems not to work... Thanks for Anyone encountered this problem yet ? is there a solution to it ? I join a picture showing the help result I expect Jenkins JENKINS 1.596 & maven-release-plugin 0. 14 7.1 Attachment: Capture.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (19/Feb/15 9:17 AM) Description: I need some help about the maven release plugin !FIRSTI encountered an issue that is obstructing my development on Jenkins.After installing the maven-release-plugin on Jenkins I've tested it.The fact is that for a project without any dependencies, the plugin works well.But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save he configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !!SECONDLYFinally to solve this problem I downgraded the maven release plugin to the 0.7.1 version and now I can select the default versioning mode :D.But the second issue I faced is that I want to release a job which depends on other one.Project B -> Project A depends onThe fact is I released the Project A in a 0.0.X version. Now I would like to use/implement this Project A release during the release of the Project B because I don't want any SNAPSHOT dependencies in my released projects !!I also tried using versions-maven-plugin but the use of both those plugin seems not to work... All I want to do is working while using the cmd !! Anyone encountered this problem yet ? is there a solution to it ? I join a picture showing the result I expectJENKINS 1.596 & maven-release-plugin 0.7.1 Attachment: Capture.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (19/Feb/15 9:30 AM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (19/Feb/15 12:02 PM) Description: I need some help about the maven release plugin !FIRSTI encountered an issue that is obstructing my development on Jenkins.After installing the maven-release-plugin on Jenkins I've tested it.The fact is that for a project without any dependencies, the plugin works well.But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save he configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !!SECONDLYFinally to solve this problem I downgraded the maven release plugin to the 0.7.1 version and now I can select the default versioning mode :D.But the second issue I faced is that I want to release a job which depends on other one.Project B -> Project A depends onThe fact is I released the Project A in a 0.0.X version. Now I would like to use/implement this Project A release during the release of the Project B because I don't want any SNAPSHOT dependencies in my released projects !!I also tried using versions-maven-plugin but the use of both those plugin seems not to work together ... Am I wrong ? All I want to do is working while using the cmd !!Anyone encountered this problem yet ? is there a solution to it ? I join a picture showing the result I expectJENKINS 1.596 & maven-release-plugin 0.7.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27031) Release & Versions Maven plugin
alexis oliot created JENKINS-27031 Release & Versions Maven plugin Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 19/Feb/15 3:44 PM Description: Hi, we have a problem with maven releases and maven version plugin. In Jenkins we want to do releases automatically upon pressing a button. To remove snapshot dependencies we want to use the maven versions plugin. Suppose we have two projects A (latest release 0.0.1, latest snapshot 0.0.2-SNAPSHOT) and project B with a dependency on ProjectA - 0.0.2-SNAPSHOT and we want to release project B. How can we upgrade project Bs dependencies to the latest available release version? The maven versions plugin goal "use-releases" does not change the 0.0.2-SNAPSHOT dependency because there is no 0.0.2 release version of this project. So my question is: how can we automatically remove snapshot dependencies and replace them with the latest available release version in our scenario? Environment: JENKINS 1.596 Git Maven Project: Jenkins Labels: maven3 release-plugin version jenkins Priority: Major Reporter: alexis oliot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27073) Cascade release plugin Failed to parse POM
alexis oliot created JENKINS-27073 Cascade release plugin Failed to parse POM Issue Type: Bug Assignee: Peter Hayes Components: release-plugin Created: 23/Feb/15 9:42 AM Description: Hello, I'm trying to use the maven cascade release plugin. It might works well but I encountered an issue when running it !! ERROR: Failed to parse POMs java.io.IOException: java.lang.NoSuchFieldException: includedRegions at com.barchart.jenkins.cascade.PluginUtilities.changeField(PluginUtilities.java:105) at com.barchart.jenkins.cascade.LayoutLogic.processLayout(LayoutLogic.java:478) at com.barchart.jenkins.cascade.LayoutLogic.process(LayoutLogic.java:292) at com.barchart.jenkins.cascade.LayoutBuildWrapper$1.tearDown(LayoutBuildWrapper.java:222) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:862) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1676) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.NoSuchFieldException: includedRegions at java.lang.Class.getDeclaredField(Class.java:1938) at com.barchart.jenkins.cascade.PluginUtilities.changeField(PluginUtilities.java:98) ... 9 more And I don't know why !! Anyone ?!? Project: Jenkins Labels: release-plugin jenkins git cascade maven Priority: Major Reporter: alexis oliot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27679) Issue when parallelizing parametrized jobs from a multi-project jobs
alexis oliot created JENKINS-27679 Issue when parallelizing parametrized jobs from a multi-project jobs Issue Type: Bug Assignee: huybrechts Components: maven-plugin, parameterized-trigger-plugin Created: 31/Mar/15 8:56 AM Description: I'm trying to parallelize parametrized jobs from a Multi-Project one. The fact is that the configurations of the jobs are the same. When I build my MP jobs the error can occur on a sub-job which is not always the same, it's really hazardous There is no logic in it Did somenone encountered this error too ? ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:101) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:855) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) project=hudson.maven.MavenModuleSet@3b3f4f26[Aggregator_XXX_(VERSIONING)] project.getModules()=[hudson.maven.MavenModule@4d30311[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Admin-jar-1.5][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Admin-jar-1.5][relativePath:_poms\ept-pom-aggregator-Admin-jar-1.5], hudson.maven.MavenModule@60a3eba9[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Common-jar-1.5][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Common-jar-1.5][relativePath:_poms\ept-pom-aggregator-Common-jar-1.5], hudson.maven.MavenModule@2c1cebdb[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Common-jar-1.6][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-Common-jar-1.6][relativePath:_poms\ept-pom-aggregator-Common-jar-1.6], hudson.maven.MavenModule@44778b0[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-ear-was85][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-ear-was85][relativePath:_poms\ept-pom-aggregator-SOAApp-ear-was85], hudson.maven.MavenModule@23c708ab[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-jar-1.5][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-jar-1.5][relativePath:_poms\ept-pom-aggregator-SOAApp-jar-1.5], hudson.maven.MavenModule@2ddd0e72[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-jar-1.6][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-jar-1.6][relativePath:_poms\ept-pom-aggregator-SOAApp-jar-1.6], hudson.maven.MavenModule@80f97da[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-war-was85][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOAApp-war-was85][relativePath:_poms\ept-pom-aggregator-SOAApp-war-was85], hudson.maven.MavenModule@41ca0966[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-ear][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-ear][relativePath:_poms\ept-pom-aggregator-SOXX-ear], hudson.maven.MavenModule@5e5d8ea8[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-jar-1.5][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-jar-1.5][relativePath:_poms\ept-pom-aggregator-SOXX-jar-1.5], hudson.maven.MavenModule@222b72db[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-war][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-SOXX-war][relativePath:_poms\ept-pom-aggregator-SOXX-war], hudson.maven.MavenModule@76192577[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-WebServices-ear-was85][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-WebServices-ear-was85][relativePath:_poms\ept-pom-aggregator-WebServices-ear-was85], hudson.maven.MavenModule@37df5e23[Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-WebServices-jar-1.5][Aggregator_XXX_(VERSIONING)/lu.ept.pom:ept-pom-aggregator-WebServices-jar-1.5][relativePat
