Community
Participate
Working Groups
Created attachment 127236 [details] Three Projects viewable in Eclipse Package Explorer Build ID: M20080911-1700 Steps To Reproduce: 1/ Install Maven on workstation <http://archive.apache.org/dist/maven/binaries/apache-maven-2.0.9-bin.zip> 2/ Install m2eclipse plugin in Eclipse <http://m2eclipse.sonatype.org/update/> 3/ Install Subversive in Eclipse 4/ Install Subversive connectors in Eclipse 5/ Install Subversive integration for m2eclipse in Eclipse 6/ Unzip [maven-parent.zip] and import into Eclipse using 'Import as Maven Project' menu At this point the multimodule project has been imported into Eclipse and will show up in the Package Explorer as three separate projects even though the maven-parent.zip contains a nested project structure that looks like this: maven-parent src pom.xml maven-first-child src pom.xml maven-second-child src pom.xml 7/ Now select maven-parent project and try to use Team -> Share Project.. to share the project in Subversion The result in Subversion will only include the files from maven-parent (i.e., src folder and pom.xml), but not include the nested project files. Using Subversion from the command line to import the maven-parent project into Subversion works as it should. 8/ To import from Subversion command line: cd inside directory maven-parent issue command 'svn import URL -m "comment for import" The above Subversion command line import will correctly import the project into Subversion such that it contains all of the file and directories under maven-parent. More information: I will be including several attachments that illustrate the appearance of the three Eclipse projects and the appearance of the correctly imported source code in the Subversive Subversion Repository Exploring view.
Created attachment 127237 [details] Maven multimodule project correctly imported into Subversion This is what the maven-parent Maven multimodule project looks like when it is correctly imported into Subversion. This was done using the Subversion command line since it wouldn't work correctly using Team -> Share Project..
There was an earlier bug filed that was related to problems sharing a Maven multimodule project using Subversive, however it didn't include a supplied test case and didn't appear to have been worked on. Bugzilla # <https://bugs.eclipse.org/bugs/show_bug.cgi?id=248043>
Created attachment 127240 [details] maven-parent.zip -- the sample Maven multimodule project The maven-parent.zip file contains a simple Maven multimodule project that can be used to illustrate import into Eclipse and import into Subversion.
One thing worth to mention is that the following folder are marked as derived: maven-parent/maven-first-child maven-parent/maven-second-child This is done on purpose, so the duplicated resources, e.g. maven-parent/maven-first-child/pom.xml won't appear in "Open Resource" and similar dialogs, because the primary ones are also in workspace, e.g. first-child/pom.xml I suppose one way to address this issue is to select child project when sharing and SVN team provider should detect that those projects are physically located under already shared parent project and then share them automatically, like it would be done when you import these projects into Eclipse.
Using this docu: http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Subversive Both way's work. 3. 'way' external svn checkout and then Team-Share. The project are checked out with svn checkout. Using the Eclipse Maven Project Import, all are imported into Eclipse, but NOT connected to by subversive to SVN. Team -> Share an existing Project, either the Master Project or a sub project doesn't work.
Details here: bug #392882 *** This bug has been marked as a duplicate of bug 392882 ***
