How to handle .bundle?

[shyonae]

Hello. I'm trying to build a maven project and at a certain point it downloads a .bundle file. The plugin knows the artifact doesn't exist and skips it, but then it doesn't check for the packages within and the project fails since the deploy still happens, giving error 409 on Azure Artifacts. How to handle this issue?

mock-file.bundle = gets checked, doesn't exist and can get deployed
mock-file.jar/.pom (etc...) = contained in the .bundle, doesn't get checked while existing on repository, gets deployed and gives error

[chonton]

I do not know the details of a .bundle - if it is a 'container' of jars, then why does deployment explode the container?

Should you check the existence of the jar instead of the bundle?

[shyonae]

How do I do that? In my script (powershell) I use your plugin via command line and it works on other projects but specifically fails with bundles. The problem is that it DOES check the bundle file (which is created with the maven bundle plugin) but then it doesn't check the files that the bundle exports and tries to deploy after. I tried using this plugin by putting it in the pom.xml of the project that gives me the error but with no success. The process, as I understand it, goes like this:

• exists plugin checks the .BUNDLE file
• sees that the file is present, skips it
• the maven bundle plugin kicks in and exports the packages within the bundle and tries to upload them
• exists plugin doesn't acknowledge this
• the project fails as I get error 409 (I'm using Azure DevOps Artifacts unfortunately)

What could be done, any ideas?