search

argouml-tigris-org / argouml

Main project of argouml. Some information in the wiki. Some old releases in releases. (depends on parentpom, testmodels)
246 stars 92 forks source link

No Java Runtime Environment #50

Closed veganaize closed 2 years ago

veganaize commented 2 years ago

ArgoUML 0.35.1 OS: Windows 8.1 (x64)

image

Setup pops up an info dialog with: "No Java Runtime Environment could be found. Setup will automatically download a suitable JRE from sun.com." --even though I have a JRE installed.

C:\> echo %JAVA_HOME%
c:\progra~1\java\jdk1.8.0_202

C:\> where java
c:\Program Files\Java\jdk1.8.0_202\bin\java.exe

...I've also tried the jre\ variations but the result was the same.

linustolke commented 2 years ago

The setup.exe is very old and the scripts that made the build are no longer used. We should use a newer Maven-based builder for the Windows installation. There is a lot of work to set such a tool up. Please help if you can with this.

linustolke commented 2 years ago

I think this is a duplicate of #36. I will close this issue as a duplicate.

veganaize commented 2 years ago

The setup.exe is very old and the scripts that made the build are no longer used. We should use a newer Maven-based builder for the Windows installation. There is a lot of work to set such a tool up. Please help if you can with this.

I totally would @linustolke but repo doesn't support Windows 8.1 (which is a bit ridiculous since even Microsoft still supports it!)

linustolke commented 2 years ago

That is unfortunate. I assume you will move to Windows 10 or Windows 11 before January so you could perhaps get back to this then.

veganaize commented 2 years ago

I will absolutely not be moving to Windows 10 or 11. :alien:

I'll be returning to GNU/Linux whenever my essential 3rd-party tools decide to abandon their compatibility with Windows 8.1... maybe a year or two from now?

I'm currently researching modern build tools & practices. I feel like there may be better options available, which should work well for all of the developers on the project.

I will make sure my proposal includes only processes & tooling that that are greater than or equal to those currently being utilized by the project maintainers, and that the burden of adoption is minimized -- ie. I'll handle any heavy lifting.

linustolke commented 2 years ago

Aha, OK.

I don't really understand what work you are referring to or what proposal you are working with. If you expect me to, please be a little more specific otherwise I will assume that it doesn't concern me or the ArgoUML project.

linustolke commented 2 years ago

It sounds interesting though...

veganaize commented 2 years ago

Sorry. I was implying that I might come back around and propose an alternative build process.

linustolke commented 2 years ago

Please let me know if you want me to go through the use cases or requirements.

veganaize commented 2 years ago

Please do.

linustolke commented 2 years ago

I realize now that my statement is rather unclear. What I meant to say was that I can review the use cases and requirements that you have identified.

On the other hand, I could write something down also.

veganaize commented 2 years ago

Oh, I see... :smile:

Maybe if you could briefly explain some reasoning behind the choices, for the current build tools? (repo, maven, etc.) If this has been explained elsewhere a link to that information would be appreciated.

Which affordances does the current tooling offer that should be carried forward, by any new tooling? Specific use cases & requirements are welcome.

veganaize commented 2 years ago

Actually, scratch all of that!

I can probably leave most/all of the current tools intact. I need to continue looking into this, on my end.

Sorry to bother you with all of this. If you don't hear from me for a while (ie. a month or more) then please feel free to ping me.

linustolke commented 2 years ago

It is no bother at all. I am as eager as you to improve the way we work.

Maven was suggested for use in the project in July 2005 when I complained about the ant build not integrating well with Eclipse. In December 2006 it was suggested again but that we should wait for Maven 2 to be released since it would be incompatible with Maven. I was a little reluctant since it involved moving around the code from an existing directory structure to a new directory structure but I think we got some basic things in place in 2008.

When moving to github I wanted an easy integration with Jenkins for the builds so I abandoned the old build scripts and fixed things in maven. I am still struggling with it and I am struggling with github. I think I am slowly getting to a better state.