You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2010/10/13 19:06:32 UTC

[jira] Updated: (TUSCANY-3674) Review/consolidate 2.x distribution structure

     [ https://issues.apache.org/jira/browse/TUSCANY-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws updated TUSCANY-3674:
--------------------------------

    Fix Version/s: Java-SCA-2.0-Beta1

Move to Beta category

> Review/consolidate 2.x distribution structure
> ---------------------------------------------
>
>                 Key: TUSCANY-3674
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3674
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0-M5
>         Environment: All
>            Reporter: Simon Laws
>             Fix For: Java-SCA-2.0-Beta1
>
>
> We currently have a number of mechanisms for packaging distributed artifacts. Primarily:
> - Modules are grouped together into features (http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/features/)
> - Modules are grouped together into shaded jars (http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/shades/)
> It's not clear why these grouped functions have to be specified in different pom.xml files in different places in the code base. 
> Also the resulting 2.x distributions have both a features directory (from the features) and a lib director (containing jars from the shades directory) alongside the modules directory. This is at best confusing. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.