[JBoss JIRA] (JBIDE-13965) Wrong datasource driver when EAP 6.1 server is present
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13965?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-13965:
--------------------------------------
Assignee: Rob Stryker
[~rob.stryker] please review the PR.
> Wrong datasource driver when EAP 6.1 server is present
> ------------------------------------------------------
>
> Key: JBIDE-13965
> URL: https://issues.jboss.org/browse/JBIDE-13965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Environment: JBDS 7.0.0.Alpha B135
> Seam 2.3.1.Final (WFK 2.2.0)
> EAP 6.1.0.ER4
> EAP 6.0.1.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
> Attachments: scr.png
>
>
> When you try to create a Seam Web Project, but have EAP 6.1 defined in the workspace (along with EAP 6.0.1 that I wanted to use for the seam project), the generated project has this in the ds.xml inside resources:
> <driver>jboss-eapnull</driver>
> Also, there is no driver jar in the resources folder.
> This is probably because both servers created their DefaultDS connection profile in Eclipse with the same name.
--
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, 10 months
[JBoss JIRA] (JBDS-2659) Installer should pick up JDK location when it is possible
by Denis Golovin (JIRA)
Denis Golovin created JBDS-2659:
-----------------------------------
Summary: Installer should pick up JDK location when it is possible
Key: JBDS-2659
URL: https://issues.jboss.org/browse/JBDS-2659
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 7.0.0.Beta1
Reporter: Denis Golovin
Assignee: Denis Golovin
When installer started with JDK like
{code}/path-to-jdk/bin/java installer.jar{code}
it is picking up JRE path as java location
{code}/path-to-jdk/jre{code}
where as it should use
{code}/path-to-jdk{code}
--
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, 10 months
[JBoss JIRA] (JBIDE-14821) NPE when creating EAP 6.1 runtime/server
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-14821:
--------------------------------------
Summary: NPE when creating EAP 6.1 runtime/server
Key: JBIDE-14821
URL: https://issues.jboss.org/browse/JBIDE-14821
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.0.Beta2
Reporter: Alexey Kazakov
{code}
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.setEffectiveBaseDir(XPathQuery.java:113)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.setCategory(XPathQuery.java:264)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathCategory.addQuery(XPathCategory.java:75)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.addQueriesToCategoryFromDefaultFile(XPathModel.java:340)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.loadDefaultPortQueries(XPathModel.java:313)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.handleAddJBossXPaths(XPathModel.java:98)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.access$1(XPathModel.java:97)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:84)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
--
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, 10 months
[JBoss JIRA] (JBIDE-14795) Subclipse as installed from JBoss Central does not include JavaHL
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14795?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-14795:
-------------------------------
Comment: was deleted
(was: [~maxandersen] If we want to override prefs via JBDS plugin_customization.ini, they would be some or all of these:
{code}
/instance/org.tigris.subversion.subclipse.ui/pref_svninterface=svnkit
/instance/org.tigris.subversion.subclipse.ui/pref_merge_provider=Default (Subclipse)
/instance/org.tigris.subversion.subclipse.ui/pref_use_javahl_commit_hack=false
/instance/org.tigris.subversion.subclipse.tools.usage/ask_user_for_usage_report_preference=false
{code}
)
> Subclipse as installed from JBoss Central does not include JavaHL
> -----------------------------------------------------------------
>
> Key: JBIDE-14795
> URL: https://issues.jboss.org/browse/JBIDE-14795
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
> Attachments: checkout-from-svn.png, no-svn-bad-svn-have-you-tried-svnkit.png, no-svn-bad-svn.png
>
>
> installed svn + mylyn and gets error on startup with respect to javahl working.
> "Failed to load JavaHL Library.
> These are the errors that were encountered:
> no libsvnjavahl-1 in java.library.path
> no svnjavahl-1 in java.library.path
> no svnjavahl in java.library.path
> java.library.path = /Users/max/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:."
--
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, 10 months
[JBoss JIRA] (JBIDE-14795) Subclipse as installed from JBoss Central does not include JavaHL
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14795?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-14795 at 6/10/13 5:35 PM:
-------------------------------------------------------------
Reopen to add these:
{code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/plugin_customization.ini}
org.tigris.subversion.subclipse.ui/pref_svninterface=svnkit
org.tigris.subversion.subclipse.ui/pref_merge_provider=Default (Subclipse)
org.tigris.subversion.subclipse.ui/pref_use_javahl_commit_hack=false{code}
Committed in master: https://github.com/jbdevstudio/jbdevstudio-product/commit/623b21dcdcba76a...
was (Author: nickboldt):
Reopen to consider adding these:
{code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/plugin_customization.ini}
org.tigris.subversion.subclipse.ui/pref_svninterface=svnkit
org.tigris.subversion.subclipse.ui/pref_merge_provider=Default (Subclipse)
org.tigris.subversion.subclipse.ui/pref_use_javahl_commit_hack=false{code}
> Subclipse as installed from JBoss Central does not include JavaHL
> -----------------------------------------------------------------
>
> Key: JBIDE-14795
> URL: https://issues.jboss.org/browse/JBIDE-14795
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
> Attachments: checkout-from-svn.png, no-svn-bad-svn-have-you-tried-svnkit.png, no-svn-bad-svn.png
>
>
> installed svn + mylyn and gets error on startup with respect to javahl working.
> "Failed to load JavaHL Library.
> These are the errors that were encountered:
> no libsvnjavahl-1 in java.library.path
> no svnjavahl-1 in java.library.path
> no svnjavahl in java.library.path
> java.library.path = /Users/max/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:."
--
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, 10 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2389 at 6/10/13 4:44 PM:
-----------------------------------------------------------
So... if you try to update JBDS from installer to a newer JBDS (rather than JBDS BYOE to newer), this happens:
{code}
An error occurred while installing the items
session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=[R]com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257 --> [R]com.jboss.jbds.all 7.0.0.Beta2-v20130610-1955, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
I/O Error while copying /home/nboldt/jbdevstudio-product-universal-7.0.0.Beta1-v20130529-0631-B257/studio/eclipse.ini - see details.
Source: /home/nboldt/jbdevstudio-product-universal-7.0.0.Beta1-v20130529-0631-B257/studio/eclipse.inidoes not exists
{code}
I've reverted the change above [1] and we'll have to try a custom touchpoint [2] if we want to fix this.
[1] https://github.com/jbdevstudio/jbdevstudio-product/commit/ca009c437b9905f...
[2] eclipsesource.com/blogs/2013/05/23/custom-touchpoints-in-p2/
was (Author: nickboldt):
So... if you try to update JBDS from installer to a newer JBDS (rather than JBDS BYOE to newer), this happens:
{code}
An error occurred while installing the items
session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=[R]com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257 --> [R]com.jboss.jbds.all 7.0.0.Beta2-v20130610-1955, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
I/O Error while copying /home/nboldt/jbdevstudio-product-universal-7.0.0.Beta1-v20130529-0631-B257/studio/eclipse.ini - see details.
Source: /home/nboldt/jbdevstudio-product-universal-7.0.0.Beta1-v20130529-0631-B257/studio/eclipse.inidoes not exists
{code}
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
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, 10 months
[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-14537:
------------------------------------
>From Eng Ops:
{quote}We've made the changes and webkitgtk should install on all RHEL6 slaves shortly
if it hasn't already.
Can you do some testing and verify you've got what you need on those hsots
please?{quote}
[~kmarmaliykov] ... back to you.
I've kicked this job, which should rebuild unchanged Beta1x branch code, this time only on webkit-enabled RHEL6:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_41/ >=70
I would also kick the master job, but it's red currently for an unrelated reason (JBIDE-14812, JBIDE-14817).
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/ >=374
> BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14537
> URL: https://issues.jboss.org/browse/JBIDE-14537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple...
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
> {code}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.SWT.error(SWT.java:4278)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36)
> at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
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, 10 months
