Re: [krazo-dev] the javax discussion

[Christian Kaltepoth]

The interesting question is whether option (2) is possible and allowed under the JCP rules. I guess we would be the first JSR not using the javax.* package namespace.

PS: Adding the jsr371 mailing list.

Ivar Grimstad <ivar.g...@gmail.com> schrieb am Mo., 6. Mai 2019, 19:20:

Hi,

It is a valid question. Christian and I have discussed this. Our current plan is:

1. Release MVC 1.0 under the JCP with javax.mvc.* namespace/package

2. Move the specification to Jakarta EE

3. Release MVC 2.0 under the JESP with jakarta.mvc.* namespace/package

An alternative plan could be:

1. Modify the namespace/package in the original JSR to be jakarta.mvc.* (I think this should be a pretty easy step but need to be investigated)

2. Release MVC 1.0 under the JCP with the jakarta.mvc.* namespace/package

3. Move the specification to Jakarta EE

4. Release MVC 1.1 under the JESP with jakarta.mvc.* namespace/package (only change here is potentially the maven coordinates)

JESP = Jakarta EE Specification Process

Ivar

On Mon, May 6, 2019 at 1:37 PM Gregor Tudan <gre...@tudan.de> wrote:

Hi everyone,

it was hard to get around the javax vs jakarta namespace discussion last week: https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/

Have we made up our minds on how to deal with this for the MVC-Spec?

Can we release using javax.mvc? We started working on the spec outside of oracle some time ago and the spec was developed in the JCP. So one could argue that the latest version from the JCP should be fine, as long as we don’t change anything. Or would we violate the upcoming deal with Oracle even by publishing under the Eclipse umbrella?

Given that we could release version 1.0 using the current namespace - should we? It’s still a young spec and there will surely be updates necessary. So should we aim for jakarta.mvc from the start to avoid breaking stuff after 1.0?

- Gregor

_______________________________________________
krazo-dev mailing list
kraz...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/krazo-dev

_______________________________________________
krazo-dev mailing list
kraz...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/krazo-dev

[Ivar Grimstad]

Yes, that is the question. Luckily there is a F2F EC meeting coming up next week, so I have the opportunity to ask this question in person there...

Ivar

--
You received this message because you are subscribed to the Google Groups "MVC 1.0 Users Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jsr371-users...@googlegroups.com.
To post to this group, send email to jsr371...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jsr371-users/CAEXeC6x8hbbzWJ0HJ7k3F4kRpmiyxCsQ_k0L30WNwLLBptbRqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Christian Kaltepoth]

👍

Please let us know about the result.

To view this discussion on the web visit https://groups.google.com/d/msgid/jsr371-users/CAOAQAPre_B3uMGUXmHtrwLetnMO3zQ7BP9RTHkJJ7qso63qq_Q%40mail.gmail.com.

[Reza Rahman]

I highly appreciate you guys standing behind Jakarta EE sooner rather than later. That is what is needed right now. Either path looks good, but I do not think you will be allowed to use anything other than javax in the JCP. It is worth checking nonetheless.

--

[Neil Griffin]

If I could vote, I'd vote +1 for the "current plan" since Apache Pluto went with "javax.mvc" with the following API:

    https://search.maven.org/artifact/javax.mvc/javax.mvc-api/1.0-pfd/bundle

Besides, the "alternative plan" would require that the mvc-api jar depend on the "javax." version of the JAX-RS API if it were to go final with the JCP in the short term.

Seems better to first go "all javax." and then subsequently "all jakarta." with a clean break.

To unsubscribe from this group and stop receiving emails from it, send an email to jsr371...@googlegroups.com.

[Tobias Erdle]

Hi Ivar,

are there any news on this topic or the roadmap for MVC 1.0?

To unsubscribe from this group and stop receiving emails from it, send an email to jsr371...@googlegroups.com.

[Reza Rahman]

Indeed I was hoping after Jakarta NoSQL, Jakarta MVC would be the next Jakarta EE specification to move forward.

If this is the case, I would highly encourage the specification leads to submit a forward looking talk to Jakarta One Live Stream.

Reza Rahman
Principal Program Manager
Java on Azure

Please note that views here are my own as an individual community member and do not represent the views of my employer.

To unsubscribe from this group and stop receiving emails from it, send an email to jsr371-users...@googlegroups.com.

To post to this group, send email to jsr371...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jsr371-users/c869e79f-1c5a-4399-b3d7-a83a9c9016b9%40googlegroups.com.

[Christian Kaltepoth]

Hi everyone,

our current plan is to go final with MVC 1.0 though the JCP as soon as possible. Unfortunately there are currently two pending issues:

• The TCK is done, but we need to create some documentation for it. I'm currently working on this. It shouldn't take very long, but I'm very busy at the moment.
• We have a few legal issues regarding Eclipse Krazo. Therefore, we currently are not allowed to publish releases of Krazo. As Eclipse Krazo is the MVC 1.0 RI, this is also a blocker for going final with the spec.

However, I'm hoping that both issues can be resolved soon. After MVC 1.0 is final, we will start the process of transferring the spec to the Eclipse Foundation.

Christian

To view this discussion on the web visit https://groups.google.com/d/msgid/jsr371-users/36d6941e-227b-20d3-565d-864573c0a863%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Christian Kaltepoth

Blog: http://blog.kaltepoth.de/

Twitter: http://twitter.com/chkal

GitHub: https://github.com/chkal