Uploaded image for project: 'Share Application'
  1. Share Application
  2. SHA-2040

Review dependencyManagement section in top level pom


    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Share Application
    • Labels:


      Following issues with the build when attempting to get the 201706 Community release out,

      Stefan Kopf has noticed some issues with the build caused by some misconfigured dependencies.

      This is because the share-services war is a repo amp.

      The fix Stefan implemented was to:
      1. Remove alfresco-core from the <dependancyManagement> section in the topmost pom
      2. Manually set the version of alfresco-core to ${dependency.alfresco-core.version} in share/pom.xml and web-editor/pom.xml

      That fix was merged to HEAD, 5.2.N, 5.1.N, 5.2.0, 5.2.1 HF Branch.

      However, Stefan has noticed some other issues that will need attention. From they Skype chat:
      [29/06/2017, 13:49:18] Stefan Kopf: Hm. This is not the only dependancy that will cause problems.
      [29/06/2017, 13:49:41] Stefan Kopf: There are a couple of other dependancies that are managed in the topmost pom but really shouldn’t
      [29/06/2017, 13:50:24] Stefan Kopf: Like alfresco-jlan-embed (not sure why the share.war needs jLan ?!?), spring-webscripts, spring-surf, etc.
      [29/06/2017, 13:51:10] Stefan Kopf: Maybe the new Share team wants to better isolate the build of share-services.amp from the rest.


          Issue Links




                • Assignee:
                  dwebster David Webster [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created:

                    Structure Helper Panel