You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2015/02/10 09:48:37 UTC
[Bug 57555] New: Cannot use JMeter 2.12 as a maven dependency
https://issues.apache.org/bugzilla/show_bug.cgi?id=57555
Bug ID: 57555
Summary: Cannot use JMeter 2.12 as a maven dependency
Product: JMeter
Version: 2.12
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: pascal.schumacher@t-systems.com
I'm unable to use JMeter 2.12 as a maven dependency, e.g. of the
jmeter-maven-plugin.
This seems to be caused by the update of excalibur-datasource to 2.1 in JMeter
2.12 (JMeter 2.10 and 2.11 worked).
Excalibur-datasource 2.1 has a dependency on
d-haven-managed-pool:d-haven-managed-pool:1.0,but this dependency can not be
found in maven central (or any other maven repo I'm aware of).
I guess the dependency should really be d-haven-mpool:managed-pool:1.0.
Managed-pool in turn has a dependency on event:event:1.0 which is also not in a
maven repo. This should be d-haven-event:d-haven-event:1.0.3 or
d-haven-event:event:1.0.1.
I was able to get it to work by excluding
d-haven-managed-pool:d-haven-managed-pool and event:event and adding
d-haven-mpool:managed-pool manually:
<dependency>
<groupId>org.apache.jmeter</groupId>
<artifactId>ApacheJMeter</artifactId>
<version>2.12</version>
<exclusions>
<exclusion>
<groupId>d-haven-managed-pool</groupId>
<artifactId>d-haven-managed-pool</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>d-haven-mpool</groupId>
<artifactId>managed-pool</artifactId>
<version>1.0</version>
<exclusions>
<exclusion>
<groupId>event</groupId>
<artifactId>event</artifactId>
</exclusion>
</exclusions>
</dependency>
Obviously this is not caused by JMeter, but by excalibur-datasource. But as
excalibur has been retired a long time ago it would be great if this could be
fixed in JMeter, e.g. by using the workaround described above.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 57555] Cannot use JMeter 2.12 as a maven dependency
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=57555
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |p.mouawad@ubik-ingenierie.c
| |om
Resolution|--- |FIXED
--- Comment #3 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Date: Thu Feb 12 20:17:50 2015
New Revision: 1659390
URL: http://svn.apache.org/r1659390
Log:
Bug 57555 - Cannot use JMeter 2.12 as a maven dependency
Bugzilla Id: 57555
Modified:
jmeter/trunk/res/maven/ApacheJMeter_parent.pom
jmeter/trunk/xdocs/changes.xml
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 57555] Cannot use JMeter 2.12 as a maven dependency
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=57555
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Sebb <se...@apache.org> ---
Looks like we cannot revert to the previous version because of Bug 55977.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 57555] Cannot use JMeter 2.12 as a maven dependency
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=57555
--- Comment #4 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Thanks for your report, analysis and fix.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 57555] Cannot use JMeter 2.12 as a maven dependency
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=57555
--- Comment #2 from pascal.schumacher@t-systems.com ---
I did some further investigation and noticed that the non-existing
"d-haven-managed-pool:d-haven-managed-pool:1.0" dependency is a transitive
dependency of excalibur-fortress. The JMeter distribution does not include
excalibur-fortress. This means the bug can be fixed by excluding the
excalibur-fortress dependencies of excalibur-datasource in
/res/maven/ApacheJMeter_parent.pom
Just replace:
<dependency>
<groupId>excalibur-datasource</groupId>
<artifactId>excalibur-datasource</artifactId>
<version>${excalibur-datasource.version}</version>
</dependency>
with:
<dependency>
<groupId>excalibur-datasource</groupId>
<artifactId>excalibur-datasource</artifactId>
<version>${excalibur-datasource.version}</version>
<exclusions>
<exclusion>
<groupId>excalibur-fortress</groupId>
<artifactId>excalibur-fortress-container-api</artifactId>
</exclusion>
<exclusion>
<groupId>excalibur-fortress</groupId>
<artifactId>excalibur-fortress-meta</artifactId>
</exclusion>
</exclusions>
</dependency>
--
You are receiving this mail because:
You are the assignee for the bug.