pom.xml shows multiple errors on including log4j dependency - eclipse

I have just created a new java project and configured it as a 'maven project' in eclipse. pom.xml file is autogenerated. It has no error at this point. I've added the log4j dependency in the auto generated pom.xml file and it shows a few errors that are shown below the pom.xml file.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>Log4JPactice</groupId>
<artifactId>Log4JPactice</artifactId>
<version>0.0.1-SNAPSHOT</version>
<build>
<sourceDirectory>src</sourceDirectory>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
</dependency>
</dependencies>
</project>
Error:
Multiple annotations found at this line:
- Missing artifact javax.jms:jms:jar:1.1
- ArtifactTransferException: Failure to transfer com.sun.jdmk:jmxtools:jar:1.2.1 from https://maven-repository.dev.java.net/nonav/repository was cached in the local repository, resolution will not be reattempted until the update interval of java.net has elapsed or
updates are forced. Original error: Could not transfer artifact com.sun.jdmk:jmxtools:jar:1.2.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net (https://maven-repository.dev.java.net/nonav/
repository) of type legacy using the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory
- ArtifactTransferException: Failure to transfer javax.jms:jms:jar:1.1 from https://maven-repository.dev.java.net/nonav/repository was cached in the local repository, resolution will not be reattempted until the update interval of java.net has elapsed or updates are
forced. Original error: Could not transfer artifact javax.jms:jms:jar:1.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net (https://maven-repository.dev.java.net/nonav/repository) of type legacy using
the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory
- ArtifactTransferException: Failure to transfer com.sun.jmx:jmxri:jar:1.2.1 from https://maven-repository.dev.java.net/nonav/repository was cached in the local repository, resolution will not be reattempted until the update interval of java.net has elapsed or updates
are forced. Original error: Could not transfer artifact com.sun.jmx:jmxri:jar:1.2.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net (https://maven-repository.dev.java.net/nonav/repository) of type
legacy using the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory
- Missing artifact com.sun.jdmk:jmxtools:jar:1.2.1
- Missing artifact com.sun.jmx:jmxri:jar:1.2.1
Eclipse used: Eclipse Juno
Any idea about this error?
Update:
On running mvn install from the command line I get the following error:
Failed to execute goal on project Log4JPactice: Could not resolve dependencies for project Failed to execute goal on project Log4JPactice: Could not resolve dependencies
for project Log4JPactice:Log4JPactice:jar:0.0.1-SNAPSHOT:
The following artifacts could not be resolved: javax.jms:jms:jar:1.1,
com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1:
Could not transfer artifact javax.jms:jms:jar:1.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository):
No connector available to access repository
java.net (https://maven-repository.dev.java.net/nonav/repository) of type legacy
using the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory -> [Help 1]

You can exclude those dependencies, as you probably don't need them
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
<exclusions>
<exclusion>
<groupId>com.sun.jdmk</groupId>
<artifactId>jmxtools</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jmx</groupId>
<artifactId>jmxri</artifactId>
</exclusion>
<exclusion>
<groupId>javax.jms</groupId>
<artifactId>jms</artifactId>
</exclusion>
</exclusions>
</dependency>

I used this and it worked
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.17</version>
</dependency>
But its not working with version 1.2.15 may be a version issue

my solution is:
<repositories>
<repository>
<id>repository.jboss.org-public</id>
<name>JBoss.org Maven repository</name>
<url>https://repository.jboss.org/nexus/content/groups/public</url>
</repository>
</repositories>

Good one yes 1.2.15 has dependencies which are missing from central repository.e.g. jmxri:jar Looks like it even does not exist or has been moved from repository.jboss.org. Just update to 1.2.16 or higher.
Below are comments from eclipse STS
Failure to transfer com.sun.jmx:jmxri:jar:1.2.1 from https://maven-repository.dev.java.net/nonav/repository was cached in the local repository, resolution will not be reattempted until the update interval of java.net has elapsed or updates are forced.
Original error
Could not transfer artifact com.sun.jmx:jmxri:jar:1.2.1 from/to java.net (https://maven-repository.dev.java.net/nonav/repository):"

Related

Neo4j Maven project

I am trying to create a Maven project in Eclipse using Neo4J. My Pom.xml is as follows:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>graphproject</groupId>
<artifactId>myneo</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>
<name>myneo</name>
<url>http://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.neo4j</groupId>
<artifactId>neo4j</artifactId>
<version>3.3.0</version>
</dependency>
<dependency>
<groupId>org.neo4j.driver</groupId>
<artifactId>neo4j-java-driver</artifactId>
<version>1.5.0-beta01</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
However, I am getting the error shown in the image below:
ArtifactTransferException: Failure to transfer org.neo4j:neo4j-cypher-compiler-2.3:jar:2.3.11 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.neo4j:neo4j-cypher-compiler-2.3:jar:2.3.11 from/to central (http://repo.maven.apache.org/maven2): No response received after 60000 pom.xml /myneo line 2 Maven Dependency Problem
ArtifactTransferException: Failure to transfer org.neo4j:neo4j-cypher-compiler-3.1:jar:3.1.6 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.neo4j:neo4j-cypher-compiler-3.1:jar:3.1.6 from/to central (http://repo.maven.apache.org/maven2): No response received after 60000 pom.xml /myneo line 2 Maven Dependency Problem
ArtifactTransferException: Failure to transfer org.scala-lang:scala-library:jar:2.11.11 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.scala-lang:scala-library:jar:2.11.11 from/to central (http://repo.maven.apache.org/maven2): No response received after 60000 pom.xml /myneo line 2 Maven Dependency Problem
I have tried re downloading the jars by recreating it and also refreshing the repository.
I see that most of the jars have been downloaded:

Adding dependency to OSGI Bundle

I am trying to setup a maven project and added following dependencies
<dependency>
<groupId>com.adobe.granite.bundles</groupId>
<artifactId>json</artifactId>
<version>20090211_1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.day.cq.wcm</groupId>
<artifactId>cq-wcm-foundation</artifactId>
<version>5.6.4</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.adobe.cq.social</groupId>
<artifactId>cq-social-commons</artifactId>
<version>1.4.172</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.adobe.cq.social</groupId>
<artifactId>cq-social-blog</artifactId>
<version>1.1.8</version>
<scope>provided</scope>
</dependency>
On running maven clean install i am getting the following error.
[ERROR] Failed to execute goal on project falcon-utils: Could not
resolve dependencies for project
com.test.wem:test-utils:bundle:0.1-SNAPSHOT: Failed to collect
dependencies at com.adobe.cq.social:cq-social-commons:jar:1.4.172:
Failed to read artifact descriptor for
com.adobe.cq.social:cq-social-commons:jar:1.4.172: Failure to find
com.adobe.cq.social:socialcommunities-parent:pom:1.1.34 in
https://repo.adobe.com/nexus/content/groups/public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of adobe has elapsed or updates are forced -> [Help 1]
I do not think this to be proxy issue because this was working before.
Kindly help me on this.
Thanks,
Jai
The jar is there at https://repo.adobe.com/nexus/content/groups/public/com/adobe/cq/social/cq-social-commons/1.4.172/
Running mvn clean install -U should force update it..

Multiple POM Issues in spring mvc

template used while project creation
http://dist.springsource.com/release/STS/help/org.springframework.templates.mvc-3.2.2.zip
POM
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.winhill</groupId>
<artifactId>elabsexpert</artifactId>
<name>elabsexpert</name>
<packaging>war</packaging>
<version>1.0.0-BUILD-SNAPSHOT</version>
<properties>
<java-version>1.6</java-version>
<org.springframework-version>3.1.1.RELEASE</org.springframework-version>
<org.aspectj-version>1.6.10</org.aspectj-version>
<org.slf4j-version>1.6.6</org.slf4j-version>
</properties>
<dependencies>
<!-- Spring -->
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>${org.springframework-version}</version>
<exclusions>
<!-- Exclude Commons Logging in favor of SLF4j -->
<exclusion>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-webmvc</artifactId>
<version>${org.springframework-version}</version>
</dependency>
<!-- AspectJ -->
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>${org.aspectj-version}</version>
</dependency>
<!-- Logging -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${org.slf4j-version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
<version>${org.slf4j-version}</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>${org.slf4j-version}</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
<exclusions>
<exclusion>
<groupId>javax.mail</groupId>
<artifactId>mail</artifactId>
</exclusion>
<exclusion>
<groupId>javax.jms</groupId>
<artifactId>jms</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jdmk</groupId>
<artifactId>jmxtools</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jmx</groupId>
<artifactId>jmxri</artifactId>
</exclusion>
</exclusions>
<scope>runtime</scope>
</dependency>
<!-- #Inject -->
<dependency>
<groupId>javax.inject</groupId>
<artifactId>javax.inject</artifactId>
<version>1</version>
</dependency>
<!-- Servlet -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.servlet.jsp</groupId>
<artifactId>jsp-api</artifactId>
<version>2.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version>
</dependency>
<!-- Test -->
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.7</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.9</version>
<configuration>
<additionalProjectnatures>
<projectnature>org.springframework.ide.eclipse.core.springnature</projectnature>
</additionalProjectnatures>
<additionalBuildcommands>
<buildcommand>org.springframework.ide.eclipse.core.springbuilder</buildcommand>
</additionalBuildcommands>
<downloadSources>true</downloadSources>
<downloadJavadocs>true</downloadJavadocs>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.5.1</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<compilerArgument>-Xlint:all</compilerArgument>
<showWarnings>true</showWarnings>
<showDeprecation>true</showDeprecation>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2.1</version>
<configuration>
<mainClass>org.test.int1.Main</mainClass>
</configuration>
</plugin>
</plugins>
</build>
</project>
Errors -
Description Resource Path Location Type
ArtifactDescriptorException: Failed to read artifact descriptor for javax.inject:javax.inject:jar:1: ArtifactResolutionException: Failure to transfer javax.inject:javax.inject:pom:1 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact javax.inject:javax.inject:pom:1 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for javax.servlet:jstl:jar:1.2: ArtifactResolutionException: Failure to transfer javax.servlet:jstl:pom:1.2 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact javax.servlet:jstl:pom:1.2 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for javax.servlet:servlet-api:jar:2.5: ArtifactResolutionException: Failure to transfer javax.servlet:servlet-api:pom:2.5 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact javax.servlet:servlet-api:pom:2.5 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for javax.servlet.jsp:jsp-api:jar:2.1: ArtifactResolutionException: Failure to transfer javax.servlet.jsp:jsp-api:pom:2.1 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact javax.servlet.jsp:jsp-api:pom:2.1 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for junit:junit:jar:4.7: ArtifactResolutionException: Failure to transfer junit:junit:pom:4.7 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact junit:junit:pom:4.7 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for log4j:log4j:jar:1.2.15: ArtifactResolutionException: Failure to transfer log4j:log4j:pom:1.2.15 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact log4j:log4j:pom:1.2.15 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.aspectj:aspectjrt:jar:1.6.10: ArtifactResolutionException: Failure to transfer org.aspectj:aspectjrt:pom:1.6.10 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.aspectj:aspectjrt:pom:1.6.10 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.slf4j:jcl-over-slf4j:jar:1.6.6: ArtifactResolutionException: Failure to transfer org.slf4j:jcl-over-slf4j:pom:1.6.6 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.slf4j:jcl-over-slf4j:pom:1.6.6 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.slf4j:slf4j-api:jar:1.6.6: ArtifactResolutionException: Failure to transfer org.slf4j:slf4j-api:pom:1.6.6 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.slf4j:slf4j-api:pom:1.6.6 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.slf4j:slf4j-log4j12:jar:1.6.6: ArtifactResolutionException: Failure to transfer org.slf4j:slf4j-log4j12:pom:1.6.6 from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.slf4j:slf4j-log4j12:pom:1.6.6 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.springframework:spring-context:jar:3.1.1.RELEASE: ArtifactResolutionException: Failure to transfer org.springframework:spring-context:pom:3.1.1.RELEASE from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.springframework:spring-context:pom:3.1.1.RELEASE from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.springframework:spring-webmvc:jar:3.1.1.RELEASE: ArtifactResolutionException: Failure to transfer org.springframework:spring-webmvc:pom:3.1.1.RELEASE from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.springframework:spring-webmvc:pom:3.1.1.RELEASE from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org pom.xml /elabsexpert line 1 Maven Dependency Problem
Please help, I am new to spring and facing this problem at start itself :'(
Environment details -
Windows - 8.1
Eclipse Luna
maven - 3.2.2

Getting javahg 0.6-SNAPSHOT from Maven

I'm trying to get JavaHG 0.6 snapshot using the following Maven pom:
<dependencies>
<dependency>
<groupId>com.aragost.javahg</groupId>
<artifactId>javahg</artifactId>
<version>0.6-SNAPSHOT</version>
</dependency>
</dependencies>
<repositories>
<repository>
<id>sonatype-ossrh</id>
<name>Sonatype Open Source Software Repository Hosting</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
</repositories>
This makes the build fail with the following error:
Could not find artifact com.aragost.javahg:javahg-parent:pom:0.6-SNAPSHOT in sonatype-ossrh (https://oss.sonatype.org/content/repositories/snapshots/) -> [Help 1]
I think this is because 0.6-SNAPSHOT is not found in
https://oss.sonatype.org/content/repositories/snapshots/com/aragost/javahg/javahg-parent/
Does anyone know how to make it work?
Unfortunately recent builds aren't in maven currently. It is possible to build locally.
This thread has some details: https://bitbucket.org/mercurialeclipse/main/issue/424/plugin-readmemd-information-out-of-date
Clone the JavaHg repositories, including javahg-parent
Update to the 0.6 tag for each
Invoke mvn install for javahg-parent, and then again for the other repositories

Maven does not automatically download dependencies

I'm a starter for Maven. I pulled a java maven project from Bitbucket. When compiling the prject Eclipse said "8/6/12 1:39:05 PM EST: Missing artifact com.tinkerpop.blueprints:blueprints-core:jar:1.0:compile":
Maven console:
8/6/12 1:39:03 PM EST: Missing artifact com.tinkerpop.blueprints:blueprints-core:jar:1.0:compile
8/6/12 1:39:05 PM EST: Missing artifact com.tinkerpop.blueprints:blueprints-core:jar:1.0:compile
but when I check the pom.xml file, it is already there in the dependency list, only the Type and Scope fields are empty. Seeing the errors, I try to add this dependency by myself. And it showed like this:
The #1 question is, Why for 1.0 version, blueprints-core only have a .pom file not a .jar file? Does this mean in the remote repository they don't provide the 1.0 version any more? (I found the codes in the project reply on 1.0 version instead of 2.0 version of this Blueprint framework)
The #2 questions is, under what circumstances Maven will not automatically download the jar files for the dependencies added?
This is the original pom.xml file:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>edu.qut.cs</groupId>
<artifactId>qut-recommender</artifactId>
<version>1.0-SNAPSHOT</version>
<relativePath>../qut-recommender/pom.xml</relativePath>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>rcmd-common</artifactId>
<packaging>jar</packaging>
<name>QUT Recommender Common Library and Utilty</name>
<dependencies>
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>11.0.1</version>
</dependency>
<dependency>
<groupId>org.mongodb</groupId>
<artifactId>mongo-java-driver</artifactId>
<version>2.7.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.mahout</groupId>
<artifactId>mahout-ext</artifactId>
<version>1.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>jgrapht</groupId>
<artifactId>jgrapht</artifactId>
<version>0.7.3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.tinkerpop.blueprints</groupId>
<artifactId>blueprints-core</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.16</version>
</dependency>
</dependencies>
</project>
The POM and Jar files of 1.0 version exist. The following picture is the directories and files in the folder of "C:\Users\n8275441.m2\repository\com\tinkerpop\blueprints". BTW, I pulled this project from Bitbucket repository. Is it possible that those 1.0 version files came along with the project in Bitbuckdet?
Based on your information and after checking maven central the problem is based on the version you have selected. Maven Central contains only a version 1.2, 2.0.0 and 2.1.0 but not a version 1.0.
Furthermore if a dependency is given without scope like in your pom:
<dependency>
<groupId>com.tinkerpop.blueprints</groupId>
<artifactId>blueprints-core</artifactId>
<version>1.0</version>
</dependency>
this means default scope which is "compile" (as in the sense of convention over configuration). I would simply suggest to change the version to 2.0.0 or 2.1.0 which should solve the problem.
If you check compiling such project i would suggest to do the first try on command line and not in Eclipse.
If you're wondering what Maven Central offers, mvnrepository.com is your friend.
In this case, there is no 1.0 version: http://mvnrepository.com/artifact/com.tinkerpop.blueprints/blueprints-core
Which leads to the interesting question why m2e reports a POM file for it. I suggest to have a look on your hard disk if the POM file really exists. You can find it (or not) in C:\Users\n8275441\.m2\repository\com\tinkerpop\blueprints\1.0\blueprints-core\
As for question #2: Maven (and m2e as well), will try to download a release (i.e. something that doesn't have SNAPSHOT in the version) only once. If the download fails, Maven will note that and never try again since it assumes that the upstream repositories (Maven Central, for example) heed the Maven rules (so if a repo doesn't have something, it won't have it tomorrow).
For snapshots, Maven will try to download them once per day to get a good balance between keeping you up to date and not wasting your time waiting for some download.