Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#50 Eclipse Plug-in/Extension detection

closed
Joerg Spieler
None
5
2012-07-19
2010-05-04
Anonymous
No

It would be nice if OCDetector does not display a warning if classes are referenced in Eclipse Plug-ins, Extensions etc.

Discussion

  • Joerg Spieler
    Joerg Spieler
    2010-05-04

    Hi,

    It don't understand this feature request:
    - Extensions: You can add plugin.xml to preference "File name pattern to search:"
    - Eclipse Plug-ins: It is not possible, that your code is referenced in eclipse like org.eclipse.swt_xxx.jar

    Jörg

     
  • Hi Jörg,

    what I meant is the following: I have created a plugin-in project in Eclipse. This plug-in has an activator which is referenced in MANIFEST.MF (not in any XML file).
    Therefore I get a warning for the activator class because no reference is found (when I use the standard name pattern *.xml).

    Then I tried the following: in the preferences page I added '.xml, .mf' to 'File name pattern to search' and scanned again. I still get a warning for the activator.
    Now comes the interesting part: if I change the pattern to '.mf, .xml' I no longer get a warning for the activator but now for a perspective class (which is referenced in 'plugin.xml').

    For me now this seems to be a bug in the file name pattern search.

    Maybe you could add 'MANIFEST.MF' to the 'File name pattern search' property by default?

    Thanks a lot,
    Bernhard

     
  • Joerg Spieler
    Joerg Spieler
    2010-05-05

    Hi Bernhard,

    same as bug 2996965 which I fixed with:
    - whitespaces are trimmed now
    - added MANIFEST.MF as default to 'File name pattern to search'

    Jörg

     


Anonymous


Cancel   Add attachments