Hi Martin, In general the recommendation with Maven is not to embed release repos in POMs.
The problem with this specific job was the use of the mvn_localrepo script. By switching the job to use the Maven Build Target with the Private Repository option, I got past this issue. On 28 May 2010, at 08:19, Martin Gencur wrote: > Pete/others, > I would like to know what the policy of specifying repositories for > maven is. Do you suppose (according to this document: > http://community.jboss.org/wiki/MavenGettingStarted-Users) that all > users of CDI-TCK will have the > https://repository.jboss.org/nexus/content/groups/public/ repository > specified in their settings.xml file? The job from subject of this email > is now failing because the repo isn't specified in settings.xml in > hudson. Isn't it better to specify the repo directly in pom.xml in > cdt-tck runner (or some other pom) so that we would be able to run the > testsuite anywhere? If not, I will send a ticket to helpdesk to change > the settings.xml (I shouldn't do it by myself). > > Thanks for clarifying this > > Martin > > > > > On Thu, 2010-05-27 at 15:53 +0100, Pete Muir wrote: >> Ok, it's using my jboss-test-harness snapshot, but it hasn't got the new >> repos set up - can you fix? > > > _______________________________________________ > weld-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/weld-dev _______________________________________________ weld-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-dev
