[jboss-jira] [JBoss JIRA] Commented: (JBAS-6098) juddi-service.sar bundles juddi.jar & scout.jar

[Richard Opalka (JIRA)]

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

Richard Opalka commented on JBAS-6098:
--------------------------------------

I did the mavenization of JAXR project, so I'll take care of this fix.

> juddi-service.sar bundles juddi.jar & scout.jar
> -----------------------------------------------
>
>                 Key: JBAS-6098
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6098
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JAXR service
>    Affects Versions: JBossAS-4.2.3.GA
>            Reporter: Dimitris Andreadis
>            Assignee: Richard Opalka
>             Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.4.GA
>
>
> Although juddi.jar & scout.jar are imported as dependencies by build-thirdparty.xml, those are not used in the final deliverable.
> Rather juddi-service.sar bundles juddi.jar & scout.jar and this is what gets expanded in the all configuration.
> First, we don't know what those version are or how they are produced. In fact, juddi.jar is altered with a class added to it:
> org/apache/juddi/auth/JBossAuthenticator$1.class
> org/apache/juddi/auth/JBossAuthenticator.class
> This has created problems with the JPackage bundle of jboss 4.2.3 for Fedora.
> I think there right approach would be to remove external dependencies from jboss-jaxr artifacts.
> It's quite possible we have the same problem in jboss trunk.

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