[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634604#action_12634604
]
Adrian Tarau commented on VELOCITY-613:
---------------------------------------
Ok, missed "changes" but it makes sense. Since this is a release
repository("never deploy snapshots or development releases to this repository
") per Maven policy once you released a dependency(version X.Y.Z) that version
it's forever(if you have repository's update policy set to "never" the users
you will download it only once and Maven will never check again the repository
- except if you remove the dependency from your local repository). Maybe it
will be better to release a new version 1.5.1 and have this problem fixed there.
Anyway it looks like Maven 2 repository(in super POM) has update policy set to
"daily" so not sure why to enforce this restriction("After deploying, NO
CHANGES OR DELETIONS ARE ALLOWED from central repo or mirrors (only exception
the maven-metadata.xml files"). Maybe because you can override the settings in
your own POM - it makes sense.
> 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]
