Re: Compiling ERExtensions in Sierra no worky

[Paul Hoadley]

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:

https://gist.github.com/hugith/e9a49e91fbcebe204e0feb4989f55631 


but also take a look at my fork of that:

https://gist.github.com/paulhoadley/cd15b90c94eb8c640fddd9ac3fbbc6dc 


They cover some slightly different areas. Hugi—we really should merge them. I 
also think Hugi’s being modest—once you’ve done a few, you can probably migrate 
a project in under 20 minutes. To "dependency management" and "third party 
library integration", I would add "simplified interaction with Jenkins” as a 
huge benefit. Throw out all those workspace setup scripts: just point Jenkins 
at your repo and you’re pretty much done. We’ve been using Maven for about 6 
months, and haven’t looked back.

If you want to live-blog your experience here on the list, Hugi and I would be 
happy to help troubleshoot if you run into any issues.


-- 
Paul Hoadley
http://logicsquad.net/


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Compiling ERExtensions in Sierra no worky

[Tim Worman]

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 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 the structure for an experimental change 
> seemed scary at the time). That didn’t go well, so I backed up and moved to 
> using Ivy with Ant for dependency management for a while. Phew. Talk about a 
> couple of months of my life that I would like to get back.
> 
> But never looked back after going full Maven.
> 
> - hugi
> 
> 
>> On 11 May 2017, at 20:56, Chuck Hill  wrote:
>> 
>> 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 2017-05-11, 1:01 PM, "Hugi Thordarson"  wrote:
>> 
>>> 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… I found that once I gave it a chance, it soon started to feel 
>> very WO Way-ish.
>> 
>>> Yes, Chuck just said that.  No, I have not been drinking.
>> 
>>   I find that extremely unlikely :-P.
>> 
>>   - hugi
>> 
>> 
>> 
>>> Chuck
>>> 
>>> 
>>> On 2017-05-11, 12:29 PM, "Webobjects-dev on behalf of Hugi Thordarson" 
>>> >> h...@karlmenn.is> wrote:
>>> 
>>>  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/e9a49e91fbcebe204e0feb4989f55631
>>> 
>>>  Note that before you can actually do this, though, you’ll have to copy the 
>>> following file to ~/.m2/settings.xml. It informs maven about the 
>>> WOCommunity maven repositories where the WO specific stuff lives.
>>> 
>>>  https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf
>>> 
>>>  After having done this with a few dozen projects, migrating a regular 
>>> no-frills Fluffy Bunny project to maven takes me less than an hour these 
>>> days (including upgrading the Jenkins build :). I sincerely recommend you 
>>> give it a try. It’s a huge boon to productivity; dependency management 
>>> alone will save you hours of headaches if you’re using any 3rd party 
>>> software. And not having to manage framework installations is awesome.
>>> 
>>>  Also, I currently don't have a life so I’m usually online to help if you 
>>> run into issues ;).
>>> 
>>>  Cheers,
>>>  - hugi
>>> 
>>> 
>>> 
 On 11 May 2017, at 18:59, Tim Worman  wrote:
 
 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
 UCLA GSE&IS
 
> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
> 
> 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 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 in Eclipse and from the terminal.
>> 
>> Calven
>> 
>>> 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 not in the original 
>>> WOCookie class. Thus you probably have some sort of class ordering 
>>> problem in your project. Check if ERXExtensions comes before 
>>> JavaWebObjects.
>>> 
>>> jw
>>> 
>>> 
 Am 08.05.2017 um 14:15 schrieb Calven Eggert :
 
 
 I changed the woolies.properties to new point to the 
 woolies.543.propert

Re: Compiling ERExtensions in Sierra no worky

[Hugi Thordarson]

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 the structure for an experimental change 
seemed scary at the time). That didn’t go well, so I backed up and moved to 
using Ivy with Ant for dependency management for a while. Phew. Talk about a 
couple of months of my life that I would like to get back.

But never looked back after going full Maven.

- hugi


