On 11/5/06, David Whitehurst <[EMAIL PROTECTED]> wrote:
I WIKI everything and I wish I had a public WIKI to write in that I felt comfortable that would stay there for all to see and wouldn't change.
That's not really the nature of wikis... people will come along and edit what you've written. In Maven's case, sometimes things get moved from the wiki into the "official" documentation, especially plugin configuration examples. http://docs.codehaus.org/display/MAVENUSER/Home
I'm new here, but this is like going to church and the message is always "this is how we do things here". It's a community or gathering and if it's not comfortable to speak up and say I have something to say, then it's not a public thing.
I'm not really sure what you mean here. There's a lot of 'convention over configuration' in Maven, so there *is* a lot of "this is how we do things here". Source code goes in src/main/java, test code in src/main/test. Yes, you _can_ put it elsewhere if you insist, but we're not necessarily going to agree that it's a good idea.
I agree with you because it's not easy to figure out how to get involved. Also, a portion or area of the server was out yesterday beause of a bug and it was very difficult for me to determine if this was a ditched effort or that someone was keeping the public away from something until a problem was fixed.
Now I'm really confused. What happened? If a server was down, there's more than likely a fairly mundane reason for it.
So when the WIKI opens up for assistance, let me know because I'm ready to share my notes. E.g. once I find out how to build plugins and debug them easily, I'll document everything. And, do I keep this for myself or does the community want my notes?
Dennis already pointed out the MAVENUSER space, where everyone is welcome to contribute: http://docs.codehaus.org/display/MAVENUSER/Home -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
