[jboss-jira] [JBoss JIRA] Commented: (SECURITY-446) JBossSX client jar has the same contents of jbosssx.jar

[Leonardo Uribe (JIRA)]

    [ https://jira.jboss.org/jira/browse/SECURITY-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12501622#action_12501622 ] 

Leonardo Uribe commented on SECURITY-446:
-----------------------------------------

Hi

I'm upgrading an application to jboss 5.1.0.GA, and I tried to use this dependency on my project:

        <dependency>
            <groupId>org.jboss.jbossas</groupId>
            <artifactId>jboss-as-client</artifactId>
            <version>5.1.0.GA</version>
            <scope>runtime</scope>
        </dependency>

and it fails:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.jboss.jbossas:jboss-as-client:jar:5.1.0.GA

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.jboss.jbossas -DartifactId=jboss-as
-client -Dversion=5.1.0.GA -Dpackaging=jar -Dfile=/path/to/file

I checked manually for the presence of this file on 

http://repository.jboss.org/maven2/org/jboss/jbossas

and the jar does not exists.

Conclusion: not all artifacts required from client are on maven2 repository. I had to install manually on my local repo to make my app work.

Additionally, the manifest for jbosssx-as-client.jar and jbosssx-server.jar looks like this:

Manifest-Version: 1.0
Specification-Title: @specification.title@
Created-By: @java.vm.version@ (@java.vm.vendor@)
Ant-Version: Apache Ant 1.6.2
Implementation-Title: @implementation.title@
Specification-Vendor: @specification.vendor@
Specification-Version: @specification.version@
Implementation-Vendor-Id: @implementation.vendor.id@
Implementation-Version: @implementation.version@
Implementation-Vendor: @implementation.vendor@
Implementation-URL: @implementation.url@

Note both files are not on maven repos too. Note that for every jar you generate you need one pom.xml to be deployed when release procedure happens, so when deploy command occur, the pom is traverse and the generated jar is deployed. I suppose for generate the jars for this project you are using something not maven friendly (ant?).

> JBossSX client jar has the same contents of jbosssx.jar
> -------------------------------------------------------
>
>                 Key: SECURITY-446
>                 URL: https://jira.jboss.org/jira/browse/SECURITY-446
>             Project: JBoss Security and Identity Management
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: JBossSecurity_2.0.4.SP2
>            Reporter: Stefan Guilhen
>            Assignee: Stefan Guilhen
>             Fix For: JBossSecurity_2.1.0.GA, JBossSecurity_2.0.4.SP4
>
>
> The jbosssx-client module of the JBossSX project is producing a jar that has the exact same contents of jbosssx.jar. That is, all classes and xsds/schemas are being included in this jar and the filter in pom.xml is not working.

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