You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Apache Wiki <wi...@apache.org> on 2007/06/21 23:40:23 UTC

[Tapestry Wiki] Update of "Tapestry5HowToCreateYourQuickstartWithMaven206" by DanielJue

Dear Wiki user,

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

The following page has been changed by DanielJue:
http://wiki.apache.org/tapestry/Tapestry5HowToCreateYourQuickstartWithMaven206

The comment on the change is:
cleared up abbreviations that might confuse non-English speakers, added a link

------------------------------------------------------------------------------
  {{{
         <repository>
             <id>org.apache.snapshot-repository</id>
-            <name>Apache Snpshot Repository</name>
+            <name>Apache Snapshot Repository</name>
             <url>http://people.apache.org/repo/m2-snapshot-repository</url>
         </repository>
  }}}
- I seemed to see some artifacts move back and forth to different repos, and
+ I seemed to see some artifacts move back and forth to different repositories, and
- adding this repo wound up allowing the build to complete. (Maven will clearly
+ adding this repository wound up allowing the build to complete. (Maven will clearly
  indicate if an artifact is missing.)
  
  That's about it: it all works fine for me here with only this indicated setup.
  
- You might try it without adding the above repo: it should be obvious if the
+ You might try it without adding the above repository: it should be obvious if the
  build just indicates a missing artifact. Then add this and see what you get.
  
  One other note is that at one point during several attempted builds, I found
- that my local repo had an entry for one of the T5 artifacts (I forget
+ that my local repository had an entry for one of the T5 artifacts (I forget
  specifically which), but the folder actually only contained the XML files and
- no jars. I deleted the artifact folders from my local repo and re-built the
+ no jars. I deleted the artifact folders from my local repository and re-built the
  project and they got downloaded intact. So if you create the archetype POM
- and then also add that repo, but still have problems, you might try removing
+ and then also add that repository, but still have problems, you might try removing
- all T5 artifacts from your local repo and re-building to see if this problem
+ all T5 artifacts from your local repository and re-building to see if this problem
  happened to you also.
  
  I never did get to diagnose this issue further: it might have been due to an
  aborted build, or maybe I was building right at the instant the artifact was
- being added to the remote repo; and I suppose it also could have been because
+ being added to the remote repository; and I suppose it also could have been because
- the actual source artifact in the remote repo was corrupt, but things are
+ the actual source artifact in the remote repository was corrupt, but things are
  building and running without issue here now so I'm just forgetting about
  that.
  
  As a side note: Removing a whole artifact should not cause any problems since Maven just finds that it's not there and then just downloads it.
  
- But there's a Maven command-line switch intended to force an update of snapshots: running with "-U" will force a check for updated snapshots. You can see more by running "mvn --help".
+ But there's a Maven command-line switch intended to force an update of snapshots: running with "-U" will force a check for updated snapshots. 
+ You can add the -U to most commands, to force Maven to look for updates.  Otherwise the default it to check once per day.
+ You can see more by running "mvn --help".
  
+ 
- You can also configure when Maven checks for updates in your settings descriptor or right in the project POM. See "updatePolicy" in the documentation on the settings or POM descriptor:
+ You can also configure when Maven checks for updates in your settings descriptor or right in the project POM.xml. See "updatePolicy" in the documentation on the settings or POM descriptor:
  
  http://maven.apache.org/settings.html
+ 
  http://maven.apache.org/pom.html
  
+ If you are using Eclipse WTP for development, please read this:
+ '''["Tapestry5EclipseWTPWithMaven2"]'''
+ 

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