Jetty
  1. Jetty
  2. JETTY-320

jetty:run should kick in on the process-classes phase, not the compile phase.

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Maven
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Some modules that I work on require post-compile bytecode mangling on the compiled classes, which kicks in during the process-classes phase, as it should be.

      Jetty should run after this phase.

        Activity

        Greg Wilkins made changes -
        Field Original Value New Value
        Assignee Jan Bartel [ janb ]
        Hide
        Jan Bartel added a comment -

        The jetty:run target executes the build lifecycle up to the test-compile phase, which is well after the process-classes phase.

        Show
        Jan Bartel added a comment - The jetty:run target executes the build lifecycle up to the test-compile phase, which is well after the process-classes phase.
        Jan Bartel made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Closed [ 6 ]

          People

          • Assignee:
            Jan Bartel
            Reporter:
            Kohsuke Kawaguchi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: