Asaf,
  I made changes to the global settings.xml file and when I update the
dependencies, I see a message that it could not transfer the metadata.  It
is finding the settings.xml in my non standard path .m2_ct .

Jason



On Wed, Aug 24, 2011 at 4:11 PM, Asaf Mesika <[email protected]> wrote:

> What settings file is used by M2E? Check the prefs? If you don't know, then
> try "damaging" your settings file to see if M2E fails, thus showing it uses
> your settings file. I'm asking this, since you're using a non default local
> repository location (~/.m2/repository)
>
> --
> Asaf Mesika
> Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
>
> On יום חמישי 25 אוגוסט 2011 at 00:08, jason brett wrote:
>
> Hi Asaf,
>    If I update by command line the jars are updated.   Here is what is in
> my settings file.
>
>  <settings xmlns="http://maven.apache.org/settings/1.0.0";
>
>           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
>           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>
>           http://maven.apache.org/xsd/settings-1.0.0.xsd";>
>
>
>   <!-- localRepository
>
>    | The path to the local repository maven will use to store artifacts.
>
>    |
>
>    | Default: ~/.m2/repository
> <localRepository>/path/to/local/repo</localRepository>
>
>    |
>
>    | It may be helpful to have a separate local repo per Maven version only
> if
>
>    | you are using different versions of Maven. The default local
> repository of
>
>    | ~/.m2 should suffice for most developers.
>
>    | Example isolated local repo for Maven 2.0.10
>
>    <localRepository>C:/work/.m2-2.0.10</localRepository>
>
>    -->
>
> <localRepository>c:/.m2_ct/repository</localRepository>
>   <mirrors>
>
>     <!-- mirror
>
>      | Specifies a repository mirror site to use instead of a given
> repository. The repository that
>
>      | this mirror serves has an ID that matches the mirrorOf element of
> this mirror. IDs are used
>
>      | for inheritance and direct lookup purposes, and must be unique
> across the set of mirrors.
>
>      |
>
>      | For UHG, at this time, we are using Artifactory as the Maven
> Repository Proxy.
>
>      | The following <mirror> directs all artifact retrieval to come from
> Artifactory.
>
>      | Artifactory is configured to cache artifacts from the most common
> Maven repositories.
>
>       -->
>
>     <mirror>
>
>       <id>artifactory</id>
>
>       <name>Artifactory</name>
>
>       <url>http://repo1test.cs.com/artifactory/repo</url>
>
>       <mirrorOf>*</mirrorOf>
>
>     </mirror>
>
>   </mirrors>
>
> </settings>
>
>
> On Wed, Aug 24, 2011 at 3:06 PM, Asaf Mesika <[email protected]>wrote:
>
>  What happens if you try to update those snapshot dependencies using the
> command line? Usually updating the snapshots depends on your update policy
> for the repository, located in your global/user settings file
> (~/.m2/settings.xml)
>
> --
> Asaf Mesika
> Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
>
> On יום רביעי 24 אוגוסט 2011 at 22:08, jason brett wrote:
>
> Hi All,
>   I am having an issue with M2E and have been searching the web and haven't
> found anything that fit my issue.  I finally decided to email the users list
> and ask for hep.
>
>  What I am seeing is that when I first download snapshots of my projects,
> things work fine.  As development continuous through the day and I want to
> update my snapshots and code, I run into an issue.  The snapshots do not get
> updated, even if I check the "Force Update of Snapshots/Releases" option.  I
> wind up going to my local repository and manually removing the snapshot jar
> and then updating to get the latest version.   I am not sure why things are
> not getting updated.  Its not just me that is having the issues, some of my
> co-workers are having the same issue and none of us have any clues what the
> root cause of the problem might be.
>
> I am using Helios, and   m2e - Maven Integration for Eclipse
> 1.0.0.20110607-2117    org.eclipse.m2e.feature.
> feature.group.
>
> Thanks in advance for any help.
>
> Jason
> _______________________________________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
>
> _______________________________________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
> _______________________________________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
>
> _______________________________________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to