@matteo_poli said in Switching Build path from lib to API when building rules:
Regarding the new parameter, I see you point it to a different folder than I do. Solibri only sees custom rules in the C:\Program Files\Solibri\SOLIBRI\API folder, which means it won’t see them unless they are manually moved to the right path. Coincidentally, trying to build into the right path fails.
Actually I have elaborated this here
https://society.solibri.com/topic/3266/rules-not-showing-up-in-solibri-when-following-the-get-started-guide/2
https://society.solibri.com/topic/3266/rules-not-showing-up-in-solibri-when-following-the-get-started-guide/13
here
https://society.solibri.com/topic/3148/solibri-24-12-0-beta-round-open/11
and here
https://society.solibri.com/topic/3307/setup-pom-xml-for-25-3/8
and I guess it’s not good to have another discussion about the same topic here again but in short:
C:/Users/Public/Solibri/SOLIBRI/API… is the location which seems to be working with the default .vmoptions - including rules. Normally there is also no need for Admin Rights to build into this folder.
C:\Program Files\Solibri\SOLIBRI\APIMight work as well, if you change the Dwd value but then it is not global anymore (e.g. if you have multiple Solibri Versions installed).
Finally I am also curious how you are sharing .jar files with your team. I guess one use case for changing the Dwd value might be to have the ressources on a shared location but this comes with risks of corrupt files as we learned the hard way and probably needs adjustmants of the .vmoptions on each machine. Therefore I am curious about stable best practice workflows of other organizations for deploying the packages.