Re: Compiling ERExtensions in Sierra no worky

On the one hand, I am tempted to ask how you got it working. I see the previous messages and tried to use the info in them. But I was really responding to the fact that every update needs to need some kind of fix and it may be that maven is more reliable when it comes to compiling java classe

Re: Compiling ERExtensions in Sierra no worky

Interesting, I feel a little behind the curve here. I finally feel that my ‘ant’ build and install is working exactly correct. I think that Sierra ‘fixed’ a bunch of things, or maybe my constant hacking made it work. But now I should learn to use maven. Did anyone do a WOWODC session on maven?

Re: Compiling ERExtensions in Sierra no worky

Hi Ray, interesting stuff. Did the javadoc also work correctly with maven, did it generate proper index html files on Sierra as well? Perhaps it's also time to move the Jenkins wonder build to maven. Maik > Am 19.05.2017 um 23:10 schrieb Ray Kiddy : > > > So, I just have to say, I wanted to

Re: Compiling ERExtensions in Sierra no worky

So, I just have to say, I wanted to build wonder on my new Sierra laptop and of course it did not work. And then, after checking several things, downloading this and that, checking some other things, sacrificing a fatted calf and so on and so forth, thinking about making this work just starti

Re: Compiling ERExtensions in Sierra no worky

>> Thanks Hugi for the links! I’m definitely going to be looking into this >> soon-ish. Goodbye fluffy bunny. > > The wiki is semi-useful, but some of it is stale and unhelpful. As far as > migration of existing projects goes, follow Hugi’s recipe: > > https://gist.github.com/hugith/e9a49e91fbc

Re: Compiling ERExtensions in Sierra no worky

Hi Tim, On 12 May 2017, at 08:57, Tim Worman wrote: > Thanks Hugi for the links! I’m definitely going to be looking into this > soon-ish. Goodbye fluffy bunny. The wiki is semi-useful, but some of it is stale and unhelpful. As far as migration of existing projects goes, follow Hugi’s recipe:

Re: Compiling ERExtensions in Sierra no worky

Thanks Hugi for the links! I’m definitely going to be looking into this soon-ish. Goodbye fluffy bunny. Good to “see" you both here. T > On May 11, 2017, at 2:24 PM, Hugi Thordarson wrote: > > That’s it — I’m calling the cops. Who are you and what have you done with our > beloved Chuck “The

Re: Compiling ERExtensions in Sierra no worky

