Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Paul Hoadley]

On 23 Feb 2019, at 8:46 pm, Maik Musall  wrote:

> I still think we should put stuff there, lacking an alternative. But we 
> should also work towards cleaning it up. Obsolete information should be 
> simply removed, and pages need to be restructured.

Completely agree. I think historically there has been a tendency to preserve 
out of date information "just in case", or out of a reluctance to stomp on 
someone else's work. It should be pruned hard where it's wrong or stale.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Maik Musall]

I still think we should put stuff there, lacking an alternative. But we should 
also work towards cleaning it up. Obsolete information should be simply 
removed, and pages need to be restructured.


> Am 23.02.2019 um 00:37 schrieb Hugi Thordarson :
> 
> I do, but I'm not quite sure the Wiki is where I'd like to post stuff. It's a 
> very confusing place.
> 
> 
>> On 22 Feb 2019, at 16:57, Ted Petrosky > <mailto:tpetro...@agencysacks.com>> wrote:
>> 
>> And do you get an ‘edit’ button on the wiki page when you log in?
>> 
>> 
>> 
>> Theodore Petrosky | IT/Finance Director
>> AgencySacks
>>  
>> 345 Seventh Avenue, New York, NY 10001
>> p. 212. 225. 9323  |  agencysacks.com <http://agencysacks.com/> 
>> 
>> 
>> From: Webobjects-dev 
>> > <mailto:webobjects-dev-bounces+tpetrosky=agencysacks@lists.apple.com>> 
>> on behalf of Hugi Thordarson mailto:h...@karlmenn.is>>
>> Date: Thursday, February 21, 2019 at 5:34 PM
>> To: Maik Musall mailto:m...@selbstdenker.ag>>
>> Cc: "Ted Petrosky (WO)" > <mailto:webobjects-dev@lists.apple.com>>
>> Subject: Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap
>> 
>> My comment was directed at you Ant guys with your property files—didn't 
>> really intend for it to backfire onto myself :p.
>> 
>> But I know there's a severe lack of documentation for using Maven with WO, 
>> and I know I should have contributed a while ago. Incidentally I now finally 
>> have time to write some docs, so it's time to own up.
>> 
>> - hugi
>> 
>> 
>>> On 21 Feb 2019, at 21:33, Maik Musall >> <mailto:m...@selbstdenker.ag>> wrote:
>>> 
>>> Hi Hugi,
>>> 
>>> glad you're volunteering to add that variant to the wiki page :)
>>> 
>>> Maik
>>> 
>>> 
>>>> Am 21.02.2019 um 18:13 schrieb Hugi Thordarson >>> <mailto:h...@karlmenn.is>>:
>>>> 
>>>> Ya'll need Maven.
>>>> 
>>>> - hugi
>>>> 
>>>> 
>>>>> On 21 Feb 2019, at 17:09, Tim Worman >>>> <mailto:li...@thetimmy.com>> wrote:
>>>>> 
>>>>> I would think, at this point, that the number of devs swapping between 
>>>>> multiple versions of WO would be close to zero. Anyone supporting a 
>>>>> legacy codebase will probably know what to do. Perhaps there could simply 
>>>>> be a link to a separate article - “How to maintain multiple versions of 
>>>>> WO."
>>>>> 
>>>>> Tim
>>>>> 
>>>>>> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky >>>>> <mailto:tedp...@yahoo.com>> wrote:
>>>>>> 
>>>>>> The problem is that (If I remember correctly) when you invoke ant on the 
>>>>>> CLI, ant uses wolips.properties. it will ignore anything else.
>>>>>> 
>>>>>> so if you have a wolips.543.properties and Eclipse is set up to use it, 
>>>>>> then Eclipse is Okay, but the CLI will not use it.
>>>>>> 
>>>>>> So I think it is better to NOT use the wolips.543.properties so that 
>>>>>> installing and or compiling from Eclipse will agree with using the CLI.
>>>>>> 
>>>>>> One can do whatever pleases themselves, but I think erring on the side 
>>>>>> of consistency is more correct (betterer???)! And it is not really 
>>>>>> erring, it is making an informed decision.
>>>>>> 
>>>>>> Can you override ant’s properties?
>>>>>> 
>>>>>> ant -Dproperties=wolips.543.properties
>>>>>> 
>>>>>> So I agree with Markus, we should tone down the usage of .543. (multiple 
>>>>>> versions) or at the least call it not recommended and the above is why.
>>>>>> 
>>>>>> 
>>>>>>> On Feb 21, 2019, at 9:39 AM, Maik Musall >>>>>> <mailto:m...@selbstdenker.ag>> wrote:
>>>>>>> 
>>>>>>> Hi Ted,
>>>>>>> 
>>>>>>> I went through the install process on a clean machine, created new 
>>>>>>> screenshots and updated the Project Wonder Installation page with that. 
>>>>>>> But I kept the wolips.543.properties scheme that ha

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Paul Hoadley]

On 22 Feb 2019, at 7:46 pm, getsh...@gmail.com wrote:

> I’m very interested in, what to me are, the dark Maven arts.
> 
> It’s such a deviation from how it all works for me now with ant and Fluffy 
> Bunny - from dev env all the way through CI and deployment artifacts. eg how 
> do I go about having my Wonder framework dependencies as open projects in my 
> workspace so the source code is as available as my application’s source?

In almost the same way as you do now, but with a caveat. Maven, as you might 
expect, is very particular about versioning. So if you have a Wonder framework 
as a project in your workspace, its version will need to match the version your 
app is dependent on. For example, if your app is dependent on 7.0, but you've 
got Wonder's HEAD checked out, then the framework is going to claim to be 
7.1-SNAPSHOT, which isn't a match, so you won't get handy features like 
command-clicking through to Wonder source, because it will be using the 7.0 JAR 
in your Maven repository. One solution would be to check out the "wonder-7.0" 
tag which should have the version you need in this example.

> Can my private repository just be a path on my jenkins http server? (there’s 
> probably an app/plugin for that).

I don't know the answer to that specific question. But you can pretty easily 
set up something like JFrog Artifactory. Jenkins would then use your 
Artifactory instance to get artifacts it needs during build (and Artifactory 
would ask the WOCommunity repository for the non-public artifacts it needs), 
and then push your built app bundle back up to Artifactory when it's done. It 
turns out to be nice to be able to treat Jenkins just as a build server, and 
offload your artifact management to a specialised repository.

> I should go away and work through some Maven primers and come back with 
> specific questions in their own thread, but +1 from me with gratitude for 
> more insight from Hugi, Paul and the rest of the WO Maven brains trust.

Start here:

https://wiki.wocommunity.org/display/WOL/Quick+Start 


I would recommend the following variations to those steps:

0. —
1. Definitely just download from Apache and install manually, then get 'mvn' on 
your path.
2. The advice there seems reasonable. It will get you started, and later you'll 
point Maven to your own Artifactory repo instead.
3. Skip this step: it's not required.
4. You can do this via the command line, or by selecting the erxapplication 
with the Eclipse wizard.
5. Obviously skip this if you've created your new project in Eclipse.
6. This is how it's done, though later you'll get Jenkins to do it for you.

Give it a try. Let us know how you go.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Hugi Thordarson]

I do, but I'm not quite sure the Wiki is where I'd like to post stuff. It's a 
very confusing place.


> On 22 Feb 2019, at 16:57, Ted Petrosky  wrote:
> 
> And do you get an ‘edit’ button on the wiki page when you log in?
> 
> 
> 
> Theodore Petrosky | IT/Finance Director
> AgencySacks
>  
> 345 Seventh Avenue, New York, NY 10001
> p. 212. 225. 9323  |  agencysacks.com 
> 
> 
> From: Webobjects-dev 
>  <mailto:webobjects-dev-bounces+tpetrosky=agencysacks@lists.apple.com>> on 
> behalf of Hugi Thordarson mailto:h...@karlmenn.is>>
> Date: Thursday, February 21, 2019 at 5:34 PM
> To: Maik Musall mailto:m...@selbstdenker.ag>>
> Cc: "Ted Petrosky (WO)"  <mailto:webobjects-dev@lists.apple.com>>
> Subject: Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap
> 
> My comment was directed at you Ant guys with your property files—didn't 
> really intend for it to backfire onto myself :p.
> 
> But I know there's a severe lack of documentation for using Maven with WO, 
> and I know I should have contributed a while ago. Incidentally I now finally 
> have time to write some docs, so it's time to own up.
> 
> - hugi
> 
> 
>> On 21 Feb 2019, at 21:33, Maik Musall > <mailto:m...@selbstdenker.ag>> wrote:
>> 
>> Hi Hugi,
>> 
>> glad you're volunteering to add that variant to the wiki page :)
>> 
>> Maik
>> 
>> 
>>> Am 21.02.2019 um 18:13 schrieb Hugi Thordarson >> <mailto:h...@karlmenn.is>>:
>>> 
>>> Ya'll need Maven.
>>> 
>>> - hugi
>>> 
>>> 
>>>> On 21 Feb 2019, at 17:09, Tim Worman >>> <mailto:li...@thetimmy.com>> wrote:
>>>> 
>>>> I would think, at this point, that the number of devs swapping between 
>>>> multiple versions of WO would be close to zero. Anyone supporting a legacy 
>>>> codebase will probably know what to do. Perhaps there could simply be a 
>>>> link to a separate article - “How to maintain multiple versions of WO."
>>>> 
>>>> Tim
>>>> 
>>>>> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky >>>> <mailto:tedp...@yahoo.com>> wrote:
>>>>> 
>>>>> The problem is that (If I remember correctly) when you invoke ant on the 
>>>>> CLI, ant uses wolips.properties. it will ignore anything else.
>>>>> 
>>>>> so if you have a wolips.543.properties and Eclipse is set up to use it, 
>>>>> then Eclipse is Okay, but the CLI will not use it.
>>>>> 
>>>>> So I think it is better to NOT use the wolips.543.properties so that 
>>>>> installing and or compiling from Eclipse will agree with using the CLI.
>>>>> 
>>>>> One can do whatever pleases themselves, but I think erring on the side of 
>>>>> consistency is more correct (betterer???)! And it is not really erring, 
>>>>> it is making an informed decision.
>>>>> 
>>>>> Can you override ant’s properties?
>>>>> 
>>>>> ant -Dproperties=wolips.543.properties
>>>>> 
>>>>> So I agree with Markus, we should tone down the usage of .543. (multiple 
>>>>> versions) or at the least call it not recommended and the above is why.
>>>>> 
>>>>> 
>>>>>> On Feb 21, 2019, at 9:39 AM, Maik Musall >>>>> <mailto:m...@selbstdenker.ag>> wrote:
>>>>>> 
>>>>>> Hi Ted,
>>>>>> 
>>>>>> I went through the install process on a clean machine, created new 
>>>>>> screenshots and updated the Project Wonder Installation page with that. 
>>>>>> But I kept the wolips.543.properties scheme that had been described 
>>>>>> there, even though the comments at the bottom recommend not doing that 
>>>>>> and ignore the versioning. I also have the impression that skipping the 
>>>>>> version distinction would be better.
>>>>>> 
>>>>>> I can update that again, but I'd like a discussion about that detail 
>>>>>> here before.
>>>>>> 
>>>>>> Maik
>>>>>> 
>>>>>> 
>>>>>>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky >>>>>> <mailto:tedp...@yahoo.com>>:
>>>>>>> 
>>>>>>> So I can edit some pages b

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Ted Petrosky]

