Patrick Forhan wrote:
Note that a bundle is simply a JAR file with extra metadata. A
non-osgi container can use them as-is. To that end, when we have
bundles that end up on a server, we simply leave them as bundles and
add them to the classpath or WAR, etc that is deployed.
Keep in mind that a normal JAR file is always a bundle, but a bundle is
not always a normal JAR file. If you embed JAR files or native libraries
in your bundle, then you cannot use it as a normal JAR file.
-> richard
Pat.
On Tue, Jan 27, 2009 at 5:24 AM, Henri Gomez <[email protected]> wrote:
Hi to all,
We're using maven to build all our company projects for about 6 months
and are very happy with it.
Some of our projects, mainly Eclipse RCP plugins, are also mavenized.
We know think about OSGIfing more of our projects (server side) and
track ASF projects Felix of course core but also ServiceMix Kernel.
BTW, we wonder if there is a consensus or strategy about OSGIfied
artifacts and their location in external repositories.
- Should we repackage our current projects to produce both jar and plugins ?
- How and where to store these artifacts to make sure Felix could get
it (did a Nexus repository could do the job).
- How to 'mark' artifacts to indicate the difference between strict
jar and OSIG jars (bundles). Eclipse prefix then with org.eclipse, SS
with com.springsource ?
Advices and experience are more than welcome.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
