You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "apache maillist (JIRA)" <ji...@apache.org> on 2016/11/30 00:09:58 UTC

[jira] [Closed] (OWC-4) After switching from Maven 2 to Maven 3, extending Maven with Ant stops working

     [ https://issues.apache.org/jira/browse/OWC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

apache maillist closed OWC-4.
-----------------------------
    Resolution: Invalid

> After switching from Maven 2 to Maven 3, extending Maven with Ant stops working
> -------------------------------------------------------------------------------
>
>                 Key: OWC-4
>                 URL: https://issues.apache.org/jira/browse/OWC-4
>             Project: ODE Web Console
>          Issue Type: Bug
>            Reporter: apache maillist
>
> We extended Maven with Ant and while it works fine with Maven2, once switching to Maven3, the following error shows:
> [DEBUG] -- end configuration --
> [DEBUG] The following standard Maven Ant-mojo support objects could not be created:
> -  Maven parameter expression evaluator for Ant properties.
> Maven project, session, mojo-execution, or path-translation parameter information is 
> missing from this mojo's plugin descriptor.
> Perhaps this Ant-based mojo depends on maven-script-ant < 2.1.0, or used maven-plugin-tools-ant < 2.2 during release?
> Which I assume causes none of the properties from Maven profiles are taken effect via -PprofileName, only works if providing via -Dname=value would be taken effect



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)