Sorry, Eugene. Poor choice of words on my part. It's probably more
accurate to say that I don't know how to use M2E properly so that it
works well with SCM. Here's an example, though:
I have checked my project out using the "Check out as Maven Project".
That works wonderfully, by the way, and my team loves it! Now, the hard
part. I add a new module to my project using the "New Maven Module
Project" feature. Again, this is great! But, my new module isn't yet
associated with my SCM (Subversion, in my case). I usually end up
refreshing the parent project and performing an SCM check-in/update. So
far, I've always had to delete the projects in Eclipse and check them
out again to pick up the new module. Otherwise, it seems that SCM just
can't quite get a grip on the new module. So, I end up going through a
few "cycles" of [check-in, delete, check-out, inspect] before everything
seems happy. Since my project is in its early life, the structure is
changing pretty rapidly. I've been through this process a number of
times in the last few days.
Like I said, it's probably more a matter of me not knowing the right way
to go about this. That was the main intention behind this thread -
trying to find out if there is a known "happy path" to make everything
play nice together and be more efficient for me.
Thanks!
Dave
Eugene Kuleshov wrote:
David C. Hicks wrote:
Normally, to create a new module, I right-click the project that I
want to create a new module in and select "Maven -> New Maven Module
Project". It does a great job of creating the new module and adding
a project to Eclipse, but it doesn't integrate well with SCM.
David, can you please elaborate what you mean that it doesn't
integrate well with SCM?
Thanks
Eugene
---------------------------------------------------------------------
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
