[JBoss JIRA] (JBDS-1990) Build JBDS product w/ Tycho?
by Nick Boldt (JIRA)
Nick Boldt created JBDS-1990:
--------------------------------
Summary: Build JBDS product w/ Tycho?
Key: JBDS-1990
URL: https://issues.jboss.org/browse/JBDS-1990
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build, P2 Enabled Product
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 5.0.0.Beta1
I've managed to get Tycho to build the p2 product using a new pom file [1] (which first regenerates the update site locally THEN builds the products for 4 or the 6 supported platforms (suspect I have to just add more platforms to the parent pom to get win64 and carbon64 in there) and a couple minor tweaks to product/features/com.jboss.jbds/pom.xml file.
However, while building, I get some errors:
{code}
java.io.FileNotFoundException: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/features/com.jboss.jbds/target/products/com.jboss.jbds.all/macosx/JBDevStudio.icns (No such file or directory)
Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9043279577960813921/launcher.exe using /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/features/com.jboss.jbds/target/products/com.jboss.jbds.all/jbds.ico
{code}
And, the resulting product can't launch (I only tried the lin64 one):
{code}
!ENTRY org.eclipse.osgi 4 0 2012-01-11 13:46:58.598
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
{code}
Any idea what's wrong here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBDS-2206) Non-intuitive - selecting SOA and "Data Services Tooling" only installs plugins assigned a category
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2206:
----------------------------------
Summary: Non-intuitive - selecting SOA and "Data Services Tooling" only installs plugins assigned a category
Key: JBDS-2206
URL: https://issues.jboss.org/browse/JBDS-2206
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Tooling / Platform
Affects Versions: 5.0.0.Beta3-SOA
Environment: SOA - http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa...
Version: 5.0.0.CR1
Build id: v20120605-2229-H183-CR1
Build date: 20120605-2229
Reporter: Len DiMaggio
Assignee: Nick Boldt
Fix For: 5.0.0.CR1-SOA
Intuitively, I would have expected that specifying "SOA and Data Services Tooling" would have selected all related plugins, whether or not they were assigned a category.
If the "Group Items by Category" option is selected, and the "SOA and Data Services Tooling" selection is chosen, then only the (14) plugins marked with * below are selected. The other plugins are only displayed if the "Group Items by Category" option is not selected.
BPEL Commons 1.0.0.v20120518-1552-H175-CI
* BPEL Editor 1.1.0.v20120606-2044-H7-Beta3-SOA
BPEL Visual Designer 1.0.0.v20120518-1552-H175-CI
Graphical Editing Framework Draw2d 3.7.2.v20110927-2020-4617w3122212803131
Graphical Editing Framework Zest Visualization Toolkit 1.3.0.v20110425-2050-67A18yF6F18CBD5A7N54242
JBoss Developer Studio - Central Discovery - SOA Tooling 1.0.0.v20120606-2044-H7-Beta3-SOA
* JBoss Drools Core 5.3.2.201206060351
JBoss Drools Guvnor 5.3.2.201206060351
* JBoss Drools Task 5.3.2.201206060351
* JBoss ESB Tools 1.5.0.v20120606-1401-H7-Beta3-SOA
JBoss jBPM Core 5.3.2.201206060351
JBoss jBPM Task 5.3.2.201206060351
* JBoss Runtime Drools Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
* JBoss Runtime ESB Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
* JBoss Runtime jBPM Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
jBPM 3 Tools Commons 4.4.0.v20120606-1036-H4-Beta3-SOA
* jBPM 3 Tools Runtime 3.2.1.v20120606-1036-H4-Beta3-SOA
* jBPM Convert 1.0.0.v20120606-1036-H4-Beta3-SOA
jBPM jPDL Tools 3.2.1.v20120606-1036-H4-Beta3-SOA
* ModeShape JCR REST Tools for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA
* ModeShape Tools JCR CND Editor for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA
Runtime Adapter for Apache ODE 1.3 1.0.0.v20120518-1552-H175-CI
* Teiid DataTools Connectivity 7.7.1.v20120606-1010-H8-Beta3-SOA
* Teiid Designer 7.7.1.v20120606-1010-H8-Beta3-SOA
* Teiid Designer Runtime 7.7.1.v20120606-1010-H8-Beta3-SOA
UML2 End-User Features 3.2.1.v201109082252
-----------------------
Similar situation for "Business Rules Tooling"
BPEL Commons 1.0.0.v20120518-1552-H175-CI
BPEL Editor 1.1.0.v20120606-2044-H7-Beta3-SOA
BPEL Visual Designer 1.0.0.v20120518-1552-H175-CI
Graphical Editing Framework Draw2d 3.7.2.v20110927-2020-4617w3122212803131
Graphical Editing Framework Zest Visualization Toolkit 1.3.0.v20110425-2050-67A18yF6F18CBD5A7N54242
JBoss Developer Studio - Central Discovery - SOA Tooling 1.0.0.v20120606-2044-H7-Beta3-SOA
* JBoss Drools Core 5.3.2.201206060351
* JBoss Drools Guvnor 5.3.2.201206060351
* JBoss Drools Task 5.3.2.201206060351
JBoss ESB Tools 1.5.0.v20120606-1401-H7-Beta3-SOA
* JBoss jBPM Core 5.3.2.201206060351
* JBoss jBPM Task 5.3.2.201206060351
* JBoss Runtime Drools Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
JBoss Runtime ESB Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
* JBoss Runtime jBPM Detector 1.3.0.v20120606-1603-H4-Beta3-SOA
jBPM 3 Tools Commons 4.4.0.v20120606-1036-H4-Beta3-SOA
jBPM 3 Tools Runtime 3.2.1.v20120606-1036-H4-Beta3-SOA
jBPM Convert 1.0.0.v20120606-1036-H4-Beta3-SOA
jBPM jPDL Tools 3.2.1.v20120606-1036-H4-Beta3-SOA
ModeShape JCR REST Tools for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA
ModeShape Tools JCR CND Editor for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA
Runtime Adapter for Apache ODE 1.3 1.0.0.v20120518-1552-H175-CI
Teiid DataTools Connectivity 7.7.1.v20120606-1010-H8-Beta3-SOA
Teiid Designer 7.7.1.v20120606-1010-H8-Beta3-SOA
Teiid Designer Runtime 7.7.1.v20120606-1010-H8-Beta3-SOA
UML2 End-User Features 3.2.1.v201109082252
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-10495) Define how BPEL users handle JBoss BPEL migration
by Max Rydahl Andersen (Created) (JIRA)
Define how BPEL users handle JBoss BPEL migration
-------------------------------------------------
Key: JBIDE-10495
URL: https://issues.jboss.org/browse/JBIDE-10495
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: BPEL
Reporter: Max Rydahl Andersen
Assignee: Robert (Bob) Brodt
Priority: Blocker
Fix For: 3.3.0.Beta1
JBDS-1909 is talking about keeping the old way of creating JBoss Legacy BPEL projects without outlining how migration works
and which packaging approach is used.
I want to be aligned on what this migration means:
It seems we will have:
2 different facets old jboss and new bpel
2 different packaging - one using WTP style packaging that is compatible with JBoss AS adapters (old jboss) and one using non-WTP style packing which is not compatible with anything but specific tomcat server adapter (new jboss)
2 different wizards for creating projects
And could we please not keep old packaging styles around if we could just migrate them over one way or the other.
And please let us not make *another* deployment/packaging approach.
I hope i'm wrong in the above observations so please let us once and for all document what the migration plan is and what reality we have ;)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-10681) Opening Agenda view throws DebugException
by Juraj Gargulak (JIRA)
Juraj Gargulak created JBIDE-10681:
--------------------------------------
Summary: Opening Agenda view throws DebugException
Key: JBIDE-10681
URL: https://issues.jboss.org/browse/JBIDE-10681
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: LATER
Reporter: Juraj Gargulak
Assignee: Kris Verlaenen
Priority: Minor
DebugException is thrown when Agenda view change focus while debugging:
!ENTRY org.drools.eclipse 4 120 2012-01-20 16:38:52.473
!MESSAGE Internal error in Drools Plugin:
!STACK 1
org.eclipse.debug.core.DebugException: Error when compiling snippet return getAgenda().getFocus();: The method getFocus() is undefined for the type Agenda
at org.drools.eclipse.debug.DebugUtil$EvaluationBlock.evaluate(DebugUtil.java:194)
at org.drools.eclipse.debug.DebugUtil.getValueByExpression(DebugUtil.java:116)
at org.drools.eclipse.debug.AgendaViewContentProvider.getAgendaElements(AgendaViewContentProvider.java:86)
at org.drools.eclipse.debug.AgendaViewContentProvider.getChildren(AgendaViewContentProvider.java:54)
at org.drools.eclipse.debug.DroolsDebugViewContentProvider.getElements(DroolsDebugViewContentProvider.java:52)
at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1010)
at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:703)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1336)
at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:605)
at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2622)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908)
at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1826)
at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1508)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465)
at org.drools.eclipse.debug.actions.ShowLogicalStructureAction$1.run(ShowLogicalStructureAction.java:55)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.drools.eclipse.debug.actions.ShowLogicalStructureAction.valueChanged(ShowLogicalStructureAction.java:53)
at org.drools.eclipse.debug.actions.ShowLogicalStructureAction.run(ShowLogicalStructureAction.java:45)
at org.eclipse.debug.ui.AbstractDebugView$3.run(AbstractDebugView.java:612)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
!SUBENTRY 1 org.drools.eclipse 4 120 2012-01-20 16:38:52.474
!MESSAGE Error when compiling snippet return getAgenda().getFocus();: The method getFocus() is undefined for the type Agenda
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months