[
https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588633#comment-15588633
]
Robert Munteanu commented on SLING-6103:
----------------------------------------
We can do this in two ways:
1) add a 'goals' setting, which overrides the global one
The advantage is that we have full control. The disadvantage is that it does
not play nicely with the 'deploy only once' logic
{code:groovy}
goals(deploy ? "-U clean deploy" : "-U clean verify");
{code}
2) Add an 'extraArguments' setting, which is appended to the global goals
The advantage is that it plays nicely with the 'deply only once' logic, but the
disadvantage is that you can't override the full command line. But OTOH that is
not necessary now.
I have a slight preference for 2), but I can also see 1) working.
> crankstart-launcher ITs fail when executed in isolation (on Jenkins)
> --------------------------------------------------------------------
>
> Key: SLING-6103
> URL: https://issues.apache.org/jira/browse/SLING-6103
> Project: Sling
> Issue Type: Bug
> Components: Crankstart
> Reporter: Robert Munteanu
> Assignee: Bertrand Delacretaz
> Labels: sling-IT
>
> When building on Jenkins SNAPSHOT dependencies can't be found. I assume that
> this is because they haven't been installed in the local repository and the
> IT does not look in the apache snapshots repository.
> In that case, it should be similar to SLING-6080 and SLING-6074.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)