In fact by default the buildnumber plugin fails if we use it on a project which isn&#39;t store in a SCM. For example if you are building it from an export of SVN instead of a checkout.<div>We had many issues with that at exo because we activated the plugin on every build and we had some users who get our sources bundles which doesn&#39;t store .svn directories).</div>

<div>In the case of gatein the buildnumber plugin is executed only within the release profile thus we should always have a SVN checkout.</div><div>This fix is only a workaround if someone get an export of our code and call &quot;mvn install -Prelease&quot; (I think it will be very rare but I prefer to be sure we don&#39;t encouter it).</div>

<div><br></div><div>I don&#39;t think it is possible to enforce SCM settings. And even if they are defined the issue isn&#39;t with SCM info but with the fact of having a local checkout of the project.</div><div><br></div>

<div>Arnaud</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Oct 6, 2009 at 8:33 AM, Thomas Heute <span dir="ltr">&lt;<a href="mailto:theute@redhat.com">theute@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">




  

<div text="#000000" bgcolor="#ffffff">
Awesome !<br>
<br>
Quick question though, I&#39;ve seen:<br>
&quot;Do not fail if we don&#39;t use an SCM - but difficult to do a release&quot;<br>
<br>
Is there a particular reason to not enforce the declaration of the SCM,
or did you just do this because we&#39;ve never said we would enforce this
? (Issue for sub-components maybe ?)<br>
<br>
I would be in favor of enforcing unless I missed something.<br>
<br>
Thanks,<br>
Thomas.<div><div></div><div class="h5"><br>
<br>
On 10/06/2009 06:08 AM, Arnaud HERITIER wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">Hi all,
  <div><br>
  </div>
  <div>  I released jboss-parent 5-Beta-3. I moved into it what I think
could be interesting for any jboss project. I let Paul review it. If
needed we&#39;ll do a beta4 if some things are wrong.</div>
  <div>  I updated gatein-parent and gatein-dep which are using it.</div>
  <div>  I released gatein-parent 1.0.0-Beta01 and gatein-dep
1.0.0-Beta01.</div>
  <div>  Now you need to use maven 2.2.1 to build gatein (an enforcer
rule checks it).</div>
  <div>  I updated all our components to use them.</div>
  <div>  I released gatein-mop 1.0.0-Beta08.</div>
  <div><br>
  </div>
  <div>  Everything was automated. Direct uploads on JBoss SVN to
deploy releases works fine.</div>
  <div><br>
  </div>
  <div>  I updated gatein-portal to require java 6 to build.</div>
  <div>  I gatein-parent I put in the release profile the check about
java 5 APIs compability</div>
  <div><br>
  </div>
  <div><br clear="all">
Cheers,<br>
  <br>
Arnaud<br>
  <br>
# Arnaud Héritier<br>
# Software Factory Manager<br>
# eXo Platform<br>
# <a href="http://www.exoplatform.com" target="_blank">http://www.exoplatform.com</a><br>
# <a href="http://blog.aheritier.net" target="_blank">http://blog.aheritier.net</a><br>
  </div>
  </div></div><pre><hr size="4" width="90%">
_______________________________________________
gatein-dev mailing list
<a href="mailto:gatein-dev@lists.jboss.org" target="_blank">gatein-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a>
  </pre>
</blockquote>
<br>
</div>

</blockquote></div><br></div>