I deleted and reinstalled Eclipse M5 with Ulrich/Dirk Olmes (Eclipse/WOLips
Hangs very often at build time) patch then I installed WOLips version 0.9.8
but Eclipse indicates WOLips in not configured properly. See status dialog
below.
Dialog text if list server drops attachments...:
This feature is not configured properly.
NO plugin: "org.objectstyle.wolips.profilling: included at runtime.
Here is my plugin directory listing:
C:\eclipse\plugins>ls
org.apache.ant_1.5.1
org.apache.lucene_1.2.1
org.apache.xerces_4.0.7
org.eclipse.ant.core_2.1.0
org.eclipse.compare_2.1.0
org.eclipse.core.boot_2.1.0
org.eclipse.core.resources.win32_2.1.0
org.eclipse.core.resources_2.1.0
org.eclipse.core.runtime_2.1.0
org.eclipse.debug.core_2.1.0
org.eclipse.debug.ui_2.1.0
org.eclipse.help.appserver_2.1.0
org.eclipse.help.ui.win32_2.1.0
org.eclipse.help.ui_2.1.0
org.eclipse.help.webapp_2.1.0
org.eclipse.help_2.1.0
org.eclipse.jdt.core_2.1.0
org.eclipse.jdt.debug.ui_2.1.0
org.eclipse.jdt.debug_2.1.0
org.eclipse.jdt.doc.isv_2.1.0
org.eclipse.jdt.doc.user_2.1.0
org.eclipse.jdt.junit_2.1.0
org.eclipse.jdt.launching_2.1.0
org.eclipse.jdt.source_2.1.0
org.eclipse.jdt.ui_2.1.0
org.eclipse.jdt_2.1.0
org.eclipse.jface.text_2.1.0
org.eclipse.jface_2.1.0
org.eclipse.pde.build_2.1.0
org.eclipse.pde.core_2.1.0
org.eclipse.pde.doc.user_2.1.0
org.eclipse.pde.runtime_2.1.0
org.eclipse.pde.source_2.1.0
org.eclipse.pde.ui_2.1.0
org.eclipse.pde_2.1.0
org.eclipse.platform.doc.isv_2.1.0
org.eclipse.platform.doc.user_2.1.0
org.eclipse.platform.source_2.1.0
org.eclipse.platform.win32.source_2.1.0
org.eclipse.platform.win32_2.1.0
org.eclipse.platform_2.1.0
org.eclipse.sdk.win32_2.1.0
org.eclipse.search_2.1.0
org.eclipse.swt.win32_2.1.0
org.eclipse.swt_2.1.0
org.eclipse.team.core_2.1.0
org.eclipse.team.cvs.core_2.1.0
org.eclipse.team.cvs.ssh_2.1.0
org.eclipse.team.cvs.ui_2.1.0
org.eclipse.team.ui_2.1.0
org.eclipse.text_2.1.0
org.eclipse.tomcat_4.0.6
org.eclipse.ui.editors_2.1.0
org.eclipse.ui.externaltools_2.1.0
org.eclipse.ui.views_2.1.0
org.eclipse.ui.win32_2.1.0
org.eclipse.ui.workbench.texteditor_2.1.0
org.eclipse.ui.workbench_2.1.0
org.eclipse.ui_2.1.0
org.eclipse.update.core.win32_2.1.0
org.eclipse.update.core_2.1.0
org.eclipse.update.ui.forms_2.1.0
org.eclipse.update.ui.win32_2.1.0
org.eclipse.update.ui_2.1.0
org.junit_3.8.1
org.objectstyle.wolips.devstudio_0.9.8
org.objectstyle.wolips.help_0.9.8
org.objectstyle.wolips.launching_0.9.8
org.objectstyle.wolips.profiling_0.9.8
org.objectstyle.wolips.source_0.9.8
org.objectstyle.wolips.support_0.9.8
org.objectstyle.wolips.targetbuilder_0.9.8
org.objectstyle.wolips_0.9.8
Here is a list of the contents of org.objectstyle.wolips.profiling_0.9.8:
C:\eclipse\plugins>ls -R org.objectstyle.wolips.profiling_0.9.8
icons lib plugin.properties plugin.xml
org.objectstyle.wolips.profiling_0.9.8/icons:
profiling
org.objectstyle.wolips.profiling_0.9.8/icons/profiling:
WOLips-profiling.gif
org.objectstyle.wolips.profiling_0.9.8/lib:
wolips-profiling.jar
Any one seen this problem?
J.R.
-----Original Message-----
From: Ulrich Köster [ mailto:ulric..ssense.com <mailto:ulric..ssense.com>
]
Sent: Tuesday, February 11, 2003 1:15 PM
To: JR Ruggentaler
Cc: woproject-de..bjectstyle.org
Subject: Re: WOLips build failure
Hi JR,
could you send me the file C:\Documents and
Settings\jr\Library\wobuild.properties
Thanks
Ulrich
Am Dienstag, 11.02.03 um 20:12 Uhr schrieb JR Ruggentaler:
> Ulrich,
> I tried the rebuild (Window->Preferences->WOLips Rebuild
> wobuild.properties) restart eclipse and rebuild project
> (Project->Rebuild
> Project) but I continue to get the following errors below.
>
> Kind Status Priority Description Resource In Folder
> Location
> Error The project was not built due to classpath errors
> (incomplete or involved in cycle). HelloWOrld
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOAccess.framework/Resources/
> Java/ja
> vaeoaccess.jar. HelloWOrld Build path
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOControl.framework/Resources/
> Java/j
> avaeocontrol.jar. HelloWOrld Build path
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaFoundation.framework/
> Resources/Java/
> javafoundation.jar. HelloWOrld Build path
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWebObjects.framework/
> Resources/Java/
> javawebobjects.jar. HelloWOrld Build path
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWOExtensions.framework/
> Resources/Jav
> a/JavaWOExtensions.jar. HelloWOrld Build path
> Error Unbound classpath variable path:
> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaXML.framework/Resources/Java/
> javaxml
> .jar. HelloWOrld Build path
>
> J.R.
> -----Original Message-----
> From: Ulrich Köster [ mailto:ulric..ssense.com
<mailto:ulric..ssense.com> ]
> Sent: Tuesday, February 11, 2003 12:42 PM
> To: JR Ruggentaler
> Cc: woproject-de..bjectstyle.org
> Subject: Re: Build error Ant can't find WOLips jars
>
>
> Hi JR,
>
> woproject is the stuff to build woapplication and woframeworks with
> ant(WOProject is located at the bottom of the download page.).
> WOLips is a plugin for Eclipse that includes WOProject.
>
> Could you try this to solve your problem:
>
> From the Eclipse menu choose
> Window->Preferences->WOLips Rebuild wobuild.properties an next launch
> and restart Eclipse.
>
> After restarting Eclipse select your project on the left and then from
> the menu Project->Rebuild Project.
> When the build has finished take a look at the task view at the bottom,
> if there are no WOLips entries you are fine.
>
> Normally there is no need to build you project manually. WOLips updates
> the target whenever there are changes in the project.
>
> Ulrich
>
> Am Dienstag, 11.02.03 um 19:29 Uhr schrieb JR Ruggentaler:
>
>> Ulrich,
>> yes I am using WOLips and Eclipse. I downloaded the file (
>> http://prdownloads.sourceforge.net/woproject/
<http://prdownloads.sourceforge.net/woproject/>
>> WOLips_0.9.8.tar.gz?download )
>> from sourceforge. I did not realize that WOLips and WOProject are
>> separate
>> projects. Do I only want WOLips to develop WO apps with Eclipse or do
>> I need
>> WOProject? I think I confused the names because both projects share
>> the same
>> home page and download page. I didn't even notice the WOProject
>> download on
>> sourceforge. I only grabbed the latest file which is WOLips v 0.9.8
>> and went
>> from there.
>>
>> J.R.
>>
>> -----Original Message-----
>> From: Ulrich Köster [ mailto:ulric..ssense.com
<mailto:ulric..ssense.com> ]
>> Sent: Tuesday, February 11, 2003 11:46 AM
>> To: JR Ruggentaler
>> Cc: woproject-de..bjectstyle.org
>> Subject: Re: Build error Ant can't find WOProject jars
>>
>>
>> Hi Jr,
>>
>> it looks like you are using the woproject support from within WOLips.
>> Am i right?
>>
>> Ulrich
>>
>>
>> Am Dienstag, 11.02.03 um 18:12 Uhr schrieb JR Ruggentaler:
>>
>>> Eclipse Platform
>>> Version: 2.1
>>> Build id: 200211151436
>>>
>>> I am trying to build the example HelloWOrld project shown in the
>>> WOProject
>>> documentation but the build fails. Here is the error from eclipse:
>>>
>>> Kind Status Priority Description Resource In
Folder
>>> Location
>>> Error Unbound classpath variable path:
>>> NEXT_SYSTEM_ROOT/Library/Frameworks/JavaXML.framework/Resources/Java/
>>> javaxml
>>> .jar. HelloWOrld Build path
>>>
>>> Here is the Ant output from the commnad like with verbose on:
>>>
>>> C:\eclipse\workspace\HelloWOrld>ant -verbose
>>> Apache Ant version 1.5.1 compiled on October 2 2002
>>> Buildfile: build.xml
>>> Detected Java version: 1.4 in: C:\j2sdk1.4.1_01\jre
>>> Detected OS: Windows 2000
>>> parsing buildfile build.xml with URI =
>>> file:C:/eclipse/workspace/HelloWOrld/buil
<file:C:/eclipse/workspace/HelloWOrld/buil>
>>> d.xml
>>> Project base dir set to: C:\eclipse\workspace\HelloWOrld
>>> Build sequence for target `build' is [setProps, init.build,
>>> build.woapp,
>>> refresh
>>> View, build]
>>> Complete build sequence is [setProps, init.build, build.woapp,
>>> refreshView,
>>> buil
>>> d, init.install, install, copy.strings, clean]
>>>
>>> setProps:
>>> [property] Loading C:\eclipse\workspace\HelloWOrld\build.properties
>>> [property] Loading C:\Documents and
>>> Settings\jr\Library\wobuild.properties
>>>
>>> init.build:
>>>
>>> build.woapp:
>>>
>>> BUILD FAILED
>>> file:C:/eclipse/workspace/HelloWOrld/build.xml:43: Could not create
>>> task or
>>> type
>>> of type: updateframeworksets.
>>>
>>> Ant could not find the task or a class this task relies upon.
>>>
>>> This is common and has a number of causes; the usual
>>> solutions are to read the manual pages then download and
>>> install needed JAR files, or fix the build file:
>>> - You have misspelt 'updateframeworksets'.
>>> Fix: check your spelling.
>>> - The task needs an external JAR file to execute
>>> and this is not found at the right place in the classpath.
>>> Fix: check the documentation for dependencies.
>>> Fix: declare the task.
>>> - The task is an Ant optional task and optional.jar is absent
>>> Fix: look for optional.jar in ANT_HOME/lib, download if needed
>>> - The task was not built into optional.jar as dependent
>>> libraries were not found at build time.
>>> Fix: look in the JAR to verify, then rebuild with the needed
>>> libraries, or download a release version from apache.org
>>> - The build file was written for a later version of Ant
>>> Fix: upgrade to at least the latest release version of Ant
>>> - The task is not an Ant core or optional task
>>> and needs to be declared using <taskdef>.
>>>
>>> Remember that for JAR files to be visible to Ant tasks implemented
>>> in ANT_HOME/lib, the files must be in the same directory or on the
>>> classpath
>>>
>>> Please neither file bug reports on this problem, nor email the
>>> Ant mailing lists, until all of these causes have been explored,
>>> as this is not an Ant bug.
>>> at
>>> org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownEleme
>>> nt.java:324)
>>> at
>>> org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:24
>>> 0)
>>> at
>>> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
>>> a:115)
>>> at org.apache.tools.ant.Task.perform(Task.java:318)
>>> at org.apache.tools.ant.Target.execute(Target.java:309)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:336)
>>> at
>>> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>>> at
>>> org.apache.tools.ant.Project.executeTargets(Project.java:1250)
>>> at org.apache.tools.ant.Main.runBuild(Main.java:610)
>>> at org.apache.tools.ant.Main.start(Main.java:196)
>>> at org.apache.tools.ant.Main.main(Main.java:235)
>>>
>>> Total time: 1 second
>>> C:\eclipse\workspace\HelloWOrld>
>>>
>>> It looks like Ant is unable to locate the WOProject jar(s) containing
>>> the
>>> updateframeworksets target. Has anyone seem this before and know how
>>> to fix
>>> it?
>>>
>>> Thanks!
>>> J.R.
This archive was generated by hypermail 2.0.0 : Wed Feb 12 2003 - 13:10:19 EST
