The File vs String types note is the relevant part IIRC... It's not just
file vs string though
On Tuesday, 25 March 2014, Henrik Østerlund Gram
wrote:
> Thanks for the link. It was quite informative, but I'm again a little
> confused because it is stated in your explanation,
> the sections wil
Thanks for the link. It was quite informative, but I'm again a little
confused because it is stated in your explanation,
the sections will have mojo-injected properties evaluated,
but that isn't the case in my example. I was trying to have such
properties evaluated in a element inside a
elemen
Please read my answer to a similar question on Stack Overflow:
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
On 23 March 2014 21:36, Henrik Østerlund Gram wrote:
> I stumbled over some rather strange behaviour regarding properties.
Hi,
> Hi Henrik,
FYI, my projects use buildnumber-maven-plugin with git and it works great.
Probably the docs are just out of date.
That looks like. I have created the following JIRA ticket for this.
https://jira.codehaus.org/browse/MBUILDNUM-119
If you have supplementals/infos etc. don't
Hi Henrik,
FYI, my projects use buildnumber-maven-plugin with git and it works great.
Probably the docs are just out of date.
Regards,
Curtis
On Mar 24, 2014 3:05 AM, "Henrik Østerlund Gram"
wrote:
> The one at
> http://mojo.codehaus.org/buildnumber-maven-plugin/create-mojo.html ? It
> states
Ok, I see.
Any chance of such a change making it into the official ear-plugin? I
think it would be generally useful to be able to reference properties in
the env-entry values. Could post a pull request if desired, but judging by
the months old ones at https://github.com/apache/maven-plugins/pull
It doesn't matter which plugin you use to set the property. What does
matter is when the property substitution takes place. It normally happens
in the very beginning of the Maven build when the pom is read, before the
build lifecycle is executed and way before your plugin is executed. So you
need t
The one at
http://mojo.codehaus.org/buildnumber-maven-plugin/create-mojo.html ? It
states in the first couple of lines that it only works with subversion and
I'm using git.
Aside from that, I can't really see why it would make a difference; how
many ways are there to set properties? I did establ
Hi,
Out of curiosity, why don't you use the seemingly equivalent mojo
buildnumber maven plugin? May not be your issue, but may be the plugin
you're using doesn't create properties in the right way (no offense, just
trying to guess)?
My 2 cents
Le 23 mars 2014 22:37, "Henrik Østerlund Gram" a
écrit
I stumbled over some rather strange behaviour regarding properties. It
seems properties generated by one plugin are not always resolved for other
plugins and I can't figure out why.
I use a plugin to make info about the git branch available in the
properties so it can be passed to other plugins.
10 matches
Mail list logo