1

By checking project's structure, I can see that until branch 5.3.x, maven and gradle are available as build tools.

Starting from branch 6.x this is not the case. There is not a pom.xml which in my understanding means that maven is not supported anymore as build tool.

However, on the official docs, for example for delegated authentication , dependency is also available as maven artifact(Maven tab).

So what is really happening? Is maven deprecated as build tool for the overlay?

leopal
  • 4,711
  • 1
  • 25
  • 35

1 Answers1

3

From the release notes published almost a year ago at:

https://apereo.github.io/2018/09/14/600rc2-release/#war-overlay

The Maven WAR overlay template is now deprecated and moved aside. The reference overlay project simply is transformed to use the Gradle build tool instead. This is done to reduce maintenance overhead and simplify the deployment strategy while allowing future attempts to make auto-generation of the overlay as comfortable as possible.

The maven dependency tab exists because:

  • In theory there is nothing stopping you from creating your own overlay using Apache Maven and using one of those dependencies in your own project on your own.

  • A Maven dependency is not only used for a CAS overlay project; it can be used as an external dependency in any other projects for extensions or add-ons all of which may be based on Apache Maven.

Misagh Moayyed
  • 4,154
  • 2
  • 15
  • 25
  • 1
    Thanks for this answer, although IMHO it's not 100% clear whether the "comfortable as possible" relates to overlay *users*, or to overlay *maintainers*. And if it is meant for *users*, I wonder what is the exact advantage, apart from that users don't need to install Maven? Or is it just authors' general preference of Gradle? – Petr Bodnár Sep 03 '20 at 07:57