-
-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
review: chore: Remove snapshot repository from parent pom #3864
review: chore: Remove snapshot repository from parent pom #3864
Conversation
My understanding is that we do this, we won't push snapshots to OW2 anymore during CD. We need to have it in a profile for everything. WDYT? |
I don't believe this is the case. We have the snapshot repository defined in the Lines 92 to 107 in 668a18b
From the Maven reference (https://maven.apache.org/pom.html#repository):
Unless I'm completely misinterpreting the docs, there's no reason to define a repository under the |
Thanks for the additional info. LGTM. |
Thanks @slarse |
Now I need to vet all of the Jenkins jobs to verify that an up-to-date Spoon snapshot is actually being pulled :) |
excellent idea!
|
Oh, and more relevant, it appears as if the snapshot deployment went fine: https://ci.inria.fr/sos/job/Spoon-Snapshot-Deployer/3403/console |
cool!
|
#3216
See my latest comments in #3216. I don't see any reason to declare the snapshot repository for anything but distribution management. In Jenkins jobs, we inject the snapshot repository into pom files of other projects.
If we agree to merge this, I'll (after merge) go over all Jenkins jobs and make sure that they correctly pull the latest snapshot (I already know of several that pull from the old snapshot repository).
EDIT: Apparently,
spoon-smpl
depends on a SNAPSHOT version ofspoon-control-flow
, so it does need the snapshot repository enabled by default. But that's the concern ofspoon-smpl
, and not all of the Spoon Maven modules, and so we define it only inspoon-smpl
.