[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
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
1 month, 2 weeks
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM:
------------------------------------------------------------
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/
There are ways to achieve more-than-260-char paths, but do we want to?
was (Author: nickboldt):
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
> Align installation default path with installer filename
> -------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
2 months, 1 week
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2719:
-------------------------------------
[~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far.
First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet).
With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error.
In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {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
2 months, 1 week
[JBoss JIRA] (JBDS-3055) cannot install Arquillian into JBDS because of missing Sapphire dependency
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3055:
--------------------------------
Summary: cannot install Arquillian into JBDS because of missing Sapphire dependency
Key: JBDS-3055
URL: https://issues.jboss.org/browse/JBDS-3055
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: discovery
Affects Versions: 8.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
JBT TP contains org.eclipse.sapphire, because Arquillian depends on it.
JBDS TP does not.
So, when we create a TP for JBoss Central Early Access, it must include:
* Arquillian
** Sapphire + org.objectweb.asm
* AngularJS
** Tern.java
* VJET
Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1].
[1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 8 months
[JBoss JIRA] (JBDS-3055) cannot install Arquillian into JBDS because of missing Sapphire dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3055?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3055:
-----------------------------
Description:
JBT TP contains org.eclipse.sapphire, because Arquillian depends on it.
JBDS TP does not (it also lacks Tern).
So, when we create a TP for JBoss Central Early Access, it must include:
* Arquillian
** Sapphire + org.objectweb.asm
* AngularJS
** Tern.java
* VJET
Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1].
[1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
was:
JBT TP contains org.eclipse.sapphire, because Arquillian depends on it.
JBDS TP does not.
So, when we create a TP for JBoss Central Early Access, it must include:
* Arquillian
** Sapphire + org.objectweb.asm
* AngularJS
** Tern.java
* VJET
Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1].
[1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
> cannot install Arquillian into JBDS because of missing Sapphire dependency
> --------------------------------------------------------------------------
>
> Key: JBDS-3055
> URL: https://issues.jboss.org/browse/JBDS-3055
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: discovery
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> JBT TP contains org.eclipse.sapphire, because Arquillian depends on it.
> JBDS TP does not (it also lacks Tern).
> So, when we create a TP for JBoss Central Early Access, it must include:
> * Arquillian
> ** Sapphire + org.objectweb.asm
> * AngularJS
> ** Tern.java
> * VJET
> Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1].
> [1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 8 months
[JBoss JIRA] (JBIDE-17486) Label in jQuery Mobile Palette
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17486?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-17486:
-------------------------------------
I must have missed the Label in the HTML5 section - I will need to go back and look for it - currently traveling until Wed.
If the label would allow me to manipulate/replace the on-screen text that is really all that I am doing - I call it "debug" or "status" and throw up messages at various points in the code execution. Letting the user know that something is happening async/behind the scenes.
> Label in jQuery Mobile Palette
> ------------------------------
>
> Key: JBIDE-17486
> URL: https://issues.jboss.org/browse/JBIDE-17486
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta3
>
>
> Does jQuery Mobile offer a basic "label"? When I just want to replace the text programmatically?
> <div id="stuff"></div>
> $("#stuff").html("stuff is happening here"); // this based on button click
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 8 months
[JBoss JIRA] (JBIDE-17408) jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17408?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-17408 at 5/31/14 5:31 PM:
-------------------------------------------------------------
[~dgolovin] Isn't this something we ought to fix for Beta2, since it's trivial to do but will prevent incompatibility issues down the road? I expected to see a commit for this in master or Beta2x branch, but when the build respun last night it didn't pick up any changes. :(
New PR for master branch:
https://github.com/jbosstools/jbosstools-jst/pull/317
was (Author: nickboldt):
[~dgolovin] Isn't this something we ought to fix for Beta2, since it's trivial to do but will prevent incompatibility issues down the road? I expected to see a commit for this in master or Beta2x branch, but when the build respun last night it didn't pick up any changes. :(
> jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17408
> URL: https://issues.jboss.org/browse/JBIDE-17408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Beta3
>
>
> Max says (paraphrasing):
> "The JSDT stuff should be locked down so that it depends on a specific version of tern.java, not just any version. We want it so that users can only install the version of tern.java we include in our TP."
> Currently, this is 0.2.0.201405210810.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 8 months
[JBoss JIRA] (JBIDE-17470) Error when running imported cordova-cli project with CordovaSim
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17470?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-17470:
---------------------------------
Component/s: browsersim
> Error when running imported cordova-cli project with CordovaSim
> ---------------------------------------------------------------
>
> Key: JBIDE-17470
> URL: https://issues.jboss.org/browse/JBIDE-17470
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Fix For: 4.2.0.Beta3
>
>
> 1. Generate cordova project using cordova cli
> {noformat}
> cordova create hello com.example.hello HelloWorld
> {noformat}
> 2. Import created project to JBT
> 3. Run it with CordovaSim
> ERROR:
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-29 09:50:15.934
> !MESSAGE An internal error occurred during: "Launching HelloWorld".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getStartPageName(CordovaSimLaunchParametersUtil.java:258)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getDefaultStartPageFromConfigXml(CordovaSimLaunchParametersUtil.java:163)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getDefaultStartPage(CordovaSimLaunchParametersUtil.java:155)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:95)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> 4. Open Run configurations and select HelloWorld configuration
> ERROR:
> {noformat}
> !ENTRY org.eclipse.jface 4 2 2014-05-29 09:57:43.006
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getStartPageName(CordovaSimLaunchParametersUtil.java:258)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getDefaultStartPageFromConfigXml(CordovaSimLaunchParametersUtil.java:163)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchParametersUtil.getDefaultStartPage(CordovaSimLaunchParametersUtil.java:155)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationTab.setSelectedStartPage(CordovaSimLaunchConfigurationTab.java:498)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationTab.setSelectedProject(CordovaSimLaunchConfigurationTab.java:452)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationTab.initializeFrom(CordovaSimLaunchConfigurationTab.java:309)
> at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:90)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationTabGroup.initializeFrom(CordovaSimLaunchConfigurationTabGroup.java:28)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:201)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:764)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:635)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:652)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:613)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:588)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1217)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1243)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
> at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:611)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:619)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:552)
> at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:82)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3416)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 8 months