|
I agree that there should be no requirement to have WO installed, especially if you are working on Linux with maven.
Maybe someone finds the time to change this WORoot-Jars-Location so that there is a fallback to the .m2-Repo if there is no local installation
Best Regards,
Wolfgang
From: WebObjects & WOnder Development <webobjects-dev@wocommunity.org> on behalf of Ramsey Gurley <webobjects-dev@wocommunity.org>
Sent: Friday, April 9, 2021 7:42:00 AM
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
Subject: [WO-DEV] Re: Source for the deployed archetypes on maven.wocommunity.org?
Sure, I understand that. However, I also think if we're using maven projects, and WO jars are installed in the maven repository, wolips shouldn't need a WORoot configured, because the
jars are in a known place inside the maven repo. Even if there's no WO installed at all, wolips should know two options are JDBC and LDAP and handle the missing WORoot gracefully in the model creation wizard. Providing a default list should be really easy.
Reading jars from the maven repo maybe not as much.
Interesting that you mention SQL generation/reverse engineering. I've been working on my work projects longer than I've had my current work laptop. Projects have migrated from machine to machine. Long ago, I did have a WORoot when I set everything
up. Since my latest macbook however, I've not installed WORoot anywhere. Just Eclipse+WOLips. Since everything is maven, the projects work. Interestingly even SQL generation works. I can confirm that SQL generation does not work on a linux box with just WOLips
and Eclipse installed. Spooky. I'll have to dig around in the wolips source to find out why.
In any case, I'd like sql gen/RE to work, but if they don't I can potentially cheat and use ERMigrations as a workaround for sql gen. I'm still looking for a mythical WODev to hire ( https://www.indeed.com/jobs?q=prosites&from=googlesl&vjk=c43301acc8ddb2a0 ),
but it looks like I'm going to have to train up a Java person. When I do, it would be nice if I could onboard them as easily as possible. :)
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
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.
Hi all,
does anyone know where the sources for the currently deployed maven archetypes (2.2-SNAPSHOT) on
maven.wocommunity.org are?
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.
|