Sorry for not being clear.
What I mean is that the regular way Maven checks for updates on SNAPSHOT
dependencies doesn't apply to parent-pom SNAPSHOT.
If you have a project with a parent-pom 1-SNAPSHOT and a set of SNAPSHOT
dependencies, the first time of the day, all dependencies will be checked
for newer SNAPSHOT but the parent-pom.
Even if you use the -U option which forces the check on SNPASHOT versions,
the parent-pom SNAPSHOT won't be checked.
Here's concrete example:
A company parent pom:
<groupId>com.company</groupId>
<artifactId>company-parent</artifactId>
<version>2-SNAPSHOT</version>
<packaging>pom</packaging>
<name>company-parent</name>
-----------------------------------------------
A company dependency:
<parent>
<groupId>com.company</groupId>
<artifactId>company-parent</artifactId>
<version>2-SNAPSHOT</version>
</parent>
<artifactId>commons</artifactId>
<packaging>jar</packaging>
<version>1.1-SNAPSHOT</version>
<name>commons</name>
-----------------------------------------------
A company project:
<parent>
<groupId>com.company</groupId>
<artifactId>company-parent</artifactId>
<version>2-SNAPSHOT</version>
</parent>
<groupId>com.company.client</groupId>
<artifactId>project</artifactId>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>
<name>project</name>
<dependencies>
<dependency>
<groupId>com.company</groupId>
<artifactId>commons</artifactId>
<version>1.1-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
</dependencies>
The first time of the day you run a maven command on your project, Maven
will check the repo for updates of commons-1.1-SNAPSHOT. Same if your run
your command with -U.
But it seems it'll never check for company-parent-2-SNAPSHOT, even when
invoked with -U.
When everyone rely on the company-parent pom in a team it causes big
problems. Maven behavior becomes different on each every instance. People
have to check out the latest version of the company-pom from the VCS and
'mvn install' on their local repository.
Hope I made it clear enough.
I'd be really surprised if it was to be the expected behavior. At the same
time I wonder why this problem doesn't seem to appear in the mailing list.
Explanation welcome!!
-nodje
Wayne Fay wrote:
>
>> In other words, it seems there is no update checks on the remote repo for
>> the parent version in a child project.
>>
>> Is that an expected behavior? If not, is there a bug filled alreay for
>> that?
>> Is there any workaround ?
>
> Its hard to understand what you are really asking here. Can you make
> it a little more concrete with an example perhaps?
>
> Please be aware that only SNAPSHOT versions are ever checked for
> updates/changes. If you deploy mulitple files with the same
> non-SNAPSHOT version (eg myjar-2.5.3.jar), you will quickly run into a
> world of pain.
>
> Finally, you should also know that repositories by default are checked
> for updates to a given snapshot once daily. You can configure this to
> occur more or less frequently -- check the documentation for
> specifics.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Parents-version-isn%27t-check-for-new-updates-on-the-remote-repository-tp20434803p20452467.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
