Even with Subclipse 1.8.20 this still seems to be occurring with m2e
using a hierarchical Maven parent POM with child POMs. The individual
child projects as listed at the top level of the Pack Explorer seem to
be using svn:ignore correctly, but under the main parent POM, the
listing of the individual child projects indicate that they have changed
resources, and if you explore down into child projects, it is the
svn:ignore-d directories and files that are causing this. I have close
and re-opened all the projects, refreshed, did a complete commit, and
then refreshed again.
Garret
On 4/10/2013 9:02 AM, Garret Wilson wrote:
> I'm running Eclipse 4.2.2 with a multi-project Maven project using m2e.
>
> I believe ever since upgrading to Subclipse 1.8.19 a week or so ago,
> my svn:ignore has stopped working. That is, my .settings, .target,
> .classpath, .project, etc. directories have little question marks by
> them in Eclipse, and I get an asterisk next to the project in "Package
> Explorer", indicating that something has changed in Subversion---but
> when I try to submit, nothing has changed. (TortoiseSVN correctly
> ignores these files, because they are marked as ignore with svn:ignore.)
>
> If I close and re-open all my projects and sub-projects, the
> subprojects go back to behaving correctly, but the parent Maven
> project still has an asterisk beside it, and the lists of the
> subprojects under it still behave incorrectly.
>
> Please include me on any replies, as I do not believe I am a member of
> this list.
>
> Garret
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3053387
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2013-04-15 19:41:32 CEST