Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: maven-archiver-2.4.1
    • Fix Version/s: None
    • Component/s: maven-archiver
    • Labels:
    • Flags:
      Patch

      Description

      I'd like to see a more flexible way to adjust the classpath entries in the manifest file. For example with the ear-plugin I'm able to put third party libraries to a different folder (e.g. lib/) than project module artifacts (e.g. root folder). For ejb-modules I need to be able to specify classpath entries for both folders (e.g. lib/log4j.jar and a.b.c.project-common.jar). As you can only specify a general prefix this layout is currently not handled.

      Attached you find a patch against the trunk which introduces a new additional configuration option classpathPrefixThirdParty. Dependencies that have a different groupId from the project itself are prefixed with that option.

        Activity

        Yves Langisch created issue -
        Mark Thomas made changes -
        Field Original Value New Value
        Project Import Sun Apr 05 13:14:21 UTC 2015 [ 1428239661755 ]
        Mark Thomas made changes -
        Workflow jira [ 12726186 ] Default workflow, editable Closed status [ 12764230 ]
        Mark Thomas made changes -
        Patch Submitted Yes [ 10763 ]
        Flags Patch [ 10430 ]
        Mark Thomas made changes -
        Project Import Mon Apr 06 01:15:59 UTC 2015 [ 1428282959282 ]
        Mark Thomas made changes -
        Workflow jira [ 12963994 ] Default workflow, editable Closed status [ 13000559 ]
        Hide
        Michael Osipov added a comment -

        Looking at your patch, artifact.getGroupId().equals(project.getGroupId()) is not a reliable way to determine that your artifact is internal. You have to grab at least all sub ids too and it is still not realiable. Even if it would work, you cannot set both prefixes. Where is the benefit then?

        Show
        Michael Osipov added a comment - Looking at your patch, artifact.getGroupId().equals(project.getGroupId()) is not a reliable way to determine that your artifact is internal. You have to grab at least all sub ids too and it is still not realiable. Even if it would work, you cannot set both prefixes. Where is the benefit then?
        Michael Osipov made changes -
        Labels close-pending

          People

          • Assignee:
            Unassigned
            Reporter:
            Yves Langisch
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development