alfresco / alfresco-sdk

The Alfresco In-Process SDK is based on Apache Maven, includes support for rapid and standard development, testing, packaging, versioning and release of your Alfresco integration and extension projects

Alfresco SDK

This is the home of the Alfresco SDK. 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).

License

This project is released under the Apache License, Version 2.0 license. If you are an Enterprise customer check the Support section.

News

• 2024-03: Alfresco SDK 4.8.0 released
• 2023-11: Alfresco SDK 4.7.0 released
• 2023-06: Alfresco SDK 4.6.0 released
• 2022-10: Alfresco SDK 4.5.0 released
• 2022-03: Alfresco SDK 4.4.0 released
• 2021-10: Alfresco SDK 4.3.0 released
• 2021-02: Alfresco SDK 4.2.0 released
• 2019-10: Alfresco SDK 4.1.0 released
• 2019-03: Alfresco SDK 4.0.0 released
• 2019-03: Alfresco SDK 3.1.0 released
• 2017-06-23: Alfresco SDK 3.0.1 released, containing a critical bugfix
• 2017-04-01: Alfresco SDK 3.0.0 released
• 2017-03-27: After years of hard work, countless iterations and gathering feedback, SDK 3.0 has finally been merged into the master branch, ready for release in the coming days
• 2016-02-20: SDK 2.2.0 released to Maven Central. Docs for Community, Enterprise, Release notes
• 2015-10-19: SDK 2.1.1 released to Maven Central. Docs for Community, Enterprise
• 2015-05-20: SDK 2.1.0 released to Maven Central. Docs for Community, Enterprise
• 2014-12-23: SDK 2.0.0 release to Maven Central. Docs, Release Notes
• 2014-08-22: First SNAPSHOT of SDK 2.0.0 in the OSS Sonatype Repository!
• 2014-07: Project fully migrated from Google Code.

User Getting Started

Important Notice about ACS 7.2

Please refer to #635 to fix the Search Services 403 problem.

Important Notice about ACS 7.1

Share Version Number

Since ACS 7.1, Share build pipeline has been refactored, and you now have to specify the internal Share version number, in addition to the version of the image, because they are not the same anymore.

This number can be located in the main pom.xml of the project used to build Share, hence:

• property <alfresco-community-share.version> of acs-community-packaging (Community)
• property <alfresco-enterprise-share.version>of acs-packaging (Enterprise)

So, if for example you want to use the community version of 7.1.0.1, you can go on acs-community-packaging, open the 7.1.0.1 release tag, browse its files, open the pom.xml in the root, then copy the value of <alfresco-community-share.version>.

You'll then need to paste this value inside the SDK property <alfresco.share.version>.

Alternate Docker User

• ACS 6 used to run everything as root.
• ACS 7 introduced an alfresco user, that should've been used after the root user completed its configurations in the Dockerfile.

Due to a bug, this wasn't working in earlier SDKs, and has been fixed in SDK 4.3.

In order to be retro-compatible with ACS 6, however, the user is specified in the SDK property <alfresco.platform.docker.user>.

Hence, its values (already in place) are root for ACS 6, and alfresco for ACS 7+.

Log file location

To prevent writing permission problems when logging with the non-root user, the alfresco.log file has also been moved to a more appropriate location (Tomcat logs instead of Tomcat root).

Important Notice about Version Numbers

In Q4 2020, Alfresco Platform has undergone a major structural refactoring.

Depending on the Platform version desired, you might need to use SDK 4.1, 4.3, 4.4, 4.5, 4.6 or SDK 4.7 instead of SDK 4.8.

• For Enterprise and Community versions of 7.x, SDK 4.4 or higher must be used
• For Enterprise versions of 6.0.x, 6.1.x, 6.2.x newer than November 2020, SDK 4.3 must be used
• For Enterprise and Community versions of 6.0.x, 6.1.x, 6.2.x older than November 2020, SDK 4.1 must be used

It's also important to remember that:

• Community Platform versions are built by acs-community-packaging
• Community Docker images are published on Docker Hub
• Enterprise Platform versions are built by acs-packaging
• Enterprise Docker images are published on Quay.io

