maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MECLIPSE-639) amp projects should be considered a java project
Date Sun, 06 Sep 2015 20:46:05 GMT

     [ https://issues.apache.org/jira/browse/MECLIPSE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MECLIPSE-639.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> amp projects should be considered a java project
> ------------------------------------------------
>
>                 Key: MECLIPSE-639
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-639
>             Project: Maven Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>            Reporter: billerby
>
> I'm developing packages for Alfresco (large open source ECM, www.alfresco.com) which
uses a packaging type named "amp" (Alfresco Module Package). When trying to generate eclipse
files for my newly created maven amp archetype (http://maven.alfresco.com/nexus/content/repositories/alfresco-docs/maven-alfresco-lifecycle/maven-alfresco-archetypes/maven-alfresco-amp-archetype/index.html)
by running mvn eclipse:eclipse only the .project file is created. After some investigation
I found out the reason is that the packaging type "amp" is not considered to be a java project
by the maven eclipse plugin. It would be much appreciated if you would like to add "amp" as
an accepted packaging type in this plugin.
> Thanks!
> /Erik Billerby



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message