And do you get an ‘edit’ button on the wiki page when you log in?



Theodore Petrosky | IT/Finance Director
AgencySacks

345 Seventh Avenue, New York, NY 10001
p. 212. 225. 9323  |  agencysacks.com


From: Webobjects-dev 
mailto:webobjects-dev-bounces+tpetrosky=agencysacks@lists.apple.com>>
 on behalf of Hugi Thordarson mailto:h...@karlmenn.is>>
Date: Thursday, February 21, 2019 at 5:34 PM
To: Maik Musall mailto:m...@selbstdenker.ag>>
Cc: "Ted Petrosky (WO)" 
mailto:webobjects-dev@lists.apple.com>>
Subject: Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

My comment was directed at you Ant guys with your property files—didn't really 
intend for it to backfire onto myself :p.

But I know there's a severe lack of documentation for using Maven with WO, and 
I know I should have contributed a while ago. Incidentally I now finally have 
time to write some docs, so it's time to own up.

- hugi


On 21 Feb 2019, at 21:33, Maik Musall 
mailto:m...@selbstdenker.ag>> wrote:

Hi Hugi,

glad you're volunteering to add that variant to the wiki page :)

Maik


Am 21.02.2019 um 18:13 schrieb Hugi Thordarson 
mailto:h...@karlmenn.is>>:

Ya'll need Maven.

- hugi


On 21 Feb 2019, at 17:09, Tim Worman 
mailto:li...@thetimmy.com>> wrote:

I would think, at this point, that the number of devs swapping between multiple 
versions of WO would be close to zero. Anyone supporting a legacy codebase will 
probably know what to do. Perhaps there could simply be a link to a separate 
article - “How to maintain multiple versions of WO."

Tim

On Feb 21, 2019, at 8:10 AM, Theodore Petrosky 
mailto:tedp...@yahoo.com>> wrote:

The problem is that (If I remember correctly) when you invoke ant on the CLI, 
ant uses wolips.properties. it will ignore anything else.

so if you have a wolips.543.properties and Eclipse is set up to use it, then 
Eclipse is Okay, but the CLI will not use it.

So I think it is better to NOT use the wolips.543.properties so that installing 
and or compiling from Eclipse will agree with using the CLI.

One can do whatever pleases themselves, but I think erring on the side of 
consistency is more correct (betterer???)! And it is not really erring, it is 
making an informed decision.

Can you override ant’s properties?

ant -Dproperties=wolips.543.properties

So I agree with Markus, we should tone down the usage of .543. (multiple 
versions) or at the least call it not recommended and the above is why.


On Feb 21, 2019, at 9:39 AM, Maik Musall 
mailto:m...@selbstdenker.ag>> wrote:

Hi Ted,

I went through the install process on a clean machine, created new screenshots 
and updated the Project Wonder Installation page with that. But I kept the 
wolips.543.properties scheme that had been described there, even though the 
comments at the bottom recommend not doing that and ignore the versioning. I 
also have the impression that skipping the version distinction would be better.

I can update that again, but I'd like a discussion about that detail here 
before.

Maik


Am 21.02.2019 um 05:06 schrieb Theodore Petrosky 
mailto:tedp...@yahoo.com>>:

So I can edit some pages but not all  :(


I can edit in here for instance:
https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project

but I cannot edit here:
https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation

I have always been very confused in the wiki. I know that Maik Musall can edit 
here because it says at the top of the page:
last modified by Maik Musall<https://wiki.wocommunity.org/display/~mmusall> on 
Dec 01, 
2017<https://wiki.wocommunity.org/pages/diffpagesbyversion.action?pageId=1835055&selectedPageVersions=60&selectedPageVersions=61>

I would be happy to help here if we can figure out how to get me edit privs.

Ted



On Feb 20, 2019, at 10:47 PM, Michael Sharp 
mailto:getsh...@gmail.com>> wrote:

A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
reference the appropriate version of Eclipse and WOLips update site URL.

- Sharpy.

On 20 Feb 2019, at 7:03 pm, Theodore Petrosky 
mailto:tedp...@yahoo.com>> wrote:

???

should the wiki be updated to reflect this URL?

I hate the idea of having to examine the mail archives to find  this.

Ted

On Feb 18, 2019, at 7:38 PM, Henrique Prange 
mailto:hpra...@gmail.com>> wrote:

Hey guys,

Just to let you know that I've merged Michael's pull request into the 
eclipse_4_10 branch. Maik did set up a new Jenkins job to build from changes on 
that branch. You can test it by pointing your WOLips update site to:

https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/

It looks good on my machine.

Cheers,

HP

On Feb 17, 2019, at 7:52 PM, Michael Sharp 
mailto:getsh...@gmail.com>> wrote:

Hi Henrique,

Thank you, PR here https://github.com/wocommunity/wolips/pull/

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Maik Musall]

Hi all,

I just edited the page to get rid of the 543 parts. Would be nice if someone 
could repeat the steps in an independent clean install and check if everything 
is correct.

Regarding the maven approach, we definitely need a wiki page about that. It's 
nice that you don't even need to install WebObjects as long as you don't want 
to actually deploy locally. At our company we're working on moving projects to 
maven, have an internal repo for our custom stuff, and I'm looking forward for 
new developers not having to go through all this.

Maik


> Am 21.02.2019 um 23:24 schrieb Theodore Petrosky :
> 
> of course this should work. to specify the property file on the command line:
> 
> cd into the project folder and issue
> 
> ant -propertyfile ~/Library/Application\ Support/WOLips/wolips.543.properties 
> install
> 
> or
> 
> ant -propertyfile wolips.543.properties install
> 
> ant will find the properties!!!
> 
> 
> 
>> On Feb 21, 2019, at 10:59 AM, Markus Ruggiero > > wrote:
>> 
>> 
>> 
>>> On 21 Feb 2019, at 15:39, Maik Musall >> > wrote:
>>> 
>>> Hi Ted,
>>> 
>>> I went through the install process on a clean machine, created new 
>>> screenshots and updated the Project Wonder Installation page with that. But 
>>> I kept the wolips.543.properties scheme that had been described there, even 
>>> though the comments at the bottom recommend not doing that and ignore the 
>>> versioning. I also have the impression that skipping the version 
>>> distinction would be better.
>>> 
>>> I can update that again, but I'd like a discussion about that detail here 
>>> before.
>>> 
>> 
>> I would remove all that versioning stuff. We oldies already know what we do 
>> and are properly set up, all others should use "the latest and greatest" 
>> WebObjects 5.4.3 anyway. I have also streamlined the whole installation and 
>> directoy setup in an add-on doc to my book Learning The Wonders. Maybe add a 
>> pointer to https://learningthewonders.com  
>> at the top of that page? All the relevant chapters are freely downloadable.
>> 
>> ---markus---
>> 
>>> Maik
>>> 
>>> 
 Am 21.02.2019 um 05:06 schrieb Theodore Petrosky >>> >:
 
 So I can edit some pages but not all  :(
 
 
 I can edit in here for instance:
 https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
  
 
 
 but I cannot edit here:
 https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
 
 
 I have always been very confused in the wiki. I know that Maik Musall can 
 edit here because it says at the top of the page:
 last modified by Maik Musall 
  on Dec 01, 2017 
 
 
 I would be happy to help here if we can figure out how to get me edit 
 privs.
 
 Ted
 
 
 
> On Feb 20, 2019, at 10:47 PM, Michael Sharp  > wrote:
> 
> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
> reference the appropriate version of Eclipse and WOLips update site URL.
> 
> - Sharpy.
> 
>> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky > > wrote:
>> 
>> ???
>> 
>> should the wiki be updated to reflect this URL?
>> 
>> I hate the idea of having to examine the mail archives to find  this.
>> 
>> Ted
>> 
>>> On Feb 18, 2019, at 7:38 PM, Henrique Prange >> > wrote:
>>> 
>>> Hey guys,
>>> 
>>> Just to let you know that I've merged Michael's pull request into the 
>>> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
>>> changes on that branch. You can test it by pointing your WOLips update 
>>> site to:
>>> 
>>> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>>>  
>>> 
>>> 
>>> It looks good on my machine.
>>> 
>>> Cheers,
>>> 
>>> HP
>>> 
 On Feb 17, 2019, at 7:52 PM, Michael Sharp >>> > wrote:
 
 Hi Henrique,
 
 Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
 
 
 Cheers,
 
 - Sharpy.
 
 
> On 18 Feb 2019, at 3:11 am, Henrique Prange  > wrote:
> 
> Hi Michael,
>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[getsh...@gmail.com]

I’m very interested in, what to me are, the dark Maven arts.

It’s such a deviation from how it all works for me now with ant and Fluffy 
Bunny - from dev env all the way through CI and deployment artifacts. eg how do 
I go about having my Wonder framework dependencies as open projects in my 
workspace so the source code is as available as my application’s source? Can my 
private repository just be a path on my jenkins http server? (there’s probably 
an app/plugin for that).

I should go away and work through some Maven primers and come back with 
specific questions in their own thread, but +1 from me with gratitude for more 
insight from Hugi, Paul and the rest of the WO Maven brains trust.

- Sharpy.

> On 22 Feb 2019, at 8:54 am, Hugi Thordarson  wrote:
> 
> For a little addition to this discussion, just if you find it interesting: 
> Today I set up a new developer environment on a new machine by:
> 
> 1) Installing Eclipse
> 2) Installing WOLips (4_10, thanks guys!)
> 3) Cloning a git repository containing a maven WebObjects project
> 4) Running the WebObjects project
> 
> Said project can also be built for deployment by just running "mvn package" 
> on it. No WebObjects installation. No property files. None of the mess or 
> wizardry that's usually involved in getting WO running on dev or build. 
> That's worth something.
> 
> To be fair, the project's pom referenced the WOCommunity repository. Usually 
> you'll have to add that to your own maven settings (since WO and WOnder are 
> not in Maven central) but that's one, one-time step.
> 
> It's just so… Lovely.
> 
> - hugi
> 
> 
> 
>> On 21 Feb 2019, at 22:38, Hugi Thordarson > > wrote:
>> 
>> Unfortunately, not really. There's that guide for converting an existing 
>> Fluffy Bunny project…
>> 
>> https://gist.github.com/hugith/e9a49e91fbcebe204e0feb4989f55631 
>> 
>> 
>> …and after that everything should just work®. But of course there are always 
>> caveats. And we're really missing basic documentation on project structure 
>> and other stuff for people new to Maven.
>> 
>> But if you give it a try, I (and others) are very happy to help along the 
>> way, both here on the list and on Slack. I don't know anyone that switched 
>> to Maven and regretted it.
>> 
>> - hugi
>> 
>> 
>> 
>>> On 21 Feb 2019, at 19:02, Fredrik Lindgren >> > wrote:
>>> 
>>> So, is there a good description/guide somewhere for how to use Maven with 
>>> WebObjects and Wonder?
>>> 
>>> Hälsningar
>>> Fredrik Lindgren
>>> 
>>> 21 feb. 2019 kl. 18:13 skrev Hugi Thordarson >> >:
>>> 
 Ya'll need Maven.
 
 - hugi
 
 
