Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-16979

Empty deployment with no error

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 4.2.0.Beta2
    • 4.2.0.Beta1
    • server
    • None
    • Hide

      Copied from JBIDE-16854
      1. Checkout ticket monster from here:
      https://github.com/mmalina/ticket-monster/tree/JBIDE-14659
      e.g. git clone git@github.com:mmalina/ticket-monster.git
      cd ticket-monster
      git checkout origin/JBIDE-14659
      2. Import to eclipse as existing maven project:
      File -> Import -> Maven -> Existing Maven project
      and point it to the demo folder.
      3. Wait for Eclipse to resolve maven dependencies
      4. Finally the project has an error decorator and I see this in Problems view:
      console configuration "ticket-monster-TRUNK" does not exist - line 0 - JPA Problem
      this is somewhat strange since it cannot be tracked to a file, but never mind now (you can actually avoid this error by deleting demo/.settings before importing the project)
      5. Set up and start JBoss AS 7.1.1
      6. In server view, select server -> Add and Remove... and add ticket-monster
      7. The project will be deployed to the server, everything seems fine. Except the deployed war is an empty dir

      Show
      Copied from JBIDE-16854 1. Checkout ticket monster from here: https://github.com/mmalina/ticket-monster/tree/JBIDE-14659 e.g. git clone git@github.com:mmalina/ticket-monster.git cd ticket-monster git checkout origin/ JBIDE-14659 2. Import to eclipse as existing maven project: File -> Import -> Maven -> Existing Maven project and point it to the demo folder. 3. Wait for Eclipse to resolve maven dependencies 4. Finally the project has an error decorator and I see this in Problems view: console configuration "ticket-monster-TRUNK" does not exist - line 0 - JPA Problem this is somewhat strange since it cannot be tracked to a file, but never mind now (you can actually avoid this error by deleting demo/.settings before importing the project) 5. Set up and start JBoss AS 7.1.1 6. In server view, select server -> Add and Remove... and add ticket-monster 7. The project will be deployed to the server, everything seems fine. Except the deployed war is an empty dir

    Description

      After Andre fixed the NPE here JBIDE-16854, there is still a problem.

      When I deploy this version of ticket monster, the tooling shows everything is fine, but on the server, only an empty dir is deployed. Maybe it's because the project is broken. But in any case, there should be an error decorator in the server view at least or something.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3043 [regression] component.exclusion.patterns aggressively exclude everything from deployment

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-16854 NPE when publishing ticket-monster

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: