Hello Hervé,
as an enduser, I just define this as a dependency to e.g. the
maven-dependency-plugin, right?
Regards Mirko
--
Sent from my mobile
On May 3, 2013 2:04 AM, "Hervé BOUTEMY" wrote:
> Hi,
>
> We solved 2 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&ver
Yes that should do it.
On Fri, May 3, 2013 at 3:20 AM, Mirko Friedenhagen
wrote:
> Hello Hervé,
>
> as an enduser, I just define this as a dependency to e.g. the
> maven-dependency-plugin, right?
>
> Regards Mirko
> --
> Sent from my mobile
> On May 3, 2013 2:04 AM, "Hervé BOUTEMY" wrote:
>
>>
Hi Mirko,
Basically yes.
But this time, this won't work with m-dependency-p because I changed the API
that the plugin uses: or you'll nee to use m-dependency-p 2.8-SNAPSHOT
This will work with m-shade-p and m-project-info-reports-p (notice this last
one requires a dependency to m-reporting-exe
Hello,
I'm trying to have the execution of release:branch trigger the execution of a
different plugin. I am aware that plugin goals can be bundled together by
attaching them to lifecycle phases, optionally using profiles, but is there a
way to bind the plugin execution directly to the execution
