Ok, I have been trying to setup an Maven 2 internal repository for our company (evaluated artifactory and proximity), dumped all our Maven 2 archetypes to the internal repository. So, configured settings.xml to reflect the shiny new repository and decided to try out one of archetype:create downloaded from the new repos, lo and behold the dreaded BUILD ERROR *%%$%, the archetype-plugin in all its wisdom refused to consider my new shiny repos (always going to the mothership central). After four hours of redeploying the archetype, changing repositories, settings.xml it turns out (thanks to google) it is an open issue with maven or the archetype-plugin. In any case the solution is to provide a -DremoteRepositories system property on the command line.
-
Recent Comments
JXL21 on Weblogic 10.3 and Maven I… Roy49 on Weblogic 10.3 and Maven I… Alex on Maven 2, TestNG and Suref… Alex on Maven 2, TestNG and Suref… wkabmwboj on Weblogic 10.3 and Maven I…
rankin said
So, did it then work?
If you don’t mind, what repository did your point to?
Thanks
Mohan said
Rankin,
No, it does not work. By default the archetype plugin only looks at the central repo. So if your archetypes
are not in the central repository, you have to “tell” the archetype plugin to find your remote repos by
giving the additional command line option:
-DremoteRepositories=
cheers
mohan