Re: Move javaee-api to Git.

[Zowalla, Richard]

Thanks to you both!

Am Montag, dem 14.02.2022 um 23:26 +0100 schrieb Jean-Louis Monteiro:
> I'd probably agree.
> 
> I went and pushed a merged version with
> https://github.com/apache/tomee-jakartaee-api/commit/fcaa0bb099cb06b6ca59a330a76c194185128372
> The feature for OSGI still needs some love and I have to review and
> replace
> remaining Geronimo specs were we have jakarta equivalents.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Mon, Feb 14, 2022 at 11:06 PM David Blevins <
> dblev...@tomitribe.com>
> wrote:
> 
> > > On Feb 14, 2022, at 4:42 PM, Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> > > I did a pom.xml comparison and it looks like in
> > tomee-jakarta/jakartaee-api
> > > module you used most of the jakarta.xxx dependencies as opposed
> > > to the
> > > usual Geronimo specs.
> > > Is there a reason?
> > 
> > I don't recall off the top of my head, but I suspect it was that we
> > didn't
> > have jakarta versions of the Geronimo API jars and some APIs were
> > updated
> > slightly, like EJB, so a straight translation would hit issues.  I
> > think it
> > was a "I don't want to deal with this now" move.
> > 
> > 
> > We could use either, though there is no longer the licensing
> > restriction
> > that forced us to create the Geronimo API jars in the first place.
> > 
> > Were it me, I'd continue to use the jars which are implementations
> > (javamail, activation, etc), but the others that are pure APIs, I'm
> > not
> > sure it's worth the effort.
> > 
> > 
> > -David
> > 
> > 


smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Apache TomEE 8.0.10

[Zowalla, Richard]

Hi Alex,

https://issues.apache.org/jira/browse/TOMEE-3838 references:

- https://nvd.nist.gov/vuln/detail/CVE-2021-40110

"In Apache James, using Jazzer fuzzer, we identified that an IMAP user
can craft IMAP LIST commands to orchestrate a Denial Of Service using a
vulnerable Regular expression. This affected Apache James prior to
3.6.1 We recommend upgrading to Apache James 3.6.1 or higher , which
enforce the use of RE2J regular expression engine to execute regex in
linear time without back-tracking."

Geronimo Java Mail uses apache-mime4j-core-0.8.6.jar (from Apache James
as shaded dependency). We do not use the Apache James Mail server in
the code base. Note, that Apache James provides a lot of different
utility libraries: https://james.apache.org/download.cgi

This also holds for:

- https://nvd.nist.gov/vuln/detail/CVE-2021-38542
- https://nvd.nist.gov/vuln/detail/CVE-2021-40111
- https://nvd.nist.gov/vuln/detail/CVE-2021-40525

I might be wrong, but imho TOMEE-3838 is a false positive.

Gruß
Richard


