"Mark Hewett" <mark.hewett@gmail.com> wrote on 07/17/2006 02:22:10 PM:
> I'm using Maven2 for my builds. Maven does it's thing in a directory
> under my project called "target", which is included in svn:ignore on
> the root project folder. As part of the release process, Maven2
> checks out a tagged version of the project into a sub-directory of the
> target directory (called "checkout") and runs it's build from there.
> As part of this build, a file is created in the checkout directory.
>
> At this point, if I do a "Team/Synchronize with Repository" the file
> that was created within the target/checkout directory shows as an
> outgoing addition. This is even though the target directory is
> ignored. The same thing shows using both JavaHL and JavaSVN.
> However, if I go to the command line and do "svn status" it shows no
> changes at the root of the project. If I switch to the
> target/checkout directory and do "svn status" I see the outgoing
> change.
>
> Anyway, I would guess that having nested working directories, even in
> ignored directories, is a bit risky - but I thought I would mention it
> since the command line seemed to handle it OK.
Try using the command line status command with the full absolute path to
one of these files. That is more the equivalent of what we are asking
Subversion. I do not think Subversion will consider the file to be
ignored in that case.
Is there any reason that Maven is not using the svn export command,
instead of checkout? I would think it would not want/need the overhead of
a working copy in the target folder.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jul 17 20:28:33 2006