Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 37348 invoked from network); 28 Aug 2006 17:22:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Aug 2006 17:22:58 -0000 Received: (qmail 88760 invoked by uid 500); 28 Aug 2006 17:22:55 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 88706 invoked by uid 500); 28 Aug 2006 17:22:55 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 88695 invoked by uid 99); 28 Aug 2006 17:22:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 10:22:55 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of sppatel@gmail.com designates 66.249.82.233 as permitted sender) Received: from [66.249.82.233] (HELO wx-out-0506.google.com) (66.249.82.233) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 10:22:53 -0700 Received: by wx-out-0506.google.com with SMTP id i27so1758303wxd for ; Mon, 28 Aug 2006 10:22:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer:sender; b=DjkMq6r7fh38kvriGPRdXvGz7ZTErWtxe1HcYW22IokvfmYO8MlAgPmcMPd21pKDmRQPkHp8pagotlFbcqA/6r9bnpiCP9XtER8MP9NIp0WIvDgHGoWM+jItKQF8EABbfm7QmEx/+mkj54aayR1FyFJ7qLlxUKcMpK73aP/+90g= Received: by 10.70.100.1 with SMTP id x1mr9677318wxb; Mon, 28 Aug 2006 10:22:32 -0700 (PDT) Received: from ?192.168.1.2? ( [71.77.17.157]) by mx.gmail.com with ESMTP id h12sm7255458wxd.2006.08.28.10.22.31; Mon, 28 Aug 2006 10:22:32 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <4369f0ce0608281017o4d6fc23ai992127654934dcfb@mail.gmail.com> References: <4369f0ce0608280901m2d1164au6f9bf3bf00d6483f@mail.gmail.com> <226D1106-A3FB-4B44-B268-59565C359035@gmail.com> <4369f0ce0608281017o4d6fc23ai992127654934dcfb@mail.gmail.com> Content-Type: multipart/alternative; boundary=Apple-Mail-6-237418333 Message-Id: <252108C9-0B71-4AA9-A3FE-1CC9CEB0B85B@gmail.com> From: Sachin Patel Subject: Re: Eclipse as development tool for Geronimo components Date: Mon, 28 Aug 2006 13:22:41 -0400 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.2) Sender: Sachin Patel X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Apple-Mail-6-237418333 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Aug 28, 2006, at 1:17 PM, Heinz Drews wrote: > Hi Sachin, > The mvn eclipse:eclipse generates the .project files with the > proper reference. > This solves the problem you mentioned. Generally it would be a nice > start but naturally is the manual import a long and tedious exercise. > I guess an exported workspace might help. > > With debugging there is currently the problem that o.g...Daemon > requires the server.jar which then refers the modules via the manifest > as jars. This forces then to build with maven instead of directly > using the generated classes. Yes that is correct. Unfortunately there is no current solution for this. > Just building the changed component is sufficient with exception of > the ones referring xmlbeans. > > I was hoing that somebody had already made more progress but I will > not give up. > > Heinz > > On 8/28/06, Sachin Patel wrote: >> >> One of the big problems is that you can not use pure Eclipse to >> develop >> Geronimo. (just make code changes and compile) The maven eclipse >> plugin >> generates the .classpath in which all the projects reference only >> the built >> jars in the maven repository rather then the projects set up to >> reference >> each other. This causes a huge annoyance in that every time you >> make a >> change that affects another module, you will not see any >> compilation errors >> since the modified module has to be rebuilt and redeployed with >> maven so >> that the affected jar picks up the change. >> >> Also using the maven plugin for eclipse doesn't help, and enabling >> the maven >> build to occur using it helps the issue but makes the build process >> extremlely long. I haven't tried the m2 eclipse goal to see if it >> addresses >> some of these issues or not. >> >> >> On Aug 28, 2006, at 12:01 PM, Heinz Drews wrote: >> >> Hello, >> >> I want to use Eclipse for development and debugging of Geronimo >> components. >> The Eclipse plugin I have already used for application development. >> >> I have run mvn eclipse:eclipse, imported manually the projects but >> I'm >> hoping for a faster approach. And I'm facing several problems. First >> I could not found the xmlbeans in the source tree, modules referring >> them don't compile. Then I have not found a way to run G directly >> from the compilation produced by Eclipse. Only approach now is to >> build a module with Maven and copy the jar to the Geronimo tree. >> >> Help would be very much appreciated. >> Regards, >> Heinz >> >> >> -sachin >> >> -sachin --Apple-Mail-6-237418333 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
On Aug 28, 2006, = at 1:17 PM, Heinz Drews wrote:

Hi Sachin,
The mvn = eclipse:eclipse generates the .project files with the proper = reference.
This solves the problem you = mentioned.=A0 Generally it = would be a nice
start but naturally is the = manual import a long and tedious exercise.
I guess = an exported workspace might help.

With debugging there is = currently the problem that o.g...Daemon
requires = the server.jar which then refers the modules via the manifest
as jars.=A0 = This forces then to build with maven instead of = directly
using the generated = classes.

Yes that is correct.=A0 = Unfortunately=A0there is no current solution for = this.

Just building = the changed component is sufficient with exception of
the ones referring xmlbeans.

I was = hoing that somebody had already made more progress but I will not give = up.

Heinz

On 8/28/06, Sachin Patel <sppatel2@gmail.com> = wrote:

One of the big problems is that = you can not use pure Eclipse to develop
=A0 The maven eclipse = plugin
generates the .classpath in = which all the projects reference only the built
jars in the maven repository rather then the = projects set up to reference
each = other.=A0 This causes a = huge annoyance in that every time you make a
change that affects another module, you will not see = any compilation errors
since the modified module = has to be rebuilt and redeployed with maven so
that the affected jar picks up the change.

Also = using the maven plugin for eclipse doesn't help, and enabling the = maven
build to occur using it helps = the issue but makes the build process
=A0 I = haven't tried the m2 eclipse goal to see if it addresses
some of these issues or not.


On Aug 28, = 2006, at 12:01 PM, Heinz Drews wrote:


I want to use Eclipse for development and debugging = of Geronimo components.
The Eclipse = plugin I have already used for application development.

I have = run mvn eclipse:eclipse, imported manually the projects but = I'm
hoping for a faster = approach.=A0 And I'm facing = several problems. First
I could not = found the xmlbeans in the source tree, modules referring
them don't compile.=A0 Then I have not found a way = to run G directly
from the compilation produced by = Eclipse.=A0 Only approach = now is to
build a module with Maven = and=A0 copy the jar to the = Geronimo tree.

Help would be very much appreciated.
Regards,




=


=

= --Apple-Mail-6-237418333--