[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 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 709532] New: CVE-2011-1498 httpcomponents-client: sends Proxy-Authorization header to host when tunneling requests through authenticated proxy server [fedora-15]
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: CVE-2011-1498 httpcomponents-client: sends Proxy-Authorization header to host when tunneling requests through authenticated proxy server [fedora-15]
https://bugzilla.redhat.com/show_bug.cgi?id=709532
Summary: CVE-2011-1498 httpcomponents-client: sends
Proxy-Authorization header to host when tunneling
requests through authenticated proxy server
[fedora-15]
Product: Fedora
Version: 15
Platform: All
OS/Version: Linux
Status: NEW
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Component: httpcomponents-client
AssignedTo: sochotni(a)redhat.com
ReportedBy: vdanen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: sochotni(a)redhat.com, sgehwolf(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org
Blocks: 709531
Classification: Fedora
Story Points: ---
fedora-15 tracking bug for httpcomponents-client: see blocks bug list for full
details of the security issue(s).
This bug is never intended to be made public, please put any public notes
in the 'blocks' bugs.
[bug automatically created by: add-tracking-bugs]
--
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, 8 months
[Bug 817516] New: Maven stop working after upgrade to Fedora 17
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 stop working after upgrade to Fedora 17
https://bugzilla.redhat.com/show_bug.cgi?id=817516
Summary: Maven stop working after upgrade to Fedora 17
Product: Fedora
Version: 17
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: maven
AssignedTo: sochotni(a)redhat.com
ReportedBy: pahan(a)hubbitus.info
QAContact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, sochotni(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
$ mvn
/usr/lib/jvm/java
---------------------------------------------------
constituent[0]: file:/usr/share/maven/lib/ext/xml-commons-apis.jar
constituent[1]:
file:/usr/share/maven/lib/plexus_containers-component-annotations.jar
constituent[2]: file:/usr/share/maven/lib/maven-core.jar
constituent[3]: file:/usr/share/maven/lib/maven-compat.jar
constituent[4]: file:/usr/share/maven/lib/maven-wagon_provider-api.jar
constituent[5]: file:/usr/share/maven/lib/maven-model.jar
constituent[6]: file:/usr/share/maven/lib/aether_connector-wagon.jar
constituent[7]: file:/usr/share/maven/lib/maven-repository-metadata.jar
constituent[8]: file:/usr/share/maven/lib/plexus_utils.jar
constituent[9]: file:/usr/share/maven/lib/sisu_sisu-inject-bean.jar
constituent[10]: file:/usr/share/maven/lib/aether_spi.jar
constituent[11]: file:/usr/share/maven/lib/maven-settings-builder.jar
constituent[12]: file:/usr/share/maven/lib/atinject.jar
constituent[13]: file:/usr/share/maven/lib/nekohtml.jar
constituent[14]: file:/usr/share/maven/lib/maven-artifact.jar
constituent[15]: file:/usr/share/maven/lib/sisu_sisu-inject-plexus.jar
constituent[16]: file:/usr/share/maven/lib/guava.jar
constituent[17]: file:/usr/share/maven/lib/maven-wagon_http-shared.jar
constituent[18]: file:/usr/share/maven/lib/plexus_plexus-cipher.jar
constituent[19]: file:/usr/share/maven/lib/aether_api.jar
constituent[20]: file:/usr/share/maven/lib/maven-aether-provider.jar
constituent[21]: file:/usr/share/maven/lib/xerces-j2.jar
constituent[22]: file:/usr/share/maven/lib/maven-wagon_file.jar
constituent[23]: file:/usr/share/maven/lib/google-guice.jar
constituent[24]: file:/usr/share/maven/lib/maven-settings.jar
constituent[25]: file:/usr/share/maven/lib/maven-wagon_http-lightweight.jar
constituent[26]: file:/usr/share/maven/lib/commons-cli.jar
constituent[27]: file:/usr/share/maven/lib/plexus_plexus-sec-dispatcher.jar
constituent[28]: file:/usr/share/maven/lib/maven-model-builder.jar
constituent[29]: file:/usr/share/maven/lib/maven-plugin-api.jar
constituent[30]: file:/usr/share/maven/lib/maven-embedder.jar
constituent[31]: file:/usr/share/maven/lib/plexus_interpolation.jar
constituent[32]: file:/usr/share/maven/lib/aether_util.jar
constituent[33]: file:/usr/share/maven/lib/aether_impl.jar
constituent[34]: file:/usr/share/maven/lib/xbean_xbean-reflect.jar
---------------------------------------------------
Exception in thread "main" java.lang.UnsupportedClassVersionError:
javax/inject/Provider : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:386)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
at org.apache.maven.cli.MavenCli.container(MavenCli.java:375)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:191)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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:616)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Version-Release number of selected component (if applicable):
$ rpm -qf `which mvn`
maven-3.0.4-2.fc17.x86_64
How reproducible:
Always
--
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, 8 months
[Bug 798263] New: maven-ant-tasks is incompatible with Maven 3
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-ant-tasks is incompatible with Maven 3
https://bugzilla.redhat.com/show_bug.cgi?id=798263
Summary: maven-ant-tasks is incompatible with Maven 3
Product: Fedora
Version: 17
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: maven-ant-tasks
AssignedTo: orion(a)cora.nwra.com
ReportedBy: mgoldman(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: orion(a)cora.nwra.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
While executing an Ant tasks that requires maven I get the following
stacktrace.
Related upstream bug report: http://jira.codehaus.org/browse/MANTTASKS-165
+
CLASSPATH=/usr/share/java/ant/ant-contrib.jar:/usr/share/java/maven-ant-tasks.jar:/usr/share/java/aqute-bnd.jar:/usr/share/java/maven2/maven-profile.jar:/usr/share/java/maven2/maven-project.jar:/usr/share/java/plexus/plexus-component-api.jar:/usr/share/java/maven2/maven-error-diagnostics.jar:/usr/share/java/plexus/classworlds.jar:/usr/share/java/plexus/utils.jar:/usr/share/java/plexus/interpolation.jar:/usr/share/java/maven-wagon/provider-api.jar:/usr/share/java/maven/maven-model.jar:/usr/share/java/maven/maven-artifact.jar:/usr/share/java/maven/maven-core.jar:/usr/share/java/maven/maven-compat.jar:/usr/share/java/maven/maven-settings.jar:/usr/share/java/maven/maven-settings-builder.jar
+ ant
-Djsf.build.home=/home/goldmann/work/glassfish-jsf-impl/BUILD/glassfish-jsf-impl-2.1.7
-Dcontainer.name=tomcat7
Buildfile:
/home/goldmann/work/glassfish-jsf-impl/BUILD/glassfish-jsf-impl-2.1.7/build.xml
BUILD FAILED
/home/goldmann/work/glassfish-jsf-impl/BUILD/glassfish-jsf-impl-2.1.7/build.xml:52:
The following error occurred while executing this line:
/home/goldmann/work/glassfish-jsf-impl/BUILD/glassfish-jsf-impl-2.1.7/common/ant/common.xml:164:
java.lang.NoSuchMethodError:
org.apache.maven.settings.RuntimeInfo.<init>(Lorg/apache/maven/settings/Settings;)V
at
org.apache.maven.artifact.ant.AbstractArtifactTask.loadSettings(AbstractArtifactTask.java:327)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.initSettings(AbstractArtifactTask.java:277)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:717)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:390)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:169)
at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:225)
at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:163)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
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:601)
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:390)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:180)
at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:82)
at org.apache.tools.ant.Main.runBuild(Main.java:793)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
error: Bad exit status from /var/tmp/rpm-tmp.tgb4cx (%build)
Version-Release number of selected component (if applicable):
maven-3.0.4-2.fc17.x86_64 and maven-ant-tasks-2.1.1-9.fc17.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, 8 months
[Bug 723276] New: ClassNotFoundException while building with maven-ant-tasks tasks
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: ClassNotFoundException while building with maven-ant-tasks tasks
https://bugzilla.redhat.com/show_bug.cgi?id=723276
Summary: ClassNotFoundException while building with
maven-ant-tasks tasks
Product: Fedora
Version: rawhide
Platform: noarch
OS/Version: Linux
Status: NEW
Severity: medium
Priority: unspecified
Component: maven-ant-tasks
AssignedTo: orion(a)cora.nwra.com
ReportedBy: guido.grazioli(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: orion(a)cora.nwra.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Description of problem:
Building with ant and maven-ant-tasks throws several ClassNotFoundExceptions
Version-Release number of selected component (if applicable):
maven-ant-tasks-2.1.1-8.fc16.noarch
How reproducible:
Run a build.xml which invokes a <artifact:> task
Actual results:
ClassNotFoundExceptions, ie:
BUILD FAILED
/home/guido/rpmbuild/BUILD/jinput/build.xml:251: The following error occurred
while executing this line:
jar:file:/home/guido/rpmbuild/BUILD/jinput/lib/maven-ant-tasks-2.1.0.jar!/org/apache/maven/artifact/ant/antlib.xml:4:
taskdef A class needed by class org.apache.maven.artifact.ant.DependenciesTask
cannot be found: org/codehaus/classworlds/DuplicateRealmException
Expected results:
Build runs succesfully
Additional info:
I could go a bit ahead in the build, avoiding CNFEs, creating the files:
/etc/ant.d/maven-project (containing "maven2/maven-project")
/etc/ant.d/maven-error-diagnostics ("maven2/maven-error-diagnostics")
/etc/ant.d/plexus-classwords (containing "plexus/classworlds")
/etc/ant.d/plexus-container-default ("plexus/container-default")
/etc/ant.d/plexus-interpolation ("plexus/interpolation")
but at some point i get:
BUILD FAILED
/home/guido/rpmbuild/BUILD/jinput/build.xml:261: Unable to find component:
org.apache.maven.artifact.manager.WagonManager
maven-ant-tasks should also get runtime requires on the packages which provide
those jars
--
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, 8 months
[Bug 810775] New: Bad %post scritlet
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: Bad %post scritlet
https://bugzilla.redhat.com/show_bug.cgi?id=810775
Summary: Bad %post scritlet
Product: Fedora
Version: 16
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: low
Priority: unspecified
Component: tomcat
AssignedTo: ivan.afonichev(a)gmail.com
ReportedBy: mattias.ellert(a)fysast.uu.se
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: ---
Description of problem:
Installing tomcat results in the following error:
Installerar : tomcat-7.0.26-1.fc16.noarch 8/8
fel vid läsning av information om tjänsten tomcat: Filen eller katalogen finns
inte
Version-Release number of selected component (if applicable):
tomcat-7.0.26-1.fc16.noarch
How reproducible:
always
Steps to Reproduce:
1. yum install tomcat
Actual results:
Error messaged about missing service information during installation
Expected results:
No errors during installation
Additional info:
Tomcat is handled using systemd. However the %post scriptlet still tries to
configure the service using chkconfig in the %post scriptlet. This call is
responsible for the error.
postinstall scriptlet (using /bin/sh):
# install but don't activate
/sbin/chkconfig --add tomcat
if [ $1 -eq 1 ]; then
#initial installation
/bin/systemctl daemon-reload >/dev/null 2>&1 || :
fi
Additionally: installing tomcat resulted in that redhat-lsb was installed as a
dependency. Native Fedora packages are not supposed to depend on this. Do you
really need it?
--
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, 8 months
[Bug 814900] New: Missing tomcat-coyote POM file in tomcat-lib
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: Missing tomcat-coyote POM file in tomcat-lib
https://bugzilla.redhat.com/show_bug.cgi?id=814900
Summary: Missing tomcat-coyote POM file in tomcat-lib
Product: Fedora
Version: 17
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: tomcat
AssignedTo: ivan.afonichev(a)gmail.com
ReportedBy: mattias.ellert(a)fysast.uu.se
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: ---
Description of problem:
I am trying to package a software module that depends on tomcat-coyote. When
running mvn-rpmbuild the dependency can not be resolved because the
tomcat-coyote POM file is missing.
Version-Release number of selected component (if applicable):
tomcat-lib-7.0.27-2.fc17
How reproducible:
Always
Actual results:
The repository system is offline but the artifact
org.apache.tomcat:tomcat-coyote:jar:6.0.24 is not available in the local
repository.
Expected results:
Resolved dependencies
--
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, 8 months