Good points, Eugene. I'll take a closer look at what we're trying to
accomplish. Maybe it does make more sense to put integration tests in a
different module. This is a very new project, so we're still figuring
out a lot of the details. It's just so easy to add source folders under
Eclipse, that it's easy to think about it that way.
Thanks for the input.
Dave
Eugene Kuleshov wrote:
David C. Hicks wrote:
Thanks again. I'll check out the build-helper plugin.
As for larger projects, that's exactly how I've done them in the past.
It requires a little massaging of the pom.xml files, but I haven't found
a cleaner way to handle it. Maybe one day between Eclipse and Maven
this won't be such a mind twister.
The primary reason I'm adding extra source folders is for test code. I
really don't want to mix functional tests with my unit tests. It made
sense, to me, to put them in a different tree, but it didn't seem like a
good fit for a sub-module.
Thanks for all the suggestions!
The m2eclipse uses pom.xml as a source of information for configuring
projects in Eclipse. The reason for that is to keep build in Eclipse and in
the command line in sync. The command line build won't run for your
additional test folders if they are not in the pom.xml. After all it might
be a good idea to keep integration tests in a separate module and that would
closely follow standard Maven conventions.
On the other hand, if you have command line build that works, but there is
some issues in the IDE for the very same build, please submit a bug report
for m2eclipse and provide test project that would allow us to reproduce it.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
