December 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-229) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-229: -------------------------------- Summary: Please update target platform dependencies to .Final Key: JBTIS-229 URL: https://issues.jboss.org/browse/JBTIS-229 Project: JBoss Tools Integration Stack Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ESB Affects Versions: 7.0.0.Final-JBDSIS Reporter: Paul Leacu Assignee: Brian Fitzpatrick Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-228) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-228: -------------------------------- Summary: Please update target platform dependencies to .Final Key: JBTIS-228 URL: https://issues.jboss.org/browse/JBTIS-228 Project: JBoss Tools Integration Stack Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools/ jBPM Affects Versions: 7.0.0.Final-JBDSIS Reporter: Paul Leacu Assignee: Kris Verlaenen Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-227) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-227?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-227: ----------------------------- Description: Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-227 > URL: https://issues.jboss.org/browse/JBTIS-227 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-227) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-227: -------------------------------- Summary: Please update target platform dependencies to .Final Key: JBTIS-227 URL: https://issues.jboss.org/browse/JBTIS-227 Project: JBoss Tools Integration Stack Issue Type: Sub-task Security Level: Public (Everyone can see) Components: BPEL Affects Versions: 7.0.0.Final-JBDSIS Reporter: Paul Leacu Assignee: Robert (Bob) Brodt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-226) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-226?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-226: ----------------------------- Description: Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! was: Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS and JBDS core so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-226 > URL: https://issues.jboss.org/browse/JBTIS-226 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, switchyard, teiid > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Paul Leacu > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-226) Please update target platform dependencies to .Final

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-226?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-226: ----------------------------------------- Hi there, I'm out of the office for the holidays, but will be back at my desk on Wednesday January 8th. Please drop me an e-mail and I'll get back to you as soon as I can. --Fitz > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-226 > URL: https://issues.jboss.org/browse/JBTIS-226 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, switchyard, teiid > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Paul Leacu > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS and JBDS core so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-226) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-226: -------------------------------- Summary: Please update target platform dependencies to .Final Key: JBTIS-226 URL: https://issues.jboss.org/browse/JBTIS-226 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, switchyard, teiid Affects Versions: 7.0.0.Final-JBDSIS Reporter: Paul Leacu Assignee: Paul Leacu Please respin your component to include JBTIS TP 4.1.5.Final On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS and JBDS core so we: 1. Know as early as possible is the .Final broke anyone 2. Establish a stable TP for subsequent kepler releases This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-2862: ------------------------------ Attachment: 2013-12-19_1512.png I am missing the New Folder option as well - see attached screenshot > During install, I should be able to create a new directory to install into > -------------------------------------------------------------------------- > > Key: JBDS-2862 > URL: https://issues.jboss.org/browse/JBDS-2862 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.CR1 > Environment: Mac OS X > Reporter: Jim Tyrrell > Assignee: Denis Golovin > Fix For: 7.1.1.GA, 8.0.0.Alpha2 > > Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png > > > See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-225) Respin bpmn2 modeler 1.0.1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-225?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-225. ------------------------------ Resolution: Done done > Respin bpmn2 modeler 1.0.1 > -------------------------- > > Key: JBTIS-225 > URL: https://issues.jboss.org/browse/JBTIS-225 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPMN2, distribution, target-platform > Affects Versions: 4.1.3.CR1, 4.1.5.CR1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > Can you please do another refresh of the JBTIS mirror from here [2] > This fixes the following BZs: > Bug 423809: BPMN2 diagram not displayed if location missing from import element > Bug 423638: Can't see the name of tasks dragged into expanded sub-process > Bug 423426: Cannot add interfaces and datatype/message/error/... > Bug 423752: Import interface to process generates an XML which cannot be parsed > [2] http://download.eclipse.org/bpmn2-modeler/updates/kepler/1.0.1/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-12109: ------------------------------------- [~rob.stryker] [~maxandersen] This seems to be outdated > JMX connection to AS7/EAP6 not working if server started with Java 1.7 > ---------------------------------------------------------------------- > > Key: JBIDE-12109 > URL: https://issues.jboss.org/browse/JBIDE-12109 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar > Mac OS X 10.7 Lion > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.x > > > When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897 > !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1 > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > ... 6 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897 > !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > !STACK 0 > java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > This has several consequences: > - server cannot be connected in MBean Explorer > - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below) > - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully > Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013