Latest Documentation

To get started with Alfresco SDK 4.7.x (latest) visit the Alfresco Documentation.

Documentation about Previous Versions

SDK Version	Alfresco Enterprise Version	Alfresco Community Version	Documentation
SDK 4.8	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x / 23.1.x/ 23.2.x	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x / 23.2.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.7	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x / 23.1.x	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x / 23.1.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.6	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x / 7.4.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.5	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x	Alfresco 7.0.x / 7.1.x / 7.2.x / 7.3.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.4	Alfresco 7.0.x / 7.1.x / 7.2.x	Alfresco 7.0.x / 7.1.x / 7.2.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.3	Alfresco 6.0.x / 6.1.x / 6.2.x / 7.0.x / 7.1.x	Alfresco 7.0.x / 7.1.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.2	Alfresco 6.0.x / 6.1.x / 6.2.x / 7.0.x	Alfresco 7.0.x	https://github.com/Alfresco/alfresco-sdk/tree/master/docs/README.md
SDK 4.1	Alfresco 6.0.x / 6.1.x / 6.2.x	Alfresco 6.0.x / 6.1.x / 6.2.x	https://github.com/Alfresco/alfresco-sdk/blob/sdk-4.1/docs/README.md
SDK 4.0	Alfresco 6.0.x / 6.1.x	Alfresco 6.0.x / 6.1.x	https://github.com/Alfresco/alfresco-sdk/blob/sdk-4.0/docs/README.md
SDK 3.1	Alfresco 5.2.x	Alfresco 5.2.x	http://docs.alfresco.com/5.2/concepts/sdk-intro.html
SDK 3.0	Alfresco 5.2.x	Alfresco 5.2.x	http://docs.alfresco.com/5.2/concepts/sdk-intro.html
SDK 2.2	Alfresco 5.1.x	Alfresco 5.1.x	https://docs.alfresco.com/5.1/concepts/alfresco-sdk-intro.html
SDK 2.1	Alfresco 5.0.1	Alfresco 5.0.d	https://docs.alfresco.com/sdk2.1/concepts/alfresco-sdk-intro.html
SDK 2.0	Alfresco 5.0.0	Alfresco 5.0.c	https://docs.alfresco.com/sdk2.0/concepts/alfresco-sdk-intro.html
SDK 1.1.1	Alfresco 4.2.x	Alfresco 4.2.x	https://docs.alfresco.com/4.2/concepts/dev-extensions-maven-sdk-intro.html

Reporting Issues and Community Support

Report issues (and contribute!) here or join us on the IRC Channel.

Alfresco Enterprise Customers and Partners Support

If you are an Alfresco Customer please check the SDK Support status for the version you are using. If your version is in Limited or Full Support and you need help, visit the Support Portal.

Maven repositories

• As of version 2.0-beta-1, The Alfresco SDK is released in Maven Central. Previous versions are available in the Alfresco Artifacts Repository.
• Alfresco (Community and Enterprise) artifacts are hosted in the Alfresco Artifacts Repository.
• Alfresco Community artifacts (JARs, WARs, AMPs, poms) and SDK artifacts are publicly available.

NOTE: By default the Alfresco SDK will use Community Edition releases but it can be configured to use Enterprise Edition releases. Enterprise and Premier customers can use the SDK with Enterprise Edition releases by following the process described in Working with Enterprise.

Alfresco Artifacts Repository

Alfresco Releases

You can use the following snippet in your pom.xml to access releases from the Alfresco Artifact repository:

<repository>
    <id>alfresco-public</id>
    <url>https://artifacts.alfresco.com/nexus/content/groups/public</url>
</repository>

SDK Snapshots

To test new unreleased (unsupported) features, you can use the following snippet in your pom.xml to access SDK nightlies (SNAPSHOTS) from the OSS Sonatype repository:

<repository>
    <id>oss-sonatype-snapshots</id>
    <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</repository>

Docker registries

