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 !!
This archive was generated by hypermail 2.0.0 : Fri Aug 25 2006 - 09:46:58 EDT