[
https://issues.jboss.org/browse/JBCOMMON-102?page=com.atlassian.jira.plug...
]
Dimitris Andreadis commented on JBCOMMON-102:
---------------------------------------------
I've modified the pom.xml to
- point to our nexus repository
http://repository.jboss.org/nexus/content/groups/public/
- use the latest org.jboss:jboss-parent:6
- use the non-legacy coordinates
change apache-httpclient to commons-httpclient
change apache-slide to slide
Projects upstream may need to update their exclude lists?
The release process is then more or less the same but you deploy directly the jboss nexus
repository, then you need to login there and move/release the artifacts from the staging
to the standard area.
http://community.jboss.org/wiki/JBossCommonCoreReleaseProcess
Release jboss-common-core 2.2.18
--------------------------------
Key: JBCOMMON-102
URL:
https://issues.jboss.org/browse/JBCOMMON-102
Project: JBoss Common
Issue Type: Release
Security Level: Public(Everyone can see)
Components: common-core (2.x)
Reporter: Dimitris Andreadis
Assignee: Dimitris Andreadis
Fix For: 2.2.18.GA
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira