Re: [krazo-dev] [jsr371-users] Re: the javax discussion

[Christian Kaltepoth <christian@xxxxxxxxxxxx>]

👍

Please let us know about the result.

Ivar Grimstad <ivar.grimstad@xxxxxxxxx> schrieb am Mo., 6. Mai 2019, 20:03:

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

On Mon, May 6, 2019 at 3:01 PM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:

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.grimstad@xxxxxxxxx> 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 <gregor@xxxxxxxx> 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
krazo-dev@xxxxxxxxxxx
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
krazo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/krazo-dev

--
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+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to jsr371-users@xxxxxxxxxxxxxxxx.
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.

--
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+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to jsr371-users@xxxxxxxxxxxxxxxx.
To view this discussion on the web visit https://groups.google.com/d/msgid/jsr371-users/CAOAQAPre_B3uMGUXmHtrwLetnMO3zQ7BP9RTHkJJ7qso63qq_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.