Wendy Smoak wrote:
I had problems today finding some documentation on the war plugin.
Pretty standard stuff but I couldn't even find the plugins documentation
start page in the left-hand menu, rather I found it on the home page
(where I happened NOT to be to start with) in the text. I think this
Wendy Smoak wrote:
On 11/16/06, Adam Hardy
Secondly the comments functionality or the link to the wiki is a pretty
urgent requirement for me, and I think I'm a typical user.
Where are you looking to add comments? Honestly I don't think we're
going to get a 'comment mechanism' on the existing
Just wanted to dredge up this old thread concerning documentation to
find out what status it has now after the last conversation.
I had problems today finding some documentation on the war plugin.
Pretty standard stuff but I couldn't even find the plugins documentation
start page in the
On 11/16/06, Adam Hardy
[EMAIL PROTECTED]://mail.google.com/mail/ wrote:
Just wanted to dredge up this old thread concerning documentation to
find out what status it has now after the last conversation.
I think this was already in the works when this thread started, but
the plugins and guides
Wendy Smoak wrote:
Any thoughts on what a menu link on each plugin site might be called?
For example, I'm planning to link Maven Javadoc Plugin
http://maven.apache.org/plugins/maven-javadoc-plugin
to its wiki page
http://docs.codehaus.org/display/MAVENUSER/Javadoc+Plugin
Just Wiki seems
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.
OK. I like this, too, but there's already the mechanism for doing this in
the form of documentation for the individual components.
Specifically, the how to use sections of most of the plugins, which are a
huge portion of the how to maven world, are weak. However, since it
requires the
On 10/31/06, Jeff Mutonho [EMAIL PROTECTED] wrote:
documents say.That led me to http://maven.apache.org/wagon/ and
clicking on the Getting Started link I ended up at the URL
http://maven.apache.org/wagon/guides/getting-started/index.html , and
almost every link there leads to a :
Good day to you all, fellow Maven Users,
I agree that right now, maven documentation is scattered. We have the apache
maven site ([1]), the docus you can build with the source code (checkout the
source and do mvn site [2]...and btw, the maven site can be checked out as
well [3]), the mailing
Excellent thoughts! I want to adopt maven2 and in-fact we are debating the
issue at work. And the cons are the lack of documentation and the fact that
ANT is easier to customize. And, that's what we all do, customize
everything to support our needs.
I WIKI everything and I wish I had a public
David Whitehurst wrote:
Excellent thoughts! I want to adopt maven2 and in-fact we are debating the
issue at work. And the cons are the lack of documentation and the fact
that
ANT is easier to customize. And, that's what we all do, customize
everything to support our needs.
I WIKI
Onderwerp: Re: Maven rant
Why not use the central repo for documentation aswell?
E.g. in
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/maven-ant-plugin/2.0-alpha-2/
could exist a bundle named user-manual.zip, containing the sources for the
user-manual. There could be a reference
Why not use the central repo for documentation aswell?
E.g. in
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/maven-ant-plugin/2.0-alpha-2/
could exist a bundle named user-manual.zip, containing the sources for
the user-manual. There could be a reference-manual.zip, a
-Oorspronkelijk bericht-
Van: Gisbert Amm [mailto:[EMAIL PROTECTED]
Verzonden: vrijdag 3 november 2006 9:43
Aan: Maven Users List
Onderwerp: Re: Maven rant
Why not use the central repo for documentation aswell?
E.g. in
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/maven-ant-plugin/2.0
be a no cost
operation, and having a predefined structure may help to achieve this goal.
Sebastien
-Original Message-
From: Sebastien Arbogast [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 31, 2006 2:45 PM
To: Maven Users List
Subject: Re: Maven rant
2 thoughts about what you wrote
-Original Message-
From: Sebastien Brunot [mailto:[EMAIL PROTECTED]
Sent: jeudi 2 novembre 2006 10:26
To: Maven Users List
Subject: RE: Maven rant
I'm just joining, but what about creating a wiki with the entire free
maven book content so that the (user) community can update
.
Sebastien
-Original Message-
From: Sebastien Arbogast [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 31, 2006 2:45 PM
To: Maven Users List
Subject: Re: Maven rant
2 thoughts about what you wrote Vincent:
I totally agree on the fact that a few people have to write the core of the
documentation
PROTECTED]
Sent: Thursday, November 02, 2006 10:31 AM
To: Maven Users List
Subject: Re: Maven rant
But you won't solve the main issue of a wiki system: information replacement.
I still think that a comment system would be more reliable on the long term.
2006/11/2, Sebastien Brunot [EMAIL PROTECTED]:
I'm
Wendy Smoak wrote:
On 10/31/06, Sebastien Arbogast [EMAIL PROTECTED] wrote:
Think of Hibernate or PHP documentation: one base reference book with
DYNAMIC comments in which people can share their thoughts and
experiences about each feature/chapter, remarks that can be later
integrated when the
Good ! When do you think it would be possible to have it online ?
Sebastien
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 11:44 AM
To: Maven Users List
Subject: Re: Maven rant
Wendy Smoak wrote:
On 10/31/06, Sebastien Arbogast [EMAIL
On 11/2/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
Good ! When do you think it would be possible to have it online ?
Have what online? We need to decide what it is first. :)
What we have available is all of Maven's documentation, (some of which
is generated, some is in APT format,) and
What I'd like to do for comments is make use of the MAVENUSER wiki
[1]. I'd like to see a link on every plugin site so that users can
share configuration examples or tell us that something is just plain
wrong.
+1 to that
What I meant by it was the comment mechanism.
Sebastien
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 3:35 PM
To: Maven Users List
Subject: Re: Maven rant
On 11/2/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
Good ! When do you
My $0.02:
First of all, lets note that I make most of my livelihood working on maven
builds, so this is not (repeat NOT) criticism of the product, developers, or
community at large.
The maven users list (and the associted developers lists and users lists for
all the OTHER
On 11/2/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
What I meant by it was the comment mechanism.
Right... it doesn't exist yet, we need to design it.
Earlier, I asked, Any ideas on how to present that as an option?
What would the menu link be called? How should the pages on the wiki
be
On 11/2/06, Mykel Alvis [EMAIL PROTECTED] wrote:
Like it or not,
people read a lot of wikis, but rarely write to them. They WILL, however,
provide their comments from the peanut gallery on a mailing list.
I'm currently looking at 1212 unread messages in my inbox from this list.
That's from
Wendy Smoak on 02/11/06 22:34, wrote:
On 11/2/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
What I meant by it was the comment mechanism.
Right... it doesn't exist yet, we need to design it.
The comment mechanism can be a wiki where the public can only add at the bottom
of the page, and
The problem, as I see it, is that the documentation is fragmented. Unlike
Hibernate and Spring, which provide a single reference manual which is kept
up to date with every release, Maven documentation is spread all over the
place (wiki, generated sites, better builds with Maven, etc.). The
Ok, this is think outside the box time... I like Thomas' comments on
centralizing documentation. I really, really like Thomas' comments on
centralizing documentation. However, I think the logistics may be
off. I'm thinking of the documentation problem as similar to the
build problem.
Before
Hello Jeff,
I think it's really a trouble.
But all will be OK, I'm sure of that.
Best Regards.
a cup of Java, cheers!
Sha Jiang
Jeff Mutonho wrote:
Is maven in the process of unintentionally killing itself due to poor
support and documentation?I may be wrong but I strongly feel that the
Jeff,
I use maven and I really like it and I don't want this to sound like
negative criticism but you are right, the learning curve for maven newbie’s
is huge and there just isn't much good docs available. I have wound up
getting bits of pieces of info from here and there...it just takes so
-Original Message-
From: Sebastien Arbogast [mailto:[EMAIL PROTECTED]
Sent: mardi 31 octobre 2006 14:18
To: Maven Users List
Subject: Re: Maven rant
I totally agree but I think that the problem is very difficult to
solve, especially with all the incredible amount
I think your right; I understand it's a hard problem to solve. That's way
I'm not negative on maven; I just think it's a big issue that needs
attention. The people that know this stuff, the developers that write maven
probably aren't great documentation people or if they are just don't have
the
the scenes.
IMHO, Maven documentation should look like that: http://drupal.org/handbooks
2006/10/31, Vincent Massol [EMAIL PROTECTED]:
-Original Message-
From: Sebastien Arbogast [mailto:[EMAIL PROTECTED]
Sent: mardi 31 octobre 2006 14:18
To: Maven Users List
Subject: Re: Maven rant
On 10/31/06, Vincent Massol [EMAIL PROTECTED] wrote:
BTW
there's already a Maven wiki which is opened to anyone interested. It's been
there for more than a year but I wouldn't call the result comprehensive
documentation.
Thanks
-Vincent
I'm sure there are many people who might want to
On 10/31/06, Sebastien Arbogast [EMAIL PROTECTED] wrote:
Think of Hibernate or PHP documentation: one base reference book with
DYNAMIC comments in which people can share their thoughts and
experiences about each feature/chapter, remarks that can be later
integrated when the reference is
The Documentation Check (DOCCK) plugin was recently created to help
address this very issue. It will help not only Maven but also its
plugins and even other projects/plugins using Maven.
Maven Dev has established a baseline for expected documentation and
will now use this plugin to enforce that
Wayne Fay [EMAIL PROTECTED] writes:
The Documentation Check (DOCCK) plugin was recently created to help
address this very issue. It will help not only Maven but also its
plugins and even other projects/plugins using Maven.
Hello to all,
And first great thanks to all maven developers and
38 matches
Mail list logo
