[
https://issues.apache.org/jira/browse/DRILL-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085998#comment-17085998
]
ASF GitHub Bot commented on DRILL-7708:
---------------------------------------
paul-rogers commented on pull request #2061: DRILL-7708: Downgrade maven from
3.6.3 to 3.6.0
URL: https://github.com/apache/drill/pull/2061
# [DRILL-7708](https://issues.apache.org/jira/browse/DRILL-7708): Downgrade
maven from 3.6.3 to 3.6.0
## Description
Thanks to @arina-ielchiieva for recently upgrading 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. This PR adjusts the required Maven version to 3.6.0.
## Documentation
Maven 3.6.0 is required to build Drill.
## Testing
Ran the full build.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
