|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MMOCKRM-10) Add support for Arc... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MMOCKRM-10) Add support fo... Robert Scholte (JIRA)

Any thoughts on this? Would it fit in the usage space of this tool?
For the mock repo:
1) If a hard-coded archetype-catalog.xml exists serve it as-is, otherwise
2) Construct an archetype-catalog.xml based on existing poms with the 'maven-archetype' packaging type.
For the proxy repo I guess we need to get the catalogs from the remote repos, and merge them. Could be a lot of work. Very much the same thing the archetype plugin needs to do (but currently doesn't).
For the local repo any existing archetype-catalog.xml file should be used.