On Mon, Aug 25, 2008 at 2:51 PM, Marco Maccaferri <macca_at_maccasoft.com> wrote:
> Mark Phippard wrote:
> > I had an install lying around that still has 1.4.1 installed. I tried
> > it, I get the prompt to add to SVN, but I see no evidence that it
> > actually does. The project is clearly associated with Subclipse, but
> > Commit does not work, Update is not enabled, and Add is not visible.
> > What should happen when it works? I'd have expected the resources to
> > all be in an Added state and waiting to be committed.
> Only the project folder is added to the repository, all resources are in
> the unknown state (with the question mark decorator), see this:
> A sample.feature
> ? sample.feature\.project
> ? sample.feature\build.properties
> ? sample.feature\feature.xml
> Commit, add to version control, and all team menu items are working as
> expected. The project and all resources also appears in the synchronize
> view, with the outgoing (+) decorator.
> The usefulness of this feature is that it allows to add a new project in
> one commit, instead of going through the team -> share project action that
> first creates the project with a commit, then adds the resources with
> another commit, when you need to add several projects it is a nightmare.
OK, I have been debugging this and I think I know the cause. I am
adding Eugene to the thread because he made this change in 1.4.3.
Subclipse used to declare the .project file as a metadata file. This
caused our SVNTeamProviderType#metaFilesDetected method to be called
when a project was created. This allowed us to discover this
situation and auto-share the project.
Eugene removed this from our plugin.xml in 1.4.3 because it was
preventing some CVS import behavior to happen.
So it seems like we need someone to step up with the right way to add
this back so that we do not interfere with CVS.
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-25 21:28:12 CEST