11:08 p.m.
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
1:33 a.m.
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 list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
7:48 a.m.
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(a)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@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/gatein-dev
4:05 a.m.
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 need to change the gatein-parent so PC component will use the
1.0.0-Beta01-SNAPSHOT
Regards,
--
Martin Podolinsky
--
Enterprise Portal Platform Product Lead
JBoss, by Red Hat
email: mpodolin(a)redhat.com
4:11 a.m.
Martin Podolinsky wrote:
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 need to change the gatein-parent so PC component will use the
1.0.0-Beta01-SNAPSHOT
uff copy&paste mistake. I meant to use 1.0.0-Beta02-SNAPSHOT
Regards,
--
Martin Podolinsky
--
Enterprise Portal Platform Product Lead
JBoss, by Red Hat
email: mpodolin(a)redhat.com
7:40 a.m.
:-) I prefer
No problem it's done for it.Do not forget to deploy the new gatein-parent
SNAPSHOT to not force others to build it locally.
Arnaud
On Tue, Oct 6, 2009 at 11:11 AM, Martin Podolinsky <mpodolin(a)redhat.com>wrote:
Martin Podolinsky wrote:
> 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 need to change the gatein-parent so PC component will use the
> 1.0.0-Beta01-SNAPSHOT
uff copy&paste mistake. I meant to use 1.0.0-Beta02-SNAPSHOT
>
> Regards,
>
>
--
Martin Podolinsky
--
Enterprise Portal Platform Product Lead
JBoss, by Red Hat
email: mpodolin(a)redhat.com
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
8:27 a.m.
Not an issue for now. That plugin settings went directly to the
component's pom.
Cheers, Martin
Arnaud HERITIER wrote:
:-) I prefer
No problem it's done for it.
Do not forget to deploy the new gatein-parent SNAPSHOT to not force
others to build it locally.
Arnaud
On Tue, Oct 6, 2009 at 11:11 AM, Martin Podolinsky <mpodolin(a)redhat.com
<mailto:mpodolin@redhat.com>> wrote:
Martin Podolinsky wrote:
> 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 need to change the gatein-parent so PC component will use the
> 1.0.0-Beta01-SNAPSHOT
uff copy&paste mistake. I meant to use 1.0.0-Beta02-SNAPSHOT
>
> Regards,
>
>
--
Martin Podolinsky
--
Enterprise Portal Platform Product Lead
JBoss, by Red Hat
email: mpodolin(a)redhat.com <mailto:mpodolin@redhat.com>
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org <mailto:gatein-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/gatein-dev
--
Martin Podolinsky
--
Enterprise Portal Platform Product Lead
JBoss, by Red Hat
email: mpodolin(a)redhat.com
5:44 a.m.
When i try to package (mvn install -Ppkg-tomcat) I now get:
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed with message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not
allowed )
org.codehaus.mojo:exec-maven-plugin. The version currently in use is
1.1.1
Best practice is to always define plugin versions!
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
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 list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
6:58 a.m.
On Oct 6, 2009, at 12:44 PM, Thomas Heute wrote:
When i try to package (mvn install -Ppkg-tomcat) I now get:
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are
not allowed )
org.codehaus.mojo:exec-maven-plugin. The version currently in
use is 1.1.1
Best practice is to always define plugin versions!
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific
messages explaining why the rule failed.
This should have been fixed by Dimitri now.
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal: http://jbossportal.blogspot.com / http://twitter.com/jbossportal
Follow me: http://metacosm.codepuccino.com / http://twitter.com/metacosm
7 a.m.
On 10/06/2009 01:58 PM, Christophe Laprun wrote:
On Oct 6, 2009, at 12:44 PM, Thomas Heute wrote:
> When i try to package (mvn install -Ppkg-tomcat) I now get:
>
> [INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
> [WARNING] Rule 0:
> org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
> message:
> Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are
> not allowed )
> org.codehaus.mojo:exec-maven-plugin. The version currently in use
> is 1.1.1
> Best practice is to always define plugin versions!
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Some Enforcer rules have failed. Look above for specific
> messages explaining why the rule failed.
This should have been fixed by Dimitri now.
I fixed this locally but got an
additional error.
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal: http://jbossportal.blogspot.com /
http://twitter.com/jbossportal
Follow me: http://metacosm.codepuccino.com / http://twitter.com/metacosm
7:03 a.m.
On 10/06/2009 02:00 PM, Thomas Heute wrote:
On 10/06/2009 01:58 PM, Christophe Laprun wrote:
> On Oct 6, 2009, at 12:44 PM, Thomas Heute wrote:
>
>
>> When i try to package (mvn install -Ppkg-tomcat) I now get:
>>
>> [INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
>> [WARNING] Rule 0:
>> org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
>> message:
>> Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are
>> not allowed )
>> org.codehaus.mojo:exec-maven-plugin. The version currently in use
>> is 1.1.1
>> Best practice is to always define plugin versions!
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Some Enforcer rules have failed. Look above for specific
>> messages explaining why the rule failed.
>>
> This should have been fixed by Dimitri now.
>
I fixed this locally but got an additional error.
It works now... Oddly enough I added this in packaging/pom.xml and it
failed, adding it in the root (as Dimitri did) it now works :)
> Cordialement / Best,
> Chris
>
> ==
> Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
> Follow JBoss Portal: http://jbossportal.blogspot.com /
> http://twitter.com/jbossportal
> Follow me: http://metacosm.codepuccino.com / http://twitter.com/metacosm
>
>
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
7:51 a.m.
Sorry for issues on gatein-portal. I just forgot to commit my changes.
Everything should be fine now.
http://builder.exoplatform.org/hudson/view/gatein/
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Tue, Oct 6, 2009 at 2:03 PM, Thomas Heute <theute(a)redhat.com> wrote:
On 10/06/2009 02:00 PM, Thomas Heute wrote:
> On 10/06/2009 01:58 PM, Christophe Laprun wrote:
>
>> On Oct 6, 2009, at 12:44 PM, Thomas Heute wrote:
>>
>>
>>> When i try to package (mvn install -Ppkg-tomcat) I now get:
>>>
>>> [INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
>>> [WARNING] Rule 0:
>>> org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
>>> message:
>>> Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are
>>> not allowed )
>>> org.codehaus.mojo:exec-maven-plugin. The version currently in use
>>> is 1.1.1
>>> Best practice is to always define plugin versions!
>>> [INFO]
>>>
------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>>
------------------------------------------------------------------------
>>> [INFO] Some Enforcer rules have failed. Look above for specific
>>> messages explaining why the rule failed.
>>>
>> This should have been fixed by Dimitri now.
>>
> I fixed this locally but got an additional error.
>
It works now... Oddly enough I added this in packaging/pom.xml and it
failed, adding it in the root (as Dimitri did) it now works :)
>> Cordialement / Best,
>> Chris
>>
>> ==
>> Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
>> Follow JBoss Portal: http://jbossportal.blogspot.com /
>> http://twitter.com/jbossportal
>> Follow me: http://metacosm.codepuccino.com /
http://twitter.com/metacosm
>>
>>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
5840
days inactive
5840
days old
11 comments
5 participants
participants (5)
-
Arnaud HERITIER -
Arnaud HERITIER -
Christophe Laprun -
Martin Podolinsky -
Thomas Heute