Vincent Massol wrote:
>I've tried this on one of my SVN projects where I've voluntarily set up
>pom.artifactId != module name. It was working fine (I haven't tried it with
>CVS though). I'll try it on one of the Maven plugins when I have time. Do
>you know why you think it may not work? (that'll win me some time if you
>tell me your suspicions :-)).
>
>
This caught my eye, maybe its the only thing:
-
defaultValue="${maven.cruisecontrol.checkout.dir}/${module}/${relativeMavenBuildDir}/test-reports/"/>
+
defaultValue="${maven.cruisecontrol.checkout.dir}/${pom.artifactId}/${relativeMavenBuildDir}/test-reports/"/>
>CC *was* using heavily the SCM plugin before I made the changes. It's now no
>longer using it except that I've just realized that I haven't removed the
>scm:validate calls. I don't think they're required any more.
>
>
You're right. I'm having a frustrating morning and not paying enough
attention to what you were saying - sorry. However, the reason I was
confused is that you are still reading the SCM plugin vars from the
cruise control plugin (this requires calling scm:validate to populate).
If this works with both versions, this is what I think is best left
alone for now.
>Yes, I understand you're saying this... But what I'm telling you is that it
>currently does not support the URL notation without the ":" module (one pb
>that I know of is in the scm:validate goal). If that's a feature then it's
>all good :-).
>
>
right, reading ahead I see where you are coming from...
>Just try calling the scm:validate goal.
>
>Hmmm... Or, are you saying that the scm:validate goal is still there but is
>meant to be called only by code that has a URL using the ":" notation for
>modules? :-)
>
>
Exactly! Sorry if my comments in the code weren't clear enough.
>>If something is working in the current release of the SCM plugin (1.4.1)
>>and not working in 1.5 - let me know. Otherwise, let's please not change
>>it.
>>
>>
>
>I'm not planning to make any change. You're the "owner" of the 1.5 version.
>I'm just mentioning the issue that I've faced so that you know... ;-)
>
>
Sounds like we understand each other now and everything is working as
expected.
>BTW, I'm pretty happy with everything as I've got the cruisecontrol plugin
>working the way I want it.
>
>
great!
>FYI, the reason I was asking for a SCM 1.5 release date is because I'm
>writing (as you know) some text describing not only its usage but also the
>usage of plugins that depend on it and I'd like to know if it's going to be
>out before my text is out... :-) (the text should be out in about 3 months).
>
>
Yep, it won't take that long :)
>
>More generally speaking I'd like to get a chance to talk to you in the
>coming days/weeks about the Maven 1.1 time frame you imagine and about the
>big changes (wagon, scm, etc).
>
>
Sure, I'm doing some planning today, so maybe we can do that and get a
better roadmap published. There is an early one in core/trunk/xdocs.
>Thanks Brett and sorry for the hassle
>
>
No problem, sorry I don't have all the answers just yet :)
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
