[
https://jira.jboss.org/jira/browse/SOAG-115?page=com.atlassian.jira.plugi...
]
Jeff Yu commented on SOAG-115:
------------------------------
Found that jBPM and Riftsaw did this differently.
jBPM uses the 'org.jbpm4.dependencies.esb.rosetta' as the new groupId for that
artifact. And then simply install rosetta into the jboss repo.
while Riftsaw put all the artifacts into its own svn repo, and then ask users to check out
it manually into its local repo.
I would prefer to use the jBPM way, as it is simple, both for users and developers. Any
objections???
create a overlord maven2 repo that contains unmavenized jars, like
jbossesb rosetta.
------------------------------------------------------------------------------------
Key: SOAG-115
URL:
https://jira.jboss.org/jira/browse/SOAG-115
Project: SOA Governance
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 1.0 MR2
Reporter: Jeff Yu
Assignee: Jeff Yu
Fix For: 1.0 MR3
Learned this both from jBPM and Riftsaw, they have their own little maven2 repo to
contain those unmavenized jars, so that users don't need to install these jars
locally.
--
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