Added plugin repositories.

[peters-axon]

No description provided.

[ivy-rew]

@linhpd-axonivy is there any public documentation available how to make the connector compatible with the dev-build? I can't find anything related to this topic in the official wiki
https://github.com/axonivy-market/market/wiki/c3-Market-Integration

[ivy-rew]

@linhpd-axonivy is there any public documentation available how to make the connector compatible with the dev-build? I can't find anything related to this topic in the official wiki https://github.com/axonivy-market/market/wiki/c3-Market-Integration

IMHO making the connector build compatible with the dev-pipeline is a complex task to do. This provokes frustration and forces our users to dive deep into Maven, which is something we want to avoid at any rate due to the steep learning curve that must be mastered. I think it would if Octopus takes that responsibility to setup the pipeline for dev compatibility. 💪
We should not bother the original developers with such frustrating work. 🤷

What do you think @linhpd-axonivy @ivy-sgi

[ghost]

Hi @ivy-rew ,
I checked with our team, and unfortunately, it seems we did not update any documentation for the dev-build. I think we also need to update the product-template.

Since Sabine is on vacation, @nqhoan-axonivy , could you help me take note of this issue?

[ivy-rew]

Hi @ivy-rew , I checked with our team, and unfortunately, it seems we did not update any documentation for the dev-build. I think we also need to update the product-template.

Since Sabine is on vacation, @nqhoan-axonivy , could you help me take note of this issue?

the problem is that the heavy parts of the configuration live in the pom.xml the user is creating during the project setup. So you can't set them up for the user beforehand in the template.

Besides this, it's a highly repetitive task, that you may even automate in a build job. But even if there would be documentation, I think it's overwhelming for normal ivy users and if something fails, requests to ivy-team are being to the rescue.

So I think it would be better if you/Ocotpus takes this responsibility. Sort of a post-onboarding step that you do after the contribution was added. Maybe even with a simple script that does the job for you 🤖