> On 11 May 2017, at 20:56, Chuck Hill  wrote:
> 
> 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 2017-05-11, 1:01 PM, "Hugi Thordarson"  wrote:
> 
>> 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… I found that once I gave it a chance, it soon started to feel very 
> WO Way-ish.
> 
>> Yes, Chuck just said that.  No, I have not been drinking.
> 
>I find that extremely unlikely :-P.
> 
>- hugi
> 
> 
> 
>> Chuck
>> 
>> 
>> On 2017-05-11, 12:29 PM, "Webobjects-dev on behalf of Hugi Thordarson" 
>> > h...@karlmenn.is> wrote:
>> 
>>   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/e9a49e91fbcebe204e0feb4989f55631
>> 
>>   Note that before you can actually do this, though, you’ll have to copy the 
>> following file to ~/.m2/settings.xml. It informs maven about the WOCommunity 
>> maven repositories where the WO specific stuff lives.
>> 
>>   https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf
>> 
>>   After having done this with a few dozen projects, migrating a regular 
>> no-frills Fluffy Bunny project to maven takes me less than an hour these 
>> days (including upgrading the Jenkins build :). I sincerely recommend you 
>> give it a try. It’s a huge boon to productivity; dependency management alone 
>> will save you hours of headaches if you’re using any 3rd party software. And 
>> not having to manage framework installations is awesome.
>> 
>>   Also, I currently don't have a life so I’m usually online to help if you 
>> run into issues ;).
>> 
>>   Cheers,
>>   - hugi
>> 
>> 
>> 
>>> On 11 May 2017, at 18:59, Tim Worman  wrote:
>>> 
>>> 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
>>> UCLA GSE&IS
>>> 
 On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
 
 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 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 in Eclipse and from the terminal.
> 
> Calven
> 
>> 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 not in the original 
>> WOCookie class. Thus you probably have some sort of class ordering 
>> problem in your project. Check if ERXExtensions comes before 
>> JavaWebObjects.
>> 
>> jw
>> 
>> 
>>> Am 08.05.2017 um 14:15 schrieb Calven Eggert :
>>> 
>>> 
>>> 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 eclipse and I get this error (which I thought was going to 
>>> be cor

Re: Compiling ERExtensions in Sierra no worky

[Chuck Hill]

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 2017-05-11, 1:01 PM, "Hugi Thordarson"  wrote:

> 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… I found that once I gave it a chance, it soon started to feel very 
WO Way-ish.

> Yes, Chuck just said that.  No, I have not been drinking.

I find that extremely unlikely :-P.

- hugi



> Chuck
> 
> 
> On 2017-05-11, 12:29 PM, "Webobjects-dev on behalf of Hugi Thordarson" 
 wrote:
> 
>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/e9a49e91fbcebe204e0feb4989f55631
> 
>Note that before you can actually do this, though, you’ll have to copy 
the following file to ~/.m2/settings.xml. It informs maven about the 
WOCommunity maven repositories where the WO specific stuff lives.
> 
>https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf
> 
>After having done this with a few dozen projects, migrating a regular 
no-frills Fluffy Bunny project to maven takes me less than an hour these days 
(including upgrading the Jenkins build :). I sincerely recommend you give it a 
try. It’s a huge boon to productivity; dependency management alone will save 
you hours of headaches if you’re using any 3rd party software. And not having 
to manage framework installations is awesome.
> 
>Also, I currently don't have a life so I’m usually online to help if 
you run into issues ;).
> 
>Cheers,
>- hugi
> 
> 
> 
>> On 11 May 2017, at 18:59, Tim Worman  wrote:
>> 
>> 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
>> UCLA GSE&IS
>> 
>>> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
>>> 
>>> 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 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 in Eclipse and from the terminal.
 
 Calven
 
> 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 not in the 
original WOCookie class. Thus you probably have some sort of class ordering 
problem in your project. Check if ERXExtensions comes before JavaWebObjects.
> 
> jw
> 
> 
>> Am 08.05.2017 um 14:15 schrieb Calven Eggert :
>> 
>> 
>> 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 eclipse and I get this error (which I thought was going to be 
corrected once that compile was working but no):
>> 
>> java.lang.NoSuchMethodError: 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>> com.webobjects.foundation.NSForwardException 
[java.lang.NoSuchMethodError] 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V:java.lang.NoSuchMethodError:
 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>>  at 
com.webobjects.foundatio

Re: Compiling ERExtensions in Sierra no worky

[Hugi Thordarson]

> 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… I found that once I gave it a chance, it soon started to feel very WO 
Way-ish.

> Yes, Chuck just said that.  No, I have not been drinking.

I find that extremely unlikely :-P.

- hugi



