Hello Fedora java developers, i just subscribed to this list.
I'm a Java developer using Fedora as main workstation from quite a long
time, and im willing to give some help if needed.
In particular i could help reviewing and packaging; right now i would help
packaging josm (java open street map). It has many dependencies on
unpackaged maven-plugins, whats the status of maven in Fedora?
Guido Grazioli <guido.grazioli(a)gmail.com>
Via Parri 11 48011 - Alfonsine (RA)
Mobile: +39 347 1017202 (10-18)
Key FP = 7040 F398 0DED A737 7337 DAE1 12DC A698 5E81 2278
Linked in: http://www.linkedin.com/in/guidograzioli
Unfortunately, there is an issue to do with velocity and maven plugins
in F13 and devel. Alexander Kurtakov and I have been working on trying
to fix it, but it's getting a bit ugly, and my time to work on Fedora
things comes and goes with busy-ness at my $DAYJOB ... anyway, we
wanted to explain the situation.
A while ago, I (perhaps rashly) updated velocity in rawhide from 1.4.x
to 1.6.3, and that change has eventually landed in F-13. This update
unfortunately produces errors when making use of maven-doxia, for
example as part of building jetty (which therefore currently FTBFS on
F-13/rawhide). It seems that the current maven-doxia relies on some
velocity 1.4.x features that changed in 1.6.x. :(
So akurtakov and I have been trying to rebuild maven-doxia and its
dependencies to get around this. We managed to get some way along this
path: we have SRPMs for new versions of maven-doxia,
maven-doxia-sitetools, and plexus-utils. But rebuilding these things
in turn breaks a number of maven plugins, including javadoc-plugin and
site-plugin. Alexander has managed to create an SRPM of the javadoc
plugin that builds, and I'm currently working on the site-plugin, but
this still seems like the tip of the iceberg. Also, various annoying
issues come up because the Fedora is still on maven 2.0.8, and a lot
of the latest plugin versions that work with the new doxia require
newer versions of maven to build.
I'm starting to think that it's best to (*shudder*) add an Epoch to
velocity in F-13 and downgrade it back to 1.4 so that at least it's
not broken when it's released. We can then try to work towards fixing
things in devel, possibly as part of a larger maven upgrade.
I'm sorry that things are in this state, but hopefully it's possible to fix ...
Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/
Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab
School of Mathematical and Computer Sciences, Heriot-Watt University
Heriot-Watt University is a Scottish charity registered under charity
Time to bring GCJ support discussion back.
We should find a way to not install java-1.5.0-gcj on every users computers.
There are packages that do not work with it and it's plain wrong to install it
as a dependency of this packages which are explicitly requiring java 1.6.0.
* Solution 1 - someone who cares for the gcj stack finds a way to not require
java-1.5.0-gcj when there are gcj bits in the package so we do not force gcj
installation on every user.
* Solution 2 - drop gcj support from packages, interested maintainers can add
gcj bits as a subpackage which requires java-1.5.0-gcj. I think that this is
what Debian is doing.
I will also propose changing Java Packaging Guidelines to not require or
recommend the addition of gcj support bits.
Has anyone dealt with any projects that use ivy? Appears to be similar
to maven and downloads jars automatically, so it's probably going to
need similar treatment to maven in the build system.
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Just looking at pending OpenJDK updates  and it looks like the F12
version-release is higher than the F13 version-release. This might be
a problem, and might explain why my F13 box has 184.108.40.206-36.b17.fc12
installed when presumably I should have 220.127.116.11-35.b17.fc13 installed.