Alex Karasulu wrote:
I agree with Alan here. Maven can get ugly with you if you start to
stray from it's conventions. It might be worth considering his approach.
It seems that we just have to figure out exactly what its conventions are...
However, I am more aligned with Chris, get it working now and sweat the
details later.
-> richard
Alex
Richard S. Hall wrote:
Carlos Sanchez wrote:
On 1/26/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
One thing we could possibly do is to allow both:
<embed-dependency>
groupId=org.mortbay.jetty;artifactId=jetty,*;scope=runtime</embed-
dependency>
or
<embed>
<match groupId="org.mortbay.jetty" artifactId="jetty"/>
<match scope="runtime"/>
</embed>
In the spirit of not trying to make more work for you, I would be
happy to contribute the latter.
A maven convention is not to use xml attributes but subelements
<embed>
<match>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty<artifactId/>
</match>
</embed>
Do I hear allowing all three!! ;-)
-> richard
