[
https://issues.apache.org/jira/browse/CASSANDRA-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-5532:
---------------------------------------
Attachment: 0001-Remove-antcall-around-m-a-t-retrieve-build.patch
Patch to revert the antcall wrapping around maven-ant-tasks-retrieve-build.
I've added the check on without.maven directly to the target which seems to me
to have the desired effect as the original patch
> Maven package installation broken by recent build changes
> ---------------------------------------------------------
>
> Key: CASSANDRA-5532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5532
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 2.0
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Attachments: 0001-Remove-antcall-around-m-a-t-retrieve-build.patch
>
>
> CASSANDRA-3818 provides the ability to disable maven ant tests during the
> build. Part of the change is to refactor the maven-ant-tasks-retrieve-build
> target to wrapped by an antcall, with a guard condition to check if m-a-t
> should be used. The use of antcall causes the target & those targets it
> depends on to be called in a separate scope to the main build, which
> unfortunately means that the repository refs and ant macros which get defined
> there are not available once the antcall is completed. The final effect is
> that the mvn-install task fails as the install macro is not defined in its
> scope, and the artifacts task fails due to the repository refs being
> similarly undefined. I haven't tried it, but I suspect the publish task would
> be affected in the same way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
