Fw: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
On Tue, 26 May 2009 08:39:36 -0700 (PDT) "Juan Carlos Garcia M." wrote: > [MECLIPSE ticket and workaround] > > Hope this help. Yes it does, thank you. Carl-Eric - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For

Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
On Tue, 26 May 2009 08:31:04 -0700 Igor Vaynberg wrote: > go to preferences/compiler/building/output folder and remove *.html > from Filtered Resources list. I know that :-) I was proposing making this the default in the archetype. > test is for tests :) > the proper way to do this is to crea

Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Juan Carlos Garcia M.
The first problem you mention is due to a change in how the maven eclipse plugins works, documented as a bug in: " http://www.mail-archive.com/d...@maven.apache.org/msg80176.html http://www.mail-archive.com/d...@maven.apache.org/msg80176.html " Known Issues: * [MECLIPSE-443] - Only include **/*.j

Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Igor Vaynberg
On Tue, May 26, 2009 at 3:25 AM, Carl-Eric Menzel wrote: > - The classpath file generated by 'mvn eclipse:eclipse' has an >  include-pattern of '**/*.java' for both src/test/java and >  src/main/java. This means that by default none of the HTML files or >  other resources will be copied to the cla

Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
Hi, when creating a fresh Wicket project with the following line as generated by the quickstart page on wicket.apache.org: mvn archetype:create -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=1.4-rc4 -DgroupId=com.mycompany -DartifactId=my