I am attempting to create an archive for my team's java project via Xcode. I can successfully build and analyze the project, but when I attempt to select the archive options, export ACTION\=install is throwing an error. The error being thrown states "Class names, 'install', are only accepted if annotation processing is explicitly requested" I've done research into this issue and it states javac is expecting a .java suffix after install, but I'm not sure how/if this suffix should be installed. Perhaps I need a different build tool for archiving? Also, I believe this install Action is an Xcode dependency rather than a dependent library class and seems to be controllable based upon the SKIP_INSTALL build setting, which is currently set to YES according to my build target log.
The project was created using an external build system with javac acting as the specified build tool. The java project has multiple subdirectories with source files and multiple external static libraries it calls upon.
Alternatively, I do have a working .app bundle for my project that was created manually. This bundle has been signed, has a bundle name specified in the info.plist file, and has the java program's jar located within the Java directory. I'm under the impression this cannot be notarized and distributed to our App Store connect listing since I cannot open this bundle in Xcode, but if there is a way to take this existing app bundle, convert it to a binary, and notarize that, this would also be an acceptable solution to our problem.
The project was created using an external build system with javac acting as the specified build tool. The java project has multiple subdirectories with source files and multiple external static libraries it calls upon.
Alternatively, I do have a working .app bundle for my project that was created manually. This bundle has been signed, has a bundle name specified in the info.plist file, and has the java program's jar located within the Java directory. I'm under the impression this cannot be notarized and distributed to our App Store connect listing since I cannot open this bundle in Xcode, but if there is a way to take this existing app bundle, convert it to a binary, and notarize that, this would also be an acceptable solution to our problem.