[Bug 824313] New: snakeyaml - FTBFS
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=824313
Bug ID: 824313
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 17
Priority: unspecified
CC: java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com, mmorsi(a)redhat.com
Assignee: jcapik(a)redhat.com
Summary: snakeyaml - FTBFS
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: mizdebsk(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: snakeyaml
Product: Fedora
Created attachment 586282
--> https://bugzilla.redhat.com/attachment.cgi?id=586282&action=edit
Patch fixing the problem
Description of problem:
snakeyaml fails to build from source
Version-Release number of selected component (if applicable):
1.9-1
How reproducible:
Always.
Steps to Reproduce:
1. build on koji
Actual results:
fails to build
How to resolve:
1) apply attached patch
or
2) merge f17 with master:
git checkout f17
git merge master -Xtheirs
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 4 months
[Bug 842620] New: tomcat - compile with -target 1.5 or greater
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=842620
Bug ID: 842620
QA Contact: extras-qa(a)fedoraproject.org
Severity: medium
Version: rawhide
Priority: medium
CC: akurtako(a)redhat.com, ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com
Assignee: ivan.afonichev(a)gmail.com
Summary: tomcat - compile with -target 1.5 or greater
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: mizdebsk(a)redhat.com
Type: ---
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: tomcat
Product: Fedora
Package tomcat appears to be using Java generics,
but generates class files in format older than 49.0,
which corresponds to J2SE 5.0, in which generics were introduced.
Please update this package to generate classes in format 49.0 or
above. This corresponds to -target 1.5 option of javac (or ecj).
For more information, see bug #842394
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 4 months
[Bug 820119] New: tomcat-lib: Bundled library
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: tomcat-lib: Bundled library
https://bugzilla.redhat.com/show_bug.cgi?id=820119
Summary: tomcat-lib: Bundled library
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: tomcat
AssignedTo: ivan.afonichev(a)gmail.com
ReportedBy: mizdebsk(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
ivan.afonichev(a)gmail.com, kdaniel(a)redhat.com
Classification: Fedora
Story Points: ---
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
tomcat-lib is bundling apache-commons-dbcp, an external library.
According to Fedora Java Packaging Guidelines this is unacceptable. See:
https://fedoraproject.org/wiki/Packaging:Java#Pre-built_JAR_files_.2F_Oth...
Please remove this library from packaging and add it as external dependency.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 4 months
[Bug 826551] New: Allow to override the default JETTY_PORT jetty.conf
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=826551
Bug ID: 826551
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 16
Priority: unspecified
CC: java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com, mizdebsk(a)redhat.com,
overholt(a)gmail.com, sochotni(a)redhat.com
Assignee: sochotni(a)redhat.com
Summary: Allow to override the default JETTY_PORT jetty.conf
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: kwizart(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: jetty
Product: Fedora
Created attachment 587736
--> https://bugzilla.redhat.com/attachment.cgi?id=587736&action=edit
Allow to override JETTY_PORT in /etc/jetty/jetty.conf
Description of problem:
The jetty doc allow to override the default port from which jetty is running.
/etc/jetty/jetty.conf file could be sourced to set an alternative JETTY_PORT.
Unfortunately the initscript doesn't pass the information to the at launch
step.
Version-Release number of selected component (if applicable):
jetty for f16
How reproducible:
always
Steps to Reproduce:
1. echo "JETTY_PORT=8082" >> /etc/jetty/jetty.conf
2. service jetty restart
3. netstat -an |grep 808
Actual results:
netstat -na |grep 808 should report the default 8088 port been used
Expected results:
netstat -na |grep 808 should report the 8082 port used by jetty.
Additional info:
Given that initscript are deprecated in current fedora, this patch explicitely
intend to be usefull on EL6 EPEL port of jetty
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 4 months
[Bug 839261] New: Build hangs when building mylyn
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=839261
Bug ID: 839261
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 17
Priority: unspecified
CC: java-sig-commits(a)lists.fedoraproject.org,
rgrunber(a)redhat.com
Assignee: rgrunber(a)redhat.com
Summary: Build hangs when building mylyn
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: kdaniel(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: tycho
Product: Fedora
I'm not sure if this is tycho or maven, but
(1) install eclipse and mylyn
(2) import eclipse-mylyn from fedora git
(3) fedpkg local
The build will be scanning projects forever. After uninstalling mylyn, build
completes normally.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 6 months
[Bug 748074] New: maven-enforcer-plugin is not compatible with maven3
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: maven-enforcer-plugin is not compatible with maven3
https://bugzilla.redhat.com/show_bug.cgi?id=748074
Summary: maven-enforcer-plugin is not compatible with maven3
Product: Fedora
Version: 16
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: unspecified
Component: maven-enforcer
AssignedTo: jcapik(a)redhat.com
ReportedBy: orion(a)cora.nwra.com
QAContact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Description of problem:
While trying to build mybatis-parent that uses maven-enforcer-plugin:
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ mybatis-parent
---
[INFO] The requirePluginVersions rule is currently not compatible with Maven3.
[WARNING] Rule 3: org.apache.maven.plugins.enforcer.RequireProperty failed with
message:
[ERROR] You must set the property 'findbugs.onlyAnalyze' in your project pom!
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.996s
[INFO] Finished at: Fri Oct 21 16:25:00 MDT 2011
[INFO] Final Memory: 7M/16M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce-java) on
project mybatis-parent: Some Enforcer rules have failed. Look above for
specific messages explaining why the rule failed. -> [Help 1]
I can set -Dfindbugs.onlyAnalyze to work around.
Version-Release number of selected component (if applicable):
maven-enforcer-plugin-1.0.1-2.fc16.noarch
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 6 months
[Bug 845993] New: Jetty unpacks deployed apps to /tmp which get cleaned up by systemd-tmpfiles
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=845993
Bug ID: 845993
QA Contact: extras-qa(a)fedoraproject.org
Severity: high
Version: 17
Priority: unspecified
CC: java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com, mizdebsk(a)redhat.com,
overholt(a)gmail.com, sochotni(a)redhat.com
Assignee: sochotni(a)redhat.com
Summary: Jetty unpacks deployed apps to /tmp which get cleaned
up by systemd-tmpfiles
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: owen(a)fraser-green.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: jetty
Product: Fedora
Description of problem:
After running a Jetty app for some days without problem, it may suddenly give
HTTP 404 messages serving static content, and java.lang.NoClassDefFoundError
exceptions for dynamic content. Closer investigation reveals that, while the
files were present in the WAR file, the WAR file has been unpacked to
/tmp/jetty-0.0.0.0-<something> and some of the contents have disappeared. While
I don't have evidence that systemd-tmpfiles is responsible, I see it's
configured to delete files in /tmp after 10 days so I assume it's the culprit.
Version-Release number of selected component (if applicable):
jetty-8.1.2-9
systemd-44-17
How reproducible:
If my assumption as to the cause are correct, this will occur in most cases a
Jetty app is deployed after 10 days.
Steps to Reproduce:
1. Deploy a Jetty app
2. Wait
Actual results:
Jetty serves HTTP 404 messages instead of content.
Expected results:
The actual content is served.
Additional info:
I worked around by simply creating the directory /usr/share/jetty/work/
As per http://wiki.eclipse.org/Jetty/Reference/Temporary_Directories Jetty will
the create it's working directory under here. While this work around is fine
for me, I believe a better place for the work directory would be under /var,
perhaps /var/lib/jetty/work.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 6 months