You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Andy <an...@gmx.de> on 2015/02/10 21:17:25 UTC

TomEE Maven Plugin possible enhancement to use 'provided' scope

Came up in a maven plugin discussion today the possiblity of using a 
projects 'provided' scope artifacts as a lib entry somthing like: 
<lib>provided:exclude:[pattern or none]</lib>

The idea being that all 'provided' scope artifacts are 'usually' 
expected to be extracted/copied to [TomEE]/lib - Except those defined by 
an optional exclude pattern, or none for all.

This would not be a guarantee for ear projects I guess, but probably 
workable for war based.

The win is not having to add all the 'provided' libs maven coordinates 
by hand.

WDYT? Sounds useful, and or possible?

Andy.

-- 
   Andy Gumbrecht
   https://twitter.com/AndyGeeDe


Re: TomEE Maven Plugin possible enhancement to use 'provided' scope

Posted by Romain Manni-Bucau <rm...@gmail.com>.
to be honest I dont get the syntax you propose but got the idea so let
discuss it.

Here some pointers:
1) would means all tomee provided stuff should be excluded (that's the
most common provided deps IMO) -> so i'd use include instead of
exclude
2) this case was originally designed to be handled with unzip (you
have a zip you explode in tomee lib) -> guess you think to N modules
where all modules need different dependencies (side note: some modules
will miss some explicit dependencies for tomee runtime if they dont
need it in the tests without being an issue but it could be completed
manually)

About the syntax i'd go back to something more common ie a prefix
(maven?) and then coordinate with wildcards:

<lib>maven:com.company:*:jar:*:provided</lib>

Then last question would be: what about transitive deps? i'm super
cold to support them for the container since I never saw it done right
but we can add an option:

<lib>maven:com.company:*:jar:*:provided?transitiveDependencies=true</lib>

it would add compile+runtime deps of this dep to lib as well

wdyt?


Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau


2015-02-10 21:17 GMT+01:00 Andy <an...@gmx.de>:
> Came up in a maven plugin discussion today the possiblity of using a
> projects 'provided' scope artifacts as a lib entry somthing like:
> <lib>provided:exclude:[pattern or none]</lib>
>
> The idea being that all 'provided' scope artifacts are 'usually' expected to
> be extracted/copied to [TomEE]/lib - Except those defined by an optional
> exclude pattern, or none for all.
>
> This would not be a guarantee for ear projects I guess, but probably
> workable for war based.
>
> The win is not having to add all the 'provided' libs maven coordinates by
> hand.
>
> WDYT? Sounds useful, and or possible?
>
> Andy.
>
> --
>   Andy Gumbrecht
>   https://twitter.com/AndyGeeDe
>