-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't compile structorizers due to javadoc. #1077
Comments
Didn't you try the ./makeStructorizer script? |
i did, this failed with the following error:
|
8 warnings, no errors (StructorizerApplet can be ignored). Didn't it produce any output in the build directory? |
oh, it did. I assumed the last 3 lines meant the entire build failed. However, when i now try to run the
|
... which is normal, as the structorizer.sh script does not start your build but the one I do ;-) |
Neither the build nor the dist directory exist. |
Okay, if there are .class files, so everything got at least compiled. You should be able to start the class files too, but honestly, I do not remember how to do that 😔😔 |
I
|
... because the resources are probably not being found because in some other directory. :-( |
How do you generate your "release builds", i.e. the Structorizer.app directory in the released zip archives? |
I generate the JAR file using NetBeans and then apply a script that does the packaging, but I won't share, because it contains sensitive data. Sorry. Anyway, you do not need the Structorizer.app directory to run your compiled version. That directory simply has that name because of OSX ;) |
Missing deprecation annotations added to avoid the 8 reported JavaDoc warnings (#1077 (comment)) for future versions. |
I am trying to compile structorizer on linux. I've tried with both jdk 19 and jdk 11. I just
cd
ed into the structorizer directory and ranant
. It failed due to javadoc errors. I uploaded the full output here. My question is: how do i build structorizer? I haven't found any info on it so i just tried running ant.The text was updated successfully, but these errors were encountered: