Re: Maven: archetypes, infrastructure, and documentation
Re: Maven: archetypes, infrastructure, and documentation
- Subject: Re: Maven: archetypes, infrastructure, and documentation
- From: Lachlan Deck <email@hidden>
- Date: Sat, 21 Jan 2012 10:39:27 +1100
I've been away over the Christmas break, but it appears no one's replied, so...
On 22/12/2011, at 5:12 AM, email@hidden wrote:
> <...>
> 1. Maven archetypes–not working with eclipse? nor the wocommunity repositories, nor wonder source builds, and no modern D2w!
>
> Archetypes create projects which use things like ERExtensions version 5.0.0-SNAPSHOT. But those things the archetypes reference don't exist anywhere. OK, now try to build those things from wonder source. Again it fails. It used to work. This is the Wonder_5_0_0_Legacy branch. The only wonder source build that works is with master, using jdk 1.6, and that creates jars of version 5.4-SNAPSHOT. Projects which used to build fail, they must be modified.
Henrique and I worked on those archetypes a few years ago. I've not been doing any WebObjects development for a couple of years now; hence I've not had the need nor the opportunity to update them.
But please feel free to attempt to improve them, via github.
> <...>
> However, these 2.1-snapshot versions are not available anywhere.
Yep, I mentioned this myself some time ago. Perhaps 2.1 release is available instead.
If Henrique is around he'll be the best one to answer which is the best version to use.
> 2. Maven infrastructure
>
> Maven requires an infrastructure in order to operate.
Everything does.
> <...> As part of this infrastructure, wouldn't it be better to have a parent pom which could have all the generic webobjects common elements for webobject types of projects?
Could be useful to some people, sure. Feel free to mock one up.
> Using it in the wonder builds would insure the generic-woparent/pom.xml was correct and kept updated. The current project poms created by the various project archetypes would work with this generic-woparent/pom.xml. Everybody that currently is using parent poms could use the info in this generic-woparent/pom.xml as well.
Sure.
> I just had a strange problem where the 5.3.3 and 5.4.3 versions of jars were both listed as dependencies, and things did not work very well; my own generic-woparent/pom.xml straightened out the problem. But why have everybody re-invent the wheel? Something like this should just be part of the infrastructure, because sooner or later, every maven users will need it. (I can email mine if anybody is interested.)
Emailing yours would continue the reinvention of the wheel. Look into contributing via github.
> 3. Maven documentation
>
> Because the versions of plug-ins, maven, etc. constantly change,
They don't change with wonder builds. They remain snapshots, unless you're using a fake release. People can pick a release from the repo if they want a particular one other than the latest snapshot or release.
> wouldn't it make sense to have a documentation page which gathered all the correct, recommended, and current versions for maven?
> All the other pages would reference this ”current-versions” page, e.g. "...see the current_versions page for the correct current version to use".
Documentation like that always gets out of date unless someone volunteers to maintain it. Source code speaks for itself, point to git:HEAD :)
> That would mean there would be only one place to check, and also only one place to update this changing version information. I would update the documentation to make this so, unless people think that is a bad idea.
I'd suggest, for now, making up some documentation that you think would work for people on your own github fork, then suggest it for use.
> Also, an errata page. There are always going to be issues and things that don't work quite right. I would be useful to have a page that listed the know problems and solutions.
There used to be one somewhere. I can't recall where on the old wiki. But sure, good idea.
> 3. Maven and Wonder conflicts
>
> I haven't been bitten--only nipped--but what all are the show stoppers in Wonder/maven? There is:
#1. wolips is really ant-oriented.
> public enemy #1: ERXFileUtilities
Yep, some code in there, IIRC, assumes no jar resources :-/
> public enemy #2: ERXStaticResourceRequestHandler- Is this a problem? does Henrique's JarResourceRequestHandler solve this?
Yes it does. I sent an updated version to Henrique (which fixes a small bug in it), which I can share.
It should go into Wonder. Not sure if Henrique plans on putting it there or not.
> ERXLocalizer?
Don't know. Never used it.
Lachlan Deck
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden