You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by mraible <ma...@raibledesigns.com> on 2008/05/06 22:24:26 UTC
Re: Is it possible to use the maven-bundle-plugin on a WAR project?
Stuart McCulloch-3 wrote:
>
> On 24/04/2008, mraible <ma...@raibledesigns.com> wrote:
>>
>> For some reason, the following doesn't work for me:
>>
>> <plugin>
>> <artifactId>maven-war-plugin</artifactId>
>> <configuration>
>> <archive>
>>
>>
>> <!--manifestFile>src/main/webapp/META-INF/MANIFEST.MF</manifestFile-->
>>
>>
>> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
>> </archive>
>> </configuration>
>> </plugin>
>> <plugin>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>maven-bundle-plugin</artifactId>
>> <extensions>true</extensions>
>> <version>1.4.0</version>
>> <configuration>
>> <instructions>
>> <!-- bundle specific conf -->
>> <Bundle-Name>${artifactId}</Bundle-Name>
>> <Bundle-SymbolicName>${osgi.symbolic.name}</Bundle-SymbolicName>
>> <Export-Package>${osgi.export.pkg}</Export-Package>
>> <Import-Package>${osgi.import.pkg}</Import-Package>
>> <Private-Package>${osgi.private.pkg}</Private-Package>
>> <!-- jar entries -->
>>
>>
>> <Embed-Dependency>*;scope=compile|runtime;inline=false</Embed-Dependency>
>> <Embed-Directory>WEB-INF/lib</Embed-Directory>
>> <Embed-Transitive>true</Embed-Transitive>
>>
>>
>> <Implementation-Title>MyApp</Implementation-Title>
>> <Implementation-Version>${pom.version}</Implementation-Version>
>> <Implementation-Vendor>AppFuse</Implementation-Vendor>
>> <Implementation-Vendor-Id>org.appfuse</Implementation-Vendor-Id>
>> <!-- Spring specific entries -->
>> <Spring-DM-Version>${spring.dm.version}</Spring-DM-Version>
>> <Spring-Version>${spring.version}</Spring-Version>
>> </instructions>
>> </configuration>
>> <executions>
>> <execution>
>> <id>bundle-manifest</id>
>> <phase>process-classes</phase>
>> <goals>
>> <goal>manifest</goal>
>> </goals>
>> </execution>
>> </executions>
>> </plugin>
>>
>> The plugin looks like it's running:
>>
>> [INFO] [bundle:manifest {execution: bundle-manifest}]
>>
>> But no manifest is created.
>>
>> Any ideas?
>
>
> yep, by default the bundleplugin ignores project types that are not bundle
> or jar
> (this feature was requested by people using bundleall with multi-module
> builds)
>
> a debug message was printed to show when this happened (-X) which wasn't
> that useful, so in 1.4.1-SNAPSHOT I changed this to be a warning message:
>
> [WARNING] Ignoring project type war - supportedProjectTypes = [jar,
> bundle]
>
> you can then configure the bundleplugin supportedProjectTypes to include
> war:
>
> <configuration>
> <supportedProjectTypes>
> jar
> bundle
> war
> </supportedProjectTypes>
> <instructions>
> <!-- etc... -->
> </instructions>
> </configuration>
>
> I hope to release 1.4.1 rsn...
>
> HTH
>
> Cheers, Stuart
>
>
Is there a published SNAPSHOT of 1.4.1 that I can try? Is "rsn" this week?
;-)
Thanks,
Matt
--
View this message in context: http://www.nabble.com/Is-it-possible-to-use-the-maven-bundle-plugin-on-a-WAR-project--tp16763483p17091071.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Is it possible to use the maven-bundle-plugin on a WAR project?
Posted by Mike Smoot <ms...@ucsd.edu>.
There's a snapshot here:
http://people.apache.org/maven-snapshot-repository
Although I'm not sure if contains the fix you're looking for.
Mike
On Tue, May 6, 2008 at 1:24 PM, mraible <ma...@raibledesigns.com> wrote:
>
>
>
> Stuart McCulloch-3 wrote:
> >
> > On 24/04/2008, mraible <ma...@raibledesigns.com> wrote:
> >>
> >> For some reason, the following doesn't work for me:
> >>
> >> <plugin>
> >> <artifactId>maven-war-plugin</artifactId>
> >> <configuration>
> >> <archive>
> >>
> >>
> >> <!--manifestFile>src/main/webapp/META-INF/MANIFEST.MF</manifestFile-->
> >>
> >>
> >>
> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
> >> </archive>
> >> </configuration>
> >> </plugin>
> >> <plugin>
> >> <groupId>org.apache.felix</groupId>
> >> <artifactId>maven-bundle-plugin</artifactId>
> >> <extensions>true</extensions>
> >> <version>1.4.0</version>
> >> <configuration>
> >> <instructions>
> >> <!-- bundle specific conf -->
> >> <Bundle-Name>${artifactId}</Bundle-Name>
> >> <Bundle-SymbolicName>${osgi.symbolic.name}</Bundle-SymbolicName>
> >> <Export-Package>${osgi.export.pkg}</Export-Package>
> >> <Import-Package>${osgi.import.pkg}</Import-Package>
> >> <Private-Package>${osgi.private.pkg}</Private-Package>
> >> <!-- jar entries -->
> >>
> >>
> >>
> <Embed-Dependency>*;scope=compile|runtime;inline=false</Embed-Dependency>
> >> <Embed-Directory>WEB-INF/lib</Embed-Directory>
> >> <Embed-Transitive>true</Embed-Transitive>
> >>
> >>
> >> <Implementation-Title>MyApp</Implementation-Title>
> >> <Implementation-Version>${pom.version}</Implementation-Version>
> >> <Implementation-Vendor>AppFuse</Implementation-Vendor>
> >> <Implementation-Vendor-Id>org.appfuse</Implementation-Vendor-Id>
> >> <!-- Spring specific entries -->
> >> <Spring-DM-Version>${spring.dm.version}</Spring-DM-Version>
> >> <Spring-Version>${spring.version}</Spring-Version>
> >> </instructions>
> >> </configuration>
> >> <executions>
> >> <execution>
> >> <id>bundle-manifest</id>
> >> <phase>process-classes</phase>
> >> <goals>
> >> <goal>manifest</goal>
> >> </goals>
> >> </execution>
> >> </executions>
> >> </plugin>
> >>
> >> The plugin looks like it's running:
> >>
> >> [INFO] [bundle:manifest {execution: bundle-manifest}]
> >>
> >> But no manifest is created.
> >>
> >> Any ideas?
> >
> >
> > yep, by default the bundleplugin ignores project types that are not
> bundle
> > or jar
> > (this feature was requested by people using bundleall with multi-module
> > builds)
> >
> > a debug message was printed to show when this happened (-X) which wasn't
> > that useful, so in 1.4.1-SNAPSHOT I changed this to be a warning
> message:
> >
> > [WARNING] Ignoring project type war - supportedProjectTypes = [jar,
> > bundle]
> >
> > you can then configure the bundleplugin supportedProjectTypes to include
> > war:
> >
> > <configuration>
> > <supportedProjectTypes>
> > jar
> > bundle
> > war
> > </supportedProjectTypes>
> > <instructions>
> > <!-- etc... -->
> > </instructions>
> > </configuration>
> >
> > I hope to release 1.4.1 rsn...
> >
> > HTH
> >
> > Cheers, Stuart
> >
> >
>
> Is there a published SNAPSHOT of 1.4.1 that I can try? Is "rsn" this week?
> ;-)
>
> Thanks,
>
> Matt
>
> --
> View this message in context:
> http://www.nabble.com/Is-it-possible-to-use-the-maven-bundle-plugin-on-a-WAR-project--tp16763483p17091071.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
____________________________________________________________
Michael Smoot, Ph.D. Bioengineering Department
tel: 858-822-4756 University of California San Diego
Re: Is it possible to use the maven-bundle-plugin on a WAR project?
Posted by Stuart McCulloch <st...@jayway.net>.
2008/5/7 mraible <ma...@raibledesigns.com>:
>
>
>
> Stuart McCulloch-3 wrote:
> >
> > On 24/04/2008, mraible <ma...@raibledesigns.com> wrote:
> >>
> >> For some reason, the following doesn't work for me:
> >>
> >> <plugin>
> >> <artifactId>maven-war-plugin</artifactId>
> >> <configuration>
> >> <archive>
> >>
> >>
> >> <!--manifestFile>src/main/webapp/META-INF/MANIFEST.MF</manifestFile-->
> >>
> >>
> >>
> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
> >> </archive>
> >> </configuration>
> >> </plugin>
> >> <plugin>
> >> <groupId>org.apache.felix</groupId>
> >> <artifactId>maven-bundle-plugin</artifactId>
> >> <extensions>true</extensions>
> >> <version>1.4.0</version>
> >> <configuration>
> >> <instructions>
> >> <!-- bundle specific conf -->
> >> <Bundle-Name>${artifactId}</Bundle-Name>
> >> <Bundle-SymbolicName>${osgi.symbolic.name}</Bundle-SymbolicName>
> >> <Export-Package>${osgi.export.pkg}</Export-Package>
> >> <Import-Package>${osgi.import.pkg}</Import-Package>
> >> <Private-Package>${osgi.private.pkg}</Private-Package>
> >> <!-- jar entries -->
> >>
> >>
> >>
> <Embed-Dependency>*;scope=compile|runtime;inline=false</Embed-Dependency>
> >> <Embed-Directory>WEB-INF/lib</Embed-Directory>
> >> <Embed-Transitive>true</Embed-Transitive>
> >>
> >>
> >> <Implementation-Title>MyApp</Implementation-Title>
> >> <Implementation-Version>${pom.version}</Implementation-Version>
> >> <Implementation-Vendor>AppFuse</Implementation-Vendor>
> >> <Implementation-Vendor-Id>org.appfuse</Implementation-Vendor-Id>
> >> <!-- Spring specific entries -->
> >> <Spring-DM-Version>${spring.dm.version}</Spring-DM-Version>
> >> <Spring-Version>${spring.version}</Spring-Version>
> >> </instructions>
> >> </configuration>
> >> <executions>
> >> <execution>
> >> <id>bundle-manifest</id>
> >> <phase>process-classes</phase>
> >> <goals>
> >> <goal>manifest</goal>
> >> </goals>
> >> </execution>
> >> </executions>
> >> </plugin>
> >>
> >> The plugin looks like it's running:
> >>
> >> [INFO] [bundle:manifest {execution: bundle-manifest}]
> >>
> >> But no manifest is created.
> >>
> >> Any ideas?
> >
> >
> > yep, by default the bundleplugin ignores project types that are not
> bundle
> > or jar
> > (this feature was requested by people using bundleall with multi-module
> > builds)
> >
> > a debug message was printed to show when this happened (-X) which wasn't
> > that useful, so in 1.4.1-SNAPSHOT I changed this to be a warning
> message:
> >
> > [WARNING] Ignoring project type war - supportedProjectTypes = [jar,
> > bundle]
> >
> > you can then configure the bundleplugin supportedProjectTypes to include
> > war:
> >
> > <configuration>
> > <supportedProjectTypes>
> > jar
> > bundle
> > war
> > </supportedProjectTypes>
> > <instructions>
> > <!-- etc... -->
> > </instructions>
> > </configuration>
> >
> > I hope to release 1.4.1 rsn...
> >
> > HTH
> >
> > Cheers, Stuart
> >
> >
>
> Is there a published SNAPSHOT of 1.4.1 that I can try? Is "rsn" this week?
> ;-)
>
the 1.4.1 release candidate that's currently being voted on is here:
http://people.apache.org/~mcculls/releases/felix/maven-bundle-plugin
(maven-repository structure - the actual bundle jar is beneath org/...)
but 1.4.0 has the <supportedProjectTypes> option already, the fix in 1.4.1
is to surface the message about unsupported project types as a warning,
whereas in 1.4.0 it was just a debug message
Thanks,
>
> Matt
>
> --
> View this message in context:
> http://www.nabble.com/Is-it-possible-to-use-the-maven-bundle-plugin-on-a-WAR-project--tp16763483p17091071.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Cheers, Stuart