Wim Deblauwe a écrit :
2005/11/30, dan tran <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:
On 11/30/05, *Wim Deblauwe* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Good suggestions there Dan! It is indeed platform dependant and
following the maven 2 way, we should be able to put those things
in the settings.xml. Is that possible? That way, it's not needed
anymore in the scm url.
Unfortunatly we dont have access to setting.xml from maven-scm.
Therefore we may endup
implementing access to setting.xml in both maven-scm-plugin and
maven-release-plugin.
We may be able to replace release:perform step with scm:bootstrap.
So only one place has
the setting info. However I dont know if settings.xml has room for
this type of user preferences.
Should we mail Brett or someone else about this?
I don't want to access to settings.xml in maven-scm. setting.xml in a maven2 file and maven-scm can
be use without it, so i think it isn't a good idea to create a maven2 file for an independant tool.
If clearcase infos can't be specified in scm url, i think it's better to use system property or we
can read an environment variable like CLEARCASE_VIEW_STORE_PATH
On the view name: shouldn't we include the artifactId also. What
if Continuum wants to build 2 projects? It will need to create 2
views and they cannot have the same name.
This will solve your case. I do have case where I want to run same
project on diffirent schedules
( ie one for snapshot build happen every hr, one for release build
every night). In this case,
we have view name collision. This is a tough case to solve. we can
try to genereate a unique
view name if userer does not specify a view name. However in this
case, who is responsible
to remove the view after build is done? maven-scm creates it, then
it should allow method to
remove it.
But let's go with ${hostname}-{user.name
<http://user.name>}-${artifactId} first. Cant discuss forever ;-)
Does Continuum 'checkout' the code, builds and then removes the working
directory again? Or does the working directory remain and is there some
kind of update command that should happen?
We don't remove working directory actually, and we update this directory in each build. In future
version, continuum users will can choose to update or checkout sources. For example update for
hourly builds and full checkout for nightly builds
about config spec file, i guest you ignore this file at
release:perform time right?
since you will generate your own spec file base on a label right?
Yes, very true. We should ignore it, if there is a non-null tag in the
checkout command.
regards,
Wim