> On 21 Feb 2019, at 17:09, Tim Worman  > wrote:
> 
> I would think, at this point, that the number of devs swapping between 
> multiple versions of WO would be close to zero. Anyone supporting a 
> legacy codebase will probably know what to do. Perhaps there could simply 
> be a link to a separate article - “How to maintain multiple versions of 
> WO."
> 
> Tim
> 
>> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky > > wrote:
>> 
>> The problem is that (If I remember correctly) when you invoke ant on the 
>> CLI, ant uses wolips.properties. it will ignore anything else.
>> 
>> so if you have a wolips.543.properties and Eclipse is set up to use it, 
>> then Eclipse is Okay, but the CLI will not use it.
>> 
>> So I think it is better to NOT use the wolips.543.properties so that 
>> installing and or compiling from Eclipse will agree with using the CLI.
>> 
>> One can do whatever pleases themselves, but I think erring on the side 
>> of consistency is more correct (betterer???)! And it is not really 
>> erring, it is making an informed decision.
>> 
>> Can you override ant’s properties?
>> 
>> ant -Dproperties=wolips.543.properties
>> 
>> So I agree with Markus, we should tone down the usage of .543. (multiple 
>> versions) or at the least call it not recommended and the above is why.
>> 
>> 
>>> On Feb 21, 2019, at 9:39 AM, Maik Musall >> > wrote:
>>> 
>>> Hi Ted,
>>> 
>>> I went through the install process on a clean machine, created new 
>>> screenshots and updated the Project Wonder Installation page with that. 
>>> But I kept the wolips.543.properties scheme that had been described 
>>> there, even though the comments at the bottom recommend not doing that 
>>> and ignore the versioning. I also have the impression that skipping the 
>>> version distinction would be better.
>>> 
>>> I can update that again, but I'd like a discussion about that detail 
>>> here before.
>>> 
>>> Maik
>>> 
>>> 
 Am 21.02.2019 um 05:

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Paul Hoadley]

On 22 Feb 2019, at 09:24, Hugi Thordarson  wrote:

> For a little addition to this discussion, just if you find it interesting: 
> Today I set up a new developer environment on a new machine by:
> 
> 1) Installing Eclipse
> 2) Installing WOLips (4_10, thanks guys!)
> 3) Cloning a git repository containing a maven WebObjects project
> 4) Running the WebObjects project

Oh yeah, I forgot to add that to my benefits list:

* Setting up a new developer takes just a few minutes—great for, say, someone 
who's maybe just doing front-end work, and really only needs to be able to run 
an app and make some changes to that project.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Hugi Thordarson]

For a little addition to this discussion, just if you find it interesting: 
Today I set up a new developer environment on a new machine by:

1) Installing Eclipse
2) Installing WOLips (4_10, thanks guys!)
3) Cloning a git repository containing a maven WebObjects project
4) Running the WebObjects project

Said project can also be built for deployment by just running "mvn package" on 
it. No WebObjects installation. No property files. None of the mess or wizardry 
that's usually involved in getting WO running on dev or build. That's worth 
something.

To be fair, the project's pom referenced the WOCommunity repository. Usually 
you'll have to add that to your own maven settings (since WO and WOnder are not 
in Maven central) but that's one, one-time step.

It's just so… Lovely.

- hugi



> On 21 Feb 2019, at 22:38, Hugi Thordarson  wrote:
> 
> Unfortunately, not really. There's that guide for converting an existing 
> Fluffy Bunny project…
> 
> https://gist.github.com/hugith/e9a49e91fbcebe204e0feb4989f55631 
> 
> 
> …and after that everything should just work®. But of course there are always 
> caveats. And we're really missing basic documentation on project structure 
> and other stuff for people new to Maven.
> 
> But if you give it a try, I (and others) are very happy to help along the 
> way, both here on the list and on Slack. I don't know anyone that switched to 
> Maven and regretted it.
> 
> - hugi
> 
> 
> 
>> On 21 Feb 2019, at 19:02, Fredrik Lindgren > > wrote:
>> 
>> So, is there a good description/guide somewhere for how to use Maven with 
>> WebObjects and Wonder?
>> 
>> Hälsningar
>> Fredrik Lindgren
>> 
>> 21 feb. 2019 kl. 18:13 skrev Hugi Thordarson > >:
>> 
>>> Ya'll need Maven.
>>> 
>>> - hugi
>>> 
>>> 
 On 21 Feb 2019, at 17:09, Tim Worman >>> > wrote:
 
 I would think, at this point, that the number of devs swapping between 
 multiple versions of WO would be close to zero. Anyone supporting a legacy 
 codebase will probably know what to do. Perhaps there could simply be a 
 link to a separate article - “How to maintain multiple versions of WO."
 
 Tim
 
> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky  > wrote:
> 
> The problem is that (If I remember correctly) when you invoke ant on the 
> CLI, ant uses wolips.properties. it will ignore anything else.
> 
> so if you have a wolips.543.properties and Eclipse is set up to use it, 
> then Eclipse is Okay, but the CLI will not use it.
> 
> So I think it is better to NOT use the wolips.543.properties so that 
> installing and or compiling from Eclipse will agree with using the CLI.
> 
> One can do whatever pleases themselves, but I think erring on the side of 
> consistency is more correct (betterer???)! And it is not really erring, 
> it is making an informed decision.
> 
> Can you override ant’s properties?
> 
> ant -Dproperties=wolips.543.properties
> 
> So I agree with Markus, we should tone down the usage of .543. (multiple 
> versions) or at the least call it not recommended and the above is why.
> 
> 
>> On Feb 21, 2019, at 9:39 AM, Maik Musall > > wrote:
>> 
>> Hi Ted,
>> 
>> I went through the install process on a clean machine, created new 
>> screenshots and updated the Project Wonder Installation page with that. 
>> But I kept the wolips.543.properties scheme that had been described 
>> there, even though the comments at the bottom recommend not doing that 
>> and ignore the versioning. I also have the impression that skipping the 
>> version distinction would be better.
>> 
>> I can update that again, but I'd like a discussion about that detail 
>> here before.
>> 
>> Maik
>> 
>> 
>>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky >> >:
>>> 
>>> So I can edit some pages but not all  :(
>>> 
>>> 
>>> I can edit in here for instance:
>>> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>>>  
>>> 
>>> 
>>> but I cannot edit here:
>>> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
>>> 
>>> 
>>> I have always been very confused in the wiki. I know that Maik Musall 
>>> can edit here because it says at the top of the page:
>>> last modified by Maik Musall 
>>>  on Dec 01, 2017 
>>> 

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Paul Hoadley]

On 22 Feb 2019, at 09:08, Hugi Thordarson  wrote:

> Unfortunately, not really. There's that guide for converting an existing 
> Fluffy Bunny project…
> 
> https://gist.github.com/hugith/e9a49e91fbcebe204e0feb4989f55631 
> 
> 
> …and after that everything should just work®. But of course there are always 
> caveats. And we're really missing basic documentation on project structure 
> and other stuff for people new to Maven.

I haven't looked at it in a while, but what I found was that the wiki 
documentation was at least a little bit incomplete and out of date. Starting a 
new Maven project is very easy. Converting from Fluffy Bunny is only marginally 
trickier, but it's usually pretty obvious when you got something wrong, and you 
can always start again. I've used Hugi's Gist instructions above many times. 
Here is my marginally different version:

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


> But if you give it a try, I (and others) are very happy to help along the 
> way, both here on the list and on Slack. I don't know anyone that switched to 
> Maven and regretted it.

The cost is the learning curve, but there are so many benefits. Just off the 
top of my head:

* Proper dependency management rather than trusting the JAR-soup in the 
frameworks.
* Enforced semantic versioning on your projects.
* Massively simplified CI: throw away all those Jenkins environment setup 
scripts and just use a Maven project.
* Civilised artifact management with something like Artifactory.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Hugi Thordarson]

Unfortunately, not really. There's that guide for converting an existing Fluffy 
Bunny project…

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


…and after that everything should just work®. But of course there are always 
caveats. And we're really missing basic documentation on project structure and 
other stuff for people new to Maven.

But if you give it a try, I (and others) are very happy to help along the way, 
both here on the list and on Slack. I don't know anyone that switched to Maven 
and regretted it.

- hugi



