Gary, Thank you for your suggestion. they make sense.
I will define a parent pom, using oparent 0.1.1 as parent. Then have other DCAEGEN2 poms to point to this as parent. Lusheng -------- Original message -------- From: Gary Wu <[email protected]> Date: 9/15/17 3:59 PM (GMT-05:00) To: "JI, LUSHENG (LUSHENG)" <[email protected]> Cc: [email protected] Subject: RE: stability of oparent artifact version Hi Lusheng, The reason to move to a release version for your dependencies [1] is to prevent your builds from breaking due to upstream changes to their SNAPSHOT artifacts. If you want to keep your oparent dependency on 1.0.0-SNAPSHOT you’re free to do so until M4, but just be aware that oparent may experiment with breaking changes in the SNAPSHOT artifact on occasion. What I would recommend is to move to the currently declared version [2] of oparent (0.1.1) at your convenience. Then, you don’t have to always upgrade to the latest oparent version right away; you only need to be on the declared version by the time we release. I don’t expect oparent to release that many more versions, but there may be new ones from time to time. If you’re sure that all of your repos should be on the same version of oparent all the time, one option to reduce the amount of work is to define your own dcae2-parent POM that all others inherit from, and only have that single POM inherit from oparent directly. This dcae2-parent would also be useful if you have DCAE2-specific settings that you want to standardize across all of your repos. [1]: https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Independent-2BVersioning-2Band-2BRelease-2BProcess&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=zyau-KuKMOZCAy8bkBGlSf3pL3gMoYC3Rhwo84pJ9t8&s=RL8NovhkwLz1fA0Z-tNY2A2CecplB6ZPjNpWtwYKVpE&e=> [2]: https://wiki.onap.org/display/DW/ONAP+Version+Manifest+Maven+Plugin<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BVersion-2BManifest-2BMaven-2BPlugin&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=zyau-KuKMOZCAy8bkBGlSf3pL3gMoYC3Rhwo84pJ9t8&s=yP4S65jjlSKq0TEqOHKxzbDu4LlN4kZcRb7RPxclF8k&e=> Thanks, Gary From: JI, LUSHENG (LUSHENG) [mailto:[email protected]] Sent: Friday, September 15, 2017 7:11 AM To: Gary Wu <[email protected]> Cc: [email protected] Subject: stability of oparent artifact version Hi Gary, We have this requirement of using oparent as parent for all project poms, which we complied, back in July/August time frame. But then the version of the oparent artifact has changed several times. This causes all referencing projects to change. For DACEGEN2, we have a dozen and half repos. This is a lot of changes every time oparent changes. Is it possible NOT to change the versioning in oparent? For example just use 1.0.0-SNAPSHOT as it was back in July, at least until the release time? Thanks, Lusheng Ji DCAE PTL
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
