Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Maven Wiki" for change 
notification.

The following page has been changed by JeanMichelGarnier:
http://wiki.apache.org/maven/MavenDiscussionConventions

------------------------------------------------------------------------------
   * proyecto de webapp estandarde
   * Gestión de las dependencias
   * Refactorisación de los proyectos existentes
+  * Usar SNAPSHOT
  
  == Proyecto de servico estandarde ==
  http://maven.apache.org/reference/conventions.html
@@ -41, +42 @@

  +- .classpath   
  }}}
  
- .claspath 
- {{{#!xml
+ Eclipse .classpath 
+ {{{
  <?xml version="1.0" encoding="UTF-8"?>
  <classpath>
        <classpathentry kind="output" path="target/test-classes"/>
@@ -90, +91 @@

  +- maven.xml    
  +- .project     
  +- .classpath   
- .wtpmodules
+ +- .wtpmodules
  }}}
  
+ El Eclipse .classpath es parecido al anterior.
  
+ Eclipse .wtpmodules
+ {{{
+ <?xml version="1.0" encoding="UTF-8"?>
+ <project-modules id="moduleCoreId">
+   <wb-module deploy-name="${ECLIPSE_PROJECT_NAME}">
+     <module-type module-type-id="jst.web">
+       <version>
+         2.4
+       </version>
+       <property name="context-root" value="${ECLIPSE_PROJECT_NAME}"/>
+       <property name="java-output-path" value="/"/>
+     </module-type>
+     <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
+     <wb-resource deploy-path="/WEB-INF/classes" 
source-path="/src/main/resources/conf/log4j"/>
+     <wb-resource deploy-path="/WEB-INF/conf" 
source-path="/src/main/resources/conf"/>
+     <wb-resource deploy-path="/" source-path="/src/main/webapp"/>
+   </wb-module>
+ </project-modules>
+ }}}
  
- 
+ Como el fichero es diferente de aquello creado con Eclipse, se podría crear 
un Eclipse wizard para los proyectos openFrame (sugerencia! Sería mas rapido 
que leer 36 paginas de documentación?)
  
  === Refactorisación de los proyectos existentes ===
  
@@ -103, +124 @@

  
  Todos los proyectos heredan las propiedades definidas en el 
project.properties en openFrame-root.
  Podemos compartir las cosas siguientes:
- 1. Checkstyle 
(http://maven.apache.org/reference/plugins/checkstyle/index.html)
+  1. Checkstyle 
(http://maven.apache.org/reference/plugins/checkstyle/index.html)
- 2. PMD (http://pmd.sourceforge.net/index.html)
+  1. PMD (http://pmd.sourceforge.net/index.html)
- 3. Gestion de las dependencias
+  1. Gestion de las dependencias
  http://maven.apache.org/using/managing-dependencies.html
  
  === Codigo fuente del project.properties en openFrame-root  ===
+ {{{
+ ## Repositories
+ #______________
+ 
maven.repo.remote=http://www.ibiblio.org/maven/,http://www.opentrends.net/repository/
  
+ ## Multiproject configuration
+ #____________________________
+ maven.multiproject.basedir=${basedir}/../
+ maven.multiproject.includes=*/project.xml
+ maven.multiproject.includes=*/*/project.xml
+ maven.multiproject.excludes=openFrame-root/project.xml
+ maven.multiproject.type=jar
+ 
+ ## Compilation configuration
+ #___________________________
+ maven.compile.deprecation=on
+ maven.compile.encoding=ISO-8859-1
+ 
+ # Target 1.4 JVMs
+ maven.compile.target = 1.4
+ 
+ ## Junit configuration
+ #_____________________
+ # Make sure we fork JUnit so that we can use a different version of Ant than 
+ # the one provided by Maven.
+ maven.junit.fork = true
+ 
+ # Display junit execution details on screen
+ maven.junit.usefile = false
+ 
+ # Do not display junit test suite summary information
+ maven.junit.printSummary = false
+ 
+ # Print names of test cases as they execute
+ maven.junit.format = plain
+ 
+ ## WEBAPP standard source folder (This property will be used only in webapp 
projects)
+ #______________________
+ maven.war.src=${basedir}/src/main/webapp
+ 
+ ## Plugin configuration Uncomment as soon as we have agreed about a convention
+ #______________________
+ # Check Style (default: sun)
+ maven.checkstyle.format=sun
+ # maven.checkstyle.properties = ${basedir}/../openFrame-root/checkstyle.xml
+ # maven.checkstyle.fail.on.violation = true
+ 
+ # PMD configuration
+ # maven.pmd.cpd.enable = true
+ # maven.pmd.rulesetfiles = ${basedir}/../openFrame-root/pmd.xml
+ 
+ ## Depedencies VERSIONS
+ #______________________
+ # See http://maven.apache.org/using/managing-dependencies.html
+ # DRY (don´t repeat yourself): This is the one place which contains the 
versions of the jars!
+ #
+ # Within each project.xml dependencies definition, you have to reference the 
version property 
+ # as in the following snippet:
+ # <dependency>
+ #   <groupId>acegisecurity</groupId>
+ #     <artifactId>acegi-security</artifactId>
+ #     <version>${version.acegi}</version>
+ #     <type>jar</type>
+ # </dependency>  
+ 
+ # To be flexible and allow projects to use their own version (within their 
project.properties)
+ maven.jar.override = on
+ 
+ # VERSIONS
+ version.spring=1.2.5
+ version.acegi=0.8.3
+ 
+ # TO BE COMPLETED .... If the openFrame teams agrees with my suggestion!
+ 
+ }}}
+ 
+ === USAR SNAPSHOTS ===
+ 
+ Me parece que los servicios de openFrame van a cambiar cada día (o más). 
Sería más sencillo de usar los SNAPSHOT.
+ 
+ Texto extracto de la documentación de Maven 
(http://maven.apache.org/using/managing-dependencies.html):
+ 
+ In Maven versions containing the keyword SNAPSHOT are considered special. 
They approximate the latest development build of a project that has been 
deployed to the repository. If a project that you depend on is changing 
frequently you can state in your POM that you wish to try and keep up with that 
project by declaring it a SNAPSHOT dependency. So, for example, you may be 
trying to stay abreast of changes in Jelly so you might put the following in 
your POM:
+ 
+ <dependency>
+   <groupId>commons-jelly</groupId>
+   <artifactId>commons-jelly</artifactId>
+   <version>SNAPSHOT</version>
+ </dependency>
+ 
+ Assuming that project is publishing a version called SNAPSHOT (which happens 
when the jar:deploy-snapshot goal is called), then each time you build Maven 
will check the remote repository for changes in that JAR and download it again 
if a newer version is available.
+ 
+ If you are working offline Maven will warn you that your SNAPSHOT 
dependencies may be out of date. This is just a warning, and as the remote copy 
often does not change frequently can be ignored.
+ 
+ Note: the version need only contain the word SNAPSHOT - it does not need to 
equal it exactly. It is traditional to append it to a version to indicate 
"development towards version X". For example, 1.2-SNAPSHOT is the development 
version between 1.1 and 1.2. 
+ 

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

Reply via email to