> On 21 Feb 2019, at 19:02, Fredrik Lindgren  wrote:
> 
> So, is there a good description/guide somewhere for how to use Maven with 
> WebObjects and Wonder?
> 
> Hälsningar
> Fredrik Lindgren
> 
> 21 feb. 2019 kl. 18:13 skrev Hugi Thordarson  >:
> 
>> Ya'll need Maven.
>> 
>> - hugi
>> 
>> 
>>> On 21 Feb 2019, at 17:09, Tim Worman >> > wrote:
>>> 
>>> I would think, at this point, that the number of devs swapping between 
>>> multiple versions of WO would be close to zero. Anyone supporting a legacy 
>>> codebase will probably know what to do. Perhaps there could simply be a 
>>> link to a separate article - “How to maintain multiple versions of WO."
>>> 
>>> Tim
>>> 
 On Feb 21, 2019, at 8:10 AM, Theodore Petrosky >>> > wrote:
 
 The problem is that (If I remember correctly) when you invoke ant on the 
 CLI, ant uses wolips.properties. it will ignore anything else.
 
 so if you have a wolips.543.properties and Eclipse is set up to use it, 
 then Eclipse is Okay, but the CLI will not use it.
 
 So I think it is better to NOT use the wolips.543.properties so that 
 installing and or compiling from Eclipse will agree with using the CLI.
 
 One can do whatever pleases themselves, but I think erring on the side of 
 consistency is more correct (betterer???)! And it is not really erring, it 
 is making an informed decision.
 
 Can you override ant’s properties?
 
 ant -Dproperties=wolips.543.properties
 
 So I agree with Markus, we should tone down the usage of .543. (multiple 
 versions) or at the least call it not recommended and the above is why.
 
 
> On Feb 21, 2019, at 9:39 AM, Maik Musall  > wrote:
> 
> Hi Ted,
> 
> I went through the install process on a clean machine, created new 
> screenshots and updated the Project Wonder Installation page with that. 
> But I kept the wolips.543.properties scheme that had been described 
> there, even though the comments at the bottom recommend not doing that 
> and ignore the versioning. I also have the impression that skipping the 
> version distinction would be better.
> 
> I can update that again, but I'd like a discussion about that detail here 
> before.
> 
> Maik
> 
> 
>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky > >:
>> 
>> So I can edit some pages but not all  :(
>> 
>> 
>> I can edit in here for instance:
>> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>>  
>> 
>> 
>> but I cannot edit here:
>> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
>> 
>> 
>> I have always been very confused in the wiki. I know that Maik Musall 
>> can edit here because it says at the top of the page:
>> last modified by Maik Musall 
>>  on Dec 01, 2017 
>> 
>> 
>> I would be happy to help here if we can figure out how to get me edit 
>> privs.
>> 
>> Ted
>> 
>> 
>> 
>>> On Feb 20, 2019, at 10:47 PM, Michael Sharp >> > wrote:
>>> 
>>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>>> reference the appropriate version of Eclipse and WOLips update site URL.
>>> 
>>> - Sharpy.
>>> 
 On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >>> > wrote:
 
 ???
 
 should the wiki be updated to reflect this URL?
 
 I hate the idea of having to examine the mail archives to find  this.
 
 Ted
 
> On Feb 18, 2019, at 7:38 PM, Henrique Prange  > wrote:
> 
> Hey guys,
> 
> Just to let you know that I've merged Michael's pull request into the 
>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Hugi Thordarson]

My comment was directed at you Ant guys with your property files—didn't really 
intend for it to backfire onto myself :p.

But I know there's a severe lack of documentation for using Maven with WO, and 
I know I should have contributed a while ago. Incidentally I now finally have 
time to write some docs, so it's time to own up.

- hugi


> On 21 Feb 2019, at 21:33, Maik Musall  wrote:
> 
> Hi Hugi,
> 
> glad you're volunteering to add that variant to the wiki page :)
> 
> Maik
> 
> 
>> Am 21.02.2019 um 18:13 schrieb Hugi Thordarson > >:
>> 
>> Ya'll need Maven.
>> 
>> - hugi
>> 
>> 
>>> On 21 Feb 2019, at 17:09, Tim Worman >> > wrote:
>>> 
>>> I would think, at this point, that the number of devs swapping between 
>>> multiple versions of WO would be close to zero. Anyone supporting a legacy 
>>> codebase will probably know what to do. Perhaps there could simply be a 
>>> link to a separate article - “How to maintain multiple versions of WO."
>>> 
>>> Tim
>>> 
 On Feb 21, 2019, at 8:10 AM, Theodore Petrosky >>> > wrote:
 
 The problem is that (If I remember correctly) when you invoke ant on the 
 CLI, ant uses wolips.properties. it will ignore anything else.
 
 so if you have a wolips.543.properties and Eclipse is set up to use it, 
 then Eclipse is Okay, but the CLI will not use it.
 
 So I think it is better to NOT use the wolips.543.properties so that 
 installing and or compiling from Eclipse will agree with using the CLI.
 
 One can do whatever pleases themselves, but I think erring on the side of 
 consistency is more correct (betterer???)! And it is not really erring, it 
 is making an informed decision.
 
 Can you override ant’s properties?
 
 ant -Dproperties=wolips.543.properties
 
 So I agree with Markus, we should tone down the usage of .543. (multiple 
 versions) or at the least call it not recommended and the above is why.
 
 
> On Feb 21, 2019, at 9:39 AM, Maik Musall  > wrote:
> 
> Hi Ted,
> 
> I went through the install process on a clean machine, created new 
> screenshots and updated the Project Wonder Installation page with that. 
> But I kept the wolips.543.properties scheme that had been described 
> there, even though the comments at the bottom recommend not doing that 
> and ignore the versioning. I also have the impression that skipping the 
> version distinction would be better.
> 
> I can update that again, but I'd like a discussion about that detail here 
> before.
> 
> Maik
> 
> 
>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky > >:
>> 
>> So I can edit some pages but not all  :(
>> 
>> 
>> I can edit in here for instance:
>> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>>  
>> 
>> 
>> but I cannot edit here:
>> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
>> 
>> 
>> I have always been very confused in the wiki. I know that Maik Musall 
>> can edit here because it says at the top of the page:
>> last modified by Maik Musall 
>>  on Dec 01, 2017 
>> 
>> 
>> I would be happy to help here if we can figure out how to get me edit 
>> privs.
>> 
>> Ted
>> 
>> 
>> 
>>> On Feb 20, 2019, at 10:47 PM, Michael Sharp >> > wrote:
>>> 
>>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>>> reference the appropriate version of Eclipse and WOLips update site URL.
>>> 
>>> - Sharpy.
>>> 
 On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >>> > wrote:
 
 ???
 
 should the wiki be updated to reflect this URL?
 
 I hate the idea of having to examine the mail archives to find  this.
 
 Ted
 
> On Feb 18, 2019, at 7:38 PM, Henrique Prange  > wrote:
> 
> Hey guys,
> 
> Just to let you know that I've merged Michael's pull request into the 
> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
> changes on that branch. You can test it by pointing your WOLips 
> update site to:
> 
> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>  
> 

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Maik Musall]

Hi Hugi,

glad you're volunteering to add that variant to the wiki page :)

Maik


> Am 21.02.2019 um 18:13 schrieb Hugi Thordarson :
> 
> Ya'll need Maven.
> 
> - hugi
> 
> 
>> On 21 Feb 2019, at 17:09, Tim Worman > > wrote:
>> 
>> I would think, at this point, that the number of devs swapping between 
>> multiple versions of WO would be close to zero. Anyone supporting a legacy 
>> codebase will probably know what to do. Perhaps there could simply be a link 
>> to a separate article - “How to maintain multiple versions of WO."
>> 
>> Tim
>> 
>>> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky >> > wrote:
>>> 
>>> The problem is that (If I remember correctly) when you invoke ant on the 
>>> CLI, ant uses wolips.properties. it will ignore anything else.
>>> 
>>> so if you have a wolips.543.properties and Eclipse is set up to use it, 
>>> then Eclipse is Okay, but the CLI will not use it.
>>> 
>>> So I think it is better to NOT use the wolips.543.properties so that 
>>> installing and or compiling from Eclipse will agree with using the CLI.
>>> 
>>> One can do whatever pleases themselves, but I think erring on the side of 
>>> consistency is more correct (betterer???)! And it is not really erring, it 
>>> is making an informed decision.
>>> 
>>> Can you override ant’s properties?
>>> 
>>> ant -Dproperties=wolips.543.properties
>>> 
>>> So I agree with Markus, we should tone down the usage of .543. (multiple 
>>> versions) or at the least call it not recommended and the above is why.
>>> 
>>> 
 On Feb 21, 2019, at 9:39 AM, Maik Musall >>> > wrote:
 
 Hi Ted,
 
 I went through the install process on a clean machine, created new 
 screenshots and updated the Project Wonder Installation page with that. 
 But I kept the wolips.543.properties scheme that had been described there, 
 even though the comments at the bottom recommend not doing that and ignore 
 the versioning. I also have the impression that skipping the version 
 distinction would be better.
 
 I can update that again, but I'd like a discussion about that detail here 
 before.
 
 Maik
 
 
> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky  >:
> 
> So I can edit some pages but not all  :(
> 
> 
> I can edit in here for instance:
> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>  
> 
> 
> but I cannot edit here:
> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
> 
> 
> I have always been very confused in the wiki. I know that Maik Musall can 
> edit here because it says at the top of the page:
> last modified by Maik Musall 
>  on Dec 01, 2017 
> 
> 
> I would be happy to help here if we can figure out how to get me edit 
> privs.
> 
> Ted
> 
> 
> 
>> On Feb 20, 2019, at 10:47 PM, Michael Sharp > > wrote:
>> 
>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>> reference the appropriate version of Eclipse and WOLips update site URL.
>> 
>> - Sharpy.
>> 
>>> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >> > wrote:
>>> 
>>> ???
>>> 
>>> should the wiki be updated to reflect this URL?
>>> 
>>> I hate the idea of having to examine the mail archives to find  this.
>>> 
>>> Ted
>>> 
 On Feb 18, 2019, at 7:38 PM, Henrique Prange >>> > wrote:
 
 Hey guys,
 
 Just to let you know that I've merged Michael's pull request into the 
 eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
 changes on that branch. You can test it by pointing your WOLips update 
 site to:
 
 https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
  
 
 
 It looks good on my machine.
 
 Cheers,
 
 HP
 
> On Feb 17, 2019, at 7:52 PM, Michael Sharp  > wrote:
> 
> Hi Henrique,
> 
> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
> 
> 
> Cheers,
> 
> - Sharpy.
> 
> 
>> O

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Hugi Thordarson]

Ya'll need Maven.

- hugi


