You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2015/12/25 12:49:51 UTC
[jira] [Closed] (MECLIPSE-441) Packaging type "maven-plugin" causes
unresolved dependencies in multi-module build
[ https://issues.apache.org/jira/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MECLIPSE-441.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
The Apache Maven team has decided to retire the maven-eclipse-plugin, so this issue won't be fixed.
> Packaging type "maven-plugin" causes unresolved dependencies in multi-module build
> ----------------------------------------------------------------------------------
>
> Key: MECLIPSE-441
> URL: https://issues.apache.org/jira/browse/MECLIPSE-441
> Project: Maven Eclipse Plugin (RETIRED)
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
> Affects Versions: 2.5.1
> Environment: Linux 2.6 (Xubuntu 8.0)
> Reporter: Alex Rau
> Assignee: Robert Scholte
> Attachments: maven_bug.tar.bz2
>
>
> Attached a sample project setup.
> How to reproduce:
> - untar attachment
> - cd into reactor folder
> - call mvn eclipse:eclipse
> Artifact x:project_plugin cannot be resolved, however the dependency and the modules set is correct.
> As soon as the packaging type of the maven-plugin is changed to "jar" it works as expected.
> Installing the maven-plugin project first is perhaps a workaround (a bad one, not tried yet). Makes however a clean/from scratch multi-module build in eclipse very ugly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)