You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:32:10 UTC
[jira] (MECLIPSE-317) Unable to build inside eclipse when module
name and artifact-id are not the same
[ https://jira.codehaus.org/browse/MECLIPSE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MECLIPSE-317.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> Unable to build inside eclipse when module name and artifact-id are not the same
> --------------------------------------------------------------------------------
>
> Key: MECLIPSE-317
> URL: https://jira.codehaus.org/browse/MECLIPSE-317
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: xp, eclipse 3.3
> Reporter: Dan Tran
>
> and example of this is issue is
> http://svn.apache.org/repos/asf/myfaces/orchestra/trunk
> where the core is buildable but core15 and examples are not
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)