> Maybe I didn't clarify these were several projects that have never been
> checked into svn before, hence the need to svn import.
Ah-ha, now it starting to make sense.
> I was commenting on the process I went through to add them to version
> control for the first time. It is not necessarily a bug, but more along the
> lines of a feature request, and I wouldn't want to open an issue unless it
> is confirmed by somebody.
> Some more clarity: when I talk about "svn import," the Eclipse equivalent
> function would be Team>Share. These should not be confused with the Eclipse
> Import... function.
> Simple Example:
> --> maven-project-P1-module1
> --> maven-project-P1-module2
> About these projects:
> * none have been checked into SVN before
> * each is a separate project in Eclipse
> What is the recommended way to add all these projects to version control
> (i.e. svn import)?
> In my case, I attempted to simply svn import maven-project-P1 and was
> hoping, because the module projects are nested on the filesystem, that this
> check-in would include the nested directories (I'm pretty sure this would be
> the behavior from the command-line when using "svn import" from the
> maven-project-P1 directory).
> However, the subdirectories were hidden from view in the synchronize view,
> and therefore were not checked-in.
That is how I would do it and it is sounds strange that Synchronize
view don't show these module folders. m2eclipse can mark these module
folders as derived (to avoid some duplication in the Eclipse UI), but as
far as I know that should not affect the synchronize view. Maybe you had
to refresh your projects or try to commit project directly using "Team /
Commit..." action, skipping the Synchronize view.
Though even after fully committing the parent project, I am almost
certain that module projects won't be shared automatically and the
easiest way to link them with svn is to delete them from Eclipse
workspace and then select your parent project and use "Import / Maven
Projects" wizard to bring them back (that's one operation).
So, it seem like you have two issues that need to be somehow addressed
* the Synchronize view don't show all resources for the parent project
(you'll need to provide more info how to reproduce it)
* automatically link nested projects with svn when their parent project
is connected to svn
Mark, do you have any comments on the above?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-02-21 19:47:57 CET