Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which was the
issue raised by Matthias in the previous vote[1]. The artifacts have
been regenerated and Matthias has tested the fix and it works. This is
still a beta release so there are still a few open bugs, but all of
+1
On 02/16/2011 07:48 AM, Scott O'Bryan wrote:
Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which was the
issue raised by Matthias in the previous vote[1]. The artifacts have
been regenerated and Matthias has tested the fix and it works. This
is still a beta
+1
On 2/16/2011 9:48 AM, Scott O'Bryan wrote:
Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which was the
issue raised by Matthias in the previous vote[1]. The artifacts have
been regenerated and Matthias has tested the fix and it works. This
is still a beta release
+1
On Wed, Feb 16, 2011 at 3:50 PM, MAX STARETS max.star...@oracle.com wrote:
+1
On 2/16/2011 9:48 AM, Scott O'Bryan wrote:
Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which was the issue
raised by Matthias in the previous vote[1]. The artifacts have been
+1
On Wed, Feb 16, 2011 at 8:20 AM, Matthias Wessendorf mat...@apache.orgwrote:
+1
On Wed, Feb 16, 2011 at 3:50 PM, MAX STARETS max.star...@oracle.com
wrote:
+1
On 2/16/2011 9:48 AM, Scott O'Bryan wrote:
Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which
+1
+1
-- Blake
On 2/16/11 7:20 AM, Matthias Wessendorf wrote:
+1
On Wed, Feb 16, 2011 at 3:50 PM, MAX STARETSmax.star...@oracle.com wrote:
+1
On 2/16/2011 9:48 AM, Scott O'Bryan wrote:
Hey Everyone,
Okay, I have checked in code to address TRINIDAD-2037 which was the issue
raised by Matthias
Hey all,
I was running the tasks needed to get the Trinidad 2.0.0-beta-2 release
out and now I need a vote as to whether everything looks good or not.
This is still a beta release so there are still a few open bugs, but all
of the unit tests pass and this beta has undergone some considerable
Okay, so my first hickup. I forgot to include the voting part. :D
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
and why..
+1
On 02/15/2011 02:09 AM, Scott O'Bryan wrote:
Okay, so my first hickup. I forgot to include the voting part. :D
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be
Downloaded the source:
https://repository.apache.org/content/repositories/orgapachemyfaces-005/org/apache/myfaces/trinidad/trinidad/2.0.0-beta-2/trinidad-2.0.0-beta-2-source-release.zip
did an unzip and mvn clean install
I am getting this error:
[INFO] [buildnumber:create {execution: default}]
Hello Matze,
good point. I think the revisionOnScmFailure parameter should be set
to 'unkown'.
Regards
Bernd
On Tue, Feb 15, 2011 at 10:52 AM, Matthias Wessendorf mat...@apache.org wrote:
Downloaded the source:
Matthias,
Can it be activated only for the release procedure? with the profile
apache-release?
It will also fail on computers that don't have a command line SVN client
installed. That is also the reason why we abandoned it in the company
projects.
regards
Rudy.
On 15 February 2011 11:07,
On Tue, Feb 15, 2011 at 11:11 AM, Rudy De Busscher
rdebussc...@gmail.com wrote:
Matthias,
Can it be activated only for the release procedure? with the profile
apache-release?
it does not make sense to do it only on releases - as they are always
from a TAG,
hence the revision is known.
It
This plugin actually kind of worries me if used on released code.
Unless we use a timestamp type build id, I think ANY revision of
tagged code should be unknown. It's not like people are going to
commit their changes to the tag, this allowing a unique number to be
calculated.
What do we use this
currently codi uses a profile for activating it for nightly builds (see
[1]).
regards,
gerhard
[1] https://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk/pom.xml
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support
Yeah... This makes more sense to me. Only nightly builds really need this
info and it should be easy enough to add the custom profile to Hudson (or
whatever they're calling it these days).. :)
On Feb 15, 2011, at 6:31 AM, Gerhard gerhard.petra...@gmail.com wrote:
currently codi uses a profile
yes it's easy - you just have to add the profile.
e.g. in case of codi: clean deploy -Pextended-manifest
(at Goals und Optionen)
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
+1
On 2/15/2011 4:09 AM, Scott O'Bryan wrote:
+1
On 02/15/2011 02:09 AM, Scott O'Bryan wrote:
Okay, so my first hickup. I forgot to include the voting part. :D
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal
-1
I am voting -1 because I am not able to build the source release.
The source release is the most important part of an apache release
-Matthias
On Tue, Feb 15, 2011 at 4:16 PM, MAX STARETS max.star...@oracle.com wrote:
+1
On 2/15/2011 4:09 AM, Scott O'Bryan wrote:
+1
On 02/15/2011
It built fine for me on my Mac. But +0 until we find out what is up with
Matthias' build.
-- Blake
On 2/15/11 9:06 AM, Matthias Wessendorf wrote:
-1
I am voting -1 because I am not able to build the source release.
The source release is the most important part of an apache release
-Matthias
On Tue, Feb 15, 2011 at 7:05 PM, Blake Sullivan
blake.sulli...@oracle.com wrote:
It built fine for me on my Mac.
I know why I bought one :-)
But +0 until we find out what is up with
Matthias' build.
-- Blake
On 2/15/11 9:06 AM, Matthias Wessendorf wrote:
-1
I am voting -1 because I am
Okay cool. Stopping the vote.
I'll get a patch right in for this and regenerate the artifacts. Expect
a vote today or tomorrow. Basically, I'm going to follow Gerhard's
suggestion and add a profile which is disabled by default which would
allow us to enable this functionality for nightly
23 matches
Mail list logo
