My bad, the properties allowed are:
${revision}
${changelist}
${sha1}
See https://maven.apache.org/docs/3.2.1/release-notes.html
Then look at https://maven.apache.org/docs/3.3.1/release-notes.html for the
core extension loading mechanism
On Tuesday 8 March 2016, Gary Gregory > wrote:
> On Tue,
On Tue, Mar 8, 2016 at 11:28 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> In the .mvn folder put an extension that contributes the ${rev} property
> based on whatever you seem safe
>
Where does this mystical .mvn folder reside, oh knowing one?
Is ${rev} a built in name?
Gary
In the .mvn folder put an extension that contributes the ${rev} property
based on whatever you seem safe
Then just have the project version include the ${rev} at the appropriate
place
On Tuesday 8 March 2016, Gary Gregory wrote:
> On Mon, Mar 7, 2016 at 6:53 PM, Eric B >
> wrote:
>
> > The firs
On Mon, Mar 7, 2016 at 6:53 PM, Eric B wrote:
> The first question I have to ask is what you are trying to accomplish with
> your continuous-delivery?
We have a Maven multi-module build which has thousands of unit tests. We
use Bamboo for CI and if we get a green build that means that all the t
More details might help.
Are you using an IDE?
Can you describe where your files are located and show some of the
console output from Maven.
It seems unlikely that you are compiling the files that you have changed.
Maven has no memory about source files and would not be able to
reconstruct fil