• Alfresco Community Docker images are publicly available at the Alfresco's Docker Hub profile.
• Alfresco Enterprise Docker images are hosted at Quay.io. Its configuration process is described in detail in How to configure private Alfresco Docker registry.

For Developers that want to contribute to the SDK

See the Developers Wiki page.

alfresco-sdk's Issues

WAR --> AMP dependency copies libs in the wrong place

From [email protected] on August 05, 2008 10:51:33

When installing (unarchive) an AMP into an Alfresco WAR, the jar
files from the AMP are copied into /WEB-INF/lib/lib instead of
/WEB-INF/lib

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=10

AMP and extension archetype should use in memory database by default

From [email protected] on August 13, 2008 14:02:38

What steps will reproduce the problem? 1. Create a project with amp or extension archetype
2. Run jetty integrated run What is the expected output? What do you see instead? We would like a seamless start even if the databse was not created. Now we
reqruire (by default, can be modified) a mysql installation with a database
named 'alf_jetty' with appropriate granted permissions.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=12

Use HSQLDB for embedded run

From [email protected] on December 02, 2009 08:00:55

This is waiting on outdated scripts in Alfresco: https://issues.alfresco.com/jira/browse/ALFCOM-3691

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=31

AMP Plugin: store config assets in fully expanded folder structure rather than a single folder

From [email protected] on October 28, 2009 14:40:52

Currently the AMP plugin stores assets src/main/config in the following
folder structure in the AMP:

config/alfresco/module/com.acme.myextension

This causes problems when trying to classload resources that are stored in
the config folder - a problem that can be avoided by using a fully expanded
folder structure in the AMP file instead, ie:

config/alfresco/module/com/acme/myextension

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=26

Support for file-mapping.properties (Alfresco MMT feature)

From [email protected] on July 21, 2008 13:25:54

What steps will reproduce the problem? 1. put file-mapping.properties into root folder (beside module-properties)

I think it is not supported ?

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=5

Exception starting log4j.properties file on windows

From [email protected] on July 14, 2008 11:07:44

The project.build.directory variable has back-slashes in it. This doesn't
work with log4j. For now I have replaced the <webapp.log.dir/> with a
hardcoded path.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=1

wrong instructions to generate archetype

From [email protected] on June 25, 2009 06:51:14

on both http://repository.sourcesense.com/maven2-sites/maven-alfresco-amp-archetype/index.html and http://repository.sourcesense.com/maven2-sites/maven-alfresco-extension-archetype/index.html the instructions should read: mvn archetype:generate
-DarchetypeCatalog= http://repository.sourcesense.com/maven2 see also https://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=20&can=1&q=ResourceDoesNotExistException

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=24

noSnapshotVersion does not work in distributionManagement

From [email protected] on May 21, 2009 13:08:06

Using strip goal of v0.0.4 of maven-nosnapshot-plugin

I tried adding the ${noSnapshotVersion} into the
distributionManagement|site|url but it is not resolved during site-deploy.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=22

Archetype: should be referring to the AMP plugin v3.0.0

From [email protected] on October 28, 2009 14:45:48

Steps to reproduce:

1. run the following command:

• mvn archetype:generate
  -DarchetypeCatalog= http://repository.sourcesense.com/nexus/content/repositories/alfresco.public.releases/archetype-catalog.xml 2. enter the following values:
• Archetype: 1
• groupId: com.acme.test
• artefactId: test-amp
• version: 1.0-SNAPSHOT
• package: com.acme.test

Expected result:
The pom.xml refers to version 3.0.0 of the AMP plugin.

Actual result:
The pom.xml refers to version 2.0.0 of the AMP plugin.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=27

WAR files take precedence over AMP files

From [email protected] on December 14, 2009 14:01:53

The way AMP processing works when creating an Alfresco extension
application (I also copied that functionality to my Share POM) does not
work. The AMPs are extracted in the process-resources phase, then the WAR
(Alfresco web client or Share) is unpacked over it in the package phase.
The result is that files in the AMP are overridden by files in the WAR.
This is not correct.

I worked around this by unpacking the AMPs to
${project.build.directory}/work/amp and then adding that folder in the
webResources configuration for the WAR plugin.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=41

