You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/10/11 02:56:31 UTC

[jira] Resolved: (BUILDR-328) Detect Eclipse plugin project with META-INF/MANIFEST.MF and "Bundle-SymblicName: "

     [ https://issues.apache.org/jira/browse/BUILDR-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert resolved BUILDR-328.
----------------------------------

    Resolution: Fixed

Fixed.

boisvert@sixtine:~/svn/buildr-328$ svn commit -m "BUILDR-328 Detect Eclipse plugin project with META-INF/MANIFEST.MF and Bundle-SymblicName: entry"
Sending        CHANGELOG
Sending        lib/buildr/ide/eclipse/plugin.rb
Sending        spec/ide/eclipse_spec.rb
Transmitting file data ...
Committed revision 823994.


> Detect Eclipse plugin project with META-INF/MANIFEST.MF and "Bundle-SymblicName: "
> ----------------------------------------------------------------------------------
>
>                 Key: BUILDR-328
>                 URL: https://issues.apache.org/jira/browse/BUILDR-328
>             Project: Buildr
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: 1.3.5
>            Reporter: Hugues Malphettes
>            Priority: Minor
>             Fix For: 1.4
>
>
> Currently a project is configured to use the plugin and java natures by default if there is a plugin.xml file or an OSGI-INF folder.
> A different critieria that will work in more cases consists of looking ofr the META-INF/MANIFEST.MF at the root of the project and check that it has a line that starts with
> "Bundle-SymblicName: "   (remove the quotes of course)
> Workaround: set the natures explicitly (see BUILDR-327)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.