> On 21 Feb 2019, at 17:09, Tim Worman  wrote:
> 
> I would think, at this point, that the number of devs swapping between 
> multiple versions of WO would be close to zero. Anyone supporting a legacy 
> codebase will probably know what to do. Perhaps there could simply be a link 
> to a separate article - “How to maintain multiple versions of WO."
> 
> Tim
> 
>> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky > > wrote:
>> 
>> The problem is that (If I remember correctly) when you invoke ant on the 
>> CLI, ant uses wolips.properties. it will ignore anything else.
>> 
>> so if you have a wolips.543.properties and Eclipse is set up to use it, then 
>> Eclipse is Okay, but the CLI will not use it.
>> 
>> So I think it is better to NOT use the wolips.543.properties so that 
>> installing and or compiling from Eclipse will agree with using the CLI.
>> 
>> One can do whatever pleases themselves, but I think erring on the side of 
>> consistency is more correct (betterer???)! And it is not really erring, it 
>> is making an informed decision.
>> 
>> Can you override ant’s properties?
>> 
>> ant -Dproperties=wolips.543.properties
>> 
>> So I agree with Markus, we should tone down the usage of .543. (multiple 
>> versions) or at the least call it not recommended and the above is why.
>> 
>> 
>>> On Feb 21, 2019, at 9:39 AM, Maik Musall >> > wrote:
>>> 
>>> Hi Ted,
>>> 
>>> I went through the install process on a clean machine, created new 
>>> screenshots and updated the Project Wonder Installation page with that. But 
>>> I kept the wolips.543.properties scheme that had been described there, even 
>>> though the comments at the bottom recommend not doing that and ignore the 
>>> versioning. I also have the impression that skipping the version 
>>> distinction would be better.
>>> 
>>> I can update that again, but I'd like a discussion about that detail here 
>>> before.
>>> 
>>> Maik
>>> 
>>> 
 Am 21.02.2019 um 05:06 schrieb Theodore Petrosky >>> >:
 
 So I can edit some pages but not all  :(
 
 
 I can edit in here for instance:
 https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
  
 
 
 but I cannot edit here:
 https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
 
 
 I have always been very confused in the wiki. I know that Maik Musall can 
 edit here because it says at the top of the page:
 last modified by Maik Musall 
  on Dec 01, 2017 
 
 
 I would be happy to help here if we can figure out how to get me edit 
 privs.
 
 Ted
 
 
 
> On Feb 20, 2019, at 10:47 PM, Michael Sharp  > wrote:
> 
> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
> reference the appropriate version of Eclipse and WOLips update site URL.
> 
> - Sharpy.
> 
>> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky > > wrote:
>> 
>> ???
>> 
>> should the wiki be updated to reflect this URL?
>> 
>> I hate the idea of having to examine the mail archives to find  this.
>> 
>> Ted
>> 
>>> On Feb 18, 2019, at 7:38 PM, Henrique Prange >> > wrote:
>>> 
>>> Hey guys,
>>> 
>>> Just to let you know that I've merged Michael's pull request into the 
>>> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
>>> changes on that branch. You can test it by pointing your WOLips update 
>>> site to:
>>> 
>>> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>>>  
>>> 
>>> 
>>> It looks good on my machine.
>>> 
>>> Cheers,
>>> 
>>> HP
>>> 
 On Feb 17, 2019, at 7:52 PM, Michael Sharp >>> > wrote:
 
 Hi Henrique,
 
 Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
 
 
 Cheers,
 
 - Sharpy.
 
 
> On 18 Feb 2019, at 3:11 am, Henrique Prange  > wrote:
> 
> Hi Michael,
> 
> I've pushed a new branch eclipse_4_10 to track changes and fixes for 
> Eclipse 2018-12 momentarily. Would you mind to create a pull request?
> 
>>>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Tim Worman]

I would think, at this point, that the number of devs swapping between multiple 
versions of WO would be close to zero. Anyone supporting a legacy codebase will 
probably know what to do. Perhaps there could simply be a link to a separate 
article - “How to maintain multiple versions of WO."

Tim

> On Feb 21, 2019, at 8:10 AM, Theodore Petrosky  wrote:
> 
> The problem is that (If I remember correctly) when you invoke ant on the CLI, 
> ant uses wolips.properties. it will ignore anything else.
> 
> so if you have a wolips.543.properties and Eclipse is set up to use it, then 
> Eclipse is Okay, but the CLI will not use it.
> 
> So I think it is better to NOT use the wolips.543.properties so that 
> installing and or compiling from Eclipse will agree with using the CLI.
> 
> One can do whatever pleases themselves, but I think erring on the side of 
> consistency is more correct (betterer???)! And it is not really erring, it is 
> making an informed decision.
> 
> Can you override ant’s properties?
> 
> ant -Dproperties=wolips.543.properties
> 
> So I agree with Markus, we should tone down the usage of .543. (multiple 
> versions) or at the least call it not recommended and the above is why.
> 
> 
>> On Feb 21, 2019, at 9:39 AM, Maik Musall > > wrote:
>> 
>> Hi Ted,
>> 
>> I went through the install process on a clean machine, created new 
>> screenshots and updated the Project Wonder Installation page with that. But 
>> I kept the wolips.543.properties scheme that had been described there, even 
>> though the comments at the bottom recommend not doing that and ignore the 
>> versioning. I also have the impression that skipping the version distinction 
>> would be better.
>> 
>> I can update that again, but I'd like a discussion about that detail here 
>> before.
>> 
>> Maik
>> 
>> 
>>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky >> >:
>>> 
>>> So I can edit some pages but not all  :(
>>> 
>>> 
>>> I can edit in here for instance:
>>> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>>>  
>>> 
>>> 
>>> but I cannot edit here:
>>> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
>>> 
>>> 
>>> I have always been very confused in the wiki. I know that Maik Musall can 
>>> edit here because it says at the top of the page:
>>> last modified by Maik Musall 
>>>  on Dec 01, 2017 
>>> 
>>> 
>>> I would be happy to help here if we can figure out how to get me edit privs.
>>> 
>>> Ted
>>> 
>>> 
>>> 
 On Feb 20, 2019, at 10:47 PM, Michael Sharp >>> > wrote:
 
 A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
 reference the appropriate version of Eclipse and WOLips update site URL.
 
 - Sharpy.
 
> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky  > wrote:
> 
> ???
> 
> should the wiki be updated to reflect this URL?
> 
> I hate the idea of having to examine the mail archives to find  this.
> 
> Ted
> 
>> On Feb 18, 2019, at 7:38 PM, Henrique Prange > > wrote:
>> 
>> Hey guys,
>> 
>> Just to let you know that I've merged Michael's pull request into the 
>> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
>> changes on that branch. You can test it by pointing your WOLips update 
>> site to:
>> 
>> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>>  
>> 
>> 
>> It looks good on my machine.
>> 
>> Cheers,
>> 
>> HP
>> 
>>> On Feb 17, 2019, at 7:52 PM, Michael Sharp >> > wrote:
>>> 
>>> Hi Henrique,
>>> 
>>> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
>>> 
>>> 
>>> Cheers,
>>> 
>>> - Sharpy.
>>> 
>>> 
 On 18 Feb 2019, at 3:11 am, Henrique Prange >>> > wrote:
 
 Hi Michael,
 
 I've pushed a new branch eclipse_4_10 to track changes and fixes for 
 Eclipse 2018-12 momentarily. Would you mind to create a pull request?
 
 Cheers,
 
 HP
 
> On Feb 14, 2019, at 10:00 PM, Michael Sharp  > wrote:
> 
> Hi Samuel,
> 
> I’m happy to create a pull request but I’m not sure there’s a

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Markus Ruggiero]

> On 21 Feb 2019, at 15:39, Maik Musall  wrote:
> 
> Hi Ted,
> 
> I went through the install process on a clean machine, created new 
> screenshots and updated the Project Wonder Installation page with that. But I 
> kept the wolips.543.properties scheme that had been described there, even 
> though the comments at the bottom recommend not doing that and ignore the 
> versioning. I also have the impression that skipping the version distinction 
> would be better.
> 
> I can update that again, but I'd like a discussion about that detail here 
> before.
> 

I would remove all that versioning stuff. We oldies already know what we do and 
are properly set up, all others should use "the latest and greatest" WebObjects 
5.4.3 anyway. I have also streamlined the whole installation and directoy setup 
in an add-on doc to my book Learning The Wonders. Maybe add a pointer to 
https://learningthewonders.com at the top of that page? All the relevant 
chapters are freely downloadable.

---markus---

> Maik
> 
> 
>> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky > >:
>> 
>> So I can edit some pages but not all  :(
>> 
>> 
>> I can edit in here for instance:
>> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>>  
>> 
>> 
>> but I cannot edit here:
>> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
>> 
>> 
>> I have always been very confused in the wiki. I know that Maik Musall can 
>> edit here because it says at the top of the page:
>> last modified by Maik Musall  
>> on Dec 01, 2017 
>> 
>> 
>> I would be happy to help here if we can figure out how to get me edit privs.
>> 
>> Ted
>> 
>> 
>> 
>>> On Feb 20, 2019, at 10:47 PM, Michael Sharp >> > wrote:
>>> 
>>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>>> reference the appropriate version of Eclipse and WOLips update site URL.
>>> 
>>> - Sharpy.
>>> 
 On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >>> > wrote:
 
 ???
 
 should the wiki be updated to reflect this URL?
 
 I hate the idea of having to examine the mail archives to find  this.
 
 Ted
 
> On Feb 18, 2019, at 7:38 PM, Henrique Prange  > wrote:
> 
> Hey guys,
> 
> Just to let you know that I've merged Michael's pull request into the 
> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
> changes on that branch. You can test it by pointing your WOLips update 
> site to:
> 
> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>  
> 
> 
> It looks good on my machine.
> 
> Cheers,
> 
> HP
> 
>> On Feb 17, 2019, at 7:52 PM, Michael Sharp > > wrote:
>> 
>> Hi Henrique,
>> 
>> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
>> 
>> 
>> Cheers,
>> 
>> - Sharpy.
>> 
>> 
>>> On 18 Feb 2019, at 3:11 am, Henrique Prange >> > wrote:
>>> 
>>> Hi Michael,
>>> 
>>> I've pushed a new branch eclipse_4_10 to track changes and fixes for 
>>> Eclipse 2018-12 momentarily. Would you mind to create a pull request?
>>> 
>>> Cheers,
>>> 
>>> HP
>>> 
 On Feb 14, 2019, at 10:00 PM, Michael Sharp >>> > wrote:
 
 Hi Samuel,
 
 I’m happy to create a pull request but I’m not sure there’s an 
 appropriate destination branch at wocommunity/wolips yet.
 
 I’d like to see jenkins.wocommunity building this too. I have jenkins 
 building it here with both rebel and jprofiler support, although I’m 
 unable to test those particular features.
 
 - Sharpy
 
 ps: my last message was sent from an email address that is not 
 registered for the list, this one should make it. It’s been a while..
 
> On 15 Feb 2019, at 1:50 am, Samuel Pelletier  > wrote:
> 
> Hi,
> 
> I managed to build your branch with the readme content (There are too 
> many build instruction out there...) and after fixing the wo.root in 
> the wobuild.property file that was not up to date. I built without 
> jprofiler and without jrebel.
> 
>>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Maik Musall]

