You are viewing a plain text version of this content. The canonical link for it is here.
Posted to droids-dev@incubator.apache.org by "Eugen Paraschiv (JIRA)" <ji...@apache.org> on 2011/03/02 22:06:37 UTC

[jira] Created: (DROIDS-134) Use explicit versions for the Maven dependencies

Use explicit versions for the Maven dependencies
------------------------------------------------

                 Key: DROIDS-134
                 URL: https://issues.apache.org/jira/browse/DROIDS-134
             Project: Droids
          Issue Type: Improvement
    Affects Versions: 0.0.2
            Reporter: Eugen Paraschiv
             Fix For: 0.0.2


It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DROIDS-134) Use explicit versions for the Maven dependencies

Posted by "Tobias Rübner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DROIDS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Rübner updated DROIDS-134:
---------------------------------

    Attachment: maven3.patch

This patch removes the plugin version warnings generated by maven 3.

> Use explicit versions for the Maven dependencies
> ------------------------------------------------
>
>                 Key: DROIDS-134
>                 URL: https://issues.apache.org/jira/browse/DROIDS-134
>             Project: Droids
>          Issue Type: Improvement
>    Affects Versions: 0.0.2
>            Reporter: Eugen Paraschiv
>             Fix For: 0.0.2
>
>         Attachments: maven3.patch, maven3.patch
>
>
> It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DROIDS-134) Use explicit versions for the Maven dependencies

Posted by "Tobias Rübner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DROIDS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Rübner updated DROIDS-134:
---------------------------------

    Attachment:     (was: maven3.patch)

> Use explicit versions for the Maven dependencies
> ------------------------------------------------
>
>                 Key: DROIDS-134
>                 URL: https://issues.apache.org/jira/browse/DROIDS-134
>             Project: Droids
>          Issue Type: Improvement
>    Affects Versions: 0.0.2
>            Reporter: Eugen Paraschiv
>             Fix For: 0.0.2
>
>         Attachments: maven3.patch
>
>
> It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DROIDS-134) Use explicit versions for the Maven dependencies

Posted by "Tobias Rübner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DROIDS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Rübner updated DROIDS-134:
---------------------------------

    Attachment: maven3.patch

now with ASF licence

> Use explicit versions for the Maven dependencies
> ------------------------------------------------
>
>                 Key: DROIDS-134
>                 URL: https://issues.apache.org/jira/browse/DROIDS-134
>             Project: Droids
>          Issue Type: Improvement
>    Affects Versions: 0.0.2
>            Reporter: Eugen Paraschiv
>             Fix For: 0.0.2
>
>         Attachments: maven3.patch, maven3.patch
>
>
> It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (DROIDS-134) Use explicit versions for the Maven dependencies

Posted by "Richard Frovarp (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DROIDS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Frovarp resolved DROIDS-134.
------------------------------------

    Resolution: Fixed

Looks like this has been fixed. mvn versions:display-dependency-updates doesn't report back any unversioned dependencies.
                
> Use explicit versions for the Maven dependencies
> ------------------------------------------------
>
>                 Key: DROIDS-134
>                 URL: https://issues.apache.org/jira/browse/DROIDS-134
>             Project: Droids
>          Issue Type: Improvement
>    Affects Versions: 0.0.2
>            Reporter: Eugen Paraschiv
>             Fix For: 0.0.2
>
>         Attachments: maven3.patch
>
>
> It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira