Hi,

I started building a custom portal from the archetype.  Basic setup is OK, the 
portal and the portlet app are correctly deployed to tomcat using target 'all'.
For subsequent changes, I only used the 'deploy-portal' and 'deploy-pa' targets.
Now I've tried to configure NTLM authentication for the portal by overriding 
web.xml and the security valve bean in the *-portal module:
*-portal directory layout:
+ src
  -+main
    -+webapp
      -+WEB-INF
        - web.xml (with the NTLM filter)
       -+ assembly
         -+ override
          - security-valve-override.xml

Everything was deployed just fine and working  using the 'deploy-portal' target.
Then I somehow corrupted the user database and had to start with a clean 
database using the 'all' target.

But the 'all' target fails with the appended error stacktrace. A workaround is 
to temporarily rename the 'assembly' directory, run the 'all' target and 
afterwards do an additional 'deploy-portal'.
Am I missing something or is this a problem with the db-maven-plugin?

Regards
  Ralf



[ERROR] Failed to execute goal 
org.apache.portals.jetspeed-2:jetspeed-db-maven-plugin:2.2.2-SNAPSHOT:init 
(seed) on project jetspeed-mvn-portal-pom: Serializer error: Unexpected error 
during import: Cannot find class 
[org.apache.jetspeed.security.impl.ntlm.NtlmSecurityValve] for bean with name 
'securityValve' defined in file 
[<...>\WEB-INF\assembly\override\security-valve-override.xml]; nested exception 
is java.lang.ClassNotFoundException: 
org.apache.jetspeed.security.impl.ntlm.NtlmSecurityValve -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.portals.jetspeed-2:jetspeed-db-maven-plugin:2.2.2-SNAPSHOT:init 
(seed) on project jetspeed-mvn-portal-pom: Serializer error:
        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
        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(LifecycleModuleBuilder.java:84)
        at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)



Reply via email to