[jboss-jira] [JBoss JIRA] Reopened: (JBBUILD-602) Missing javax.jms:jms:jar:1.1
[
https://jira.jboss.org/jira/browse/JBBUILD-602?page=com.atlassian.jira.pl...
]
Thomas Diesler reopened JBBUILD-602:
------------------------------------
AFACS, we are talking about a transitive dependency that is pulled in from log4j, which I
cannot change.
Any jboss project should be able to define such a dependency (on log4j) without hitting
this issue. As a consequence, this would mean that transitive dependencies from key 3rd
party artefacts should be available in the federated public repo and not only the
deprecated one.
Try building jboss-logging-log4j:jar:2.2.0.CR1 with an initially empty local repo. This
should work, right?
Missing javax.jms:jms:jar:1.1
-----------------------------
Key: JBBUILD-602
URL: https://jira.jboss.org/jira/browse/JBBUILD-602
Project: JBoss Build System
Issue Type: Bug
Components: Artifact Repositories
Reporter: Thomas Diesler
Assignee: Paul Gier
Fix For: Maven Repository 2.0
Missing:
----------
1) javax.jms:jms:jar:1.1
Try downloading the file manually from:
http://java.sun.com/products/jms/docs.html
Then, install it using the command:
mvn install:install-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.osgi.framework:jboss-osgi-framework:jar:1.0.0.Alpha5-SNAPSHOT
2) org.jboss.logging:jboss-logging-log4j:jar:2.2.0.CR1
3) log4j:log4j:jar:1.2.15
4) javax.jms:jms:jar:1.1
--
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