ArneD a écrit :
Emmanuel Venisse wrote:
Are you sure it isn't possible to checkout sources in a specific folder
with cleartool?
It is possible with snapshot views. My ClearCase know-how is limited, but I
am quite sure it is not possible with dynamic views.
Do you think the suggested
my Continuum installation is accessing a file system directory using
scm-local provider to get sources (BTW, the directory is on a ClearCase
dynamic view). Updates are working fine as long as files are only changed or
added. But when files are removed from the source directory, they still
a patch.
Regards,
Arne
--
View this message in context:
http://www.nabble.com/Update-over-scm-local-does-not-delete-files-removed-from-source-dir-tf2257460.html#a6303945
Sent from the Continuum - Users forum at Nabble.com.
ArneD a écrit :
Emmanuel Venisse wrote:
Do you think the suggested enhancement for scm-local would be useful and
make sense? Not only in combination with ClearCase dynamic views but for
other usage as well, e.g. testing.
yes. Do you want to implement it?
Yes, I can try to do so and
\where, without copying to a working directory?
Probably you are only talking about Maven stand-alone usage. Then, I agree,
it is no problem, as long as you are running the clean goal.
Regards,
Arne
--
View this message in context:
http://www.nabble.com/Update-over-scm-local-does-not-delete-files
What Continuum does (with help of scm-local) is to copy all files from
Z:\VOB\some\where to D:\continuum-work\99 before running the build. If
someone removes an outdated class from ClearCase, it won't be on
Z:\VOB\some\where any longer.
Is there a reason you can't use a snapshot view? It
://www.nabble.com/Update-over-scm-local-does-not-delete-files-removed-from-source-dir-tf2257460.html#a6281593
Sent from the Continuum - Users forum at Nabble.com.
Are you sure it isn't possible to checkout sources in a specific folder with
cleartool?
Emmanuel
ArneD a écrit :
Emmanuel Venisse wrote:
thanks a lot for your answer. A ClearCase dynamic view looks like a
normal
filesystem, so I think scm-local in principle is a fine solution. I think
.
- Even the changelog command can interpret .maven-scm-local
- For add and checkin commands, I don't think that changes are needed.
What do you think?
Regards,
Arne
--
View this message in context:
http://www.nabble.com/Update-over-scm-local-does-not-delete-files-removed-from
, they still
exist in the target directory. Especially after refactoring activities, this
leads to build errors.
Seems like a bug to me... Or am I missing something?
Many thanks,
Arne
--
View this message in context:
http://www.nabble.com/Update-over-scm-local-does-not-delete-files-removed
scm-local was developped for tests and it's used in some case when a scm provider isn't available
like dynamic-view support for Clearcase.
It's a very simple provider that copy file from sources directory, but it can't know if some files
are deleted because it doesn't have some metadata that
-local-does-not-delete-files-removed-from-source-dir-tf2257460.html#a6267099
Sent from the Continuum - Users forum at Nabble.com.
ArneD a écrit :
Emmanuel Venisse wrote:
scm-local was developped for tests and it's used in some case when a scm
provider isn't available
like dynamic-view support for Clearcase.
It's a very simple provider that copy file from sources directory, but it
can't know if some files
are
13 matches
Mail list logo
