I like the idea of adding more structural information to the directory layout but all changes should be backward compatible because many projects already use maven and can not adapt a possible new structure without great effort.


In other words: The path to the different source directories (java, test, ...) should be configurable by properties :-)

Regards Juergen


Ben Walding wrote:


That's my preference also. And it also makes it look like you can have multiple build trees, yet not! Muahahaha... I demand more emails on the user list dammit!

Michal Maczka wrote:

I also think it is bit inconsistent.

But think that the most consistent approach is

/ basedir
    main
        java
        resources
        aspects
        conf
    test
       java
       test-resources
       ...


Michal


P.S.

I am not saying we should change anything ...




-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 3:23 PM
To: 'Maven Developers List'
Subject: RE: Why is the java source directory named "main" for plugins?






-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 19 June 2003 15:02
To: Maven Developers List
Subject: Re: Why is the java source directory named "main" for

plugins?


On Thu, 2003-06-19 at 06:32, Vincent Massol wrote:


Hi,

Why is the java source directory named "main" for plugins (instead

of


"java")?

/src/test /src/main

Seem to make more sense as a pattern as the testing code is also

'java'


code.

Ok, my comment wasn't about whether the name made more sense or not about consistency. At present we use src/java everywhere else and everyone I know who uses maven also uses this convention. In cvs we also src/java for Maven...

-Vincent





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



Reply via email to