Project

Profile

Help

Story #5413

closed

As a plugin writer, declarative artifacts without a "remote" will not have RemoteArtifacts created

Added by ppicka about 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 59
Quarter:

Description

If a plugin writer does not declarate a "remote" on a declarative Artifact have no RemoteArtifact objects be created.

Validation adjustments

The validation there will need to be loosened to allow remote to be unset. When unset, the Artifact must already have it's binary data attached to the in-memory Artifact causing ArtifactDownloader to pass it through unmodified.

The Artifact can be saved or unsaved. If saved the ArtifactSaver stage will effectively pass it through unmodified. If unsaved the ArtifactSaver stage will perform its usual operation.

Useful for example in modularity support when we got artifact from first stage which doesn't need to be downloaded but should go through stage to create right relations with content.

Also available in: Atom PDF