Re: svn commit: r535724 - in /maven/continuum/trunk/continuum-webapp/src/main: java/org/apache/maven/continuum/web/bean/ProjectGroupUserBean.java webapp/WEB-INF/jsp/projectGroupMembers.jsp
Did you update this particular commit with svn pe --revprop -r535724 svn:log ? On 09/05/2007, at 7:40 PM, Maria Odea Ching wrote: Ok, I'll take note of that Trygve Laugstøl wrote: [EMAIL PROTECTED] wrote: Author: oching Date: Sun May 6 20:34:07 2007 New Revision: 535724 URL: http://svn.apache.org/viewvc?view=revrev=535724 Log: CONTINUUM-1256 Applied patch submitted by Teodoro Cue Can you please include some information about what changed when committing stuff? It's annoying having to go through the patch and/ or read the issue for smaller stuff. [snip] -- Trygve !DSPAM:602,4641b305257069182317745!
Maven Diagram Maker
I will create this summer (as a Google Summer of Code participant - with Jason van Zyl as a mentor) a software system that will allow, during the build process of a project, to automatically generate diagrams of chosen aspects of the project. I would like to start community discussion about the details - to provide very useful tool. I know - the mail is very long, but decisions made now will be essential. So: *please read and constructive comment*. I would like to provide two components: a graphical editor and a Maven plug-in. 'The Graphical Editor will offer live (WYSIWYG) preparation of a graphical presentation of the project by setting such properties as: - Type and subset of data, we want to present, - What part of the data is to be presented, - The method of presenting of each type of diagram nodes (that is, what attributes of the item will be displayed), and the general 'style' of the presentation. I would like to provide UML-like design. - The general layout algorithm - The positions of selected locked nodes – which we want to put in a fixed area. All other nodes will be positioned automatically. The schema of the diagram created by the editor will be saved to an XML file. Additionally the editor may be used as a graphical browser (explorer) of chosen aspects of the project. The editor will use the Prefuse library (http://prefuse.org). The Maven Plug-in (maven-graph-plugin) – will be using the XML file prepared by the Graphical Editor and the current state of project to prepare images in various graphic formats (JPG, TIFF, PNG and others supported by the Sun JAI library (http://java.sun.com/javase/technologies/desktop/media/jai/). The plug-in will be able to prepare the HTML map tag for the picture too (to create an active area on web page containing the image). The resulting file will be ready to use in the next Maven phases by Doxia or other documenting tool. The maven-graph-plugin will cope with changes in the project made after generating the schema XML file. This means that if an object from the XML file is no longer exists in the project, it won't be visible in the picture. It also means that if the object is new, it will be placed in the picture (in a place calculated by the general layout strategy set in the XML file). Additionally the user will be warned about any discrepancies between the expected and actual data and problems with finding space for a new object. The diagram generation will not modify the XML file, but will only try to interpret it for the current situation. During Google Summer of Code time I wish I prepare two connectors (possibilities to visualize an aspect of project): - Dependencies diagram connector – to visualize the chosen project's subset of the dependencies (internal or external, up to a configured depth or/and included in a given scope). It will be also possible to exclude some dependencies from the diagram. - Class diagram – to visualize the inheritance and composition aspects of the class hierarchy. The information will be obtained by reflection. Of course the mechanism of the connectors will be universal enough to make the addition of a new aspect of a project as simple as possible. Why „Maven Diagram-Maker? There are no good, free tools to prepare diagrams – especially such that would automatically generate diagrams from the source code and project descriptors. On the other hand, good and up-to-date documentation is a very important part of software development process – particularly in the Open Source world, where documentation is critical to help many people work on projects. On the other hand, nobody likes preparing documents and diagrams. To make the matters worse, using standard one-time diagrammers helps only for a short period of time. In fast growing projects, the pictures become obsolete very quickly. They start to mislead. Therefore I think that adding possibility to generate actual up-to-date diagrams in the build process is a very important idea – and Maven is the perfect environment to do that. Java developers can nowadays use very good text documenting tools, such a JavaDoc and Doxia, but the lack of methods to prepare and incorporate actual visual information in the documents is a very serious shortcoming of those tools. Planned editor features The Graphical Editor will help the user create and edit the visualization schema XML file. The file will contain two types of information: - The dataSource section will describe which data will be presented, that is - how to acquire the information to present. The classes and attributes of connectors, which will extract the data from the project, will be given. No actual data will be stored in the XML file itself. -The view section will describe how to present data. In details it will contain: - Perspective (coordinates of the visible area in the picture) or the information that the whole diagram has to fit into the
RE: Project artifacts w/ scope == test
Put @requiresDependencyResolution test in your mojo declaration. -Original Message- From: Zak Jacobson [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 12:48 AM To: dev@maven.apache.org Subject: Project artifacts w/ scope == test Hi - I'm writing a plugin that executes a java app. It builds the classpath for the external app based on the dependencies specified in the pom. I'm having trouble building the classpath if dependencies have a scope of test because the artifact is not in the list of artifacts. It appears the test scoped artifacts are not available in project.getArtifacts() or project.getTestArtifacts(). The plugin's execution specifies the test phase. Is there a way to get the test scoped dependencies? The plugin also runs during the process-classes phase and I don't want the test scoped dependncies in that case. Is there a better or easier way to get the classpath needed for a project to be tested? The surefire plugin is getting it, but I can't see how (yet, I just started looking at that code). Thanks- Zak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tool to clean snapshots from the repo
Any idea of how to remove old artifact snapshot ? Can repositorytools be useful for that ? Thanks Damien Which goal specifically? I can only see: repositorytools:add-artifact repositorytools:add-plugin-group repositorytools:add-repository repositorytools:copy-artifact repositorytools:copy-repository repositorytools:deploy-bundle repositorytools:deploy-repository repositorytools:export-csv repositorytools:validate Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven 1.1 RC1
+1 Arnaud HERITIER wrote: Hi folks, The time has come to release maven 1.1 RC1. Since the beta 3 we fixed several issues [1] and particularly : - We fixed latest incompabilities that avoided maven 1.1 to read POM working with maven 1.0.X [MAVEN-1755]. The new parser is a little bit more strict, thus if a pom isn't read, it's because it doesn't respect the schema. - We changed the central repository to http://repo1.maven.org/maven/[MAVEN-1789] - We improved the windows installer and changed the LF [MAVEN-1812][MAVEN-1808] [2] - We updated 33 plugins [3][4] to fixed a lot of bugs and add some improvements. We are preparing the release note. You'll find the binaries in 1 hour here : http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20070508/ Vote closes in 72 hours. +1 from me. Arnaud [1] http://jira.codehaus.org/browse/MAVEN?report=com.atlassian.jira.plugin.system.project:roadmap-panel [2] http://maven.apache.org/maven-1.x/plugins/nsis/screenshots.html#Modern_UI_ScreenShots [3] http://jira.codehaus.org/browse/MAVEN-1769 [4] http://people.apache.org/~aheritier/staging-sites/m1-core/maven-1.x/plugins/bundledHistory.html .. Arnaud Heritier OCTO Technology [EMAIL PROTECTED] www.octo.com | blog.octo.com ... -- View this message in context: http://www.nabble.com/-vote--Release-maven-1.1-RC1-tf3712345s177.html#a10435134 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tool to clean snapshots from the repo
HI Damien, While there might be a more elegant method, we used a scheduled task to delete all snapshot builds that were older than 7 days. We typically build 10-20 snapshots a day for a given component. If you are interested in this method, I can point you to the script that does the cleaning. Evan On 5/11/07, Damien Lecan [EMAIL PROTECTED] wrote: Any idea of how to remove old artifact snapshot ? Can repositorytools be useful for that ? Thanks Damien Which goal specifically? I can only see: repositorytools:add-artifact repositorytools:add-plugin-group repositorytools:add-repository repositorytools:copy-artifact repositorytools:copy-repository repositorytools:deploy-bundle repositorytools:deploy-repository repositorytools:export-csv repositorytools:validate Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: little get together at Apachecon?
FYI. I'll be scribe to bring notes back to the list for further discussion / any decisions that need to be made. Begin forwarded message: From: Brett Porter [EMAIL PROTECTED] Date: 10 May 2007 3:14:58 PM To: [EMAIL PROTECTED] Subject: Re: little get together at Apachecon? Reply-To: [EMAIL PROTECTED] List-Id: repository.apache.org Message-Id: [EMAIL PROTECTED] On 08/05/2007, at 8:00 AM, Henri Yandell wrote: b) Anyone for a JavaOne catchup? I think Brett and Carlos are here at least. I've just spoken to Henri and arranged to meet tomorrow (Friday) at 1pm. If anyone else is available, it'd be great to have a quick meet up. Let's meet in the lobby of Moscone South and go and grab some lunch? Cheers, Brett
Re: little get together at Apachecon?
On 11 May 07, at 9:44 AM 11 May 07, Brett Porter wrote: FYI. I'll be scribe to bring notes back to the list for further discussion / any decisions that need to be made. Begin forwarded message: From: Brett Porter [EMAIL PROTECTED] Date: 10 May 2007 3:14:58 PM To: [EMAIL PROTECTED] Subject: Re: little get together at Apachecon? Reply-To: [EMAIL PROTECTED] List-Id: repository.apache.org Message-Id: [EMAIL PROTECTED] On 08/05/2007, at 8:00 AM, Henri Yandell wrote: b) Anyone for a JavaOne catchup? I think Brett and Carlos are here at least. I've just spoken to Henri and arranged to meet tomorrow (Friday) at 1pm. If anyone else is available, it'd be great to have a quick meet up. Let's meet in the lobby of Moscone South and go and grab some lunch? You guys just chatting about the Apache maven repository setup? Jason. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven 1.1 RC1
With 3 binding votes (Lukas, Stefan, and me) and 2 non-bindings (Jeff and JBlack), the vote passed. The thread : http://www.nabble.com/-vote--Release-maven-1.1-RC1-tf3712345s177.html I'm preparing the release. Arnaud On 11/05/07, jblack [EMAIL PROTECTED] wrote: +1 Arnaud HERITIER wrote: Hi folks, The time has come to release maven 1.1 RC1. Since the beta 3 we fixed several issues [1] and particularly : - We fixed latest incompabilities that avoided maven 1.1 to read POM working with maven 1.0.X [MAVEN-1755]. The new parser is a little bit more strict, thus if a pom isn't read, it's because it doesn't respect the schema. - We changed the central repository to http://repo1.maven.org/maven/[MAVEN-1789] - We improved the windows installer and changed the LF [MAVEN-1812][MAVEN-1808] [2] - We updated 33 plugins [3][4] to fixed a lot of bugs and add some improvements. We are preparing the release note. You'll find the binaries in 1 hour here : http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20070508/ Vote closes in 72 hours. +1 from me. Arnaud [1] http://jira.codehaus.org/browse/MAVEN?report=com.atlassian.jira.plugin.system.project:roadmap-panel [2] http://maven.apache.org/maven-1.x/plugins/nsis/screenshots.html#Modern_UI_ScreenShots [3] http://jira.codehaus.org/browse/MAVEN-1769 [4] http://people.apache.org/~aheritier/staging-sites/m1-core/maven-1.x/plugins/bundledHistory.html .. Arnaud Heritier OCTO Technology [EMAIL PROTECTED] www.octo.com | blog.octo.com ... -- View this message in context: http://www.nabble.com/-vote--Release-maven-1.1-RC1-tf3712345s177.html#a10435134 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ...
Re: Maven Diagram Maker
On 5/11/07, Piotr Tabor [EMAIL PROTECTED] wrote: I would like to provide two components: a graphical editor and a Maven plug-in. 'The Graphical Editor will offer live (WYSIWYG) preparation of a graphical presentation of the project by setting such properties as: - Type and subset of data, we want to present, - What part of the data is to be presented, - The method of presenting of each type of diagram nodes (that is, what attributes of the item will be displayed), and the general 'style' of the presentation. I would like to provide UML-like design. - The general layout algorithm - The positions of selected locked nodes – which we want to put in a fixed area. All other nodes will be positioned automatically. The schema of the diagram created by the editor will be saved to an XML file. Additionally the editor may be used as a graphical browser (explorer) of chosen aspects of the project. The editor will use the Prefuse library (http://prefuse.org). The Maven Plug-in (maven-graph-plugin) – will be using the XML file prepared by the Graphical Editor and the current state of project to prepare images in various graphic formats (JPG, TIFF, PNG and others supported by the Sun JAI library (http://java.sun.com/javase/technologies/desktop/media/jai/). The plug-in will be able to prepare the HTML map tag for the picture too (to create an active area on web page containing the image). The resulting file will be ready to use in the next Maven phases by Doxia or other documenting tool. Does this mean we can export the graph of dependencies in a UML format? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Diagram Maker
On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote: On 5/11/07, Piotr Tabor [EMAIL PROTECTED] wrote: I would like to provide two components: a graphical editor and a Maven plug-in. 'The Graphical Editor will offer live (WYSIWYG) preparation of a graphical presentation of the project by setting such properties as: - Type and subset of data, we want to present, - What part of the data is to be presented, - The method of presenting of each type of diagram nodes (that is, what attributes of the item will be displayed), and the general 'style' of the presentation. I would like to provide UML-like design. - The general layout algorithm - The positions of selected locked nodes – which we want to put in a fixed area. All other nodes will be positioned automatically. The schema of the diagram created by the editor will be saved to an XML file. Additionally the editor may be used as a graphical browser (explorer) of chosen aspects of the project. The editor will use the Prefuse library (http://prefuse.org). The Maven Plug-in (maven-graph-plugin) – will be using the XML file prepared by the Graphical Editor and the current state of project to prepare images in various graphic formats (JPG, TIFF, PNG and others supported by the Sun JAI library (http://java.sun.com/javase/technologies/desktop/media/jai/). The plug-in will be able to prepare the HTML map tag for the picture too (to create an active area on web page containing the image). The resulting file will be ready to use in the next Maven phases by Doxia or other documenting tool. Does this mean we can export the graph of dependencies in a UML format? It's not a priority, but I'm sure it could be done. It's just going to be a general graph model that can be attached to various sinks, or a sink model (for ui tools) so you can easily add it. IDE integration is the primary target. Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Diagram Maker
This is interesting. Might be a good idea to post these notes to the Wiki and keep the consolidated the discussion consolidated in one place. Rahul - Original Message - From: Piotr Tabor [EMAIL PROTECTED] To: Maven Developers List dev@maven.apache.org Sent: Friday, May 11, 2007 11:22 PM Subject: Maven Diagram Maker I will create this summer (as a Google Summer of Code participant - with Jason van Zyl as a mentor) a software system that will allow, during the build process of a project, to automatically generate diagrams of chosen aspects of the project. I would like to start community discussion about the details - to provide very useful tool. I know - the mail is very long, but decisions made now will be essential. So: *please read and constructive comment*. I would like to provide two components: a graphical editor and a Maven plug-in. 'The Graphical Editor will offer live (WYSIWYG) preparation of a graphical presentation of the project by setting such properties as: - Type and subset of data, we want to present, - What part of the data is to be presented, - The method of presenting of each type of diagram nodes (that is, what attributes of the item will be displayed), and the general 'style' of the presentation. I would like to provide UML-like design. - The general layout algorithm - The positions of selected locked nodes – which we want to put in a fixed area. All other nodes will be positioned automatically. The schema of the diagram created by the editor will be saved to an XML file. Additionally the editor may be used as a graphical browser (explorer) of chosen aspects of the project. The editor will use the Prefuse library (http://prefuse.org). The Maven Plug-in (maven-graph-plugin) – will be using the XML file prepared by the Graphical Editor and the current state of project to prepare images in various graphic formats (JPG, TIFF, PNG and others supported by the Sun JAI library (http://java.sun.com/javase/technologies/desktop/media/jai/). The plug-in will be able to prepare the HTML map tag for the picture too (to create an active area on web page containing the image). The resulting file will be ready to use in the next Maven phases by Doxia or other documenting tool. The maven-graph-plugin will cope with changes in the project made after generating the schema XML file. This means that if an object from the XML file is no longer exists in the project, it won't be visible in the picture. It also means that if the object is new, it will be placed in the picture (in a place calculated by the general layout strategy set in the XML file). Additionally the user will be warned about any discrepancies between the expected and actual data and problems with finding space for a new object. The diagram generation will not modify the XML file, but will only try to interpret it for the current situation. During Google Summer of Code time I wish I prepare two connectors (possibilities to visualize an aspect of project): - Dependencies diagram connector – to visualize the chosen project's subset of the dependencies (internal or external, up to a configured depth or/and included in a given scope). It will be also possible to exclude some dependencies from the diagram. - Class diagram – to visualize the inheritance and composition aspects of the class hierarchy. The information will be obtained by reflection. Of course the mechanism of the connectors will be universal enough to make the addition of a new aspect of a project as simple as possible. Why „Maven Diagram-Maker? There are no good, free tools to prepare diagrams – especially such that would automatically generate diagrams from the source code and project descriptors. On the other hand, good and up-to-date documentation is a very important part of software development process – particularly in the Open Source world, where documentation is critical to help many people work on projects. On the other hand, nobody likes preparing documents and diagrams. To make the matters worse, using standard one-time diagrammers helps only for a short period of time. In fast growing projects, the pictures become obsolete very quickly. They start to mislead. Therefore I think that adding possibility to generate actual up-to-date diagrams in the build process is a very important idea – and Maven is the perfect environment to do that. Java developers can nowadays use very good text documenting tools, such a JavaDoc and Doxia, but the lack of methods to prepare and incorporate actual visual information in the documents is a very serious shortcoming of those tools. Planned editor features The Graphical Editor will help the user create and edit the visualization schema XML file. The file will contain two types of information: - The dataSource section will describe which data will be presented, that is - how to acquire the information to present. The classes and attributes
Remote resources plugin for assemblies?
Is the remote resources plugin also intended for assemblies? I have it configured to include license/notice in all the jars, but I also need to get the files into the top level of the Archiva and Continuum .tar.gz distributions. Any advice? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Diagram Maker
I still think a summary in the wiki is the best place to start. This will get lost amidst the noise. Then I will go from there with a response. Thanks for putting the material together though, a great start. Jason. On 11 May 07, at 4:22 AM 11 May 07, Piotr Tabor wrote: I will create this summer (as a Google Summer of Code participant - with Jason van Zyl as a mentor) a software system that will allow, during the build process of a project, to automatically generate diagrams of chosen aspects of the project. I would like to start community discussion about the details - to provide very useful tool. I know - the mail is very long, but decisions made now will be essential. So: *please read and constructive comment*. I would like to provide two components: a graphical editor and a Maven plug-in. 'The Graphical Editor will offer live (WYSIWYG) preparation of a graphical presentation of the project by setting such properties as: - Type and subset of data, we want to present, - What part of the data is to be presented, - The method of presenting of each type of diagram nodes (that is, what attributes of the item will be displayed), and the general 'style' of the presentation. I would like to provide UML-like design. - The general layout algorithm - The positions of selected locked nodes – which we want to put in a fixed area. All other nodes will be positioned automatically. The schema of the diagram created by the editor will be saved to an XML file. Additionally the editor may be used as a graphical browser (explorer) of chosen aspects of the project. The editor will use the Prefuse library (http://prefuse.org). The Maven Plug-in (maven-graph-plugin) – will be using the XML file prepared by the Graphical Editor and the current state of project to prepare images in various graphic formats (JPG, TIFF, PNG and others supported by the Sun JAI library (http://java.sun.com/javase/technologies/desktop/media/jai/). The plug-in will be able to prepare the HTML map tag for the picture too (to create an active area on web page containing the image). The resulting file will be ready to use in the next Maven phases by Doxia or other documenting tool. The maven-graph-plugin will cope with changes in the project made after generating the schema XML file. This means that if an object from the XML file is no longer exists in the project, it won't be visible in the picture. It also means that if the object is new, it will be placed in the picture (in a place calculated by the general layout strategy set in the XML file). Additionally the user will be warned about any discrepancies between the expected and actual data and problems with finding space for a new object. The diagram generation will not modify the XML file, but will only try to interpret it for the current situation. During Google Summer of Code time I wish I prepare two connectors (possibilities to visualize an aspect of project): - Dependencies diagram connector – to visualize the chosen project's subset of the dependencies (internal or external, up to a configured depth or/and included in a given scope). It will be also possible to exclude some dependencies from the diagram. - Class diagram – to visualize the inheritance and composition aspects of the class hierarchy. The information will be obtained by reflection. Of course the mechanism of the connectors will be universal enough to make the addition of a new aspect of a project as simple as possible. Why „Maven Diagram-Maker? There are no good, free tools to prepare diagrams – especially such that would automatically generate diagrams from the source code and project descriptors. On the other hand, good and up-to-date documentation is a very important part of software development process – particularly in the Open Source world, where documentation is critical to help many people work on projects. On the other hand, nobody likes preparing documents and diagrams. To make the matters worse, using standard one-time diagrammers helps only for a short period of time. In fast growing projects, the pictures become obsolete very quickly. They start to mislead. Therefore I think that adding possibility to generate actual up-to-date diagrams in the build process is a very important idea – and Maven is the perfect environment to do that. Java developers can nowadays use very good text documenting tools, such a JavaDoc and Doxia, but the lack of methods to prepare and incorporate actual visual information in the documents is a very serious shortcoming of those tools. Planned editor features The Graphical Editor will help the user create and edit the visualization schema XML file. The file will contain two types of information: - The dataSource section will describe which data will be presented, that is - how to acquire the information to present. The classes and attributes of connectors, which will
[ANN] Maven 1.1-RC1 Released
Maven 1.1-RC1 Released The Apache Maven team is pleased to announce the release of Maven 1.1-RC1! Downloadhttp://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/start/download.html[1] Maven 1.1-RC1 and read the Installation Instructionshttp://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/start/install.html[2]. Maven is a project management and project comprehension tool. Maven is based on the concept of a project object model: builds, documentation creation, site publication, and distribution publication are all controlled from the project object model. Maven also provides tools to create source metrics, change logs based directly on source repository, and source cross-references. Compared to Maven 1.1-beta-3, this release focuses on the following objectives: - Upgrade dependencies, eg wagon, maven-model, plexus-utils, commons-jexl, - Upgrade a number of pluginshttp://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/plugins/bundledHistory.html[3], see MAVEN-1769 http://jira.codehaus.org/browse/MAVEN-1769 [4] for a complete list, - Improved error handling and reporting, - Improved handling of groupId/artifactId. For a full list of changes, please see JIRAhttp://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10030styleName=Htmlversion=11971[5]. With just a few exceptions http://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/reference/backwards-compatibility.html[6], Maven 1.1-RC1 is backwards compatible with Maven 1.0. *Please note*: Maven 2.0.6 http://maven.apache.org/ [7] is the latest stable release of Maven and is recommended for all new projects, but it is not compatible with Maven 1.x. Maven 1.1 is meant to improve the performance and stability for those using Maven 1.0 for their builds. We hope you enjoy using Maven! If you have any questions, please consult: - the FAQ [8] http://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/faq.html - the maven-userhttp://people.apache.org/%7Eaheritier/staging-sites/m1-core/maven-1.x/mail-lists.html[9] mailing list *- The Apache Maven Team* [1] http://maven.apache.org/maven-1.x/start/download.html [2] http://maven.apache.org/maven-1.x/start/install.html [3] http://maven.apache.org/maven-1.x/plugins/bundledHistory.html [4] http://jira.codehaus.org/browse/MAVEN-1769 [5] http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10030styleName=Htmlversion=11971 [6] http://maven.apache.org/maven-1.x/reference/backwards-compatibility.html [7] http://maven.apache.org/ [8] http://maven.apache.org/maven-1.x/faq.html [9] http://maven.apache.org/maven-1.x/mail-lists.html .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ...