> Chuck
> 
> 
> On 2017-05-11, 12:29 PM, "Webobjects-dev on behalf of Hugi Thordarson" 
>  h...@karlmenn.is> wrote:
> 
>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/e9a49e91fbcebe204e0feb4989f55631
> 
>Note that before you can actually do this, though, you’ll have to copy the 
> following file to ~/.m2/settings.xml. It informs maven about the WOCommunity 
> maven repositories where the WO specific stuff lives.
> 
>https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf
> 
>After having done this with a few dozen projects, migrating a regular 
> no-frills Fluffy Bunny project to maven takes me less than an hour these days 
> (including upgrading the Jenkins build :). I sincerely recommend you give it 
> a try. It’s a huge boon to productivity; dependency management alone will 
> save you hours of headaches if you’re using any 3rd party software. And not 
> having to manage framework installations is awesome.
> 
>Also, I currently don't have a life so I’m usually online to help if you 
> run into issues ;).
> 
>Cheers,
>- hugi
> 
> 
> 
>> On 11 May 2017, at 18:59, Tim Worman  wrote:
>> 
>> 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
>> UCLA GSE&IS
>> 
>>> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
>>> 
>>> 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 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 in Eclipse and from the terminal.
 
 Calven
 
> 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 not in the original 
> WOCookie class. Thus you probably have some sort of class ordering 
> problem in your project. Check if ERXExtensions comes before 
> JavaWebObjects.
> 
> jw
> 
> 
>> Am 08.05.2017 um 14:15 schrieb Calven Eggert :
>> 
>> 
>> 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 eclipse and I get this error (which I thought was going to 
>> be corrected once that compile was working but no):
>> 
>> java.lang.NoSuchMethodError: 
>> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>> com.webobjects.foundation.NSForwardException 
>> [java.lang.NoSuchMethodError] 
>> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V:java.lang.NoSuchMethodError:
>>  
>> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>>  at 
>> com.webobjects.foundation.NSForwardException._runtimeExceptionForThrowable(NSForwardException.java:39)
>>  at 
>> com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:124)
>>  at 
>> com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
>>  at 
>> com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
>>  at 
>> com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
>>  at 
>> com.webobjects.apps

Re: Compiling ERExtensions in Sierra no worky

[Chuck Hill]

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 Hugi Thordarson" 
 wrote:

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/e9a49e91fbcebe204e0feb4989f55631

Note that before you can actually do this, though, you’ll have to copy the 
following file to ~/.m2/settings.xml. It informs maven about the WOCommunity 
maven repositories where the WO specific stuff lives.

https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf

After having done this with a few dozen projects, migrating a regular 
no-frills Fluffy Bunny project to maven takes me less than an hour these days 
(including upgrading the Jenkins build :). I sincerely recommend you give it a 
try. It’s a huge boon to productivity; dependency management alone will save 
you hours of headaches if you’re using any 3rd party software. And not having 
to manage framework installations is awesome.

Also, I currently don't have a life so I’m usually online to help if you 
run into issues ;).

Cheers,
- hugi



> On 11 May 2017, at 18:59, Tim Worman  wrote:
> 
> 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
> UCLA GSE&IS
> 
>> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
>> 
>> 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 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 in Eclipse and from the terminal.
>>> 
>>> Calven
>>> 
 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 not in the 
original WOCookie class. Thus you probably have some sort of class ordering 
problem in your project. Check if ERXExtensions comes before JavaWebObjects.
 
 jw
 
 
> Am 08.05.2017 um 14:15 schrieb Calven Eggert :
> 
> 
> 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 eclipse and I get this error (which I thought was going to be 
corrected once that compile was working but no):
> 
> java.lang.NoSuchMethodError: 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
> com.webobjects.foundation.NSForwardException 
[java.lang.NoSuchMethodError] 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V:java.lang.NoSuchMethodError:
 
com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>   at 
com.webobjects.foundation.NSForwardException._runtimeExceptionForThrowable(NSForwardException.java:39)
>   at 
com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:124)
>   at 
com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
>   at 
com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
>   at 
com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
>   at 
com.webobjects.appserver._private.WOComponentRequestHandler._handleRequest(WOComponentRequestHandler.java:370)
>   at 
com.webobjects.appserver._private.WOComponentRequestHandler.handleRequest(WOComponentRequestHandler.java:445)
>   at 
com.webobjects.appserv

Re: Compiling ERExtensions in Sierra no worky

[Hugi Thordarson]

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/e9a49e91fbcebe204e0feb4989f55631

Note that before you can actually do this, though, you’ll have to copy the 
following file to ~/.m2/settings.xml. It informs maven about the WOCommunity 
maven repositories where the WO specific stuff lives.

https://gist.github.com/hugith/e2887fad3baecdd493e0b9f5311fe0bf

After having done this with a few dozen projects, migrating a regular no-frills 
Fluffy Bunny project to maven takes me less than an hour these days (including 
upgrading the Jenkins build :). I sincerely recommend you give it a try. It’s a 
huge boon to productivity; dependency management alone will save you hours of 
headaches if you’re using any 3rd party software. And not having to manage 
framework installations is awesome.

Also, I currently don't have a life so I’m usually online to help if you run 
into issues ;).

