eclipse-sig May 2015

eclipse-sig@lists.stg.fedoraproject.org

10 participants
36 discussions

[Bug 1196167] New: tycho-extras: One of setGitDir or setWorkTree must be called
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1196167 Bug ID: 1196167 Summary: tycho-extras: One of setGitDir or setWorkTree must be called Product: Fedora Version: rawhide Component: tycho-extras Assignee: rgrunber(a)redhat.com Reporter: mizdebsk(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, mizdebsk(a)redhat.com, rgrunber(a)redhat.com Description of problem: It looks like tycho-sourceref-jgit is not compatible with jgit used in Fedora. When trying to use tycho-sourceref-jgit from tycho-packaging-plugin, an IllegalArgumentException is thrown. Version-Release number of selected component (if applicable): 0.22.0-2 Reproducer: <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-packaging-plugin</artifactId> <version>${tycho-version}</version> <configuration> <format>yyyyMMdd-HHmm</format> <sourceReferences> <generate>true</generate> </sourceReferences> </configuration> <dependencies> <dependency> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-sourceref-jgit</artifactId> <version>${tycho-extras-version}</version> </dependency> </dependencies> </plugin> Result: Caused by: java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must be called. at org.eclipse.jgit.lib.BaseRepositoryBuilder.requireGitDirOrWorkTree(BaseRepositoryBuilder.java:587) at org.eclipse.jgit.lib.BaseRepositoryBuilder.setup(BaseRepositoryBuilder.java:554) at org.eclipse.jgit.storage.file.FileRepositoryBuilder.build(FileRepositoryBuilder.java:92) at org.eclipse.tycho.extras.sourceref.jgit.JGitSourceReferencesProvider.getSourceReferencesHeader(JGitSourceReferencesProvider.java:41) at org.eclipse.tycho.packaging.sourceref.SourceReferenceComputer.addSourceReferenceHeader(SourceReferenceComputer.java:50) at org.eclipse.tycho.packaging.PackagePluginMojo.updateManifest(PackagePluginMojo.java:253) at org.eclipse.tycho.packaging.PackagePluginMojo.createPluginJar(PackagePluginMojo.java:210) at org.eclipse.tycho.packaging.PackagePluginMojo.execute(PackagePluginMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=8c4LF9Q2iK&a=cc_unsubscribe

1 5

[Bug 1191547] New: eclipse: new Java project wizard hungs
by Red Hat Bugzilla 18 Aug '16

18 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1191547 Bug ID: 1191547 Summary: eclipse: new Java project wizard hungs Product: Fedora Version: rawhide Component: eclipse Assignee: akurtako(a)redhat.com Reporter: mizdebsk(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, msimacek(a)redhat.com, overholt(a)gmail.com, rgrunber(a)redhat.com, swagiaal(a)redhat.com Description of problem: I'm using latest Eclipse from rawhide. New Java project wizard hangs after clicking finish. Version-Release number of selected component (if applicable): 4.4.1-17.fc22.x86_64 How reproducible: 100% Steps to Reproduce: 1. install eclipse in minimal chroot 2. start eclipse 3. click file -> new -> Java project 4. type project name "foo" 5. click finish Actual results: Wizard appears to hang - it remains open, all SWT widgets are disabled (grayed). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xvbEQhz27A&a=cc_unsubscribe

1 4

[Bug 1197028] New: should not eclipse-dtp be pulling mysql-connector-java @install time or something else...
by Red Hat Bugzilla 19 Jul '16

19 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=1197028 Bug ID: 1197028 Summary: should not eclipse-dtp be pulling mysql-connector-java @install time or something else... Product: Fedora Version: 22 Component: eclipse-dtp Severity: medium Assignee: akurtako(a)redhat.com Reporter: peljasz(a)yahoo.co.uk QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, swagiaal(a)redhat.com Description of problem: that provides drivers? and if it could, mysql-connector-java-5.1.28-3.fc21.noarch.rpm provides/installs: /usr/share/java/mysql-connector-java.jar yet Eclipse looks for mysql-connector-java-5.1.0-bin.jar and errors, furthermore Eclipse does not detect/see this system-wide jar, user has to manually add it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=mmmjXD1W6X&a=cc_unsubscribe

1 2

[Bug 1202238] New: eclipse: Dropin cache not updated completely
by Red Hat Bugzilla 20 May '16

20 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1202238 Bug ID: 1202238 Summary: eclipse: Dropin cache not updated completely Product: Fedora Version: rawhide Component: eclipse Assignee: rgrunber(a)redhat.com Reporter: mizdebsk(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, msimacek(a)redhat.com, rgrunber(a)redhat.com, swagiaal(a)redhat.com Description of problem: It looks like Eclipse Mars is caching dropins in ~/.eclipse and not refreshing this cache entirely after dropin change (eg. package update). Version-Release number of selected component (if applicable): 4.5.0-0.4.git201503030800 Steps to Reproduce: 1. rm -rf ~/.eclipse 2. install eclipse-m2e-core-1.6.0-0.1.fc23.noarch 3. run eclipse -data /tmp/new-workspace 4. close eclipse after it starts 5. update m2e to eclipse-m2e-core-1.6.0-0.2.fc23.noarch 6. re-run eclipse -data /tmp/new-workspace Actual results: There are a lot of exceptions printed on stdout, such as: java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /usr/share/eclipse/dropins/m2e-core/eclipse/plugins/org.eclipse.m2e.scm_1.6.0.20150312-2022.jar These paths are refering to old m2e bundles from 1.6.0-0.1 which were removed during eclipse-m2e-core package update. Removing ~/.eclipse gets rid of these exceptions, so it looks like old paths are cached there. M2E works after update, so this is not critical. However accumulating warnings like that clutters Eclipse stdout and makes noticing real problems more difficult. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6eGilMjmu9&a=cc_unsubscribe

1 11

[Bug 1210898] New: Eclipse tries to use non-existent Mozilla (xulrunner) browser
by Red Hat Bugzilla 20 May '16

20 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1210898 Bug ID: 1210898 Summary: Eclipse tries to use non-existent Mozilla (xulrunner) browser Product: Fedora Version: 21 Component: eclipse Severity: high Priority: high Assignee: akurtako(a)redhat.com Reporter: rgrunber(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, msimacek(a)redhat.com, rgrunber(a)redhat.com, swagiaal(a)redhat.com It looks like the user has some jboss-tools plugins installed that ultimately try to bring up the browser. When it come sup, the user sees errors regarding missing libswt-xulrunner. The call would seem to originate from https://github.com/jbosstools/jbosstools-base/blob/master/runtime/plugins/o… . The other interesting part to note is that the BrowserFactory is returning the Mozilla class, which could only happen if WebKit.IsInstalled () is false. 11:31 < k170> I keep getting an error in eclipse (luna), every time I try to download and install a new server runtime. 11:33 < k170> The error states that it cannot find libswt-xulrunner-gtk.so 11:33 < k170> as well as libswt-xulrunner-gtk-4430.so 11:34 < k170> I'm running fedora 21 64bit and I have no idea how to install those files !ENTRY org.eclipse.ui 4 0 2015-04-09 21:52:39.606 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4430 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so Can't load library: /home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so ) at org.eclipse.swt.SWT.error(SWT.java:4467) at org.eclipse.swt.SWT.error(SWT.java:4356) at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2745) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:670) at org.eclipse.swt.browser.Browser.<init>(Browser.java:99) at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment.createComposite(DownloadRuntimeLicenseFragment.java:90) at org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizardPage.createControl(TaskWizardPage.java:44) at org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizard.createPageControls(TaskWizard.java:401) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:759) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:622) at org.eclipse.jface.window.Window.create(Window.java:435) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101) at org.eclipse.jface.window.Window.open(Window.java:797) at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHomeComposite$DownloadAndInstallListener.widgetSelected(DownloadRuntimeHomeComposite.java:75) 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:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526) at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:372) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2078) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5539) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668) 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:9106) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) 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:2477) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3407) at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) at org.eclipse.jface.window.Window.open(Window.java:808) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) 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:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) 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: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:497) 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) Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4430 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so Can't load library: /home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so at org.eclipse.swt.internal.Library.loadLibrary(Library.java:321) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:242) at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2743) ... 61 more -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Hc32FZ0PMz&a=cc_unsubscribe

1 21

[Bug 1226615] New: Quick Outline (Ctrl+O) doesn't work (Outline is closed immediately)
by Red Hat Bugzilla 15 Apr '16

15 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1226615 Bug ID: 1226615 Summary: Quick Outline (Ctrl+O) doesn't work (Outline is closed immediately) Product: Fedora Version: 22 Component: eclipse-cdt Assignee: jjohnstn(a)redhat.com Reporter: hedayatv(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com, rgrunber(a)redhat.com Description of problem: Eclipse in Fedora 22 has many problems (actually, mostly about its color theme which is unreadable/unnoticable in some places), but one of the most annoying ones is that the Quick Outline view (Ctrl+O) doesn't work. It does open the outline window, but it is closed immediately. Also, it has a black background while it was yellow (IIRC) in F21; but this is not that important. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C5gKD2cpuS&a=cc_unsubscribe

1 8

[Bug 1196736] New: eclipse gui white-unreadable text - changing colors too
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1196736 Bug ID: 1196736 Summary: eclipse gui white-unreadable text - changing colors too Product: Fedora Version: 22 Component: eclipse-pdt Severity: high Assignee: mat.booth(a)redhat.com Reporter: peljasz(a)yahoo.co.uk QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, mat.booth(a)redhat.com Created attachment 995677 --> https://bugzilla.redhat.com/attachment.cgi?id=995677&action=edit snapshot of white text Description of problem: please take a look a the attached snap, I'd happy it says more than if I tried to explain. Also, the yellow background of the second windows changes to black, is yellow only the first time is invoked, every subsequent invocation is black. The white text is most troublesome as you cannot see what is says, row that gets focus changes to white text. I thought it was configurable somewhere but failed to find settings if there are any. Version-Release number of selected component (if applicable): eclipse-emf-runtime-2.10.1-3.fc22.noarch eclipse-xsd-2.10.1-3.fc22.noarch eclipse-pdt-3.3.1-5.fc22.noarch eclipse-equinox-osgi-4.4.1-17.fc22.x86_64 eclipse-pde-4.4.1-17.fc22.x86_64 eclipse-gef-3.9.101-3.fc22.noarch eclipse-subclipse-1.10.5-2.fc22.noarch eclipse-jdt-4.4.1-17.fc22.x86_64 eclipse-webtools-common-core-3.6.2-1.fc22.noarch eclipse-dltk-5.1.0-6.fc22.noarch eclipse-webtools-sourceediting-3.6.2-1.fc22.noarch eclipse-rse-3.6.0-4.fc22.noarch eclipse-platform-4.4.1-17.fc22.x86_64 eclipse-webtools-servertools-core-3.6.2-1.fc22.noarch eclipse-webtools-common-3.6.2-1.fc22.noarch eclipse-filesystem-1.0-3.fc22.x86_64 eclipse-dltk-rse-5.1.0-6.fc22.noarch eclipse-swt-4.4.1-17.fc22.x86_64 eclipse-subclipse-graph-1.10.5-2.fc22.noarch eclipse-emf-core-2.10.1-3.fc22.x86_64 eclipse-mylyn-3.14.2-1.fc22.noarch eclipse-webtools-servertools-3.6.2-1.fc22.noarch eclipse-dltk-mylyn-5.1.0-6.fc22.noarch eclipse-ecf-core-3.9.2-2.fc22.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JkxqBUsj6O&a=cc_unsubscribe

1 12

[Bug 1222165] New: Xdebug step not working
by Red Hat Bugzilla 08 Dec '15

08 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1222165 Bug ID: 1222165 Summary: Xdebug step not working Product: Fedora Version: 22 Component: eclipse-pdt Assignee: mat.booth(a)redhat.com Reporter: dev002(a)pas-world.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, mat.booth(a)redhat.com Description of problem: Xdebug step not working Version-Release number of selected component (if applicable): eclipse-platform-4.4.2-5.fc22.x86_64 eclipse-pdt-3.3.1-5.fc22.noarch php-pecl-xdebug-2.3.2-1.fc22.x86_64 How reproducible: Steps to Reproduce: 1. Open PHP file 2. Configure Debug with Xdebug 3. Try step line to line 4. PDT window does not refresh the change of line. Actual results: Debug not working Expected results: Show line of debug step. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YQUSiccCDh&a=cc_unsubscribe

1 6

[Bug 1198217] New: Mouse scrolling doesn't work in editor windows
by Red Hat Bugzilla 31 Oct '15

31 Oct '15

https://bugzilla.redhat.com/show_bug.cgi?id=1198217 Bug ID: 1198217 Summary: Mouse scrolling doesn't work in editor windows Product: Fedora Version: 22 Component: eclipse-pydev Severity: high Assignee: akurtako(a)redhat.com Reporter: sgallagh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, nathaniel(a)natemccallum.com, overholt(a)gmail.com, swagiaal(a)redhat.com Description of problem: Mouse scrolling doesn't work in editor windows. I can mouse-scroll on the "Project Explorer" or "Outline" frames, but not in the main editor. It works properly on other languages, so it appears to be an issue specifically with eclipse-pydev. Version-Release number of selected component (if applicable): eclipse-pydev-3.7.1-2.fc22.noarch How reproducible: Every time Steps to Reproduce: 1. Open a python file in eclipse-pydev 2. Attempt to scroll using the mousewheel 3. Actual results: Nothing happens Expected results: The editor window should scroll. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=M5GIu6iAIm&a=cc_unsubscribe

1 17

[Bug 1217126] New: eclipse-emf does not build on ppc64/s390(x)
by Red Hat Bugzilla 30 Oct '15

30 Oct '15

https://bugzilla.redhat.com/show_bug.cgi?id=1217126 Bug ID: 1217126 Summary: eclipse-emf does not build on ppc64/s390(x) Product: Fedora Version: 22 Component: eclipse-emf Assignee: mat.booth(a)redhat.com Reporter: than(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, rgrunber(a)redhat.com rpmbuild --rebuild eclipse-emf-2.10.2-1.fc22.src.rpm has failed on ppc64/s390(x) looking at the build.log, the genericTargets.xml is searched in nonexistent directory /usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml build.log --------- BUILD FAILED /usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/build.xml:35: The following error occurred while executing this line: /usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/build.xml:91: The following error occurred while executing this line: /usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/templates/package-build/customTargets.xml:19: The following error occurred while executing this line: java.io.FileNotFoundException: /usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.<init>(FileInputStream.java:138) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:34) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:34) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:566) 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.ant.core.AntRunner.run(AntRunner.java:511) at org.eclipse.ant.core.AntRunner.start(AntRunner.java:607) 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:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) 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.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) at org.eclipse.core.launcher.Main.main(Main.java:34) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=rrGvoYD4YO&a=cc_unsubscribe

1 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig May 2015