[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2394:
-----------------------------
Comment: was deleted
(was: PR 14 applied in 33x branch. Also bumped the plugin and its containing features to version 2.3.2.)
> CLONE - ESB projects cannot be deployed using Server Add/Remove
> ---------------------------------------------------------------
>
> Key: JBDS-2394
> URL: https://issues.jboss.org/browse/JBDS-2394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 5.0.2.GA
>
> Attachments: JBDS2394.patch.txt
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Robert (Bob) Brodt commented on JBIDE-11121:
--------------------------------------------
Thanks Mickael. I would like to try and do this myself to get a better understanding of what's going on here...
You can "teach a man to fish" and help me out here by filling in the holes in my understanding, indicated by <hole></hole> below...
So, I need to:
1. copy the file jbosstools-build/target-platforms/soatools-4.2.1.a/soa-extensions.target from your github repo to the BPEL and BPMN2 editor project <hole>which directories, project root only, or every plugin directory?</hole>
2. make the changes to the pom.xml in the BPEL and BPMN2 project roots as you described <hole>I will only be able to do this locally because I don't want to push these pom.xml changes to eclipse.org, right?</hole>
3. test the BPEL and BPMN2 editor builds using <hole>"mvn verify" and a bunch of other options, which are...?</hole>
4. attach the build log to this JIRA
FYI, the projects at eclipse are here:
https://git.eclipse.org/c/bpel/org.eclipse.bpel.git/
https://git.eclipse.org/c/bpmn2-modeler/org.eclipse.bpmn2-modeler.git/
The BPEL editor also has a required plugin which lives at github because it uses some JBoss libraries and therefore can't be included in the git.eclipse.org repo; that plugin is here:
https://github.com/jbosstools/jbosstools-bpel
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.x
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13297) Prevent from associating xml files to Android xml editor
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13297:
--------------------------------------
Summary: Prevent from associating xml files to Android xml editor
Key: JBIDE-13297
URL: https://issues.jboss.org/browse/JBIDE-13297
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: UpStream
Affects Versions: 4.0.0.Final
Reporter: Stefan Bunciak
Assignee: Max Rydahl Andersen
After installing the Android Development Tools into JBDS/JBT all xml files gets associated to Android Common Xml Editor, even pom.xml files which we used to open with the Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be fixed.
--
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
13 years, 4 months
[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2394:
----------------------------------
PR 14 applied in 33x branch. Also bumped the plugin and its containing features to version 2.3.2.
> CLONE - ESB projects cannot be deployed using Server Add/Remove
> ---------------------------------------------------------------
>
> Key: JBDS-2394
> URL: https://issues.jboss.org/browse/JBDS-2394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 5.0.2.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 4 months
[JBoss JIRA] (JBDS-2429) NullPointerException when closing JBDS 6.0 beta2
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2429?page=com.atlassian.jira.plugin.... ]
Snjezana Peco updated JBDS-2429:
--------------------------------
Fix Version/s: 6.1.0.Alpha1
> NullPointerException when closing JBDS 6.0 beta2
> ------------------------------------------------
>
> Key: JBDS-2429
> URL: https://issues.jboss.org/browse/JBDS-2429
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.Beta2
> Reporter: Itamar Heim
> Assignee: Snjezana Peco
> Fix For: 6.1.0.Alpha1
>
>
> downloaded and installed:
> jbdevstudio-product-universal-6.0.0.Beta2-v20121115-0009-B105.jar
> open jbds.
> agreed to send stats to redhat
> closed jbds
> got:
> SESSION 2012-12-07 14:03:30.380 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_22
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> !ENTRY org.eclipse.osgi 4 0 2012-12-07 14:25:56.679
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182)
> at org.eclipse.swt.widgets.Display.release(Display.java:3233)
> at org.eclipse.swt.graphics.Device.dispose(Device.java:248)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: java.lang.NullPointerException
> at org.eclipse.ui.internal.WorkbenchPartReference.subscribe(WorkbenchPartReference.java:209)
> at org.eclipse.ui.internal.WorkbenchPage.createEditorReferenceForPart(WorkbenchPage.java:972)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3078)
> at org.eclipse.ui.internal.WorkbenchPage.access$22(WorkbenchPage.java:3003)
> at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:2985)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2981)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2940)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2923)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:377)
> at org.jboss.tools.central.JBossCentralActivator$2$1.run(JBossCentralActivator.java:355)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 18 more
--
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
13 years, 4 months
[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-2394:
--------------------------------
Assignee: Nick Boldt (was: Rob Stryker)
> CLONE - ESB projects cannot be deployed using Server Add/Remove
> ---------------------------------------------------------------
>
> Key: JBDS-2394
> URL: https://issues.jboss.org/browse/JBDS-2394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 5.0.2.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 4 months
[JBoss JIRA] (JBDS-2429) NullPointerException when closing JBDS 6.0 beta2
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2429?page=com.atlassian.jira.plugin.... ]
Snjezana Peco updated JBDS-2429:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> NullPointerException when closing JBDS 6.0 beta2
> ------------------------------------------------
>
> Key: JBDS-2429
> URL: https://issues.jboss.org/browse/JBDS-2429
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.Beta2
> Reporter: Itamar Heim
> Assignee: Snjezana Peco
>
> downloaded and installed:
> jbdevstudio-product-universal-6.0.0.Beta2-v20121115-0009-B105.jar
> open jbds.
> agreed to send stats to redhat
> closed jbds
> got:
> SESSION 2012-12-07 14:03:30.380 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_22
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> !ENTRY org.eclipse.osgi 4 0 2012-12-07 14:25:56.679
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182)
> at org.eclipse.swt.widgets.Display.release(Display.java:3233)
> at org.eclipse.swt.graphics.Device.dispose(Device.java:248)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: java.lang.NullPointerException
> at org.eclipse.ui.internal.WorkbenchPartReference.subscribe(WorkbenchPartReference.java:209)
> at org.eclipse.ui.internal.WorkbenchPage.createEditorReferenceForPart(WorkbenchPage.java:972)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3078)
> at org.eclipse.ui.internal.WorkbenchPage.access$22(WorkbenchPage.java:3003)
> at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:2985)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2981)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2940)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2923)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:377)
> at org.jboss.tools.central.JBossCentralActivator$2$1.run(JBossCentralActivator.java:355)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 18 more
--
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
13 years, 4 months