[
https://issues.jboss.org/browse/ARQ-898?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on ARQ-898:
-------------------------------
Aha, now I see where the disconnect in my logic is. I suspected that the name attribute on
the @Deployment annotation determined the middle segment (the deployment name), but I
didn't realize that the first segment came from the @TargetsContainer annotation (the
target name).
I had thought that the target name came from the qualifier in arquillian.xml.
If there is no @TargetsContainer annotation, is it possible to use the qualifier of the
active configuration, if any? Or are these orthogonal things?
Improve the readability of the name of the archive file exported by
the ArchiveDeploymentExporter
-------------------------------------------------------------------------------------------------
Key: ARQ-898
URL:
https://issues.jboss.org/browse/ARQ-898
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.0.Final
Reporter: Dan Allen
Priority: Minor
The archive file that is exported by the ArchiveDeploymentExporter is very oddly named
under typical circumstances.
_DEFAULT___DEFAULT__test.war
We need to find some way to make this more friendly to the developer. For one, we could
use hyphens to separate the segments so that they don't stack:
_DEFAULT_-_DEFAULT_-test.war
Another option is to strip the underscores if the name is _DEFAULT_:
DEFAULT-DEFAULT-test.war
That at least looks presentable.
We should also document somewhere when the _DEFAULT_ name gets replaced with a custom one
(I can't figure it out).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira