Github user ChristianSchulte commented on the pull request:

    https://github.com/apache/maven/pull/32#issuecomment-67625161
  
    Maybe the proper solution would be to control this behaviour based on an 
attribute of the lifecycle ? So a lifecycle can be flagged as producing 
artifacts or as consuming artifacts. Lifecycles producing artifacts behave like 
Maven 3. Lifecycles consuming artifacts behave like Maven 2.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to