[
https://issues.jboss.org/browse/ARQ-796?page=com.atlassian.jira.plugin.sy...
]
Vineet Reynolds edited comment on ARQ-796 at 11/17/12 1:00 PM:
---------------------------------------------------------------
Deleted the {{GlassFishRestDeploymentAppender}}.
Aslak, I've not deleted the older SPI file referenced in the comment - the
{{glassfish-embedded-3}} artifact is no longer built, since it is not registered as a
Maven module in the project. Would it be wise to delete the {{glassfish-embedded-3}} and
{{glassfish-remote-3}} directories, seeing that they're not built anymore ? I think we
should test the current adapter against GF 3.0 (we test against 3.1 currently) and then
proceed to delete the older unused ones.
NB - The modules built in CI currently are {{glassfish-managed-3.1}},
{{glassfish-remote-3.1}}, {{glassfish-embedded-3.1}} and {{glassfish-common}}.
was (Author: vineet.reynolds):
Deleted the {{GlassFishRestDeploymentAppender}}.
Aslak, I've not deleted the older SPI file referenced in the comment - the
{{glassfish-embedded-3}} artifact is no longer built, since it is not registered as a
Maven module in the project. Would it be wise to delete the {{glassfish-embedded-3}} and
{{glassfish-remote-3}} directories, seeing that they're not built anymore ? I think we
should test the current adapter against GF 3.0 (we test against 3.1 currently) and then
proceed to delete the older unused ones.
NB - The modules built in CI currently are {{glassfish-managed-3.1}},
{[glassfish-remote-3.1}}, {{glassfish-embedded-3.1}} and {{glassfish-common}}.
Remove the GlassFishRestDeploymentAppender from the GlassFish
container adapter
-------------------------------------------------------------------------------
Key: ARQ-796
URL:
https://issues.jboss.org/browse/ARQ-796
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Priority: Minor
The GlassFishRestDeploymentAppender does not appear to serve any purpose. Although it is
implemented as an auxiliary archive appender, it does not appear to be used to enhance the
deployment archive. It assumes the responsibility of enhancing the archive with
TestEnrichers, but this is already done by the TestEnricher extensions themselves.
--
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