[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634482#action_12634482
]
Adrian Tarau commented on VELOCITY-613:
---------------------------------------
Based on Maven 2 Super POM, central repository has a default update policy -
since is not defined (updatePolicy: This element specifies how often updates
should attempt to occur. Maven will compare the local POM's timestamp (stored
in a repository's maven-metadata file) to the remote. The choices are: always,
daily (default), interval:X (where X is an integer in minutes) or never.)
Replacing all the existing POMs with a relocation POM should not be a problem,
since Maven will download again the POM if changed.
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>Maven Repository Switchboard</name>
<url>http://repo1.maven.org/maven2</url>
</repository>
> Wrong Velocity 1.5 POM file in Maven repository
> -----------------------------------------------
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/jira/browse/VELOCITY-613
> Project: Velocity
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Zdeněk Zikán
>
> Velocity's POM file in Maven repository has incorrect groupId:
> http://repo1.maven.org/maven2/velocity/velocity/1.5/velocity-1.5.pom
> It does not match the jar file
> Currently: <groupId>org.apache.velocity</groupId>
> Should be: <groupId>velocity</groupId>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
