[jira] Issue Comment Edited: (MWAR-167) Final manifest not written to exploded location

["Haikal Saadh (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187320#action_187320 ] 

Haikal Saadh edited comment on MWAR-167 at 8/16/09 11:14 PM:
-------------------------------------------------------------

This is important so that, say, Spring Tools Suite for eclipse can deploy a war project to DM Server. 

Funny thing is, with 2.1-beta-1, if you do either a war:war, *or* a war:exploded, the custom manifest (generated by maven-bundle-plugin) is ignored, BUT if I do a maven package, the output directory contains the correct manifest.

Here's an extract from the pom I'm using. I've tried various configs, but this is the only one what gives me the right manifest at the right place:

{code}<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  ...
  <groupId>osgi.hello</groupId>
  <artifactId>speaker.web</artifactId>
  <packaging>war</packaging>
  ...
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-war-plugin</artifactId>
        <version>2.1-beta-1</version>
        <configuration>
          <packagingExcludes>WEB-INF/lib/**</packagingExcludes>
          <archive>
            <manifestFile>${project.build.directory}/${project.build.finalName}/META-INF/MANIFEST.MF</manifestFile>
          </archive>
        </configuration>
      </plugin>
      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <executions>
          <execution>
            <id>bundle-manifest</id>
            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <manifestLocation>${project.build.directory}/${project.build.finalName}/META-INF</manifestLocation>
          <supportedProjectTypes>
            <supportedProjectType>jar</supportedProjectType>
            <supportedProjectType>bundle</supportedProjectType>
            <supportedProjectType>war</supportedProjectType>
          </supportedProjectTypes>
          <instructions>
            ...
          </instructions>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>{code}

      was (Author: tunaranch):
    This is important so that, say, Spring Tools Suite for eclipse can deploy a war project to DM Server. 

Funny thing is, with 2.1-beta-1, if you do either a war:war, *or* a war:exploded, the custom manifest (generated by maven-bundle-plugin) is ignored, BUT if I do a maven package, the output directory contains the correct manifest.

Here's an extract from the pom I'm using. I've tried various configs, but this is the only one what gives me the right manifest at the right place:

{code}<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  ...
  <groupId>osgi.hello</groupId>
  <artifactId>speaker.web</artifactId>
  <packaging>bundle</packaging>
  ...
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-war-plugin</artifactId>
        <version>2.1-beta-1</version>
        <configuration>
          <packagingExcludes>WEB-INF/lib/**</packagingExcludes>
          <archive>
            <manifestFile>${project.build.directory}/${project.build.finalName}/META-INF/MANIFEST.MF</manifestFile>
          </archive>
        </configuration>
      </plugin>
      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <executions>
          <execution>
            <id>bundle-manifest</id>
            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <manifestLocation>${project.build.directory}/${project.build.finalName}/META-INF</manifestLocation>
          <supportedProjectTypes>
            <supportedProjectType>jar</supportedProjectType>
            <supportedProjectType>bundle</supportedProjectType>
            <supportedProjectType>war</supportedProjectType>
          </supportedProjectTypes>
          <instructions>
            ...
          </instructions>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>{code}
  
> Final manifest not written to exploded location
> -----------------------------------------------
>
>                 Key: MWAR-167
>                 URL: http://jira.codehaus.org/browse/MWAR-167
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-1
>            Reporter: Paul Benedict
>            Priority: Minor
>
> When I open up my generated WAR file, the Manifest file contains all the entries I specified. This is correct. However, when I look into the exploded location, it's just the file I had in my project to begin with.
> The exploded Manifest should be updated with the final contents.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira