Sonatype buildNumber和时间戳不同步 [英] Sonatype buildNumber and timestamp out of sync

查看:197
本文介绍了Sonatype buildNumber和时间戳不同步的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的快照部署有一个非常奇怪的问题: https://gist.github.com/fommil / 5042065

I have a really weird problem with my snapshot deployment: https://gist.github.com/fommil/5042065

<groupId>com.github.fommil</groupId>
<artifactId>emokit</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
    <snapshot>
        <timestamp>20130226.204310</timestamp>
        <buildNumber>13</buildNumber>
    </snapshot>
    <lastUpdated>20130226204310</lastUpdated>
    <snapshotVersions>
        <snapshotVersion>
            <extension>jar</extension>
            <value>1.0-20130226.204248-12</value>
            <updated>20130226204310</updated>
        </snapshotVersion>
    ...

基本上, buildNumber timestamp 不同意 snapshotVersion s的名称,这将SBT和IntelliJ混淆在一起我不能依赖这些快照。

Basically, the buildNumber and timestamp do not agree with the names of the snapshotVersions, which confuses SBT and IntelliJ to the point where I can't depend on these snapshots.

我尝试删除并重新部署所有快照,但尚未修复。

I have tried deleting and redeploying all the snapshots, but it hasn't fixed it.

我想让某人帮助我解决这个问题,所以这些字段都是一致的,我可以使用SBT作为上游应用程序中的构建工具。我提交了一个关于SBT的问题,但没有收到任何关注(这可以说是一个SBT错误,而不是处理这个): https://github.com/sbt/sbt/issues/679

I'd like somebody to help me fix this so that the fields all agree and I can use SBT as my build tool in upstream applications. I filed an issue on SBT but it has received no attention (this is arguably an SBT bug in not dealing with this): https://github.com/sbt/sbt/issues/679

项目本身托管在 https://github.com/fommil/emokit-java ,上传的文件(将更改)来源于 https://oss.sonatype。 org / content / repositories / snapshots / com / github / fommil / emokit / 1.0-SNAPSHOT / maven-metadata.xml

The project itself is hosted at https://github.com/fommil/emokit-java and the uploaded file (which will change) is sourced at https://oss.sonatype.org/content/repositories/snapshots/com/github/fommil/emokit/1.0-SNAPSHOT/maven-metadata.xml

有时它修复自己 - 我期待有一些sonatype cronjob整理了这一切。

Sometimes it fixes itself - I expect there was some sonatype cronjob that tidied this all up.

(注意:我投票关闭,因为我认为它似乎修复了自己,但是问题再次出现。 )

(NOTE: I voted to close because I thought it seemed to fix itself, but then the problem arose again.)

推荐答案

你是否声明了maven-depl oy插件专门在你的pom?仔细检查版本和该插件。

Have you declared the maven-deploy-plugin specifically in your pom? Double check the version and of that plugin.

这篇关于Sonatype buildNumber和时间戳不同步的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