I have fixed this already in Wagon 3.2.0 in WAGON-486. Use a Maven
version which has this builtin. It should fix your NAT problem.
Reread the tickets, my explanations were very detailed.
Michael
Am 2018-12-27 um 00:20 schrieb Sander Verhagen:
Hi all,
I'm sorry for reposting this[1]. But I'm
Hi all,
I'm sorry for reposting this[1]. But I'm sure there is someone in this
community who could inspire me to fix this. We are still seeing a lot of
stalled Maven builds on Bitbucket, and we don't know anymore what to do about
it, besides moving off of Bitbucket (which we've talked
Hi Jochen,
On 26/12/18 23:27, Jochen Wiedmann wrote:
On Wed, Dec 26, 2018 at 10:54 PM Karl Heinz Marbaise wrote:
I have written a Maven plugin, which must interpret values like
${project.artifactId}, and the like.
Where exactly do you use them ? Are injected as parameters ?
No, they are
On Wed, Dec 26, 2018 at 10:54 PM Karl Heinz Marbaise wrote:
> > I have written a Maven plugin, which must interpret values like
> > ${project.artifactId}, and the like.
>
> Where exactly do you use them ? Are injected as parameters ?
No, they are basically snippets, which have been extracted
Hi Jochen,
On 26/12/18 22:36, Jochen Wiedmann wrote:
Hi,
I have written a Maven plugin, which must interpret values like
${project.artifactId}, and the like.
Where exactly do you use them ? Are injected as parameters ?
My first attempt was to use
Hi,
I have written a Maven plugin, which must interpret values like
${project.artifactId}, and the like.
My first attempt was to use
project.getProperties().get("project.artifactId"), but that seems
to work only for the values, which are configured in the POM's
property section. So, what would be
