Kjetil,
I have been using the Felix Bunde plug-in for Maven in various projects. The
most straightforward approach is going for *bundle* packaging. But
unfortunately a lot of other Maven plug-ins do not understand this and will
stop working, hence it is fairly common to stick to *jar* packaging and add
a build specification for the Felix Bundle plug-in like this:

        <plugin>
          <groupId>org.apache.felix</groupId>
          <artifactId>maven-bundle-plugin</artifactId>
          <version>2.0.0</version>
          <extensions>true</extensions>
          <executions>
            <execution>
              <id>create-bundle</id>
              <phase>package</phase>
              <goals>
                <goal>bundle</goal>
              </goals>
            </execution>
            <execution>
              <id>bundle-install</id>
              <phase>install</phase>
              <goals>
                <goal>install</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

In the Lift case this was the way I went initially until David recognized
that the output from the compression of the JavaScript libraries was missing
in the artifacts. Well, the Felix Bundle plug-in just did not pick these. As
I could not spot the reason immediately, I had to go for this way which is
very valid, because the results are as expected.

Of course I would like to stick to the more common approach described above.
Maybe you want to take a look at the POMs and analyze if/how the Felix
Bundle plug-in can pick the compressed JavaScript libraries?

Cheers
Heiko

2009/6/19 Kjetil Valstadsve <[email protected]>

>
> Looking at the OSGi-enabled Lift poms, I find it curious that the M.O.
> for building bundles looks like a two-step:
>
> 1) Build a bundle with maven-bundle-plugin
> 2) Dig out the manifest and use it in the jar
>
> This works ok, but given my experience with Maven, it seems to be a
> case of challenging destiny (Norwegian idiom, sorry); I can vividly
> picture future Mavenisms shuffling the order of plugins somehow,
> wreaking silent havoc.
>
> My preferred approach would be to change the packaging of the pom from
> jar to bundle. From what I can tell, the plugin simply binds to this
> packaging type (or something), and does the same job. I tried this to
> bundle-wrap the  Mapper and the Widgets (trying to deploy my app in
> Felix + Jetty), and it works fine. Should be faster, too.
>
> Unless, of course, I'm missing something here?
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to