You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jacob Nowosatka (JIRA)" <ji...@apache.org> on 2011/07/18 20:55:57 UTC
[jira] [Created] (OPENJPA-2031) Unable to import maven projects
with m2e version 1.0
Unable to import maven projects with m2e version 1.0
----------------------------------------------------
Key: OPENJPA-2031
URL: https://issues.apache.org/jira/browse/OPENJPA-2031
Project: OpenJPA
Issue Type: Improvement
Reporter: Jacob Nowosatka
Priority: Minor
Using m2e v1.0, importing maven projects will cause errors such as:
maven-dependency-plugin(goals "copy-dependencies", "unpack") is not supported by m2e
Plugin execution not covered by lifecycle configuration:
The reason for these errors is described in the link.
http://wiki.eclipse.org/M2E_plugin_execution_not_covered#m2e_maven_plugin_coverage_status
A solution to this problem using the method set forth by the wiki is attached. The patch applies to the pom.xml in openjpa-parent.
This should solve any maven related problem. However, there still may be errors in the source of openjpa-kernel and openjpa-openbooks. The first is solved by adding target/generated-sources/javacc to the build path of openjpa-kernel. The second is done in the same way, except with target/generated-metamodel/java to the build path of openjpa-openbooks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-2031) Unable to import maven projects
with m2e version 1.0
Posted by "Jacob Nowosatka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Nowosatka updated OPENJPA-2031:
-------------------------------------
Attachment: OPENJPA-2031.patch.txt
> Unable to import maven projects with m2e version 1.0
> ----------------------------------------------------
>
> Key: OPENJPA-2031
> URL: https://issues.apache.org/jira/browse/OPENJPA-2031
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Jacob Nowosatka
> Priority: Minor
> Attachments: OPENJPA-2031.patch.txt
>
>
> Using m2e v1.0, importing maven projects will cause errors such as:
> maven-dependency-plugin(goals "copy-dependencies", "unpack") is not supported by m2e
> Plugin execution not covered by lifecycle configuration:
> The reason for these errors is described in the link.
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered#m2e_maven_plugin_coverage_status
> A solution to this problem using the method set forth by the wiki is attached. The patch applies to the pom.xml in openjpa-parent.
> This should solve any maven related problem. However, there still may be errors in the source of openjpa-kernel and openjpa-openbooks. The first is solved by adding target/generated-sources/javacc to the build path of openjpa-kernel. The second is done in the same way, except with target/generated-metamodel/java to the build path of openjpa-openbooks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENJPA-2031) Unable to import maven projects with
m2e version 1.0
Posted by "Albert Lee (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-2031.
-------------------------------
Close issue in preparation for 2.2.0 release.
> Unable to import maven projects with m2e version 1.0
> ----------------------------------------------------
>
> Key: OPENJPA-2031
> URL: https://issues.apache.org/jira/browse/OPENJPA-2031
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Jacob Nowosatka
> Assignee: Jacob Nowosatka
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: OPENJPA-2031.patch.txt
>
>
> Using m2e v1.0, importing maven projects will cause errors such as:
> maven-dependency-plugin(goals "copy-dependencies", "unpack") is not supported by m2e
> Plugin execution not covered by lifecycle configuration:
> The reason for these errors is described in the link.
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered#m2e_maven_plugin_coverage_status
> A solution to this problem using the method set forth by the wiki is attached. The patch applies to the pom.xml in openjpa-parent.
> This should solve any maven related problem. However, there still may be errors in the source of openjpa-kernel and openjpa-openbooks. The first is solved by adding target/generated-sources/javacc to the build path of openjpa-kernel. The second is done in the same way, except with target/generated-metamodel/java to the build path of openjpa-openbooks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENJPA-2031) Unable to import maven projects
with m2e version 1.0
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick resolved OPENJPA-2031.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Thanks for the patch, this worked great in my environment.
> Unable to import maven projects with m2e version 1.0
> ----------------------------------------------------
>
> Key: OPENJPA-2031
> URL: https://issues.apache.org/jira/browse/OPENJPA-2031
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Jacob Nowosatka
> Assignee: Jacob Nowosatka
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: OPENJPA-2031.patch.txt
>
>
> Using m2e v1.0, importing maven projects will cause errors such as:
> maven-dependency-plugin(goals "copy-dependencies", "unpack") is not supported by m2e
> Plugin execution not covered by lifecycle configuration:
> The reason for these errors is described in the link.
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered#m2e_maven_plugin_coverage_status
> A solution to this problem using the method set forth by the wiki is attached. The patch applies to the pom.xml in openjpa-parent.
> This should solve any maven related problem. However, there still may be errors in the source of openjpa-kernel and openjpa-openbooks. The first is solved by adding target/generated-sources/javacc to the build path of openjpa-kernel. The second is done in the same way, except with target/generated-metamodel/java to the build path of openjpa-openbooks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OPENJPA-2031) Unable to import maven projects
with m2e version 1.0
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick reassigned OPENJPA-2031:
-------------------------------------
Assignee: Jacob Nowosatka
> Unable to import maven projects with m2e version 1.0
> ----------------------------------------------------
>
> Key: OPENJPA-2031
> URL: https://issues.apache.org/jira/browse/OPENJPA-2031
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Jacob Nowosatka
> Assignee: Jacob Nowosatka
> Priority: Minor
> Attachments: OPENJPA-2031.patch.txt
>
>
> Using m2e v1.0, importing maven projects will cause errors such as:
> maven-dependency-plugin(goals "copy-dependencies", "unpack") is not supported by m2e
> Plugin execution not covered by lifecycle configuration:
> The reason for these errors is described in the link.
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered#m2e_maven_plugin_coverage_status
> A solution to this problem using the method set forth by the wiki is attached. The patch applies to the pom.xml in openjpa-parent.
> This should solve any maven related problem. However, there still may be errors in the source of openjpa-kernel and openjpa-openbooks. The first is solved by adding target/generated-sources/javacc to the build path of openjpa-kernel. The second is done in the same way, except with target/generated-metamodel/java to the build path of openjpa-openbooks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira