Bug 537473 - Build issue plugin, The following artifacts could not be downloaded
Summary: Build issue plugin, The following artifacts could not be downloaded
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.9   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-30 01:25 EDT by Ozer ozerxy CLA
Modified: 2022-07-11 12:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ozer ozerxy CLA 2018-07-30 01:25:33 EDT 
Hello,

Last week i have successfully able to build my plugin, but this week when i tried to build my plugin i have faced with below error, Even if i have not changed any thing in my side this error occur. Could you please let me know why this issue occur, and how can i fix it ? 


....
[ERROR] The following artifacts could not be downloaded: 
[ERROR]   osgi.bundle,ilg.gnuarmeclipse.core,3.2.1.201806261203
[ERROR]   osgi.bundle,ilg.gnuarmeclipse.templates.core,2.5.5.201806261203
[ERROR] Internal error: java.lang.RuntimeException: Some required artifacts could not be downloaded. See log output for details. -> [Help 1]

Thanks
Ozer
Comment 1 Eclipse Genie CLA 2020-07-20 08:57:39 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-07-11 12:35:04 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.