[
https://issues.apache.org/jira/browse/MWAR-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147083#comment-17147083
]
Herve Boutemy commented on MWAR-433:
------------------------------------
trying to reproduce, but can't generate GWT project:
{noformat}$ mvn archetype:generate -DarchetypeGroupId=org.codehaus.mojo
-DarchetypeArtifactId=gwt-maven-plugin -DarchetypeVersion=2.9.0 -e
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] ---------------< org.apache.maven.its.mng-5001:readonly >---------------
[INFO] Building Configure read-only plugin parameter 2.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) >
generate-sources @ readonly >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) <
generate-sources @ readonly <<<
[INFO]
[INFO]
[INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ readonly ---
[INFO] Generating project in Interactive mode
[INFO] Archetype repository not defined. Using the one from
[org.codehaus.mojo:gwt-maven-plugin:2.9.0] found in catalog remote
Define value for property 'groupId': mwar
Define value for property 'artifactId': mwar-433
Define value for property 'version' 1.0-SNAPSHOT: :
Define value for property 'package' mwar: :
Define value for property 'module': mod
Confirm properties configuration:
groupId: mwar
artifactId: mwar-433
version: 1.0-SNAPSHOT
package: mwar
module: mod
Y: :
[INFO]
----------------------------------------------------------------------------
[INFO] Using following parameters for creating project from Archetype:
gwt-maven-plugin:2.9.0
[INFO]
----------------------------------------------------------------------------
[INFO] Parameter: groupId, Value: mwar
[INFO] Parameter: artifactId, Value: mwar-433
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: mwar
[INFO] Parameter: packageInPathFormat, Value: mwar
[INFO] Parameter: package, Value: mwar
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: module, Value: mod
[INFO] Parameter: groupId, Value: mwar
[INFO] Parameter: artifactId, Value: mwar-433
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.579 s
[INFO] Finished at: 2020-06-27T21:54:41+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on
project readonly: org.apache.maven.archetype.exception.InvalidPackaging: Unable
to add module to the current project as it is not of packaging type 'pom' ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on
project readonly: org.apache.maven.archetype.exception.InvalidPackaging: Unable
to add module to the current project as it is not of packaging type 'pom'
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException:
org.apache.maven.archetype.exception.InvalidPackaging: Unable to add module to
the current project as it is not of packaging type 'pom'
at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute
(CreateProjectFromArchetypeMojo.java:206)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
{noformat}
> Maven WAR plugin is deleting files generated by other plugins after upgrading
> to 3.3.0
> --------------------------------------------------------------------------------------
>
> Key: MWAR-433
> URL: https://issues.apache.org/jira/browse/MWAR-433
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Kyle Lieber
> Priority: Critical
> Fix For: 3.3.1
>
>
> My project generates wsdls using the {{jaxws-maven-plugin}} which puts the
> generated wsdls in
> {{${project.build.directory}/${project.build.finalName}/WEB-INF/wsdls}} so
> that they are packaged up in the war file. Then I have a client jar that
> copies those wsdls out of the war file using the {{maven-dependency-plugin}}
> and generates a client from the wsdls using the {{jaxws-maven-plugin}}.
> This all works fine using {{3.2.3}} of the {{maven-war-plugin}}. However,
> after upgrading to {{3.3.0}} my project fails to build because the wsdls are
> no longer preserved. It seems that they are being deleted by the
> {{maven-war-plugin}}.
> I created an example project on Github which recreates the problem. The
> {{master}} branch is using {{3.2.3}} and the {{maven-war-plugin-3.3.0}}
> branch is using {{3.3.0}}. You can find more details in the readme file of
> the example project:
> https://github.com/klieber/maven-war-plugin-bug
> I also suspect that MWAR-427 is the change that introduced this bug.
> Please let me know if there is anymore information I can provide. Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
