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

[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 **/*.java in Java source directories
may affect you if you use ajdt or have non-java sources in your
directories that you expect to be compiled
Release 2.6.1 (which may get renamed to 2.7) has fixed this issue and will
be released shortly.

However in order to get it works and better don't need to worry about fixing
this in eclipse every time you generate the Eclipse project through mvn
eclipse:eclipse, you can specify to use version 2.5 of maven-eclipse-plugin
in your POM.xml

 build
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId
  version2.5/version
/plugin
  /plugins
  /build

Hope this help.


igor.vaynberg wrote:
 
 On Tue, May 26, 2009 at 3:25 AM, Carl-Eric Menzel
 cm.wic...@users.bitforce.com 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 classpath when for example
  using the 'Start' class.
 
 go to preferences/compiler/building/output folder and remove *.html
 from Filtered Resources list.
 
 The second problem is due to the way I set up my project -- it may be
 odd (is it?), but I think this is rather sensible for standalone
 component development.

 - I am developing a standalone component for use in other projects, so
  under src/main/ I'd like to have only the classes and resources that
  belong to the component. On the other hand, for testing and debugging
  purposes, a simple Wicket application and page are very handy, so I
  moved those from src/main to src/test, since these shouldn't show up
  in the generated jar file.
 
 test is for tests :)
 
 the proper way to do this is to create a multimodule project - one
 module containing the component and another containing a demo which
 you can also use for testing.
 
 -igor
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-Maven-archetype%2C-Eclipse-Classpath-and-jetty%3Arun-tp23720481p23725755.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

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

[Igor Vaynberg]

On Tue, May 26, 2009 at 3:25 AM, Carl-Eric Menzel
cm.wic...@users.bitforce.com 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 classpath when for example
  using the 'Start' class.

go to preferences/compiler/building/output folder and remove *.html
from Filtered Resources list.

 The second problem is due to the way I set up my project -- it may be
 odd (is it?), but I think this is rather sensible for standalone
 component development.

 - I am developing a standalone component for use in other projects, so
  under src/main/ I'd like to have only the classes and resources that
  belong to the component. On the other hand, for testing and debugging
  purposes, a simple Wicket application and page are very handy, so I
  moved those from src/main to src/test, since these shouldn't show up
  in the generated jar file.

test is for tests :)

the proper way to do this is to create a multimodule project - one
module containing the component and another containing a demo which
you can also use for testing.

-igor

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

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

[Carl-Eric Menzel]

On Tue, 26 May 2009 08:31:04 -0700
Igor Vaynberg igor.vaynb...@gmail.com 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 create a multimodule project - one
 module containing the component and another containing a demo which
 you can also use for testing.

Interesting idea, I'll try that.

But I need a page if I want to test a form (and thus testing how my
component acts within the form), don't I? WicketTester.newFormTester
seems to want to have a page started first. That's why I wanted to have
the page in the test directory, because I only need it as a test
fixture.

Thanks for the reply
Carl-Eric

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org