[JBoss JIRA] Created: (GPD-199) org.jbpm.gd.jpdl plugin contains errors (possibly not up-to-date in CVS)
by John Ruud (JIRA)
org.jbpm.gd.jpdl plugin contains errors (possibly not up-to-date in CVS)
------------------------------------------------------------------------
Key: GPD-199
URL: http://jira.jboss.com/jira/browse/GPD-199
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM jPDL Designer 3.2.0.alpha1
Reporter: John Ruud
Assigned To: Koen Aers
Priority: Minor
I have loaded the latest org.jbpm.gd.common, org.jbpm.gd.pf, and org.jbpm.gd.jpdl plugins into my Eclipse workspace, but the org.jbpm.gd.jpdl project shows up in Eclipse as containing a number of errors.
According to the plugin manifests the plugins are all: 3.2.0.alpha1, and I loaded them from HEAD (for example: HEAD in jbpm.3/designer/jpdl/org.jbpm.gd.jpdl)
One problem is that dom4j class references are not resolved (due to the dom4j jar not being included in the .classpath file), but there are several other errors as well (for example I needed to add org.eclipse.jface.text as a required bundle).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBMETA-161) XmlValidationUnitTestCase.testValidation failed
by Jeff Zhang (JIRA)
XmlValidationUnitTestCase.testValidation failed
-----------------------------------------------
Key: JBMETA-161
URL: https://jira.jboss.org/jira/browse/JBMETA-161
Project: JBoss Metadata
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Jeff Zhang
Assignee: Alexey Loubyansky
Fix For: 1.0.0.GA
junit.framework.AssertionFailedError: Zero invalid files among total of 158 expected:<0> but was:<6>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.test.metadata.xml.XmlValidationUnitTestCase.testValidation(XmlValidationUnitTestCase.java:120)
....
Both failed on Hudson and local
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBPM-963) NullPointerException in the Eclipse plugin
by Oleksandr Alesinskyy (JIRA)
NullPointerException in the Eclipse plugin
------------------------------------------
Key: JBPM-963
URL: http://jira.jboss.com/jira/browse/JBPM-963
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM jPDL 3.2
Environment: WinXP SP2 Eclipse 3.2.1, JDK 1.5.0_11 and/or JDK 1.4.2_13
Reporter: Oleksandr Alesinskyy
Assigned To: Tom Baeyens
Hello,
I have downloaded and installed jBPM suite 3.2GA then I have installed Eclipse plugin from that suite into pre-existing Eclipse 3.2.1 (by copying contents of designer/eclipse directory to Eclipse extesions directory) and have created new JBoss JBPM Process project (with sample contents) - all succesfully. Then I have checked in the project into CVS. After this on Eclise restart comes message "Can not initialize JDT tooling" and following error stack:
java.lang.NullPointerException
at org.jbpm.ui.util.JbpmClasspathContainer.getJarNames(Unknown Source)
at org.jbpm.ui.util.JbpmClasspathContainer.createJbpmLibraryEntries(Unknown Source)
at org.jbpm.ui.util.JbpmClasspathContainer.getClasspathEntries(Unknown Source)
at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:494)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4119)
at org.jbpm.ui.util.JbpmClasspathContainerInitializer.initialize(Unknown Source)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4189)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize(JREContainerInitializer.java:57)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073)
at org.eclipse.jdt.internal.core.JavaModelManager.determineIfOnClasspath(JavaModelManager.java:808)
at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:697)
at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:626)
at org.eclipse.jdt.core.JavaCore.create(JavaCore.java:1383)
at org.eclipse.jdt.internal.ui.ResourceAdapterFactory.getAdapter(ResourceAdapterFactory.java:44)
at org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:63)
at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:256)
at org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:66)
at org.eclipse.jdt.internal.ui.filters.NamePatternFilter.select(NamePatternFilter.java:62)
at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.isFiltered(ProblemTreeViewer.java:187)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.isFiltered(PackageExplorerPart.java:301)
at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.isExpandable(ProblemTreeViewer.java:174)
at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:1900)
at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2487)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:754)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:731)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:705)
at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:892)
at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1288)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1323)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.preservingSelection(PackageExplorerPart.java:404)
at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1277)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:250)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1542)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.createPartControl(PackageExplorerPart.java:638)
at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:332)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:3915)
at org.eclipse.ui.internal.WorkbenchPage.restoreState(WorkbenchPage.java:2929)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1936)
at org.eclipse.ui.internal.Workbench.doRestoreState(Workbench.java:2857)
at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:2805)
at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1681)
at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:1421)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1679)
at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1650)
at org.eclipse.ui.internal.Workbench$17.run(Workbench.java:1529)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1473)
at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:702)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
and Eclipse package explorer becomes unavailable.
The same occurs if I install plugin on other computer and check-out the project and restart Eclipse. I#m still able to create another new jBPM Process project and work with it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months