FYI....the installer is just about to reach an open beta status (OS X
10.5.1 & WO 5.4 - only). Probably next week.
It will include the following components:
1) Eclipse 3.3.2 (Stream) + Basic WOLips integration & Configuration
2) Latest nightly builds for WOLips
3) JavaEOGenerator + Templates
4) launchd arguments for auto-initiation of wotaskd and javamonitor
upon boot
We're just trying to wrap up a few bugs left in the IDE settings, and
manage the mess that the new version of PackageMaker leaves
behind...it has a nasty habit of "forgetting" an application bundle
inside a folder (which is fine, unless you actually need to use
Eclipse!)...and wreaking small havoc with filesystem
permissions....repeatedly.
Thanks,
jeremy
On Nov 29, 2007, at 9:17 PM, Mike Schrag wrote:
>> So I imported the plugs-in with Import-> Plug-ins and Fragments, I
>> now have all plug-ins as projects in Eclipse.
> I have never done this step ... I don't even know what it actually
> does.
>
>> I also imported WOLips source (from Subversion) into Eclipse.
>>
>> Next step: adding a WOLips.product file into the woproject/wolips
>> folder. From this place, I am able to run the standalone IDE with
>> "Launch an Eclipse application". BUT if I try to export the
>> product with the "Eclipse Product export wizard" and I run the
>> exported IDE, I always get:
>>
>> 07-11-29 20:32:43 [0x0-0x1d01d].org.eclipse.eclipse[2107] Exception
>> in thread "main"
>> 07-11-29 20:32:43 [0x0-0x1d01d].org.eclipse.eclipse[2107]
>> java.lang.NoClassDefFoundError: org/eclipse/equinox/launcher/
>> JNIBridge
>> 07-11-29 20:32:43 [0x0-0x1d01d].org.eclipse.eclipse[2107] Exception
>> in thread "main"
>> 07-11-29 20:32:43 [0x0-0x1d01d].org.eclipse.eclipse[2107]
>> java.lang.NoClassDefFoundError: org/eclipse/equinox/launcher/Main
>> 07-11-29 20:32:48 com.apple.launchd[356]
>> ([0x0-0x1d01d].org.eclipse.eclipse[2107]) Exited with exit code: 255
> I don't know what this is -- never seen it ... You should checkout
> woproject/wolips/entityModeler to see how Entity Modeler builds, but
> there are definitely oddities in this process. Eclipse product
> deploy wants to overwrite build.xml files with its own temp
> build.xml (and then delete them, which is super retarded), but
> build.xml's are required to actually make a wolips build, so I don't
> know if you'll run into problems or not. Entity Modeler only needs
> a subset of the plugins, so I don't know what happens if you try to
> do this for all of them. I also don't know what happens if you try
> to make a wolips product and then try to do an upgrade from the
> Eclipse update site, whether it actually installs the features
> properly or not necessary to know which build number is installed.
> I have a feeling you're going to be fighting this one. Also, Jeremy
> Matthews is working on (basically has a) WOLips installer package
> with all the parts. The only thing that's different is that he
> doesn't have an overridden welcome page, but honestly I'm not sure
> it's worth the pain to go through this eclipse deploy process just
> for that, but I'll let you be the judge of your own pain threshold.
>
> ms
>
This archive was generated by hypermail 2.0.0 : Thu Nov 29 2007 - 22:37:21 EST