Hi Ted,

I went through the install process on a clean machine, created new screenshots 
and updated the Project Wonder Installation page with that. But I kept the 
wolips.543.properties scheme that had been described there, even though the 
comments at the bottom recommend not doing that and ignore the versioning. I 
also have the impression that skipping the version distinction would be better.

I can update that again, but I'd like a discussion about that detail here 
before.

Maik


> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky :
> 
> So I can edit some pages but not all  :(
> 
> 
> I can edit in here for instance:
> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>  
> 
> 
> but I cannot edit here:
> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
> 
> 
> I have always been very confused in the wiki. I know that Maik Musall can 
> edit here because it says at the top of the page:
> last modified by Maik Musall  
> on Dec 01, 2017 
> 
> 
> I would be happy to help here if we can figure out how to get me edit privs.
> 
> Ted
> 
> 
> 
>> On Feb 20, 2019, at 10:47 PM, Michael Sharp > > wrote:
>> 
>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>> reference the appropriate version of Eclipse and WOLips update site URL.
>> 
>> - Sharpy.
>> 
>>> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >> > wrote:
>>> 
>>> ???
>>> 
>>> should the wiki be updated to reflect this URL?
>>> 
>>> I hate the idea of having to examine the mail archives to find  this.
>>> 
>>> Ted
>>> 
 On Feb 18, 2019, at 7:38 PM, Henrique Prange >>> > wrote:
 
 Hey guys,
 
 Just to let you know that I've merged Michael's pull request into the 
 eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
 changes on that branch. You can test it by pointing your WOLips update 
 site to:
 
 https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
  
 
 
 It looks good on my machine.
 
 Cheers,
 
 HP
 
> On Feb 17, 2019, at 7:52 PM, Michael Sharp  > wrote:
> 
> Hi Henrique,
> 
> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
> 
> 
> Cheers,
> 
> - Sharpy.
> 
> 
>> On 18 Feb 2019, at 3:11 am, Henrique Prange > > wrote:
>> 
>> Hi Michael,
>> 
>> I've pushed a new branch eclipse_4_10 to track changes and fixes for 
>> Eclipse 2018-12 momentarily. Would you mind to create a pull request?
>> 
>> Cheers,
>> 
>> HP
>> 
>>> On Feb 14, 2019, at 10:00 PM, Michael Sharp >> > wrote:
>>> 
>>> Hi Samuel,
>>> 
>>> I’m happy to create a pull request but I’m not sure there’s an 
>>> appropriate destination branch at wocommunity/wolips yet.
>>> 
>>> I’d like to see jenkins.wocommunity building this too. I have jenkins 
>>> building it here with both rebel and jprofiler support, although I’m 
>>> unable to test those particular features.
>>> 
>>> - Sharpy
>>> 
>>> ps: my last message was sent from an email address that is not 
>>> registered for the list, this one should make it. It’s been a while..
>>> 
 On 15 Feb 2019, at 1:50 am, Samuel Pelletier >>> > wrote:
 
 Hi,
 
 I managed to build your branch with the readme content (There are too 
 many build instruction out there...) and after fixing the wo.root in 
 the wobuild.property file that was not up to date. I built without 
 jprofiler and without jrebel.
 
 AddKey works again.
 
 It would be a good thing to create the official repo with these and 
 start the automatic builds. What is the next step to put that in place 
 ?
 
 Regards,
 
 Samuel
 
> Le 13 févr. 2019 à 18:29, Michael Sharp  > a écrit :
> 
> I’m building a WOLips4.10 variation locally from my branch at 
> https://github.com/getsharp/wolips/tree/eclipse_4_10 
> 
> 
> The changes to their internal JDT APIs (such as StubUtility) was a 
>>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Maik Musall]

Hi Ted,

I'll try to find some time today to update those articles, and also look after 
the permission situation.

Maik


> Am 21.02.2019 um 05:06 schrieb Theodore Petrosky :
> 
> So I can edit some pages but not all  :(
> 
> 
> I can edit in here for instance:
> https://wiki.wocommunity.org/display/documentation/Building+a+WebObjects+Project
>  
> 
> 
> but I cannot edit here:
> https://wiki.wocommunity.org/display/WEB/Project+Wonder+Installation 
> 
> 
> I have always been very confused in the wiki. I know that Maik Musall can 
> edit here because it says at the top of the page:
> last modified by Maik Musall  
> on Dec 01, 2017 
> 
> 
> I would be happy to help here if we can figure out how to get me edit privs.
> 
> Ted
> 
> 
> 
>> On Feb 20, 2019, at 10:47 PM, Michael Sharp > > wrote:
>> 
>> A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
>> reference the appropriate version of Eclipse and WOLips update site URL.
>> 
>> - Sharpy.
>> 
>>> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky >> > wrote:
>>> 
>>> ???
>>> 
>>> should the wiki be updated to reflect this URL?
>>> 
>>> I hate the idea of having to examine the mail archives to find  this.
>>> 
>>> Ted
>>> 
 On Feb 18, 2019, at 7:38 PM, Henrique Prange >>> > wrote:
 
 Hey guys,
 
 Just to let you know that I've merged Michael's pull request into the 
 eclipse_4_10 branch. Maik did set up a new Jenkins job to build from 
 changes on that branch. You can test it by pointing your WOLips update 
 site to:
 
 https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
  
 
 
 It looks good on my machine.
 
 Cheers,
 
 HP
 
> On Feb 17, 2019, at 7:52 PM, Michael Sharp  > wrote:
> 
> Hi Henrique,
> 
> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
> 
> 
> Cheers,
> 
> - Sharpy.
> 
> 
>> On 18 Feb 2019, at 3:11 am, Henrique Prange > > wrote:
>> 
>> Hi Michael,
>> 
>> I've pushed a new branch eclipse_4_10 to track changes and fixes for 
>> Eclipse 2018-12 momentarily. Would you mind to create a pull request?
>> 
>> Cheers,
>> 
>> HP
>> 
>>> On Feb 14, 2019, at 10:00 PM, Michael Sharp >> > wrote:
>>> 
>>> Hi Samuel,
>>> 
>>> I’m happy to create a pull request but I’m not sure there’s an 
>>> appropriate destination branch at wocommunity/wolips yet.
>>> 
>>> I’d like to see jenkins.wocommunity building this too. I have jenkins 
>>> building it here with both rebel and jprofiler support, although I’m 
>>> unable to test those particular features.
>>> 
>>> - Sharpy
>>> 
>>> ps: my last message was sent from an email address that is not 
>>> registered for the list, this one should make it. It’s been a while..
>>> 
 On 15 Feb 2019, at 1:50 am, Samuel Pelletier >>> > wrote:
 
 Hi,
 
 I managed to build your branch with the readme content (There are too 
 many build instruction out there...) and after fixing the wo.root in 
 the wobuild.property file that was not up to date. I built without 
 jprofiler and without jrebel.
 
 AddKey works again.
 
 It would be a good thing to create the official repo with these and 
 start the automatic builds. What is the next step to put that in place 
 ?
 
 Regards,
 
 Samuel
 
> Le 13 févr. 2019 à 18:29, Michael Sharp  > a écrit :
> 
> I’m building a WOLips4.10 variation locally from my branch at 
> https://github.com/getsharp/wolips/tree/eclipse_4_10 
> 
> 
> The changes to their internal JDT APIs (such as StubUtility) was a 
> pretty good incentive to leave them alone all together.
> 
> Add Key and a few other broken features are fixed for me with this 
> build.
> 
> Sharpy.
> 
> 
>> On 14 Feb 2019, at 7:37 am, Samuel Pelletier > > wrote:
>> 
>> Hi all,
>> 

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Michael Sharp]

A wiki update would be good. I’ve updated README.md in the 4.10 repo to 
reference the appropriate version of Eclipse and WOLips update site URL.

- Sharpy.

> On 20 Feb 2019, at 7:03 pm, Theodore Petrosky  wrote:
> 
> ???
> 
> should the wiki be updated to reflect this URL?
> 
> I hate the idea of having to examine the mail archives to find  this.
> 
> Ted
> 
>> On Feb 18, 2019, at 7:38 PM, Henrique Prange > > wrote:
>> 
>> Hey guys,
>> 
>> Just to let you know that I've merged Michael's pull request into the 
>> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from changes 
>> on that branch. You can test it by pointing your WOLips update site to:
>> 
>> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>>  
>> 
>> 
>> It looks good on my machine.
>> 
>> Cheers,
>> 
>> HP
>> 
>>> On Feb 17, 2019, at 7:52 PM, Michael Sharp >> > wrote:
>>> 
>>> Hi Henrique,
>>> 
>>> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
>>> 
>>> 
>>> Cheers,
>>> 
>>> - Sharpy.
>>> 
>>> 
 On 18 Feb 2019, at 3:11 am, Henrique Prange >>> > wrote:
 
 Hi Michael,
 
 I've pushed a new branch eclipse_4_10 to track changes and fixes for 
 Eclipse 2018-12 momentarily. Would you mind to create a pull request?
 
 Cheers,
 
 HP
 
