Return-Path: X-Original-To: apmail-cayenne-user-archive@www.apache.org Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F05369A9F for ; Sun, 25 Mar 2012 13:29:44 +0000 (UTC) Received: (qmail 30233 invoked by uid 500); 25 Mar 2012 13:29:44 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 30215 invoked by uid 500); 25 Mar 2012 13:29:44 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 30205 invoked by uid 99); 25 Mar 2012 13:29:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2012 13:29:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.78.103.231] (HELO vorsha.objectstyle.org) (208.78.103.231) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 25 Mar 2012 13:29:37 +0000 Received: (qmail 458 invoked from network); 25 Mar 2012 13:29:16 -0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 25 Mar 2012 13:29:16 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: cgen and newer M2Eclipse plugin From: Andrus Adamchik In-Reply-To: Date: Sun, 25 Mar 2012 16:29:14 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@cayenne.apache.org X-Mailer: Apple Mail (2.1084) Sorry, I forgot to mention one step - after the M2Eclipse upgrade = projects would lose their Maven "nature". So after adding XML below to = the pom, I had to right-click the project and do "Configure > Convert to = Maven Project". The result was that Eclipse metadata files are now = compatible with both new and old versions of M2Eclipse. Here is a = trimmed diff from upgrade commit to give you an idea: --- .classpath 2012-03-15 14:35:48 UTC (rev 40403) +++ .classpath 2012-03-15 14:41:26 UTC (rev 40404) @@ -1,8 +1,9 @@ + --- .project 2012-03-15 14:35:48 UTC (rev 40403) +++ .project 2012-03-15 14:41:26 UTC (rev 40404) @@ -29,8 +29,14 @@ + + org.eclipse.m2e.core.maven2Builder + + + + org.eclipse.m2e.core.maven2Nature org.eclipse.jdt.core.javanature Andrus --------------- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a On Mar 25, 2012, at 3:29 PM, Andrus Adamchik wrote: > I just had some problems with cgen declaration in the POM after = upgrading to 1.0 version of M2Eclipse plugin. Turns out Cayenne projects = now need the following declaration in the POM for the plugin to = correctly work with cgen. This does not affect the command line build, = only the behavior within Eclipse.=20 >=20 > See http://wiki.eclipse.org/M2E_plugin_execution_not_covered for more = details. >=20 > We may need to contribute an extension to M2Eclipse, so that it = recognizes Cayenne out of the box without this hack in the future. For = now add this to your poms. >=20 > Andrus >=20 >=20 > > > > > org.eclipse.m2e > = lifecycle-mapping > 1.0.0 > > > > = > = > = org.apache.cayenne.plugins > = maven-cayenne-plugin > = [1.0,) > = > = cgen > = > = > > = > = > = > > > > > > >