On 11/10/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
I know that my official role on the project is 'mentor' not
troublemaker, but I take the view the more I break things, the better
the tests people get to write.
I agree, I like problem reports, it's the best way to improve a tool. And
Ivy still need a lot of improvements :-)
Here's my next problem:
I can declare that a filesystem layout shoudl be m2 compatible:
<filesystem name="team">
ivys="true" artifacts="true"
m2compatible="true" >
<artifact
pattern="${ivy.conf.dir}/repository/${maven2.pattern.ext}"/>
<ivy pattern="${ivy.conf.dir}/repository/${maven2.pattern}.xml"/>
</filesystem>
But it doesnt pick up, because the javax.j2ee pattern isnt being
switched to javax/j2ee.
[ivy:resolve] team: tried
/home/slo/Projects/examples/diary/repository/javax.j2ee/j2ee/1.5/j2ee-
1.5.xml
[ivy:resolve] team: tried artifact [ javax.j2ee | j2ee
| 1.5 ]/j2ee.jar[jar]:
[ivy:resolve]
/home/slo/Projects/examples/diary/repository/javax.j2ee/j2ee/1.5/j2ee-
1.5.jar
Is this intentional?
No it isn't, I'm even surprised it doesn't work. You can open a bug in jira
(still on http://jira.jayasoft.org, but will be moved to apache soon :-) ).
Xavier
