Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <50F8EF54.5020402@xanthippe.ping.de>
Date: Fri, 18 Jan 2013 07:44:36 +0100
From: Dirk Olmes <dirk@xanthippe.ping.de>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:10.0.11) Gecko/20121115 Thunderbird/10.0.11
MIME-Version: 1.0
To: Maven Users List <users@maven.apache.org>
Subject: Re: Write dependency information to a file (new custom plugin)
References: 
 <CAL=o=--=tWen2EnoSg6JZQ6usL5G-4tqqFFTGuf-PLSJm6P-xQ@mail.gmail.com>
In-Reply-To: 
 <CAL=o=--=tWen2EnoSg6JZQ6usL5G-4tqqFFTGuf-PLSJm6P-xQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 01/17/2013 05:09 PM, Danny Schimke wrote:
> Hi Dirk,
> 
> thank you very much. Yes, it works, I figured out, but something very
> important is missing here: the properties does not contain the version
> number of the artifact. 

Well the property does not but the value points to an absolute path of
the artifact in the local repository, which includes the version.

You did not say much about your use case - for me, the full path was all
I needed. See https://github.com/dirk-olmes/dependency-plugin-demo for a
demo that shows the properties and the values.

> My coworker said I should not use Groovy - I am
> with him, this should work out of the box without being dependent on a
> further technology.

Well yes it should. But it doesn't so you can now either give up or use
the groovy plugin as "yet another plugin in the build".

-dirk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org