Beware...you cause subtle break in maven if you rely on them being jars.
if they have gone only as far as the compile phase in the lifecycle
then they will not be jars but instead
${project.build.outputDirectory}s for each of the dependencies...
The very best Maven Way plugins respect that difference enabling one
to run tests and build everything without having to go as far as
package in the lifecycle
-Stephen
On 15 June 2011 16:37, Benson Margulies <[email protected]> wrote:
> Why? It just wants to construct a list of jars and pass them to the
> compiler, not actually include them in a classloader. Not that's it is
> especially hard to get from one to the other.
>
> On Wed, Jun 15, 2011 at 11:12 AM, Jochen Wiedmann
> <[email protected]> wrote:
>> The maven-compiler-plugin should do exactly that.
>>
>> On Wed, Jun 15, 2011 at 5:09 PM, Benson Margulies <[email protected]>
>> wrote:
>>> I find myself looking to create a plugin where, as part of execution,
>>> it wants to create a classpath composed of the declared dependencies.
>>> Can anyone suggest a model?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>>
>>
>> --
>> Capitalism is the astounding belief that the most wickedest of men
>> will do the most wickedest of things for the greatest good of
>> everyone.
>>
>> John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes)
>>
>> ---------------------------------------------------------------------
>> 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]
