Thanks Wendy!

I followed your instructions precisely and encountered the same error. However I deployed to Tomcat 5.5 and it worked without any problems.

Jetty was indeed picking up the wrong servlet-api.jar

I fixed it by removing the geronimo-j2ee_1.4_spec dependency from the maven-jetty-plugin-6.1.11 in pom.xml

*I have committed this fix to your branch for the blank achetype. It did not affect the starter archetype*

---

However, there is an additional problem that the applications do not support the groupId completely.

The classes are generated in "net/wsmoak/example" but:
 struts.xml references class="example.HelloWorld"; and
 HelloWorld.java states the package is "package example";

Strangely, this doesn't prevent it from running. Is there a way for Maven to insert the groupId as a prefix in arbitary files so that struts.xml and the java use the correct package?

regards,
Jeromy Evans




Wendy Smoak wrote:
Our user docs point to snapshots of the archetypes, which is not
ideal.  Especially since old snapshots were removed recently by infra
to free up disk space, and the commands in the docs no longer work.

I've branched the blank and starter archetypes [1], updated them to
version 2.0.11.2-SNAPSHOT, and deployed new snapshots.

Can someone please try the blank archetype and figure out why 'mvn
jetty:run' does not work?  I get:

mvn archetype:create -DarchetypeArtifactId=struts2-archetype-blank
-DarchetypeVersion=2.0.11.2-SNAPSHOT
-DarchetypeGroupId=org.apache.struts -DgroupId=net.wsmoak
-DartifactId=test123

cd test123

mvn install jetty:run

http://localhost:8080/test123

HTTP ERROR: 500

javax.servlet.jsp.tagext.TagAttributeInfo.<init>(Ljava/lang/String;ZLjava/lang/String;ZZLjava/lang/String;ZZLjava/lang/String;Ljava/lang/String;)V

RequestURI=/test123/example/HelloWorld.action

[1] svn co 
https://svn.apache.org/repos/asf/struts/maven/branches/ARCHETYPES_2_0_X

Thanks,


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to