[ 
http://jira.codehaus.org/browse/MECLIPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148263#action_148263
 ] 

Barrie Treloar commented on MECLIPSE-418:
-----------------------------------------

There is nothing about what versions of OSGi the plugin supports, so I am 
assuming it at least supports OSGi 3 and probably 2.

h2. From the specs

h3.  Version 2
Manifest header (named "Bundle-Name") identifying the bundle's name.

No information about whether it is mandatory.

Bundle-SymbolicName not supported.

h3. Version 3
(same as Version 2)

No information about whether it is mandatory.

Bundle-SymbolicName not supported.

h3. Version 4
Bundle-Name:
The Bundle-Name header defines a readable name for this bundle. This
should be a short, human-readable name that can contain spaces.

Bundle-SymbolicName
The Bundle-SymbolicName manifest header is a mandatory header

A bundle gets its unique Bundle-SymbolicName from the developer (The
Bundle-Name manifest header provides a human-readable name for a bundle
and is therefore not replaced by this header).

Therefore the patch as provided has not been applied.
Instead either Bundle-Name or Bundle-SymbolicName must be present for the 
bundle to be installed.

Unit tests have been created and refactored for easier to reading.

> Goal install-plugins looks for "Bundle-Name" to check whether, a jar is a 
> bundle. But "Bundle-Name" is an optional parameter. "Bundle-SymbolicName" 
> instead is mandatory.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-418
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-418
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: OSGi, Manifest
>    Affects Versions: 2.5
>         Environment: Java 6, Maven 2.0.8
>            Reporter: Robert Radkiewicz
>            Priority: Minor
>         Attachments: Bundle-SymbolicName.patch
>
>
> After the 
> "Osgi Service Platform Core Specification  Release 4, Version 4.1"
> the parameter "Bundle-Name" in the MANIFEST.MF is only a optional parameter.
> In the "InstallPluginsMojo" this parameter is checked, to decide whether this 
> jar is an osgi-bundle or not.
> The use of "Bundle-SymbolicName" would be more stable, because it is 
> mandatory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to