|
||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||||
- [mojo-dev] [jira] (MNBMODULE-102) Transitive dependen... Herve Boutemy (JIRA)
- [mojo-dev] [jira] (MNBMODULE-102) Transitive dep... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-102) Transitive dep... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-102) Transitive dep... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-102) Transitive dep... Milos Kleint (JIRA)

http://fisheye.codehaus.org/changelog/mojo/?cs=17295
this appears to have fixed the batik-js issue and all org.mozilla._javascript_ packages are now correctly found. However the sample build is still failing because of commmons-logging references to Log and LogFactory. I assume that's some sort of error in maven metadata (missing dependency on commons logging someplace), I was not able to find the dependency anywhere in the affected artifacts..
bumped minimal required version of maven to 2.2.0, that's what maven-dependency is using. Tested with maven 3.0.4