Share archetype does not overlay amps

From [email protected] on December 10, 2009 13:05:22

The DoD5015.2 module is available as two AMPs, one for the Alfresco web
client, one for Share. I would like to apply these with Maven. The
Alfresco extension war archetype handles overlaying AMP dependencies, but
the Share archetype does not. Please add support for this.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=38

Creating a amp-archetype with -SNAPSHOT as version number creates a invalid maven-amp.

From [email protected] on October 08, 2008 10:14:59

Doing a mvn create of -DarchetypeVersion=1.0.0
-DarchetypeArtifactId=maven-alfresco-amp-archetype with
-Dversion=0.1-SNAPSHOT seems to work. However it creates a broken maven-amp
environment. SNAPSHOT is a common maven idiom for projects versions that
are under development and should be supported.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=15

Branches cleanup

From carlo.sciolla on March 16, 2010 08:07:44

the branches folder contains stale/unused/experimental stuff that should be
rather moved in a more proper location (e.g. branches/experimental/...)

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=50

Alfresco 3.2r2 component .jars missing from maven.alfresco.com

From [email protected] on February 16, 2010 10:24:18

When searching for, e.g. alfresco-repository.jar within the new
repository, 3.2r2 artifacts don't seem to be available. http://maven.alfresco.com/nexus/index.html#nexus-search;quick~alfresco- repository

Am I looking in the wrong place or are they not there for a reason? If
not, would it be possible to add them?

Many thanks for making this available!

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=44

POM - wrong <desktop.action.package> for Alfresco 2.1.0

From [email protected] on May 05, 2009 05:11:33

What steps will reproduce the problem? 1. Open the pom.xml of maven-alfresco-extension-archetype-1.1.4.
2. Lookup these lines:

<desktop.action.package>org.alfresco.filesys.repo.desk</desktop.action.package>
3. It seems that these lines should be:

<desktop.action.package>org.alfresco.filesys.smb.server.repo.desk</desktop.action.package>

What do you think?

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=21

Cannot generate eclipse project files from maven-alfresco-amp-archetype

From [email protected] on July 14, 2008 11:09:18

Calling mvn eclipse:eclipse generates an empty .project file and no
.classpath file.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=3

Alfresco artifacts classifier should be specified as a property

From carlo.sciolla on January 26, 2010 08:51:43

What steps will reproduce the problem? 1. mvn archetype:generate your repo extension project
2. try to work against Alfresco 3.0c-labs What is the expected output? What do you see instead? The target Alfresco version will result as a 3.0c-labs-community, I want to be
able to completely override the classifier.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=43

AMP Plugin: src/main/config directory resource rules should be the default

From [email protected] on October 28, 2009 14:50:12

Currently in order for the AMP plugin to correctly store assets in
src/main/config in the config/ folder inside the AMP file, the following
resource block is required in the pom.xml:

<resource>
  <filtering>true</filtering>
  <directory>src/main/config</directory>
  <targetPath>alfresco/module/com.acme.test.test-amp</targetPath>
  <excludes>
    <exclude>**README-*</exclude>
  </excludes>
</resource>

Because the config/ folder is almost ubiquitous in AMP files, it would be
better if this was the default behaviour of the plugin, thereby simplifying
each and every pom.xml file.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=29

Cleanup of AMP archetype

From [email protected] on March 03, 2010 04:18:20

I found 2 issues in AMP archetype:

1. File archetype.xml is deprecated and should be removed for clarity
2. Java file are put in the wrong folder
   (com.mycompany.org.alfresco.demoamp instead of org.alfresco.demoamp)

Here is a patch to fix these issues.

Attachment: alfresco-maven-amp-cleanup.patch

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=47

depend on released plugin versions of artifacts

From [email protected] on December 07, 2009 05:57:23

What steps will reproduce the problem? 1. generate a new project from archetype What is the expected output? What do you see instead? the generated project should use the released versions of the plugins.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=33

Share archetype references lfresco.com

From [email protected] on December 07, 2009 17:25:14

