April 2012 - jbosstools-dev - Jboss List Archives

JBoss Tools 3.3.0.M4 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. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4a/ http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4a.soa-too... http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4a.webtools/ Builds: http://download.jboss.org/jbosstools/builds/development/3.3.0.M4a/ http://download.jboss.org/jbosstools/builds/development/3.3.0.M4a.soa-too... http://download.jboss.org/jbosstools/builds/development/3.3.0.M4a.webtools/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

8 months

2
1
0 / 0

Branching for SOA tools Beta1

by Doug Palmer

Hi everyone I am planning on cutting a branch of https://anonsvn.jboss.org/repos/jbosstool/trunk for a JBDS SOA Tooling Beta1. Is there anything anyone urgently needs to commit before I branch? Regards Doug Douglas Palmer dpalmer(a)redhat.com JBoss, by Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson (USA), Charlie Peters (USA)

12 years, 6 months

3
3
0 / 0

Source lookup in maven component

by Max Andersen

Nick - forgot to mention snjezana will be adding sourcelookup to the maven component as a separate feature. If you spot something problematic dependency/build wise then let me know. /max (sent from my phone)

12 years, 6 months

7
19
0 / 0

Brainstorming: Target Platform for developers too

by Mickael Istria

Hi all, As you may know, we leverage Target Platform (TP) at build-time to set up a build path. A TP is basically a list of dependencies we allow for build to perform. TP are also usable at dev-time in PDE and guarantees what you can depend on when you write a plugin. For example, if you depend on something that is not part of your TP, you'll see some errors for unresolved bundles. The next step for this Target Platforms would the *you, developers, use these target platforms in PDE*. Then we would all ensure we depend on the same stuff at dev-time and build-time, and it would prevent some synchronization errors between what you require, and what the TP contain. You can use TP by importing them into your workspace (checkout build/target-platform folder), and then enable them with Window > Preferences > Plugin Development > Target Platform. We already identified some pitfalls with current TP, but we'll work on making them more usable for developers. Please report your ideas in JIRA on how to improve target platforms so that you could use them too. Here are some first ideas, please contribute to these ideas and raise new ones. https://issues.jboss.org/browse/JBIDE-11688 https://issues.jboss.org/browse/JBIDE-11689 https://issues.jboss.org/browse/JBIDE-11690 Thanks, -- 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>

12 years, 6 months

2
3
0 / 0

JBoss Tools Core 3.3.0.Beta3 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. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.core/ http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.webto... Builds: http://download.jboss.org/jbosstools/builds/development/3.3.0.Beta3.core/... http://download.jboss.org/jbosstools/builds/development/3.3.0.Beta3.webto... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.core/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: https://anonsvn.jboss.org/repos/jbosstools/trunk/documentation/whatsnew/i... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 6 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4765 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4765 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4765/ to view the results.

12 years, 6 months

1
2
0 / 0

Build Failures: No test report files were found

by Rob Cernich

Hey all, Recently, the SwitchYard tooling builds have started failing in the publish phase. Below is a summary of the error. The complete output can be found here: http://hudson.jboss.org/hudson/job/SwitchYard-Tools/65/console Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE Archiving artifacts Sending e-mails to: switchyard-dev(a)lists.jboss.org Build was marked for publishing on https://hudson.jboss.org/hudson/ Notifying upstream projects of job completion Finished: FAILURE Any ideas? Best, Rob

12 years, 6 months

2
2
0 / 0

JBoss Tools & Dev Studio are branched for Beta3

by Nick Boldt

Branches created: http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.0.Beta3/ http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.0.Beta3/ Jobs: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/ http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_3.3.indigo/ Note that we are *code frozen* for Beta3, which means only urgent fixes should be done in the branch, associated w/ a JIRA. Trunk remains open for new development work. Where applicable, please remember to commit changes in BOTH trunk and the new branch. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 6 months

2
2
0 / 0

jbosstools-3.3_stable_branch.aggregate - Build # 137 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_stable_branch.aggregate - Build # 137 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggreg... to view the results.

12 years, 6 months

1
3
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4752 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4752 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4752/ to view the results.

12 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev April 2012