Re: Modernizing plugin dependencies

There has been a (short) discussion on this topic recently in this list [1]. Although it contained no formal vote, my provisional conclusion would be to create a JIRA ticket and then provide a merge request. Thanks, Maarten [1] https://lists.apache.org/thread.html/r3b921993565a04ea0c20e6439d

Modernizing plugin dependencies

What's current best practice for updating the versions of the test harness and other bits and bobs?

Re: Merging via GitHub

I have checked it out with all three enabled in [1] but i still see the same number of buttons as before. How it should behave? I would like to have the rebase even in the squash but the comment above the "rebase: true" says "button" and not a "behavior" in another buttons e.g, "Squash and merge".

Re: Maven Shade and MSHADE-352 (timestamp support), mitigate the breaking change of last release

Perfect, merci Hervé ;). Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: Maven Shade and MSHADE-352 (timestamp support), mitigate the breaking change of last release

Hi, I created MSHADE-363 Jira issue and did a fix in corresponding Git branch, implementing exactly your strategy, even if I called the new interface "ReproducibleResourceTransformer" instead of TimeAware... :) I just transformed the Git branch into a PR to get review: https://github.com/apache

Re: Merging via GitHub

it can be configured at ASF with .asf.yaml setting: https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Mergebuttons Le mardi 12 mai 2020, 00:45:31 CEST David Jencks a écrit : > It's possible to configure GitHub to allow

Maven Shade and MSHADE-352 (timestamp support), mitigate the breaking change of last release

Hi everyone, Wonder if we can't mitigate the breaking change in the last minor of shade plugin (due to MSHADE-352). Idea would be to have a TimeAwareResourceTransformer extends ResourceTransformer and handle an instanceof or equivalent in our codebase to avoid to break all transformers outside ma

Re: Maven in python

Hi Vikas, If you really want to use Apache Maven to build a python project (it is not really done for it) you have two main options: 1. Use jython and maven integrations ( http://mavenjython.sourceforge.net/compile/) 2. Just disable default maven lifecycle and use exec maven plugin to launch virt

Re: Maven in python

Hi Vikas, I think you should contact the developer of the other 'maven': https://github.com/john-sandall . His email is listed there. But this 'maven' provides easy access to open datasets in both raw and model-ready formats, with usages for UK elections and Cov