HI, > - download woproject.jar only once instead of once per framework > - remove reference to nexus.xyrality.net <http://nexus.xyrality.net/> > - remove postgres dependencies > - allow setting webobjectsVersion / wonderVersion before applying the plugin > since automatically added frameworks will use the default versions otherwise
Feel absolutely free to submit pull requests, preferable separate ones for this :-) Generally we're not that happy either yet with the default dependency mechanism; while "fine" for most projects sometimes you want to switch out some dependency which is not that easy to do afterwards in Gradle. >>> [2015-8-10 16:14:34 CEST] <main> Couldn't load properties file: >>> /Users/ycanal/WebObjects.properties at path: /Users/ycanal >>> [2015-8-10 16:14:34 CEST] <main> Unable to initialize WOProperties for >>> reason: Cannot find JavaWebObjects framework ! >>> java.lang.IllegalStateException: Unable to locate the "JavaWebObjects" >>> bundle >>> [2015-8-10 16:14:34 CEST] <main> A fatal exception occurred: >>> <WOApplication>: Cannot be initialized. >>> [2015-8-10 16:14:34 CEST] <main> >>> com.webobjects.foundation.NSForwardException >>> [java.lang.IllegalStateException] Unable to locate the "JavaWebObjects" >>> bundle:<WOApplication>: Cannot be initialized. >>> at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:918) >>> at >>> er.extensions.appserver.ajax.ERXAjaxApplication.<init>(ERXAjaxApplication.java:30) >>> at >>> er.extensions.appserver.ERXApplication.<init>(ERXApplication.java:1097) >>> at >>> fr.sophiacom.corason.foundation.appserver.COCoreApplication.<init>(COCoreApplication.java:22) >>> at fr.sophiacom.app.NRApplication.<init>(NRApplication.java:19) >>> at fr.sophiacom.app.Application.<init>(Application.java:30) >>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) >>> at >>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) >>> at >>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) >>> at java.lang.reflect.Constructor.newInstance(Constructor.java:422) >>> at java.lang.Class.newInstance(Class.java:442) >>> at com.webobjects.appserver.WOApplication.main(WOApplication.java:547) >>> at er.extensions.appserver.ERXApplication.main(ERXApplication.java:866) >>> at fr.sophiacom.app.Application.main(Application.java:25) >>> Caused by: java.lang.IllegalStateException: Unable to locate the >>> "JavaWebObjects" bundle >>> at >>> com.webobjects.appserver.WOResourceManager.__getJavaWebObjectsResourceAsStream(WOResourceManager.java:131) >>> at >>> com.webobjects.appserver._private.WOProperties.initUserDefaultsKeys(WOProperties.java:317) >>> at >>> com.webobjects.appserver.WOApplication._initWOApp(WOApplication.java:5743) >>> at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:779) >>> ... 13 more >>> >>> Do you have any idea how to fix that ? >>> Right now we are still keeping our old .project / build.xml /.classpath but >>> we would like to avoid maintaining 2 configurations. >> >> How did you import the project exactly? Did you keep the old .project and >> .classpath around for that or did you do a fresh import using the gradle >> plugin? There could be some issue with the classpath, if the old files are >> around, best would be to have gradle generate new ones. Have a look at the >> project properties -> Build path, there should be no more references to WO >> libraries but only to JARs in yourhomefolder/.gradle/ (see attachment), even >> for all the frameworks. > We tried to use gradle + eclipse in a new workspace after a "gradle > cleanEclipse eclipse" so the generated .classpath only reference .jar as in > your screenshot. > It may be a missing (runtime)dependency but the exception is not really > helpful :( Does that scenario give you the exact same stack trace? Which Eclipse version and Gradle plugin did you use? I investigated the new Buildship plugin but that one still has some issues that prevent this in a WO context, mainly it doesn't allow the gradle.build to add custom project natures. As the WOLips plugin for now is unaware of Buildship, the WO build nature never gets added to the project and thus some specific WO builders do not run at all. Check your generated .project if it includes the build command for org.objectstyle.wolips.incrementalbuilder and a project nature of org.objectstyle.wolips.incrementalapplicationnature or org.objectstyle.wolips.incrementalframeworknature. If this is missing, this can also result in some WOLips exceptions, if you try to access the WOLips part of the project properties. Greetings Dennis -- ----------------------------------------------------- Dennis Bliefernicht • Backend Development T +49 40 357 3001 62 [email protected] XYRALITY GmbH • Friedensallee 290 • 22763 Hamburg www.xyrality.com <http://www.xyrality.com/> Registergericht: Hamburg HRB 115332 Geschäftsführer: Sven Ossenbrüggen -----------------------------------------------------
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
