[jboss-jira] [JBoss JIRA] Commented: (JBAS-6320) Provide a working maven pom.xml for jbossall-client.jar

[Keith Johnston (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12442559#action_12442559 ] 

Keith Johnston commented on JBAS-6320:
--------------------------------------

After some more investigating it seems that jboss as jars are now located at http://repository.jboss.org/maven2/org/jboss/jbossas

If so, it looks like http://repository.jboss.org/maven2/org/jboss/jbossas/jboss-as-client/5.0.0.GA/jboss-as-client-5.0.0.GA.pom could fit the bill. Could you confirm that this pom is equivalent to the old jbossall-client.jar?

> Provide a working maven pom.xml for jbossall-client.jar
> -------------------------------------------------------
>
>                 Key: JBAS-6320
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6320
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>    Affects Versions: JBossAS-5.0.0.GA
>         Environment: All
>            Reporter: Keith Johnston
>            Assignee: Paul Gier
>
> Issue
> From jBoss 4.2 to 5.0 the decision was made to change jbossall-client.jar to be an empty jar, referring to other jars via the manifest classpath. Unfortunately this significantly increases the maintenance burden for developers, particularly those using maven. Rather than simply add a single dependency to a project pom we must now add a dependency  for each entry in the manifest classpath.
> Resolution
> Publish a pom for jbossall-client that describes all necessary dependencies to the jboss maven repo. The problem would be solved using maven transitive dependencies.
> Further detail
> This point has already been raised by Bill Burke elsewhere: http://lists.jboss.org/pipermail/jboss-development/2008-February/011420.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira