Eugene Kuleshov wrote:
John, you should read my response.
I should also say, that plugin won't be confused with anything you edit.
Ok cool, thanks.
As long as you understand what you are doing and won't confuse
yourself, but that is generally a good idea anyways, isn't it? :-)
Yes a good idea in theory, if I only could achieve it in practice ;)
regards,
Eugene
John Towell wrote:
Well I can certainly start playing with my build properties, however
I was under the impression that the m2eclipse plugin was managing
those. So if I start changing the setting's there am I going down
the road where I could confuse the plugin and subsequently break it
in my environment?
Xavier Coulon wrote:
John,
Did you check the project's 'java build path' properties in Eclipse
? You can specify the target directory for each source folder
defined in your build path.
You can also check the 'allow output folder' option to specify an
output forlder for each source folder, thus making a clean
separation between main resources and test resources.
For instance, you could set the target directory as 'target/classes'
for your main resources (java classes + properties), and
'target/test-classes' for your test classes (junit, etc..) and their
resources (properties, test data, etc..).
Hope this helps.
Regards,
Xavier
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
