Keep the version rules in versions-maven-plugin #157

khmarbaise · 2017-05-28T07:44:11Z

If you need the rules.xml or the versions rules of versions-maven-plugin please vote into this ticket.
So I can see if really someone is using this. Otherwise this will be removed with version 3.0.0 of versions-maven-plugin.

The text was updated successfully, but these errors were encountered:

binkley · 2017-06-04T11:45:35Z

I use rules.xml to selectively control uses of milestone (M) and release candidate (RC) versions. I have several projects which are for trying out combinations of "cutting edge" projects to find incompatibilities during their development. Examples include Spring projects and Kotlin.

khmarbaise · 2017-06-04T11:56:55Z

First thanks for your feedback. Can you give some example how to use the rules.xml file? Cause I never used it at all...

Stephan202 · 2017-06-04T13:48:27Z

We use it i.c.w. with a script that we frequently run to check for version updates. We use the XML file to suppress suggested updates that we're not interested in. The file currently looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<ruleset xmlns="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" comparisonMethod="maven" xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0 https://mojo.codehaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd">
    <ignoreVersions>
        <ignoreVersion type="regex">.*[aA]lpha.*</ignoreVersion>
    </ignoreVersions>
    <rules>
        <rule groupId="com.google.guava">
            <ignoreVersions>
                <ignoreVersion type="regex">.*-android</ignoreVersion>
            </ignoreVersions>
        </rule>
        <rule groupId="com.hazelcast">
            <ignoreVersions>
                <ignoreVersion type="regex">.*-EA</ignoreVersion>
            </ignoreVersions>
        </rule>
        <rule groupId="commons-collections">
            <ignoreVersions>
                <ignoreVersion type="regex">200[34].*</ignoreVersion>
            </ignoreVersions>
        </rule>
        <rule groupId="javax.servlet">
            <ignoreVersions>
                <ignoreVersion type="regex">.*-b\d+</ignoreVersion>
            </ignoreVersions>
        </rule>
        <rule groupId="org.jvnet.jaxb2_commons">
            <ignoreVersions>
                <ignoreVersion>1.11.1</ignoreVersion>
                <ignoreVersion>1.11.1-PUBLISHED-BY-MISTAKE</ignoreVersion>
            </ignoreVersions>
        </rule>
        <rule groupId="org.postgresql">
            <ignoreVersions>
                <ignoreVersion type="regex">.*\.jre[67]</ignoreVersion>
            </ignoreVersions>
        </rule>
    </rules>
</ruleset>

I would prefer to see this functionality be part of the plugin's "in-POM" configuration, though. Cause right now we do this:

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>versions-maven-plugin</artifactId>
    <version>2.4</version>
    <configuration>
        <rulesUri>file://${basedir}/version-number-rules.xml</rulesUri>
    </configuration>
</plugin>

But that means the versions:display-dependency-updates and versions:display-plugin-updates goals must be executed in the context of the project's root pom.xml.

binkley · 2017-06-05T14:48:35Z

@khmarbaise Here is the file I use to stay on "dev" builds of Kotlin, rather than revert to older milestones:

<ruleset comparisonMethod="maven"
             xmlns="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                      xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0 http://mojo.codehaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd">
    <rules>
        <rule groupId="org.jetbrains.kotlin">
            <ignoreVersions>
                <ignoreVersion type="regex">.*-M.*</ignoreVersion>
            </ignoreVersions>
        </rule>
    </rules>
</ruleset>

The default rules for the maven plugin don't understand JetBrains' idiosyncratic choices for versioning. :)

An example "dev" version: 1.1.4-dev-530.

An example milestone version: 1.1-M04.

More examples here: https://mvnrepository.com/artifact/org.jetbrains.kotlin/kotlin-stdlib

binkley · 2017-06-05T15:17:54Z

I tested something. Removing the rules file, I still get the desired behavior. Running versions:update-properties does not revert to an older kotlin dependency. I do not know if this is the result of an intentional change, or a happy accident that might work differently as more Kotlin versions come out.

