ivy
by Orion Poplawski
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.
--
Orion Poplawski
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
13 years, 1 month
jakarta-commons-lang 2.4
by Jerry James
I maintain findbugs, whose latest version needs jakarta-commons-lang
2.4. We currently ship 2.3. The upstream release notes [1][2] claim
that 2.4 has no incompatibilities with 2.3. On the other hand, I see
that jpackage (5.0) has both a jakarta-commons-lang (version 2.3)
package and a jakarta-commons-lang24 package, but I don't know why.
According to repoquery, these packages currently require jakarta-commons-lang:
directory-naming
eclipse-mylyn
findbugs
jakarta-commons-cli
jakarta-commons-configuration
jeuclid
maven2
maven2-plugin-changes
maven2-plugin-enforcer
maven2-plugin-gpg
maven2-plugin-jar
maven2-plugin-javadoc
openoffice.org-wiki-publisher
plexus-registry
Do the maintainers of any of these packages have any reason why
jakarta-commons-lang should not be upgraded from 2.3 to 2.4?
References:
[1] http://commons.apache.org/lang/upgradeto2_4.html
[2] http://commons.apache.org/lang/article2_4.html
--
Jerry James
http://www.jamezone.org/
13 years, 3 months
xerces-j2 unversioned Provides
by Andrew Overholt
Hi,
In xerces-j2 we have an unversioned Provides statement:
Provides: jaxp_parser_impl
Does anyone know what the version of this virtual Provide should be?
Thanks,
Andrew
13 years, 4 months
Re: [fedora-java] Candidate packages for removal due to FTBFS, implications
by Mary Ellen Foster
2010/1/15 Matt Domsch <Matt_Domsch(a)dell.com>:
> OK, re-run, removing the three packages noted as fixed overnight.
>
> -----------------
> Removing geronimo-specs also removes:
[ lots of stuff! ]
Almost all of these are due to the dependency chain jms (virtual
provide) -> avalon-logkit -> velocity -> (all of maven). avalon-logkit
is basically a dead project, and velocity is the only package that
requires it; akurtakov and I are currently working on patching the
avalon-logkit requirement out of velocity (it's only optional anyway),
which should clean things up a bit.
MEF
--
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
number SC000278
13 years, 4 months
Re: [fedora-java] Candidate packages for removal due to FTBFS, implications
by Mary Ellen Foster
2010/1/15 Matt Domsch <Matt_Domsch(a)dell.com>:
> Removing geronimo-specs removes these:
> geronimo-specs-compat-0:1.0-2.M2.fc10.x86_64
Eek! I think geronimo-specs-compat is (transitively) needed by a bunch
of other Java packages including maven; on my computer, "yum remove
geronimo-specs" attempts to remove 45 packages (mostly maven-*). The
issue is that geronimo-specs-compat has a bunch of virtual provides
which don't show up in repoquery.
For reference, repoquery --whatrequires --recursive jms jacc jta ejb |
wc -l returns 112 on my computer (F12, x86_64).
MEF
--
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
number SC000278
13 years, 4 months
Naming packages from apache.org
by Orion Poplawski
crossposting to java and packaging -
Seems like we need an accepted standard for naming packages from
apache.org, particularly commons.apache.org. We already have lots of
"jakarta-commons-*" packages, but now "commons" is an ex-jakarta project
and jakarta.apache.org/commons redirects to commons.apache.org. Same
with jakarta taglibs (although that moved to tomcat).
As of now, the only apache-* package I know of is apache-ivy, which I
would have named simply "ivy". I've got a package request in for
"commons-jexl"[1], but it has been suggested that it be named
apache-commons-jexl. If it were named that I would want a Provides:
commons-jexl much like most jakarta-commons-* packages, so it doesn't
really clean up the namespace any (just adds to it in fact).
commons-* is a lousy name though too, be very generic.
So, I'm fine with either (although I think it's quite possible that
"apache commons" could get renamed again), but at this juncture before a
bunch more packages come in from apache commons, I think we should make
a decision and stick with it.
1 - https://bugzilla.redhat.com/show_bug.cgi?id=531379
--
Orion Poplawski
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
13 years, 4 months
Packaging an eclipse-RCP based app
by stefan riemens
Hi all,
I'm looking into packaging kelpie, a flightplanner for flightgear.
This is a mature app, using the eclipse RCP framework. However, it
appears as if this would be the very first eclipse-rcp app in fedora.
(note, not all dependencies are packaged yet, most notably jogl).
Upstream is very responsive, he's made me an ant build script to start
with. See https://sourceforge.net/projects/fgflightplanner/forums/forum/285350/topi...
for my communication with him.
I was hoping for some guidance, as I don't have java experience yet.
Thanks, Stefan
13 years, 4 months
Update on Soprano/Sesame progress -- review swaps?
by Mary Ellen Foster
For anyone who's still interested in my project to get the Sesame
backend for Sesame packaged, here's the latest...
Unfortunately, I didn't get anything done over the holidays, but I'm
now back and keen to move forwards on this. All of the required
updates to existing Fedora packages have now been made, so the "only"
thing left to do is the reviews of the new packages.
The document at
https://fedoraproject.org/w/uploads/c/c9/Sesame-Dependencies.pdf shows
the current state of the package dependencies. In summary, the most
urgent review at the moment is javamail and then, once that's done,
logback, because the whole chain of aduna-* packages all depend
(directly or indirectly) on logback. xml-security is another
"leaf-node" package that could be done at any time, but it's not
actually needed until all of the other stuff has been processed so
it's less urgent.
I'm willing to review any packages, particularly Java-based packages,
in return for anyone who can review these packages. Once it gets to
the aduna-* packages, the spec files are all nearly identical so
hopefully they can be processed fairly efficiently.
Best wishes,
MEF
--
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
number SC000278
13 years, 5 months
eclipse problems on fedora
by Guy McArthur
Hello, I want to use the Google Eclipse plugin for developing
appengine stuff in fedora 12 x86_64 kde spin but have encountered
serious problems getting this going. The straightforward way,
downloading the whole platform from eclipse.org has a rendering bug.
In the attached screenshot, the Google repository has been added, the
items are there: text shows up when you click in the right areas, but
nothing is shown or selectable. There are other weird problems with
various controls including buttons and dropdowns. This is with both
the latest openjdk and sunjdk. I don't know where in the stack (SWT,
GTK, KDE/Qt, X, ATI radeon driver, SELinux?) the problem could be so
am not sure where to file a bug report.
With the other way, installing eclipse from fedora repositories via
yum, I'm not sure how to add the Google plugin or any of its
dependencies.
What is the path of least resistance here?
13 years, 5 months
xerces-j2 Update
by Mat Booth
Just an FYI because many, many packages use xerces-j2...
I intend to update xerces-j2 from 2.7 to 2.9 (in Rawhide only) once
the package review for xml-stylebook[1] is completed.
Eclipse already expects version 2.9.0 (the OSGi manifest is currently
lying to it) so I don't anticipate any problems in that area.
Hopefully most other packages will be equally unaffected.
Regards,
Mat
[1] https://bugzilla.redhat.com/show_bug.cgi?id=552580
--
Mat Booth
13 years, 5 months
