3 Replies Latest reply on Oct 9, 2008 2:29 PM by Bruno Santos

    JBoss Tools Archiver is unreliable

    Bruno Santos Newbie

      Guys,

      We've been trying to upgrade from Eclipse 3.1 to 3.2 and now 3.3 for a long, long, time. Unfortunately we've been having major issues with JBoss AS Tools.

      The good old JBossIDE packager worked just fine and it is unfortunate that it is not supported for Eclipse 3.2 and 3.3.

      I've just tried the new JBoss AS Tools in Eclipse Ganymede WTP and we can't upgrade yet. The only plug-ins that we've installed are:

      - JBossTools Core - 3.0.0.Alpha1
      - JBossAS Tools - 2.0.0.Alpha1

      From all this, all I've been trying to create are the jar/war/ear/sar, etc using the Archiver tools. The Archiver no longer freezes Eclipse while generating the deployables (as it did in Eclipse 3.2) and I've also noticed some other major improvements in the tool. Still, the most annoying problem is that it will fail to reliably generate the deployable files.

      For example, sometimes the created ear will fail to include other internal jars or wars that have been configured to be part of the package. Restarting Eclipse seems to fix it and the ear will be nicely generated, but as we go, it will end-up failing again. In the end we have to constantly explode the deployed files and check if the contents are correctly placed.

      Here is how I'm configuring it:

      my.ear
      |_ my.jar
      |_ my.war
      | |_WEB-INF
      | |_classes
      | ...
      |_META-INF
      ...

      And I would try to create them separately, but there's no way I can guarantee the packages generation order.

      Another problem is that the JBoss Archiver files from Eclipse 3.2 do not work with the JBoss Archiver for Eclipse 3.3 and, the JBossIDE to Archiver converter fails to reliably generate the new Archiver configuration files (also failed for 3.2).

      Would be nice to have the Archiver stable since it is a main building block for developers.

      Thanks,




        • 1. Re: JBoss Tools Archiver is unreliable
          Rob Stryker Master

          In the Project Archives View, selecting your ear / jar / war etc and right-clicking it, then selecting "Build Archive", should *always* produce a proper jar.

          I've been working hard to remove any bugs found in project archives, and I think what's currently in TRUNK / nightly builds is much improved over what was available previously.

          Something of note is that in the new builds, Project Archives has been moved out to its own component, and "core" is no longer present.

          >Another problem is that the JBoss Archiver files from Eclipse 3.2 do not work with the JBoss Archiver for Eclipse 3.3

          Can you elaborate on this? I went to pains to ensure old archive files would not be broken by any changes made.

          • 2. Re: JBoss Tools Archiver is unreliable
            Bruno Santos Newbie

            Rob,

            Thanks for your quick answer.

            So, and if I understand correctly, all I need to install over Ganymede WTP is the new JBossTools-Archives package from the nightly build page?

            Regarding the issue with the JBoss Archiver files from Eclipse 3.2 that do not work with the JBoss Archiver for Eclipse 3.3, all I can tell you is that it seems that it can't convert from 3.2 ".packages" file to the newer format.

            Let me know if that's all I need to install and I'll try again. I'll come back to you with the results.

            Thanks,
            Bruno

            • 3. Re: JBoss Tools Archiver is unreliable
              Bruno Santos Newbie

              Rob,

              Forget about the JBossArchive question. I got the latest Archiver nightly build installed. At first look, everything seems to be working just fine. I'll try to put under fire as soon as I get some more time.

              Thanks for the help,
              Bruno