[Greg Soulsby]

I have tried to build a project selecting the Maven option, as I am trying to replicate what Cindy as done for my problem https://www.genuitec.com/forums/topic/getting-access-to-dojox/

Even a simple create project is failing as I get errors, which I will paste below.

I do have access to the internet while the project is created. When I put http://repo1.maven.org/maven2/ into a browser it comes back “Browsing for this directory has been disabled.” which I take to mean my read of the location is not blocked some how.

Description Resource Path Location Type
ArtifactDescriptorException: Failed to read artifact descriptor for javax.xml:webservices-api-osgi:jar:2.0.1: ArtifactResolutionException: Failure to transfer javax.xml:webservices-api-osgi:pom:2.0.1 from http://repo1.maven.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.xml:webservices-api-osgi:pom:2.0.1 from/to central (http://repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/javax/xml/webservices-api-osgi/2.0.1/webservices-api-osgi-2.0.1.pom pom.xml /xx008 line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for javax.xml.bind:jaxb-api-osgi:jar:2.2.1: ArtifactResolutionException: Failure to transfer javax.xml.bind:jaxb-api-osgi:pom:2.2.1 from http://repo1.maven.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.xml.bind:jaxb-api-osgi:pom:2.2.1 from/to central (http://repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api-osgi/2.2.1/jaxb-api-osgi-2.2.1.pom pom.xml /xx008 line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.glassfish:javax.enterprise.deploy:jar:3.0.1: ArtifactResolutionException: Failure to transfer org.glassfish:javax.enterprise.deploy:pom:3.0.1 from http://repo1.maven.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.glassfish:javax.enterprise.deploy:pom:3.0.1 from/to central (http://repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/org/glassfish/javax.enterprise.deploy/3.0.1/javax.enterprise.deploy-3.0.1.pom pom.xml /xx008 line 1 Maven Dependency Problem
ArtifactDescriptorException: Failed to read artifact descriptor for org.glassfish.web:jstl-impl:jar:1.2: ArtifactResolutionException: Failure to transfer org.glassfish.web:jstl-impl:pom:1.2 from http://repo1.maven.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.glassfish.web:jstl-impl:pom:1.2 from/to central (http://repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/org/glassfish/web/jstl-impl/1.2/jstl-impl-1.2.pom pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact ch.qos.cal10n:cal10n-api:jar:0.7.2 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact com.google.collections:google-collections:jar:1.0 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javassist:javassist:jar:3.11.0.GA pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.activation:activation:jar:1.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.annotation:jsr250-api:jar:1.0 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.enterprise:cdi-api:jar:1.0-SP1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.inject:javax.inject:jar:1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.mail:mail:jar:1.4.3 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact javax.ws.rs:jsr311-api:jar:1.1.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.eclipse.persistence:javax.persistence:jar:2.0.0 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:bean-validator:jar:3.0-JBoss-4.0.2 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.annotation:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.ejb:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.jms:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.management.j2ee:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.resource:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.security.auth.message:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.security.jacc:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.servlet:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.servlet.jsp:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.servlet.jsp.jstl:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.glassfish:javax.transaction:jar:3.0.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.interceptor:jboss-interceptor-api:jar:1.1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.interceptor:jboss-interceptor:jar:1.0.0-CR11 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.weld:weld-api:jar:1.0-SP1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.weld:weld-core:jar:1.0.1-SP3 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.weld:weld-osgi-bundle:jar:1.0.1-SP3 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.jboss.weld:weld-spi:jar:1.0-SP1 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.slf4j:slf4j-api:jar:1.5.10 pom.xml /xx008 line 1 Maven Dependency Problem
Missing artifact org.slf4j:slf4j-ext:jar:1.5.10 pom.xml /xx008 line 1 Maven Dependency Problem

[support-tony]

P0rridge,

Could you provide a bit more information for us to investigate?

1. Please attach your installation details (from MyEclipse->Installation Summary->Installation Details), and mention the OS you are using.
2. Please clear your .log file, replicate the error and then attach the resultant .log file (in the .metadata folder of your workspace).
3. Are you trying to include Maven support because that is what Cindy did or because you actually need to use Maven? This isn’t entirely clear from your other forum topic.
4. Where are you seeing the errors you listed and at what point in creating the project?

[Greg Soulsby]

Tony,

I got this working. My interpretation is that the first time you ever use Maven it has to create .m2 directory, and presumably other things as well. Whatever triggers are required to make these initialisations happen did not fire for me first time through. Randomly poking around in the app fired the build of .m2. While some jars did not download automatically I eventually got a clean .m2 with some manual downloading.

Does not leave me with a warm feeling about the robustness of Eclipse, but is consistent with other Eclipse issues -error messages not clearing immediately the error is fixed, always having to do cleans and refreshes etc

Thanks for the advice on submitting problems – it makes total sense to provide that info.

Greg

[support-tony]

Greg,

I’m glad you got it working.

However, it would be good to track down the cause of this. I couldn’t replicate the problem, even after deleting my .m2 folder; I don’t think maven creates anything else. If we can’t replicate the problem, then it gets tough to fix it.

Sorry you’re having to wrestle with eclipse sometimes. It’s a big beast now, especially in the MyEclipse mode, so there can be odd interactions that aren’t always seen until a customer does something a little different or has a slightly different set-up to begin with.

If you have more insights on this, we’d love to get them.

[Author]

Posts