> On Feb 14, 2019, at 10:00 PM, Michael Sharp  > wrote:
> 
> Hi Samuel,
> 
> I’m happy to create a pull request but I’m not sure there’s an 
> appropriate destination branch at wocommunity/wolips yet.
> 
> I’d like to see jenkins.wocommunity building this too. I have jenkins 
> building it here with both rebel and jprofiler support, although I’m 
> unable to test those particular features.
> 
> - Sharpy
> 
> ps: my last message was sent from an email address that is not registered 
> for the list, this one should make it. It’s been a while..
> 
>> On 15 Feb 2019, at 1:50 am, Samuel Pelletier > > wrote:
>> 
>> Hi,
>> 
>> I managed to build your branch with the readme content (There are too 
>> many build instruction out there...) and after fixing the wo.root in the 
>> wobuild.property file that was not up to date. I built without jprofiler 
>> and without jrebel.
>> 
>> AddKey works again.
>> 
>> It would be a good thing to create the official repo with these and 
>> start the automatic builds. What is the next step to put that in place ?
>> 
>> Regards,
>> 
>> Samuel
>> 
>>> Le 13 févr. 2019 à 18:29, Michael Sharp >> > a écrit :
>>> 
>>> I’m building a WOLips4.10 variation locally from my branch at 
>>> https://github.com/getsharp/wolips/tree/eclipse_4_10 
>>> 
>>> 
>>> The changes to their internal JDT APIs (such as StubUtility) was a 
>>> pretty good incentive to leave them alone all together.
>>> 
>>> Add Key and a few other broken features are fixed for me with this 
>>> build.
>>> 
>>> Sharpy.
>>> 
>>> 
 On 14 Feb 2019, at 7:37 am, Samuel Pelletier >>> > wrote:
 
 Hi all,
 
 I experience Eclipse 2018-12 with WOLips and DCEVM and the latest 
 WOLips and it works quite well to date.
 
 I use the openjdk11 with DCEVM and Hotswap integrated found at this 
 location, it is important to use the latest (+8 at this time) version 
 if you use Groovy.
 https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
 
 
 This download contains the entire JVM directory, to install it :
cd /Library/Java/JavaVirtualMachines/
sudo tar zxf 
 /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
Then go to Eclipse preferences to add the new JVM.
 
 This JVM is for dev only, it always starts with DCEVM and Hotswap. 
 DCEVM is a free hot code replacement like JRebel and HotSwap contains 
 plugins to help the engine.
 
 Apps compile and run faster (real or placebo effet) than my previous 
 setup.
 
 The only downside to date is the addKey in the WO editor that no 
 longer works.
 
 It fail with java.lang.NoClassDefFoundError: 
 org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found 
 the addKey problem in WOLips, the team moved an internal classe used 
 by this function in 

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Paul Hoadley]

On 19 Feb 2019, at 11:08, Henrique Prange  wrote:

> Just to let you know that I've merged Michael's pull request into the 
> eclipse_4_10 branch. Maik did set up a new Jenkins job to build from changes 
> on that branch. You can test it by pointing your WOLips update site to:
> 
> https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/
>  
> 
> 
> It looks good on my machine.

Works here! Adding keys from the template working again. Thanks everyone.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Henrique Prange]

Hey guys,

Just to let you know that I've merged Michael's pull request into the 
eclipse_4_10 branch. Maik did set up a new Jenkins job to build from changes on 
that branch. You can test it by pointing your WOLips update site to:

https://jenkins.wocommunity.org/job/WOLips410/lastSuccessfulBuild/artifact/temp/dist/

It looks good on my machine.

Cheers,

HP

> On Feb 17, 2019, at 7:52 PM, Michael Sharp  wrote:
> 
> Hi Henrique,
> 
> Thank you, PR here https://github.com/wocommunity/wolips/pull/139 
> 
> 
> Cheers,
> 
> - Sharpy.
> 
> 
>> On 18 Feb 2019, at 3:11 am, Henrique Prange > > wrote:
>> 
>> Hi Michael,
>> 
>> I've pushed a new branch eclipse_4_10 to track changes and fixes for Eclipse 
>> 2018-12 momentarily. Would you mind to create a pull request?
>> 
>> Cheers,
>> 
>> HP
>> 
>>> On Feb 14, 2019, at 10:00 PM, Michael Sharp >> > wrote:
>>> 
>>> Hi Samuel,
>>> 
>>> I’m happy to create a pull request but I’m not sure there’s an appropriate 
>>> destination branch at wocommunity/wolips yet.
>>> 
>>> I’d like to see jenkins.wocommunity building this too. I have jenkins 
>>> building it here with both rebel and jprofiler support, although I’m unable 
>>> to test those particular features.
>>> 
>>> - Sharpy
>>> 
>>> ps: my last message was sent from an email address that is not registered 
>>> for the list, this one should make it. It’s been a while..
>>> 
 On 15 Feb 2019, at 1:50 am, Samuel Pelletier >>> > wrote:
 
 Hi,
 
 I managed to build your branch with the readme content (There are too many 
 build instruction out there...) and after fixing the wo.root in the 
 wobuild.property file that was not up to date. I built without jprofiler 
 and without jrebel.
 
 AddKey works again.
 
 It would be a good thing to create the official repo with these and start 
 the automatic builds. What is the next step to put that in place ?
 
 Regards,
 
 Samuel
 
> Le 13 févr. 2019 à 18:29, Michael Sharp  > a écrit :
> 
> I’m building a WOLips4.10 variation locally from my branch at 
> https://github.com/getsharp/wolips/tree/eclipse_4_10 
> 
> 
> The changes to their internal JDT APIs (such as StubUtility) was a pretty 
> good incentive to leave them alone all together.
> 
> Add Key and a few other broken features are fixed for me with this build.
> 
> Sharpy.
> 
> 
>> On 14 Feb 2019, at 7:37 am, Samuel Pelletier > > wrote:
>> 
>> Hi all,
>> 
>> I experience Eclipse 2018-12 with WOLips and DCEVM and the latest WOLips 
>> and it works quite well to date.
>> 
>> I use the openjdk11 with DCEVM and Hotswap integrated found at this 
>> location, it is important to use the latest (+8 at this time) version if 
>> you use Groovy.
>>   https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
>> 
>> 
>> This download contains the entire JVM directory, to install it :
>>  cd /Library/Java/JavaVirtualMachines/
>>  sudo tar zxf /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
>>  Then go to Eclipse preferences to add the new JVM.
>> 
>> This JVM is for dev only, it always starts with DCEVM and Hotswap. DCEVM 
>> is a free hot code replacement like JRebel and HotSwap contains plugins 
>> to help the engine.
>> 
>> Apps compile and run faster (real or placebo effet) than my previous 
>> setup.
>> 
>> The only downside to date is the addKey in the WO editor that no longer 
>> works.
>> 
>> It fail with java.lang.NoClassDefFoundError: 
>> org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found 
>> the addKey problem in WOLips, the team moved an internal classe used by 
>> this function in the AddKeyInfo class. Here is the import that need to 
>> change in this file.
>> 
>> -import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
>> +import org.eclipse.jdt.internal.core.manipulation.StubUtility;
>> 
>> My problem now is I do not have a working WOLips build environment to 
>> test this. I tried to follow the Wiki instruction but I only get fail 
>> build du to missing something.
>> 
>> If someone has a working WOLips development setup, please update it with 
>> Eclipse 2018-12 and apply my patch to build a new WOLips. This will 
>> require a new WOLips version for Eclipse 4.10+ since this code will no 
>> longer works with the previous version.
>> 
>> Samuel
>> ___
>> Do not post admin requests to the list. They will be ignored.
>>

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Michael Sharp]

Hi Henrique,

Thank you, PR here https://github.com/wocommunity/wolips/pull/139 


Cheers,

- Sharpy.


> On 18 Feb 2019, at 3:11 am, Henrique Prange  wrote:
> 
> Hi Michael,
> 
> I've pushed a new branch eclipse_4_10 to track changes and fixes for Eclipse 
> 2018-12 momentarily. Would you mind to create a pull request?
> 
> Cheers,
> 
> HP
> 
>> On Feb 14, 2019, at 10:00 PM, Michael Sharp > > wrote:
>> 
>> Hi Samuel,
>> 
>> I’m happy to create a pull request but I’m not sure there’s an appropriate 
>> destination branch at wocommunity/wolips yet.
>> 
>> I’d like to see jenkins.wocommunity building this too. I have jenkins 
>> building it here with both rebel and jprofiler support, although I’m unable 
>> to test those particular features.
>> 
>> - Sharpy
>> 
>> ps: my last message was sent from an email address that is not registered 
>> for the list, this one should make it. It’s been a while..
>> 
>>> On 15 Feb 2019, at 1:50 am, Samuel Pelletier >> > wrote:
>>> 
>>> Hi,
>>> 
>>> I managed to build your branch with the readme content (There are too many 
>>> build instruction out there...) and after fixing the wo.root in the 
>>> wobuild.property file that was not up to date. I built without jprofiler 
>>> and without jrebel.
>>> 
>>> AddKey works again.
>>> 
>>> It would be a good thing to create the official repo with these and start 
>>> the automatic builds. What is the next step to put that in place ?
>>> 
>>> Regards,
>>> 
>>> Samuel
>>> 
 Le 13 févr. 2019 à 18:29, Michael Sharp >>> > a écrit :
 
 I’m building a WOLips4.10 variation locally from my branch at 
 https://github.com/getsharp/wolips/tree/eclipse_4_10 
 
 
 The changes to their internal JDT APIs (such as StubUtility) was a pretty 
 good incentive to leave them alone all together.
 
 Add Key and a few other broken features are fixed for me with this build.
 
 Sharpy.
 
 
> On 14 Feb 2019, at 7:37 am, Samuel Pelletier  > wrote:
> 
> Hi all,
> 
> I experience Eclipse 2018-12 with WOLips and DCEVM and the latest WOLips 
> and it works quite well to date.
> 
> I use the openjdk11 with DCEVM and Hotswap integrated found at this 
> location, it is important to use the latest (+8 at this time) version if 
> you use Groovy.
>https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
> 
> 
> This download contains the entire JVM directory, to install it :
>   cd /Library/Java/JavaVirtualMachines/
>   sudo tar zxf /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
>   Then go to Eclipse preferences to add the new JVM.
> 
> This JVM is for dev only, it always starts with DCEVM and Hotswap. DCEVM 
> is a free hot code replacement like JRebel and HotSwap contains plugins 
> to help the engine.
> 
> Apps compile and run faster (real or placebo effet) than my previous 
> setup.
> 
> The only downside to date is the addKey in the WO editor that no longer 
> works.
> 
> It fail with java.lang.NoClassDefFoundError: 
> org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found the 
> addKey problem in WOLips, the team moved an internal classe used by this 
> function in the AddKeyInfo class. Here is the import that need to change 
> in this file.
> 
> -import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
> +import org.eclipse.jdt.internal.core.manipulation.StubUtility;
> 
> My problem now is I do not have a working WOLips build environment to 
> test this. I tried to follow the Wiki instruction but I only get fail 
> build du to missing something.
> 
> If someone has a working WOLips development setup, please update it with 
> Eclipse 2018-12 and apply my patch to build a new WOLips. This will 
> require a new WOLips version for Eclipse 4.10+ since this code will no 
> longer works with the previous version.
> 
> Samuel
> ___
> 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/getsharp%40gmail.com
>  
> 
> 
> This email sent to getsh...@gmail.com 
 
