9:12 a.m.
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
1:13 p.m.
There's one projects left that hasn't moved to Beta2 parent pom:
Aerogear: https://issues.jboss.org/browse/JBIDE-14834 (PR pending)
Thanks to everyone else for moving to Beta2.
Cheers,
On 06/11/2013 10:12 AM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4:53 p.m.
On 06/11/2013 11:13 AM, Nick Boldt wrote:
There's one projects left that hasn't moved to Beta2 parent
pom:
Aerogear: https://issues.jboss.org/browse/JBIDE-14834 (PR pending)
pushed to master.
Denis
Thanks to everyone else for moving to Beta2.
Cheers,
On 06/11/2013 10:12 AM, Max Rydahl Andersen wrote:
> Hi core-compnent leads,
>
> Thursday 13th is branch/codefreeze day as planned [1].
>
> Special Note:
> Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
> line of defense/attack on this codefreeze.
>
> A quick reminder what branch/codefreeze means for each component/repo owner:
>
> 0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
>
> 1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
> Should look something like this:
>
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.0.Beta2-SNAPSHOT</version>
> </parent>
>
> 2) Make sure your component builds and passes its tests when run locally.
>
> $ mvn clean verify
>
> 3) Make a branch for the Beta2 builds to use.
>
> Most components uses master, thus the steps would be something like:
>
> $ git checkout master
> $ git pull origin master
> $ git checkout -b jbosstools-4.1.0.Beta2x
> $ git push origin jbosstools-4.1.0.Beta2x
>
> 4) Respond to this mail before end of Thursday with a "All Done for component:
> <your component>" or "<your component> cannot
branch/freeze today because of
> <jira issues> must be done first"
>
> Thank you!
>
> [1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
2:11 p.m.
ALL DONE for OpenShift. See Details below:
0) DONE
1) DONE
2) DONE
[INFO] openshift.all ..................................... SUCCESS [0.585s]
[INFO] openshift.plugins ................................. SUCCESS [0.013s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.417s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.553s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.508s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [5.324s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [23.883s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [30.976s]
[INFO] openshift.features ................................ SUCCESS [0.009s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.287s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.249s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS
[0.137s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.149s]
[INFO] openshift.site .................................... SUCCESS [13.779s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11:20.463s
[INFO] Finished at: Thu Jun 13 21:07:28 CEST 2013
3) DONE
To git@github.com:jbosstools/jbosstools-openshift.git
* [new branch] jbosstools-4.1.0.Beta2x -> jbosstools-4.1.0.Beta2x
On 06/11/2013 04:12 PM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
3:32 p.m.
New subject: ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
ESB and Web Services both are running with yellow builds (not green) right now. Have
branched and cleaned up JIRAs for 4.1.0.Beta2.
The issues remaining are: JBIDE-14866 (ESB, asking Rob Stryker for help - builds and tests
fine locally, but not on Jenkins) and JBIDE-14867 (WS, looking into now)
So unfortunately ESB & WS are not going to be ready for code freeze because of these
two test issues.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Tuesday, June 11, 2013 8:12:35 AM
Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps
inside
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:40 p.m.
New subject: ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
Thanks to some help from Denis, WS tests are now blue!
Thanks Denis!
Still hoping for some help from Rob Stryker on the ESB test failures.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>
To: "Max Rydahl Andersen" <manderse(a)redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Thursday, June 13, 2013 2:32:21 PM
Subject: Re: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday -
steps inside
ESB and Web Services both are running with yellow builds (not green) right now. Have
branched and cleaned up JIRAs for 4.1.0.Beta2.
The issues remaining are: JBIDE-14866 (ESB, asking Rob Stryker for help - builds and tests
fine locally, but not on Jenkins) and JBIDE-14867 (WS, looking into now)
So unfortunately ESB & WS are not going to be ready for code freeze because of these
two test issues.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Tuesday, June 11, 2013 8:12:35 AM
Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps
inside
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:44 p.m.
New subject: ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
Thanks, Denis !!!
Best regards,
/Xavier
On Jun 17, 2013, at 9:40 PM, Brian Fitzpatrick wrote:
Thanks to some help from Denis, WS tests are now blue!
Thanks Denis!
Still hoping for some help from Rob Stryker on the ESB test failures.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>
To: "Max Rydahl Andersen" <manderse(a)redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Thursday, June 13, 2013 2:32:21 PM
Subject: Re: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday -
steps inside
ESB and Web Services both are running with yellow builds (not green) right now. Have
branched and cleaned up JIRAs for 4.1.0.Beta2.
The issues remaining are: JBIDE-14866 (ESB, asking Rob Stryker for help - builds and
tests fine locally, but not on Jenkins) and JBIDE-14867 (WS, looking into now)
So unfortunately ESB & WS are not going to be ready for code freeze because of these
two test issues.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Tuesday, June 11, 2013 8:12:35 AM
Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps
inside
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
11:35 p.m.
New subject: ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
Cool. The esb stuff is for JBTIS release so it's not a hard requirement right now.
But still good to have the tests pass.
/max (sent from my phone)
On 17/06/2013, at 21.40, Brian Fitzpatrick
<bfitzpat(a)redhat.com> wrote:
Thanks to some help from Denis, WS tests are now blue!
Thanks Denis!
Still hoping for some help from Rob Stryker on the ESB test failures.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Brian Fitzpatrick" <bfitzpat(a)redhat.com>
To: "Max Rydahl Andersen" <manderse(a)redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Thursday, June 13, 2013 2:32:21 PM
Subject: Re: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze
Thursday - steps inside
ESB and Web Services both are running with yellow builds (not green) right now. Have
branched and cleaned up JIRAs for 4.1.0.Beta2.
The issues remaining are: JBIDE-14866 (ESB, asking Rob Stryker for help - builds and
tests fine locally, but not on Jenkins) and JBIDE-14867 (WS, looking into now)
So unfortunately ESB & WS are not going to be ready for code freeze because of these
two test issues.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Tuesday, June 11, 2013 8:12:35 AM
Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday -
steps inside
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
3:39 p.m.
All Done for component: birt, portlet.
arquillian cannot branch/freeze today because of
https://issues.jboss.org/browse/JBIDE-14843 must be reviewed.
Snjeza
On 6/11/2013 4:12 PM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4:16 p.m.
All DONE for component LiveReload
/Xavier
On Jun 13, 2013, at 10:39 PM, Snjezana Peco wrote:
All Done for component: birt, portlet.
arquillian cannot branch/freeze today because of
https://issues.jboss.org/browse/JBIDE-14843 must be reviewed.
Snjeza
On 6/11/2013 4:12 PM, Max Rydahl Andersen wrote:
> Hi core-compnent leads,
>
> Thursday 13th is branch/codefreeze day as planned [1].
>
> Special Note:
> Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
> line of defense/attack on this codefreeze.
>
> A quick reminder what branch/codefreeze means for each component/repo owner:
>
> 0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
>
> 1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
> Should look something like this:
>
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.0.Beta2-SNAPSHOT</version>
> </parent>
>
> 2) Make sure your component builds and passes its tests when run locally.
>
> $ mvn clean verify
>
> 3) Make a branch for the Beta2 builds to use.
>
> Most components uses master, thus the steps would be something like:
>
> $ git checkout master
> $ git pull origin master
> $ git checkout -b jbosstools-4.1.0.Beta2x
> $ git push origin jbosstools-4.1.0.Beta2x
>
> 4) Respond to this mail before end of Thursday with a "All Done for component:
> <your component>" or "<your component> cannot branch/freeze
today because of
> <jira issues> must be done first"
>
> Thank you!
>
> [1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
12:29 a.m.
On 06/13/2013 11:16 PM, Xavier Coulon wrote:
All DONE for component LiveReload
Hi Xavier,
It looks like LiveReload had a regression yesterday. Is this regression
in the branch?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa...
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
1:36 a.m.
I built yesterday on my machine before pushing and it worked :-/
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] livereload.all .................................... SUCCESS [0.395s]
[INFO] livereload.plugins ................................ SUCCESS [0.010s]
[INFO] org.jboss.tools.livereload.core ................... SUCCESS [3.755s]
[INFO] org.jboss.tools.livereload.ui ..................... SUCCESS [1.591s]
[INFO] livereload.tests .................................. SUCCESS [0.015s]
[INFO] org.jboss.tools.livereload.test ................... SUCCESS [1:25.807s]
[INFO] livereload.features ............................... SUCCESS [0.009s]
[INFO] org.jboss.tools.livereload.feature ................ SUCCESS [0.422s]
[INFO] org.jboss.tools.livereload.test.feature ........... SUCCESS [0.238s]
[INFO] livereload.site ................................... SUCCESS [6.740s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:17.529s
[INFO] Finished at: Thu Jun 13 23:14:54 CEST 2013
[INFO] Final Memory: 57M/636M
Now, let me see what I can do...
/Xavier
On Jun 14, 2013, at 7:29 AM, Mickael Istria wrote:
On 06/13/2013 11:16 PM, Xavier Coulon wrote:
> All DONE for component LiveReload
Hi Xavier,
It looks like LiveReload had a regression yesterday. Is this regression in the branch?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa...
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
3:02 a.m.
aerogear branched..
--
Gorkem
On Fri, Jun 14, 2013 at 2:36 AM, Xavier Coulon <xcoulon(a)redhat.com> wrote:
I built yesterday on my machine before pushing and it worked :-/
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] livereload.all .................................... SUCCESS [0.395s]
[INFO] livereload.plugins ................................ SUCCESS [0.010s]
[INFO] org.jboss.tools.livereload.core ................... SUCCESS [3.755s]
[INFO] org.jboss.tools.livereload.ui ..................... SUCCESS [1.591s]
[INFO] livereload.tests .................................. SUCCESS [0.015s]
[INFO] org.jboss.tools.livereload.test ................... SUCCESS
[1:25.807s]
[INFO] livereload.features ............................... SUCCESS [0.009s]
[INFO] org.jboss.tools.livereload.feature ................ SUCCESS [0.422s]
[INFO] org.jboss.tools.livereload.test.feature ........... SUCCESS [0.238s]
[INFO] livereload.site ................................... SUCCESS [6.740s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2:17.529s
[INFO] Finished at: Thu Jun 13 23:14:54 CEST 2013
[INFO] Final Memory: 57M/636M
Now, let me see what I can do...
/Xavier
On Jun 14, 2013, at 7:29 AM, Mickael Istria wrote:
On 06/13/2013 11:16 PM, Xavier Coulon wrote:
All DONE for component LiveReload
Hi Xavier,
It looks like LiveReload had a regression yesterday. Is this regression in
the branch?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa...
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com/> - My
Tweets<http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4:21 p.m.
All done for central
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] central.maven.examples.all ........................ SUCCESS [0.577s]
[INFO] maven.all ......................................... SUCCESS [0.084s]
[INFO] maven.plugins ..................................... SUCCESS [0.051s]
[INFO] org.jboss.tools.maven.core ........................ SUCCESS [3.281s]
[INFO] org.jboss.tools.maven.ui .......................... SUCCESS [1.958s]
[INFO] org.jboss.tools.maven.conversion.ui ............... SUCCESS [1.119s]
[INFO] maven.features .................................... SUCCESS [0.068s]
[INFO] org.jboss.tools.maven.feature ..................... SUCCESS [0.831s]
[INFO] org.jboss.tools.maven.seam ........................ SUCCESS [2.408s]
[INFO] org.jboss.tools.maven.seam.feature ................ SUCCESS [0.414s]
[INFO] org.jboss.tools.maven.cdi ......................... SUCCESS [1.437s]
[INFO] org.jboss.tools.maven.cdi.feature ................. SUCCESS [0.252s]
[INFO] org.jboss.tools.maven.hibernate ................... SUCCESS [1.364s]
[INFO] org.jboss.tools.maven.hibernate.feature ........... SUCCESS [0.318s]
[INFO] org.jboss.tools.maven.portlet ..................... SUCCESS [1.462s]
[INFO] org.jboss.tools.maven.portlet.feature ............. SUCCESS [0.449s]
[INFO] examples.all ...................................... SUCCESS [0.057s]
[INFO] examples.plugins .................................. SUCCESS [0.062s]
[INFO] org.jboss.tools.project.examples .................. SUCCESS [4.969s]
[INFO] org.jboss.tools.maven.project.examples ............ SUCCESS [2.765s]
[INFO] org.jboss.tools.project.examples.cheatsheet ....... SUCCESS [1.313s]
[INFO] examples.features ................................. SUCCESS [0.066s]
[INFO] org.jboss.tools.project.examples.feature .......... SUCCESS [0.309s]
[INFO] org.jboss.tools.maven.project.examples.feature .... SUCCESS [0.342s]
[INFO] maven.tests ....................................... SUCCESS [0.038s]
[INFO] org.jboss.tools.maven.common.test ................. SUCCESS [42.016s]
[INFO] org.jboss.tools.maven.jbosspackaging .............. SUCCESS [1.047s]
[INFO] org.jboss.tools.maven.jdt ......................... SUCCESS [1.010s]
[INFO] org.jboss.tools.maven.configurators.tests ......... SUCCESS
[3:40.889s]
[INFO] org.jboss.tools.maven.conversion.test ............. SUCCESS [49.050s]
[INFO] org.jboss.tools.maven.profiles.core ............... SUCCESS [0.482s]
[INFO] org.jboss.tools.maven.profiles.test ............... SUCCESS [25.455s]
[INFO] org.jboss.tools.maven.sourcelookup.core ........... SUCCESS [0.923s]
[INFO] org.jboss.tools.maven.sourcelookup.ui ............. SUCCESS [1.086s]
[INFO] org.jboss.tools.maven.sourcelookup.test ........... SUCCESS
[2:57.039s]
[INFO] org.jboss.tools.maven.test.feature ................ SUCCESS [2.403s]
[INFO] org.jboss.tools.maven.jbosspackaging.feature ...... SUCCESS [4.318s]
[INFO] org.jboss.tools.maven.profiles.ui ................. SUCCESS [3.816s]
[INFO] org.jboss.tools.maven.profiles.feature ............ SUCCESS [0.569s]
[INFO] org.jboss.tools.maven.gwt ......................... SUCCESS [3.434s]
[INFO] org.jboss.tools.maven.gwt.feature ................. SUCCESS [1.518s]
[INFO] org.jboss.tools.maven.sourcelookup.feature ........ SUCCESS [0.931s]
[INFO] org.jboss.tools.maven.jdt.feature ................. SUCCESS [1.351s]
[INFO] org.jboss.tools.community.project.examples ........ SUCCESS [0.532s]
[INFO] org.jboss.tools.community.project.examples.feature SUCCESS [0.531s]
[INFO] examples.tests .................................... SUCCESS [0.211s]
[INFO] org.jboss.tools.project.examples.test ............. SUCCESS
[6:24.881s]
[INFO] org.jboss.tools.project.examples.test.feature ..... SUCCESS [1.585s]
[INFO] central.all ....................................... SUCCESS [0.120s]
[INFO] central.plugins ................................... SUCCESS [0.077s]
[INFO] org.jboss.tools.central ........................... SUCCESS [11.125s]
[INFO] org.jboss.tools.community.central ................. SUCCESS [0.253s]
[INFO] org.jboss.tools.central.themes .................... SUCCESS [0.857s]
[INFO] central.features .................................. SUCCESS [0.076s]
[INFO] org.jboss.tools.central.feature ................... SUCCESS [0.239s]
[INFO] org.jboss.tools.community.central.feature ......... SUCCESS [18.750s]
[INFO] org.jboss.tools.central.themes.feature ............ SUCCESS [0.876s]
[INFO] central.tests ..................................... SUCCESS [0.122s]
[INFO] org.jboss.tools.central.test ...................... SUCCESS
[1:42.105s]
[INFO] org.jboss.tools.central.test.feature .............. SUCCESS [0.255s]
[INFO] central.maven.examples.site ....................... SUCCESS
[1:23.228s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 21:34.544s
[INFO] Finished at: Thu Jun 13 23:18:01 CEST 2013
[INFO] Final Memory: 194M/667M
[INFO]
------------------------------------------------------------------------
Fred Bricon@FBRICON-WIN /d/Dev/GitHub/jbosstools-central
(jbosstools-4.1.0.Beta2x)
Looks like one Jenkins slave always timeouts one test. Works locally, on
other slaves, couldn't find what really happens so I've extended the
timeout. We'll see how it goes.
Le 11/06/2013 16:12, Max Rydahl Andersen a écrit :
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
5:27 p.m.
All Done for base, jst, javaee.
On 06/11/2013 07:12 AM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
7:04 p.m.
Done for XULRunner and VPE.
On Tue, Jun 11, 2013 at 5:12 PM, Max Rydahl Andersen <manderse(a)redhat.com>wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo
owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in
jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for
jboss tools parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for
component:
<your component>" or "<your component> cannot branch/freeze
today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Best Regards,
Yahor Radtsevich
11:06 p.m.
Server is blue-balled, branched, and ready to go.
Max: Nobody made the n&n jiras ;)
On 06/11/2013 10:12 PM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
1:05 a.m.
https://issues.jboss.org/browse/JBIDE-14869 Create New and Noteworthy
for 4.1.0.Beta2
was created, component leads, please provide PR for N&N or reject
component subtask if there is nothing to say about component in
4.1.0.Beta2 release.\
Thanks
Denis
On 06/11/2013 07:12 AM, Max Rydahl Andersen wrote:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze
today because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
3:05 a.m.
All Done for components Hibernate & Forge
Cheers,
Koen
Op 11-jun.-2013, om 16:12 heeft Max Rydahl Andersen het volgende geschreven:
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today
because of
<jira issues> must be done first"
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
3974
days inactive
3981
days old
jbosstools-dev@lists.jboss.org
18 comments
15 participants
participants (15)
-
Alexey Kazakov -
André Dietisheim -
Brian Fitzpatrick -
Denis Golovin -
Fred Bricon -
Gorkem Ercan -
Koen Aers -
Max Andersen -
Max Rydahl Andersen
-
Mickael Istria -
Nick Boldt -
Rob Stryker -
Snjezana Peco -
Xavier Coulon -
Yahor Radtsevich