Elliotte Rusty Harold created MRESOLVER-31:
----------------------------------------------

             Summary: OSGi metadata
                 Key: MRESOLVER-31
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-31
             Project: Maven Resolver
          Issue Type: Improvement
          Components: resolver
    Affects Versions: Maven Artifact Resolver 1.1.0
         Environment: all
            Reporter: Elliotte Rusty Harold


The MANIFEST.MF for the HTTP transport (and I suspect the file transport too 
though I haven't popped it open and looked yet) does not have OSGI metadata:

elharo-macbookair99:Downloads elharo$ more META-INF/MANIFEST.MF
Manifest-Version: 1.0
Implementation-Title: Maven Artifact Resolver Transport HTTP
Implementation-Version: 1.1.0
Built-By: mosipov
Specification-Vendor: The Apache Software Foundation
Created-By: Apache Maven 3.5.0
Implementation-URL: https://maven.apache.org/resolver/maven-resolver-t
 ransport-http/
Implementation-Vendor: The Apache Software Foundation
Automatic-Module-Name: org.apache.maven.resolver.transport.http
Implementation-Vendor-Id: org.apache.maven.resolver
Build-Jdk: 1.7.0_121
Specification-Title: Maven Artifact Resolver Transport HTTP
Specification-Version: 1.1
Archiver-Version: Plexus Archiver


Adding this would be extremely helpful for anyone who wants to use this in an 
Eclipse plugin. E.g.

Bundle-ManifestVersion: 2
Bundle-Name: org.apache.maven.resolver.transport.http
Bundle-RequiredExecutionEnvironment: J2SE-1.5, J2SE-1.4
Bundle-SymbolicName: org.apache.maven.resolver.transport.http
Bundle-Vendor: apache.org
Bundle-Version: 1.1.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to