JiBX
  1. JiBX
  2. JIBX-83

Eclipse builder fails to run (classpath issues)

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: eclipse-plugin
    • Labels:
      None
    • Environment:
      eclipse 3.1 on linux
    • Number of attachments :
      1

      Description

      The JiBX eclipse builder fails to execute because of classpath issues. The error that is thrown is that org.jibx.runtime.Utility cannot be located. The JiBX compiler does some adhoc classloading which doesn't jive with the eclipse plugin context. It is necessary to add jibx-run.jar to the eclipse project and have it picked up by the JiBX builder to send to the Compile#compile method.

      Additionally, for projects that use alternate output locations, such as WTP (.deployables/../classes), it is necessary to ensure that all of these folders are included properly. The buildJibxClasspath method should look at all "output" folders and referenced jar files (since it needs the runtime jar).

        Activity

        Hide
        Dan Allen added a comment -

        Apply this patch to /jibxeclipse-plugin/src/java/org/jibx/plugins/eclipse/JibxBuilder.java

        This patch finds all output folders (folders that contain *.class files generated by the project), includes the jibx-run.jar in the classpath (if found, if not informs user to add it to build path), and cleans up the message output to avoid double printed messages and a more verbose error output by using e.rootCause() when compile fails.

        Show
        Dan Allen added a comment - Apply this patch to /jibxeclipse-plugin/src/java/org/jibx/plugins/eclipse/JibxBuilder.java This patch finds all output folders (folders that contain *.class files generated by the project), includes the jibx-run.jar in the classpath (if found, if not informs user to add it to build path), and cleans up the message output to avoid double printed messages and a more verbose error output by using e.rootCause() when compile fails.
        Hide
        Dennis Sosnoski added a comment -

        I'd love to see the Eclipse builder brought up to date, but have actually recommended against using it in the RC2 documentation because there's been no one to maintain it and I've been unwilling to take it on myself. Are you interested in contributing in this area, Dan?

        Show
        Dennis Sosnoski added a comment - I'd love to see the Eclipse builder brought up to date, but have actually recommended against using it in the RC2 documentation because there's been no one to maintain it and I've been unwilling to take it on myself. Are you interested in contributing in this area, Dan?
        Hide
        Dan Allen added a comment -

        Since jibx is key to our development, I will most likely be contributing to it in the future and therefore could take on some of its development. However, I am very strapped for time, so it will come at my convenience. I have spent a couple of nights looking over the code and could likely make improvements. I will do what I can.

        Show
        Dan Allen added a comment - Since jibx is key to our development, I will most likely be contributing to it in the future and therefore could take on some of its development. However, I am very strapped for time, so it will come at my convenience. I have spent a couple of nights looking over the code and could likely make improvements. I will do what I can.

          People

          • Assignee:
            Unassigned
            Reporter:
            Dan Allen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: