java-devel January 2016

java-devel@lists.fedoraproject.org

17 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

building new tuxguitar with maven
by Orcan Ogetbil 01 Feb '16

01 Feb '16

Hi folks, It's been a while. I am giving a shot to update our tuxguitar package from 1.2 to the recent 1.3. The new release comes with a build system switch from ant to maven. I do not have much experience with maven, so I tried to follow the packaging instructions [1] which I found quite useful. I managed to build the package from source, but I still have 4 problems: 1- tuxguitar-1.3 has an itext5 dependency, but we only ship itext2 in Fedora. I tried to disable the tuxguitar-pdf plugin (which uses itext) by various combinations of %pom_remove_dep, %pom_remove_plugin, %pom_disable_module. The following takes me a couple steps further %pom_remove_dep -r com.itextpdf:itextpdf %pom_remove_dep -r com.itextpdf.tool:xmlworker but I end up getting: [ERROR] Failed to execute goal on project tuxguitar-pdf: Could not resolve dependencies for project org.herac.tuxguitar:tuxguitar-pdf:jar:1.3.0: The following artifacts could not be resolved: com.itextpdf:itextpdf:jar:SYSTEM, com.itextpdf.tool:xmlworker:jar:SYSTEM: Cannot access swt-repo (https://swt-repo.googlecode.com/svn/repo/) in offline mode and the artifact com.itextpdf:itextpdf:jar:SYSTEM has not been downloaded from it before. -> [Help 1] So, I worked around by patching the pom.xml file and removed the dependency by hand. I am pretty sure there is a better way of doing this with the maven macros. 2- When the package is built with %mvn_build and installed with %mvn_install the jar files get installed into /usr/share/java/tuxguitar/. But looking at the launcher script, the application expects the jar files to be in /usr/share/tuxguitar/. Is there a way to tell maven to install the jar files there instead (these are application jars, not shared libraries) ? 3- I manually moved the jar files into /usr/share/tuxguitar/. The launcher calls the entry point in tuxguitar.jar. But this jar doesn't find the other jars, for example the tuxguitar-editor-utils.jar, and the application doesn't launch. I can add this jar file and the other 15 jar files to the CLASSPATH in the lancher script, but I am not sure this is the right way. I didn't have to do this with ant. With ant, the tuxguitar.jar somehow knew about the other jars. How can we fix this? 4- There are a bunch of supplementary files (.desktop file, icons, mime xmls, the launcher script etc) which are listed in the main pom.xml file, but %mvn_install doesn't install them. I had to copy them manually to the $RPM_BUILD_ROOT. Is there a way to do this with better? My current work is at https://oget.fedorapeople.org/tuxguitar/tuxguitar.spec https://oget.fedorapeople.org/tuxguitar/tuxguitar-1.3.0-0.fc23.src.rpm Note that I had to remove some SF2, EXE and DLL files from the source tarball, as their license situations were unclear. I would be happy if someone knowledgeable with maven could take a look and give me some clues. Best, Orcan [1] https://fedorahosted.org/released/javapackages/doc/#maven

4 8

Heads-up: mongo-java-driver 3.x coming in rawhide
by Severin Gehwolf 28 Jan '16

28 Jan '16

Hi, I'm going to update mongo-java-driver to version 3.x in rawhide soon (probably Monday). Please let me know if your package isn't 100% 3.x compatible and I'll help you get it migrated. A scratch build for testing is available here: http://koji.fedoraproject.org/koji/taskinfo?taskID=12649172 Thanks, Severin

2 2

SpagoBI - restito dependency
by Sandro Bonazzola 25 Jan '16

25 Jan '16

Hi, here's another dependency for SpagoBI. Looks like the gradle macro works only on Rawhide and the javadoc build fails. How should I replace the gradle macro on FC23 and EL7? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Is there a good newbie tutorial for jboss under Fedora 23?
by John W. Himpel 24 Jan '16

24 Jan '16

Good afternoon, In the past, I have done JEE development in a corporate environment (I was a developer not an admin) and am looking to start my own web site using JBoss. I have found several tutorials on installing JBoss, but most do not assume Fedora packaging. Would someone be so kind as to point me to a tutorial (or HOWTO) on installing and starting JBoss on a recent version of Fedora? I'm assuming JBoss is the JEE server of choice in Fedora. If it isn't, what would be the JEE server of choice? If this is the wrong list, please excuse my unfamiliarity. Any references to a possibly better list, would be appreciated. Thanks.

4 3

WILDFLY: Packaging errors and cannot deploy quickstart application
by John W. Himpel 23 Jan '16

23 Jan '16

Good morning, While attempting to install and startup Wildfly under F23, I encountered several packaging errors. They are shown in https://bugzilla.redhat.com/show_bug.cgi?id=1226991. I did apply the "fix" shown in comment #1 and comment #2. Now Wildfly does start using "standalone.sh", but I get the following stacktrace: 11:13:18,174 ERROR [org.jboss.msc.service.fail] (MSC service thread 1- 2) MSC000001: Failed to start service jboss.ws.endpoint- config.Recording-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContro llerImpl.java:1904) [jboss-msc.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja va:1142) [rt.jar:1.8.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j ava:617) [rt.jar:1.8.0_65] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] Caused by: java.lang.NoSuchMethodError: org.jboss.wsf.spi.metadata.config.EndpointConfig: method <init>()V not found at org.jboss.as.webservices.service.ConfigService.start(ConfigService.java :65) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Serv iceControllerImpl.java:1948) [jboss-msc.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContro llerImpl.java:1881) [jboss-msc.jar:1.2.2.Final] ... 3 more A little later in the log it says: 11:13:20,072 ERROR [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) JBAS015102: Unable to load console module for slot main, disabling console 11:13:20,078 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 11:13:20,771 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 11:13:20,866 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.ws.client-config.Standard-Client-Config: org.jboss.msc.service.StartException in service jboss.ws.client- config.Standard-Client-Config: Failed to start service service jboss.ws.endpoint-config.Standard-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint- config.Standard-Endpoint-Config: Failed to start service service jboss.ws.endpoint-config.Recording-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint- config.Recording-Endpoint-Config: Failed to start service Wildfly seems to run as it answers web requests, but I cannot seem to deploy the helloworld quickstart. #mvn wildfly:deploy [INFO] ---------------------------------------------------------------- -------- [INFO] BUILD FAILURE [INFO] ---------------------------------------------------------------- -------- [INFO] Total time: 8.124 s [INFO] Finished at: 2016-01-23T11:13:51-06:00 [INFO] Final Memory: 19M/281M [INFO] ---------------------------------------------------------------- -------- [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven- plugin:1.1.0.Alpha5:deploy (default-cli) on project jboss-helloworld: Please make sure a server is running before executing goal deploy on deployment /home/jwhimpel/Downloads/jboss-eap-quickstarts- 6.4.0.GA/helloworld/target/jboss-helloworld.war. Reason: java.net.ConnectException: WFLYPRT0053: Could not connect to http- remoting://192.168.1.188:9990. The connection failed: Connection refuse d -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/Conne ctException Could the two be related? I am using wildfly-8.1.0.3, I see "ausil" and "goldmann" have submitted subsequent builds for wilfly but are marked ad "Failed" in koji. What needs to be done to get a working package of wildfire into Fedora? I am not a packager, but am willing to test and assist in any manner that I can. PS: Attempting to start Wildfly using systemd yields: #systemctl enable wildfly #systemctl start wildfly #journalctl --lines 10 Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked. Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: Started The WildFly Application Server. Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: Starting The WildFly Application Server... Jan 23 11:35:24 dubby.jlhimpel.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=wildfl Jan 23 11:35:26 dubby.jlhimpel.net polkitd[1066]: Unregistered Authentication Agent for unix-process:22770:36862048 (system bus name :1.451, object pat Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Main process exited, code=exited, status=1/FAILURE Jan 23 11:35:26 dubby.jlhimpel.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=wildfly Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Unit entered failed state. Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Failed with result 'exit-code'. Thanks for listening. John

2 1

Packaging Spago BI
by Sandro Bonazzola 21 Jan '16

21 Jan '16

Hi, I started trying to package Spago BI ( http://spagobi.com/ ) for Fedora. An initial spec file I created mostly to understand what's being built is here: https://gerrit.ovirt.org/#/c/52375/1/specs/spagobi/spagobi.spec.in The output of maven install is a set of war files which includes libraries and javascript libraries from external sources / projects (maven central mostly). During the build, several jar files are created and not installed by mvn install. I've searched for a packaging guidelines wiki page about packaging wildfly webapps and in IRC I've been pointed to thermostat package as example. I'm not realy sure to have understood what's expected from the package: - is it ok to just have the final war file in the package? - is it ok to have libraries (jar and js) from other packages included in the war file? (I know, I'm using mvn and not maven-local since I don't have packaged dependencies yet, but supposing they're in fedora, is it allowed to have them in the war file? Help with the packaging effort is welcome :-) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 11

osgi-resource-locator retirements
by gil 15 Jan '16

15 Jan '16

Hi, osgi-resource-locator has been retired It is now provided by glassfish-hk2-osgi-resource-locator >= 2.4.0 regards .g

1 0

Java packages in the RHEL devtoolset
by Julius Schwartzenberg 04 Jan '16

04 Jan '16

Hi, Does anyone here happen to know what would be an appropriate place to discuss the Java packages which are in the RHEL devtoolset? I tried to use Eclipse from the devtoolset-3 (1) on CentOS 7 for instance, but there are multiple bugs which make it unusable. Best regards, Julius (1) https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/

2 1

failed to read link /usr/bin/javaws: No such file or directory
by Sudhir Khanger 04 Jan '16

04 Jan '16

Hi, I installed Oracle JDK on my Fedora 23 KDE box. I setup alternatives as follow [1]. alternatives --install /usr/bin/javaws javaws /usr/java/default/jre/bin/javaws 200000 This doesn't always work and result in the error in the subject like. It can be fixed by following [2]. rm /var/lib/alternatives/javaws alternatives --install /usr/bin/javaws javaws /usr/java/default/jre/bin/javaws 200000 I am curious why does it happen. Why does the link fail? [1] https://github.com/sudhirkhanger/Fedora [2] http://johnglotzer.blogspot.in/2012/09/alternatives-install-gets-stuck-fail… -- Regards, Sudhir Khanger, sudhirkhanger.com.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

java-devel January 2016