Ok, thanks. What I've done so far is a "final" commit from my
development machine, and then I renamed the project in svn, moving it
into branches, so that it's no longer in trunk. (I realized just now
that I should have disconnected the project from svn before I moved it,
but no matter since that's just a simple job of removing all of the .svn
directories on my development machine.) I've started a new eclipse
project using the eclipse maven plugin and will move the pieces into it
into their "correct" locations, and then do a commit from the new project.
Chad La Joie wrote:
I had a series of projects that had different directory structures
than what Maven uses by default. When we mad the conversion we
changed our local copy around until it was what we wanted and then
just did a commit. Wasn't much to it really.
Rusty Wright wrote:
I have an existing eclipse project, a "dynamic web application", which
I've been working on. I'm also using subversion (subclipse). My
problem is that my directory/folder structure is significantly different
than the maven convention, and I would prefer to switch to the maven
convention. I'm not sure how I should proceed.
For example, could I simply reorganize my directory structure in
subversion to match the maven convention and then import it into a new
eclipse project that's been set up to play nicely with maven?
I guess I'm looking for suggestions on the best way to proceed, for long
term happiness, and not some hack method that I may regret later on.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
