[
http://jira.codehaus.org/browse/CONTINUUM-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated CONTINUUM-836:
-----------------------------------
Fix Version/s: 1.x
> Improve HTTP access to POMs for adding a multi-module project
> -------------------------------------------------------------
>
> Key: CONTINUUM-836
> URL: http://jira.codehaus.org/browse/CONTINUUM-836
> Project: Continuum
> Issue Type: New Feature
> Components: Core system
> Affects Versions: 1.0.3
> Reporter: Aaron Mulder
> Fix For: 1.x
>
>
> If you're not using SVN, there's no obvious way to load a multi-module POM
> into continuum.
> If you point it to a M2 repo, then the child module paths are all resolved
> relative to the parent's group/artifact/version/ directory, which doesn't
> work (parent-group/parent-artifact/parent-version/child-module-name/...)
> If you point it to a file:// URL it doesn't work because that's disabled by
> default.
> If you're using CVS, there is no clear way to get the POMs into the web --
> perhaps exporting the whole source tree onto an HTTP server, but that's going
> to be manual.
> Ideally, you could point Continuum to the parent POM in the M2 repository and
> it would check out the tree to access the child POMs, which would avoid this
> whole issue.
--
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
