Have organization level restriction on docker usage on local machine.
a) Is it possible to have sdk 4.1 to build extension jar and also run without docker for alfresco 6.2 enterprise application ?
b) Do we have any forked version of (https://github.com/Alfresco/alfresco-sdk) which does not mandate docker installation . (Like sdk 3.1 or sdk 2.2 , which does not need docker)
Note: I understand that -
i) The sdk 4.1 set up can be tweaked to build and generate jar(but not run application) .(without docker)
ii) The extension jar created (in above step i) can be used in another alfresco enterprise set up (using distribution zip) to run application.
The Alfresco SDK is used by developers to build extensions for the Alfresco Digital Business Platform. It is based on Apache Maven, compatible with major IDEs and enables Rapid Application Development (RAD) and Test Driven Development (TDD).
a - yes, you can build extensions. Just use maven command : "mvn clean package" or "mvn clean install -DskipTests=true". Please note that if you want to use integration-tests, you would be required to update the url of running instance in order to use it. By default "mvn clean install" tries to launch the containers and perform the integration tests.
You can find this property in pom.xml:
<!-- Default local -->
<!-- For a remote instance -->
see here for more details: https://github.com/Alfresco/alfresco-sdk/blob/master/docs/advanced-topics/integration-testing/it-working.md
You can also setup debugging , see here: https://github.com/Alfresco/alfresco-sdk/blob/master/docs/advanced-topics/debugging/debug-eclipse.md
b - No, sdk4.1 is based on docker and docker-compose.
You can generate extensions and deploy them anywhere irrespective of community or enterprise version unless you have something very specific to enterprise version. You can generate jar and amp both from the sdk4.1. You need to uncomment following plugin in order to generate the amps.
<!-- Build an AMP if 3rd party libs are needed by the extensions JARs are the default artifact produced in your modules, if you want to build an amp for each module you have to enable this plugin and inspect the src/main/assembly.xml file if you want to customize the layout of your AMP. The end result is that Maven will produce both a JAR file and an AMP with your module. -->
(ACSCE, AWS SAA, Azure Admin)