maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jvan...@apache.org
Subject svn commit: r544255 - /maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt
Date Mon, 04 Jun 2007 20:42:37 GMT
Author: jvanzyl
Date: Mon Jun  4 13:42:35 2007
New Revision: 544255

URL: http://svn.apache.org/viewvc?view=rev&rev=544255
Log:
o clean up the notes

Modified:
    maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt

Modified: maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt
URL: http://svn.apache.org/viewvc/maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt?view=diff&rev=544255&r1=544254&r2=544255
==============================================================================
--- maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt
(original)
+++ maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/MNG-2289/notes.txt
Mon Jun  4 13:42:35 2007
@@ -3,6 +3,6 @@
 3. Set your local repo in settings.xml to something else e.g. <localRepository>/temp/repo-m2-local</localRepository>
 4. Go to the parent directory and change the version of junit to 3.8
 5. Call again mvn deploy, but Maven will now use the temporary local repo for installation
of the updated POM
-6. Go to the issue directory and call noformat}}mvn eclipse:eclipse{{noformat, the project
is now dependent on junit-3.8 as defined in the dependencyManagement of the parent
+6. Go to the issue directory and call mvn eclipse:eclipse, the project is now dependent on
junit-3.8 as defined in the dependencyManagement of the parent
 7. Restore your settings.xml
 8. Call mvn eclipse:eclipse again for the issue, the project is still dependent on junit-3.7
the available newer version of the snapshot parent is ignored



Mime
View raw message