[
https://issues.jboss.org/browse/FORGE-1790?page=com.atlassian.jira.plugin...
]
George Gastaldi closed FORGE-1790.
----------------------------------
Resolution: Won't Fix
The annotations placed on top of @Deployment are the addons to be deployed. The
AddonDependencies set when creating a ForgeArchive are the addons that the current addon
depends on.
We find this useful for testing, and if subclassing is required, one solution is to move
the @Deployment method to the concrete class.
Best Regards,
George
Make adding addon deps easier in getDeployment().
-------------------------------------------------
Key: FORGE-1790
URL:
https://issues.jboss.org/browse/FORGE-1790
Project: Forge
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Ondrej Zizka
Currently, the deps need to be stated twice - once in annotations, and then in
getDeployment(). If getDeployment() wasn't static, one could get that using
reflection. But Arquillian needs getDeployment static.
This also limits usage of subclassing, because subclass can't add dependencies to
it's parent.
Would be nice to come up with some solution to this.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)