[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tuscany-dev
Subject:    [jira] Updated: (TUSCANY-3674) Review/consolidate 2.x distribution
From:       "Simon Laws (JIRA)" <dev () tuscany ! apache ! org>
Date:       2010-10-29 14:42:20
Message-ID: 2632325.142631288363340735.JavaMail.jira () thor
[Download RAW message or body]


     [ 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:     (was: Java-SCA-2.0-Beta1)
                   Java-SCA-2.x

We've done enough of this for the beta but keeping it open on 2.x for any further \
actions

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


[prev in list] [next in list] [prev in thread] [next in thread]