You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Claude Brisson (JIRA)" <ji...@apache.org> on 2016/08/31 09:08:20 UTC
[jira] [Updated] (INFRA-12533) Maven metadata is not up-to-date for
Velocity 1.7
[ https://issues.apache.org/jira/browse/INFRA-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson updated INFRA-12533:
-----------------------------------
Description:
Velocity 1.7 has been published almost six years ago.
But the artifact is in a strange state on the repository.apache.org repository:
- velocity 1.7 jars *are* visible and downloadable on the maven jar repositories,
see for instance http://maven.antelink.com/content/repositories/central/org/apache/velocity/velocity/1.7/
- on https://repository.apache.org , the most recent visible version is velocity-1.7-beta1
see https://repository.apache.org/#nexus-search;gav~org.apache.velocity~velocity~~~~kw,versionexpand
- same problem in the metadata :
http://repo1.maven.org/maven2/org/apache/velocity/velocity/maven-metadata.xml
I thought of trying to re-publish the jars using something like:
mvn deploy:deploy-file \
-Durl=https://repository.apache.org/service/local/staging/deploy/maven2 \
-DrepositoryId=apache.releases.https \
-Dfile=velocity-1.7.jar \
-DgroupId=org.apache.velocity \
-DartifactId=velocity \
-Dversion=1.7 \
-Dpackaging=jar \
-Dclassifier=javadoc,sources
But I don't even know if it is the way to go (publication dates would be wrong, the staging artifact would have to be promoted again, etc...), or if it has any chance to work.
All help or remark is welcome.
was:
Velocity 1.7 has been published almost six years ago.
But the artifact is in a strange state on the repository.apache.org repository:
- velocity 1.7 jars *are* visible and downloadable on the maven jar repositories,
see for instance http://maven.antelink.com/content/repositories/central/org/apache/velocity/velocity/1.7/
- on https://repository.apache.org , the most recent visible version is velocity-1.7-beta1
see https://repository.apache.org/#nexus-search;gav~org.apache.velocity~velocity~~~~kw,versionexpand
- same problem in the metadata :
http://repo1.maven.org/maven2/org/apache/velocity/velocity/maven-metadata.xml
I thought of trying to re-publish the jars using something like:
mvn -Durl=https://repository.apache.org/service/local/staging/deploy/maven2 \
-DrepositoryId=apache.releases.https \
-Dfile=velocity-1.7.jar \
-DgroupId=org.apache.velocity \
-DartifactId=velocity \
-Dversion=1.7 \
-Dpackaging=jar \
-Dclassifier=javadoc,sources
But I don't even know if it is the way to go (publication dates would be wrong, the staging artifact would have to be promoted again, etc...), or if it has any chance to work.
All help or remark is welcome.
> Maven metadata is not up-to-date for Velocity 1.7
> -------------------------------------------------
>
> Key: INFRA-12533
> URL: https://issues.apache.org/jira/browse/INFRA-12533
> Project: Infrastructure
> Issue Type: Bug
> Components: Nexus
> Reporter: Claude Brisson
>
> Velocity 1.7 has been published almost six years ago.
> But the artifact is in a strange state on the repository.apache.org repository:
> - velocity 1.7 jars *are* visible and downloadable on the maven jar repositories,
> see for instance http://maven.antelink.com/content/repositories/central/org/apache/velocity/velocity/1.7/
> - on https://repository.apache.org , the most recent visible version is velocity-1.7-beta1
> see https://repository.apache.org/#nexus-search;gav~org.apache.velocity~velocity~~~~kw,versionexpand
> - same problem in the metadata :
> http://repo1.maven.org/maven2/org/apache/velocity/velocity/maven-metadata.xml
> I thought of trying to re-publish the jars using something like:
> mvn deploy:deploy-file \
> -Durl=https://repository.apache.org/service/local/staging/deploy/maven2 \
> -DrepositoryId=apache.releases.https \
> -Dfile=velocity-1.7.jar \
> -DgroupId=org.apache.velocity \
> -DartifactId=velocity \
> -Dversion=1.7 \
> -Dpackaging=jar \
> -Dclassifier=javadoc,sources
> But I don't even know if it is the way to go (publication dates would be wrong, the staging artifact would have to be promoted again, etc...), or if it has any chance to work.
> All help or remark is welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)