{"action":"opened","issue":{"url":"https://api.github.com/repos/mojohaus/versions-maven-plugin/issues/175","repository_url":"https://api.github.com/repos/mojohaus/versions-maven-plugin","labels_url":"https://api.github.com/repos/mojohaus/versions-maven-plugin/issues/175/labels{/name}","comments_url":"https://api.github.com/repos/mojohaus/versions-maven-plugin/issues/175/comments","events_url":"https://api.github.com/repos/mojohaus/versions-maven-plugin/issues/175/events","html_url":"https://github.com/mojohaus/versions-maven-plugin/issues/175","id":239123519,"number":175,"title":"versions:set is not updating the dependencies on second run","user":{"login":"ram87reddy","id":6534135,"avatar_url":"https://avatars2.githubusercontent.com/u/6534135?v=3","gravatar_id":"","url":"https://api.github.com/users/ram87reddy","html_url":"https://github.com/ram87reddy","followers_url":"https://api.github.com/users/ram87reddy/followers","following_url":"https://api.github.com/users/ram87reddy/following{/other_user}","gists_url":"https://api.github.com/users/ram87reddy/gists{/gist_id}","starred_url":"https://api.github.com/users/ram87reddy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ram87reddy/subscriptions","organizations_url":"https://api.github.com/users/ram87reddy/orgs","repos_url":"https://api.github.com/users/ram87reddy/repos","events_url":"https://api.github.com/users/ram87reddy/events{/privacy}","received_events_url":"https://api.github.com/users/ram87reddy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-06-28T10:42:36Z","updated_at":"2017-06-28T10:42:36Z","closed_at":null,"body":"Lets say I have a multi-module project\r\n\r\nProject A (pom.xml)\r\n  - B (module pom.xml)\r\n  - C (module pom.xml)\r\nNow in A's pom.xml, under dependency management, i have the following dependency:\r\n\r\n<dependency>\r\n   <groupId>com.mycompany</groupId>\r\n   <artifactId>C</artifactId>\r\n   <version>1.0.0-SNAPSHOT</version>\r\n<dependency>\r\nIn B's pom.xml I use the above dependency.\r\n\r\n<dependency>\r\n   <groupId>com.mycompany</groupId>\r\n   <artifactId>C</artifactId>\r\n<dependency>\r\nNow lets say I run the following command on the root pom.xml (A's pom.xml)\r\n\r\n**mvn versions:set -DnewVersion=137.0.18 -DprocessDependencies=false**\r\n\r\nThis command only sets the version for the parent and the submodules version (but doesn't update the dependency), which is as expected.\r\n\r\nNow if I want to run the following command and process the dependency as well, like this:\r\n**mvn versions:set -DnewVersion=137.0.19 -DprocessDependencies=true**\r\n\r\nNow it does NOT process the dependency. Had if I ran the first command with processDependencies=true, it would have updated the dependency. I am unable to understand why running it the second time its not processing the dependencies? Sounds to me like a bug on versions plugin."}}
{"actor":{"display_login":"ram87reddy"}}