You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "David Hawkins (JIRA)" <ji...@codehaus.org> on 2005/11/10 22:29:06 UTC
[jira] Created: (MNG-1507) Merge contents of dependent wars into war being built
Merge contents of dependent wars into war being built
-----------------------------------------------------
Key: MNG-1507
URL: http://jira.codehaus.org/browse/MNG-1507
Project: Maven 2
Type: New Feature
Components: maven-war-plugin
Versions: 2.0
Reporter: David Hawkins
We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied.
Also made a minor change in getExcludes to not add the default excludes from FileUtils. The default excludes were already being added in the method getWarFiles( File sourceDir ) by scanner.addDefaultExcludes().
We are trying to integrate Maven into our environment and not having this functionality was a show-stopper for us. We have applications that reuse jsps, and .tag files from a generic war that need to be included in all of our wars. We have also seen people request this functionality.
By default these changes will have no effect, unless you have wars specified in your <dependencies>.
Here is an example configuration that uses the includes and excludes for the dependent wars.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.0-beta-3-SNAPSHOT</version>
<configuration>
<!-- This is the default for dependentWarIncludes
<dependentWarIncludes>**</dependentWarIncludes>
-->
<dependentWarExcludes>**/*.properties</dependentWarExcludes>
</configuration>
</plugin>
It will not overwrite existing files that are already in the war, the way to get around this is to remove the files you want overwritten using the standard excludes configuration. For example, the following configuration would allow the overwriteme.jar to be overwritten by something in a dependent war.
<configuration>
<excludes>WEB-INF/lib/overwriteme.jar</excludes>
</configuration>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1507) Merge contents of dependent wars into war being built
Posted by "David Hawkins (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1507?page=all ]
David Hawkins updated MNG-1507:
-------------------------------
Attachment: MNG-1507-maven-war-plugin.patch
> Merge contents of dependent wars into war being built
> -----------------------------------------------------
>
> Key: MNG-1507
> URL: http://jira.codehaus.org/browse/MNG-1507
> Project: Maven 2
> Type: New Feature
> Components: maven-war-plugin
> Versions: 2.0
> Reporter: David Hawkins
> Attachments: MNG-1507-maven-war-plugin.patch
>
>
> We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied.
> Also made a minor change in getExcludes to not add the default excludes from FileUtils. The default excludes were already being added in the method getWarFiles( File sourceDir ) by scanner.addDefaultExcludes().
> We are trying to integrate Maven into our environment and not having this functionality was a show-stopper for us. We have applications that reuse jsps, and .tag files from a generic war that need to be included in all of our wars. We have also seen people request this functionality.
> By default these changes will have no effect, unless you have wars specified in your <dependencies>.
> Here is an example configuration that uses the includes and excludes for the dependent wars.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0-beta-3-SNAPSHOT</version>
> <configuration>
> <!-- This is the default for dependentWarIncludes
> <dependentWarIncludes>**</dependentWarIncludes>
> -->
> <dependentWarExcludes>**/*.properties</dependentWarExcludes>
> </configuration>
> </plugin>
> It will not overwrite existing files that are already in the war, the way to get around this is to remove the files you want overwritten using the standard excludes configuration. For example, the following configuration would allow the overwriteme.jar to be overwritten by something in a dependent war.
> <configuration>
> <excludes>WEB-INF/lib/overwriteme.jar</excludes>
> </configuration>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1507) Merge contents of dependent wars into war being built
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1507?page=all ]
Emmanuel Venisse closed MNG-1507:
---------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 2.0.1
Applied
> Merge contents of dependent wars into war being built
> -----------------------------------------------------
>
> Key: MNG-1507
> URL: http://jira.codehaus.org/browse/MNG-1507
> Project: Maven 2
> Type: New Feature
> Components: maven-war-plugin
> Versions: 2.0
> Reporter: David Hawkins
> Assignee: Emmanuel Venisse
> Fix For: 2.0.1
> Attachments: MNG-1507-maven-war-plugin.patch
>
>
> We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied.
> Also made a minor change in getExcludes to not add the default excludes from FileUtils. The default excludes were already being added in the method getWarFiles( File sourceDir ) by scanner.addDefaultExcludes().
> We are trying to integrate Maven into our environment and not having this functionality was a show-stopper for us. We have applications that reuse jsps, and .tag files from a generic war that need to be included in all of our wars. We have also seen people request this functionality.
> By default these changes will have no effect, unless you have wars specified in your <dependencies>.
> Here is an example configuration that uses the includes and excludes for the dependent wars.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0-beta-3-SNAPSHOT</version>
> <configuration>
> <!-- This is the default for dependentWarIncludes
> <dependentWarIncludes>**</dependentWarIncludes>
> -->
> <dependentWarExcludes>**/*.properties</dependentWarExcludes>
> </configuration>
> </plugin>
> It will not overwrite existing files that are already in the war, the way to get around this is to remove the files you want overwritten using the standard excludes configuration. For example, the following configuration would allow the overwriteme.jar to be overwritten by something in a dependent war.
> <configuration>
> <excludes>WEB-INF/lib/overwriteme.jar</excludes>
> </configuration>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MWAR-8) Merge contents of dependent wars into war
being built
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-8?page=all ]
Stephane Nicoll reopened MWAR-8:
--------------------------------
> Merge contents of dependent wars into war being built
> -----------------------------------------------------
>
> Key: MWAR-8
> URL: http://jira.codehaus.org/browse/MWAR-8
> Project: Maven 2.x War Plugin
> Type: New Feature
> Reporter: David Hawkins
> Assignee: Emmanuel Venisse
> Fix For: 2.0
> Attachments: MNG-1507-maven-war-plugin.patch
>
>
> We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied.
> Also made a minor change in getExcludes to not add the default excludes from FileUtils. The default excludes were already being added in the method getWarFiles( File sourceDir ) by scanner.addDefaultExcludes().
> We are trying to integrate Maven into our environment and not having this functionality was a show-stopper for us. We have applications that reuse jsps, and .tag files from a generic war that need to be included in all of our wars. We have also seen people request this functionality.
> By default these changes will have no effect, unless you have wars specified in your <dependencies>.
> Here is an example configuration that uses the includes and excludes for the dependent wars.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0-beta-3-SNAPSHOT</version>
> <configuration>
> <!-- This is the default for dependentWarIncludes
> <dependentWarIncludes>**</dependentWarIncludes>
> -->
> <dependentWarExcludes>**/*.properties</dependentWarExcludes>
> </configuration>
> </plugin>
> It will not overwrite existing files that are already in the war, the way to get around this is to remove the files you want overwritten using the standard excludes configuration. For example, the following configuration would allow the overwriteme.jar to be overwritten by something in a dependent war.
> <configuration>
> <excludes>WEB-INF/lib/overwriteme.jar</excludes>
> </configuration>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MWAR-8) Merge contents of dependent wars into war
being built
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-8?page=all ]
Stephane Nicoll closed MWAR-8:
------------------------------
Resolution: Fixed
Fix Version: 2.0
> Merge contents of dependent wars into war being built
> -----------------------------------------------------
>
> Key: MWAR-8
> URL: http://jira.codehaus.org/browse/MWAR-8
> Project: Maven 2.x War Plugin
> Type: New Feature
> Reporter: David Hawkins
> Assignee: Emmanuel Venisse
> Fix For: 2.0
> Attachments: MNG-1507-maven-war-plugin.patch
>
>
> We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied.
> Also made a minor change in getExcludes to not add the default excludes from FileUtils. The default excludes were already being added in the method getWarFiles( File sourceDir ) by scanner.addDefaultExcludes().
> We are trying to integrate Maven into our environment and not having this functionality was a show-stopper for us. We have applications that reuse jsps, and .tag files from a generic war that need to be included in all of our wars. We have also seen people request this functionality.
> By default these changes will have no effect, unless you have wars specified in your <dependencies>.
> Here is an example configuration that uses the includes and excludes for the dependent wars.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0-beta-3-SNAPSHOT</version>
> <configuration>
> <!-- This is the default for dependentWarIncludes
> <dependentWarIncludes>**</dependentWarIncludes>
> -->
> <dependentWarExcludes>**/*.properties</dependentWarExcludes>
> </configuration>
> </plugin>
> It will not overwrite existing files that are already in the war, the way to get around this is to remove the files you want overwritten using the standard excludes configuration. For example, the following configuration would allow the overwriteme.jar to be overwritten by something in a dependent war.
> <configuration>
> <excludes>WEB-INF/lib/overwriteme.jar</excludes>
> </configuration>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org