Updated the installation guide by replacing obsolete info with GF7 info

[Ariho-Seth]

Updated the https://github.com/eclipse-ee4j/glassfish/blob/master/docs/installation-guide/src/main/asciidoc/installing.adoc by:

• Updating the Javassist Library License Notice with the MOZILLA PUBLIC LICENSE Version 2.0
• Updated the Eclipse GlassFish Full Profile and Web Profile Features with the current versions
• Removed Solaris OS from the installation procedures.

---

• Fixes Update the installation guide which is still based on GF5 #25628
• Closes Automatically generate versions of components in the installation guide #25642

[OndroMih]

I would remove the patch version, which can easily change with some fix. THe major and minor version of components is important.

Suggested change

	|Jakarta JSON Processing 2.1.3 |X |X
	|Jakarta JSON Processing 2.1 |X |X

[OndroMih]

Derby is not a Jakarta EE API, we are not bound to any version - we can upgrade it to any version, it's not worth keeping the version number in this guide. Unless we generate the version from pom.xml, which would be nice, but we don't do it now. It's better to remove the version rather than keep an outdated version.

Suggested change

	|Apache Derby 10.15.2.0 |X |X
	|Apache Derby|X |X

[dmatej]

Actually it could be worth to have the concrete version and also to link to its documentation from our documentation, but that is probably work for another task. However ... when you mentioned filtering, we have these properties in POMs.

[OndroMih]

I agree, this would be for another task. And it would be really useful to publish the versions of components this way, but it has to be automated. We're not capable of keeping the versions up to date manually.

[OndroMih]

Actually, the versions are already defined, so we could directly reference them in the docs, like {derby.version}. The problem is that asciidoc doesn't support period in the reference, so we need to redeclare them as variables without periods, fore example: ${derby.version}, and then refer to them as {derbyVersion} in adoc files. That works, I just tried.

[OndroMih]

I created a separate issue to reference real versions of components: #25642.

@Ariho-Seth, if you want, you can resolve that issue in this same PR, it should be pretty easy as I described in that issue.

It would then be OK also to use patch numbers for Jakarta EE APIs, for example 3.1.1 instead of 3.1, because it would be automatically kept up to date.

[Ariho-Seth]

Sure thing, let me work on that

[OndroMih]

I would remove the version here for the same reasons as for Derby DB.

Suggested change

	|OMG CORBA APIs 3.0 |X |X
	|OMG CORBA APIs |X |X

[OndroMih]

Suggested change

	|JAX-RS 2.1 (Jersey) |X |X
	|RESTful Web Services 3.1 (Jersey) |X |X

[OndroMih]

I would remove the version as this is not a Jakarta EE spec

Suggested change

	|CORBA 3.0.0 |X a|*
	|CORBA |X a|*

[Ariho-Seth]

Thanks @OndroMih, for your review, I've worked on the suggested changes, please let me know of any adjustments in case.

[Ariho-Seth]

Hello @OndroMih, please have a look at this commit for the solution to the discussion above.
It also fixes this issue #25642

Please feel free to suggest any other adjustments if necessary

Changes introduced after approval to be reverted.

[Ariho-Seth]

Hello @pzygielo, @OndroMih, hope these changes look clean now?

[pzygielo]

👍

but I've checked only for property references.