Thanx,

The spring-osgi example will be fine. actually I'm using it for the same
purpose.

Alin

On 3/15/07, Stuart McCulloch <[EMAIL PROTECTED]> wrote:

Example using the maven-antrun-plugin:

        <plugin>
          <artifactId>maven-antrun-plugin</artifactId>
          <executions>
            <execution>
              <id>unpack-manifest</id>
              <phase>package</phase>
              <goals>
                <goal>run</goal>
              </goals>
              <configuration>
                <tasks>
                  <unjar src="${bundle.location}" dest="${project.basedir
}">
                    <patternset>
                      <include name="META-INF/MANIFEST.MF"/>
                    </patternset>
                  </unjar>
                </tasks>
              </configuration>
            </execution>
          </executions>
        </plugin>

where bundle.location is a property set in the pom:

  <properties>
    <bundle.location>${project.build.directory}/${project.build.finalName
}.jar</bundle.location>
  </properties>

Same example using the exec-maven-plugin:

        <plugin>
          <groupId>org.codehaus.mojo</groupId>
          <artifactId>exec-maven-plugin</artifactId>
          <executions>
            <execution>
              <id>unpack-manifest</id>
              <phase>package</phase>
              <goals>
                <goal>exec</goal>
              </goals>
              <configuration>
                <executable>${java.home}/bin/jar</executable>
                <arguments>
                  <argument>-xvf</argument>
                  <argument>${bundle.location}</argument>
                  <argument>META-INF/MANIFEST.MF</argument>
                </arguments>
              </configuration>
            </execution>
          </executions>
        </plugin>

I have a more complete example, where I've refactored a subset of the
Spring-OSGi project to try and smooth the maven-eclipse integration.

I'll see if I can make it available this afternoon - hope you find it
useful.

Cheers, Stuart

On 15/03/07, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
> Thanx Stuart,
>
> Can you post an example?
> But most of all I wanted built in. Can be done as proven by carlos, it's
> already there and is very useful for the eclipse case.
>
> Alin Dreghiciu
>
> On 3/15/07, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> >
> > A quick workaround is to extract it from the jar at the end of the
package
> > phase, using either the exec-maven-plugin or the maven-antrun-plugin.
> >
> > On 15/03/07, Alin Dreghiciu (JIRA) <[EMAIL PROTECTED]> wrote:
> > > maven-bundle-plugin and manifest generation outside the bundle (jar)
> > > --------------------------------------------------------------------
> > >
> > >                  Key: FELIX-257
> > >                  URL:
https://issues.apache.org/jira/browse/FELIX-257
> > >              Project: Felix
> > >           Issue Type: New Feature
> > >           Components: Maven Plugin
> > >             Reporter: Alin Dreghiciu
> > >
> > >
> > > I (and as I see some other more) would like to be able to get the
> > manifest generated by maven-bundle-plugin also outside the generated
bundle.
> > > A use case is the development using the PDE support form Eclipse.
This
> > requires the manifest in a specific location and I would love to have
it
> > generated by maven-bundle-plugin/bnd. In this way we can eliminate the
> > necesity of maintaining 2 manifests (one manifest and the settings
from
> > pom).and will be for sure less error prone as you will be able to use
for
> > development the same manifest you would have in runtime.
> > >
> > > There is already done by carlos sanchez on FELIX-199.
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
>

Reply via email to