Issue 119 in maven-alfresco-archetypes: enable-profile-testing Profile activation

[maven-alfres...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 119 by mauri...@session.it: enable-profile-testing Profile
activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

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>

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[maven-alfres...@googlecode.com]

Updates:
Labels: Milestone-Release-sdk-1.1.0

Comment #1 on issue 119 by colum...@gmail.com: enable-profile-testing
Profile activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

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) ?

[maven-alfres...@googlecode.com]

Updates:
Owner: maurizio...@alfresco.com

Comment #2 on issue 119 by colum...@gmail.com: enable-profile-testing
Profile activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

(No comment was entered for this change.)

[maven-alfres...@googlecode.com]

Comment #3 on issue 119 by colum...@gmail.com: enable-profile-testing
Profile activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

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

[maven-alfres...@googlecode.com]

Issue 119: enable-profile-testing Profile activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

This issue is now blocking issue maven-alfresco-archetypes:151.
See http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=151

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[maven-alfres...@googlecode.com]

Updates:
Status: WontFix

Comment #5 on issue 119 by maurizio...@alfresco.com: enable-profile-testing
Profile activation
http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=119

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