You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2007/02/19 21:47:05 UTC

[jira] Closed: (MUSE-193) One jar for all Muse artifacts

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

Dan Jemiolo closed MUSE-193.
----------------------------

       Resolution: Won't Fix
    Fix Version/s: 2.2.0

This was resolved here (see News and Decisions):

http://marc.theaimsgroup.com/?l=muse-dev&m=117191512916051&w=2

We will still need to add the jars to the maven repository for this release.


> One jar for all Muse artifacts
> ------------------------------
>
>                 Key: MUSE-193
>                 URL: https://issues.apache.org/jira/browse/MUSE-193
>             Project: Muse
>          Issue Type: Improvement
>          Components: Build - Maven, Dependencies, and Optimizations
>            Reporter: Srinath Perera
>         Assigned To: Dan Jemiolo
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Right now Muse depeandancies include number of jars. As most of the users would be use them together, it may be good idea to create a one jar that has all muse stuff - (Axis2 and OGSI specific code). There are two options
> 1. Put the all muse jar in to maven repsotory only 
> 2. Put all muse jar in the disitibution and keep seperate jars only at maven reposiotry. This way  having many jars is not the deafult option. However if users need seperate jars thay can get them from maven repository. 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org