<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 04/11/2012 03:45 PM, Max Rydahl Andersen wrote:
<blockquote
cite="mid:4CDE35E1-010C-4FEB-A223-AD94ECCF606C@redhat.com"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">If JBoss Nexus is a requirement now then it seem to be missing instructions on adding the snapshot repo to ones ~/.m2/settings.xml ?
</pre>
</blockquote>
<pre wrap="">The Nexus repo is added to the top-level pom.xml for each component, so it works without additional effort.
</pre>
</blockquote>
<pre wrap="">
please don't do that. thats a very bad mvn practice.
IMO provide a settings.xml users can use via -s settings.xml or copy to their ~/.m2/settings.xml instead.
</pre>
</blockquote>
What about <release><enabled>false</...> on
snapshot repo, it could be more comfortable for users and would also
prevent from getting releases build in snapshot repo (which is the
issue you are concerned about, isn't it) ?<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>