Cheers,
- hugi



> On 11 May 2017, at 18:59, Tim Worman  wrote:
> 
> 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
> UCLA GSE&IS
> 
>> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
>> 
>> 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 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 in Eclipse and from the terminal.
>>> 
>>> Calven
>>> 
 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 not in the original 
 WOCookie class. Thus you probably have some sort of class ordering problem 
 in your project. Check if ERXExtensions comes before JavaWebObjects.
 
 jw
 
 
> Am 08.05.2017 um 14:15 schrieb Calven Eggert :
> 
> 
> 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 eclipse and I get this error (which I thought was going to be 
> corrected once that compile was working but no):
> 
> java.lang.NoSuchMethodError: 
> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
> com.webobjects.foundation.NSForwardException 
> [java.lang.NoSuchMethodError] 
> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V:java.lang.NoSuchMethodError:
>  
> com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
>   at 
> com.webobjects.foundation.NSForwardException._runtimeExceptionForThrowable(NSForwardException.java:39)
>   at 
> com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:124)
>   at 
> com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
>   at 
> com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
>   at 
> com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
>   at 
> com.webobjects.appserver._private.WOComponentRequestHandler._handleRequest(WOComponentRequestHandler.java:370)
>   at 
> com.webobjects.appserver._private.WOComponentRequestHandler.handleRequest(WOComponentRequestHandler.java:445)
>   at 
> com.webobjects.appserver.WOApplication.dispatchRequest(WOApplication.java:1687)
>   at 
> er.extensions.appserver.ERXApplication.dispatchRequestImmediately(ERXApplication.java:2092)
>   at 
> er.extensions.appserver.ERXApplication.dispatchRequest(ERXApplication.java:2057)
>   at COREApplication.dispatchRequest(COREApplication.java:461)
>   at 
> com.webobjects.appserver._private.WOWorkerThread.runOnce(WOWorkerThread.java:144)
>   at 
> com.webobjects.appserver._private.WOWorkerThread.

Re: Compiling ERExtensions in Sierra no worky

[Tim Worman]

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
UCLA GSE&IS

> On May 9, 2017, at 9:38 AM, Hugi Thordarson  wrote:
> 
> 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 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 in Eclipse and from the terminal.
>> 
>> Calven
>> 
>>> 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 not in the original 
>>> WOCookie class. Thus you probably have some sort of class ordering problem 
>>> in your project. Check if ERXExtensions comes before JavaWebObjects.
>>> 
>>> jw
>>> 
>>> 
 Am 08.05.2017 um 14:15 schrieb Calven Eggert :
 
 
 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 eclipse and I get this error (which I thought was going to be 
 corrected once that compile was working but no):
 
 java.lang.NoSuchMethodError: 
 com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
 com.webobjects.foundation.NSForwardException [java.lang.NoSuchMethodError] 
 com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V:java.lang.NoSuchMethodError:
  
 com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
at 
 com.webobjects.foundation.NSForwardException._runtimeExceptionForThrowable(NSForwardException.java:39)
at 
 com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:124)
at 
 com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
at 
 com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
at 
 com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
at 
 com.webobjects.appserver._private.WOComponentRequestHandler._handleRequest(WOComponentRequestHandler.java:370)
at 
 com.webobjects.appserver._private.WOComponentRequestHandler.handleRequest(WOComponentRequestHandler.java:445)
at 
 com.webobjects.appserver.WOApplication.dispatchRequest(WOApplication.java:1687)
at 
 er.extensions.appserver.ERXApplication.dispatchRequestImmediately(ERXApplication.java:2092)
at 
 er.extensions.appserver.ERXApplication.dispatchRequest(ERXApplication.java:2057)
at COREApplication.dispatchRequest(COREApplication.java:461)
at 
 com.webobjects.appserver._private.WOWorkerThread.runOnce(WOWorkerThread.java:144)
at 
 com.webobjects.appserver._private.WOWorkerThread.run(WOWorkerThread.java:226)
at java.lang.Thread.run(Thread.java:748)
 Caused by: java.lang.NoSuchMethodError: 
 com.webobjects.appserver.WOCookie.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;IZZ)V
at 
 er.extensions.appserver.ERXApplication.addBalancerRouteCookie(ERXApplication.java:2853)
at 
 er.extensions.appserver.ERXApplication.addBalancerRouteCookieByNotification(ERXApplication.java:2836)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
 com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:122)
... 12 more
 
 
 It works if I run the app from the terminal.  What am I missing here?
 
 
 
> On May 8, 2017, at 7:52 AM, Theodore Petrosky  wrote:
> 
> 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 w