Nicola writes:


| From: <[EMAIL PROTECTED]>
| > Hi Nicola,
| >
| > given how much discussion is currently going on @ Krysalis about
| > autogenerating the build file for the user, and how much doco there is 
on
| > cents, this is an unusual post.
| 
| Autogenerating the build file for a user has nothing to do with cents.
| I don't see how "poor" documentation on cents has to do with the cents
| themselves.
You must've missed the goal about leaving the user's build file alone 
then. Here it is again: 
" Allow user to keep their build file the way they want "

| > - Cents don't have an autogenerated init target(?)
| They don't need it.
They would to run in maven.

| > - There is no common delegator file in Centipede(?)
| 
| There is.
| It's just that we don't like to call simple build files "delegators" 
just to
| give them a cool name.
Nice ad hominem attack. At least I know more than I did before. 

| You didn't mention other things that cents do:
| "
| > - Plugins are jars with the following contents: plugin.properties,
| > plugin-build.xml, plugin-delegators.xml
| "
| Apart from the delegators, cents do this.
Let's see. We have a build system. It uses properties and build files. It 
provides extensions. There's not too many more ways to do it. We'd looked 
at other options before this and came up with dead ends.

| "
| > - User downloads plugins and copies them to ${maven.home}/plugins
| "
| Cents users can do this, or have them downloaded automatically.
User's can download files without Maven or Centipede.

| "
| > - The user can tell maven about the plugins by doing: ant
| > maven:install-plugins
| >     - This process: 1) scans the plugins directory comparing jars to
| > directories, ala Tomcat with WARs and webapps
| >     -               2) unzips any 'new' plugins
| >     -               3) runs a task to parse the init target and 
produce
| > the callbacks
| >     -             4) runs a task to regenerate a proposed new file -
| > delegators.xml with all targets that may be
| >                        delegated to in all available plugins and 'core
| > maven'
| "
| On the Centipede site, it's stated that they behave like .war files.
| And the automatic delegation is done by a special cent.
Is this the 'evil' automagic cent that everyone wants to get rid of?

| > > We offered to merge efforts in a single new project in a discussion 
at
| > > Jakarta General, but some developers simply said no.
| > > Is this "copying" what you want to do?
| > > We have integrated Maven documentation generation in Centipede since 
our
| > > last beta, and give you due credit.
| > The extent of your documentation on maven in Centipede at
| http://krysalis.sourceforge.net/centipede/centipede/maven-cent.html is
| > vast. As a maven developer, it stuns me that's all you can come up 
with.
| > Not even a single link to the maven site.
| 
| It's in alpha stage.
No. It's in beta stage. Your latest release is 1.0 beta 2, right.


| It's called maven.cent. We didn't change classnames like you are doing 
with
| all the code that Maven is gobbling up.
| No other cent has more documentation for now.
And there's the rub.

| > And if I remember correctly, I'm the one that started the discussion 
on
| > the krysalis list. It didn't get far, though.
| 
| Why? I did reply, I showed you how, I also put Maven parts in Centipede 
to
| show you a possible way.
That's not merging. That's copying a small piece. Aren't you peeved about 
that already?

| Guess why it failed.
Lack of interest from what I can tell.

| > > You are free to do it, but I just wanted to tell the Maven community
| > what is happening.
| > And me posting to the dev list is hiding it somehow?
| 
| Did I see "Centipede" in the posting?
| No.
That's because it's not a Cent, or Centipede. It's the equivalent thing 
for Maven. I don't expect you to post your webapp cent and call it Maven.

| > I've tried to read your documentation, and understand how things work. 
You
| > make it too hard. I told you that 2 months ago, and now you're 
starting to
| > document stuff?
| 
| Do I need to apologise?
No. Just fix your documentation if you expect people to work with your 
tools.

| This is getting ridiculous.
I agree. Posting off-topic to a maven developers list about centipede is 
ridiculous.

| > According to the forest developers (which Centipede uses) "Forrest 
isn't
| > ready for prime time yet,". There's no site, no docs and hence I've 
gotten
| > nowhere with it. Since that's your documentation system (something I'm
| > interested in), I thought that would be a good place.
| 
| Keep trying.
Why? I've been told by the forrest developers to wait.

| I had a terrible time integrating the Maven documentation system, which 
has
| no documentation on how it works.
You might've asked someone who knows. That would be collaboration...

[snip]
| If we were converging, the post would have been about using cents and
| enhancing them so they fit both projects.
Why would I post about something I can even get built?

| Anyway, as I said, you can do as you wish.
| I just wanted to tell you all that Centipede already has most of this
| functionality.
And I just wanted to say I can't use it and couldn't tell if it did.

| That's all.
| 
| Have a nice day.
Thanks, you too.
 
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to