Open alitokmen opened 2 years ago
Hi @alitokmen, thank you for your feedback! I will take this up with our engineering team and will report back here later.
Thanks and Happy New Year!
I created an internal Jira ticket for this for our engineering team to pick up.
hi @nvankampenhout I still observe the old version - Do you know if there are plans to handle this?
Please also note that the cargo-maven3-plugin
version is meanwhile 1.10.7
Hi @alitokmen , thanks for the reminder. The internal Jira ticket has been sitting in the backlog, I'll bring it up with the relevant engineering team.
Hi @alitokmen , it turns out this is not trivial to fix and has low priority so for now it remains in the backlog.
Hi @nvankampenhout thanks for checking, please do let me know if I can help, as the change in Codehaus Cargo is normally a 100% drop and replace change, with no expecting breakages with Maven 3.
Thanks @alitokmen. If you wanted to have a go at it, our archetype source is here:
https://github.com/bloomreach/brxm/tree/brxm-15.2.3/archetype
It should be just a dependency update but from what I remember it broke something in our setup. I'm just the documentation guy and don't know the details, the developer community forum would be a better place to discuss this.
Dear Bloomreach teams
I have seen your article https://documentation.bloomreach.com/14/library/development/run-and-develop-with-cargo.html which is quite well written - Congratulations!
One thing I spotted is that it still references the old Codehaus Cargo Maven 2 plugin - Which is quite obsolete as Maven 2 itself is obsolete, and we hence also made the Codehaus Cargo plugin to be Maven 3 only since its 1.9.0 version in January 2021. Would you mind updating that in the meantime? The updated dependency information could be:
Regards