ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-454) Deleting artifacts from ACE (shop repo) does not remove the artifacts from the OBR
Date Mon, 17 Feb 2014 09:30:19 GMT


Marcel Offermans commented on ACE-454:

To add a little word of warning: ACE relies on the fact that if an artifact has a specific
BSN + version, this artifact is unique and will never change. It does so because if this were
not the case, then regardless of a version of an artifact, you could never depend on it being
the same artifact and you would always have to update it. That in turn would mean that having
a modular application and updating just parts of it makes no sense, since then you always
need to send all artifacts, so you might as well send one big monolithic one.

What I'm saying: if you want to use ACE in a development environment, you must make sure that
your build produces artifacts whose version changes if (and probably only if) the artifact
itself changes. In the gogo scripting commands, we actually have a command (called "cd") that
will take a set of bundles from your build, check them with a release and snapshot repository,
and bump the qualifier if needed.

Some background on the how and why can be found in this presentation that [~Japio007] and
myself gave at EclipseCon/OSGi DevCon:

> Deleting artifacts from ACE (shop repo) does not remove the artifacts from the OBR
> ----------------------------------------------------------------------------------
>                 Key: ACE-454
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>          Components: OBR, Repository
>            Reporter: Wilfried Sibla
> in such a way it's not so easy to use ACE in dev environment where a artifact possibly
changes without changing it's version

This message was sent by Atlassian JIRA

View raw message