java-devel January 2014

java-devel@lists.fedoraproject.org

11 participants
10 discussions

Apache TomEE rpms
by David Blevins 12 Feb '16

12 Feb '16

Hello Fedora/Java people, First post to the list, so hello! We've crafted up some RPMs for Apache TomEE and are looking to contribute them to Fedora if at all possible. * http://dl.bintray.com/hgomez/devops-incubator-rpm/tomee-jaxrs-1.5.2-1.noarc… * http://dl.bintray.com/hgomez/devops-incubator-rpm/tomee-webprofile-1.5.2-1.… * http://dl.bintray.com/hgomez/devops-incubator-rpm/tomee-plus-1.5.2-1.noarch… I haven't much of an idea on what the process for this might be. Dan Allen (RedHat) pointed us this way. Hoping someone here might have insight, even if that is some other list. -David

5 5

Why no Class-Path manifest attribute?
by Florian Weimer 06 Feb '14

06 Feb '14

It seems that a significant number of JAR files under /usr/share/java do not declare their dependencies using the Class-Path manifest attribute. As a result, the dependencies need to be collected manually and included with the final link (typically, in the -classpath argument to /usr/bin/java). This is mightily inconvenient and leaks implementation details across Java RPM package boundaries. (I don't think %jpackage_script does recursive linking, unlike the JVM.) rpmlint flags usage of the Class-Path attribute: http://fedoraproject.org/wiki/Packaging:Java#class-path-in-manifest But why? -- Florian Weimer / Red Hat Product Security Team

10 23

Duplicate OSGi provides
by Mikolaj Izdebski 29 Jan '14

29 Jan '14

Java packages have OSGi auto-provides generated from JAR manifests. They are used by auto-requires generator to specify automatic RPM dependencies for OSGi bundles. The problem is that there may be more than one package providing bundle with the same Bundle-SymbolicName (BSN), in which case generated auto-provides are also the same. I have generated a report of BSN duplication for other cases (included below). It doesn't include packages for which I am aware of open bugs in Bugzilla that affect OSGi provides. osgi(javax.servlet.jsp): glassfish-jsp-api: package version: 2.3.1 provided version: 2.3.1 tomcat-jsp-2.2-api (tomcat): package version: 7.0.47 provided version: 2.2.0 osgi(org.apache.geronimo.specs.geronimo-jaspic_1.0_spec): geronimo-jaspic-spec: package version: 1.1 provided version: 1.1.0 jetty: package version: 9.1.1 provided version: 1.1.0 osgi(org.eclipse.cdt.core.tests): eclipse-cdt: package version: 8.2.1 provided version: 5.4.0 eclipse-cdt-tests (eclipse-cdt): package version: 8.2.1 provided version: 5.4.0 osgi(org.eclipse.emf.edit): eclipse-emf-core (eclipse-emf): package version: 2.9.1 provided version: 2.9.0 eclipse-emf-sdk (eclipse-emf): package version: 2.9.1 provided version: 2.9.0 osgi(org.eclipse.jetty.monitor): jetty: package version: 9.1.1 provided version: 9.1.1 jetty-monitor (jetty): package version: 9.1.1 provided version: 9.1.1 osgi(org.eclipse.jgit): eclipse-jgit: package version: 3.2.0 provided version: 3.2.0 jgit (eclipse-jgit): package version: 3.2.0 provided version: 3.2.0 osgi(org.eclipse.jgit.java7): eclipse-jgit: package version: 3.2.0 provided version: 3.2.0 jgit (eclipse-jgit): package version: 3.2.0 provided version: 3.2.0 osgi(org.eclipse.jpt.common.branding): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jpt.common.core): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jpt.common.ui): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jpt.common.utility): eclipse-wtp-jpa: package version: 3.5.1 provided version: 2.2.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 2.2.0 osgi(org.eclipse.jpt.jaxb.branding): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jpt.jaxb.core): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.3.1 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.3.1 osgi(org.eclipse.jpt.jaxb.core.schemagen): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.1.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.1.0 osgi(org.eclipse.jpt.jaxb.ui): eclipse-wtp-jpa: package version: 3.5.1 provided version: 1.4.0 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 1.4.0 osgi(org.eclipse.jsf.branding): eclipse-wtp-jsf: package version: 3.5.1 provided version: 3.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 3.5.0 osgi(org.eclipse.jst.jsf.apache.trinidad.tagsupport): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.4.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.4.0 osgi(org.eclipse.jst.jsf.common): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.jsf.common.runtime): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.4.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.4.0 osgi(org.eclipse.jst.jsf.common.ui): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.jsf.core): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.7.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.7.0 osgi(org.eclipse.jst.jsf.facelet.core): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jst.jsf.facelet.ui): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.3.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.3.0 osgi(org.eclipse.jst.jsf.facesconfig): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.jsf.facesconfig.ui): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.jsf.standard.tagsupport): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.jsf.ui): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.6.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.6.0 osgi(org.eclipse.jst.pagedesigner): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.6.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.6.0 osgi(org.eclipse.jst.pagedesigner.jsf.ui): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.jst.pagedesigner.jsp.core): eclipse-wtp-jsf: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-jsf-sdk (eclipse-wtp-jsf): package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.mylyn.discovery.ui.source): eclipse-mylyn: package version: 3.10.0 provided version: 3.10.0 eclipse-mylyn-sdk (eclipse-mylyn): package version: 3.10.0 provided version: 3.10.0 osgi(org.eclipse.mylyn.ide.ui): eclipse-mylyn-context-java (eclipse-mylyn): package version: 3.10.0 provided version: 3.10.0 eclipse-mylyn-ide (eclipse-mylyn): package version: 3.10.0 provided version: 3.10.0 osgi(org.eclipse.persistence.jpa.jpql): eclipse-wtp-jpa: package version: 3.5.1 provided version: 2.5.1 eclipse-wtp-jpa-sdk (eclipse-wtp-jpa): package version: 3.5.1 provided version: 2.5.1 osgi(org.eclipse.ptp.core.source): eclipse-ptp-core-source (eclipse-ptp): package version: 7.0.3 provided version: 7.0.0 eclipse-ptp-sdk (eclipse-ptp): package version: 7.0.3 provided version: 7.0.0 osgi(org.eclipse.wst.internet.monitor.core): eclipse-wtp-common: package version: 3.5.1 provided version: 1.0.505 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.0.505 osgi(org.eclipse.wst.internet.monitor.ui): eclipse-wtp-servertools: package version: 3.5.1 provided version: 1.0.608 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.0.608 osgi(org.eclipse.wst.server.core): eclipse-wtp-common: package version: 3.5.1 provided version: 1.5.0 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.5.0 osgi(org.eclipse.wst.server.discovery): eclipse-wtp-servertools: package version: 3.5.1 provided version: 1.0.400 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.0.400 osgi(org.eclipse.wst.server.ui): eclipse-wtp-servertools: package version: 3.5.1 provided version: 1.4.104 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.4.104 osgi(org.eclipse.wst.server.ui.doc.user): eclipse-wtp-servertools: package version: 3.5.1 provided version: 1.1.500 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.1.500 osgi(org.eclipse.wst.server.ui.infopop): eclipse-wtp-servertools: package version: 3.5.1 provided version: 1.1.100 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.1.100 osgi(org.eclipse.wst.web): eclipse-wtp-jeetools: package version: 3.5.1 provided version: 1.1.700 eclipse-wtp-sourceediting: package version: 3.5.1 provided version: 1.1.700 osgi(org.jboss.netty): netty3: package version: 3.6.6 provided version: 3.6.6 netty31: package version: 3.1.5 provided version: 3.1.5 osgi(org.objectweb.asm): objectweb-asm: package version: 5.0 provided version: 5.0.0 objectweb-asm3: package version: 3.3.1 provided version: 3.3.1

3 4

Fwd: Broken dependencies: zanata-common
by Patrick Huang 28 Jan '14

28 Jan '14

Hi guys, Can anyone give me a hint on what went wrong on this? I got several emails saying a package I own (zanata-common) has broken dependencies(mvn(xom:xom:1.0)). But when I build it in koji, it works ok. http://koji.fedoraproject.org/koji/taskinfo?taskID=6432277 I explicitly added the BR and R for xom. Anything else I missed? Thanks. Regards, Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ----- Forwarded Message ----- From: buildsys(a)fedoraproject.org To: zanata-common-owner(a)fedoraproject.org Sent: Tuesday, January 21, 2014 4:36:40 AM Subject: Broken dependencies: zanata-common zanata-common has broken dependencies in the rawhide tree: On x86_64: zanata-common-3.1.0-3.fc21.noarch requires mvn(xom:xom:1.0) On i386: zanata-common-3.1.0-3.fc21.noarch requires mvn(xom:xom:1.0) On armhfp: zanata-common-3.1.0-3.fc21.noarch requires mvn(xom:xom:1.0) Please resolve this as soon as possible.

3 3

Newer JDK 8 packages?
by Florian Weimer 22 Jan '14

22 Jan '14

Could we please get newer JDK 8 packages, at least in rawhide? b115 is no longer completely usable for JDK 9 development. -- Florian Weimer / Red Hat Product Security Team

3 2

Fedora eclipse package built on OpenMandriva
by Paulo César Pereira de Andrade 21 Jan '14

21 Jan '14

Hi, I would like to let you know that after 2+ months of work I managed to port almost all fedora java stack to OpenMandriva. The most eye candy package should be eclipse: x86_64: https://abf.rosalinux.ru/build_lists/1543009 i586: https://abf.rosalinux.ru/build_lists/1543008 Most of my problems were first needing to start from a completely broken java stack, and second using rpm5. To "bootstrap" I installed fedora packages on OpenMandriva, then rebuilt them native and "injected" them in cooker repositories: https://abf.rosalinux.ru/openmandriva/javapackages-bootstrap/blob/master/cr… while rebuilding on the proper build system added a single line header on every spec: %{?_javapackages_macros:%_javapackages_macros} that is defined in /etc/rpm/macros.d/javapackages-tools.macros: https://abf.rosalinux.ru/openmandriva/javapackages-tools/blob/master/javapa… and some other rpm macros, to allow mostly unmodified fedora specs. I know some people will just say I was cheap and did just copy work from others, that probably is true :-) I basically ported f20 packages, on a few exceptions I fetched FTBFS corrections from rawhide, or when trivial did it myself, but 99% of the packages rebuilt properly. Thanks, Paulo

3 2

New Packaging Guidelines Vote
by Stanislav Ochotnicky 16 Jan '14

16 Jan '14

I want to give our current packaging draft[1] to FPC for approval. The diff is relatively big. See original announcement from October[2] for more details. To simplify/speed up vote please reply to this email with +1 votes, or comments if you'd like some changes done to the draft before I pass it on. [1] https://fedoraproject.org/wiki/User:Akurtakov/JavaPackagingDraftUpdate [2] https://lists.fedoraproject.org/pipermail/java-devel/2013-October/005020.ht… -- Stanislav Ochotnicky <sochotnicky(a)redhat.com> Software Engineer - Developer Experience PGP: 7B087241 Red Hat Inc. http://cz.redhat.com

2 3

Packaging tomcat shell scripts
by Robert Rati 16 Jan '14

16 Jan '14

I logged a bz (https://bugzilla.redhat.com/show_bug.cgi?id=990588) to request that the tomcat shell scripts (catalina.sh and the rest) be packaged. I've had some discussions with the person the bz is assigned to and few others, but no one knows why the scripts were not packaged. Nor, it seems, does anyone see a problem with them being packaged as far as I can tell. Does anyone know some history here? Rob

5 22

Netty upgraded to 4.0.14 in Rawhide
by Marek Goldmann 13 Jan '14

13 Jan '14

Hiya, Today I upgraded the netty package in Rawhide to version 4.0.14.Final. Most probably this will break some packages - be prepared to patch your packages if necessary. https://bugzilla.redhat.com/show_bug.cgi?id=1052047 The ideal case would be to not introduce any netty 3 compat package, so please do everything to not require netty 3. Thanks! --Marek

1 0

Heads-up: Upcoming netty major version update in Rawhide (Will Break Stuff)
by Jon VanAlten 02 Jan '14

02 Jan '14

Hi Java folks, The current netty in Fedora is 3.6.3. There are newer updates to 3.X series upstream but also for some time now 4.X series has been available. In the spirit of keeping the most up to date version in our distro, I aim/plan to update this in rawhide in the coming weeks. However, there have been some changes upstream that any maintainers of packages which depend on netty will need to be aware of. Those packages are: async-http-client bookkeeper eclipse-m2e-core hadoop hornetq littleproxy resteasy thermostat zookeeper In addition, we currently have a compat netty31 package, which is used only by the eucalyptus package. I'd also like to encourage the maintainer of eucalyptus to look into porting to the newer netty, so this longstanding compat package can be retired. (Well, there are other packages that "repoquery --whatrequires netty31" returns, but inspection of .spec shows that they only Require: netty without a version; only eucalyptus has an explicit requirement for netty31.) So, what are the implications of this update? Well, upstream netty has moved from being a jboss project to being independent at netty.io, and has changed their package namespace accordingly. In addition, some key API classes have slightly changed names. Finally, and I haven't looked deep at this part yet, but it seems there are some other incompatible API changes. Any package currently using netty will *at least* require a search-and- replace for package/class name changes, and may require more indepth fixes in order to work with the most recent upstream releases. The bulk of the changes came with the 4.0 release, and conveniently enough upstream made a single commit updating most of their example code at once[1] which is likely to be a good reference for anyone porting an application. I'll be starting on this work around mid-November. My plan is to first create package of the newest netty release at the time but not push to rawhide just yet, rather make srpm available to interested maintainers via other means. Then, as co-maintainer of thermostat, I will help to port that package to the new netty API. I hope around this same time maintainers of other packages will do same. To me, this will act as "sanity check" for the updated netty package, and if this check is successful, I'll then push the netty changes to rawhide. If all goes well, this should be done by the end of November (modulo a week or so). Please, if you have any concerns with this plan, speak up! Otherwise, wait for my email in a few weeks with .srpm to play with :) cheers, jon P.S. I *really* hope that at the end of all this we are not left with *two* compat packages for netty, ie I hope that either eucalyptus is able to port or that all of the others are able to port, or even better both of the above. [1] https://github.com/netty/netty/commit/8237afff64509520865c08bf4f5fd130e06ae…

5 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

java-devel January 2014