Re: [Wonder-disc] wonder trunk (hopefully briefly) unstable

[Ramsey G. <ra...@by...>]

Just a heads up... I've just tried to update an existing workspace (created clean just before I updated from 3.5 to eclipse 3.6), and I get lots of red Xs related to build.  For ERExtensions, I get one:

Description	Resource	Path	Location	Type
The project was not built since the source file /ERExtensions/Sources/com/webobjects/foundation/NSBundle.java could not be read	ERExtensions		Unknown	Java Problem

Other projects say

Description	Resource	Path	Location	Type
The project cannot be built until its prerequisite ERExtensions is built. Cleaning and building all projects is recommended	BugTracker		Unknown	Java Problem

Creating a new workspace in 3.6 and importing the exact same things the same way appears to work properly though.

Ramsey

On Jul 2, 2010, at 2:19 PM, Mike Schrag wrote:

> We're working on including a new rapid turnaround feature into Wonder trunk, so you might run into some goofiness until we get all the kinks worked out.
> 
> If you are using Eclipse 3.6/WOLips 3.6 and want to try this feature out, do the following:
> 
> * Update to the latest WOLips 3.6
> * Update to the latest Wonder trunk
> * Eclipse Preferences=>WOLips=>Build, uncheck "Generate Bundles"
> * Delete your "build" folders (you won't need them anymore)
> * Launch your app
> 
> If things are working properly, what you SHOULD find is that your app looks exactly like it did 5 minutes prior. What you no longer have, though, is the mock bundle build folder, which means you get builds that should be substantially faster (as much as 25% in my testing) and the problems of the build folder being out-of-sync with your real source should be gone.
> 
> Things of Note
> * When running in deployment, everything should be 100% the same. If you see anything different, please let me know.
> * When "Generate Bundles" is ON, everything should be 100% the same. If you see anything different, please let me know.
> * The Maven folder structure might not match what people are other Maven people are using. I need feedback from Maven users who are interested in this feature.
> * Because bundles can now resolved without a bundle folder, it also means that it should be much easier to load bundles off of a completely normal classpath -- this should make it much easier to do things like JUnit testing and using mixing WO with other non-WO tools inside the IDE.
> 
> ms
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc