Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-6541

slingstart-maven-plugin: Make enriching the Maven classpath optional

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Slingstart Maven Plugin 1.7.0
    • Component/s: Tooling
    • Labels:
      None

      Description

      Currently the o.a.s.maven.slingstart.DependencyLifecycleParticipant takes care of enriching the Maven classpath for all projects referencing this Maven plugin. Although in most of the cases this may be desired, this is not necessarily the case.
      E.g. when I have a bundle module which contains some ITs leveraging sling-mocks and others leveraging e.g. a teleporter test, the merged classpath often conflicts with sling-mocks. When using a model leveraging a slingstart project like the sling launchpad the merged classpath is huge and may negatively affect also other ITs (which are not executed remotely).

      I therefore propose to make the extension of the classpath optional.

      Initially this was only done for slingstart and slingfeature but changed to all projects referencing this plugin in SLING-6068.

        Attachments

        1. SLING-6541-v02.patch
          8 kB
          Konrad Windszus

          Issue Links

            Activity

              People

              • Assignee:
                kwin Konrad Windszus
                Reporter:
                kwin Konrad Windszus
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: