geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sachin Patel <>
Subject Re: eclipse deployment problem
Date Sat, 16 Jul 2005 03:39:04 GMT
I was able to resolve the problem for each of the projects containing this error by including
given project's snapshot from the Maven repository in the eclipse build path.  So you'll have
do the initial build from the command line so that you get the correct snapshot generated
installed into the repo.  Then start your workbench, fix the build paths, and then the errors
go away.

However, this won't last you long. :(

The problem is that even if you add the built jar to the classpath, then next time eclipse
a build it will delete these generated files.  Thus the next time you generate the snapshot
doing a 'rebuild' you'll get the errors again.

Eclipse can handle this type of situation, however.  You can added a "classes" folder (different

from output folder) to the .classpath.  Any files in this folder will be added to the classpath
will remain there and will NOT be deleted when eclipse triggers a build.

So the next step is if we can specify these files to go into a different directory rather
target/classes.  If so then we can mark the new destination folder as a "classes" folder at
content will be preserved.



Stefan Schmidt wrote:
> David,
> Could you tell me exactly which .jar (name + location) you are talking 
> about?
> David Jencks wrote:
>> This is caused by a new feature of xmlbeans2 that many eclipse users 
>> are less than happy with -- it generates one class (not java) file 
>> which needs to be in the classpath.  I put it in the target/classes 
>> directory.  
> of which module/plugin?
>> There was some discussion of this on the xmlbeans list and IIUC to fix 
>> this you need to include the built jar in the classpath.
>> thanks
>> david jencks
>> On Jul 15, 2005, at 3:51 AM, Stefan Schmidt wrote:
>>> Hi,
>>> The Wiki page about Eclipse deployment 
>>> ( seems to be 
>>> outdated due to the switch to xmlbeans 2 recently.
>>> I am getting lots of problems similar to this:
>>> 'schemaorg_apache_xmlbeans.system.sF35A79E0FA7890579F78B8B0A5364966 
>>> cannot be resolved'
>>> Can someone give me advice on how to solve this problem?
>>> Stefan Schmidt
> Stefan

View raw message