[
https://issues.apache.org/jira/browse/TOMEE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15809709#comment-15809709
]
Romain Manni-Bucau commented on TOMEE-1978:
-------------------------------------------
1. war should be replaced by ${project.packaging} but recall not having done it
intentionally but don't recall yet. Think it was cause undeploy will not work
with this path so for symmetry it was better to not default it but no more sure.
2. rechecking your error message it is linked to .war extension more than ## so
this is supportable (you can PR on the TomcatWebAppDeployer to try to find the
webapp without the extension if present)
To summarize I'm not sure for 1, once rephrased no problem with 2.
Side note: not sure about adoption (was it just to try to make your issue
moving forward? ;)). Most actual tomee users rely on run/debug and pretty much
never on deploy - that's why this is a feature not very advanced.
> JEE WAR not getting deployed with tomee-maven-plugin 7.0.2
> ----------------------------------------------------------
>
> Key: TOMEE-1978
> URL: https://issues.apache.org/jira/browse/TOMEE-1978
> Project: TomEE
> Issue Type: Documentation
> Components: TomEE Maven Plugin
> Affects Versions: 7.0.2
> Environment: Mac OS Sierra, Java 1.8.0_25, Eclipse Neon, Maven TomEE
> Plugin 7.0.2
> Reporter: Dev Null 52
>
> I am using TommEE org.apache.tomee.maven plugin version 7.0.2 to deploy a JEE
> WAR to a TomEE 7.0.2 running on a seperate JVM process ( not embedded within
> Eclipse ). I am am very familiar with tomcat7:deploy task. However equivalent
> tomee:deploy fails with different messaged.
> 1. If I use as-is, it complains with message:
> The parameters 'path' for goal
> org.apache.tomee.maven:tomee-maven-plugin:7.0.2:deploy are missing or invalid.
> 2. If I provide a path within configuration it fails with message:
> Caused by: org.apache.openejb.OpenEJBException: Creating application failed:
> /LOCAL_FS_PATH/Eclipse/workspace/jee-examples/target/jeeexamples##0.0.1:
> addChild: Child name '/jeeexamples##0.0.1' is not unique.
> My webapps directory is empty. I had initial difficulties with deployment but
> I was able to deploy a tomee.war and able to proceed. Not sure if it helps,
> but I have added following based on posts to system.properties ( I dont know
> all the implications yet but I have added to go past while I learn more ).
> Not sure if I am contributing to the problem.
> system.properties
> ===============
> tomee.remote.support = true
> tomee.serialization.class.whitelist =
> tomee.serialization.class.blacklist =
> org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan,java.lang.Process
> openejb.system.apps = true
> ## tomee.version=7.0.2
> <plugin>
> <groupId>org.apache.tomee.maven</groupId>
> <artifactId>tomee-maven-plugin</artifactId>
> <version>${tomee.version}</version>
> <configuration>
>
> <tomeeVersion>${tomee.version}</tomeeVersion>
> <tomeeClassifier>plus</tomeeClassifier>
>
> <tomeeHttpPort>${tomee.port}</tomeeHttpPort>
> </configuration>
> </plugin>
> Command line usage:
> mvn -X -e -file ${PROJECT_LOC}/pom.xml -settings
> ~/LOCAL_M2_PATH/.m2/settings.xml clean install tomee:deploy
> -Dmaven.test.skip=true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
