[
https://issues.apache.org/jira/browse/UIMA-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-5252:
---------------------------------
Description:
Seems maven central changed, and building on linux fails due to lack of eclipse
platform dependency.
Failed to execute goal on project uimaj-ep-debug: Could not resolve
dependencies for project org.apache.uima:uimaj-ep-debug:jar:2.10.0-SNAPSHOT:
Failed to collect dependencies at
org.eclipse.jdt:org.eclipse.jdt.debug.ui:jar:3.2.0 ->
org.eclipse.jdt:org.eclipse.jdt.ui:jar:3.12.2 ->
org.eclipse.platform:org.eclipse.search:jar:3.11.1 ->
org.eclipse.platform:org.eclipse.ui:jar:3.108.1 ->
org.eclipse.platform:org.eclipse.swt:jar:3.105.2 ->
org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]:
No versions available for
org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]
within specified range
The step after org.eclipse.jdt.debug.ui:3.2.0 appears to hit new artifacts
uploaded Jan 7. The failing one has a machine qualifier: "aarch64" which is
for an "ARM" machine. So the build probably needs to be directed to not build
for that architecture?
Build was on "ubuntu" machine, which is unlikely to be an "arm" - so probably
something is wrong with the maven upload that happened on Jan 7. Investigating.
There are multiple artifacts missing in maven central from the Jan 7 update.
The fix seems to be to exclude somewhat high up in the chain of dependencies.
Added 4 exclude points determined by trial and error to ep-debug and
ep-launcher, the other projects don't seem to have an issue. Now builds.
was:
Seems maven central changed, and building on linux fails due to lack of eclipse
platform dependency.
Failed to execute goal on project uimaj-ep-debug: Could not resolve
dependencies for project org.apache.uima:uimaj-ep-debug:jar:2.10.0-SNAPSHOT:
Failed to collect dependencies at
org.eclipse.jdt:org.eclipse.jdt.debug.ui:jar:3.2.0 ->
org.eclipse.jdt:org.eclipse.jdt.ui:jar:3.12.2 ->
org.eclipse.platform:org.eclipse.search:jar:3.11.1 ->
org.eclipse.platform:org.eclipse.ui:jar:3.108.1 ->
org.eclipse.platform:org.eclipse.swt:jar:3.105.2 ->
org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]:
No versions available for
org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]
within specified range
The step after org.eclipse.jdt.debug.ui:3.2.0 appears to hit new artifacts
uploaded Jan 7. The failing one has a machine qualifier: "aarch64" which is
for an "ARM" machine. So the build probably needs to be directed to not build
for that architecture?
Build was on "ubuntu" machine, which is unlikely to be an "arm" - so probably
something is wrong with the maven upload that happened on Jan 7. Investigating.
> uima core debug plugin no longer building - dependency issue
> ------------------------------------------------------------
>
> Key: UIMA-5252
> URL: https://issues.apache.org/jira/browse/UIMA-5252
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp, 2.10.0SDK
>
>
> Seems maven central changed, and building on linux fails due to lack of
> eclipse platform dependency.
> Failed to execute goal on project uimaj-ep-debug: Could not resolve
> dependencies for project org.apache.uima:uimaj-ep-debug:jar:2.10.0-SNAPSHOT:
> Failed to collect dependencies at
> org.eclipse.jdt:org.eclipse.jdt.debug.ui:jar:3.2.0 ->
> org.eclipse.jdt:org.eclipse.jdt.ui:jar:3.12.2 ->
> org.eclipse.platform:org.eclipse.search:jar:3.11.1 ->
> org.eclipse.platform:org.eclipse.ui:jar:3.108.1 ->
> org.eclipse.platform:org.eclipse.swt:jar:3.105.2 ->
> org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]:
> No versions available for
> org.eclipse.platform:org.eclipse.swt.gtk.linux.aarch64:jar:[3.105.2,3.105.2]
> within specified range
> The step after org.eclipse.jdt.debug.ui:3.2.0 appears to hit new artifacts
> uploaded Jan 7. The failing one has a machine qualifier: "aarch64" which is
> for an "ARM" machine. So the build probably needs to be directed to not
> build for that architecture?
> Build was on "ubuntu" machine, which is unlikely to be an "arm" - so probably
> something is wrong with the maven upload that happened on Jan 7.
> Investigating.
> There are multiple artifacts missing in maven central from the Jan 7 update.
> The fix seems to be to exclude somewhat high up in the chain of dependencies.
> Added 4 exclude points determined by trial and error to ep-debug and
> ep-launcher, the other projects don't seem to have an issue. Now builds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
