You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Dobes Vandermeer (Jira)" <ji...@apache.org> on 2020/04/17 19:08:00 UTC
[jira] [Commented] (DRILL-7708) Downgrade maven from 3.6.3 to 3.6.0
[ https://issues.apache.org/jira/browse/DRILL-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085994#comment-17085994 ]
Dobes Vandermeer commented on DRILL-7708:
-----------------------------------------
Another workaround is to install maven yourself into your home directory and run it from there, I think that's pretty common.
> Downgrade maven from 3.6.3 to 3.6.0
> -----------------------------------
>
> Key: DRILL-7708
> URL: https://issues.apache.org/jira/browse/DRILL-7708
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.18.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Major
> Fix For: 1.18.0
>
>
> DRILL-7704 upgraded Drill's Maven version to 3.6.3.
> As it turns out, I use Ubuntu (Linux Mint) for development. Maven is installed as a package using apt-get. Packages can lag behind a bit. The latest maven available via apt-get is 3.6.0.
> It is a nuisance to install a new version outside the package manager. I changed the Maven version in the root pom.xml to 3.6.0 and the build seemed to work. Any reason we need the absolute latest version rather than just 3.6.0 or later?
> The workaround for now is to manually edit the pom.xml file on each checkout, then revert the change before commit. This ticket requests to adjust the "official" version to 3.6.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)