The WAR plugin isn't released yet, so we may still get a chance to allow
it to do both (ie, exploded also wars it up). Is that useful?
Regardless, a new release can be made at any time - no more tying
plugins to m2 releases.
- Brett
Mark Hobson wrote:
>On 16/09/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>>+++
>>maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
>> Thu Sep 15 17:37:58 2005
>>@@ -314,7 +314,10 @@
>> {
>> generateExplodedWebapp();
>>
>>- if ( !"exploded".equals( mode ) )
>>+ // TODO: make a separate 'exploded' Mojo. For now,
>>+ // disable not making an artifact so the install phase
>>+ // doesn't fail.
>>+ // if ( !"exploded".equals( mode ) )
>> {
>> //generate war file
>> getLog().info( "Generating war " + warFile.getAbsolutePath()
>> );
>>
>>
>
>This obviously stops mode="exploded" from doing anything useful now :(
> I use this loads to save warring-up my 15mb webapp when deploying
>inplace to tomcat, since the zipping process is quite slow when in
>development.
>
>Looks like any fix missed the beta1 boat whilst I was asleep.. would
>I have to wait until beta2 for this or could an updated war plugin be
>released in the meantime?
>
>Cheers,
>
>Mark
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
