Bug 161951 – new package: dev-java/excalibur-instrumentation

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Petteri Räty (RETIRED) 2007-01-13 21:48:47 UTC]

http://excalibur.apache.org/containerkit.html

The deptree thickens.

[Comment 1 Petteri Räty (RETIRED) 2007-01-13 22:21:38 UTC]

Now available in our overlay:
https://overlays.gentoo.org/svn/proj/java/migrated-java-experimental-overlay/dev-java/excalibur-instrument

I did not have the energy to write separate ebuilds for all the modules so I put them into this one ebuild. Could use flag the modules though if there is stuff that only needs a subset. If we eventually package a lot of the excalibur stuff this logic needs to be eclassed. Now it's just -pool and this so I don't think that is enough.

[Comment 2 Marat Radchenko 2007-04-27 07:44:15 UTC]

http://bugs.gentoo.org/show_bug.cgi?id=176204
syrro for duplication.

[Comment 3 Charles Nérot 2015-01-19 15:54:51 UTC]

Block jmeter bump for years now (https://bugs.gentoo.org/show_bug.cgi?id=158498).

Will this hit the main tree ?

[Comment 4 Miroslav Šulc 2015-01-19 17:13:09 UTC]

really not sure, the project has already been retired for four years, see http://excalibur.apache.org/containerkit.html

"2010/12/15 - Apache Excalibur has been retired."

on the other side jmeter seems to still depend on it. dropping the retired excalibur from jmeter by upstream would be probably the best solution from package maintainer point of view but i have no idea what are their intentions. anyway, probably should be escalated upstream to get rid of the unmaintained library.

[Comment 5 Patrice Clement 2015-02-28 01:53:10 UTC]

It's clear from the homepage Excalibur is dead and won't resurect from the grave.. so why do we bother keeping these bugs open for decades? I don't understand.

I fetched jmeter-2.12 and looked at the source code, excalibur seems mostly gone from jmeter:

patrice@lair ~/src/apache-jmeter-2.12/src $ grep -ir 'excalibur' *
jorphan/org/apache/commons/cli/avalon/AbstractParserControl.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/CLArgsParser.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/CLOption.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/CLOptionDescriptor.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/CLUtil.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/ParserControl.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/Token.java:// Renamed from org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/package.html:These classes were originally in the Avalon project in the package org.apache.avalon.excalibur.cli
jorphan/org/apache/commons/cli/avalon/package.html:* Demonstrates the excalibur command-line parsing utility.
jorphan/org/apache/commons/cli/avalon/package.html:        msg.append("Excalibur command-line arg parser demo").append(lSep);
jorphan/org/apache/jorphan/logging/LoggingManager.java:import org.apache.avalon.excalibur.logger.LogKitLoggerManager;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:import org.apache.avalon.excalibur.datasource.DataSourceComponent;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:import org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:    private transient ResourceLimitingJdbcDataSource excaliburSource;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:            if (excaliburSource != null) {
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:                excaliburSource.dispose();
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:            excaliburSource = null;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:                    excaliburSource = src;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:                    variables.putObject(poolName, new DataSourceComponentImpl(excaliburSource));
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:            el.excaliburSource = excaliburSource;

Only deps I'm witnessing are these:
jorphan/org/apache/jorphan/logging/LoggingManager.java:import org.apache.avalon.excalibur.logger.LogKitLoggerManager;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:import org.apache.avalon.excalibur.datasource.DataSourceComponent;
protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:import org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource;

[Comment 6 Patrice Clement 2015-02-28 02:15:48 UTC]

@Charles: the fact that JMeter depends on a dead project bugs the hell out of me. Further, it has been holding a bump back for years bug the hell out of me. We have to sort this out.

[Comment 7 Patrice Clement 2015-02-28 10:35:21 UTC]

See James's last comment in bug 158498. Since Excalibur is a dead project, if we need *some* Excalibur jars, we will bundle them in jmeter.