|
||||||||
|
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] (MJSIMP-9) Conflicting dependenc... Cam Christiansen (JIRA)
- [mojo-dev] [jira] (MJSIMP-9) Conflicting depe... Cam Christiansen (JIRA)
- [mojo-dev] [jira] (MJSIMP-9) Conflicting depe... Cam Christiansen (JIRA)
- [mojo-dev] [jira] (MJSIMP-9) Conflicting depe... Cam Christiansen (JIRA)
- [mojo-dev] [jira] (MJSIMP-9) Conflicting depe... Cam Christiansen (JIRA)

After looking at the code more, it looks like it was an intentional design decision to only get the transitive dependencies of js dependencies. The real issue (I incorrectly stated it above) is that I need the whole dependency tree traversed for js dependencies, not just the direct line of the immediate js dependencies. I am working on fixing this and seeing if it is viable to do so. I still have the problem though that I'm working directly on the 1.0.1 release code.