Hi Shawn, Here are the files that you have asked for. I have renamed pom.xml from realm to pom_realm.xml. I have manually deleted rest from webapps in Tomcat and restarted Tomcat. Then I ran "mvn clean -e tomcat:deploy” And got as usually: 94: warning - Tag @link: can't find objectName in org.apache.directory.fortress.core.rbac.PermObj [WARNING] /Users/myusername/git/directory-fortress-enmasse/src/main/java/org/apache/d irectory/fortress/rest/FortressService.java:1919: warning - Tag @link: can't find warningId in org.apache.directory.fortress.core.rbac.Session [WARNING] /Users/myusername/git/directory-fortress-enmasse/src/main/java/org/apache/d irectory/fortress/rest/FortressService.java:1964: warning - Tag @link: can't find warningId in org.apache.directory.fortress.core.rbac.Session [INFO] Building jar: /Users/myusername/git/directory-fortress-enmasse/target/fortress-rest-1.0-R C40-SNAPSHOT-javadoc.jar [INFO] [INFO] >>> maven-source-plugin:2.4:jar (attach-sources) @ fortress-rest >>> [INFO] [INFO] <<< maven-source-plugin:2.4:jar (attach-sources) @ fortress-rest <<< [INFO] [INFO] --- maven-source-plugin:2.4:jar (attach-sources) @ fortress-rest --- [INFO] Building jar: /Users/myusername/git/directory-fortress-enmasse/target/fortress-rest-1.0-R C40-SNAPSHOT-sources.jar [INFO] [INFO] <<< tomcat-maven-plugin:1.1:deploy (default-cli) @ fortress-rest <<< [INFO] [INFO] --- tomcat-maven-plugin:1.1:deploy (default-cli) @ fortress-rest --- [INFO] Deploying war to http://localhost:8080/fortress-rest-1.0-RC40-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 19.512s [INFO] Finished at: Wed Apr 22 21:56:21 CEST 2015 [INFO] Final Memory: 43M/474M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project fortress-rest: Cannot invoke Tomcat manager: FAIL - Deployed application at context path /fortress-rest-1.0-RC40-SNAPSHOT but context failed to start -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project fortress-rest: Cannot invoke Tomcat manager: FAIL - Deployed application at context path /fortress-rest-1.0-RC40-SNAPSHOT but context failed to start
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif
ecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif
ecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Li
fecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStart
er.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
2)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.j
ava: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.MojoExecutionException: Cannot invoke
Tomcat manager: FAIL - Deployed application at context path
/fortress-rest-1.0-RC40-SNAPSHOT but context failed to start
at
org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.
java:145)
at
org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarCatalin
aMojo.java:70)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildP
luginManager.java:106)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
208)
... 19 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
/Oleksandr
On 22/4/2015 16:47 , "Shawn McKinney" <[email protected]> wrote:
>
>> On Apr 22, 2015, at 8:34 AM, Oleksandr Bodriagov (Polystar)
>><[email protected]> wrote:
>>
>> It has never worked really.
>> I have erroneously assumed that if tests ³mvn test -Dtest=EmTest² work
>> then the REST module works.
>
>Olekandr,
>
>You get success on the rest mvn test after a failed deployment?
>
>Can you send me the pom.xml and context.xml from your rest package? And
>send the pom.xml from fortress realm-impl folder.
>
>Also send the complete tomcat log from startup to error. If you can
>clear out the apps from webapps before redeploying that would be good
>too, just so I see the complete listing.
>
>Obviously this is a problem I’ve never seen. I’m sure it is something
>simple, but once we get it figured out, it will be documented, so we
>don’t forget.
>
>Thanks for your patience,
>
>Shawn
>[email protected]
pom_realm.xml
Description: pom_realm.xml
context.xml
Description: context.xml
pom.xml
Description: pom.xml
