I just bumped the thread were we were working on this. Looks like we converted it but for some reason didn't use it. One of those times I wished I had written my future self a better explanation :)
-David > On Feb 14, 2022, at 3:55 PM, Jean-Louis Monteiro <[email protected]> > wrote: > > Hi, > > I was starting a PR to move tomee master to 9.x for Jakarta EE 9.x but I > realized we would need a new API. > > We used to have https://svn.apache.org/repos/asf/tomee/javaee-api/trunk to > handle our API uber jar. > > Is there any issue if I ask for a new Git repo for Jakarta EE API? > > We could move javaee-api svn repo to git and then create a maintenance > branch and then move master to jakartaee-api. But it looks maybe weird to > have a Git repo named javaee-api and create a jar named jakartaee-api. > > What do you think? > What would be your preference? > > I can also just move svn trunk to a maintenance branch and move trunk to > jakartaee-api. > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com
smime.p7s
Description: S/MIME cryptographic signature
