You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Zdenek Zikan (JIRA)" <de...@velocity.apache.org> on 2008/08/20 12:36:47 UTC

[jira] Created: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven 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: Zdenek Zikan


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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634580#action_12634580 ] 

Adrian Tarau commented on VELOCITY-613:
---------------------------------------

Files are not accessible : You don't have permission to access /~nbubna/velocity/engine/1.5/velocity-1.5.pom on this server.

Well, if nothing can be deleted, at least the relocation POM will override the old one(which is not valid now) and all M2 users will be redirected to the new location.
If somebody will download the velocity jar directly it will be still fine.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


Re: [jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by ap...@recks.org.
Hi Adrian,

thanks for assisting Nathan on the maven issues!

Some of these things happened March last year in this area by Carlos Sanchez, see the whole thread at:
http://www.nabble.com/Re:--repo---www-people.apache.org-repo-m1-ibiblio-rsync-repository--td9481767.html

Best regards,
Christoph

Adrian Tarau (JIRA) wrote:
>     [ 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>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634554#action_12634554 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

Ok, that's a start, but i don't actually have access to http://repo1.maven.org/maven2/velocity/velocity/1.5/  

i do have access to http://people.apache.org/repo/m2-ibiblio-rsync-repository/, but i don't believe it mirrors deletions or changes to the main repo, just additions.  I also will need to have a vote on releasing a new pom there, amongst numerous other instructions.   The readme for the rsync repo says:
----------------------------------------------------------------------------------------------------------------------
> cat README.txt
http://www.apache.org/dist/maven-repository

This is a Maven 2.0+ repository for deployment of official Apache releases.

DO NOT INCLUDE THIS IN YOUR PROJECT REPOSITORY LIST - USE A MIRROR

Please follow these rules when deploying to this repository:

- only deploy releases voted on by the PMC
- sign all artifacts and POMs (currently, this is a manual step)
- never deploy snapshots or development releases to this repository
- ensure that if a release is deleted from /dist/, it is removed from here completely also (excluding archiving)
- no artifacts are allowed from projects under incubation
- make sure you have your maven settings correctly set to make directories group writeable.

This repository IS synced AUTOMATICALLY to Ibiblio and the Maven mirrors, with non delete option, so be carefull with what you dep
loy here.

After deploying, NO CHANGES OR DELETIONS ARE ALLOWED from central repo or mirrors (only exception the maven-metadata.xml files)



This repository is archived to http://archive.apache.org/dist/maven-repository/
and synced to iBiblio with a no-delete option, so things can be deleted from apache and still available through ibiblio


IMPORTANT:

Permissions should be

775 for directories
644 for files

Which can be done in Maven 2 settings.xml with

    <server>
      <id>apache.releases</id>
      <directoryPermissions>775</directoryPermissions>
      <filePermissions>644</filePermissions>
    </server>
    <server>
      <id>apache.snapshots</id>
      <directoryPermissions>775</directoryPermissions>
      <filePermissions>644</filePermissions>
    </server>


Due to a bug in Maven (http://jira.codehaus.org/browse/MDEPLOY-28) maven-metadata.* files need to have 664 permissions

Run these commands to fix the permissions of your files after deployment:

snapshots:

find /www/cvs.apache.org/maven-snapshot-repository ! -perm 775 -type d -user ${USER} -exec chmod 775 {} \;
find /www/cvs.apache.org/maven-snapshot-repository ! -perm 664 -iname maven-metadata.xml* -user ${USER} -exec chmod 664 {} \;
find /www/cvs.apache.org/maven-snapshot-repository ! -perm 644 ! -iname maven-metadata.xml* -type f -user ${USER} -exec chmod 644
{} \;

releases:

find /www/www.apache.org/dist/maven-repository ! -perm 775 -type d -user ${USER} -exec chmod 775 {} \;
find /www/www.apache.org/dist/maven-repository ! -perm 664 -iname maven-metadata.xml* -user ${USER} -exec chmod 664 {} \;
find /www/www.apache.org/dist/maven-repository ! -perm 644 ! -iname maven-metadata.xml* -type f -user ${USER} -exec chmod 644 {} \
;
----------------------------------------------------------------------------------------------------------------------

so, i'm not sure how to get this to the maven.org repo.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Zdenek Zikan (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624287#action_12624287 ] 

Zdenek Zikan commented on VELOCITY-613:
---------------------------------------

I can use org.apache.velocity, of course. However, the wrong velocity is referenced by maven-archetype-plugin, which is not my work. Of course, I could as well file an issue in maven-archetype-plugin's issue tracker. For our project where we use it, I've already created a workaround by posting new, correct POM to our maven repository. However, there's an velocity jar file in http://repo1.maven.org/maven2/velocity/velocity/1.5/ which has incorrect POM, so I'm reporting that so that other people don't need to do same workarounds.

> 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: Zdenek Zikan
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634555#action_12634555 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

I signed the relocation pom and moved it to:
http://people.apache.org/~nbubna/velocity/engine/1.5/

in case we need to vote on it.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634328#action_12634328 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

Adrian, would you be willing/able to whip a relocation pom and a set of instructions for this?  i'll carry them out, but i'd rather not spend much more time on this than that.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624003#action_12624003 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

So why not use:

http://repo1.maven.org/maven2/org/apache/velocity/velocity/1.5/velocity-1.5.pom

?

> 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: Zdenek Zikan
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634624#action_12634624 ] 

Adrian Tarau commented on VELOCITY-613:
---------------------------------------

After that, meanwhile I will prepare all relocation POMs

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634584#action_12634584 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

Fixed the permissions; thanks for catching that.

And it says no changes or deletions are allowed.  So, i'm not sure i can even change the POM after reading that.  This might be something better taken up on one of the Maven lists.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634618#action_12634618 ] 

Nathan Bubna commented on VELOCITY-613:
---------------------------------------

Yeah, a 1.5.1 is probably the proper way to fix this, but honestly, i'd rather just focus on getting 1.6 out the door.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
    [ 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Resolved: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
     [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bubna resolved VELOCITY-613.
-----------------------------------

    Resolution: Won't Fix

I think this is something better fixed by the maven folks, as i don't recall being the one to put that pom there.   I also don't actually know the proper way to fix this.  If the maven folks say they need me to do this, please let me know.

> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org