[
https://issues.apache.org/jira/browse/YETUS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481332#comment-16481332
]
Allen Wittenauer commented on YETUS-635:
----------------------------------------
This sort of came up in SOLR-10912. The team was confused by javac not working
when compile was disabled. That's a lot less obvious than maven vs maven site.
In other words, we have a lot of plugins that actually have dependencies on
other plugins being enabled. Currently, there is no dependency system in
place. I'm not sure if we are at a point where it makes sense to build one,
but this is clearly causing end users difficulty.
It's tempting to say that this should just auto-add the maven plugin when a
dependent plugin is enabled but I'm not sure if the architecture allows that.
> Maven plugin should fail when partially enabled
> -----------------------------------------------
>
> Key: YETUS-635
> URL: https://issues.apache.org/jira/browse/YETUS-635
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Affects Versions: 0.6.0, 0.7.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: YETUS-635.0.patch, YETUS-635.1.patch
>
>
> The maven build plugin defines two additional test types: mvnsite and
> mvninstall. Currently, users can say they want to enable these tests without
> also stating they want the maven plugin enabled. This can lead to
> nonintuitive failures because those tests rely on command line arguments that
> are only handled by the maven plugin.
> This came up in HBASE-20591, because the HBase project was attempting to have
> parallel test runs to cover unit tests with different dependency options and
> had 'mvninstall' without 'maven' result in failures due to stomping on the
> default maven repo.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