The Share extension archetype creates a POM pointing to a repository at http://maven.lfresco.com/nexus/content/groups/public/ . This obviously
needs to be changed to alfresco.com.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=35

The test-integration goal doesn't make META-INF files available

From [email protected] on August 04, 2008 04:41:46

This is a problem for example when trying to package
web-client-config-custom.xml file into an AMP. See http://groups.google.com/group/maven-alfresco/browse_thread/thread/2208961ccc6ef065

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=8

AMP Archetype is using the old repository URLs

From [email protected] on October 28, 2009 14:47:30

Steps to reproduce:

1. run the following command:

• mvn archetype:generate
  -DarchetypeCatalog= http://repository.sourcesense.com/nexus/content/repositories/alfresco.public.releases/archetype-catalog.xml 2. enter the following values:
• Archetype: 1
• groupId: com.acme.test
• artefactId: test-amp
• version: 1.0-SNAPSHOT
• package: com.acme.test

Expected result:
The pom.xml contains the following repository URLs (for both artifact and
plugin repositories): http://repository.sourcesense.com/nexus/content/repositories/alfresco.public.releases/ Actual result:
The pom.xml contains the following repository URLs (for both artifact and
plugin repositories): http://repository.sourcesense.com/maven2

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=28

unified formatting and indenting of all source code

From [email protected] on December 07, 2009 05:39:17

I prefer having a unified formatting of the generated pom.xmls.
This includes the following

• deletion the extra ctrl-M-s on the end of the lines
• reformatted with eclipse using the 80 char print margin setting
• delete the | (pipe) characters from the comments.

Tib

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=32

Align to one clear repository layout

From [email protected] on August 04, 2008 05:30:15

Align archetypes, and sourcesense maven repo layout to a rational suggested
repository organization.

org.alfresco

|__ alfesco (webapp)

|__ alfresco-config

|__ alfresco-core

|__ alfresco-deployment

|__ alfresco-jndi-client

|__ alfresco-link-validation

|__ alfresco-mbeans

|__ alfresco-mmt

|__ alfresco-repository

|__ alfresco-remote-api

|__ alfresco-web-client

|__ alfresco-ws-client

|__ maven

| |__ archetypes

| | |__ maven-archetypes (Multi-module POM)

| | |__ maven-archetype-parent (POM)

| | |__ maven-alfresco-archetype

| | |__ maven-amp-parent

| |__ plugins

| |__ maven-plugins (Multi-module POM)

| |__ maven-plugin-parent (POM)

| |__ maven-amp-plugin

| |__ maven-mmt-plugin

|__ modules

| |__ record-mgt

| |__ trashcan-cleaner (forge)

|__ sdk

|__ alfresco-sdk-embeded (POM)

|__ alfresco-sdk-remote (POM)

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=9

Change naming of modules created by AMP archetype

From [email protected] on December 18, 2009 07:22:58

The modules are now named ${groupId}.${artifactID}, which results in a folder
containing dots in its name. This prevents resource properties from beeing
correctly loaded by the JVM.

Discussed here: http://groups.google.com/group/maven- alfresco/browse_thread/thread/969d66714d6d58fc What version of the product are you using? On what operating system? AMP-archetype version 1.0.0
Windows7

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=42

Cannot create the Eclipse project with the newest version of the Eclipse plugin

From carlo.sciolla on July 27, 2009 05:45:39

What steps will reproduce the problem? 1. Create the project with archetype:generate
2. run mvn eclipse:eclipse What is the expected output? What do you see instead? I expect a BUILD SUCCESSFUL, but instead it will fail with this message:

org.apache.maven.lifecycle.LifecycleExecutionException: Request to merge
when 'filtering' is not identical. Original=resource src/main/resources:
output=target/classes, include=[],
exclude=[/restore-context.xml|/ldap-.xml|__/.java], test=false,
filtering=false, merging with=resource src/main/resources:
output=target/classes,
include=[log4j.properties|alfresco/extension/file-servers-custom.xml],
exclude=[*/.java], test=false, filtering=true

