[JBoss JIRA] (JBTIS-397) Missing source bundle for org.teiid.designer.webservice.lib
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-397?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-397:
----------------------------------
[~blafond] - the org.teiid.designer.webservice.lib.source is still missing - please take a look. thkx
> Missing source bundle for org.teiid.designer.webservice.lib
> -----------------------------------------------------------
>
> Key: JBTIS-397
> URL: https://issues.jboss.org/browse/JBTIS-397
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Priority: Minor
>
> Source bundle for org.teiid.designer.webservice.lib is missing in JBDS-IS 8.0.0.CR3. Notice that this bundle contains only two classes
> * org/teiid/designer/webservice/lib/WebServiceLibPlugin.class
> * org/teiid/designer/webservice/lib/WebServiceLibConstants.class
> so I set the priority as minor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-19178:
-------------------------------------------
{quote}
One way to make this nicer could be to have a way to hide/show a properties view inside a view - basically a "slide-in" that behaves exactly like a properties view but only react to selections within the view.
{quote}
+1 Sounds like a good idea. Definitely better than the current behavior. I understand that one can always configure your own views were things are arranged a bit better, but for me using Eclipse the first time for a long time again w/o any pre-configuration, it was a bit confusing how the server and properties were arranged in relation to each other.
> Explorer, Servers view: Add logical view to OpenShift v3 explorer
> -----------------------------------------------------------------
>
> Key: JBIDE-19178
> URL: https://issues.jboss.org/browse/JBIDE-19178
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
> Fix For: 4.3.x
>
> Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png
>
>
> Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21012:
---------------------------------------------
huh ? the fail to nexus for freemarker was because of a bad/missing version bumping according to https://issues.jboss.org/browse/JBIDE-20908 - and I seriously hope that was not fixed by doing something like 1.5.151-SNAPSHOT.
That would be wrong.
None of our other version issue detectors catched that missing bump afaik ?
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19081:
---------------------------------------------
Yes please. The item outstanding is the same as before - check that before and after this change is made we don't end up with running the same tests multiple times.
> Use simpler Surefire include/exclude pattern in parent pom
> ----------------------------------------------------------
>
> Key: JBIDE-19081
> URL: https://issues.jboss.org/browse/JBIDE-19081
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.4.x
>
>
> 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude:
> {code}
> include = *Test*, *Test, *TestCase
> exclude = *Abstract*
> {code}
> 2. If that causes test failures because running incorrectly named
> abstract stuff, they can refactor, add their own root pom overrides, use
> a TestSuite, or use @Ignore in test classes.
> 3. If the count of tests run suddenly DROPS because the pattern isn't
> running the correct # of tests, they can add their own root pom
> overrides, or use a TestSuite.
> Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 / 9.1.0
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3562:
-------------------------------------------
[~nickboldt] no, those statements do not state opposite things.
I'm stating that there are no known vulnerability to exploit in Eclipse that makes it critical for us to release updated plugins.
That Eclipse.org in jpa and m2e is preparing to have fixes into Mars.2 just to be on the safe side is not in any way on its own an indication that Eclipse is vulnerable. And for sure it means that we can't actually include their bits in the release - it will only be in the actual installer, not for those installing jboss tools or devstudio from the updatesite.
Thus why I ask why we are spending time on discussing updating of TP's etc. if the only thing we for now know we need and can do is update the Installer ?
> Prepare for 9.0.1 / 9.1.0
> --------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.1.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.1.GA
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3538) read timeouts accessing JBDS discovery bits (possible Akamai problem?)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3538?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-3538.
----------------------------
No issue with read timeouts was reported for quite some time. Closing.
> read timeouts accessing JBDS discovery bits (possible Akamai problem?)
> ----------------------------------------------------------------------
>
> Key: JBDS-3538
> URL: https://issues.jboss.org/browse/JBDS-3538
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, discovery, updatesite
> Affects Versions: 9.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.0.0.GA
>
>
> As reported in JBDS-3525:
> {code}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:19.289
> !MESSAGE Cannot download bundle at
> https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.0...:
> Read timed out
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> at java.net.SocketInputStream.read(SocketInputStream.java:170)
> at java.net.SocketInputStream.read(SocketInputStream.java:141)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
> at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:593)
> at sun.security.ssl.InputRecord.read(InputRecord.java:532)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:198)
> at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178)
> at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137)
> at java.io.FilterInputStream.read(FilterInputStream.java:133)
> at java.io.FilterInputStream.read(FilterInputStream.java:107)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-10-08 09:40:29.700
> !MESSAGE Unexpected error
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> ... 8 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> ... 13 more{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-20070.
-----------------------------------
I agree, the user story is fixed by new workflow. (JBT nightly from 22nd Nov)
> Fix minor issues in RedDeer import
> ----------------------------------
>
> Key: JBIDE-20070
> URL: https://issues.jboss.org/browse/JBIDE-20070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: dialog.png
>
>
> When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not).
> List of minor issues:
> - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there
> - features has listed "Maven" but plugins and tests have "Maven, Java"
> - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Deprecate BIRT
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21105:
---------------------------------------------
Any reason why we should keep maintaining this ? Will it work with new versions of hibernate ?
How about asking on birt-dev if anyone even still interested and would like to take over ?
Seems all this time spent on making it built could be postponed until we actually know for sure we want/need it included.
> Deprecate BIRT
> --------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
> *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21044) Error when trying to import Thym or JS project
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21044?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova updated JBIDE-21044:
------------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Error when trying to import Thym or JS project
> ----------------------------------------------
>
> Key: JBIDE-21044
> URL: https://issues.jboss.org/browse/JBIDE-21044
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, easymport, target-platform
> Affects Versions: 4.3.1.Beta1
> Environment: Nightly jboss-devstudio-9.0.1.Beta1-v20151101-1911-B132 with Hybrid mobile tools installed
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.1.Beta1
>
>
> When I try to import the kitchensink-cordova example for the 2nd time, an error occurs and the following error is logged.
> {code}
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:478)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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:173)
> at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.lang.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> ... 72 more
> Root exception:
> java.lang.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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:173)
> at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months