You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "sachin kamdar (JIRA)" <ji...@codehaus.org> on 2008/03/05 07:38:28 UTC

[jira] Created: (MNG-3437) Always updating local repository from remote repository

Always updating local repository from remote repository
-------------------------------------------------------

                 Key: MNG-3437
                 URL: http://jira.codehaus.org/browse/MNG-3437
             Project: Maven 2
          Issue Type: Improvement
          Components: Settings
            Reporter: sachin kamdar


With the following settings in the settings.xml file,

<settings>
...
  <repository>
      <id>inhouse-repo</id>
      <name>Inhouse M2 Repo</name>
      <url>http://inhouse.maven.repo</url>
      <releases>
          <enabled>true</enabled>
          <updatePolicy>always</updatePolicy>
          <checksumPolicy>warn</checksumPolicy>
      </releases>
  </repository>
...
</settings>


* Dev A has a copy of demo-1.0.0.jar in his local repository
* Dev B makes a code change to demo project and packages the jar without updating the version in the POM (which I think is a BAD BAD thing).
* Dev B then deploys a changed demo-1.0.0.jar into Inhouse Remote Repository.
* When Dev A does his next build, despite of the <updatePolicy>always</> setting the local repository doesn't get the newer copy from the Inhouse Remote Repository.

Is this kind of expected? Does maven only looks at the version number of an artifact to determines if they are different? And if all this is true then under what circumstances would <updatePolicy>always</> fetch a newer artifact?

Is there any way I can get Maven to always update an artifact from Inhouse Remote Repository into the local repository even though the version numbers are same?




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MNG-3437) Always updating local repository from remote repository

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-3437.
---------------------------

      Assignee: John Casey
    Resolution: Won't Fix

Released artifacts are considered by Maven to be immutable. Therefore, they are never subject to updates. The updateInterval in the releases section of the repository definition really pertains only to metadata about things like the RELEASE and LATEST meta-versions, which are normally used to resolve plugins when you don't specify their versions in your POM.

As you said, changing a released artifact is a BAD BAD thing.

> Always updating local repository from remote repository
> -------------------------------------------------------
>
>                 Key: MNG-3437
>                 URL: http://jira.codehaus.org/browse/MNG-3437
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Settings
>            Reporter: sachin kamdar
>            Assignee: John Casey
>
> With the following settings in the settings.xml file,
> <settings>
> ...
>   <repository>
>       <id>inhouse-repo</id>
>       <name>Inhouse M2 Repo</name>
>       <url>http://inhouse.maven.repo</url>
>       <releases>
>           <enabled>true</enabled>
>           <updatePolicy>always</updatePolicy>
>           <checksumPolicy>warn</checksumPolicy>
>       </releases>
>   </repository>
> ...
> </settings>
> * Dev A has a copy of demo-1.0.0.jar in his local repository
> * Dev B makes a code change to demo project and packages the jar without updating the version in the POM (which I think is a BAD BAD thing).
> * Dev B then deploys a changed demo-1.0.0.jar into Inhouse Remote Repository.
> * When Dev A does his next build, despite of the <updatePolicy>always</> setting the local repository doesn't get the newer copy from the Inhouse Remote Repository.
> Is this kind of expected? Does maven only looks at the version number of an artifact to determines if they are different? And if all this is true then under what circumstances would <updatePolicy>always</> fetch a newer artifact?
> Is there any way I can get Maven to always update an artifact from Inhouse Remote Repository into the local repository even though the version numbers are same?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira