Mark Struberg <[EMAIL PROTECTED]> wrote on 05/06/2008 18:32:23:
> > So long as maven supports your scm...
> But then it is still much better to get this SCM supported then having
> hundred of developers tweaking around manually.
>
> Which SCM you need isn't supported yet?
>
> Since I already wr
No, I meant exactly what I said.
Maven itself needs to be able to check in/out etc from your SCM.
We use ClearCase in with UCM Dynamic Views, which is not supported
(particularly well (if at all?)) by maven.
So, in that instance, we will need to basically to a release manually.
If maven fully
Hi Simon,
Thanks a lot for that reply.
Yes, I have a workflow in ANT (with CVS), which asks the user whether he
wants a timestamp or a version build. With that as a mindset, I was looking
on Maven. You have identified it right that Maven has its own stuff when it
comes to versioning the builds.
W
I don't think this information is what Niranjan is really looking for.
He appears to have some workflow that he is used to with some other
build tool, and is trying to use Maven to reproduce that same workflow.
But my guess is that it isn't a workflow that maven is designed to
implement, hence the
> So long as maven supports your scm...
But then it is still much better to get this SCM supported then having hundred
of developers tweaking around manually.
Which SCM you need isn't supported yet?
Since I already wrote the maven-scm-providers-git, I maybe can help you in
writing another one.
repo!
LieGrü,
strub
--- Niranjan Deshpande <[EMAIL PROTECTED]> schrieb am Do, 5.6.2008:
> Von: Niranjan Deshpande <[EMAIL PROTECTED]>
> Betreff: Re: AW: modifying version number in POM
> An: "Maven Users List"
> Datum: Donnerstag, 5. Juni 2008, 8:49
> Hi
Niranjan,
The maven release plugin allows performing a dry run of the prepare goal [1].
mvn release:prepare -DdryRun=true
The dry run performs all the local file changes but without executing any SCM
operations (commits and tagging).
To revert the file changes from the dry run you can also us
Hi Chris,
So you meant to say that SNAPSHOT will be repaced by a timestamp at the run
time?
also, can we avoid the chekin of the pom and tagging of the project that
happens after mvn release:prepare? i am rather experimenting on things
and dnt want to invite the wrath of other developers if ther r
Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008 22:53:35:
> Maybe i missed the point, or you did.
>
> The usual behaviour is to always have a SNAPSHOT version in your SCM
> e.g. 1.4-SNAPSHOT
>
> If you make a build, you simply use the maven-release-plugin
>
> $>mvn release:prepare
> this
build version
So there is usually no need to set versions in the pom manually.
LieGrü,
strub
--- Niranjan Deshpande <[EMAIL PROTECTED]> schrieb am Mi, 4.6.2008:
> Von: Niranjan Deshpande <[EMAIL PROTECTED]>
> Betreff: modifying version number in POM
> An: users@maven.apac
Niranjan Deshpande schrieb:
> In POM we have a version number of the project as
>
> 1.4
>
> Instead of hardcoding it each time I take a new build, I would like to
> replace it with the one entered by the user when he takes a buld using
> maven. I want the user to enter the version number, which wi
In POM we have a version number of the project as
1.4
Instead of hardcoding it each time I take a new build, I would like to
replace it with the one entered by the user when he takes a buld using
maven. I want the user to enter the version number, which will be used
placed in maven's pom.xml an
In POM we have a version number of the project as
1.4
Instead of hardcoding it each time I take a new build, I would like to
replace it with the one entered by the user when he takes a buld using
maven. I want the user to enter the version number, which will be used
placed in maven's pom.xml and
13 matches
Mail list logo
