go to post Nicole Aaron · Nov 15, 2016 The development team plans to address the inconsistency of the white package icons in the server section of the Atelier Explorer with Atelier 1.1.
go to post Nicole Aaron · Nov 10, 2016 The other issues you reported are on file and will be addressed when development is able to pick them up.
go to post Nicole Aaron · Nov 9, 2016 John, this looks like a bug to me. I'll file a report with development and let you know what I hear back. Thanks for pointing this out!
go to post Nicole Aaron · Oct 20, 2016 Agreed, that could be confusing. I filed an enhancement request to retain error messages in the Server Connection Configuration dialog as long as the problem persists.
go to post Nicole Aaron · Oct 19, 2016 Certain characters are not allowed in the Server Connection name - spaces, accented letters, etc. When an invalid character is entered in the Connection Name field, the Finish button should be grayed out and an error displayed at the top of the Server Connection Configuration window: "Illegal connection name. Please edit and try again."
go to post Nicole Aaron · May 3, 2016 When you try to start Atelier with the wrong version or bitness of Java installed, you will see that error pop up. There are a few things you can check when this occurs: 1. In an OS command prompt, enter “java –version” to display something like: java version "1.8.0_51" Java(TM) SE Runtime Environment (build 1.8.0_51-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode) This shows the version and the bitness of the Java version installed on your machine. So this can help make sure you are meeting a couple of requirements: A. You need the Java JDK or JRE version 1.8 (JDK for Mac, JRE for other platforms) B. The bitness of Java must match the bitness of your Atelier client. I’ve seen that a 64-bit install indicates that it is 64-bit in the "java –version” output. But for a 32-bit version of Java, no bitness is listed in the "java –version” output. 2. Check your JAVA_HOME environment variable. Make sure that if this is set that it is pointing to your Java JDK/JRE with the correct version and bitness. On a Mac, you can check the location of your Java 1.8 home directory with the Terminal command: /usr/libexec/java_home -v 1.8. On a Windows machine, you can enter this in a Command Prompt: where java.
