On 12/14/06, David Jencks <[EMAIL PROTECTED]> wrote:
I agree that spec support is the way to go.

the jee5 ear lets you specify a lib directory (default is "lib")
where all the jars inside get added to the classpath.  We could work
on jee5 support, that ought to keep everyone happy.  Does the
defaultJarBundleDir do this?  I guess if so it might need to be put
in the generated application.xml??  As you can tell I haven't looked
at what the plugin actually does now.

Well yes it does just do
[...]
<configuration>
 <defaultJarBundleDir>lib</defaultJarBundleDir>
 [...]
</configuration>

No we can imagine configuration profiles. If we're using Jave EE5,
this is the default value and libraries (artifact with type = jar) are
automatically copied to this lib directory. Sounds good to me.

There is no solution for 1.3 and 1.4 though but it's a start.

Thanks,
Stéphane


thanks
david jencks

>
> Cheers,
> Stéphane
>
> On 12/14/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> Using the v2.3-SNAPSHOT version of the ear plugin, I am struggling
>> to get
>> the application.xml file built correctly.
>>
>> Between maven1 and maven2, the ejb plugin lost it's ability to bundle
>> dependencies inside the ejb.
>>
>> This means (as I understand it) that it's now up to the ear plugin
>> to add
>> all the dependencies to the application.xml file.
>>
>> However, it seems that the maven-ear-plugin does not have any
>> documented
>> functionality to add dependencies to application.xml, except for
>> explicitly declaring dependencies using the jarModule tag.
>>
>> This duplicates the dependency list, and removes all the power behind
>> transitive dependency management, which is supposed to handle
>> dependencies
>> for you.
>>
>> Is there a setting I am not seeing, or does the ear plugin have no
>> dependency management features at all?
>>
>> Regards,
>> Graham
>> --
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to