|
|
| Signed Data (Text SHA256) |
I'm okay with moving away from ant builds for wonder. Someone pointed out to me the jenkins build on wocommunity has been broken for a few months now.
While on the subject of maven, I did some work on a new archetype for WO in my spare time. It's basically https://github.com/nullterminated/wodocker with a few extras. I've managed to run it not just as a docker container, but under minikube as well.
I've thought about making a couple more (one for woframework and a D2W app). I'm hoping to maybe push to maven central under a org.wocommunity.archetypes groupId, with the goal of reducing the getting started process with WO to three steps. 1. Install Eclipse 2. Install wolips 3. Start project with archetype from maven central. No local woinstall required, no fiddling with ~/.m2/settings.xml. Just three steps. And name the artifactId so searching "webobjects" finds its.
I'm aware of the existing archetypes. I don't think that repo should go away, but does anyone actually use non-Wonder woapplications anymore? Is Dave Avendasora still around? Does D2JC even work past Java 8?
Anyway, I think it would be most streamlined if the archetypes were only the 2-3 that people may use, on maven central, and easy to find. Then maybe make a quick little tutorial about how to get started in three easy steps.
+1 sounds good to me even though I still do things the old-fashioned way with ant and my hands. Haven’t gone to Maven yet but "it’s in the pipe line" (TM) 😇
---markus---
BTW, I would be willing to put some money into a “fund me” kind of thing where someone that uses Maven creates a real wiki section on using Maven. Just a thought. I’m like Ted, I though it would prevent me from keeping my current (ant) projects as they are. I understand this only applies to building Wonder. I don’t think it would be fair to ask the contributors to spend time on keeping a build system for Wonder that none of them use. So as far as my opinion counts, I’m not against dropping ant build system from the Wonder build:)
Just to answer the question from before, I do build my own Wonder frameworks. It looks like I am going to have to put in the time to get Maven going in my work flow., BTW, does anyone here subscribe to Builtlwith? I was looking around and I was amazed that the Siemens login page has a video tutorial. As I watched it I noticed that all the pages referred to had WebObjects in the URL. There is WebObjects out there. Already answered, but just for additional reassurance: What about us guys whose projects are smallish projects and never instituted Maven...
It won't affect your projects! This is purely about building the Wonder frameworks from source. You won't need to migrate your projects to Maven if you don't want to, though I strongly recommend that you do.
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._______________________________________________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/mailinglists%40kataputt.comThis email sent to mailinglists@kataputt.com
Markus Ruggiero
4051 Basel / Switzerland mobile +41 79 508 4701
|
| Content Unaltered as verified By: |
| <markus.ruggiero@rucotec.ch> |
|
|