Strange thing happens,
under maven2 the contents of ${plugin} is empty, ( ie
plugin.getArtifacts() = null ), does it has something to do with me
upgrade to latest mojo-parent?
Thanks
-D
On Sun, Feb 24, 2013 at 10:30 AM, Dan Tran <[email protected]> wrote:
> Thanks Robert, this gives me a good start
>
> -D
>
> On Sun, Feb 24, 2013 at 2:46 AM, Robert Scholte <[email protected]> wrote:
>> Hi Dan,
>>
>> ${plugin} will return the ProjectDescriptor[1]
>> From here you can get the artifacts or artifactsMap and maybe you could
>> filter on runtime-scoped artifacts.
>> That will probably be good enough most of the time, but it not really
>> reliable (you're not sure if you get only the required artifacts).
>> You could also do the same trick as with docletArtifacts in the
>> maven-javadoc-plugin, but now the plugin is responsible for collecting these
>> artifacts. Because of this the maven-release-plugin is not able to recognize
>> these as dependencies it can't fail the build if these contain snapshots.
>>
>> Robert
>>
>> [1]
>> http://maven.apache.org/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html
>>
>> Op Sun, 24 Feb 2013 09:25:02 +0100 schreef Dan Tran <[email protected]>:
>>
>>> Hello,
>>>
>>> I am trying to fix https://jira.codehaus.org/browse/MOJO-1534 need
>>> advice to how achieve the solution mentioned in to topic.
>>>
>>> Very much appreciated.
>>>
>>> Thanks
>>>
>>> -D
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
