Did you make the groupId muse.osgi-bundles when you tried to put it in the
parent POM (/modules/osgi-bundles/pom.xml)? Or did you only try and do it
in /modules/pom.xml? It might have failed on the OSGi bundle creation
because they have a different groupId.
Also, is /target/classes right? I thought the POMs were changed to use the
default output directory, which puts the classes and JAR file right under
/target.
Dan
"Hawkins, Joel" <[EMAIL PROTECTED]> wrote on 09/12/2006 01:00:57
PM:
> Adding the following block to the OSGi pom.xmls seems to do the trick
for
> creating an all-inclusive bundle:
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>dependency-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>unpack</id>
> <phase>compile</phase>
> <goals>
> <goal>unpack</goal>
> </goals>
> <configuration>
> <artifactItems>
> <artifactItem>
> <groupId>muse</groupId>
> <artifactId>${artifactId}</artifactId>
> <version>2.0.0</version>
> <type>jar</type>
> <outputDirectory>target/classes</outputDirectory>
> </artifactItem>
> </artifactItems>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
>
> Sadly, adding this block to the parent pom.xml doesn?t work, so a change
would
> be required to each bundle?s pom. Any of our Maven mavens wanna hop in
at this
> point, feel free. J
>
> I haven?t figured out how to do the two-stage packaging (as far as I can
tell,
> Maven only gives you one shot at the packaging lifecycle step).
>
> Thoughts?
>
> Joel
>
>
>
> -----Original Message-----
> From: Andrew Eberbach [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2006 11:05 AM
> To: [email protected]
> Subject: RE: [jira] Created: (MUSE-99) Package the code in the OSGi
bundles into a jar
>
>
> No no no.
>
> I'm talking about the osgi-specific code. The code in muse-osgi-core for
example.
>
> for example. muse-osgi-core when unpacked has the following entries:
>
> META-INF/
> org/
> resources/
>
> all I'm saying is put the org folder into a jar called
muse-osgi-runtime.jar
> or something like that and put that jar in the bundle classpath.
>
> Thanks,
> Andrew
>
> Andrew Eberbach
> Autonomic Computing
> (919) 254-2645
> T/L: 444-2645
> [EMAIL PROTECTED]
>
> Daniel Jemiolo/Durham/[EMAIL PROTECTED]
> 09/12/2006 10:58 AM
>
> Please respond to
> [email protected]
>
> To
>
> [email protected]
>
> cc
>
>
>
> Subject
>
> RE: [jira] Created: (MUSE-99) Package the code in the OSGi bundles into
a jar
>
>
>
>
>
>
>
>
>
>
> The unjar/rejar thing seems rather complicated, which is why I liked
your
> original build. Andrew, can you describe the specific TPTP issue in a
> little more detail so we can think about solutions to this?
>
> Dan
>
>
> "Hawkins, Joel" <[EMAIL PROTECTED]> wrote on 09/12/2006
10:53:36
> AM:
>
> > Ideally, all the code for each OSGi bundle would be in one jar. The
> > issue is that OSGi's classpath code can't deal with nested jars. To do
> > this, we need to unjar the core muse jars and re-jar them with the new
> > (osgi) manifest and additional classes/resources.
> >
> > This would be simple using ant - any idea how to do it with MAVEN?
> >
> > I'd originally had the build create jars that were essentially these
> > nested jars - you unpacked the build results and wound up with the
> > exploded plug-in deployment. I suppose it would be easy to create two
> > jars (one for the core stuff, one for the osgi-specific stuff). Is
this
> > what you want, or would you prefer the full-boat unjar/rejar version?
> >
> >
> > -----Original Message-----
> > From: Andrew Eberbach (JIRA) [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, September 12, 2006 10:42 AM
> > To: [email protected]
> > Subject: [jira] Created: (MUSE-99) Package the code in the OSGi
bundles
> > into a jar
> >
> > Package the code in the OSGi bundles into a jar
> > -----------------------------------------------
> >
> > Key: MUSE-99
> > URL: http://issues.apache.org/jira/browse/MUSE-99
> > Project: Muse
> > Issue Type: Improvement
> > Components: Deployment - OSGi
> > Affects Versions: 2.0.0 M2, 2.0.0 M1, 2.0.0
> > Reporter: Andrew Eberbach
> > Assigned To: Dan Jemiolo
> >
> >
> > Can the code from the OSGi bundles (osgi.core, etc) be put into a jar
> > that sits inside the bundle and is on the bundle classpath? This would
> > help greatly with copying over to TPTP. Current the code sits in the
> > unpacked java class structure (ie a folder called org, with a
subfolder
> > apache and so on).
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the
administrators:
> > http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> > http://www.atlassian.com/software/jira
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > The contents of this e-mail are intended for the named addressee only.
> It
> > contains information that may be confidential. Unless you are the
named
> > addressee or an authorized designee, you may not copy or use it, or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> >
> > ---------------------------------------------------------------------
> > 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]
> =00The contents of this e-mail are intended for the named addressee
only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
