[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
