search

DPascalBernard / maven-alfresco-archetypes

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

enable-profile-testing Profile activation #119

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The alfresco-sdk-parent defines a profile as follows

<profile>
  <id>enable-alfresco-testing</id>
  <activation>
    <file>
      <exists>src/test/java</exists>
    </file>
  </activation>
  ....

Since a multi-module project (whose parent is defined as alfresco-sdk-parent) 
may contain also modules that are not Alfresco-related but containing 
src/test/java, we need to specialise the activation.

A simple solution would be to define activation as follows

<activation>
  <file>
    <exists>src/test/java</exists>
  </file>
  <file>
    <exists>src/main/amp/module.properties</exists>
  </file>
</activation>

Original issue reported on code.google.com by mauri...@session.it on 26 Mar 2013 at 2:47

GoogleCodeExporter commented 9 years ago 
So we enable that only for AMPs. Makes sense to merge it in the enable-amp 
profile? Or keep it separate so it can be disabled explicitly (e.g. by 
!enable-testing) ?

Original comment by colum...@gmail.com on 21 Jun 2013 at 11:11

GoogleCodeExporter commented 9 years ago

Original comment by colum...@gmail.com on 3 Nov 2013 at 1:54

GoogleCodeExporter commented 9 years ago 
Quoting upstream issue "http://jira.codehaus.org/browse/MNG-4565" , "Multiple 
profile activation conditions does not work" ...

Original comment by colum...@gmail.com on 3 Nov 2013 at 1:55

GoogleCodeExporter commented 9 years ago

Original comment by colum...@gmail.com on 3 Nov 2013 at 2:00

GoogleCodeExporter commented 9 years ago 
The "enable-alfresco-testing" profile should not affect any jar testing 
execution (other than adding dependencies to the classpath).

Original comment by maurizio...@alfresco.com on 3 Nov 2013 at 2:40