search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

AMP archetype issues after building the AMP #95

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm trying to use the AMP archetype and I noticed that:

1. it creates a file-mappings.properites file in the root of the AMP (!?)

2. it seems that the created AMP doesn't work correctly when applied to Alfresco

For the first point I think that the correct name for the file should be 
file-mapping.properties, but how I can manage this file?
How can I remove this from AMP?
How can I put my own file-mapping.properties?

For the second point trying to put some resources in the module of the AMP, I 
mean config/alfresco/module/myModule/*, MMT doesn't copy all the needed 
resources inside the Alfresco WAR in the same folder structure.

What could be the problem here?

Thank you for your support.

Original issue reported on code.google.com by piergiorgiolucidi on 28 Jun 2012 at 7:53

GoogleCodeExporter commented 9 years ago 
I see that in my Alfresco WAR, MMT will put only module.properties file...

Original comment by piergiorgiolucidi on 28 Jun 2012 at 7:56

GoogleCodeExporter commented 9 years ago 
Ok so the built AMP is correct, I tried to install it manually and it works!

But I think that there is a problem with the overlay process that it seems 
broken using "mvn clean install -P webapp".

Original comment by piergiorgiolucidi on 28 Jun 2012 at 8:26

GoogleCodeExporter commented 9 years ago 
Changing the version of the maven-war-plugin to 2.1.1 fix this problem and the 
overlay works fine!
So probably the AMP archetype (3.9.1) should set 2.1.1 as the default version 
of the maven-war-plugin.

Hope this helps.

Original comment by piergiorgiolucidi on 3 Jul 2012 at 11:16

GoogleCodeExporter commented 9 years ago 
The file-mappings.properties file is required in order to deploy assets into 
WEB-INF (e.g. web.xml).  Although rarely required and NOT recommended, there 
are times when this is necessary and the default MMT file mappings do not allow 
this by default.

Please see 
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=5 for more 
details on why this is happening (and indeed, must continue to happen).

Original comment by pmo...@gmail.com on 3 Jul 2012 at 8:45

GoogleCodeExporter commented 9 years ago 
With the final release of Maven Alfresco SDK 1.0 and the alfresco-maven-plugin 
0.7 file-mappings.properties can be added in the sources at:

src/main/amp/file-mappings.properties

On the install side instead, we embed now MMT so we behave "exactly" as 
Alfresco MMT does.

Scheduling fix version 1.0.0 of the SDK and solving the issue.

Original comment by colum...@gmail.com on 30 Oct 2012 at 12:29

GoogleCodeExporter commented 9 years ago 
Shouldn't the file-mapping file be named file-mapping.properties, not 
file-mappings.properties? 
https://wiki.alfresco.com/wiki/AMP_Files#Customising_the_structure_of_an_AMP_fil
e

Original comment by w...@jonesgeeks.com on 19 Nov 2012 at 9:03