Hi, we are currently working on the Maven2 mojos, and I expect them to be ready by the end of the month or at the beginning of October. Can you try to make the servlet samples work with Maven2? It should be pretty stright-forward: just navigate to /samples/servlet and execute mvn clean install After that you can see how things work their, and try to make it work for yourself.
Thanks, Petar. 2008/9/22, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > > > > > Hello, > > I'd like to use cactus with maven 2. The documentation states that for > this I'd need cactus 1.8.1 > I could only find 1.8.1-snapshot in svn, so I'm trying to build it. > However, I'm getting the following error: > > [INFO] Using version: 2.0 of plugin: > org.apache.maven.plugins:maven-changes-plugin > org.apache.maven.lifecycle.LifecycleSpecificationException: > > No lifecycle phase binding can be found for goal: announcement-generate, > specified as a part of the execution: announcement-generatein plugin: > org.apache.maven.plugins:maven-changes-plugin > > This plugin was resolved successfully. > However, the mojo metadata it contains does not specify a default lifecycle > phase binding. > > Please provide a valid <phase/> specification for execution: > announcement-generate > in plugin: org.apache.maven.plugins:maven-changes-plugin > > > at > > org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings( > DefaultLifecycleBindingManager.java:266) > at > > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0( > DefaultBuildPlanner.java:99) > at > > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice( > DefaultBuildPlanner.java:403) > at > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan( > DefaultBuildPlanner.java:1) > at > > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan( > DefaultBuildPlanner.java:67) > at > > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans( > DefaultBuildPlanner.java:56) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > DefaultLifecycleExecutor.java:138) > at org.apache.maven.DefaultMaven.execute_aroundBody0( > DefaultMaven.java:223) > at org.apache.maven.DefaultMaven.execute_aroundBody1$advice( > DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2( > MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice( > MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute( > MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > > Is this a known problem? Is there a workaround for this? > > Regards, > Bo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Petar! Karlovo, Bulgaria. - - - - - - - - | Author @ Manning Publications. | Technical Consultant @ HP | BGJUG-Bulgarian Java User Group Leader. | Apache Jakarta PMC member. | Jakarta Cactus Lead Developer. | Blogger: http://weblogs.java.net/blog/paranoiabla/ - - - - - - - - Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
