ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-540) Cannot add Artifact
Date Fri, 06 May 2016 07:44:12 GMT


Marcel Offermans commented on ACE-540:

Actually this is not a bug, but a feature. Let me try to explain why...

When you add a resource processor to the system, we accept that as an artifact, but we will
never show it in the UI. That sounds weird and counter-intuitive at first. Why would you not
want to show it? The reason is that the UI was designed for a user to organise artifacts by
grouping them into features, etc. And that is exactly where a resource processor is different.
It makes no sense to add it to a feature. Processors will be deployed alongside artifacts
of the type they support automatically when necessary. So beyond adding them to the system,
there is nothing that you as a user need to do.

The UI also has a separate view on resource processors. There you should see it after you
add it.

The fact that you managed to create an artifact manually via the shell is because in the shell
you created a basic artifact that is not flagged as a resource processor. In that sense the
shell is very powerful and does not protect you against so many logical mistakes.

Now can we improve on this? Probably. Feel free to come up with suggestions. Or further questions.

> Cannot add Artifact
> -------------------
>                 Key: ACE-540
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 2.0.1
>            Reporter: Niels Schroeter
> When uploading an artifact, it does not show up in the artifacts column. When trying
to upload it again, an error message pops up: "All 1 artifacts failed! Failed to add new object:
entity already exists!"
> The artifact is org.apache.felix.deployment.rp.autoconf-0.1.8 (available via maven repo)
and its manifest looks (fine, i guess )like this:
> {quote}
> Manifest-Version: 1.0
> Bundle-Description: A customizer bundle that publishes a Resource Proc
>  essor service that processes configuration resources shipped in a Dep
>  loyment Package.
> Bundle-License:
> DeploymentPackage-Customizer: true
> Bundle-SymbolicName: org.apache.felix.deployment.rp.autoconf
> Built-By: jawi
> Bundle-ManifestVersion: 2
> Bnd-LastModified: 1452955859778
> Bundle-DocURL:
> Bundle-Vendor: The Apache Software Foundation
> Import-Package:;version="[4.1,5)",org.osgi.framewo
>  rk;version="[1.5,2)",;version="[1.3,2)",org.osgi.s
>  ervice.deploymentadmin;version="[1.0,2)",org.osgi.service.deploymenta
>  dmin.spi;version="[1.0,2)",org.osgi.service.event;version="[1.2,2)",o
>  rg.osgi.service.log;version="[1.3,2)",org.osgi.service.metatype;versi
>  on="[1.3,2)",org.osgi.util.tracker;version="[1.4,2)"
> Tool: Bnd-1.15.0
> Export-Package: org.osgi.service.deploymentadmin.spi;uses:="org.osgi.f
>  ramework,org.osgi.service.deploymentadmin";version="1.0",org.osgi.ser
>  vice.metatype;uses:="org.osgi.framework";version="1.2"
> Deployment-ProvidesResourceProcessor: org.osgi.deployment.rp.autoconf
> Bundle-Version: 0.1.8
> Bundle-Name: Apache Felix AutoConf Resource Processor
> Bundle-Activator: org.apache.felix.deployment.rp.autoconf.Activator
> Created-By: Apache Maven Bundle Plugin
> Build-Jdk: 1.8.0_45
> {quote}
> Note: this happens for many other artifacts aswell, i just picked this one since it is
an official felix bundle.

This message was sent by Atlassian JIRA

View raw message