Re: [jetty-users] licensing round 2: bundling jetty-home

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Keep your jetty-home and your configured jetty-base instance separate.

Don't nest them inside of each other (in either way).

Don't modify (add/remove/edit) any content in the unarchived jetty-home directory.

Feel free to use a script to download and install a jetty-home if one is not provided/present.

Allow your users to upgrade their jetty-home when they want to.

Your jetty-base directory can move to a new version of jetty-home easily enough.

Just write documentation telling folks to keep within a specific version range for your webapp.

(Since you are going from jetty 9 to jetty 10, that means you are on javax.servlet, you don't want your users going to jetty 11 with jakarta.servlets)

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Sat, May 28, 2022 at 6:08 AM Bill Ross via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

Round 1 result: Thanks to Simone, I moved from 9->10 and commented out
"#--module=https" in start.ini, so keystore is gone.

Is there any conclusive argument for bundling a jetty-home zip file vs.
including a wget fetch in an install script?

Any tips or reassurances on licensing correctly, yet not forcing naive
users to figure out licenses?

Thanks,

Bill

--
Phobrain.com
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users