Ulrich Köster wrote:
>
> Am 25.08.2006 um 15:18 schrieb Henrique Prange:
>
>> Hi Ulrich,
>>
>> I think that Gulherme was talking about these lines of the .classpath
>> files:
>>
>> Sometimes the WO classpath seens like this:
>>
>> <classpathentry kind="con"
>> path="org.objectstyle.wolips.WO_CLASSPATH/ERExtensions/JavaWOExtensions/MOLUtilitarios/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
>>
>>
>> Occasionally seens like this one:
>>
>> <classpathentry kind="con"
>> path="org.objectstyle.wolips.ContainerInitializer/10/1/ERExtensions/1/nil/1/nil/1/0/1/false/10/1/JavaWOExtensions/1/nil/1/nil/1/0/1/false/10/1/MOLUtilitarios/1/nil/1/nil/1/0/1/false/10/1/shipping/1/nil/1/nil/1/0/1/false/10/1/JavaEOAccess/1/nil/1/nil/1/0/1/false/10/1/JavaEOControl/1/nil/1/nil/1/0/1/false/10/1/JavaFoundation/1/nil/1/nil/1/0/1/false/10/1/JavaJDBCAdaptor/1/nil/1/nil/1/0/1/false/10/1/JavaWebObjects/1/nil/1/nil/1/0/1/false/10/1/JavaXML/1/nil/1/nil/1/0/1/false"/>
>>
>>
>> Is it the predictable behavior? Why it happens?
>
> We have two classpath container in WOLips. When you remove the default
> one with new one you'll get a a different .classpath.
>>
>> I'm using another output folder as a replacement for "bin" and it
>> works. I just had to change the build.properties file.
>
> You could change the output folder to whatever you want and change it
> in the build.properties. target/classes is used by maven. So two tools
> are overwriting there output.
>>
>> Thanks,
>>
>> Henrique
>>
>> Ulrich Köster wrote:
>>> That's really evil:
>>>> <classpathentry kind="output" path="target/classes"/>
>>> You're in trouble when playing with a new version of a JDK. Keep the
>>> tools side by side and not mixed.
>>> The behavior of the car mainly depends on the driver :-) You've
>>> changed the classpath.
>>> I have no idea why you framework is sometimes there and sometimes not.
>>> Uli
>>> Am 24.08.2006 um 21:54 schrieb Guilherme melo:
>>>> hello , i am new to WO (i am using WOlips version 2.0.0.3063 and i
>>>> have been having some inconsistencies with the class paths ,one
>>>> of my frameworks appears on the classpath but dosen't apear on the
>>>> list of frameworframeworks loaded by WOLips(WO Frameworks) and
>>>> randomly it comes back. also sometimes it has the behavior below
>>>>
>>>> <classpath>
>>>> <classpathentry kind="src" path="src/main/java"/>
>>>> <classpathentry excluding="**" output="src/main/resources"
>>>> kind="src" path="src/main/resources"/>
>>>> <classpathentry kind="con"
>>>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>>>> <classpathentry kind="con"
>>>> path="org.objectstyle.wolips.WO_CLASSPATH/ERExtensions/JavaWOExtensions/MOLUtilitarios/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
>>>>
>>>> <classpathentry kind="con"
>>>> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>>>> <classpathentry kind="output" path="target/classes"/>
>>>> </classpath>
>>>>
>>>> <classpath>
>>>> <classpathentry kind="src" path="src/main/java"/>
>>>> <classpathentry kind="con"
>>>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>>>> <classpathentry kind="con"
>>>> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>>>> <classpathentry kind="con"
>>>> path="org.objectstyle.wolips.ContainerInitializer/10/1/ERExtensions/1/nil/1/nil/1/0/1/false/10/1/JavaWOExtensions/1/nil/1/nil/1/0/1/false/10/1/MOLUtilitarios/1/nil/1/nil/1/0/1/false/10/1/shipping/1/nil/1/nil/1/0/1/false/10/1/JavaEOAccess/1/nil/1/nil/1/0/1/false/10/1/JavaEOControl/1/nil/1/nil/1/0/1/false/10/1/JavaFoundation/1/nil/1/nil/1/0/1/false/10/1/JavaJDBCAdaptor/1/nil/1/nil/1/0/1/false/10/1/JavaWebObjects/1/nil/1/nil/1/0/1/false/10/1/JavaXML/1/nil/1/nil/1/0/1/false"/>
>>>>
>>>> <classpathentry kind="output" path="target/classes"/>
>>>> </classpath>
>>>>
>>>> is this happening to anyone else ?? anyone know the reason ? thx !!
>
>
i am also getting this error , this is freezing up my workspace ,ive
tried reinstaling WO is it related ?
java.lang.NullPointerException
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2186)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.initializeRoots(DeltaProcessingState.java:286)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:717)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4023)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4197)
at
org.objectstyle.wolips.jdt.classpath.WOClasspathContainerInitializer.initialize(WOClasspathContainerInitializer.java:98)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900)
at
org.eclipse.jdt.internal.core.JavaModelManager$7.run(JavaModelManager.java:1846)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:1855)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1265)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2014)
at
org.objectstyle.wolips.jdt.ant.UpdateOtherClasspathIncludeFiles.buildIncludeFiles(UpdateOtherClasspathIncludeFiles.java:101)
at
org.objectstyle.wolips.jdt.ant.UpdateOtherClasspathIncludeFiles.execute(UpdateOtherClasspathIncludeFiles.java:89)
at
org.objectstyle.wolips.jdt.listener.UpdateIncludeFilesJob.runInWorkspace(UpdateIncludeFilesJob.java:91)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
This archive was generated by hypermail 2.0.0 : Mon Aug 28 2006 - 22:30:04 EDT