On 2017-01-03T19:32:59 +0100
Guillaume Boué wrote:
> It sounds like you're looking for the parse-version goal of the
> build-helper-maven-plugin:
On 2017-01-03T19:36:16 +0100
Karl Heinz Marbaise wrote:
> Hi,
>
> have you taken a look at the build-helper-maven-plugin
On 2017-01-03T12:45:19 -
Hi,
In addition to the suggestion of others to use parse-version, the
build-helper-maven-plugin also has the regex-property goal, which lets you
assign a property based on a regex. Here is an example:
sanitize-version
regex-property
sanitizedVersion
${project.version}
Hi,
have you taken a look at the build-helper-maven-plugin which has a goal
parse-version which will result in appropriate properties which than can
be used to achieve what you like.
Kind regards
Karl Heinz Marbaise
http://www.mojohaus.org/build-helper-maven-plugin/parse-version-mojo.html
Hi,
It sounds like you're looking for the parse-version goal of the
build-helper-maven-plugin:
http://www.mojohaus.org/build-helper-maven-plugin/parse-version-mojo.html.
It can decompose the project version into several Maven properties.
There is an example of usage here
http://www.mojohaus.
Hello.
I have a small project that contains a plugin for Blender[0]. Plugins
in Blender are Python files that must contain a hash value at the top
of the file containing version information. The version information has
to be numeric constants as Blender actually parses this data rather
than evalua