I just extended my subscription plan to include BProc withing my subscription.
However I am not being able to configure the project with the BProc add-on.
Can you please assess what to do?
The error shown while building the project is as follows:
A problem occurred configuring project ':app-core'.
> Could not resolve all dependencies for configuration ':appComponent'.
> Could not resolve com.haulmont.addon.bproc:bproc-global:1.2.0.
Required by:
project :
> Could not resolve com.haulmont.addon.bproc:bproc-global:1.2.0.
> Could not get resource 'https://repo.cuba-platform.com/content/groups/premium/com/haulmont/addon/bproc/bproc-global/1.2.0/bproc-global-1.2.0.pom'.
> Could not GET 'https://repo.cuba-platform.com/content/groups/premium/com/haulmont/addon/bproc/bproc-global/1.2.0/bproc-global-1.2.0.pom'. Received status code 401 from server: Unauthorized
Hi,
could you please provide the following information:
What Studio version do you use? You can find this information on the “Welcome” screen. In IntelliJ Idea open the CUBA - Welcome menu. There is Product Versions section there. Copy the information from the section and paste it here please.
How do you install the BProc add-on? Using the CUBA - Marketplace screen from IntelliJ idea?
How do you run the project? Do you use CUBA Studio or run gradle commands manually?
Please try to reproduce the problem on the new sample project - just create the new empty CUBA project and try to add the add-on using the Marketplace window in CUBA Studio. Will you get the same error in this case?
As I see you use rather old IntelliJ idea and CUBA Studio plugin versions (2019.3 and 14.3).
What you may do:
Try the latest IntelliJ Idea and the latest CUBA Studio plugin (the current plugin version is 15.6 or 15.4 if you download a bundle from the web site)
Try to run the build using the command line to ensure the license is valid. You can run the following Gradle command to do that (replace user and password with the values from your license key - they are separated by the dash):
I have an assumption that old studio may have some bug with passing your license credentials into build tasks, so the steps described above will help to check it.