This is due to some different behaviors between the newest version of the
eclipse plugin (2.7) and the old ones. Either force the use of the 2.6
version of the maven eclipse plugin or try to sort out the issue.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=25

Dependent AMPs can't be deployed to Alfresco extension WAR on windows

From [email protected] on October 15, 2008 06:41:13

See these threads http://groups.google.com/group/maven- alfresco/browse_thread/thread/4cf30e77dc9809f6 http://groups.google.com/group/maven- alfresco/browse_thread/thread/4f5a5e03be2f299b

Errors are
String index out of range: 0

And /lib and /config folders in the AMP ending up in the wrong place in the
war.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=16

Add support for Alfresco v3.x

From [email protected] on October 16, 2008 11:12:14

Now that Alfresco Labs 3 is out it would be good if extensions and amps
could be easily switched between 2.x and 3.x systems. There are some
problems with class renames between Alfresco versions that can make this a
little tricky.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=17

Broken dependencies

From carlo.sciolla on February 27, 2010 15:50:04

What steps will reproduce the problem? 1. mvn archetype:generate using archetype catalog in maven.alfresco.org
2. cd to the newly created project folder
3. mvn install

What is the expected output?
BUILD SUCCESFUL

What do you see instead?
[ERROR] BUILD ERROR

[INFO] --------------------------------------------------------------------

[INFO] Failed to resolve artifact.

Missing:

1. org.alfresco.maven.plugin:maven-amp-plugin:jar:3.0.1-SNAPSHOT

Still to be tested if this is still the case in trunk.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=46

META-INF created in AMPs root folder

From [email protected] on February 12, 2009 06:31:53

I want to add some specific files like faces-config.xml in the JAR
generated for my AMP file.

I create src/main/resources/META-INF folder in my maven project and put
faces-config.xml there. When I run "mvn package", the file really ends up
in JAR META-INF folder.

However, another META-INF folder is also created in root folder of AMP
package, with the same faces-config.xml file. When I install such AMP to my
alfresco.war, I can see faces-config.xml in the following directory:

alfresco/WEB-INF/classes/META-INF

I think that this behaviour is wrong.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=19

AMP archetype should depend on a common base to facilitate upgrades

From [email protected] on September 16, 2008 12:08:20

The current pom.xml provided by the AMP archetype is intimidating for new
users because it is so large. Also, improvements to the pom have to be
manually added to existing modules.

Atlassian archetypes use a base pom with all the common functionality
resulting in a much smaller project pom for end users. http://confluence.atlassian.com/display/DEVNET/Atlassian+Plugin+Archetypes I'm going to look at splitting the amp archetype pom into a base pom in the
same way that atlassian do. I'll do this in a branch.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=13

Module ID is not consistent in AMP archetype

From [email protected] on March 03, 2010 06:16:11

In module.properties there is:
module.id=${pom.artifactId}

In src/main/config/service-context.xml there is:

This lead to issue when deploying AMP:
11:29:35,927 INFO [repo.module.ModuleServiceImpl] Found 1 module(s).
11:29:37,552 INFO [repo.module.ModuleServiceImpl] Installing module
'myamp' version 1.0.1.
11:29:38,130 ERROR [repo.module.ModuleComponentHelper] The component
'myamp.exampleComponent' belongs to a non-existent module
'com.mycompany.myamp'.

Please also note that pom.* properties are deprecated and you should use
project.*

See attached patch.

Attachment: alfresco-maven-amp-moduleId.patch

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=48

Add Share 3.3+ JAR Extensions packaging support

From [email protected] on February 23, 2010 13:11:33

