[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634381#action_12634381
]
Adrian Tarau commented on VELOCITY-613:
---------------------------------------
Done. You can download the POM from :
http://repo.adrian.tarau.org/velocity/velocity/1.5/. Just dump the POM(and
checksums) here http://repo1.maven.org/maven2/velocity/velocity/1.5/.
You can remove everything that exists now at
http://repo1.maven.org/maven2/velocity/velocity/1.5/ ,just a POM with
relocation is enough to point to the real POM.
I will have a second look tomorrow in all groups and build a relocation POM for
them.
You can use this dummy project to see how it works first :
http://repo.adrian.tarau.org/org/tarau/adrian/dummy/0.1-SNAPSHOT/dummy-0.1-20080925.055220-1.pom.
You can change the informational message (Please change Velocity groupId from
velocity to org.apache.velocity.) with a different one.
I think I know how those POMs got there. I presume many artifacts in Maven 2
repository were just moved to the new repository format using the Maven 1
repository .What I don't understand is why a (valid) Maven 2 POM existed in
Velocity Maven 1 repository at the conversion time. If you look at
http://repo1.maven.org/maven/velocity/poms/ there is a velocity-1.5.pom.carlos
which gives me the idea that somebody played with those files (who's Carlos? :)
).
> 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]
