[
https://jira.jboss.org/jira/browse/SECURITY-446?page=com.atlassian.jira.p...
]
Stefan Guilhen commented on SECURITY-446:
-----------------------------------------
Leonardo,
all these issues you're mentioning are actually JBoss AS issues, not JBoss SX issues.
The jbosssx jars that don't exist in the repo are generated by the AS build process
and not by the JBoss SX project build (perhaps calling these jars jbosssx* is not a good
idea as it may lead to confusion). The manifests of these jar on my trunk build are fixed
now, so I'm guessing this problem has been solved.
What I really don't know is why these jars are not being uploaded to the maven repo.
I'll ask Paul Gier to take a look at this and if it is indeed an issue he can open a
separate jira.
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