March 2014 - jbosstools-dev - Jboss List Archives

JBoss Tools Core 4.1.2.CR1a bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. JBoss Tools Target Platforms: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... (JBoss Tools - current release) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBoss Tools - upcoming milestone) (This is loaded automatically into Eclipse when installing JBoss Tools. Provided here simply for reference.) Update Sites (Staging): http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.1.2.CR1... http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.1.2.CR1... http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.1.2.CR1... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1a.core/2... http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1a.corete... http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1a.webtoo... JBoss Central: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep... (JBoss Central - current release) http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3... (JBoss Central - upcoming milestone) To test the upcoming version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.1.2.CR1a/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.2.CR1a/ -- New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Changes prompting this respin-a are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%2... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 8 months

1
0
0 / 0

SCHEDULE REMINDER :: JBT 4.2.0.Beta1 / JBDS 8.0.0.Beta1: Luna M6 TP, code freeze and N&N deadlines

by Nick Boldt

Reminder: Coming early next week is the new Luna M6 target platform. Then, the code freeze for JBT 4.2.0.Beta1 / JBDS 8.0.0.Beta1 is next Thursday, March 20, 2014. Your N&N are due a week later, on Friday, March 28, 2014. Additional upcoming dates: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... See also this epic jira for more changes coming for Beta1: https://issues.jboss.org/browse/JBIDE-16739 Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 8 months

1
0
0 / 0

ACTION REQUIRED :: Please test building your JBT 4.2.0.Beta1 component with Tycho 0.20.0

by Nick Boldt

Tycho 0.20.0 is being staged currently at Eclipse for release shortly. Therefore, it's time for you to test-build your component with the new version, as we'll hopefully be adopting it for JBT 4.2.0.Beta1 (code freeze is March 20, by the way). Here's how to add the staging repo to the 4.2.0.Beta1 parent pom (or your root pom, if you prefer): https://github.com/nickboldt/jbosstools-build/commit/d5697b8cb57f0d355a0e... * If you apply the above commit locally, be sure that your root pom references the CORRECT VERSION of the parent pom (4.2.0.Beta1-SNAPSHOT, not 4.2.0.Alpha2-SNAPSHOT), and that you've built the parent pom locally. * If you add the staging <pluginRepository> to your own root pom to try it out, be sure to also set -DtychoVersion=0.20.0 via the commandline when building. Should you encounter any problems with Tycho 0.20.0, please report it here: https://issues.jboss.org/browse/JBIDE-16737 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 8 months

1
0
0 / 0

JBoss Tools Core 4.1.2.CR1 bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. JBoss Tools Target Platforms: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... (JBoss Tools - current release) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBoss Tools - upcoming milestone) (This is loaded automatically into Eclipse when installing JBoss Tools. Provided here simply for reference.) Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.2.CR1.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.2.CR1.coretests/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.2.CR1.webtools/ Builds: http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1.core/20... http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1.coretes... http://download.jboss.org/jbosstools/builds/development/4.1.2.CR1.webtool... JBoss Central: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep... (JBoss Central - current release) http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3... (JBoss Central - upcoming milestone) To test the upcoming version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.1.2.CR1/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.2.CR1/ -- New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 8 months

3
4
0 / 0

Does your code depend on Zest or GEF ?

by Mickael Istria

Hi all, I could notice target-platform currently contains a few features related to GEF and Zest. Is anyone actually using them or could we investigate removing them from the Target-platform? (some bundles would remain pulled transitively anyway). Cheers, -- 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>

10 years, 8 months

4
4
0 / 0

ACTION REQUIRED: JBT 4.1.2.CR1 / JBDS 7.1.1.CR1 build status

by Nick Boldt

The following issues block the release of CR1 to QE, due to incorrect parent pom reference in root pom: Server : https://issues.jboss.org/browse/JBIDE-16681 OpenShift : https://issues.jboss.org/browse/JBIDE-16683 LiveReload : https://issues.jboss.org/browse/JBIDE-16686 Please apply these PRs: https://github.com/jbosstools/jbosstools-server/pull/205 https://github.com/jbosstools/jbosstools-openshift/pull/364 https://github.com/jbosstools/jbosstools-livereload/pull/76 Then you can close the above JIRAs, and kick your jobs: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Mickael sent out an email on Thursday [1] reminding everyone to do the above, but as that process deviates from the usual task JIRA notification method, a few projects forgot / didn't see the email. [1] http://lists.jboss.org/pipermail/jbosstools-dev/2014-February/008612.html The result is that we won't have a build ready for QE by EOD tonight. ---- In addition to the above blocking issues, there are a few projects with test failures, including (but not limited to) these: Hibernate : https://issues.jboss.org/browse/JBIDE-16669 Webservices: : https://issues.jboss.org/browse/JBIDE-16670 These may in fact be configuration problems w/ the new "virt" slaves, but figured it was worth documenting the issues in case there's a larger problem here. Suspect we can solve this simply by excluding the "virt" slaves or by having the slaves fixed to include whatever is missing for running tests. If the test owners can speculate as to what's missing in the above JIRAs, that might help me communicate that to eng-ops in order to get the missing config added. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev March 2014