[arquillian-issues] [JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules

[Karel Piwko (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karel Piwko reopened ARQ-1584:
------------------------------



As for depchains, this is not how it should be done. *arquillian-droidium-native* is still depchain, because user needs to specify <type>pom</type.

Now it is more confusing then previously. We should stick with following rule:

dependency of packaging jar -> no depchain in name
dependency of type pom -> always depchain in name

Depchain are generally used to make dependency specifications simpler - that is to couple a set of independent components together within a single dependency. My suggestion was, as is hardly a screnario when end user will depend on native-spi and native-api when *using* Droidium, it would make more sense to have:

native-impl renamed to arquillian-droidium-native, being of type jar and that would be what end user will import into their projects.
                
> Remove duplication from Droidium modules
> ----------------------------------------
>
>                 Key: ARQ-1584
>                 URL: https://issues.jboss.org/browse/ARQ-1584
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Droidium
>    Affects Versions: droidium_1.0.0.Alpha2
>            Reporter: Karel Piwko
>            Assignee: Stefan Miklosovic
>             Fix For: droidium_1.0.0.Alpha3
>
>
> Currently, a lot of modules are not necessary and could be removed altogether to make structure simpler
> For instance, build per each native, container, web might be moved into a single build module, some depchain could be removed - depchain make more sense if there is a sense in including only a part of extension, which is not valid for native, web - it's all-or-nothing.

--
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