java-devel November 2013

java-devel@lists.fedoraproject.org

18 participants
19 discussions

mizdebsk vacation
by Mikolaj Izdebski 15 Nov '13

15 Nov '13

I'll be taking a vacation and I will be unavailable in the next days. I'm coming back on 4 December. If there are problems with Maven/XMvn or any other packages I take care of then you can contact Stanislav Ochotnicky (sochotni). -- Mikolaj Izdebski IRC: mizdebsk

3 3

Packaging of ObjectWeb ASM
by Mikolaj Izdebski 13 Nov '13

13 Nov '13

Currently Fedora ships two versions of ObjectWeb ASM -- objectweb-asm (version 3.x) and objectweb-asm4 (version 4.x), neither of which are compat packages. About a month ago upstream released version 5.0 beta and we can already start seeing packages requiring this new version. Final version 5.0 can be expected soon. Currently we can't get rid of ASM 3 as it is required by many packages, but ASM 4 and ASM 5 should be compatible, so it should be OK for Fedora to ship just versions 3 and 5. My proposal of updating is: 1) Create a new package objectweb-asm3 which would be a copy of current objectweb-asm and would be converted to be a compat package. 2) Give some time for maintainers of dependant packages to decide whether they want to stay on version 3.x or keep depending on default system version (which will be upgraded to 5.x). The most important packages can be ported by interested parties or provenpackagers. 3) Update objectweb-asm from version 3.x to version 5.x. This version would obsolete and provide objectweb-asm4. 4) Deprecate objectweb-asm4 package. After these steps are completed, we'll have 2 ASM packages: 1) objectweb-asm, ASM version 5.x default provider of ASM (non-compat package) provides, obsoletes: objectweb-asm4 2) objectweb-asm3, ASM version 3.x compat package What do you think about that? Do you have any better idea how to proceed with update to ASM 5.x? -- Mikolaj Izdebski IRC: mizdebsk

3 6

Gradle upgrade issues (#976330)
by Michael Ekstrand 12 Nov '13

12 Nov '13

In bug #976330[1], there's been some discussion of the desire to upgrade Gradle from 1.0 to a new version (currently 1.8), and that there is significant hassle to actually do so. Some of this hassle I see in the bugs blocking 976330 - upgrading to Aether, newer Plexus containers, and maybe Polyglot Maven. What are the key issues that make it difficult to upgrade and maintain Gradle in Fedora? The likely ones I see: - Incompatible dependencies (Gradle may require package versions no longer shipped in Fedora) - Bootstrapping problems (the Gradle 1.8 sources won't build with Gradle 1.8, they seem to require 1.7) - Possibly library embedding (although the Gradle sources do seem to pull in the dependencies from Maven) 1. https://bugzilla.redhat.com/show_bug.cgi?id=976330 -- Michael Ekstrand — http://elehack.net/

6 12

Maven tycho Plugin and Reproducible Version Qualifiers
by Manuel Faux 12 Nov '13

12 Nov '13

I'm trying to create a package of a maven project. The project uses the tycho-packaging maven plugin with reproducible version qualifiers. I am not checking out the git repository of the project, but a tgz bundle. Therefore tycho cannot do any git operations and fails with the following error: [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.18.1:build-qualifier (default-build-qualifier) on project org.eclipse.osgi: Execution default-build-qualifier of goal org.eclipse.tycho:tycho-packaging-plugin:0.18.1:build-qualifier failed: One of setGitDir or setWorkTree must be called. -> [Help 1] Does anyone have a suggestion how to ether disable the reproducible version qualifiers functionality of tycho, or how else to circumvent this error? Manuel

2 1

R: Packaging of ObjectWeb ASM
by GILBERTO CTTNEO 12 Nov '13

12 Nov '13

>----Messaggio originale---- >Da: mizdebsk(a)redhat.com >Data: 11/11/2013 15.49 >A: <objectweb-asm-owner(a)fedoraproject.org>, <objectweb-asm4- owner(a)fedoraproject.org>, "Fedora Java Development List"<java-devel@lists. fedoraproject.org> >Ogg: Packaging of ObjectWeb ASM > >Currently Fedora ships two versions of ObjectWeb ASM -- objectweb-asm >(version 3.x) and objectweb-asm4 (version 4.x), neither of which are >compat packages. About a month ago upstream released version 5.0 beta >and we can already start seeing packages requiring this new version. >Final version 5.0 can be expected soon. > >Currently we can't get rid of ASM 3 as it is required by many packages, >but ASM 4 and ASM 5 should be compatible, so it should be OK for Fedora >to ship just versions 3 and 5. > >My proposal of updating is: > >1) Create a new package objectweb-asm3 which would be a copy of current >objectweb-asm and would be converted to be a compat package. > >2) Give some time for maintainers of dependant packages to decide >whether they want to stay on version 3.x or keep depending on default >system version (which will be upgraded to 5.x). The most important >packages can be ported by interested parties or provenpackagers. > >3) Update objectweb-asm from version 3.x to version 5.x. This version >would obsolete and provide objectweb-asm4. > >4) Deprecate objectweb-asm4 package. > >After these steps are completed, we'll have 2 ASM packages: > >1) objectweb-asm, ASM version 5.x > default provider of ASM (non-compat package) > provides, obsoletes: objectweb-asm4 > >2) objectweb-asm3, ASM version 3.x > compat package > >What do you think about that? Do you have any better idea how to proceed >with update to ASM 5.x? +1 > >-- >Mikolaj Izdebski >IRC: mizdebsk >

