This is excellent - thank you. One question - how do you handle the case where one of the sub-projects is shared between several multi-module projects? Both in terms of eclipse and SVN? Is it a matter of declaring it as an external dependency? Thanks
@frobfoo Again answering myself: after freshly checking out the parent project from SVN (New > Maven > Checkout Maven Projects from SCM), all projects are correctly shown in Eclipse. Ugh. I assume that this is rather a Subversive problem so I'm investigating in that direction further.
@frobfoo One problem (or misunderstanding) remains: After sharing the parent project, it is correctly shown as connected to SVN in the package explorer. But the module projects are not, which I find rather confusing... Now when I change module A, the parent project shows changes and I have to commit at the parent project level ... Any solution to that?
Thx for the intro into multi module projects. I want to adopt the layout for a legacy project (monolithic, built with ant). The problem I have is the question how to share the multi module project into a (in my case: Subversion, using the Subversive Eclipse plugin) source code repo. I tried "Team > Share Project..." on the newly created multi module project. But then I am unable to add resources of module projects (e.g. .settings) to svn:ignore, it only works for the parent project. Any hints?
nice
hrfernsehen 1 month ago
This is excellent - thank you. One question - how do you handle the case where one of the sub-projects is shared between several multi-module projects? Both in terms of eclipse and SVN? Is it a matter of declaring it as an external dependency? Thanks
langfors 1 year ago
@frobfoo Again answering myself: after freshly checking out the parent project from SVN (New > Maven > Checkout Maven Projects from SCM), all projects are correctly shown in Eclipse. Ugh. I assume that this is rather a Subversive problem so I'm investigating in that direction further.
frobfoo 1 year ago
@frobfoo One problem (or misunderstanding) remains: After sharing the parent project, it is correctly shown as connected to SVN in the package explorer. But the module projects are not, which I find rather confusing... Now when I change module A, the parent project shows changes and I have to commit at the parent project level ... Any solution to that?
frobfoo 1 year ago
@frobfoo Ahh, I figured it out. It can be done editing the property "svn:ignore" via "Show Properties", setting it to
.settings
target
.project
.classpath
and the using "Apply property recursively to" > "All resources"
frobfoo 1 year ago
Thx for the intro into multi module projects. I want to adopt the layout for a legacy project (monolithic, built with ant). The problem I have is the question how to share the multi module project into a (in my case: Subversion, using the Subversive Eclipse plugin) source code repo. I tried "Team > Share Project..." on the newly created multi module project. But then I am unable to add resources of module projects (e.g. .settings) to svn:ignore, it only works for the parent project. Any hints?
frobfoo 1 year ago