[
http://jira.codehaus.org/browse/MAVENUPLOAD-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MAVENUPLOAD-2524.
---------------------------------------
Assignee: Carlos Sanchez
Resolution: Fixed
you were right, one entry for each top level groupId
> Project with Multiple groupID's need to be rsynced to central repo
> ------------------------------------------------------------------
>
> Key: MAVENUPLOAD-2524
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2524
> Project: Maven Upload Requests
> Issue Type: Task
> Reporter: Mark Diggory
> Assignee: Carlos Sanchez
>
> Repo Maintainers,
> We have just successfully merged two OS projects (http://www.dspace.org,
> http://www.fedora-commons.org) into a new foundation
> (http://www.duraspace.org) and are looking to combine our maven local release
> repository
> ("org.dspace","[email protected]:/var/maven/release","rsync_ssh","DSpace
> Developers","[email protected]",,) for publishing
> artifacts from both projects into the maven central repository. What is the
> recommended practice in this area when one would want to have multiple
> groupId's rsync'd (org.dspace, org.fedora-commons, org.duraspace) from the
> same source repository? Do we need to request separate entries be added?
> ("org.duraspace","[email protected]:/var/maven/release","rsync_ssh","DSpace
> Developers","[email protected]",,)
> ("org.fedora-commons","[email protected]:/var/maven/release","rsync_ssh","DSpace
> Developers","[email protected]",,)
> ("org.dspace","[email protected]:/var/maven/release","rsync_ssh","DSpace
> Developers","[email protected]",,)
> Cheers,
> Mark Diggory
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
