[JBoss JIRA] (JBIDE-11324) Features are missing Description
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-11324:
-----------------------------------
Summary: Features are missing Description
Key: JBIDE-11324
URL: https://issues.jboss.org/browse/JBIDE-11324
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.Beta1
Reporter: Vlado Pakan
Fix For: 3.3.0.Beta2
Features with Description containing only feature name:
JBoss ESB Tools
JBoss BPEL Editor
JBoss Maven CDI Configurator
JBoss Maven Hibernate Configurator
JBoss Maven JPA Configurator
JBoss Maven Project Examples
JBoss Runtime Drools Detector
JBoss Runtime ESB Detector
JBoss Runtime ESB Detector
The JBoss Tools for Savara.
JBoss Tools Common
JBoss Tools Common Text editing extensions
JBoss Tools Common UI
JBoss Tools Usage Reporting
JBoss Tools Verification
Smooks Tools
Feature JBoss Tools RichFaces has poor description "Visual editing"
--
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] Created: (JBIDE-8054) Text selection in VPE source pane is not synchronized with selection in Visual Pane
by Vlado Pakan (JIRA)
Text selection in VPE source pane is not synchronized with selection in Visual Pane
-----------------------------------------------------------------------------------
Key: JBIDE-8054
URL: https://issues.jboss.org/browse/JBIDE-8054
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.CR1
Environment: Linux 32bit JBDS 4.0.0.v201012161657N-H584-CR1
Reporter: Vlado Pakan
Assignee: Maxim Areshkau
Attachments: selectionError.swf
Steps to reproduce:
1. Open any jsp page in VPE editor and select some text in VPE source pane. The same text is selected in visual pane.
2. Make mouse left click somewhere in visual pane. There should be no selected text.
3. Select the same text in step 1. via source pane
4. No text is selected in visual pane but the same text selected in source pane has to be selected in visual pane.
After reopening jsp page it's working again as mentioned above. Selection is synchronized only first time.
See attached screencast.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[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] (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
[JBoss JIRA] (JBIDE-10707) Audit view cannot load log file
by Juraj Gargulak (JIRA)
Juraj Gargulak created JBIDE-10707:
--------------------------------------
Summary: Audit view cannot load log file
Key: JBIDE-10707
URL: https://issues.jboss.org/browse/JBIDE-10707
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: LATER
Reporter: Juraj Gargulak
Assignee: Kris Verlaenen
Audit view cannot load log file. Probably because of this exception:
!ENTRY org.drools.eclipse 4 120 2012-01-25 15:58:37.076
!MESSAGE Internal error in Drools Plugin:
!STACK 0
java.lang.NoClassDefFoundError: org/xmlpull/v1/XmlPullParserFactory
at com.thoughtworks.xstream.io.xml.XppDriver.createParser(XppDriver.java:57)
at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:58)
at com.thoughtworks.xstream.XStream.createObjectInputStream(XStream.java:1660)
at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:118)
at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:103)
at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:276)
at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061)
at org.eclipse.swt.dnd.DropTarget.drag_data_received(DropTarget.java:371)
at org.eclipse.swt.dnd.DropTarget.Drag_Data_Received(DropTarget.java:251)
at org.eclipse.swt.internal.gtk.OS._gtk_drag_get_data(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_drag_get_data(OS.java:6693)
at org.eclipse.swt.dnd.DropTarget.drag_drop(DropTarget.java:416)
at org.eclipse.swt.dnd.DropTarget.Drag_Drop(DropTarget.java:258)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207)
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)
After this exception audit view shows message "The selected audit log is empty." but the log file is not empty and it contains logged data.
--
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