[JBoss JIRA] (ARQ-2019) Upgrade Karaf to 4.0.4
by Steve Storck (JIRA)
Steve Storck created ARQ-2019:
---------------------------------
Summary: Upgrade Karaf to 4.0.4
Key: ARQ-2019
URL: https://issues.jboss.org/browse/ARQ-2019
Project: Arquillian
Issue Type: Sub-task
Components: OSGi Containers
Affects Versions: osgi_2.1.0.Final
Reporter: Steve Storck
Assignee: Thomas Diesler
Upgrade Karaf to 4.0.4 for managed and remote. Update execution environment accordingly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2016) arquillian-osgi-bundle includes dependencies but does not export them
by Steve Storck (JIRA)
[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ]
Steve Storck commented on ARQ-2016:
-----------------------------------
When I get the container and bundle configurations sufficient to ensure the use of custom test runners, I will want to be able to test it with the latest version of Karaf.
> arquillian-osgi-bundle includes dependencies but does not export them
> ---------------------------------------------------------------------
>
> Key: ARQ-2016
> URL: https://issues.jboss.org/browse/ARQ-2016
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Environment: Under Linux, and inside Karaf 4.x
> Reporter: Steve Storck
>
> When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows:
> {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid}
> package org.jboss.arquillian.spock;
> public class ArquillianSputnik extends Sputnik {
> import org.jboss.arquillian.test.spi.TestRunnerAdaptor;
> import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder;
> // Methods and fields omitted for brevity, but you can see that the
> // proper packages are imported
> public void run(RunNotifier notifier) {
> // Code omitted for brevity
> final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build();
> // More code omitted for brevity
> }
> }
> {code}
> {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> public class TestRunnerAdaptorBuilder {
> private static final String DEFAULT_EXTENSION_CLASS =
> "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader";
> private static final String TEST_RUNNER_IMPL_CLASS =
> "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor";
> public static TestRunnerAdaptor build() {
> // omitted lines for brevity
> ManagerBuilder builder = ManagerBuilder.from()
> .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS));
> return SecurityActions.newInstance(
> TEST_RUNNER_IMPL_CLASS,
> new Class<?>[] {ManagerBuilder.class},
> new Object[] {builder},
> TestRunnerAdaptor.class);
> }
> }
> {code}
> {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> final class SecurityActions {
> static <T> T newInstance(final String className,
> final Class<?>[] argumentTypes,
> final Object[] arguments,
> final Class<T> expectedType) {
> @SuppressWarnings("unchecked")
> Class<T> implClass = (Class<T>) loadClass(className);
> if (!expectedType.isAssignableFrom(implClass)) {
> throw new RuntimeException("Loaded class " +
> className +
> " is not of expected type " +
> expectedType);
> }
> return newInstance(implClass, argumentTypes, arguments);
> }
> }
> {code}
> I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own.
> Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2016) arquillian-osgi-bundle includes dependencies but does not export them
by Steve Storck (JIRA)
[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ]
Steve Storck edited comment on ARQ-2016 at 3/5/16 12:50 PM:
------------------------------------------------------------
When I get the container and bundle configurations sufficient to ensure the use of custom test runners, I will want to be able to test it with the latest version of Karaf. Added link to ARQ-2018
was (Author: stevestorck):
When I get the container and bundle configurations sufficient to ensure the use of custom test runners, I will want to be able to test it with the latest version of Karaf.
> arquillian-osgi-bundle includes dependencies but does not export them
> ---------------------------------------------------------------------
>
> Key: ARQ-2016
> URL: https://issues.jboss.org/browse/ARQ-2016
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Environment: Under Linux, and inside Karaf 4.x
> Reporter: Steve Storck
>
> When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows:
> {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid}
> package org.jboss.arquillian.spock;
> public class ArquillianSputnik extends Sputnik {
> import org.jboss.arquillian.test.spi.TestRunnerAdaptor;
> import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder;
> // Methods and fields omitted for brevity, but you can see that the
> // proper packages are imported
> public void run(RunNotifier notifier) {
> // Code omitted for brevity
> final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build();
> // More code omitted for brevity
> }
> }
> {code}
> {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> public class TestRunnerAdaptorBuilder {
> private static final String DEFAULT_EXTENSION_CLASS =
> "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader";
> private static final String TEST_RUNNER_IMPL_CLASS =
> "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor";
> public static TestRunnerAdaptor build() {
> // omitted lines for brevity
> ManagerBuilder builder = ManagerBuilder.from()
> .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS));
> return SecurityActions.newInstance(
> TEST_RUNNER_IMPL_CLASS,
> new Class<?>[] {ManagerBuilder.class},
> new Object[] {builder},
> TestRunnerAdaptor.class);
> }
> }
> {code}
> {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> final class SecurityActions {
> static <T> T newInstance(final String className,
> final Class<?>[] argumentTypes,
> final Object[] arguments,
> final Class<T> expectedType) {
> @SuppressWarnings("unchecked")
> Class<T> implClass = (Class<T>) loadClass(className);
> if (!expectedType.isAssignableFrom(implClass)) {
> throw new RuntimeException("Loaded class " +
> className +
> " is not of expected type " +
> expectedType);
> }
> return newInstance(implClass, argumentTypes, arguments);
> }
> }
> {code}
> I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own.
> Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2018) Upgrade Karaf to latest release for arquillian-container-karaf-managed
by Steve Storck (JIRA)
Steve Storck created ARQ-2018:
---------------------------------
Summary: Upgrade Karaf to latest release for arquillian-container-karaf-managed
Key: ARQ-2018
URL: https://issues.jboss.org/browse/ARQ-2018
Project: Arquillian
Issue Type: Enhancement
Components: OSGi Containers
Affects Versions: osgi_2.1.0.Final
Reporter: Steve Storck
Assignee: Thomas Diesler
The current version of the managed Karaf container is 2.3.3. This was released in 2013, so it is quite outdated. The latest release is 4.0.4, which was released in early 2016.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2016) arquillian-osgi-bundle includes dependencies but does not export them
by Steve Storck (JIRA)
[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ]
Steve Storck updated ARQ-2016:
------------------------------
Summary: arquillian-osgi-bundle includes dependencies but does not export them (was: Test extensions should be separate from OSGi Container extensions)
> arquillian-osgi-bundle includes dependencies but does not export them
> ---------------------------------------------------------------------
>
> Key: ARQ-2016
> URL: https://issues.jboss.org/browse/ARQ-2016
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Environment: Under Linux, and inside Karaf 4.x
> Reporter: Steve Storck
>
> When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows:
> {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid}
> package org.jboss.arquillian.spock;
> public class ArquillianSputnik extends Sputnik {
> import org.jboss.arquillian.test.spi.TestRunnerAdaptor;
> import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder;
> // Methods and fields omitted for brevity, but you can see that the
> // proper packages are imported
> public void run(RunNotifier notifier) {
> // Code omitted for brevity
> final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build();
> // More code omitted for brevity
> }
> }
> {code}
> {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> public class TestRunnerAdaptorBuilder {
> private static final String DEFAULT_EXTENSION_CLASS =
> "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader";
> private static final String TEST_RUNNER_IMPL_CLASS =
> "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor";
> public static TestRunnerAdaptor build() {
> // omitted lines for brevity
> ManagerBuilder builder = ManagerBuilder.from()
> .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS));
> return SecurityActions.newInstance(
> TEST_RUNNER_IMPL_CLASS,
> new Class<?>[] {ManagerBuilder.class},
> new Object[] {builder},
> TestRunnerAdaptor.class);
> }
> }
> {code}
> {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> final class SecurityActions {
> static <T> T newInstance(final String className,
> final Class<?>[] argumentTypes,
> final Object[] arguments,
> final Class<T> expectedType) {
> @SuppressWarnings("unchecked")
> Class<T> implClass = (Class<T>) loadClass(className);
> if (!expectedType.isAssignableFrom(implClass)) {
> throw new RuntimeException("Loaded class " +
> className +
> " is not of expected type " +
> expectedType);
> }
> return newInstance(implClass, argumentTypes, arguments);
> }
> }
> {code}
> I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own.
> Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2017) Export embedded libraries in arquillian-container-osgi :: osgi-bundle
by Steve Storck (JIRA)
[ https://issues.jboss.org/browse/ARQ-2017?page=com.atlassian.jira.plugin.s... ]
Steve Storck commented on ARQ-2017:
-----------------------------------
[~thomas.diesler] : I notice that the "org.jboss.arquillian.osgi" package is listed both under <Private-Package> and also under <_exportcontents>. I assume that you would prefer one or the other. Let me know which one is appropriate and I will remove the duplicate from the other element.
I am also curious why you have declined to inline the embedded dependencies, but to embed them as jars instead. There may be classloader improvements, among other things, if they are inlined instead. Are there licensing issues that require you to embed the jars? Otherwise, I would like to try inlining them instead. Please let me know. Thanks!
> Export embedded libraries in arquillian-container-osgi :: osgi-bundle
> ---------------------------------------------------------------------
>
> Key: ARQ-2017
> URL: https://issues.jboss.org/browse/ARQ-2017
> Project: Arquillian
> Issue Type: Sub-task
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Reporter: Steve Storck
> Assignee: Thomas Diesler
>
> So that test extensions other than the provided JUnit test extension can be used, more packages need to be exported for availability in the container for use by other extensions. This includes, but may not be limited to, the test SPI packages.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2016) Test extensions should be separate from OSGi Container extensions
by Steve Storck (JIRA)
[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ]
Steve Storck commented on ARQ-2016:
-----------------------------------
I don't see the "Assign to me" option in your JIRA. Is there a way that I can assign this story, and sub-tasks that I create, to myself?
> Test extensions should be separate from OSGi Container extensions
> -----------------------------------------------------------------
>
> Key: ARQ-2016
> URL: https://issues.jboss.org/browse/ARQ-2016
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Environment: Under Linux, and inside Karaf 4.x
> Reporter: Steve Storck
>
> When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows:
> {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid}
> package org.jboss.arquillian.spock;
> public class ArquillianSputnik extends Sputnik {
> import org.jboss.arquillian.test.spi.TestRunnerAdaptor;
> import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder;
> // Methods and fields omitted for brevity, but you can see that the
> // proper packages are imported
> public void run(RunNotifier notifier) {
> // Code omitted for brevity
> final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build();
> // More code omitted for brevity
> }
> }
> {code}
> {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> public class TestRunnerAdaptorBuilder {
> private static final String DEFAULT_EXTENSION_CLASS =
> "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader";
> private static final String TEST_RUNNER_IMPL_CLASS =
> "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor";
> public static TestRunnerAdaptor build() {
> // omitted lines for brevity
> ManagerBuilder builder = ManagerBuilder.from()
> .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS));
> return SecurityActions.newInstance(
> TEST_RUNNER_IMPL_CLASS,
> new Class<?>[] {ManagerBuilder.class},
> new Object[] {builder},
> TestRunnerAdaptor.class);
> }
> }
> {code}
> {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> final class SecurityActions {
> static <T> T newInstance(final String className,
> final Class<?>[] argumentTypes,
> final Object[] arguments,
> final Class<T> expectedType) {
> @SuppressWarnings("unchecked")
> Class<T> implClass = (Class<T>) loadClass(className);
> if (!expectedType.isAssignableFrom(implClass)) {
> throw new RuntimeException("Loaded class " +
> className +
> " is not of expected type " +
> expectedType);
> }
> return newInstance(implClass, argumentTypes, arguments);
> }
> }
> {code}
> I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own.
> Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2017) Export embedded libraries in arquillian-container-osgi :: osgi-bundle
by Steve Storck (JIRA)
Steve Storck created ARQ-2017:
---------------------------------
Summary: Export embedded libraries in arquillian-container-osgi :: osgi-bundle
Key: ARQ-2017
URL: https://issues.jboss.org/browse/ARQ-2017
Project: Arquillian
Issue Type: Sub-task
Components: OSGi Containers
Affects Versions: osgi_2.1.0.Final
Reporter: Steve Storck
Assignee: Thomas Diesler
So that test extensions other than the provided JUnit test extension can be used, more packages need to be exported for availability in the container for use by other extensions. This includes, but may not be limited to, the test SPI packages.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (ARQ-2016) Test extensions should be separate from OSGi Container extensions
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on ARQ-2016:
-------------------------------------
Perhaps you'd like to provide a PR for this
> Test extensions should be separate from OSGi Container extensions
> -----------------------------------------------------------------
>
> Key: ARQ-2016
> URL: https://issues.jboss.org/browse/ARQ-2016
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Affects Versions: osgi_2.1.0.Final
> Environment: Under Linux, and inside Karaf 4.x
> Reporter: Steve Storck
> Assignee: Thomas Diesler
>
> When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows:
> {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid}
> package org.jboss.arquillian.spock;
> public class ArquillianSputnik extends Sputnik {
> import org.jboss.arquillian.test.spi.TestRunnerAdaptor;
> import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder;
> // Methods and fields omitted for brevity, but you can see that the
> // proper packages are imported
> public void run(RunNotifier notifier) {
> // Code omitted for brevity
> final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build();
> // More code omitted for brevity
> }
> }
> {code}
> {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> public class TestRunnerAdaptorBuilder {
> private static final String DEFAULT_EXTENSION_CLASS =
> "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader";
> private static final String TEST_RUNNER_IMPL_CLASS =
> "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor";
> public static TestRunnerAdaptor build() {
> // omitted lines for brevity
> ManagerBuilder builder = ManagerBuilder.from()
> .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS));
> return SecurityActions.newInstance(
> TEST_RUNNER_IMPL_CLASS,
> new Class<?>[] {ManagerBuilder.class},
> new Object[] {builder},
> TestRunnerAdaptor.class);
> }
> }
> {code}
> {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid}
> package org.jboss.arquillian.test.spi;
> final class SecurityActions {
> static <T> T newInstance(final String className,
> final Class<?>[] argumentTypes,
> final Object[] arguments,
> final Class<T> expectedType) {
> @SuppressWarnings("unchecked")
> Class<T> implClass = (Class<T>) loadClass(className);
> if (!expectedType.isAssignableFrom(implClass)) {
> throw new RuntimeException("Loaded class " +
> className +
> " is not of expected type " +
> expectedType);
> }
> return newInstance(implClass, argumentTypes, arguments);
> }
> }
> {code}
> I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own.
> Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months