[
http://jira.codehaus.org/browse/MIDEA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111211
]
Edwin Punzalan edited comment on MIDEA-68 at 10/23/07 7:46 PM:
---------------------------------------------------------------
This is due to the ArtifactResolver's behavior. When it fails to resolve an
artifact, it throws an exception and the resulting artifact list is never
returned.
Maybe if the resolver can add the resolved artifacts along with the exception,
then its possible to add at least these resolved artifacts into module.
Otherwise, should it just fail ?
was:
This is due to the ArtifactResolver's behavior. When it fails to resolve an
artifact, it throws an exception and the resulting artifact list is never
returned.
Maybe if the resolver can add the resolved artifacts along with the exception,
then its possible.
> if a dependency is not found, it doesn't fail but excludes legitimate
> dependencies
> ----------------------------------------------------------------------------------
>
> Key: MIDEA-68
> URL: http://jira.codehaus.org/browse/MIDEA-68
> Project: Maven 2.x IDEA Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Brett Porter
> Assignee: Edwin Punzalan
>
> to reproduce:
> - have a multiproject with a module not installed
> - mvn idea:idea from the root
> - it will succeed, but the module file for the module that depends on the
> missing artifact contains module dependencies, but no jar dependencies
--
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
