The new classpath system (coming ..... at some point, though I hear
from a test user that it is working well for the in-Eclipse portion)
is much more clear. It's more like:
<classpathentry kind = "con" path = "WOFramework/Ajax"/>
<classpathentry kind = "con" path = "WOFramework/ERExtensions"/>
etc
The current format is admittedly a little crazy, but it's really the
fault of Eclipse here. They don't provide support for adding
additional state of classpathentries, so you have to encode all of
your state in the path string. The main difference with the new style
is that it splits WO frameworks out into individual classpath entries
so we don't have to encode quite so much into a single path. It also
does more "guessing" at settings so it doesn't have as many knobs you
can turn, and thus fewer /nil/nil/1's.
ms
On Feb 29, 2008, at 12:36 PM, Ricardo Parada wrote:
> I asked the same a while back. I believe the answer is that it's
> normal. It's not a bug.
> But wait for Mike the man to confirm. ;-)
>
>
> On Feb 29, 2008, at 10:27 AM, Michael Hast wrote:
>
>> Hi everyone:
>>
>> I just updated to use Eclipse 3.3.2 and WOLips 4896. I created a
>> new workspace and checkout out one of my projects into it. I then
>> imported it via Eclipse. The .classpath file now contains a bunch
>> of ".../nil/1/0/1/..."
>>
>> Before:
>> -------
>> <classpathentry kind="con"
>> path="org.objectstyle.wolips.WO_CLASSPATH/Ajax/DSSAjax/
>> DSSDatabaseObject/DSSFoundation/DSSUtilities/DSSWebTools/
>> ERExtensions/ERJars/JavaWOExtensions/JavaEOAccess/JavaEOControl/
>> JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
>>
>> After:
>> ------
>> <classpathentry kind="con"
>> path="org.objectstyle.wolips.ContainerInitializer/10/1/Ajax/1/nil/1/
>> nil/1/0/1/false/10/1/DSSAjax/1/nil/1/nil/1/0/1/false/10/1/
>> DSSDatabaseObject/1/nil/1/nil/1/0/1/false/10/1/DSSFoundation/1/nil/
>> 1/nil/1/0/1/false/10/1/DSSUtilities/1/nil/1/nil/1/0/1/false/10/1/
>> DSSWebTools/1/nil/1/nil/1/0/1/false/10/1/ERExtensions/1/nil/1/nil/
>> 1/0/1/false/10/1/ERJars/1/nil/1/nil/1/0/1/false/10/1/
>> JavaWOExtensions/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/JavaWebO
>> bjects/1/nil/1/nil/1/0/1/false/10/1/JavaXML/1/nil/1/nil/1/0/1/
>> false"/>
>>
>> Wasn't that fixed a while ago? Why is it happening again? Do I need
>> to file a bug?
>>
>> Michael.
>> --
>> Tel: (520) 572-9410
>> Desert Sky Software: www.desertsky.com
>> Specializing in the Development and Hosting of
>> e-Business Applications.
>
This archive was generated by hypermail 2.0.0 : Fri Feb 29 2008 - 12:43:41 EST