New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug with WOLips.framework and WOLips 3.7 #5
Comments
I can't reproduce this problem doing as you have described, the app launches fine for me under 3.7 with and without the Wonder source in my workspace How are you building/installing the WOLips.framework? |
I'm using the build from webobjects.mdimension.com. Tried with a June build, and with the latest. |
Building it from the latest source doesn't work, same thing for David Holt. |
Problem arises when WOLips is set to bundle-less. If bundles are enabled, problem goes away. |
I still cannot reproduce this with bundle-less builds enabled or disabled. |
I have the same problem with a plain Eclipse (3.7.1) with only WOLips (3.7.10096) as an extra plugin. As soon as I disable bundles generation, I get the exception. It's a brand new workspace with a "Wonder Application" in it, the only did I did was to add the WOLips framework. $ java -version On OS X 10.6.8. |
Closing this issue since I can only reproduce in my account, using another user on my MBP don't have that issue. |
While trying out all templates, I found that the Wonder D2W App template won't launch the app because of this exception:
[2011-9-18 22:54:59 EDT]
A fatal exception occurred: ERXExtensions have not been initialized. Please report the classpath and the rest of the bundles to the Wonder mailing list:Remaining frameworks: [WOLips]
Classpath:
..
If I remove WOLips from the list of frameworks, it works fine. Now, if I open the WOLips framework project in Eclipse, the problem goes away. If I use WOLips 3.6, problem goes away too.
So this exception arises when you use WOLips 3.7 with the build WOLips.framework. I also tried to revert the WOLips 3.7 code base to the first commit for 3.7, and I get the same problem. David Holt reported the same problem.
The text was updated successfully, but these errors were encountered: