On 2 February 2011 11:04, Ron Wheeler <
[hidden email]> wrote:
> On 02/02/2011 12:46 PM, Hilco Wijbenga wrote:
>> On 2 February 2011 08:50, Kenneth Litwak<
[hidden email]> wrote:
>>> Thanks for the links but actually I've read a bunch of stuff on Maven.
>>> Unfortunately, I've found diverse examples, mostly generic, and none that
>>> address the exact specifics of precisely, in every possible detail, the
>>> exact structure that one needs for a multi-module project and every _single_
>>> line in every file that Maven needs. If you can point me to a reference for
>>> that, I'll happily read it. I read the POM reference at the Maven site, for
>>> example, and didn't see any detailed, full-example-based discussion of what
>>> I'm trying to find out.
>>
>> I know it's a bit frustrating, you want to get things done but you
>> want to do it properly and that's slowing you down. You are really
>> going to have to read Maven by Example
>> (
http://www.sonatype.com/books.html). Try the examples and try to
>> understand the structure of a project (e.g. Java source files don't go
>> in src/main/webapp but in src/main/java). Start with a single project,
>> not a multi-project build. You need to understand the Maven lifecycle
>> and then have a look at the various plugins as they become relevant to
>> you (
http://maven.apache.org/plugins/index.html).
>>
>> For all its faults, Maven is incredibly well documented so take
>> advantage of that and read it. It shouldn't take you all that long.
>
> It really lacks a Best Practice guide that lays out exactly how to construct
> applications of different types in different situations.
> The difficulty is that the guys that really know Maven well (Apache team
> members and Sonotype guys) are so intimately involved in the product that
> they can give you 20 ways to get anything done but are not very focused on
> dictating Best Practices.
> They also know the code so well and are fluent in reading it that they
> forget that the rest of us are just trying to get going as quickly as
> possible and regard
> the Maven setup as a necessary tool but not anywhere near the top of the
> list of things that we have to consider to get our applications built.
Hear, hear! :-)
> The rest of us are so happy that we are getting things built but are not
> sure if we are doing it optimally.
>
> What you are asking for is exactly what is missing in the documentation.
> The books are helpful and there are a few but they all suffer from being a
> bit too "inside the beltway" and give way too many ways to do things.
I too would love to see such a Best Practices guide. There is too much
"you're not doing it the Maven Way" without any reference to what the
"Maven Way" *is*. :-)
But while I agree with you in general, in this particular case I
believe Maven by Example shows (in excruciating detail and with
examples) exactly what the OP wants to do (or seems to want to do).
---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]
Locked
