From: "Jean-Noël Rivasseau" <elvanor@gentoo.org>
To: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: [gentoo-java] On ebuilds using OSGi packaging and revbumps
Date: Wed, 6 Feb 2008 19:50:12 +0100 [thread overview]
Message-ID: <d61c57300802061050u27a9d133iaefa28f43b87154a@mail.gmail.com> (raw)
In-Reply-To: <d61c57300802061010k5a5631f6rf90999462a33dd36@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Hello all,
I just noticed that the commons-logging-r5 ebuild (which is stable now) does
not use anymore the OSGi packaging functions. As a result, this ebuild
produces a bundle not usable with Eclipse, thus Eclipse is currently
unusable (as it depends on >=commons-logging-1.1-r4)
The -r6 ebuild is fine (eg, uses OSGi packaging).
So, as a reminder, when bumping a package using OSGi, *please keep these
functions*. Else the new version won't produce correct bundles. There is NO
need to bump with a version not using OSGi and one using OSGi; all versions
should use OSGi from now on for the following packages (eclipse deps):
>=dev-java/swt-${PV}
>=dev-java/jsch-0.1.36-r1
>=dev-java/icu4j-3.6.1
>=dev-java/commons-el-1.0-r2
>=dev-java/commons-logging-1.1-r4
>=dev-java/tomcat-servlet-api-5.5.25-r1:2.4
dev-java/lucene:1.9
Referenced bug is http://bugs.gentoo.org/show_bug.cgi?id=209087, I will
change the Eclipse ebuild to depend on commons-logging-1.1-r6 to fix it.
Elvanor
[-- Attachment #2: Type: text/html, Size: 1491 bytes --]
next parent reply other threads:[~2008-02-06 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d61c57300802061010k5a5631f6rf90999462a33dd36@mail.gmail.com>
2008-02-06 18:50 ` Jean-Noël Rivasseau [this message]
2008-02-06 21:26 ` [gentoo-java] On ebuilds using OSGi packaging and revbumps Vlastimil Babka
2008-02-07 9:29 ` Jean-Noël Rivasseau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d61c57300802061050u27a9d133iaefa28f43b87154a@mail.gmail.com \
--to=elvanor@gentoo.org \
--cc=gentoo-java@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox