[wildfly-dev] Re: Milestone -jbossorg releases of EE 10 API

I'm not sure if this is technically allowed, but this does seem to work https://github.com/resteasy/resteasy/pull/3039. A pseudo fork so to speak. On Thu, Mar 3, 2022 at 11:44 AM James Perkins <jperkins(a)redhat.com&gt; wrote: > > > On Thu, Mar 3, 2022 at 9:39 AM Brian Stansberry < > brian.stansberry(a)redhat.com&gt; wrote: > >> >> >> On Thu, Mar 3, 2022 at 11:18 AM James Perkins <jperkins(a)redhat.com&gt; >> wrote: >> >>> Oh sorry, my mistake :) I would guess >>> https://github.com/jboss/jboss-jakarta-jaxrs-api_spec and each other >>> spec likely has one there with a few exceptions. If you need access to the >>> repository just let me know. >>> >>> On Thu, Mar 3, 2022 at 9:12 AM Scott Stark <sstark(a)redhat.com&gt; wrote: >>> >>>> Into which JBoss org are we forking these jakartaee and eclipse-ee4j >>>> repos is the question? >>>> >>>> On Mar 3, 2022 at 10:58:03 AM, James Perkins <jperkins(a)redhat.com&gt; >>>> wrote: >>>> >>>>> 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 added a column to >> https://docs.google.com/spreadsheets/d/1ql5hpsqs5ZjawErhyVQX8idigFfm0uZZx.... >> Let's track data there. If people want write access please ping me with the >> google account to use. >> >> 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. > > >> >> >>>>> On Thu, Mar 3, 2022 at 8:54 AM Scott Stark <sstark(a)redhat.com&gt; wrote: >>>>> >>>>>> 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(a)lists.jboss.org >>> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org >>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> >> >> -- >> Brian Stansberry >> Principal Architect, Red Hat JBoss EAP >> He/Him/His >> > > > -- > James R. Perkins > JBoss by Red Hat > -- James R. Perkins JBoss by Red Hat