That’s it — I’m calling the cops. Who are you and what have you done with our beloved Chuck “The Ant” Hill? But yes, I absolutely agree. When I first started trying out Maven with WO, I made a few attempts at “soft” migration so I wouldn’t have to change the structure of my projects (changing t

Re: Compiling ERExtensions in Sierra no worky

I am not saying that Maven feels unnatural or un-WO like, but that there are Maven ways of doing things (like the project layout) and fighting that to do it “the way that I always have” just leads to a poor Maven experience. With Ant you can beat it into whatever shape you want. Chuck On 20

Re: Compiling ERExtensions in Sierra no worky

> Wait, what? You had a life before?!!? :-P Good point. > Maven is actually good :-O > and useful :-O :-O > provided that you do things The Maven Way and don’t try and fight it to do > things the WO way. I know where you’re coming from and I totally agreed with you for a long time. But…

Re: Compiling ERExtensions in Sierra no worky

Wait, what? You had a life before?!!? :-P Maven is actually good and useful provided that you do things The Maven Way and don’t try and fight it to do things the WO way. Yes, Chuck just said that. No, I have not been drinking. Chuck On 2017-05-11, 12:29 PM, "Webobjects-dev on behalf of Hu

Re: Compiling ERExtensions in Sierra no worky

The documentation on the wiki seems pretty outdated. But the transition isn’t really complicated. Most of the work is the manual work of converting the Eclipse project—here’s a basic guide for achieving that for an application project: https://gist.github.com/hugith/e9a49e91fbcebe204e0feb4989f5

Re: Compiling ERExtensions in Sierra no worky

I’m definitely interested in moving to Maven. It seems it can be a rocky transition from what I’ve seen. But it also positions one better to make the move to other technologies that probably utilize Maven too (Cayenne?). Is the wiki pretty up-to-date regarding what’s required to mavenize? Tim U

Re: Compiling ERExtensions in Sierra no worky

You can also switch to maven and skip that whole “install WebObjects”-mess [ducks and runs away before anyone can beat him up] - hugi > On 9 May 2017, at 16:05, Calven Eggert wrote: > > I’ve finally managed to get the ERExtensions to compile without errors. The > trick was to place the comm

Re: Compiling ERExtensions in Sierra no worky

I’ve finally managed to get the ERExtensions to compile without errors. The trick was to place the commons-lang3-3.5 folder (downloaded from apache) in the Libraries folder in ERExtensions like so: /Users/calven/WonderSource/Frameworks/Core/ERExtensions/Libraries And now all my WO projects run

Re: Compiling ERExtensions in Sierra no worky

I deleted the Root folder and did the ant frameworks and unfortunately the build on the ERExtensions is still an error as described before (error: package org.apache.commons.lang3.builder does not exist) So I think that if this problem gets solved then I think it’ll all work. What is that all

Re: Compiling ERExtensions in Sierra no worky

> Am 08.05.2017 um 14:30 schrieb Calven Eggert : > > Hmmm, do you mean ERExtensions? I don’t have ERXExtensions in my build path. yes > > >> On May 8, 2017, at 8:24 AM, Johann Werner wrote: >> >> The reported constructor method signature >> >> (String, String, String, String, int, boolean,

Re: Compiling ERExtensions in Sierra no worky

Hmmm, do you mean ERExtensions? I don’t have ERXExtensions in my build path. > On May 8, 2017, at 8:24 AM, Johann Werner wrote: > > The reported constructor method signature > > (String, String, String, String, int, boolean, boolean) > > does only exist in Wonder’s variant of WOCookie and no

Re: Compiling ERExtensions in Sierra no worky

The reported constructor method signature (String, String, String, String, int, boolean, boolean) does only exist in Wonder’s variant of WOCookie and not in the original WOCookie class. Thus you probably have some sort of class ordering problem in your project. Check if ERXExtensions comes befo

Re: Compiling ERExtensions in Sierra no worky

I changed the woolies.properties to new point to the woolies.543.properties and now it works. Thanks for that hint. I suppose with the changes we discussed earlier in getting this setup it messed this up. However, I’m still having problems with one of my apps where I try to run it from ecli

Re: Compiling ERExtensions in Sierra no worky

I think you are going to find that your Apple WebObjects files are hurt. Of course you will not be able to use the apple WebObjects.mpkg will not install WO. You will need to use the WOInstaller.jar. What do you have in your wobuild.properties (~/Library), and what about ~/Library/Application\

Re: Compiling ERExtensions in Sierra no worky

I get the same error for this source. > On May 7, 2017, at 5:57 PM, Theodore Petrosky wrote: > > So, you are trying to build ERExtensions only? What do you get when you do an > ‘ant frameworks’ at the top level of your repo? > > >> On May 7, 2017, at 4:23 PM, Calven Eggert >

Re: Compiling ERExtensions in Sierra no worky

So, you are trying to build ERExtensions only? What do you get when you do an ‘ant frameworks’ at the top level of your repo? > On May 7, 2017, at 4:23 PM, Calven Eggert wrote: > > I’ve been installing my dev environment on a new Mac in Sierra however, I’m > having problems with one of my app

Compiling ERExtensions in Sierra no worky

I’ve been installing my dev environment on a new Mac in Sierra however, I’m having problems with one of my applications. When I build the Wonder code I get an error with ERExtensions. See below. I’ve downloaded the file org.apache.commons.lang3 cause of the error message but I still get the er