Le jeu. 10 déc. 2020 à 15:49, Rémy Maucherat <r...@apache.org> a écrit :
> On Thu, Dec 10, 2020 at 3:13 PM Mark Thomas <ma...@apache.org> wrote: > > > On 10/12/2020 13:58, Christopher Schultz wrote: > > > Mark, > > > > > > On 12/10/20 06:39, Mark Thomas wrote: > > >> The proposed Apache Tomcat migration tool for Jakarta EE 0.1.0 is now > > >> available for voting. > > >> > > >> This is (potentially) the first release. > > >> > > >> It can be obtained from: > > >> > > > https://dist.apache.org/repos/dist/dev/tomcat/jakartaee-migration/v0.1.0/ > > >> > > >> The Maven staging repo is: > > >> > > https://repository.apache.org/content/repositories/orgapachetomcat-1291/ > > >> > > >> The tag is: > > >> https://github.com/apache/tomcat-jakartaee-migration/tree/0.1.0 > > >> cbada3204bf9c43ca0cf481cd88c7521690b30a0 > > >> > > >> The proposed 0.1.0 release is: > > >> > > >> [ ] -1: Broken. Do not release because... > > >> [ ] +1: Acceptable. Go ahead and release. > > > > > > Do we even need (a) a release and (b) a VOTE? > > > > If we want a release, we MUST have a VOTE. > > > > > I once heard Ross say that there was an ASP project (Subversion?) that > > > never had votes; they only had releases. That seemed to cut-down on the > > > red-tape required to get things out into the world. I can't find a > > > reference for that, now. > > > > That doesn't sound right. From memory, Subversion doesn't have votes for > > new committers but PMC membership and releases require a VOTE. > > > > > Since this is a developer tool and not a runtime library or anything > > > like that, maybe we can just say "YMMV, this is available any time you > > > want it"? > > > > It could be a runtime library. One possibility is that we integrate it > > into Tomcat 10 somehow so that if you try and deploy a Java EE 8 WAR it > > gets automatically converted to a Jakarta EE 9 WAR. > > > > It sounds doable with a special folder of the host (like a legacyAppBase), > and it creates the result in the host's appBase. Like HostConfig.deployApps > simply does this first, then moves down the usual deployments. I'm not sure > that this is really useful though. > Does it sound stupid to make the library a ClassFileTransformer added on the webapp classloader? Sounds the most hurtless for users even if it will adds a small overhead (and avoids a lot of file duplication which can be harder to maintain at some point). > > Rémy > > > > > > > That said, I have no objections whatsoever with holding a vote. I am an > > > unsigned "0" on the vote itself; I have not even downloaded the source > > > let alone attempted to migrate a project using it. > > > > Fair enough. > > > > I think the naming of some of the artefacts could be improved. As this > > is the first ever release I'm leaning towards cancelling / voting > > against to get them fixed so all releases will (hopefully) use a > > consistent naming convention rather it changing after the first release. > > > > Mark > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > >
