[
https://issues.apache.org/jira/browse/OAK-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226035#comment-15226035
]
Davide Giannella commented on OAK-4136:
---------------------------------------
Maven does not allow to enable profiles from within profiles.
We have two approaches for having a release profile that will ease the
command line for performing a full coverage test:
# create a profile where manually we enable all the plugin
# create a java property (ie: {{-Drelease=true}}) and use such to
activate multiple profiles.
The {{integrationTesting}} profiles already makes use of the
activation by property (OAK-163)
{noformat}
<activation>
<property>
<name>env.OAK_INTEGRATION_TESTING</name>
</property>
</activation>
{noformat}
https://github.com/apache/jackrabbit-oak/blob/b071fab9e8f4b7fac3742ffd598590109d36de95/oak-parent/pom.xml#L566
It seems this property fell in disuse
(http://oak.markmail.org/thread/4qwtq2mckmsauowk).
Will try property approach first.
/cc [~chetanm], [~jukkaz]
> release profile in maven
> ------------------------
>
> Key: OAK-4136
> URL: https://issues.apache.org/jira/browse/OAK-4136
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Davide Giannella
> Assignee: Davide Giannella
> Fix For: 1.6
>
>
> Create a maven profile (ie {{-Prelease}}) which will take care of
> enabling all the required profiles as well as injecting the right
> maven variables.
> So far
> {noformat:title=profiles to be activated}
> pedantic
> integrationTesting
> unittesting
> rdb-derby
> {noformat}
> {noformat:title=variables to be injected}
> nsfixtures=
> rdb.jdbc-url=jdbc:derby:foo;create=true
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
