jira-importer commented on issue #609: URL: https://github.com/apache/maven-scm/issues/609#issuecomment-2964606645
**[Chris Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)** commented Ie, make it a nested, non flat structure. That will not work, as it presumes a few things. 1. That the existing structure can indeed be changed. In some cases it may be able to be changed, in others it certainly will not. 2. Subclipse will not cope with this structure (having projects overlap) 3. It does not fix the issue (which is a real one), it simply ignores it. Looking at the dates from the Subversion issue (2007) it has been around for a while.Their point of view is that it is a maven bug in that it is maven that fails to deal with a known issue. I can see their point. The fact of the matter is that Maven supports non nested directory structures, and so should the plugins. The SCM/subversion modules must be able to cater for this situation, it is not an uncommon one.Whilst it may be a hack to commit each project separately, it (to me at least, and from what I can read others as well) it would be an acceptable workaround. Perhaps there should be an option to use SVNKit, as that does handle this situation. -Chris -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
