-
Updated
Nov 1, 2020 - Makefile
project-template
Here are 433 public repositories matching this topic...
-
Updated
Nov 3, 2020 - C#
-
Updated
Jun 27, 2020 - Ruby
-
Updated
Oct 31, 2020 - PHP
-
Updated
Sep 13, 2020 - TypeScript
-
Updated
Aug 16, 2020 - CMake
-
Updated
Oct 26, 2020 - Haskell
-
Updated
Nov 2, 2020 - Python
-
Updated
May 14, 2018 - Clojure
-
Updated
Apr 20, 2020 - Go
-
Updated
Oct 6, 2017 - Clojure
-
Updated
Oct 19, 2020 - CMake
-
Updated
Jul 20, 2020 - CMake
-
Updated
Feb 24, 2020 - Python
-
Updated
Sep 21, 2017 - JavaScript
-
Updated
Nov 3, 2020 - Python
-
Updated
Sep 30, 2020 - PHP
-
Updated
Jun 5, 2020 - Python
-
Updated
Oct 1, 2020 - JavaScript
Since v 6 will probably include a bunch of backwards compatibility issues, we need a max copier version constraint.
By default, it must be something like <next_major_version(min_copier_version).
Pesy would be a great utility for detecting and reporting common issues with your project setup.
This Issue is to accumulate common issues that pesy is well positioned to detect and warn about.
We don't have enough requirements gathered to actually implement something like this feature but let's discuss the possibilities.
Basically, any time someone is confused by something with native projects
-
Updated
Oct 5, 2020 - R
-
Updated
Nov 1, 2018 - JavaScript
-
Updated
Sep 30, 2020 - PHP
-
Updated
Oct 27, 2020 - Rust
Improve this page
Add a description, image, and links to the project-template topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the project-template topic, visit your repo's landing page and select "manage topics."


Now that Cloud Manager supports Java 11 and lets you configure it using the toolchains plugin
https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/creating-aem-application-project.html#using-java-11
It would be nice if the archetypes takes Java version as a user input and configures the toolchains plugin out of the box.