What steps will reproduce the problem? 1. As Share 3.3+ Share modules can be built as JARs (see http://blogs.alfresco.com/wp/kevinr/2010/01/28/alfresco-share-33-extensions-and-springsurf/ )
2. Add a maven-alfresco-share-module-archetype producing a JAR (and add
sample dashlet inside)
3. Test a maven-alfresco-share-archetype generated project depending on a
maven-alfresco-share-module-archetype generated module to test that dashlet
is actualy deployed

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=45

mAmpResources aren't processed

From [email protected] on June 17, 2009 05:06:27

In my project, I declare some mAmpResources to be processed:


src/main/myfolder
myfolder
true

I think the bug may come from the AmpProjectPackagingTask constructor,
which doesn't handle properly the webResource(s?) parameter.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=23

Maven fails to download alfresco dependencies

From [email protected] on February 19, 2009 14:39:38

What steps will reproduce the problem? 1. Create the archetype according to instructions
2. mvn package What is the expected output? What do you see instead? I see this (elided) output:

Downloading: http://repository.sourcesense.com/maven2/alfresco/community/alfresco/2.1.0/alfresco-2.1.0.war ...

Missing:

1. alfresco.community:alfresco:war:2.1.0

I can see why this is failing: the war file on the sourcesense repository
is named alfresco-2.1.0-labs.war.

I have the same problem with 3.0Stable. What version of the product are you using? On what operating system? archetype version is 1.1.0 Please provide any additional information below.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=20

Merge application.properties and alfresco-global.properties

From [email protected] on December 09, 2009 11:32:34

What steps will reproduce the problem? 1. At the moment the archetype uses the
src/main/properties//application.properties as main configuration file
for the webapp
2. Since 3.2 Alfresco introduced alfresco-global.properties (see
src/main/resources/alfresco-global.properties) of the generated
maven-alfresco-extension-archetype for a customizable version of it
3. We need to align this 2 mechanisms

What is the expected result?
Having only one runtime properties configuration mechanism which maximizes
the usage of Alfresco standard functionalities.

Solution?
Just move the alfresco-global.properties to src/main/properties/
(making it environment switchable) and remove unnecessary spring property
beans from default sample *-context.xml in
src/main/resources/archetype-resources/src/main/resources/alfresco/extension

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=37

missing wagon-http-shared:jar version 1.0-beta-6-patched

From [email protected] on December 07, 2009 06:21:14

What steps will reproduce the problem? 1. check out maven-alfresco-archetypes project
2. mvn compile What is the expected output? What do you see instead? The build fails, because it cannot find the wagon-http-shared.jar with
version 1.0-beta-6-patched.
Searching on http://maven.alfresco.com/nexus/index.html#nexus-search;quick~wagon-http-shared find no such version. I
found a 1.0-beta-7-SNAPSHOT version in the apache snapshots repository, but
not sure if this contains the necessary patches.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=34

AMP plugin does not obey file-mapping.properties

From [email protected] on December 10, 2009 14:56:48

I have an AMP (DoD5015.2 Share AMP) that has a file-mapping.properties in
it. The AmpUnArchiver does not look at this file when creating a mapping.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=39

Test not possible in amp plugin

From [email protected] on September 26, 2008 14:48:00

What steps will reproduce the problem? 1. mvn test

Does not invoke maven-surefire-plugin.

Solution:
Bind properly phases in components.xml ;)

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=14

Document is unclear on use of -SNAPSHOT version numbers

From [email protected] on July 14, 2008 14:36:36

There is a note in pom.xml that says Alfresco doesn't support alpha
characters in AMP version numbers. Its not clear from this note why this is
the case and whether it is possible to use Maven snapshoting. A recommended
solution should be added to this comment..

<!-- No shapshot or beta version, as this is used for filtering

module.properties

As in http://wiki.alfresco.com/wiki/Developing_an_Alfresco_Module :

"The version number must be made up of numeric values separated by dots.

For example '2.1.56' is a valid version number, '2.3.4a' is not. "

If you want to use (and I do) maven snapshot capabilities than you could
remove the filtering and maintaining versions (pom and module.properties)

aligned manually

-->

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=4

web script packing: what is the correct way to pack them ?

From [email protected] on July 21, 2008 13:40:14

What steps will reproduce the problem? 1. put webscripts into
/src/main/resources/alfresco/extension/templates/webscripts/...
2. mvn package puts them into
module-1.0.amp/lib/module-1.0.jar/alfresco/extension/templates/webscripts/...
AND into module-1.0.amp/config/alfresco/extension/templates/webscripts/...

Is it corrent, that the files end up in both places?

