[Bug 1196167] New: tycho-extras: One of setGitDir or setWorkTree must be called
by Red Hat Bugzilla
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
7 years, 4 months
[Bug 1191547] New: eclipse: new Java project wizard hungs
by Red Hat Bugzilla
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
7 years, 8 months
[Bug 1197028] New: should not eclipse-dtp be pulling mysql-connector-java @install time or something else...
by Red Hat Bugzilla
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
7 years, 9 months
[Bug 1202238] New: eclipse: Dropin cache not updated completely
by Red Hat Bugzilla
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
7 years, 11 months
[Bug 1196736] New: eclipse gui white-unreadable text - changing colors too
by Red Hat Bugzilla
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
8 years, 1 month
[Bug 1198217] New: Mouse scrolling doesn't work in editor windows
by Red Hat Bugzilla
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
8 years, 5 months
eclipse/secure-boot channel in fedora koji and ssds
by Kevin Fenzi
Greetings.
Just as a FYI:
The arm04-builder00 to arm04-builder07 arm builders now have ssd's in
them instead of spinning disks.
I have setup things so kernel/secure-boot and eclipse channel
(eclipse/gcc) go to these arm builders.
It likely won't be any kind of vast improvement, but it should
hopefully make builds faster for you folks.
Please let us know if you run into any issues with them.
kevin
8 years, 7 months
[Bug 1197661] New: eclipse's editor smudges on scrolling
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1197661
Bug ID: 1197661
Summary: eclipse's editor smudges on scrolling
Product: Fedora
Version: 22
Component: eclipse
Severity: high
Assignee: akurtako(a)redhat.com
Reporter: peljasz(a)yahoo.co.uk
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
Created attachment 997017
--> https://bugzilla.redhat.com/attachment.cgi?id=997017&action=edit
smudged editor
Description of problem:
sometimes editor gets smudged after scrolling, I have to click to get focus
back to editor for the smudges to refresh and dissapear.
Version-Release number of selected component (if applicable):
eclipse-platform-4.4.1-17.fc22.x86_64
mesa-dri-drivers-10.5.0-1.20150218.fc22.x86_64
mesa-filesystem-10.5.0-1.20150218.fc22.x86_64
mesa-libEGL-10.5.0-1.20150218.fc22.i686
mesa-libEGL-10.5.0-1.20150218.fc22.x86_64
mesa-libEGL-devel-10.5.0-1.20150218.fc22.x86_64
mesa-libgbm-10.5.0-1.20150218.fc22.i686
mesa-libgbm-10.5.0-1.20150218.fc22.x86_64
mesa-libGL-10.5.0-1.20150218.fc22.i686
mesa-libGL-10.5.0-1.20150218.fc22.x86_64
mesa-libglapi-10.5.0-1.20150218.fc22.i686
mesa-libglapi-10.5.0-1.20150218.fc22.x86_64
mesa-libGL-devel-10.5.0-1.20150218.fc22.x86_64
mesa-libGLES-10.5.0-1.20150218.fc22.x86_64
mesa-libGLU-9.0.0-7.fc22.x86_64
mesa-libGLU-devel-9.0.0-7.fc22.x86_64
mesa-libOpenCL-10.5.0-1.20150218.fc22.x86_64
mesa-libwayland-egl-10.5.0-1.20150218.fc22.x86_64
mesa-libxatracker-10.5.0-1.20150218.fc22.x86_64
mesa-vdpau-drivers-10.5.0-1.20150218.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=NEOvsxUz2o&a=cc_unsubscribe
8 years, 7 months
[Bug 1206893] New: Binary blobs in upstram tarball we build from
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1206893
Bug ID: 1206893
Summary: Binary blobs in upstram tarball we build from
Product: Fedora
Version: rawhide
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: praiskup(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
I can see that output of the following command is not empty:
tar tf R4_platform-aggregator-I20150317-2000.tar.xz \
| grep -e \\.jar$ -e \\.njar$
Do you think that we could call something like:
find -delete -name '*.jar' -o -name '*.njar' -o -name '*.class'
.. somewhere early in %prep phase, as soon as the tarballs are extracted?
That would kind of work-around our guarantees that we don't build from hacked
binary blobs.
I was unable to check whether those binary files are actually used
because the eclipse package fails to build in my mock profile even if I do not
edit it. However, if those actually are used - it would be probably serious
packaging problem against our Java PG.
(background story: I tried to resolve similar problems in my package and I
picked eclipse randomly as typical java package I should learn from, but
found similar issues)
Pavel
--
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=PrN4W1NzXm&a=cc_unsubscribe
8 years, 8 months
[Bug 1188412] New: Debugging with variable inspection view crashes frequently
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1188412
Bug ID: 1188412
Summary: Debugging with variable inspection view crashes
frequently
Product: Fedora
Version: 20
Component: eclipse
Severity: high
Assignee: akurtako(a)redhat.com
Reporter: rgasch(a)gmail.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
Created attachment 987225
--> https://bugzilla.redhat.com/attachment.cgi?id=987225&action=edit
Debug log file produced by eclipse
Description of problem: If you debug a Java program using eclipse and open the
variable inspection view (Alt-Shift-Q and then "v") Eclipse periodically hangs
and then crashes.
Version-Release number of selected component (if applicable):
Eclipse Version: 4.3.2
Build id: 3fc20
How reproducible: see above. This typically happens when the program is stopped
at a breakpoint and the variable inspection view is open. It does not happen
all the time, but happens intermittedly.
Steps to Reproduce:
1. Set breakpoint in java program
2. Start debug session
3. When breakpoint is reached, open the variable inspection view (Alt-Shift-Q
and then "v")
4. Continue stepping through the program. Sometimes this works for a given
session and then 1 or 2 sessions down the road it crashes.
Actual results: Eclipse crashes
Expected results: It should just work.
Additional info: Please see attached log file which points towards C
[libgtk-x11-2.0.so.0+0x256e92] gtk_tree_view_get_background_area+0xb2 as being
the source fo the problem.
--
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=Mj68I7xXJX&a=cc_unsubscribe
8 years, 9 months