1 0

Unexpected Exception on JVM shutdown
by Krzysztof Daniel 09 Nov '13

09 Nov '13

Hey everyone, I've recently switched to the f20, and each time I shutdown Eclipse, ABRT reports an error (via abrt-java-connector): Uncaught java.lang.ClassNotFoundException exception in thread "main" in a method java.lang.ClassLoader.loadClass() with signature (Ljava/lang/String;Z )Ljava/lang/Class; Exception in thread "main" java.lang.ClassNotFoundException: .usr.lib64.eclipse..plugins.org.eclipse.equinox.launcher_1.3.0.v20131030-1100.jar at java.net.URLClassLoader$1.run(URLClassLoader.java:366) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/rt.ja r!/java/net/URLClassLoader$1.class] at java.net.URLClassLoader$1.run(URLClassLoader.java:355) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/rt.ja r!/java/net/URLClassLoader$1.class] at java.security.AccessController.doPrivileged(Native Method) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/r t.jar!/java/security/AccessController.class] at java.net.URLClassLoader.findClass(URLClassLoader.java:354) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/r t.jar!/java/net/URLClassLoader.class] at java.lang.ClassLoader.loadClass(ClassLoader.java:425) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/rt.jar !/java/lang/ClassLoader.class] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/li b/rt.jar!/sun/misc/Launcher$AppClassLoader.class] at java.lang.ClassLoader.loadClass(ClassLoader.java:358) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre/lib/rt.jar !/java/lang/ClassLoader.class] VM arguments attached for a reference: -Xms128m -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Dorg.eclipse.swt.browser.UseWebKitGTK=true -Dhelp.lucene.tokenizer=standard -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init> -XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate -XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding -XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile -XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState -Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins -Declipse.p2.skipMovedInstallDetection=true -XX:MaxPermSize=256m -jar /usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20131030-1100.jar This stack trace is beyond my skills. It looks like JVM tried to interpret a jar as a class, but since VM is going down, I get no chance to debug it (jvm is terminated before remote breakpoint is even hit). As I have no clue what to do with it further, I'd appreciate any advice. -- Krzysztof Daniel <kdaniel(a)redhat.com> Red Hat

2 2

Heads-up: Hibernate upgrade to 4.3.0.Beta4
by Marek Goldmann 08 Nov '13

08 Nov '13

Hi All, I want to immediately upgrade hibernate package to 4.3.0.Beta4 in Fedora Rawhide and in F20 too. Please let me *now* know if I should hold on with it. I created a scratch build for Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=6149492 --Marek

2 2

XMvn build arch packages when are marked as noarch
by gil 07 Nov '13

07 Nov '13

