Into which JBoss org are we forking these jakartaee and eclipse-ee4j repos is the question?
For Jakarta REST it's
https://github.com/jakartaee/rest. If everyone else agrees with doing this I'm happy to get a full list together for the ones in question. If we want to just test with one first though I'm happy to have RESTEasy be the tester.
I don't think we should do these unless the people driving our integration of a spec ask. We shouldn't spend time producing forks/releases if there won't be much benefit.
I guess "benefit" is somewhat relative. There is definitely a cost to using the forked version. It requires the time to handle it and brings the question of "how often do we rebase?". What RESTEasy is doing does work. However, as I said it's polluting the local repository of anyone that builds RESTEasy's main branch.
One option I've thought of, but haven't tested, was to see if there is a way with the maven-scm-plugin and the org.codehaus.mojo plugin to create a fork during the build. I can have a look at this as it seems easier at least than fully forking a repository. We wouldn't deploy these artifacts into Nexus, but they could at least be used for local testing without polluting the local repository.
I can take it on since this impacts our getting WildFly certified for EE10. What GitHub org would I use for these forked repos?
--
James R. Perkins
JBoss by Red Hat
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His