review chore:Use Maven INRIA instead of Gforge to deploy snapshots #1900
Conversation
surli
changed the title
surli
changed the title
|
There are also urls to change in the scripts in /doc |
I think I replaced all mentions now: checked with a grep in the folder. If you know other locations of the mention, tell me. |
pom.xml
Outdated
| @@ -169,9 +169,9 @@ | |||
| <url>http://spoon.gforge.inria.fr/repositories/releases</url> | |||
| </repository> | |||
| <repository> | |||
| <id>gforge.inria.fr-snapshot</id> | |||
| <id>maven.inria.fr-snapshot</id> | |||
There was a problem hiding this comment.
I guess we can remove the whole repository tag since we release on Central, and lonly keep the snapshotRepository?
There was a problem hiding this comment.
I suppose we can indeed. I just kept the same pattern as before.
pom.xml
Outdated
| <name>inria-snapshots</name> | ||
| <url>scp://scm.gforge.inria.fr/home/groups/spoon/htdocs/repositories/snapshots</url> | ||
| <id>maven.inria.fr-snapshot</id> | ||
| <name>http://maven.inria.fr-snapshots</name> |
There was a problem hiding this comment.
What about avoiding http://, it may be confusing, looking like a URL and not a name.
|
I guess we have to update the Jenkins job? (at least to give the crendentials?) |
Yes, I'm on it. |
Fix #1900