https://bugzilla.redhat.com/show_bug.cgi?id=1167988
Bug ID: 1167988
Summary: [abrt] javapackages-tools:
maven_depmap.py:109:_get_jpp_from_filename:IOError:
JAR path doesn't exist
Product: Fedora
Version: 20
Component: javapackages-tools
Assignee: mizdebsk(a)redhat.com
Reporter: projects.rg(a)smart.ms
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
msrb(a)redhat.com
Description of problem:
happened while rpmbuild'ing ...
That user error should be handled else and propably not be reported to Abrt:
"IOError: JAR path doesn't exist"
Version-Release number of selected component:
javapackages-tools-3.4.1-1.fc20
Additional info:
reporter: libreport-2.2.3
cmdline: python -m /usr/share/java-utils/maven_depmap -p /usr -n ''
/home/build/rpmbuild/BUILDROOT/rabbitmq-java-client-3.4.1-2.fc20.x86_64/usr/share/maven-fragments/rabbitmq-java-client
/home/build/rpmbuild/BUILDROOT/rabbitmq-java-client-3.4.1-2.fc20.x86_64/usr/share/maven-poms/JPP-rabbitmq-java-client.pom
/home/build/rpmbuild/BUILDROOT/rabbitmq-java-client-3.4.1-2.fc20.x86_64/usr/share/java/*.jar
dso_list: python-libs-2.7.5-15.fc20.x86_64
executable: /usr/share/java-utils/maven_depmap.py
kernel: 3.17.3-200.fc20.x86_64
type: Python
Truncated backtrace:
maven_depmap.py:109:_get_jpp_from_filename:IOError: JAR path doesn't exist
Traceback (most recent call last):
File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/share/java-utils/maven_depmap.py", line 385, in <module>
fragment = parse_pom(pom_path, prefix, jar_path)
File "/usr/share/java-utils/maven_depmap.py", line 229, in parse_pom
jpp_gid, jpp_aid = _get_jpp_from_filename(pom_file, prefix, jar_file,
extension)
File "/usr/share/java-utils/maven_depmap.py", line 109, in
_get_jpp_from_filename
raise IOError("JAR path doesn't exist")
IOError: JAR path doesn't exist
Local variables in innermost frame:
prefix: '/usr'
pom_path:
'/home/build/rpmbuild/BUILDROOT/rabbitmq-java-client-3.4.1-2.fc20.x86_64/usr/share/maven-poms/JPP-rabbitmq-java-client.pom'
extension: 'jar'
pomname: 'JPP-rabbitmq-java-client.pom'
jar_path:
'/home/build/rpmbuild/BUILDROOT/rabbitmq-java-client-3.4.1-2.fc20.x86_64/usr/share/java/*.jar'
--
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=n93Ip09zpm&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1163157
Bug ID: 1163157
Summary: jetty-9.2.4.v20141103 is available
Product: Fedora
Version: rawhide
Component: jetty
Keywords: FutureFeature, Triaged
Assignee: mizdebsk(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com, msrb(a)redhat.com,
overholt(a)gmail.com
Latest upstream release: 9.2.4.v20141103
Current version/release in Fedora Rawhide: 9.2.3-2.fc22
URL: http://repo2.maven.org/maven2/org/eclipse/jetty/jetty-project/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service
will be implemented by a new system: https://github.com/fedora-infra/anitya/
It will require to manage monitored projects via a new web interface. Please
make yourself familiar with the new system to ease the transition.
--
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=jFzEudfyDk&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1163148
Bug ID: 1163148
Summary: httpcomponents-client-4.3.6 is available
Product: Fedora
Version: rawhide
Component: httpcomponents-client
Keywords: FutureFeature, Triaged
Assignee: mizdebsk(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
msrb(a)redhat.com
Latest upstream release: 4.3.6
Current version/release in Fedora Rawhide: 4.3.5-1.fc22
URL: http://www.apache.org/dist/httpcomponents/httpclient/source/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service
will be implemented by a new system: https://github.com/fedora-infra/anitya/
It will require to manage monitored projects via a new web interface. Please
make yourself familiar with the new system to ease the transition.
--
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=AMoTW5Pnby&a=cc_unsubscribe
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Missing service provider configuration files in the woodstox jar files
https://bugzilla.redhat.com/show_bug.cgi?id=796739
Summary: Missing service provider configuration files in the
woodstox jar files
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Linux
Status: NEW
Severity: medium
Priority: unspecified
Component: woodstox-core
AssignedTo: jcapik(a)redhat.com
ReportedBy: juan.hernandez(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
The jar files provided in the woodstox-jar package don't contain the service
provider configuration files needed to use the
Version-Release number of selected component (if applicable):
woodstox-core-4.1.2-2.fc17.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Write and compile the following java program:
import javax.xml.stream.XMLInputFactory;
public class Test {
public static void main(String[] args) throws Exception {
System.out.println(XMLInputFactory.newInstance());
}
}
2. Run it with the version of the "woodstox-core-asj.jar" provided by the RPM:
$ java -cp $(build-classpath woodstox-core stax2-api):. Test
Actual results:
com.sun.xml.internal.stream.XMLInputFactoryImpl@605df3c5
It is using the internal implementation provided by the JDK.
Expected results:
com.ctc.wstx.stax.WstxInputFactory@a5ae1e7
It should use the implementation provided by the woodstox-core package.
Additional info:
I believe that the problem is that the service provider configuration files
that are available in the source of the package in the "src/resources"
directory are not copied to the "META-INF/services" directory of the generated
jar files.
This can be fixed with the following patch for the spec:
--- a/woodstox-core.spec
+++ b/woodstox-core.spec
@@ -64,7 +64,6 @@ sed -i "s/@REQ_STAX2_VERSION@/%{stax2_ver}/g" pom.xml
pom-lgpl.xml
# removing bundled stuff
rm -rf lib
rm -rf src/maven
-rm -rf src/resources
rm -rf src/samples
rm -rf src/java/org
rm -rf src/test/org
@@ -76,6 +75,11 @@ mv -f src/java src/main/
mkdir src/test/java
mv -f src/test/wstxtest src/test/java/
+# Make sure that the service provider configuration files end up
+# in the META-INF/services directory of the resulting jar files:
+mkdir -p src/main/resources/META-INF/services
+cp src/resources/* src/main/resources/META-INF/services/.
+
%build
# stax2 missing -> cannot compile tests -> tests skipped
mvn-rpmbuild -Dmaven.test.skip=true \
--
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.