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/
Hello! I've continued working on the process of getting Sesame to
build from source (http://www.openrdf.org/) After a bit of a false
step, it turns out that the one monster horrible package that pulled
in most of the dependencies is only used in one subpackage, which -- I
hope! -- isn't needed for the Sesame backend of Soprano that was the
motivation for this whole undertaking. I *WILL* follow through on the
review requests I put up as part of that initial effort, though --
don't worry, Java people! :)
So anyway, I now have a SRPM of Sesame that builds locally on my
computer after building and installing all of the dependencies. There
are still a fair number of dependencies to get in, but the individual
packages are mostly pretty straightforward. There are also a few
packages already in Fedora which need a minor update so that Sesame
can build against them. I've summarised my progress here:
https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame#The_new_stuff
At this point, I really need to give the review requests that I filed
earlier a bit of love before spamming the review queue again (there
are 16 packages that need to be reviewed before Sesame can be built).
I'd like to review any Java-based packages that are out there in
return -- is there any way to find such packages short of searching
for "java" in the review requests?
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
Hi Everyone,
Sorry for the cross-list posting, but the matter is of interest to both
lists afaict, as I have seen messages related to maven on both.
As some of you might know, we intend to put maven 2.2.1 in rawhide. The
new maven will be a completely re-written rpm, one that should be a lot
easier to maintain, and much more stable. All progress related to this
upgrade is now on the wiki:
https://fedoraproject.org/wiki/MavenUpdate
Updates/new packages for dependencies will be a significant effort. Once
we (Andrew Overholt, Alexander Kurtakov and myself) start work on that, we
will need all the help we can get :) So if you are interested in helping,
or just tracking progress -- that is the page to subscribe to/check out!
I'll send one more mail to this list when work on dependencies starts.
Cheers,
Deepak
Hi Everyone,
as you may or may not know, we started and effort to get IntelliJ IDEA
Community Edition packaged for Fedora 13 [1]. I'm wondering if you find
it useful? If you do, you could help us and your help would really be
appreciated.
This Friday, FESCo [2] will decide whether it's noteworthy enough to be
accepted as Fedora 13 feature. If you think so it might be a good idea
to have a short look at brainstorming page [3] and add your ideas there.
Also you're welcome to join the feature team, hopefully you'll find
everything you need on the feature page [1].
[1] https://fedoraproject.org/wiki/Features/IntelliJ_IDEA
[2] https://fedoraproject.org/wiki/Development/SteeringCommittee
[3] https://fedoraproject.org/wiki/Talk:Features/IntelliJ_IDEA
Regards,
Lubo
--
Flash is the Web2.0 version of blink and animated gifs.
-- Stephen Smoogen
What's the benefit of doing the GCJ AOT-compilation steps as defined
in https://fedoraproject.org/wiki/Packaging/GCJGuidelines? Doesn't
everyone just use OpenJDK these days? It adds a bunch of extra stuff
to every Java spec file and makes all java packages arch-specific
instead of noarch, which always feels a bit weird ...
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
Hi,
I've packaged jai-imageio-core for Fedora, minus the forbidden parts.
With this package, ImageIO.read() and ImageIO.write() will now work with
BMP, GIF, PCX, PNM, raw (not RAW), TIFF, PCX, and WBMP.
Does someone want to review this package? It's at
https://bugzilla.redhat.com/show_bug.cgi?id=536944
Thanks,
Adam
I'm still trying to get jakarta-commons-lang to build with maven
(F-12+ only). I'm getting closer, but I'm having a problem with a
missing jdepend-maven-plugin. This plugin is referred to in at least
two F-12 poms, namely:
/usr/share/maven2/default_poms/JPP-commons-parent.pom
/usr/share/maven2/default_poms/JPP.codehaus-mojo.pom
Both of those poms are supplied by the maven2-common-poms package.
The problem is that I can't find a package that supplies
jdepend-maven-plugin. Does it even exist in Fedora?
--
Jerry James
http://www.jamezone.org/
Looking more closely at my current /etc/maven/maven2-depmap.xml file,
I notice a range of conventions for what fragments are called. Here
are a few examples:
For jakarta-commons-lang (from Fedora):
<dependency>
<maven>
<groupId>lang</groupId>
<artifactId>lang</artifactId>
<version>2.3</version>
</maven>
<jpp>
<groupId>JPP</groupId>
<artifactId>jakarta-commons-lang</artifactId>
<version>2.3</version>
</jpp>
</dependency>
For jakarta-commons-logging (from JPackage):
<dependency>
<maven>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1</version>
</maven>
<jpp>
<groupId>JPP</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1</version>
</jpp>
</dependency>
For ant (from Fedora):
<dependency>
<maven>
<groupId>org.apache.ant</groupId>
<artifactId>ant</artifactId>
<version>1.7.1</version>
</maven>
<jpp>
<groupId>JPP</groupId>
<artifactId>ant</artifactId>
<version>1.7.1</version>
</jpp>
</dependency>
For aqute-bindlib (from Fedora):
<dependency>
<maven>
<groupId>biz.aQute</groupId>
<artifactId>bndlib</artifactId>
<version>0.0.363</version>
</maven>
<jpp>
<groupId>JPP</groupId>
<artifactId>aqute-bndlib</artifactId>
<version>0.0.363</version>
</jpp>
</dependency>
So should the groupId be the package name, the full project name, the
sub-project name, or what? And what's the role of the "JPP" part in
all of this? There seem to be several different conventions going on
...
Thanks for any light you can shed,
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
Hi,
Looks like there's been a regression in F13, because this builds
perfectly on F12:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1794704
This is the interesting part of the build log:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:35:
The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:91:
The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/templates/package-build/customTargets.xml:19:
The following error occurred while executing this line:
java.io.FileNotFoundException:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
(No such file or directory)
Why is ${eclipse.pdebuild.scripts} not defined?
--
Mat Booth
A: Because it destroys the order of the conversation.
Q: Why shouldn't you do it?
A: Posting your reply above the original message.
Q: What is top-posting?
In the course of some other Java stuff, I noticed that the
geronimo-specs package doesn't include Maven depmaps
(https://bugzilla.redhat.com/show_bug.cgi?id=530088) I then decided
to take a look at the actual SRPM itself to see how hard it would be
to add things, and it looks like it's actually *very* old (version
1.0M2, released in August 2004) and it doesn't actually build from
source any more on Rawhide (errors about javax.transaction.*).
What's this package for, anyway? Would it hurt anything to package the
2.1.4 version (March 2009) instead?
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