rwgaj commented on issue #2141: URL: https://github.com/apache/karaf/issues/2141#issuecomment-3520471575
I did not clearly describe the use case, let me elaborate: Usually, during development, I change a bundles version to let's say `1.5.0-SNAPSHOT`. Once I made some changes, I install it to my local repository and it gets updated in my locally running development application (using `bundle:watch *`), where I test and verify the changes. Basically, that's my development cycle. It works very well. Before last week, I didn't even know, that the `bundle:watch` command only updates snapshot bundles. I made some changes in a bundle (let's say version `1.1.0`) and installed it to my local repository (overwriting the existing `1.1.0`). I know it's bad practice and a release version should not change. I then looked into several things, like my Maven configuration and a couple other, because I was wondering, why the bundle did not update. It was then, that I discovered, that it only updates snapshot bundles automatically. I solved my issue by temporarily changing the bundles version to a snapshot for local development and then changing it to a release once I was done (like I should have from the start). So I guess my point is: Although it's bad practice to make changes in the release version of a bundle, would there be any harm with allowing auto updates in this case? Basically, I see this feature request as a nice to have, even though it's technically based on bad practice (but would not cause any harm, I guess ^^). I hope I could get my point across, as English is not my native language. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
