|
|
This is awesome :)
> On 11 Nov 2021, at 00:55, Ramsey Gurley <webobjects-dev@wocommunity.org> wrote:
>
> So I fixed this,
>
> https://github.com/wocommunity/wolips/pull/160
>
> I've modified the entity modeler such that a WO installation is not needed to build entity modeler. It turns out there were only 3 classes that even needed the WO_HOME. So I rebuilt those three using reflection and assume the classes are available at runtime. It can find the WO jars in the maven repository after my last fix. It still does the old thing as well, checking for the roots set up in WOLips.properties. It just adds the additional magic if your project is using maven. And it works.
>
> Hopefully this makes contributing to WOLips easier too as there's no extra step of installing a WO_HOME required. Just install eclipse, clone the wolips source, import the wolips projects, and set up the run configuration. Once it is merged, I'll try to update https://wiki.wocommunity.org/display/WOL/Debugging+WOLips with the simplified instructions.
>
> I'll probably merge around the end of the week. Check it out and play with it if anyone is inclined to do so.
>
> Ramsey
>
>> On Apr 9, 2021, at 1:03 PM, Wolfgang Hartmann <webobjects-dev@wocommunity.org> wrote:
>>
>> The WORoot is necessary because the EOAdapter and especially the EO-ReverseEngineer-Tool are needing some classes out of WebObjects-Jars.
>>
>> Due to the current licence this WebObject-Jars are not allowed to be bundled and shipped with WOLips. Therefore the Wolips-Tool in that area has the workaround to modify the eclipse-classpath OnTheFly to include the Jars from WORoot.
>>
>> Best Regards,
>> Wolfgang
>>
>> Get Outlook for Android
>>
>> From: WebObjects & WOnder Development <webobjects-dev@wocommunity.org> on behalf of Ramsey Gurley <webobjects-dev@wocommunity.org>
>> Sent: Thursday, April 8, 2021 2:08:20 AM
>> To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
>> Subject: [WO-DEV] Re: Source for the deployed archetypes on maven.wocommunity.org?
>>
>> I bet you need to talk to Henrique :)
>>
>> I've been looking into making some new archetypes for a basic woapp and framework. Some observations,
>>
>> Adding the wocommunity repos in the pom.xml <repositories> and <pluginRepositories> allows me to build a woproject in maven successfully without any additional magic, which is great. This is almost to the point where to do WO Dev, all you need is eclipse, install wolips, and then create a new maven project with the archetype. Three easy steps.
>>
>> The only snag I've found so far is the EOModel creation wizard in WOLips. The Adaptor: and PlugIn: popup menus are empty and trying to click finish produces an index out of bound exception instead of a new model. It's easy to work around this by creating a plist file like,
>>
>> proj/Resources/myNewModel.eomodeld/index.eomodeld
>>
>> with a contents of
>>
>> {
>> EOModelVersion = "2.1";
>> adaptorName = JDBC;
>> connectionDictionary = {};
>> userInfo = {};
>> }
>>
>> That's enough to get it to open in EOModeler, but it would be nicer if the wizard worked without a WORoot configured. Realistically, nobody is going to use anything other than adaptorName=JDBC anyway, but the wizard could use a hard coded default list (JDBC,LDAP) if WORoot is empty. Nobody is making new adaptors.
>>
>>> On Apr 8, 2021, at 6:51 AM, Hugi Thordarson <webobjects-dev@wocommunity.org> wrote:
>>>
>>> Hi all,
>>> does anyone know where the sources for the currently deployed maven archetypes (2.2-SNAPSHOT) on maven.wocommunity.org are?
>>> The WOCommunity WOLips repo has sources (https://github.com/wocommunity/wolips/tree/master/maven2/archetypes) but these seem, well, ancient.
>>>
>>> Cheers,
>>> - hugi
>>
>> Confidentiality Notice: This email, including all attachments and replies thereto, are covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521 and are legally privileged. This information is confidential, and intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. Please notify us if you have received this transmission in error. Thank you.
>
> Confidentiality Notice: This email, including all attachments and replies thereto, are covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521 and are legally privileged. This information is confidential, and intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. Please notify us if you have received this transmission in error. Thank you.
|
|