See mojohaus/versions#157.

mattnelson · 2017-06-05T16:43:16Z

Using the use-latest-versions and update-properties goals in combination with a custom script[1] to configure the entire dependency tree in the dependencyManagement section. This allows us to inherit updates to deep transitive dependencies which enables Gemfile.lock like functionality. I would still like the ability to configure the rules either via external file or inline in the pom.

[1] https://gist.github.com/mattnelson/3225aac8ec3be4db7194
[2] https://gist.github.com/mattnelson/5fe6c2bc84a0ffc48dcb17d3bc99f133
[3] https://stackoverflow.com/questions/27016865/gemfile-lock-equivalent-in-maven-and-gradle

famod · 2017-06-06T08:35:54Z

We do check for external dependency updates across our entire project via a maven profile. In this profile we reference a rules.xml to filter out inappropriate version:

<ruleset comparisonMethod="maven"
         xmlns="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0 http://mojo.codehaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd">
  <ignoreVersions>
    <ignoreVersion type="regex">(?i).*[-_\.]CR[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*[-_\.]rc[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*[-_\.]beta[0-9\.-]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*[-_\.]alpha[0-9\.-]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*[-_\.]nightly[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*[-_\.]jboss[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*-atlassian-[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">(?i).*-jenkins-[0-9\.]*</ignoreVersion>
    <ignoreVersion type="regex">.*[-\.]redhat-[0-9]+</ignoreVersion>
    <ignoreVersion type="regex">\d{4,}.*</ignoreVersion>  <!-- z.B. commons-collections:commons-collections ... 3.2.1.redhat-7 -> 20040117.000000 -->
  </ignoreVersions>
  <rules>
    <rule groupId="org.slf4j" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-xwiki</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.apache.maven.plugins" artifactId="maven-surefire-plugin" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>9c6abc2</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.codehaus.mojo" artifactId="properties-maven-plugin" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-tc</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="javax.portlet" artifactId="portlet-api" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-r\d+</ignoreVersion>
        <ignoreVersion type="regex">.*-Draft\d+</ignoreVersion>
      </ignoreVersions>
    </rule>
  </rules>
</ruleset>

rsiggi · 2017-06-06T12:10:09Z

We use jdk7 and always more libraries need jdk8 to work.
this is our version.xml. First exclude many old apache stuff and then the jdk depends.

<ruleset comparisonMethod="maven"
         xmlns="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0 http://mojo.codehaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd">
  <rules>
    <rule groupId="ant-contrib" artifactId="ant-contrib" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20020829</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-beanutils" artifactId="commons-beanutils" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20030211.134440</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-cli" artifactId="commons-cli" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20040117.000000</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-collections" artifactId="commons-collections" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20040616</ignoreVersion>
        <ignoreVersion>20040102.233541</ignoreVersion>
        <ignoreVersion>20031027.000000</ignoreVersion>
        <ignoreVersion>20030418.083655</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-configuration" artifactId="commons-configuration" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20041012.002804</ignoreVersion>
        <ignoreVersion>20041012.002623</ignoreVersion>
        <ignoreVersion>20040121.140929</ignoreVersion>
        <ignoreVersion>20030706.202021</ignoreVersion>
        <ignoreVersion>20030620.073343</ignoreVersion>
        <ignoreVersion>20030311.152757</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-dbcp" artifactId="commons-dbcp" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20030825.184428</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-io" artifactId="commons-io" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20030203.000550</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="commons-lang" artifactId="commons-lang" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20030203.000129</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="dom4j" artifactId="dom4j" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>20040902.021138</ignoreVersion>
        <ignoreVersion type="regex">.*-.*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.beanio" artifactId="beanio" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*\.M.*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.codehaus.groovy" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-beta.*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="junit" artifactId="junit" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-beta.*</ignoreVersion>
      </ignoreVersions>
    </rule>
<!--
	depends on JDK 8
-->
    <rule groupId="org.apache.ant" artifactId="ant" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">1\.1.*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.aspectj" artifactId="aspect*" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion>1.8.10</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="com.beust" artifactId="jcommander" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">1\.[5-9][0-9]*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.apache.derby" artifactId="derby*" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">10\.1[3-9][0-9]?.*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.sonarsource.scanner.maven" artifactId="sonar-maven-plugin" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">3\.[1-9].*</ignoreVersion>
      </ignoreVersions>
    </rule>
    <rule groupId="org.hsqldb" artifactId="hsqldb" comparisonMethod="maven">
      <ignoreVersions>
        <ignoreVersion type="regex">2\.[4-9]\.*</ignoreVersion>
      </ignoreVersions>
    </rule>
  </rules>
</ruleset>```

joergsesterhenn · 2017-06-06T13:09:44Z

We also use rules for automatic updates to avoid some versions. Please don't drop this feature.

sellersj · 2017-06-06T15:10:31Z

Same with us. We use this extensively to exclude versions from jboss, redhat, atlassian, sonatype, milestones, alphas, betas, dev, RC's, jenkins, commons versions that start with the year (2004), as well as versions that depend on new java versions (8, we can only use 7).

I use this task on our various branches of bill of materials (BOM) pom's used across 100's of projects, 500+ modules.

Please, please do not remove this feature.

JeneJasper · 2017-06-08T18:27:04Z

Using this to remove clutter from the report:

With for example:

<?xml version="1.0" encoding="UTF-8"?>

<ruleset comparisonMethod="maven"
         xmlns="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0" 
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0 http://www.mojohaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd">
  <rules>
    <rule groupId="commons-logging" artifactId="commons-logging">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-does-not-exist</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="log4j" artifactId="log4j">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-atlassian.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="com.google.guava">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-rc.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="org.springframework">
      <ignoreVersions>
        <ignoreVersion type="regex">.*\.M.*</ignoreVersion>
        <ignoreVersion type="regex">.*\.RC.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="org.hibernate">
      <ignoreVersions>
        <ignoreVersion type="regex">.*\.Alpha.*</ignoreVersion>
        <ignoreVersion type="regex">.*\.Beta.*</ignoreVersion>
        <ignoreVersion type="regex">.*\.CR.*</ignoreVersion>
        <ignoreVersion type="regex">.*-atlassian-.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="junit">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-beta-.*</ignoreVersion>
        <ignoreVersion type="regex">.*-brew.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="org.mockito">
      <ignoreVersions>
        <ignoreVersion type="regex">.*-dev.*</ignoreVersion>
        <ignoreVersion type="regex">.*-beta.*</ignoreVersion>
        <ignoreVersion type="regex">.*-rc.*</ignoreVersion>
      </ignoreVersions>
    </rule>

    <rule groupId="org.slf4j">
      <ignoreVersions>
        <ignoreVersion type="regex">.*jbossorg.*</ignoreVersion>
      </ignoreVersions>
    </rule>
  </rules>
</ruleset>

Resulting in:

khmarbaise · 2017-06-15T10:26:43Z

So this feedback makes clear it is used in the wild so I don't see any reason to remove the support for that..

Thanks to all who have given feedback.

lesv · 2017-06-17T18:16:23Z

I use it so guide a bot to update and test new releases: https://github.com/GoogleCloudPlatform/java-repo-tools/blob/master/versions-rules.xml

Glad your keeping it.

Jessevanbekkum · 2017-07-13T12:10:07Z

Thanks for keeping it. We also use it, especially for filtering out milestones/beta's/release candidates, filtering out dependencies with mistakes or old versioning methods such as this, and suppressing messages about dependencies we cannot update yet.

obfischer · 2017-07-27T15:17:28Z

I was not aware of this feature, but this is exactly what I was looking fore. Please keep it.

jpdigital · 2017-08-02T15:19:23Z

Another one for keeping it. We have a project which uses commons-collections and commons-primitives. It looks like they changed their versioning system sometime. In Maven Central their are very old versions like 20040616... But these version are much are older then for example 3.2.2. But of course the versions plugins reports 20040616 as an update. The rules feature is the perfect solution for removing such clutter from the plugins reports.

Another possible use case: I you are building a Java EE application with Hibernate which is deployed on Wildfly it is maybe a good idea to use the same version of Hibernate than the one including in your Wildfly. But these bundled version is usually older than the most current version. Using a rule you also remove this from report of the versions plugin.

efenderbosch · 2017-09-29T15:23:23Z

Update the docs here: http://www.mojohaus.org/versions-maven-plugin/rule.html
to remove the link to this issue

johndevs · 2017-10-24T08:32:28Z

This was an awesome issue in getting examples of using the plugin, really helped me in filtering our dependencies. Thanks to everybody who provided examples of their setup 👍

gquintana · 2017-11-02T15:06:53Z

I am using it to skip betas and alphas.

<ruleset>
  <ignoreVersions>
    <ignoreVersion type="regex">.*[-_\.](alpha|Alpha|ALPHA|beta|Beta|BETA|rc|RC|M|EA)[-_\.]?[0-9]?.*</ignoreVersion>
  </ignoreVersions>
</ruleset>

This ruleset is so simple that I'd like to have it the pom.xml instead of having to reference a file URI.

Andrei-Pozolotin · 2017-11-04T18:39:54Z

+1

sazzer · 2017-12-22T09:32:48Z

I'm just starting to use it to filter out versions that we're not ready to upgrade to yet. For example, it keeps showing the 1.8 beta releases of SLF4J, which is a pain.

caladyon · 2017-12-27T16:46:46Z

Thanks for continuing to support this feature. I'm starting to use it now, to exclude dependencies in beta version.

There may remain good reasons for defining custom versioning rules to let versions-maven-plugin apply, but at least not the old Maven 2.x limitation

sabgit · 2018-02-01T05:28:30Z

+1: we are using it for similar reasons already mentioned by other voters

pgervais70 · 2018-02-01T14:21:27Z

+1: We are using it also to control dependency updates like other voters mentioned

sellersj · 2018-02-07T15:13:04Z

Since it looks like this feature won't be removed, can this ticket be closed with a "don't worry, the feature stays" message. It was in June when it was said that the feature is staying.

#157 (comment)

tesaarni · 2018-03-09T14:48:27Z

+1

rroman81 · 2018-03-21T20:24:24Z

+1 This feature seems very helpful

COvayurt · 2018-05-30T06:47:52Z

+1

khmarbaise · 2018-07-10T16:46:57Z

Based on the good feedback this will not been removed.

soruce · 2018-09-05T09:58:10Z

+1

romani · 2018-12-28T13:07:08Z

It would be good to remove deprecation note from documentation

famod · 2019-01-20T15:38:51Z

It would be good to remove deprecation note from documentation

See PR #273. Unfortunately there hasn't been any progress lately.

See: #157 (comment)

khmarbaise added the deprecated label May 28, 2017

khmarbaise added this to the 3.0.0 milestone May 28, 2017

binkley added a commit to binkley/sproingk that referenced this issue Jun 5, 2017

Remove versions rules file

9c1664d

See mojohaus/versions#157.

khmarbaise removed this from the 3.0.0 milestone Jul 15, 2017

mouyang mentioned this issue Aug 8, 2017

User-Defined Version Comparison Methods #194

Closed

romani mentioned this issue Oct 20, 2017

Use versions-maven-plugin to report versions to update checkstyle/checkstyle#5208

Closed

hboutemy added a commit that referenced this issue Jan 28, 2018

#157 document the end of versioning limitations in Maven 3.x

3efd354

There may remain good reasons for defining custom versioning rules to let versions-maven-plugin apply, but at least not the old Maven 2.x limitation

ctrueden mentioned this issue Apr 28, 2018

Remove notice of deprecation for comparison rules #273

Merged

khmarbaise closed this as completed Jul 10, 2018

sbondorf mentioned this issue Aug 19, 2018

#32 maven cleanup NetCal/DNC#37

Closed

pbougrier mentioned this issue Aug 29, 2018

Remove deprecating message in rules documentation #302

Closed

nsidhaye mentioned this issue Sep 5, 2018

versions:use-latest-releases updates to the highest version number but not to recent release #263

Closed

romani mentioned this issue Dec 28, 2018

update Maven plugins checkstyle/eclipse-cs#118

Merged

olamy pushed a commit that referenced this issue Jan 23, 2019

Remove notice of deprecation for comparison rules (#273)

d7c3f33

See: #157 (comment)

rarkins mentioned this issue May 13, 2019

[Question] How to pickup new version of Guava that is tagged "*-jre"? renovatebot/config-help#232

Closed

fwilhe mentioned this issue Apr 3, 2020

Add step to prepare the version for an artifact SAP/jenkins-library#1343

Merged

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Keep the version rules in versions-maven-plugin #157

Keep the version rules in versions-maven-plugin #157

khmarbaise commented May 28, 2017

binkley commented Jun 4, 2017

khmarbaise commented Jun 4, 2017

Stephan202 commented Jun 4, 2017

binkley commented Jun 5, 2017

binkley commented Jun 5, 2017

mattnelson commented Jun 5, 2017

famod commented Jun 6, 2017 •

edited

Loading

rsiggi commented Jun 6, 2017

joergsesterhenn commented Jun 6, 2017

sellersj commented Jun 6, 2017 •

edited

Loading

JeneJasper commented Jun 8, 2017

khmarbaise commented Jun 15, 2017

lesv commented Jun 17, 2017

Jessevanbekkum commented Jul 13, 2017

obfischer commented Jul 27, 2017

jpdigital commented Aug 2, 2017

efenderbosch commented Sep 29, 2017

johndevs commented Oct 24, 2017

gquintana commented Nov 2, 2017

Andrei-Pozolotin commented Nov 4, 2017

sazzer commented Dec 22, 2017

caladyon commented Dec 27, 2017

sabgit commented Feb 1, 2018

pgervais70 commented Feb 1, 2018

sellersj commented Feb 7, 2018

tesaarni commented Mar 9, 2018

rroman81 commented Mar 21, 2018

COvayurt commented May 30, 2018

khmarbaise commented Jul 10, 2018

soruce commented Sep 5, 2018

romani commented Dec 28, 2018

famod commented Jan 20, 2019

Keep the version rules in versions-maven-plugin #157

Keep the version rules in versions-maven-plugin #157

Comments

khmarbaise commented May 28, 2017

binkley commented Jun 4, 2017

khmarbaise commented Jun 4, 2017

Stephan202 commented Jun 4, 2017

binkley commented Jun 5, 2017

binkley commented Jun 5, 2017

mattnelson commented Jun 5, 2017

famod commented Jun 6, 2017 • edited Loading

rsiggi commented Jun 6, 2017

joergsesterhenn commented Jun 6, 2017

sellersj commented Jun 6, 2017 • edited Loading

JeneJasper commented Jun 8, 2017

khmarbaise commented Jun 15, 2017

lesv commented Jun 17, 2017

Jessevanbekkum commented Jul 13, 2017

obfischer commented Jul 27, 2017

jpdigital commented Aug 2, 2017

efenderbosch commented Sep 29, 2017

johndevs commented Oct 24, 2017

gquintana commented Nov 2, 2017

Andrei-Pozolotin commented Nov 4, 2017

sazzer commented Dec 22, 2017

caladyon commented Dec 27, 2017

sabgit commented Feb 1, 2018

pgervais70 commented Feb 1, 2018

sellersj commented Feb 7, 2018

tesaarni commented Mar 9, 2018

rroman81 commented Mar 21, 2018

COvayurt commented May 30, 2018

khmarbaise commented Jul 10, 2018

soruce commented Sep 5, 2018

romani commented Dec 28, 2018

famod commented Jan 20, 2019

famod commented Jun 6, 2017 •

edited

Loading

sellersj commented Jun 6, 2017 •

edited

Loading