maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Brechbühl <rotscher...@gmail.com>
Subject Re: Lightweight maven-releases, or an alternative to the maven-release-plugin
Date Wed, 01 May 2013 10:31:04 GMT
Hi Nambi

1. Why does the jar need to be part of maven installation? Why not a plugin?

The version given on the command line is passed into the model when it's
loaded (model.setVersion(version)). And this is done for all modules when
the model is read. When having a plugin I would change the version when the
module is built. And I guess, it's not possible at that time.

And as there is a different install-plugin for the install phase, I'll
change that in the lifecycle mapper (which is also part of the maven
installation).

2. Can it generate a version based on some strategy? Looks like the version
needs to be supplied through CLI parameter.

With Release 0.2.0 there are more possibilites to "generate" a unique
version number: when the feature is active but no version is provided then
the pom version is taken and a buildnumber is appended. The buildnumber is
either taken from jenkins/hudson (env.BUILD_NUMBER) or its an incremented
integer stored in a file named .buildnumber

Of course, it would be possible to think about different version generation
strategies.

3. Some releases need a TAG in SCM while some releases don't require a TAG.
   Is there a possibility of having this functionality?

I guess this would be possible. To me storing the revision number into the
manifest files is more important. With this information you can always tag
and/or branch from a specific revision.

4. What happens if the release is trying to overwrite an already existing
version on the repository?
This should be configured in your central maven repo (e.g. Nexus/Archiva)
where you configure a repository to not allow releases to be overwritten.

5. What kind of formats are supported? jar, war etc.
I don't get this question... Actually all generated artifacts are handled
the same way.

Cheers,
Rotsch



2013/5/1 Sankaran, Nambi <nsankaran@ebay.com>

> Hi Rotch
>
> This sounds quite interesting and I feel it would be useful to a lot of
> projects.
> The release-plugin as it is, is not very flexible.
>
> Questions
>
> 1. Why does the jar need to be part of maven installation? Why not a
> plugin?
> 2. Can it generate a version based on some strategy? Looks like the
> version needs to be supplied through CLI parameter.
> 3. Some releases need a TAG in SCM while some releases don't require a TAG.
>    Is there a possibility of having this functionality?
> 4. What happens if the release is trying to overwrite an already existing
> version on the repository?
> 5. What kind of formats are supported? jar, war etc.
>
> Thanks
> nambi
>
> -----Original Message-----
> From: Roger Brechbühl [mailto:rotscher.ch@gmail.com]
> Sent: Tuesday, April 30, 2013 2:22 PM
> To: users@maven.apache.org
> Subject: Lightweight maven-releases, or an alternative to the
> maven-release-plugin
>
> Hi all
>
> Maybe somebody is interested in how a release could be built in a more
> lightweight and safe way than with the maven-release-plugin. Especially
> recommended for nightly releases.
>
> It's not yet released, but basically fully working:
>
> *mvn clean install -Dversion.override=1.2.3-S-5*
>
>
> https://github.com/rotscher/emerging/tree/version.override-with_maven_install-2.4
> .
>
> Have fun.
> Rotsch
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message