Am Dienstag, dem 15.02.2022 um 07:46 +0100 schrieb Alex The Rocker:
> Hello,
> 
> May I suggest [-1] until TOMEE-3838 is solved (it's a CVE-related
> issue, marked as a blocker, CVE's score is High at 75) ?
> 
> Thanks,
> Alex
> 
> Le ven. 11 févr. 2022 à 11:12, Zowalla, Richard
>  a écrit :
> > Hi,
> > 
> > +1 from my side.
> > 
> > I tested the 8.0.10 plus artifact with our fullstack EAR app (jpa,
> > jaxrs, jsf).
> > 
> > Thanks, JL for conducting the release.
> > 
> > Gruss
> > Richard
> > 
> > 
> > Am Freitag, dem 11.02.2022 um 09:53 +0100 schrieb Jean-Louis
> > Monteiro:
> > > Hi All,
> > > 
> > > This is a first attempt at a vote for a release of Apache TomEE
> > > 8.0.10
> > > 
> > > Maven Repo:
> > > https://repository.apache.org/content/repositories/orgapachetomee-1193/
> > > 
> > > Binaries & Source:
> > > https://dist.apache.org/repos/dist/dev/tomee/staging_1193-TomEE-8.0.10/
> > > 
> > > Tags:
> > > https://github.com/apache/tomee/releases/tag/tomee-project-8.0.10
> > > 
> > > Release notes:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12350706
> > > 
> > > Here are the releases notes
> > > Sub-task
> > > 
> > >- [TOMEE-2117 <
> > > https://issues.apache.org/jira/browse/TOMEE-2117>;;]
> > > -
> > >Rework ProcessObserverMethod integration
> > >- [TOMEE-2289 <
> > > https://issues.apache.org/jira/browse/TOMEE-2289>;;]
> > > -
> > >MicroProfile OpenAPI Example
> > >- [TOMEE-2349 <
> > > https://issues.apache.org/jira/browse/TOMEE-2349>;;]
> > > -
> > >Ensure each module can generate javadoc jars on release
> > >- [TOMEE-2350 <
> > > https://issues.apache.org/jira/browse/TOMEE-2350>;;]
> > > -
> > >Create a list of existing Javadoc using html
> > >- [TOMEE-2351 <
> > > https://issues.apache.org/jira/browse/TOMEE-2351>;;]
> > > -
> > >MicroProfile OpenTracing Example for Distributed Microservices
> > >- [TOMEE-2358 <
> > > https://issues.apache.org/jira/browse/TOMEE-2358>;;]
> > > -
> > >MicroProfile JWT rest-mp-jwt-claim Example
> > > 
> > > Bug
> > > 
> > >- [TOMEE-2169 <
> > > https://issues.apache.org/jira/browse/TOMEE-2169>;;]
> > > -
> > >Interceptor Bean injection does not work for EJBs
> > >- [TOMEE-2270 <
> > > https://issues.apache.org/jira/browse/TOMEE-2270>;;]
> > > -
> > >Java11: Unable to initialize agent with embedded-maven-plugin
> > >- [TOMEE-2403 <
> > > https://issues.apache.org/jira/browse/TOMEE-2403>;;]
> > > -
> > >AutoConnectionTrackerTest fails randomly
> > >- [TOMEE-2427 <
> > > https://issues.apache.org/jira/browse/TOMEE-2427>;;]
> > > -
> > >Align text above the pictures
> > >- [TOMEE-2800 <
> > > https://issues.apache.org/jira/browse/TOMEE-2800>;;]
> > > -
> > >Issue : Unable to run EJB test cases for upgradation in
> > > current
> > > project
> > >with Java 1.8 and WebLogic version 12.2.1.4 along with
> > > openejb.cxf.version
> > >7.0.1 / openejb.cxf.version 8 jar.
> > >- [TOMEE-2941 <
> > > https://issues.apache.org/jira/browse/TOMEE-2941>;;]
> > > -
> > >Regression: A connection factory created with
> > > TransactionSupport
> > > of "none"
> > >only sending message when transaction completes
> > >- [TOMEE-3777 <
> > > https://issues.apache.org/jira/browse/TOMEE-3777>;;]
> > > -
> > >
> > >org.apache.openjpa.persistence.ArgumentException: The
> > > persistence
> > > provider
> > >is attempting to use properties in the persistence.xml file to
> > > resolve the
> > >data source ...
> > >- [TOMEE-3816 <
> > > https://issues.apache.org/jira/browse/TOMEE-3816>;;]
> > > -
> > >Return "this" on stateless EJB method looses container
> > > transaction
> > >management
> > >- [TOMEE-3823 <
> > > https://issues.apache.org/jira/browse/TOMEE-3823>;;]
> > > -
> > >TomEE and Java 17 compatibility issue with Windows Service
> > > Tooling
> > >- [TOMEE-3825 <
> > > https://issues.apache.org/

Re: [VOTE] Apache TomEE 8.0.10

[Alex The Rocker]

Hello,

May I suggest [-1] until TOMEE-3838 is solved (it's a CVE-related
issue, marked as a blocker, CVE's score is High at 75) ?

Thanks,
Alex

Le ven. 11 févr. 2022 à 11:12, Zowalla, Richard
 a écrit :
>
> Hi,
>
> +1 from my side.
>
> I tested the 8.0.10 plus artifact with our fullstack EAR app (jpa,
> jaxrs, jsf).
>
> Thanks, JL for conducting the release.
>
> Gruss
> Richard
>
>
> Am Freitag, dem 11.02.2022 um 09:53 +0100 schrieb Jean-Louis Monteiro:
> > Hi All,
> >
> > This is a first attempt at a vote for a release of Apache TomEE
> > 8.0.10
> >
> > Maven Repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1193/
> >
> > Binaries & Source:
> > https://dist.apache.org/repos/dist/dev/tomee/staging_1193-TomEE-8.0.10/
> >
> > Tags:
> > https://github.com/apache/tomee/releases/tag/tomee-project-8.0.10
> >
> > Release notes:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12350706
> >
> > Here are the releases notes
> > Sub-task
> >
> >- [TOMEE-2117 ;]
> > -
> >Rework ProcessObserverMethod integration
> >- [TOMEE-2289 ;]
> > -
> >MicroProfile OpenAPI Example
> >- [TOMEE-2349 ;]
> > -
> >Ensure each module can generate javadoc jars on release
> >- [TOMEE-2350 ;]
> > -
> >Create a list of existing Javadoc using html
> >- [TOMEE-2351 ;]
> > -
> >MicroProfile OpenTracing Example for Distributed Microservices
> >- [TOMEE-2358 ;]
> > -
> >MicroProfile JWT rest-mp-jwt-claim Example
> >
> > Bug
> >
> >- [TOMEE-2169 ;]
> > -
> >Interceptor Bean injection does not work for EJBs
> >- [TOMEE-2270 ;]
> > -
> >Java11: Unable to initialize agent with embedded-maven-plugin
> >- [TOMEE-2403 ;]
> > -
> >AutoConnectionTrackerTest fails randomly
> >- [TOMEE-2427 ;]
> > -
> >Align text above the pictures
> >- [TOMEE-2800 ;]
> > -
> >Issue : Unable to run EJB test cases for upgradation in current
> > project
> >with Java 1.8 and WebLogic version 12.2.1.4 along with
> > openejb.cxf.version
> >7.0.1 / openejb.cxf.version 8 jar.
> >- [TOMEE-2941 ;]
> > -
> >Regression: A connection factory created with TransactionSupport
> > of "none"
> >only sending message when transaction completes
> >- [TOMEE-3777 ;]
> > -
> >
> >org.apache.openjpa.persistence.ArgumentException: The persistence
> > provider
> >is attempting to use properties in the persistence.xml file to
> > resolve the
> >data source ...
> >- [TOMEE-3816 ;]
> > -
> >Return "this" on stateless EJB method looses container transaction
> >management
> >- [TOMEE-3823 ;]
> > -
> >TomEE and Java 17 compatibility issue with Windows Service Tooling
> >- [TOMEE-3825 ;]
> > -
> >TomEE Maven Plugin does not wait for container startup, if
> > "checkStarted"
> >is set to true
> >- [TOMEE-3832 ;]
> > -
> >JAX-RS TomEEJsonbProvider not registered in tomee-embedded-maven-
> > plugin
> >when MicroProfile is present
> >
> > New Feature
> >
> >- [TOMEE-2306 ;]
> > - New
> >Java EE Schemas for Java EE Deployment Descriptors
> >- [TOMEE-2584 ;]
> > - Java
> >11 compliancy
> >- [TOMEE-2706 ;]
> > - New
> >TomEE Embedded Bootstrap
> >
> > Improvement
> >
> >- [TOMEE-1618 ;]
> > -
> >Replace three register maps in Container in favour of one
> >- [TOMEE-2277 ;]
> > -
> >Java11: module name for TomEE
> >- [TOMEE-2425 ;]
> > -
> >Generate TomEE-Cluster.html page
> >- [TOMEE-2519 ;]
> > - MP
> >JWT Logging Improvements
> >- [TOMEE-2847 ;]
> > -
> >Patch key `jakarta` namespace support
> >- [TOMEE-2949 ;]
> > -
> >Match TomEE tar

Re: Move javaee-api to Git.

[Jean-Louis Monteiro]

I'd probably agree.

I went and pushed a merged version with
https://github.com/apache/tomee-jakartaee-api/commit/fcaa0bb099cb06b6ca59a330a76c194185128372
The feature for OSGI still needs some love and I have to review and replace
remaining Geronimo specs were we have jakarta equivalents.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Feb 14, 2022 at 11:06 PM David Blevins 
wrote:

> > On Feb 14, 2022, at 4:42 PM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > I did a pom.xml comparison and it looks like in
> tomee-jakarta/jakartaee-api
> > module you used most of the jakarta.xxx dependencies as opposed to the
> > usual Geronimo specs.
> > Is there a reason?
>
> I don't recall off the top of my head, but I suspect it was that we didn't
> have jakarta versions of the Geronimo API jars and some APIs were updated
> slightly, like EJB, so a straight translation would hit issues.  I think it
> was a "I don't want to deal with this now" move.
>
>
> We could use either, though there is no longer the licensing restriction
> that forced us to create the Geronimo API jars in the first place.
>
> Were it me, I'd continue to use the jars which are implementations
> (javamail, activation, etc), but the others that are pure APIs, I'm not
> sure it's worth the effort.
>
>
> -David
>
>

Re: Move javaee-api to Git.

[David Blevins]

> On Feb 14, 2022, at 4:42 PM, Jean-Louis Monteiro  
> wrote:
> 
> I did a pom.xml comparison and it looks like in tomee-jakarta/jakartaee-api
> module you used most of the jakarta.xxx dependencies as opposed to the
> usual Geronimo specs.
> Is there a reason?

I don't recall off the top of my head, but I suspect it was that we didn't have 
jakarta versions of the Geronimo API jars and some APIs were updated slightly, 
like EJB, so a straight translation would hit issues.  I think it was a "I 
don't want to deal with this now" move.


We could use either, though there is no longer the licensing restriction that 
forced us to create the Geronimo API jars in the first place.

Were it me, I'd continue to use the jars which are implementations (javamail, 
activation, etc), but the others that are pure APIs, I'm not sure it's worth 
the effort.


-David

Re: Move javaee-api to Git.

[Jean-Louis Monteiro]

I did a pom.xml comparison and it looks like in tomee-jakarta/jakartaee-api
module you used most of the jakarta.xxx dependencies as opposed to the
usual Geronimo specs.
Is there a reason?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Feb 14, 2022 at 10:13 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> That's exactly what I wanted to do.
> I was just missing the repo.
>
> I'll try to do that tonight very quick.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Feb 14, 2022 at 10:11 PM David Blevins 
> wrote:
>
>>
>> > On May 18, 2021, at 12:22 PM, David Blevins 
>> wrote:
>> >
>> > As long as I was doing the tomee-release-tools converstion from svn to
>> git, I went ahead and did this one too:
>> >
>> > - https://github.com/apache/tomee-jakartaee-api
>> >
>> > We did end up creating a module for an updated jakartaee-api jar in the
>> `tomee-jakarta` repo:
>> >
>> > - https://github.com/apache/tomee-jakarta/tree/master/jakartaee-api
>> >
>> > Next steps for anyone who has the energy is to move that setup into the
>> `tomee-jakartaee-api` repo then remove it from `tomee-jakarta`
>>
>> Jean-Louis,
>>
>> Here's the last status on jakartaee-api I remember.
>>
>>
>> -David
>>
>>
>> >
>> >> On May 19, 2020, at 7:18 PM, Cesar Hernandez 
>> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I need help from a PMC member in order to create the repo.
>> >>
>> >> In the INFRA ticket [1] we obtained the link for the self-service
>> creation
>> >> of a new git repository but it most be performed by a PMC member.
>> >> This is the link for the request:
>> >> https://gitbox.apache.org/setup/newrepo.html
>> >>
>> >> As peer the data requested by the form, this is the information
>> required.
>> >> Notice that I left the repo name with tomee as the prefix because all
>> the
>> >> other gitbox repositories related with Tomee has it.
>> >>
>> >> Repository name: tomee-jakartaee-api
>> >> Repository description: Apache TomEE jakartaee-api
>> >> Commit notification list: dev@tomee.apache.org
>> >> GitHub notification list: dev@tomee.apache.org
>> >>
>> >>
>> >> [1]
>> >>
>> https://issues.apache.org/jira/browse/INFRA-20280?focusedCommentId=17111651&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17111651
>> >>
>> >>
>> >> El lun., 18 may. 2020 a las 16:07, Daniel Dias Dos Santos (<
>> >> daniel.dias.analist...@gmail.com>) escribió:
>> >>
>> >>> great :  )
>> >>> --
>> >>>
>> >>> *Daniel Dias dos Santos*
>> >>> Java Developer
>> >>> SouJava & JCP Member
>> >>> GitHub: https://github.com/Daniel-Dos
>> >>> Linkedin: www.linkedin.com/in/danieldiasjava
>> >>> Twitter: http://twitter.com/danieldiasjava
>> >>>
>> >>>
>> >>> Em seg., 18 de mai. de 2020 às 19:04, Cesar Hernandez <
>> >>> cesargu...@gmail.com>
>> >>> escreveu:
>> >>>
>>  My own +1
>>  Here are the results from the vote.
>> 
>> 
>>  +1s
>> 
>>  Jonathan Gallimore (binding)
>> 
>>  David JencksDaniel "soro" Cunha
>> 
>>  Daniel Dias Dos Santos
>> 
>>  Thiago Henrique Hupner
>> 
>>  Nishant Raut
>>  Mark Struberg (binding)
>> 
>>  Carlos Chacín
>> 
>>  Cesar Hernandez
>> 
>> 
>>  There are no other votes, so this vote passes. I'll open the infra
>> ticket
>>  for this task.
>> 
>>  El jue., 30 abr. 2020 a las 9:39, Carlos Chacín (> >)
>>  escribió:
>> 
>> > +1
>> >
>> > On Thu, Apr 30, 2020 at 6:04 AM Mark Struberg
>> >>> > >
>> > wrote:
>> >
>> >> +1 (binding)
>> >>
>> >> LieGrue,
>> >> strub
>> >>
>> >>
>> >>> Am 29.04.2020 um 23:39 schrieb Cesar Hernandez <
>> >>> cesargu...@gmail.com
>> > :
>> >>>
>> >>> Hi,
>> >>>
>> >>> As a follow up from the `Javax -> Jakarta rename` thread [1]
>> >>> I would like to propose moving the existing SVN javaee-api repo
>> [2]
>>  to
>> >>> Git[3] to enable wider visibility and collaboration either via
>> >>> GitHub
>> > or
>> >>> gitbox.apache.org.
>> >>>
>> >>> I will create the Apache JIRA Infra migration ticket after the
>> vote
>>  has
>> >>> passed.
>> >>>
>> >>> [ ] +1 approve the release move javaee-api repo to Git
>> >>> [ ] +0 no opinion
>> >>> [ ] -1 disapprove (and reason why)
>> >>>
>> >>> [1]
>> >>>
>> >>
>> >
>> 
>> >>>
>> https://lists.apache.org/thread.html/refb945e599cad66d8508a540fa5801fd2b04682424e9e29b4e6dd7b4%40%3Cdev.tomee.apache.org%3E
>> >>> [2] https://svn.apache.org/repos/asf/tomee/javaee-api/
>> >>> [3] https://gitbox.apache.org/
>> >>> --
>> >>> Atentamente:
>> >>> César Hernández.
>> >>
>> >>
>> >
>> > --
>> > *Carlos Chacin*
>> > Senior SDE
>> >
>> 
>> 
>>  --
>>  Atentamente:
>>  César Hernández.
>> 
>> >>>
>> >>
>> >>
>> >> --
>> >> Atentamente:
>> >> Cé

Re: Move javaee-api to Git.

[Jean-Louis Monteiro]

That's exactly what I wanted to do.
I was just missing the repo.

I'll try to do that tonight very quick.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Feb 14, 2022 at 10:11 PM David Blevins 
wrote:

>
> > On May 18, 2021, at 12:22 PM, David Blevins 
> wrote:
> >
> > As long as I was doing the tomee-release-tools converstion from svn to
> git, I went ahead and did this one too:
> >
> > - https://github.com/apache/tomee-jakartaee-api
> >
> > We did end up creating a module for an updated jakartaee-api jar in the
> `tomee-jakarta` repo:
> >
> > - https://github.com/apache/tomee-jakarta/tree/master/jakartaee-api
> >
> > Next steps for anyone who has the energy is to move that setup into the
> `tomee-jakartaee-api` repo then remove it from `tomee-jakarta`
>
> Jean-Louis,
>
> Here's the last status on jakartaee-api I remember.
>
>
> -David
>
>
> >
> >> On May 19, 2020, at 7:18 PM, Cesar Hernandez 
> wrote:
> >>
> >> Hi,
> >>
> >> I need help from a PMC member in order to create the repo.
> >>
> >> In the INFRA ticket [1] we obtained the link for the self-service
> creation
> >> of a new git repository but it most be performed by a PMC member.
> >> This is the link for the request:
> >> https://gitbox.apache.org/setup/newrepo.html
> >>
> >> As peer the data requested by the form, this is the information
> required.
> >> Notice that I left the repo name with tomee as the prefix because all
> the
> >> other gitbox repositories related with Tomee has it.
> >>
> >> Repository name: tomee-jakartaee-api
> >> Repository description: Apache TomEE jakartaee-api
> >> Commit notification list: dev@tomee.apache.org
> >> GitHub notification list: dev@tomee.apache.org
> >>
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/browse/INFRA-20280?focusedCommentId=17111651&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17111651
> >>
> >>
> >> El lun., 18 may. 2020 a las 16:07, Daniel Dias Dos Santos (<
> >> daniel.dias.analist...@gmail.com>) escribió:
> >>
> >>> great :  )
> >>> --
> >>>
> >>> *Daniel Dias dos Santos*
> >>> Java Developer
> >>> SouJava & JCP Member
> >>> GitHub: https://github.com/Daniel-Dos
> >>> Linkedin: www.linkedin.com/in/danieldiasjava
> >>> Twitter: http://twitter.com/danieldiasjava
> >>>
> >>>
> >>> Em seg., 18 de mai. de 2020 às 19:04, Cesar Hernandez <
> >>> cesargu...@gmail.com>
> >>> escreveu:
> >>>
>  My own +1
>  Here are the results from the vote.
> 
> 
>  +1s
> 
>  Jonathan Gallimore (binding)
> 
>  David JencksDaniel "soro" Cunha
> 
>  Daniel Dias Dos Santos
> 
>  Thiago Henrique Hupner
> 
>  Nishant Raut
>  Mark Struberg (binding)
> 
>  Carlos Chacín
> 
>  Cesar Hernandez
> 
> 
>  There are no other votes, so this vote passes. I'll open the infra
> ticket
>  for this task.
> 
>  El jue., 30 abr. 2020 a las 9:39, Carlos Chacín ()
>  escribió:
> 
> > +1
> >
> > On Thu, Apr 30, 2020 at 6:04 AM Mark Struberg
> >>>  >
> > wrote:
> >
> >> +1 (binding)
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 29.04.2020 um 23:39 schrieb Cesar Hernandez <
> >>> cesargu...@gmail.com
> > :
> >>>
> >>> Hi,
> >>>
> >>> As a follow up from the `Javax -> Jakarta rename` thread [1]
> >>> I would like to propose moving the existing SVN javaee-api repo [2]
>  to
> >>> Git[3] to enable wider visibility and collaboration either via
> >>> GitHub
> > or
> >>> gitbox.apache.org.
> >>>
> >>> I will create the Apache JIRA Infra migration ticket after the vote
>  has
> >>> passed.
> >>>
> >>> [ ] +1 approve the release move javaee-api repo to Git
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>> [1]
> >>>
> >>
> >
> 
> >>>
> https://lists.apache.org/thread.html/refb945e599cad66d8508a540fa5801fd2b04682424e9e29b4e6dd7b4%40%3Cdev.tomee.apache.org%3E
> >>> [2] https://svn.apache.org/repos/asf/tomee/javaee-api/
> >>> [3] https://gitbox.apache.org/
> >>> --
> >>> Atentamente:
> >>> César Hernández.
> >>
> >>
> >
> > --
> > *Carlos Chacin*
> > Senior SDE
> >
> 
> 
>  --
>  Atentamente:
>  César Hernández.
> 
> >>>
> >>
> >>
> >> --
> >> Atentamente:
> >> César Hernández.
> >
>
>

Re: SVN / GIT javaee-api / jakartaee-api

[David Blevins]

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  
> 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

Re: Move javaee-api to Git.

[David Blevins]

> On May 18, 2021, at 12:22 PM, David Blevins  wrote:
> 
> As long as I was doing the tomee-release-tools converstion from svn to git, I 
> went ahead and did this one too:
> 
> - https://github.com/apache/tomee-jakartaee-api
> 
> We did end up creating a module for an updated jakartaee-api jar in the 
> `tomee-jakarta` repo:
> 
> - https://github.com/apache/tomee-jakarta/tree/master/jakartaee-api
> 
> Next steps for anyone who has the energy is to move that setup into the 
> `tomee-jakartaee-api` repo then remove it from `tomee-jakarta`

Jean-Louis,

Here's the last status on jakartaee-api I remember.


-David


> 
>> On May 19, 2020, at 7:18 PM, Cesar Hernandez  wrote:
>> 
>> Hi,
>> 
>> I need help from a PMC member in order to create the repo.
>> 
>> In the INFRA ticket [1] we obtained the link for the self-service creation
>> of a new git repository but it most be performed by a PMC member.
>> This is the link for the request:
>> https://gitbox.apache.org/setup/newrepo.html
>> 
>> As peer the data requested by the form, this is the information required.
>> Notice that I left the repo name with tomee as the prefix because all the
>> other gitbox repositories related with Tomee has it.
>> 
>> Repository name: tomee-jakartaee-api
>> Repository description: Apache TomEE jakartaee-api
>> Commit notification list: dev@tomee.apache.org
>> GitHub notification list: dev@tomee.apache.org
>> 
>> 
>> [1]
>> https://issues.apache.org/jira/browse/INFRA-20280?focusedCommentId=17111651&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17111651
>> 
>> 
>> El lun., 18 may. 2020 a las 16:07, Daniel Dias Dos Santos (<
>> daniel.dias.analist...@gmail.com>) escribió:
>> 
>>> great :  )
>>> --
>>> 
>>> *Daniel Dias dos Santos*
>>> Java Developer
>>> SouJava & JCP Member
>>> GitHub: https://github.com/Daniel-Dos
>>> Linkedin: www.linkedin.com/in/danieldiasjava
>>> Twitter: http://twitter.com/danieldiasjava
>>> 
>>> 
>>> Em seg., 18 de mai. de 2020 às 19:04, Cesar Hernandez <
>>> cesargu...@gmail.com>
>>> escreveu:
>>> 
 My own +1
 Here are the results from the vote.
 
 
 +1s
 
 Jonathan Gallimore (binding)
 
 David JencksDaniel "soro" Cunha
 
 Daniel Dias Dos Santos
 
 Thiago Henrique Hupner
 
 Nishant Raut
 Mark Struberg (binding)
 
 Carlos Chacín
 
 Cesar Hernandez
 
 
 There are no other votes, so this vote passes. I'll open the infra ticket
 for this task.
 
 El jue., 30 abr. 2020 a las 9:39, Carlos Chacín ()
 escribió:
 
> +1
> 
> On Thu, Apr 30, 2020 at 6:04 AM Mark Struberg
>>>  
> wrote:
> 
>> +1 (binding)
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 29.04.2020 um 23:39 schrieb Cesar Hernandez <
>>> cesargu...@gmail.com
> :
>>> 
>>> Hi,
>>> 
>>> As a follow up from the `Javax -> Jakarta rename` thread [1]
>>> I would like to propose moving the existing SVN javaee-api repo [2]
 to
>>> Git[3] to enable wider visibility and collaboration either via
>>> GitHub
> or
>>> gitbox.apache.org.
>>> 
>>> I will create the Apache JIRA Infra migration ticket after the vote
 has
>>> passed.
>>> 
>>> [ ] +1 approve the release move javaee-api repo to Git
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>> 
>>> [1]
>>> 
>> 
> 
 
>>> https://lists.apache.org/thread.html/refb945e599cad66d8508a540fa5801fd2b04682424e9e29b4e6dd7b4%40%3Cdev.tomee.apache.org%3E
>>> [2] https://svn.apache.org/repos/asf/tomee/javaee-api/
>>> [3] https://gitbox.apache.org/
>>> --
>>> Atentamente:
>>> César Hernández.
>> 
>> 
> 
> --
> *Carlos Chacin*
> Senior SDE
> 
 
 
 --
 Atentamente:
 César Hernández.
 
>>> 
>> 
>> 
>> -- 
>> Atentamente:
>> César Hernández.
> 



smime.p7s
Description: S/MIME cryptographic signature

SVN / GIT javaee-api / jakartaee-api

[Jean-Louis Monteiro]

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