subclipse, so you can deal with merge conflicts.
Configure the scm in maven 2 too though, for:
- changelog
- continuum
- release tagging
I've found this an overall best practice:
Let maven 2 generate the configuration for IDEA/Eclipse,
and compile/run/update/commit directly from the IDE most of the time.
All extra-ordinary stuff (adding dependencies, site generation, ...) I
do using maven 2.
Pieter Vandepitte wrote:
Hi,
I can't figure out what I should use: maven scm for updating my source
code in my repository (or isn't this possible) or using the subclipse
plugin for eclipse. Is there anybody who has experiences with both and
who can tell me what the best practices are? Also, where can I find good
tutorials on scm?
best regards
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
