[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634319#action_12634319
]
Adrian Tarau commented on VELOCITY-613:
---------------------------------------
If I remember correctly there was a bug related with deploying artifacts under
a hierarchical namespace. A group like org.apache.velocity it should be
deployed under a path org/apache/velocity but it was probably deployed under
velocity(the POM actually has org.apache.velocity groupId and since nobody
seems to place those files there, it could be due some old bug in the deploy
plugin).
It is nice to put a POM with relocation informations to allow an easier
migration, even if is not so hard to change your POM from velocity to
org.apache.velocity.
Here it is about relocation :
http://maven.apache.org/guides/mini/guide-relocation.html,
http://maven.apache.org/pom.html#Relocation
> 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]
