Stuart McCulloch-3 wrote:
> 
> On 24/04/2008, mraible <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to