Menu

#1129 Issue building custom config fragment with more recent plugins.

Eclipse-Plugin
closed
nobody
None
Eclipse
2-Critical
Bug
2014-06-10
2013-09-06
lhasadad
No

eclipse indigo
plugin version: net.sourceforge.pmd.eclipse.plugin_4.0.1.v20130811-0001.jar

have a problem with the more recent form of plugin trying to build a fragment to provide a custom configuration. This fragment is being built as part of a custom eclipse distro built with {pderoot}/scripts/productBuild/productBuild.xml. using an eclipse distro antrunner as the bootstrap. as part of this it builds plugins using a transformed repository that includes packages pulled in to the distro. in this case its pulling in the latest PMD eclipse plugin and not finding the classes under target/classes in the plugin. it used to build just fine so figuring there is something in the newer layout that is creating the issue.

Discussion

  • lhasadad

    lhasadad - 2013-09-10

    I just created a workspace using eclipse kepler and the above mentioned version of the plugin and pulled in my fragment as an eclipse project. I see the same behavior as before but I noted something this time in the package explorer view under plugin dependencies. All of the non-jar-ed class files are showing with target.classes at the start of their name. so something in the linkage to that plugin is causing eclipse builder to think the name of the package includes the first 2 segments of the path in the plugin jar file.

    I think if the packaging were corrected the compile issue would resolve. I'll try and poke at the plugin to see what might be causing this behavior. Oddly it does not appear to affect the runtime.

    ClassPackageOddity

     
  • Jeroen Benckhuijsen

    I'm also affected by this issue. The cause seems to be that both the target/classes and the "." folder are defined in the Manifest als Build-Path. Eclipse PDE only uses the "." folder as build-path entry to resolve classes, not the target/classes folder, although the runtime indeed does.

    Repackaging the plugin where the classes are stored in the root object the jar should fix this problem.

    This issues has been reported to the Eclipse project (PDE project) as a bug. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=423419 for reference.

     
  • Andreas Dangel

    Andreas Dangel - 2014-02-02
    • Milestone: New Tickets --> Eclipse-Plugin
     
  • Andreas Dangel

    Andreas Dangel - 2014-06-10
    • status: open --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB