[gatein-dev] Some releases and updates

[Arnaud HERITIER]

In fact by default the buildnumber plugin fails if we use it on a project
which isn't store in a SCM. For example if you are building it from an
export of SVN instead of a checkout.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't store .svn directories).
In the case of gatein the buildnumber plugin is executed only within the
release profile thus we should always have a SVN checkout.
This fix is only a workaround if someone get an export of our code and call
"mvn install -Prelease" (I think it will be very rare but I prefer to be
sure we don't encouter it).

I don't think it is possible to enforce SCM settings. And even if they are
defined the issue isn't with SCM info but with the fact of having a local
checkout of the project.

Arnaud



On Tue, Oct 6, 2009 at 8:33 AM, Thomas Heute <theute at redhat.com> wrote:

>  Awesome !
>
> Quick question though, I've seen:
> "Do not fail if we don't use an SCM - but difficult to do a release"
>
> Is there a particular reason to not enforce the declaration of the SCM, or
> did you just do this because we've never said we would enforce this ? (Issue
> for sub-components maybe ?)
>
> I would be in favor of enforcing unless I missed something.
>
> Thanks,
> Thomas.
>
>
> On 10/06/2009 06:08 AM, Arnaud HERITIER wrote:
>
> Hi all,
>    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'll do
> a beta4 if some things are wrong.
>   I updated gatein-parent and gatein-dep which are using it.
>   I released gatein-parent 1.0.0-Beta01 and gatein-dep 1.0.0-Beta01.
>   Now you need to use maven 2.2.1 to build gatein (an enforcer rule checks
> it).
>   I updated all our components to use them.
>   I released gatein-mop 1.0.0-Beta08.
>
>    Everything was automated. Direct uploads on JBoss SVN to deploy
> releases works fine.
>
>    I updated gatein-portal to require java 6 to build.
>   I gatein-parent I put in the release profile the check about java 5 APIs
> compability
>
>
> Cheers,
>
> Arnaud
>
> # Arnaud Héritier
> # Software Factory Manager
> # eXo Platform
> # http://www.exoplatform.com
> # http://blog.aheritier.net
>
> ------------------------------
>
> _______________________________________________
> gatein-dev mailing listgatein-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/gatein-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091006/c7bb0c74/attachment.html