Hi Karl-Heinz,
Karl Heinz Marbaise wrote:
Hi,
Move the Java code that should contain the version into an own
directory
tree (e.g. src/main/java-templates). Replace the version string with an
expression (e.g. ${project.version}) and use the copy-resources goal of
the resources plugin
Hi Maveners,
Greetings from Apache Olingo :)
I am working with the shade plugin to create ueber jar for Android use case.
The plugin is cool and technically everything is fine. But I am having problems
to get the LICENSE and NOTICE files included as required by Apache policies.
I tried out
I've been tracking this bug for a while now
Still no progress
You can track it here. There is a workaround there that i haven't tried
Let us know if you try it and whether it works
https://jira.codehaus.org/browse/MRELEASE-875
Alejandro Endo | Software Designer/Concepteur de logiciels
To: users@maven.apache.org
Subject: Re: mvn release with pom.xml not in root of git repo
From: alejandro.e...@miranda.com
Date: Fri, 18 Jul 2014 09:53:50 -0400
I've been tracking this bug for a while now
Still no progress
You can track it here. There is a workaround there that i
i do have the latest m-release-p, but the git version i don't know how to
set that nor what it currently is. How can i check that?
Thank you Martin
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Martin Gainty mgai...@hotmail.com
To: users@maven.apache.org
I tried it with the m-r-p 2.5 and 1.9 of the jgit provider - same issue it does
not work
/Domi
On 18 Jul 2014, at 17:01, alejandro.e...@miranda.com wrote:
i do have the latest m-release-p, but the git version i don't know how to
set that nor what it currently is. How can i check that?
Hi Jörg,
nice article ;-)
There's one comment I do not understand though:
The main disadvantage of this approach is that you can only use the
Implementation and Specification parts of your MANIFEST.MF file which
might be enough in some situations but not in all.
The comment is related to
Hi Russ,
this can only be done programmatically in a plugin/MOJO.
However, it is very easy: You need to invoke setFile(File) on the
MavenProject:
this.project.setFile( flattenedPomFile );
Before I also tried to configure maven-install-plugin and
maven-deploy-plugin to use a
There is a very simple process here. Turn on filtering in the resource
plugin, and add a .properties file that filters in what you need. Then
get those properties. No problems with unit tests, no problems keeping
track of _which_ MANIFEST.MF from classpath is the one you need.
On Fri, Jul 18,
