Hi Christian,
Ok first activation problem looks like being solved I've retested this
with my example project...Thanks for fixing that...
But what is unclear to me why during the run information from another
profile in particular the one which is defined in the parent of my
echo-maven-plugin will leak into my example project? (Described in the
issue MNG-6070)...I never thought profiles used in a plugin could have
influence into my own project which only use those plugins? But those
profiles are read....
The questions is profiles are read which are in the plugins which I'm
using in my project...that sounds like they are not clearly separated....
?
Kind regards
Karl Heinz
On 7/23/16 8:20 PM, Christian Schulte (JIRA) wrote:
[
https://issues.apache.org/jira/browse/MNG-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-6070:
-----------------------------------
Summary: Default profile in settings.xml must not use an id possibly
already in use. (was: [REGRESSION] Profile activation based on a property
does not work correctly)
Default profile in settings.xml must not use an id possibly already in use.
----------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
