Re: maven.
Re: maven.
- Subject: Re: maven.
- From: Chuck Hill <email@hidden>
- Date: Mon, 6 Apr 2009 16:19:39 -0700
On Apr 6, 2009, at 3:52 PM, Mike Schrag wrote:
We should have a concrete site for the WOProject tool set. Maven
is pretty good to generate this kind of documentation. The Wiki
could be reorganized to make general user lives easier. We need a
better structure for the wiki documentation. That is my thought
about what can help to solve the problem. But am I right?
I think just defining ANY structure for the WOProject/WOLips wiki
would be enough. At the moment it's all over the place and
there's a lot of old stuff. I like keeping it a Wiki because we
DO have several people contributing to it, and that format is just
easier -- I think it just needs an overarching outline to organize
it.
Maven automatically generates documentation for plug-ins. The
generated documentation contains information like plug-in goals and
parameters. The documentation is synchronized with the plug-in
binaries, since it is produced at the same time. If only this
portion of the documentation stay in a fixed site, it will be
easier to keep things up to date.
That is why I think a fixed site for the WOProject Maven plug-ins
will be an advantage.
Oh you're speaking specifically about the Maven parts ... We have
this same problem with all the open source stuff. People want to be
able to contribute content but they don't have commit access.
Wonder has this same issue. There was a discussion at one point
about linking all the javadoc to corresponding wiki pages to provide
the ability for people to extend the javadoc. I considered also
making it so a doclet would pull that content into the real javadoc
at build time, but Chuck mentioned that Sun provide doclets in 1.5?
I'm still not convinced I believe him, though :)
Well, when I said that I used real English sentences. ;-) And what I
said was that Sun is changing the API and so made it private in 1.5
thus preventing any custom doclets being generated.
"Sun implemented a lock-out in the doclet toolkit API to prevent
others from using it The idea was to develop the toolkit further to
finalize it and then remove the lock and make the API public. It's
unknown when or if Sun would remove this lock. Both the Standard and
MIF doclets use the doclet toolkit."
http://forums.sun.com/thread.jspa?threadID=773492
Maybe xdoclet.codehaus.org for what you want?
re: roadmap, I'm not against a roadmap, I just don't typically have
an extended time period roadmap in my mind, I have a bunch of things
I'm interested in seeing done, and maybe some of them get done.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
| References: | |
| | >maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Henrique Prange <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Lachlan Deck <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Lachlan Deck <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Lachlan Deck <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Lachlan Deck <email@hidden>) |
| | >Re: maven. (From: Henrique Prange <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Henrique Prange <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |