-
Bug
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
-
None
-
OSX 10.12.4, Maven 3.5.0
20170512 update: Santosh alerted me to the fact we need the onap public repo - in addition to release and snapshot
added to reference settings.xml
<profile> <id>openecomp-public</id> <repositories> <repository> <id>openecomp-public</id> <name>openecomp-public</name> <url>https://nexus.onap.org/content/repositories/public/</url> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>openecomp-public</id> <name>openecomp-public</name> <url>https://nexus.onap.org/content/repositories/public/</url> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile>
Update:
Update: the following changes to revert these 2 libraries back to their previous versions resolves and compiles - however I don't know if runtime failures will occur on calls that require the new 3.10 and 3.4.200-v2014 from 3.9 and 3.4.200-v2013 changes.
<dependency>
<groupId>org.eclipse.core</groupId>
<artifactId>runtime</artifactId> <!-- from org.eclipse.core.runtime -->
<!--version>3.10.0.v20140318-2214</version--><!-- does not resolve -->
<version>3.9.100-v20131218-1515</version><!-- resolves (same pom as 3.10 though -->
</dependency>
<dependency>
<groupId>org.eclipse.core</groupId>
<artifactId>contenttype</artifactId> <!-- from org.eclipse.core.contentType -->
<!--version>3.4.200.v20140207-1251</version--><!-- does not resolve -->
<version>3.4.200-v20130326-1255</version> <!-- resolves -->
</dependency>
[INFO] ncomp-core-types ................................... SUCCESS [ 1.748 s] [INFO] ncomp-core-model ................................... SUCCESS [ 5.660 s] [INFO] ncomp-core-tools ................................... SUCCESS [ 0.708 s] [INFO] ncomp-core ......................................... SUCCESS [ 0.006 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.911 s [INFO] Finished at: 2017-05-10T18:29:37-04:00 [INFO] Final Memory: 27M/433M [INFO] ------------------------------------------------------------------------ obrienbiometrics:core michaelobrien$ pwd /Users/michaelobrien/wse_onap/onap/ncomp/core obrienbiometrics:core michaelobrien$ mvn clean install -U -DskipTests
Issue
during a maven install - failure to resolve the 2
org.eclipse.core:org.eclipse.core.contenttype:jar:3.4.200.v20140207-1251
org.eclipse.core.runtime:jar:3.10.0.v20140318-2214
obrienbiometrics:ncomp-core-model michaelobrien$ pwd /Users/michaelobrien/wse_onap/onap/ncomp/core/ncomp-core-model obrienbiometrics:ncomp-core-model michaelobrien$ mvn clean install -U -DskipTests [ERROR] Failed to execute goal on project ncomp-core-model: Could not resolve dependencies for project org.openecomp.ncomp.core:ncomp-core-model:jar:1.1.0-SNAPSHOT: The following artifacts could not be resolved: org.eclipse.core:org.eclipse.core.runtime:jar:3.10.0.v20140318-2214, org.eclipse.core:org.eclipse.core.contenttype:jar:3.4.200.v20140207-1251: Could not find artifact org.eclipse.core:org.eclipse.core.runtime:jar:3.10.0.v20140318-2214 in opendaylight-mirror (https://nexus.opendaylight.org/content/repositories/public/) -> [Help 1]
in ncomp-maven-xcore/pom.xml - only the last 2 libraries fail to resolve
<dependency> <groupId>org.eclipse.emf</groupId> <artifactId>org.eclipse.emf.ecore</artifactId> <version>2.11.0-v20150123-0347</version> </dependency> <dependency> <groupId>org.eclipse.emf</groupId> <artifactId>org.eclipse.emf.common</artifactId> <version>2.11.0-v20150123-0347</version> </dependency> <dependency> <groupId>org.eclipse.xtext</groupId> <artifactId>org.eclipse.xtext.xbase.lib</artifactId> <version>2.8.2</version> </dependency> <dependency> <groupId>org.eclipse.core</groupId> <artifactId>org.eclipse.core.runtime</artifactId> <version>3.10.0.v20140318-2214</version> </dependency> <dependency> <groupId>org.eclipse.core</groupId> <artifactId>org.eclipse.core.contenttype</artifactId> <version>3.4.200.v20140207-1251</version> </dependency>
My ~/.m2/settings.xml config is set for all 4 onap and opendaylight artifactories properly
<activeProfile>openecomp-release</activeProfile> <activeProfile>openecomp-snapshots</activeProfile> <activeProfile>opendaylight-release</activeProfile> <activeProfile>opendaylight-snapshots</activeProfile>
the jar is there but in a "runtime" package - not "org.eclipse.core.runtime" which is what is used for 3.6.0 forward
http://repo.maven.apache.org/maven2/org/eclipse/core/runtime/3.10.0-v20140318-2214/
http://repo.maven.apache.org/maven2/org/eclipse/core/org.eclipse.core.runtime/
switching to artifactId=runtime still does not resolve
<groupId>org.eclipse.core</groupId> <artifactId>runtime</artifactId> <version>3.10.0.v20140318-2214</version>
Guys, getting the same error specific to this project (settings.xml is ok, doing a force update) and it's use of Eclipse EMF in ncomp-maven-xcore. I'll try the workaround in the following or likely raise a JIRA in ncomp if some excludes don't work
There are open discussions and a bug on why this artifact is not pushed to maven central
https://bugs.eclipse.org/bugs/show_bug.cgi?id=497982
https://www.eclipse.org/forums/index.php/m/1738005/#msg_1738005
It exists here
https://mvnrepository.com/artifact/org.eclipse.core/runtime/3.10.0-v20140318-2214
related
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-