Community
Participate
Working Groups
Build Identifier: 20110615-0604 After some SVN activity (commit changes, update Maven module from SVN) .svn folders (with its content) from src/main/java/ are appearing in target/classes/ (and in resulting jar artifact), and .svn from src/test/java/ in target/test-classes/, respectively. Installation details: Eclipse 3.7 with plugins m2e 1.0.0.20110607-2117 and Subversive SVN Team Provider 0.7.9.I20110602-1700. Reproducible: Sometimes Steps to Reproduce: (all steps are performed in Eclipse, no other command-line/GUI actions) 1. Check out Maven module from SVN. Import as Maven project. 2. Change some files. Commit to SVN. 3. Update project from SVN. It's hard to detect, because it is not visible from Eclipse, it can be detected only when inspecting target folder in file manager or when size of artifacts is grown enormously.
.svn folders are already present after import (on the step 1) and always reappearing after mvn clean + clean + build. After adding .svn to Preferences->Java->Compiler->Building->Filtered resources folders are still appearing, but without files (i.e. .svn with subfolders, but without files).
FYI, we (m2e developers) do not currently use subversive and will not be able to attend to this problem any time soon unless somebody provides a quality patch (we do prioritize review of submitted patches).
I think this problem is more common, and is not related to just Subversive. Please read comments to other tickets: https://bugs.eclipse.org/bugs/show_bug.cgi?id=284309#c1 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=320927#c7 - the .svn resources should be ignored by maven builder because they are marked as team private, not because of their Subversive-specific names. From reading above mentioned tickets (284309, 320927) I think the similar problem was in Java builder (and is successfully resolved, because in our non-Maven projects .svn is never appearing in build folders).
I was not suggesting the problem is specific to svn. Still, we are not affected by this problem (we currently use git for all our opensource and commercial work), so investigating and fixing this problem is not going to be high on our priority list. In other words, somebody will have to provide a quality patch if this problem is to be addressed any time soon.
closing old/stale bugreports
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
