-
Notifications
You must be signed in to change notification settings - Fork 30
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
JakartaEE Descriptors #115
Comments
Hi @stbischof . I've recently taken over the Shrinkwrap project and I haven't got the time to get to Descriptors just yet, but I can merge PRs and release new versions so feel free to give it a shot 👍 |
any opinions on the java version? java 5 /6 as in setup should not be the goal. With JAVA 9+ we cant use but uses this.
so update over java8 breaks API because needs rework on transformation to not use |
Personally I would stick with Java 8 for now. The rest of Shrinkwrap also uses Java 8 and although I would love to go for 11 (or even 17 or 21), I'd prefer to stabilize the code now and bump the version later |
@petrberan what is the default branch? 2.0.0-X seems the newest |
@stbischof Sorry, I've been busy with preparing a conference lately, I'll have a look at those PRs soon. As for the branch, it really seems that 2.0.0-X has some newer commits. Though I must say I'm not a fan of having non-"main" branch named as a maintenance one and the "main" being behind. Over the time I'd love to leave the 2.0.0-X as a maintenance and release 3.0.0 from Main branch, using the Java version bump as a fresh start |
I would rename the 2.0.0-X to main. And than update there to a 3.0.0. And just tag for Version releases. Just devel on main is best. |
Sounds good to me. Can't find anything that's in master and not in 2.0.0-X so I'll close the master, duplicate the 2.0.0-X for maintenance and make the 2.0.0-X the new main. |
I am willing to add JakartaEE Descriptors.
but before I start it would be important to know if someone would merge and create at release.
Is there someone who is willing and able to merge and release?
The text was updated successfully, but these errors were encountered: