You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Nathan Sowatskey (JIRA)" <ji...@apache.org> on 2006/07/17 15:06:14 UTC

[jira] Updated: (MUSE-43) Update Maven 2.0 build system in line with Maven best practices

     [ http://issues.apache.org/jira/browse/MUSE-43?page=all ]

Nathan Sowatskey updated MUSE-43:
---------------------------------

    Attachment: pom.xml

This is the original file before Daniel made some changes, so it is just for the record, as it were.

> Update Maven 2.0 build system in line with Maven best practices
> ---------------------------------------------------------------
>
>                 Key: MUSE-43
>                 URL: http://issues.apache.org/jira/browse/MUSE-43
>             Project: Muse
>          Issue Type: Improvement
>          Components: Build - Maven, Dependencies, and Optimizations
>    Affects Versions: 2.0.0 M1
>         Environment: Maven 2.0
>            Reporter: Nathan Sowatskey
>         Assigned To: Dan Jemiolo
>            Priority: Minor
>         Attachments: pom.xml
>
>
> Update poms for Maven 2.0 build and directory structure in line with Maven best practices.
> The typical structure for a maven 2 project is:
> src |
>      - main |
>             - java |
>                    - <org|com|...>
>             - resources |
>                         - xsd
>                         - wsdl
>      - test |
>             - java |
>                    - <org|com|...>
>             - resources |
>                         log4j.properties
>                         - xsd
>                         - wsdl
>                  site-> ...
> See http://maven.apache.org/guides/introduction/introduction-to-the- 
> standard-directory-layout.html for more details.
> The main advantage of adopting this standard layout is that the pom 
> files get smaller, as everything is where it is supposed to be by 
> default, and Maven will thus find it there by default, thus we don't 
> need to configure the locations of our files in the pom itself.
> There are also archetypes, especially EA ones, that are not yet 
> configurable, so will only work when everything is where it is 
> supposed to be by default.
> And, of course, anyone who knows Maven will know where to find stuff 
> in the project structure.
> Though I can see that it would be a bit of work, and a little 
> disruptive for a period, I'd suggest adopting this structure for Muse 
> as it will be advantageous in the medium to long term.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org