>>> 
>>> ___
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing l

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Henrique Prange]

Hi Michael,

I've pushed a new branch eclipse_4_10 to track changes and fixes for Eclipse 
2018-12 momentarily. Would you mind to create a pull request?

Cheers,

HP

> On Feb 14, 2019, at 10:00 PM, Michael Sharp  wrote:
> 
> Hi Samuel,
> 
> I’m happy to create a pull request but I’m not sure there’s an appropriate 
> destination branch at wocommunity/wolips yet.
> 
> I’d like to see jenkins.wocommunity building this too. I have jenkins 
> building it here with both rebel and jprofiler support, although I’m unable 
> to test those particular features.
> 
> - Sharpy
> 
> ps: my last message was sent from an email address that is not registered for 
> the list, this one should make it. It’s been a while..
> 
>> On 15 Feb 2019, at 1:50 am, Samuel Pelletier > > wrote:
>> 
>> Hi,
>> 
>> I managed to build your branch with the readme content (There are too many 
>> build instruction out there...) and after fixing the wo.root in the 
>> wobuild.property file that was not up to date. I built without jprofiler and 
>> without jrebel.
>> 
>> AddKey works again.
>> 
>> It would be a good thing to create the official repo with these and start 
>> the automatic builds. What is the next step to put that in place ?
>> 
>> Regards,
>> 
>> Samuel
>> 
>>> Le 13 févr. 2019 à 18:29, Michael Sharp >> > a écrit :
>>> 
>>> I’m building a WOLips4.10 variation locally from my branch at 
>>> https://github.com/getsharp/wolips/tree/eclipse_4_10 
>>> 
>>> 
>>> The changes to their internal JDT APIs (such as StubUtility) was a pretty 
>>> good incentive to leave them alone all together.
>>> 
>>> Add Key and a few other broken features are fixed for me with this build.
>>> 
>>> Sharpy.
>>> 
>>> 
 On 14 Feb 2019, at 7:37 am, Samuel Pelletier >>> > wrote:
 
 Hi all,
 
 I experience Eclipse 2018-12 with WOLips and DCEVM and the latest WOLips 
 and it works quite well to date.
 
 I use the openjdk11 with DCEVM and Hotswap integrated found at this 
 location, it is important to use the latest (+8 at this time) version if 
 you use Groovy.
 https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
 
 
 This download contains the entire JVM directory, to install it :
cd /Library/Java/JavaVirtualMachines/
sudo tar zxf /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
Then go to Eclipse preferences to add the new JVM.
 
 This JVM is for dev only, it always starts with DCEVM and Hotswap. DCEVM 
 is a free hot code replacement like JRebel and HotSwap contains plugins to 
 help the engine.
 
 Apps compile and run faster (real or placebo effet) than my previous setup.
 
 The only downside to date is the addKey in the WO editor that no longer 
 works.
 
 It fail with java.lang.NoClassDefFoundError: 
 org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found the 
 addKey problem in WOLips, the team moved an internal classe used by this 
 function in the AddKeyInfo class. Here is the import that need to change 
 in this file.
 
 -import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
 +import org.eclipse.jdt.internal.core.manipulation.StubUtility;
 
 My problem now is I do not have a working WOLips build environment to test 
 this. I tried to follow the Wiki instruction but I only get fail build du 
 to missing something.
 
 If someone has a working WOLips development setup, please update it with 
 Eclipse 2018-12 and apply my patch to build a new WOLips. This will 
 require a new WOLips version for Eclipse 4.10+ since this code will no 
 longer works with the previous version.
 
 Samuel
 ___
 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/getsharp%40gmail.com
  
 
 
 This email sent to getsh...@gmail.com 
>>> 
>> 
>> ___
>> 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/getsharp%40gmail.com 
>> 
>> 
>> This email sent to getsh...@gmail.com 
> 
> _

Re: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Michael Sharp]

Hi Samuel,

I’m happy to create a pull request but I’m not sure there’s an appropriate 
destination branch at wocommunity/wolips yet.

I’d like to see jenkins.wocommunity building this too. I have jenkins building 
it here with both rebel and jprofiler support, although I’m unable to test 
those particular features.

- Sharpy

ps: my last message was sent from an email address that is not registered for 
the list, this one should make it. It’s been a while..

> On 15 Feb 2019, at 1:50 am, Samuel Pelletier  wrote:
> 
> Hi,
> 
> I managed to build your branch with the readme content (There are too many 
> build instruction out there...) and after fixing the wo.root in the 
> wobuild.property file that was not up to date. I built without jprofiler and 
> without jrebel.
> 
> AddKey works again.
> 
> It would be a good thing to create the official repo with these and start the 
> automatic builds. What is the next step to put that in place ?
> 
> Regards,
> 
> Samuel
> 
>> Le 13 févr. 2019 à 18:29, Michael Sharp > > a écrit :
>> 
>> I’m building a WOLips4.10 variation locally from my branch at 
>> https://github.com/getsharp/wolips/tree/eclipse_4_10 
>> 
>> 
>> The changes to their internal JDT APIs (such as StubUtility) was a pretty 
>> good incentive to leave them alone all together.
>> 
>> Add Key and a few other broken features are fixed for me with this build.
>> 
>> Sharpy.
>> 
>> 
>>> On 14 Feb 2019, at 7:37 am, Samuel Pelletier >> > wrote:
>>> 
>>> Hi all,
>>> 
>>> I experience Eclipse 2018-12 with WOLips and DCEVM and the latest WOLips 
>>> and it works quite well to date.
>>> 
>>> I use the openjdk11 with DCEVM and Hotswap integrated found at this 
>>> location, it is important to use the latest (+8 at this time) version if 
>>> you use Groovy.
>>>  https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
>>> 
>>> 
>>> This download contains the entire JVM directory, to install it :
>>> cd /Library/Java/JavaVirtualMachines/
>>> sudo tar zxf /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
>>> Then go to Eclipse preferences to add the new JVM.
>>> 
>>> This JVM is for dev only, it always starts with DCEVM and Hotswap. DCEVM is 
>>> a free hot code replacement like JRebel and HotSwap contains plugins to 
>>> help the engine.
>>> 
>>> Apps compile and run faster (real or placebo effet) than my previous setup.
>>> 
>>> The only downside to date is the addKey in the WO editor that no longer 
>>> works.
>>> 
>>> It fail with java.lang.NoClassDefFoundError: 
>>> org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found the 
>>> addKey problem in WOLips, the team moved an internal classe used by this 
>>> function in the AddKeyInfo class. Here is the import that need to change in 
>>> this file.
>>> 
>>> -import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
>>> +import org.eclipse.jdt.internal.core.manipulation.StubUtility;
>>> 
>>> My problem now is I do not have a working WOLips build environment to test 
>>> this. I tried to follow the Wiki instruction but I only get fail build du 
>>> to missing something.
>>> 
>>> If someone has a working WOLips development setup, please update it with 
>>> Eclipse 2018-12 and apply my patch to build a new WOLips. This will require 
>>> a new WOLips version for Eclipse 4.10+ since this code will no longer works 
>>> with the previous version.
>>> 
>>> Samuel
>>> ___
>>> 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/getsharp%40gmail.com 
>>> 
>>> 
>>> This email sent to getsh...@gmail.com 
>> 
> 
> ___
> 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/getsharp%40gmail.com
> 
> This email sent to getsh...@gmail.com

 ___
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: WOLips, Eclipse 2018-12 with openjdk11 and dcevm-hotswap

[Samuel Pelletier]

Hi,

I managed to build your branch with the readme content (There are too many 
build instruction out there...) and after fixing the wo.root in the 
wobuild.property file that was not up to date. I built without jprofiler and 
without jrebel.

AddKey works again.

It would be a good thing to create the official repo with these and start the 
automatic builds. What is the next step to put that in place ?

Regards,

Samuel

> Le 13 févr. 2019 à 18:29, Michael Sharp  a écrit :
> 
> I’m building a WOLips4.10 variation locally from my branch at 
> https://github.com/getsharp/wolips/tree/eclipse_4_10 
> 
> 
> The changes to their internal JDT APIs (such as StubUtility) was a pretty 
> good incentive to leave them alone all together.
> 
> Add Key and a few other broken features are fixed for me with this build.
> 
> Sharpy.
> 
> 
>> On 14 Feb 2019, at 7:37 am, Samuel Pelletier > > wrote:
>> 
>> Hi all,
>> 
>> I experience Eclipse 2018-12 with WOLips and DCEVM and the latest WOLips and 
>> it works quite well to date.
>> 
>> I use the openjdk11 with DCEVM and Hotswap integrated found at this 
>> location, it is important to use the latest (+8 at this time) version if you 
>> use Groovy.
>>   https://github.com/TravaOpenJDK/trava-jdk-11-dcevm/releases 
>> 
>> 
>> This download contains the entire JVM directory, to install it :
>>  cd /Library/Java/JavaVirtualMachines/
>>  sudo tar zxf /Users/yourDownloadLocation/java11-openjdk-dcevm-osx.tar.gz
>>  Then go to Eclipse preferences to add the new JVM.
>> 
>> This JVM is for dev only, it always starts with DCEVM and Hotswap. DCEVM is 
>> a free hot code replacement like JRebel and HotSwap contains plugins to help 
>> the engine.
>> 
>> Apps compile and run faster (real or placebo effet) than my previous setup.
>> 
>> The only downside to date is the addKey in the WO editor that no longer 
>> works.
>> 
>> It fail with java.lang.NoClassDefFoundError: 
>> org/eclipse/jdt/internal/corext/codemanipulation/StubUtility. I found the 
>> addKey problem in WOLips, the team moved an internal classe used by this 
>> function in the AddKeyInfo class. Here is the import that need to change in 
>> this file.
>> 
>> -import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
>> +import org.eclipse.jdt.internal.core.manipulation.StubUtility;
>> 
>> My problem now is I do not have a working WOLips build environment to test 
>> this. I tried to follow the Wiki instruction but I only get fail build du to 
>> missing something.
>> 
>> If someone has a working WOLips development setup, please update it with 
>> Eclipse 2018-12 and apply my patch to build a new WOLips. This will require 
>> a new WOLips version for Eclipse 4.10+ since this code will no longer works 
>> with the previous version.
>> 
>> Samuel
>> ___
>> 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/getsharp%40gmail.com 
>> 
>> 
>> This email sent to getsh...@gmail.com
> 

 ___
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