Affected:
amp version 2.0 (11.th Juli)

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=6

package of DemoComponent.java

From [email protected] on August 07, 2008 09:51:56

What steps will reproduce the problem? 1. Created an amp archetype with groupId hu.codwell.kmm.amp
2. The archetype created a DemoCompoent.java in
src/main/java/hu/codwell/kmm/amp/com/sourcesense/demoamp What is the expected output? What do you see instead? The DemoComponent should have been created in hu.codwell.kmm.amp package. What version of the product are you using? On what operating system? 1.0 linux

Tib

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=11

Move to maven.alfresco.com Alfresco hosted infra

From [email protected] on December 02, 2009 06:29:07

Migrate the whole release process to maven.alfresco.com

This means:

• (optionally) change package (org.alfresco)
• change repositories and distributionManagement
• maven-sql-plugin
• enforcer (maven 2.2.1)
• maven amp buildnumber fix to 1.0-beta-2 (due to incompatibility problems)
• remove filtering of classes in amp plugin (broken compilation)
• update changes.xml
• update site docs
• update alfresco wiki

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=30

Allow customization of alfresco.db.username and alfresco.db.password in POM file

From [email protected] on July 14, 2008 11:08:47

I want to be able to override the default alfresco:alfresco credentials for
MySQL. I have added this to the POM which seems to work..

<alfresco.db.username>username</alfresco.db.username>
<alfresco.db.password>password</alfresco.db.password>

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=2

Update AMP archetype to have a JNDI datasource in Jetty

From [email protected] on March 04, 2010 03:19:34

The AMP archetype is supposed to use a MySql database, but running
mvn integration-test -Pwebapp
fails as there is no datasource configured in Jetty.

I'll try to write a patch to improve archetype to include jetty-env.xml
with correct datasource.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=49

FTL contents are destroyed: module title appears at strange places!

From [email protected] on July 26, 2008 13:04:35

What steps will reproduce the problem? 1. create folder-properties.get.json.ftl and put it into
src\main\resources\alfresco\extension\templates\webscripts\ of a module

folder-properties.get.json.ftl contains:
[
<#list result as res>
{"name": "${res.name}", "title": "${res.title}", "text":"${res.text}",
"allowedValues" : [
<#list res.allowedValues as av>
"${av}"
<#if av_has_next>,</#if>
</#list>
]}
<#if res_has_next>,</#if>
</#list>
]

Wrong result:
[
<#list result as res>
{"name": "Maven Alfresco AMP Packaging Sample", "title": "${res.title}",
"text":"${res.text}", "allowedValues" : [
<#list res.allowedValues as av>
"${av}"
<#if av_has_next>,</#if>
</#list>
]}
<#if res_has_next>,</#if>
</#list>
]

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=7

Share archetype: can't find application.properties when build invoked from parent

From [email protected] on December 07, 2009 17:37:56

I have a Share extension project that is a module of a parent project.
When I invoke the build from the module directory, it works fine, but when
I invoke it from the parent directory, I get the following error:

Caused by: org.apache.maven.plugin.MojoExecutionException: Error loading
property file 'src/main/properties/local/application.properties'
at
org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:450)
at
org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:394)
at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:195)
at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:157)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Error
loading property file 'src/main/properties/local/application.properties'
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperties(DefaultMavenFileFilter.java:265)
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFilterWrappers(DefaultMavenFileFilter.java:143)
at
org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:442)
... 22 more
Caused by: java.io.FileNotFoundException:
src/main/properties/local/application.properties
at
org.apache.maven.shared.filtering.PropertyUtils.loadPropertyFile(PropertyUtils.java:65)
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperties(DefaultMavenFileFilter.java:260)

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=36

jetty-maven-plugin upgrade

From [email protected] on December 14, 2009 09:19:37

I think the archetypes should be upgraded to use the new jetty-maven-plugin
instead of the old maven-jetty-plugin. Actually I upgraded and both the
extension and the amp archetype works fine with the new jetty plugin, so I
might commit this change back.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=40

Google Code skipped issue 18

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=18