[ http://jira.codehaus.org/browse/MIDEA-16?page=comments#action_55380 ]
Geoffrey commented on MIDEA-16: ------------------------------- A similar problem are optional transitive dependencies: the plugin now requires them to be there. My project depends on acegi, which has a lot of optional dependencies, that I don't use, don't need and don't want to hear about, such as javamail, activation: mvn idea:idea ... required artifacts missing: javax.resource:connector:jar:1.0 javax.mail:mail:jar:1.3.2 javax.activation:activation:jar:1.0.2 for the artifact: org.x.y:y-model:jar:0.0.1-SNAPSHOT Thos optional dependencies shouldn't even bee assumed silently I believe. > idea target only works after compilation > ---------------------------------------- > > Key: MIDEA-16 > URL: http://jira.codehaus.org/browse/MIDEA-16 > Project: Maven 2.x Idea Plugin > Type: Bug > Reporter: Matthew Pocock > > > In a multi-module project, you have to build it before you can idea:idea it. > Let's have modules a and b, with b depending on a. The idea plugin runs for > a, but then fails on b because it can't find a.jar, as you've not build a > yet. However, there are case where it's not practical to build the project > before loading it up in idea e.g. if you've checked it out of svn to fix a > bug that prevents compilation. > The work-arround would be for the idea plugin to require resolution for all > jars that are external dependencies but to silently assume the presence of > all jars that would be built as part of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
