Closed sslavic closed 8 years ago
@reiz Is that update supposed to happen when posting to /v2/projects/{project_id}
? If yes, might that be fixed by implementing #9?
My tests seem to confirm that this is an issue with the API, the updated name in the uploaded pom.xml
or pom.json
is ignored.
@reiz Can you give any feedback if it's intended that way or confirm that it is a VersionEye API bug?
@stempler Yes. Currently the name from the pom.json is ignored. That's by design. Because if you rename your project via the VersionEye web interface you don't want it to get reseted by fresh uploads through the API.
@reiz maybe versioneye server could keep separate information - was project renamed in server or not. When plugins try to update project in VersionEye, if project wasn't renamed in server then use/apply name from pom.json, and ignore it if project was renamed in server.
@reiz But project name and GA seem to be separate - I can change the name, but not the GA, so maybe the GA should be updated via the pom.json
?
Closing this because this is an issue with the behavior of the VersionEye API and not the plugin.
Using id 'org.standardout.versioneye' version '1.2.0' plugin, after changing rootProject.name, and running versioneye-update task, VersionEye project GA did not get updated.