Mike Arnott

The simple issue with that is, I work for a software company. I did not write all of the code in the axCommunity module. I am therefor not putting our signing cert on code I did not create or even test. If someone would like to volunteer to use their cert to sign the code and make it public they are welcome to do so, I will promote them to an administrator in the project. From: Patrick Cunningham patrickc@users.sourceforge.net Sent: Tuesday, October 6, 2020 3:51 PM To: [niagaraaxcommun:discussion]...

Going to have to point this one back to the folks at Tridium. The decision to move to only signed code was theirs. Don't take this personally - I don't have the free time to teach non developers how to do development with Tridium. It is not a lighthearted subject that can be put into a couple of paragraphs - and even worse if it doesn't work for you who do you ask for tech support? I hope someone from Tridium steps up and helps with this issue - I know a lot of developers use the axCommunity module...

No. We will no longer be publishing compiled version of the axCommunity application because of the signature requirement. Anyone that needs it will have to compile it themselves with their own code signing certificate. From: Marcello cello@users.sourceforge.net Sent: Friday, September 4, 2020 5:40 AM To: [niagaraaxcommun:discussion] 898552@discussion.niagaraaxcommun.p.re.sourceforge.net Subject: [niagaraaxcommun:discussion] N4.9 Hi Guys Is possible to have this module in 4.9. sig? Let me know MR,...

Code signing is a warning in Niagara 4.8 and less, unsigned code will still run. It becomes a requirement in Niagara 4.10 - unsigned code will not run. Because this is an open source project the administrators will no longer be providing compiled jar files from this time forward because of the code signing requirements. In the future users will have to download and compile the modules using their own code signing certificate. From: Eugene Parizher eparizher@users.sourceforge.net Sent: Sunday, May...

Hard to say exactly, but I suspect it might be an issue with path variables. And I'm a hack at best when it comes to Gradle. Make sure you have a NIAGARA_USER_HOME environment variable pointed at your Niagara home, something like "C:\Users\Administrator\Niagara4.6\vykon" Make sure you have a GRADLE_HOME variable populated, mine is "C:\Gradle\gradle-4.8" I also have "C:\Gradle\gradle-4.8\bin;" in my Path variable And... I think you should be using gradlew not gradle. I actually use the gradle tools...

It's really hard to say. There is nothing in this error related to axCommunity and we have no idea what you are trying to do or use. I use axC in version 4.4 with no issues. From: zulkifli jebat@users.sourceforge.net Sent: Tuesday, September 4, 2018 4:02 AM To: [niagaraaxcommun:discussion] 898553@discussion.niagaraaxcommun.p.re.sourceforge.net Subject: [niagaraaxcommun:discussion] Installation, am I doing it wrong? javax.baja.naming.UnresolvedException: platformssl: at com.tridium.platcrypto.daemon.se.BDaemonSecureScheme.resolve(BDaemonSecureScheme.java:103)...

01/15/17 MLA - modified BCSVStringToStatusNumeric

Accidental creation