Dennis Lundberg [EMAIL PROTECTED]:
Steinar Bang wrote:
Two things have locked us to 2.0.4:
- a bug in maven proper (I think) where maven will ungzip a tar.gz
or tgz file it downloads, before dropping it in the local maven
repo, still with the same name, which breaks when an attempt is
Dennis Lundberg [EMAIL PROTECTED]:
Thanks for your input Steinar.
But this isn't at all helpful. Because is to vague. In order for us
(the Maven devs) to fix things we need you (the Maven users) to let us
know *exactly* what is wrong. Please give us concrete examples, then
we can fix them.
Steinar Bang wrote:
Dennis Lundberg [EMAIL PROTECTED]:
Thanks for your input Steinar.
But this isn't at all helpful. Because is to vague. In order for us
(the Maven devs) to fix things we need you (the Maven users) to let us
know *exactly* what is wrong. Please give us concrete examples,
On 9/30/07, Steinar Bang [EMAIL PROTECTED] wrote:
Well, the plugin that had documentation preceeding the currently
released plugin was maven-dependency-plugin a way back. I was trying
to use the analysis goal, which the documentation showed but the
plugin didn't have. And also there were
Dennis Lundberg schrieb:
[...]
Well, the plugin that had documentation preceeding the currently
released plugin was maven-dependency-plugin a way back. I was trying
to use the analysis goal, which the documentation showed but the
plugin didn't have. And also there were some exclude* parameters
Tim Kettler wrote:
Dennis Lundberg schrieb:
[...]
Well, the plugin that had documentation preceeding the currently
released plugin was maven-dependency-plugin a way back. I was trying
to use the analysis goal, which the documentation showed but the
plugin didn't have. And also there were some
On 9/28/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Lee Meador wrote:
That sounds as easy as herding cats. Trying to get all the people on the
user list to NOT do anything is unlikely.
The fact is, as I see it, its easier to just give a quick answers to
questions that strike my fancy
Lally Singh wrote:
On 9/28/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Lee Meador wrote:
That sounds as easy as herding cats. Trying to get all the people on the
user list to NOT do anything is unlikely.
The fact is, as I see it, its easier to just give a quick answers to
questions that
The standard for how we document the plugins within the Maven project
can be found here:
http://maven.apache.org/guides/development/guide-plugin-documentation.html
It has been a long way and a lot of work to get this in place for all
our plugins. The purpose of the standard was to document
Lally Singh wrote:
On 9/26/07, Wendy Smoak [EMAIL PROTECTED] wrote:
(There *is* a doc standard that they have to pass prior to being
promoted from the sandbox and released. Does it need to be changed?)
YES.
Right now the docs tend to look 100% autogenerated and be 0% useful.
Well, that's
Lee Meador wrote:
That sounds as easy as herding cats. Trying to get all the people on the
user list to NOT do anything is unlikely.
The fact is, as I see it, its easier to just give a quick answers to
questions that strike my fancy than it is to hunt it down in the docs and
point them to it.
Steinar Bang wrote:
Denis Bessmertniy [EMAIL PROTECTED]:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
Here are the problems I have had:
- unclear where maven ends
What about not answering any questions on the mailinglist anymore, but only
point to existing documentation. If there is no suitable docs for the
question, put in a JIRA issue. That should improve the docs fast!
regards,
Wim
2007/9/27, Wayne Fay [EMAIL PROTECTED]:
On 9/26/07, Tomasz Pik
Denis Bessmertniy wrote:
Now I recall words from one of our team member: I my last project we
started to use maven and then we refused to use it because it was hard. Then
we started to use Ant, and that is ok.
The problem with ant is that it lets you do anything, and that is its
key
On 9/27/07, Wayne Fay [EMAIL PROTECTED] wrote:
On 9/26/07, Tomasz Pik [EMAIL PROTECTED] wrote:
Example - please, try to find out how to skip executing of tests
during build starting from http://maven.apache.org
OK, I'll bite...
starting at http://maven.apache.org
on the left, click on
2007/9/27, Lally Singh [EMAIL PROTECTED]:
If you have to use google to search a website, the navigation is broken.
Partially true: information should be easily available both through search
engines and navigation links (it's Jakob Nielsen opinion, and mine obviously
:-) )
Antonio
On 9/27/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
2007/9/27, Lally Singh [EMAIL PROTECTED]:
If you have to use google to search a website, the navigation is broken.
Partially true: information should be easily available both through search
engines and navigation links (it's Jakob
rant
How about you pay me and i'll do it... I don't get people who bitch and
complain about stuff that really works if you can be arsed to actually try to
figure it out. People have done all this work mostly for free... the least
you could do is write a little bit of documentation where you
Ok, enough complaining out of me. If I could change all the files
directly, I would. But, here are what I think would really help ASAP.
1. The front-page link to the 'Users Center' should instead point to
the Maven Documentation Index
http://maven.apache.org/guides/index.html. It's really the
On Thu, September 27, 2007 12:29 pm, Michael McCallum wrote:
rant
How about you pay me and i'll do it... I don't get people who bitch and
complain about stuff that really works if you can be arsed to actually try
to
figure it out. People have done all this work mostly for free... the least
2007/9/27, Graham Leggett [EMAIL PROTECTED]:
The idea that it's free, what do you expect? quality? undermines
confidence in both maven and open source in general, and this doesn't do
the maven project any favours at all.
Well in fact I think open source software has a higher level of
If everyone that posted an email on this thread actually wrote a Wiki
article with a single paragraph, Maven would already be easier.
Regards,
Rodrigo
On 9/27/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
2007/9/27, Graham Leggett [EMAIL PROTECTED]:
The idea that it's free, what do you
On Thu, September 27, 2007 12:59 pm, Rodrigo Madera wrote:
If everyone that posted an email on this thread actually wrote a Wiki
article with a single paragraph, Maven would already be easier.
No no no no.
The problem is not the _quantity_ of the documentation, but the _quality_
of the
Lally Singh [EMAIL PROTECTED] writes:
On 9/27/07, Wayne Fay [EMAIL PROTECTED] wrote:
On 9/26/07, Tomasz Pik [EMAIL PROTECTED] wrote:
Example - please, try to find out how to skip executing of tests
during build starting from http://maven.apache.org
ot
Answer is: you never ever skip
On 9/27/07, Insitu [EMAIL PROTECTED] wrote:
Lally Singh [EMAIL PROTECTED] writes:
On 9/27/07, Wayne Fay [EMAIL PROTECTED] wrote:
On 9/26/07, Tomasz Pik [EMAIL PROTECTED] wrote:
Example - please, try to find out how to skip executing of tests
during build starting from
On 9/27/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
2007/9/27, Graham Leggett [EMAIL PROTECTED]:
The idea that it's free, what do you expect? quality? undermines
confidence in both maven and open source in general, and this doesn't do
the maven project any favours at all.
Well in
I would like to suggest better cross linking between the maven documents
and the wiki. It is very hard for most users to modify the official
maven documentation. If each plugin and main maven document had a
reference to a sister wiki page then it would be easier for users to add
their own two
On 9/27/07, Graham Leggett [EMAIL PROTECTED] wrote:
This thread has highlighted the fact that the documentation doesn't help
new users of maven, or users of maven who have no desire to become
experts. Just dumping yet more documentation on this group of people isn't
going to answer their
This thread has highlighted the fact that the documentation doesn't
help new users of maven, or users of maven who have no desire to
become experts. Just dumping yet more documentation on this
group of
people isn't going to answer their questions.
There are some questions that
That sounds as easy as herding cats. Trying to get all the people on the
user list to NOT do anything is unlikely.
The fact is, as I see it, its easier to just give a quick answers to
questions that strike my fancy than it is to hunt it down in the docs and
point them to it. That allows me to
How can you help people who ask this question (and others
like it)? I agree that _more_ documentation is not
necessarily the magic bullet that many believe it is.
The argument that some people don't read documentation so there is no
point in writing any more is a non-sequitor. Please
Andy,
You said, My *personal* opinion about why *I* find maven so hard is the
complete
mental disconnect between the lifecycle phase (task) and the
configuration, coupled with the voodoo of 'convention'.
I think thats an amazingly concise description of what is hard about Maven.
I do think the
. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 11:51 PM
To: Maven Users List
Subject: RE: Why Maven is Hard?
There is a newer book available at http://sonatype.com/book
(no registration required and it's html so you can just hop
in and out as
needed
is using any snapshots.
-Original Message-
From: Lally Singh [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 27, 2007 6:34 AM
To: Maven Users List
Subject: Re: Why Maven is Hard?
Ok, enough complaining out of me. If I could change all the files
directly, I would. But, here are what I
Here are some random thoughts.
What would happen if mvn help printed out
.
mvn faq plugin - faq for the plugin
mvn myfaq - your personal faq (creates a personal site/maven-faq.xml )
mvn faqreport - reports something that you think should be an faq
mvn faqreport would
Hi Elizabeth,
Please use the http://docs.codehaus.org/display/MAVENUSER/ wiki pages.
Raphaël
2007/9/26, Sommers, Elizabeth [EMAIL PROTECTED]:
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
What I want is an active mailing list for plugin developers. I have
not
express it well.
Making Maven easier to diagnose is probably a worthwhile effort.
-- Gael
-Original Message-
From: Kevin Jackson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 7:50 AM
To: Maven Users List
Subject: Re: Why Maven is Hard?
In my opinion, those that have
Another thing that is hard in Maven is solving classpath issues.
Classpath issues can be hard to solve in java but in Maven it is even harder
because your plugin inherits from a classpath built by maven from your
dependencies and others as well.
So when something fails, you must understand who
mvn -X
what more can you ask for?
mvn dependency:resolve
mvn help:effective-pom
On Thursday 27 September 2007 00:28, Marziou, Gael wrote:
Another thing that is hard in Maven is solving classpath issues.
Classpath issues can be hard to solve in java but in Maven it is even
harder because
I have to agree with the comments in this thread.
Asking someone to contribute documentation for a plugin they didn't
write is pretty lame. How about not letting someone submit a plugin
until not only has the code been tested/proven, but the associated
documentation is up to snuff? I don't know
, September 26, 2007 9:20 AM
To: Maven Users List
Subject: Re: Why Maven is Hard?
mvn -X
what more can you ask for?
mvn dependency:resolve
mvn help:effective-pom
On Thursday 27 September 2007 00:28, Marziou, Gael wrote:
Another thing that is hard in Maven is solving classpath issues.
Classpath issues
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
What I want is an active mailing list for plugin developers. I have
written too many plugins with less than stellar testing harnesses and
tools. The developers' mailing list is not the right place to discuss
plugins.
I
I think you expressed things very well. Maven is great for fairly
trivial projects, but once you have a complicated build or deployment
requirement, it is very hard to find out whether or how you can meet
your requirements. And many of the existing plugins are indeed poorly
documented.
Our most
I highly recommend: Better Builds with Maven
(http://www.devzuz.com/web/guest/products/resources#BBWM)
On 9/24/07, Denis Bessmertniy [EMAIL PROTECTED]
wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much
PROTECTED] wrote:
I highly recommend: Better Builds with Maven
(http://www.devzuz.com/web/guest/products/resources#BBWM)
On 9/24/07, Denis Bessmertniy [EMAIL PROTECTED]
wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I
On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
As I recommended earlier, I think we should copy and paste the Better Builds
with Maven book into the official Maven documentation.
Why not?
The book is already free. (Yes, you have to register.) There's
another very good book at
Thinking about it, it seems like the mojo-dev list would be the
right place for Maven plugin development discussion. Its just not
very high traffic at this point.
Probably if you joined and started posting questions etc, we could
turn it into the mailing list we want/need with active
September 2007 16:38
To: Maven Users List
Subject: Re: Why Maven is Hard?
Thinking about it, it seems like the mojo-dev list would be the
right place for Maven plugin development discussion. Its just not
very high traffic at this point.
Probably if you joined and started posting questions etc, we
To: Maven Users List
Subject: RE: Why Maven is Hard?
I have to agree with the comments in this thread.
Asking someone to contribute documentation for a plugin they didn't
write is pretty lame. How about not letting someone submit a plugin
until not only has the code been tested/proven
everything better but surely it will help new people like
me!
Richard
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: 26 September 2007 16:05
To: Maven Users List
Subject: Re: Why Maven is Hard?
On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
As I recommended
!
Richard
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: 26 September 2007 16:05
To: Maven Users List
Subject: Re: Why Maven is Hard?
On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
As I recommended earlier, I think we should copy and paste the Better
Builds
-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: 26 September 2007 16:05
To: Maven Users List
Subject: Re: Why Maven is Hard?
On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
As I recommended earlier, I think we should copy and paste the Better
Builds
with Maven book
On 9/26/07, Wendy Smoak [EMAIL PROTECTED] wrote:
(There *is* a doc standard that they have to pass prior to being
promoted from the sandbox and released. Does it need to be changed?)
YES.
Right now the docs tend to look 100% autogenerated and be 0% useful.
It's tough to find the useful
Denis Bessmertniy [EMAIL PROTECTED]:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
Here are the problems I have had:
- unclear where maven ends and plugins take over
Lally Singh schrieb:
[...]
That'd be nice. Even before hearing back from the respective authors,
HOW ABOUT LINKING TO THEM I don't mind registering. I mind
finding out about the book randomly from the mailing list or google.
Just open the maven website and click on
The user center.
Sorry, didn't mean to be so harsh about it. But when I see 5 tiny
links on the user center, I see that there isn't much documentation on
the site. I stop looking on the site for anything else -- I hit
google.
On 9/26/07, Tim Kettler [EMAIL PROTECTED] wrote:
Lally Singh
: RE: Why Maven is Hard?
It seems very odd to me that the Maven book *isn't* on the maven site:
the place I would go to look for documentation. Why put another hurdle
of going elsewhere and registering? I registered had to wait a few hours
to get the email, it seemed a bit ridiculous. I agree
On 9/26/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
As I recommended earlier, I think we should copy and paste the Better Builds
with Maven book into the official Maven documentation.
Why not?
The book is already free. (Yes, you have to
On 9/26/07, Tomasz Pik [EMAIL PROTECTED] wrote:
Example - please, try to find out how to skip executing of tests
during build starting from http://maven.apache.org
OK, I'll bite...
starting at http://maven.apache.org
on the left, click on Wiki
scroll down to Children, click on FAQs, see its not
Dennis Lundberg wrote:
Don't let the fact that you're not a native English speaker stop you
from contributing to the documentation. I'm not a native English speaker
myself and started out here at the Maven project by improving the
documentation.
Reading your mails on this list, I can say
Gisbert Amm wrote:
O.k., I'll try it. I assume the current online docs are for the version
2.0.7 of Maven and I should create patches using that branch.
Just immediately after that posting I found out that the maintainance
branch obviously is maven-2.0.x
Never mind.
-Gisbert
--
Gisbert
Documentation is 100% the largest weakpoint of maven.
On 9/24/07, Steve Mactaggart [EMAIL PROTECTED] wrote:
Case in point
http://maven.apache.org/guides/mini/guide-multi-module.html
Something that is really useful, but still non existant.
Another datapoint: I've read both books, been using
To: Maven Users List
Subject: Re: Why Maven is Hard?
Documentation is 100% the largest weakpoint of maven.
On 9/24/07, Steve Mactaggart [EMAIL PROTECTED] wrote:
Case in point
http://maven.apache.org/guides/mini/guide-multi-module.html
Something that is really useful, but still non existant
I always find this [1] a good starting point for the internal lifecycle
and packaging workings of Maven.
Hth,
Nick Stolwijk
[1] http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html
In maven, so much of it is implicit (but un/under documented) that
it's tough to see what's
No it's not a catch 22. I will clarify what I was saying in my other
statement. People have exactly 2 choices when faced with a problem such as
documentation. The first one is to say, Boy this product is too hard for
me to learn and there isn't enough documentation, so I'll go find something
Thanks for the recommendation of this page,
I think before reading that I even don't understand what I was
asking to maven to let it work. :P
In the build lifecycle introduction on maven site, there's a table
which lists the phase - goal mapping for jar packaging, but that
table doesn't have
Maven docs are time consuming.
Now I recall words from one of our team member: I my last
project we started to use maven and then we refused to use it
because it was hard. Then we started to use Ant, and that is ok.
Maven has a steep learning curve, no doubt. However, once you've gotten
Exactly, I'll never turn back. I'll also mention again, I don't know who
uses netbeans, but I really find this Maven2 netbeans plugin to be
invaluable:
http://mevenide.codehaus.org/m2-site/
It has a lot of context sensitive input for the pom.xml, for dependencies
and treats a maven2 project as
One problem is that you only want to document some of the internal workings
of Maven. If you document it in too much detail, you lose the ability to
innovate and make it better. It's difficult, though, to find the correct
amount of detail to document.
-- Lee
On 9/25/07, Ryan Moquin [EMAIL
I also think that Maven is hard because it has not been endorsed by large
vendors like BEA.
BEA WebLogic comes with a set of ant tasks and conventions like the split
directory project structure.
There is a WebLogic plugin on codehaus that encapsulates these ant tasks but
using it is difficult
: Marziou, Gael [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 25, 2007 1:23 PM
To: Maven Users List
Subject: RE: Why Maven is Hard?
I also think that Maven is hard because it has not been endorsed by
large vendors like BEA.
BEA WebLogic comes with a set of ant tasks and conventions like
On 9/25/07, Brian E. Fox [EMAIL PROTECTED] wrote:
It's not an immediate help, but go back to your vendors and tell them
you want maven integration. I know many of them are working on it but
just like any product, customer demand can help drive it. I doubt the
big guys were first in line with
Hi,
I've been reading this thread with interest.
No it's not a catch 22. I will clarify what I was saying in my other
statement. People have exactly 2 choices when faced with a problem such as
documentation. The first one is to say, Boy this product is too hard for
me to learn and there
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
for some of the plugins is hard to
understand. But mostly, this are third party plugins, so the Maven team
can't do anything about it. You will have to mail the team of the plugin.
Hth,
Nick Stolwijk
Denis Bessmertniy wrote:
It is interesting why maven is so hard to understand? Why it is not well
the team of the plugin.
Hth,
Nick Stolwijk
Denis Bessmertniy wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example
is org.apache.maven.plugin.ear.EarModule[] here? How I may understand
what I need to pass?
Standard Maven plugins really bad documented.
-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 11:17 AM
To: Maven Users List
Subject: Re: Why Maven is Hard
Hi Denis,
Denis Bessmertniy wrote on Monday, September 24, 2007 10:07 AM:
It is interesting why maven is so hard to understand? Why it is not
well documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
Regading the EJBs there are quite a lot examples
Subject: Re: Why Maven is Hard?
What documentation did you read? There are two very good books about maven
2
(and they are free to download)
1. Maven the Definitive Guide (http://www.sonatype.com/book/) 2. Better
Builds with Maven
(http://www.devzuz.com/web/guest/products/resources#BBWM
PROTECTED]
Sent: Monday, September 24, 2007 11:50 AM
To: Maven Users List
Subject: Re: Why Maven is Hard?
Denis,
Will all due respect, do you really wish to just read a page and get running
and fully understanding Maven?
Do you really say Maven is hard because you didn't understand your very
first
Denis Bessmertniy wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
I am in the process of doing a handover of a fully mavenised build (all
the way through to using
a structure and tutorials that I
think we need to write.
Paul Keeble
- Original Message
From: Denis Bessmertniy [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Monday, 24 September, 2007 9:56:01 AM
Subject: RE: Why Maven is Hard?
I said that it is hard because
to this is: Because what I want to do is probably not
correct...
-Toni
Denis Bessmertniy wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example
To: Maven Users List
Subject: Re: Why Maven is Hard?
Denis,
Will all due respect, do you really wish to just read a page and get
running and fully understanding Maven?
Do you really say Maven is hard because you didn't understand your very
first plugin encounter, which happens
Easy to you but not for clietns.
Client is always right ;-)
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 1:04 PM
To: Maven Users List
Subject: Re: Why Maven is Hard?
with a few subtle exceptions related to bugs that are fixed
Michael McCallum wrote:
with a few subtle exceptions related to bugs that are fixed in 2.0.7 every
question i've been asked in regard to using maven2 has been found in the
documentation in under 5 minutes
That depends just how much of maven you are using. You might choose to
use maven to
:50 AM
To: Maven Users List
Subject: Re: Why Maven is Hard?
Denis,
Will all due respect, do you really wish to just read a page and get
running and fully understanding Maven?
Do you really say Maven is hard because you didn't understand your very
first plugin encounter, which happens
Michael McCallum wrote:
with a few subtle exceptions related to bugs that are fixed in 2.0.7 every
question i've been asked in regard to using maven2 has been found in the
documentation in under 5 minutes
That might be the case for the questions you came across. The mere
traffic on this list
Denis,
I get what you mean now and I agree...
I have spent hours with Maven debugging and I know what you feel.
It's been less than five hours since I had to download the source code of a
plugin to see what was going on inside of it... and got no results.
Fortunately, knowledgeable people
just to repeat i have been able to answer every question I have been asked
thats not to say every question but to say every question that in my
experience new users have asked... often they proceeded to go and do
something else anyway but thats beside the point...
modules are way overused IMO
I should also add that that does not include supporting 3rd party plugins...
and often getting the source for them can be useful... i have my own versions
of mojo hibernate, xslt among a few others while waiting for bug fixes...
thats like saying that micrsoft is responsible for the
Bessmertniy wrote:
It is interesting why maven is so hard to understand? Why it is not well
documented? (It is all my own opinions)
I haven't so much probmlems with Ant, for example.
I am in the process of doing a handover of a fully mavenised build (all
the way through to using
I'm really floored that this discussion is even happening. Here is why:
If people are build their core infrastructure around Maven to the point
where they feel like they should give the project developers a hard time due
to something as simple as documentation, don't you think then that it's
On Tuesday 25 September 2007 01:10, Ryan Moquin wrote:
If people are build their core infrastructure around Maven to the point
where they feel like they should give the project developers a hard time
due to something as simple as documentation, don't you think then that it's
time to
And having read the rest of your statement I do exactly the same with with 90+
artifacts culminating in 9 different aggregations == war, ear, compound jar
On Tuesday 25 September 2007 01:10, Ryan Moquin wrote:
I'm managing a full enterprise application with Maven 2, with MANY
subprojects
Isn't this sort of a catch-22?
People are saying I don't get maven, it's too complex.
Now it's time for them to give something back and document it?
How do you propose they do that? Start at the source and pore through
it to explain it? Saying that is sort of a cop-out, IMO.
I think that the
The Maven User wiki is a great place for users to begin contributing
in a meaningful way:
http://docs.codehaus.org/display/MAVENUSER/Home
Also, the wiki is a great place to look for help, documentation,
examples etc. If you're having trouble with finding things on the
Maven site, check out the
One of Maven's values is that it
does the heavy lifting for you.
(as it's literature describes.)
But that is also exactly the problem - because
it is sometimes hard to tell what is going
on. You need to keep the Maven cycle in
mind at all times - and that does add
another level of indirection.
Ryan Moquin wrote:
So you are saying that Maven IS hard because someone doesn't understand a
huge project that they've never used before?
Yes.
You are saying that if it was
done in ant it would be easier to understand?
Absolutely not. What on earth gave you that idea?
Regards,
Graham
--
the builder what is happening.
Regards,
John
-Original Message-
From: Bob Aiello [mailto:[EMAIL PROTECTED]
Sent: 24 September 2007 16:24
To: Maven Users List
Subject: RE: Why Maven is Hard?
One of Maven's values is that it
does the heavy lifting for you.
(as it's literature describes
1 - 100 of 107 matches
Mail list logo