hi any ideas? + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Kd1t0F + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch '!=' / ']' + rm -rf /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch ++ dirname /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch + cd thredds-4.3.19 + xmvn-install -R .xmvn-reactor -n thredds -d /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch [INFO] =============================================== [INFO] SOURCE ARTIFACT: [INFO] groupId: edu.ucar [INFO] artifactId: thredds-parent [INFO] extension: pom [INFO] classifier: [INFO] version: 4.3.19 [INFO] stereotype: pom [INFO] namespace: [INFO] file: /builddir/build/BUILD/thredds-4.3.19/pom.xml [INFO] ----------------------------------------------- [INFO] TARGET ARTIFACT: [INFO] groupId: JPP/thredds [INFO] artifactId: thredds-parent [INFO] extension: pom [INFO] classifier: [INFO] version: SYSTEM [INFO] stereotype: [INFO] namespace: [INFO] file: usr/share/maven-poms/JPP.thredds-thredds-parent.pom [INFO] =============================================== [INFO] =============================================== [INFO] SOURCE ARTIFACT: [INFO] groupId: edu.ucar [INFO] artifactId: udunits [INFO] extension: jar [INFO] classifier: [INFO] version: 4.3.19 [INFO] stereotype: [INFO] namespace: [INFO] file: /builddir/build/BUILD/thredds-4.3.19/udunits/target/udunits-4.3.19.jar [INFO] ----------------------------------------------- [INFO] TARGET ARTIFACT: [INFO] groupId: JPP/thredds [INFO] artifactId: udunits [INFO] extension: jar [INFO] classifier: [INFO] version: SYSTEM [INFO] stereotype: [INFO] namespace: [INFO] file: usr/lib/java/thredds/udunits.jar [INFO] =============================================== [INFO] =============================================== [INFO] SOURCE ARTIFACT: [INFO] groupId: edu.ucar [INFO] artifactId: netcdf [INFO] extension: jar [INFO] classifier: [INFO] version: 4.3.19 [INFO] stereotype: [INFO] namespace: [INFO] file: /builddir/build/BUILD/thredds-4.3.19/cdm/target/netcdf-4.3.19.jar [INFO] ----------------------------------------------- [INFO] TARGET ARTIFACT: [INFO] groupId: JPP/thredds [INFO] artifactId: netcdf [INFO] extension: jar [INFO] classifier: [INFO] version: SYSTEM [INFO] stereotype: [INFO] namespace: [INFO] file: usr/lib/java/thredds/netcdf.jar [INFO] =============================================== [WARNING] Failed to resolve artifact: edu.ucar:udunits:jar:4.3.19 + jdir=target/site/apidocs + '[' -d target/site/apidocs ']' + install -dm755 /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch/usr/share/javadoc/thredds + cp -pr target/site/apidocs/allclasses-frame.html target/site/apidocs/allclasses-noframe.html target/site/apidocs/com target/site/apidocs/constant-values.html target/site/apidocs/deprecated-list.html target/site/apidocs/help-doc.html target/site/apidocs/index-all.html target/site/apidocs/index.html target/site/apidocs/overview-frame.html target/site/apidocs/overview-summary.html target/site/apidocs/overview-tree.html target/site/apidocs/package-list target/site/apidocs/resources target/site/apidocs/serialized-form.html target/site/apidocs/stylesheet.css target/site/apidocs/thredds target/site/apidocs/ucar target/site/apidocs/uk /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch/usr/share/javadoc/thredds + echo /usr/share/javadoc/thredds + install -pm 644 cdm/target/netcdf-4.3.19-tests.jar /builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch/usr/share/java/thredds/netcdf-tests.jar install: cannot create regular file '/builddir/build/BUILDROOT/thredds-4.3.19-4.fc20.noarch/usr/share/java/thredds/netcdf-tests.jar': No such file or directory RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.Kd1t0F (%install) Bad exit status from /var/tmp/rpm-tmp.Kd1t0F (%install) Child return code was: 1 EXCEPTION: Command failed. See logs for output. # ['bash', '--login', '-c', 'rpmbuild -bb --target noarch --nodeps builddir/build/SPECS/thredds.spec'] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 361, in do raise mockbuild.exception.Error, ("Command failed. See logs for output.\n # %s" % (command,), child.returncode) Error: Command failed. See logs for output. # ['bash', '--login', '-c', 'rpmbuild -bb --target noarch --nodeps builddir/build/SPECS/thredds.spec'] LEAVE do --> EXCEPTION RAISED

2 2

XMvn 1.3.0 release notes
by Mikolaj Izdebski 05 Nov '13

05 Nov '13

What's new in XMvn 1.3.0 XMvn 1.3.0 was released on 2013-11-05. Most important changes include: * Major features * Installation of Ivy modules Since version 1.3.0 XMvn can install Ivy modules. Ivy descriptor files are transparently converted to Maven POMs and installed as such. This feature is still experimental. * Major bugfixes * Fix manifest injection XMvn no longer injects manifests to JAR files that have no manifests. This also fixes a bug that caused POM files to be replaced with empty JAR files in some cases. * Delay simplification of effective POMs Effective POMs are now simplified during package installation, not build. This way installer has enough information needed to generate auto-requires on Java version. * Make resolver ignore artifact types Configured artifact types by repositories no longer affect behaviour of XMvn resolver, but are still understood by installer. * Minor bugfixes * Fix potential resource leaks XMvn 1.3.0 fixes a few bugs in which certain resources (mostly files) were not released (closed) even when they were no longer needed.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

java-devel November 2013