Hey,

yeah sorry we upgraded/changed our CI script and did some testing with snapshot releases. I wasn't aware these are used in production. I will make a new snapshot release which resolves this issue.

Edit: Release is up and is getting synced now

Good for me, thanks.

Hi,

Sorry for reopening the issue, I though it was ok, but it is not.

The deployed snapshots on https://repository.ow2.org/nexus/content/repositories/snapshots/fr/inria/gforge/spoon/spoon-core/10.4.1-SNAPSHOT/ , so far any of spoon-core-10.4.1-*.pom refers to the parent artifact

<parent>
<groupId>fr.inria.gforge.spoon</groupId>
<artifactId>spoon-pom</artifactId>
<version>10.4.1-SNAPSHOT</version>
<relativePath>spoon-pom</relativePath>
</parent>

Unless I am missing something there is not such fr.inria.gforge.spoon:spoom-pom:10.4.1-SNAPSHOT deployed. The maven resolution fails on this.

Thanks,
Lionel.

PS: this is not that I am using "in production". I am running a project that uses Spoon with the latest snapshot to ensure that it is still running with the latest snapshot.

There are different options:

• set up snapshot CD for spoon-parent
• ensuring that spoon-core does not depend on snapshots, that's chore: ensure in CI that there is no dependency to snapshots #5395
• removing the parent, that's remove parent POM spoon-parent #5397

@MartinWitt says that the parent pom snapshot will be CDed and deployed to https://oss.sonatype.org/content/repositories/snapshots/fr/inria/gforge/spoon/spoon-pom/ once #5394 is merged

@seintur the fix is to change the snapshot repo, see SpoonLabs/npefix@b8b2e6e

Good, thanks Martin, it works for me. I am closing the issue.