ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bree Van Oss (JIRA)" <>
Subject [jira] [Created] (ACE-512) Custom artifacts not conformed to filename standard are ignored by repo:cd Gogo command
Date Tue, 27 Jan 2015 19:34:36 GMT
Bree Van Oss created ACE-512:

             Summary: Custom artifacts not conformed to filename standard are ignored by repo:cd
Gogo command
                 Key: ACE-512
             Project: ACE
          Issue Type: Bug
          Components: Repository
    Affects Versions: 2.0.1
         Environment: OS X 10.10.1 with Java 8

java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
            Reporter: Bree Van Oss
            Priority: Minor

Non-Java OSGi artifacts whose names do not end in a version number, in the form dash number
(e.g. are silently ignored by the ACE repo:cd Gogo command.

Presently we are attempting to use ACE to provision several non-Java OSGi artifacts. Each
of these components has a different artifact naming convention and none of the conventions
conform what ACE (or BND) expects. We do not have control over the name of one artifact type
(RPM) and I believe it will be fairly difficult to overcome this obstacle by simply working
around the issue on our end.

A bit more detail follows.

The following filter is used, however when the "version" attribute is not specified, the filter
fails and the artifact is consequently filtered out

filter: (&(osgi.identity=*)(version=*)(type=*))

Map<Requirement, Collection<Capability>> sourceResources = repository.findProviders(Collections.singleton(requirement));

FrameworkUtil$FilterImpl.match(Dictionary<String,?>) line: 418	
CapabilityIndex.appendMatchingCapabilities(Requirement, Collection<Capability>) line:
AceObrRepository(AbstractIndexedRepo).findProviders(Collection<Requirement>) line: 332

RepositoryUtil.findResources(Repository, Requirement) line: 296	
RepositoryUtil.findResources(Repository, String, String, String) line: 285	
RepositoryUtil.findResources(Repository, String, String) line: 278	
ContinuousDeployer.deployResources() line: 68, CommandRepo, CommandRepo) line: 136	
... (more)

This message was sent by Atlassian JIRA

View raw message