Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1-beta-1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Linux, tomcat6.
-
Testcase included:yes
-
Patch Submitted:Yes
-
Number of attachments :
Description
I'd like to be able to have a 'development' profile which I configure to include all versioning files. I'm dealing with complicated overlays, and sometimes it's simply easiest to fix a jsp or so directly on the spot where it is deployed, on the test-server or so, and check it in from there too. Probably I could also change our habits or so, and find some way of working which is more or less handy too, but for the moment I have no idea how that would go, and everything would work just fine if the 'useDefaultExcludes' feature can be disabled with a configuration option.
I tried to implement it myself, and am attaching a patch, which includes such an option.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-2-SNAPSHOT</version>
<configuration>
<useDefaultExcludes>false</useDefaultExcludes>
</configuration>
</plugin>
Issue Links
Activity
Michiel Meeuwissen
made changes -
Michiel Meeuwissen
made changes -
Dennis Lundberg
made changes -
| Description |
I'd like to be able to have a 'development' profile which I configure to _include_ all versioning files. I'm dealing with complicated overlays, and sometimes it's simply easiest to fix a jsp or so directly on the spot where it is deployed, on the test-server or so, and check it in from there too. Probably I could also change our habits or so, and find some way of working which is more or less handy too, but for the moment I have no idea how that would go, and everything would work just fine if the 'useDefaultExcludes' feature can be disabled with a configuration option. I tried to implement it myself, and am attaching a patch, which includes such an option. <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1-beta-2-SNAPSHOT</version> <configuration> <useDefaultExcludes>false</useDefaultExcludes> </configuration> </plugin> |
I'd like to be able to have a 'development' profile which I configure to _include_ all versioning files. I'm dealing with complicated overlays, and sometimes it's simply easiest to fix a jsp or so directly on the spot where it is deployed, on the test-server or so, and check it in from there too. Probably I could also change our habits or so, and find some way of working which is more or less handy too, but for the moment I have no idea how that would go, and everything would work just fine if the 'useDefaultExcludes' feature can be disabled with a configuration option.
I tried to implement it myself, and am attaching a patch, which includes such an option. {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1-beta-2-SNAPSHOT</version> <configuration> <useDefaultExcludes>false</useDefaultExcludes> </configuration> </plugin> {code} |