User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
I don't remember the history of why we contributed the document that
we did.
If there was a 1.3 version available, I would've thought we would
contribute that. Perhaps we lost the source to that version? I
don't know.
Tracking all this down and correcting it will likely time more time
and effort than it's worth. My advice is to just apply the same
sorts of changes that were made to the JCP version to create 1.3
from 1.2 and apply them to the Jakarta 1.2 version. I assume that's
a relatively small amount of changes.
If you think that's going to be too difficult and you want me to
track down the original 1.3 version, let me know.
Just from a visual inspection of the PDF I can see 1.3
seems to at least have changed a reference of EJB servers to
Java EE servers and added some data related to Java SE
providing the .xa package.
(I would note that although 1.3 talks about .xa being in
the Java SE packages there are sections that refer to how to
implement some of those [3.4 and 3.5] which might be better to
move to a relevant Java SE specification - however that might
be as well to discuss with the JTA list once we have clarity
on what spec version we are using).
I should have read the passage before
responding... The doc already states that only
"checkin" is required before starting work on the
doc. The "Approval" is required before the doc
can be included in a public release (or service
release). Any Milestone or Release Candidate
drivers are okay to include the doc before these
CQs are approved. If you look at the complete
list of CQs, you'll see about half of them are in
the Approved state. This is a state at the IP
team moves the CQ to -- after the development team
has updated the CQ with the information that the
source has been merged and any requested actions
have been taken care of.
On Wed, Feb 12,
2020 at 7:57 AM Kevin Sutter <kwsutter@xxxxxxxxx>
wrote:
That is not correct, Tom. The CQ gets
marked Approved after each component does the
required work to incorporate the source into
their repo. The keyword "checkin" is required
as well as PMC approval. I'll update those
instructions. Thanks!
On Wed, 22
Jan 2020 at 14:43, Kevin Sutter <sutter@xxxxxxxxxx>
wrote:
Just
to ensure that everyone knows about
this... Based on our efforts for the
Platform and Web Profile Specs, we
compiled some helpful hints. I just
referenced these when I did the
Jakarta-izing of the Managed Beans Spec
and it helped jog my memory. Good luck!
On
22/01/2020 11:54, Dmitry Kornilov
wrote:
> I am currently working on JPA
spec and facing the same issues. It’s
not difficult, but time consuming
because there is no other way than
doing it manually section by section.
+1
Also, from experience of doing the EL
and WebSocket specs watch for
escaping issues around code snippets.
I found there was a reasonable amount
that could be done via search and
replace on the source but you have to
review each one. You can't just do
a global search and replace.
And there was no getting away from the
repeated cycles of generate PDF,
proof-read, correct, repeat.
Mark
>
> - Dmitry
>
>> On 22 Jan 2020, at 12:42,
arjan tijms <arjan.tijms@xxxxxxxxx>
wrote:
>>
>> Hi,
>>
>> I just started with the
JASPIC to Jakarta Authentication spec
document conversion, and just a
heads-up for anyone who hasn't started
yet: it's quite labour intensive.
>>
>> Tables are completely
missing, image captions are mistaken
for headings meaning section numbering
and hierarchies are all wrong, even
chapter numbering can become all
wrong, footnotes are missing, etc etc.
>>
>> This is far more than just a
semi-automated search & replace
for terms as with the Javadocs
adjustments for Jakarta EE 8.
>>
>> Basically it boils down to
reading the entire document, adjusting
errors wherever you see them,
compiling the PDF, checking it's
correct now and repeat that.
>>
>> Absolutely doable of course,
but just taking a fair amount of time.
>>
>> Kind regards,
>> Arjan
>>
>>
_______________________________________________
>> jakartaee-platform-dev
mailing list
>> jakartaee-platform-dev@xxxxxxxxxxx
>> To change your delivery
options, retrieve your password, or
unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>
>
_______________________________________________
> jakartaee-platform-dev mailing
list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options,
retrieve your password, or unsubscribe
from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>
