The reason the spec name was included is because when all the
javadocs are combined to form the platform javadocs, it's much less
clear what spec "1.1" refers to.
Using a Jakarta spec name in @since can be misleading or wrong since
we didn't have old versions of the Jakarta specs. Still, I think
that's better than dropping the spec name entirely and introducing
the ambiguity.
Scott Stark wrote on 7/15/19 11:42 AM:
The most common things seems to be to simply drop the reference to
the spec
@since Common Annotations 1.1 -> @since 1.1
How do we handle "@since" tags?
For example:
> * @since Common Annotations 1.1
I'm guessing we leave them but I wanted to
make sure.
- Ray
Right,
the staged approach is what we are going to have to
do.
Just to follow up on the TCK
call from earlier today.
Please can we confirm a
decision for spec leads on how to deal
with dependencies on other Jakarta EE
projects in their poms and whether to
proceed to staging/TCK runs before those
other projects release or whether we
will form some kind of sequencing?
Perhaps as a community we could do it in
two stages? Request an initial release
to staging this week with current
dependency sets then a follow up release
once we know all the artifacts are
staged?
Hi,
First, a
message to all the specification
project leads:
You are strongly
encouraged to join this mailing
list:
We are on a tight
schedule to get the Jakarta EE
specifications ready for the Jakarta
EE 8 Release. I am in the process of
creating GitHub issues in the
projects that will be followed up
here: https://github.com/orgs/eclipse-ee4j/projects/15
If you don't have an
issue created for you yet, please
feel free to create an issue titled
"Prepare Jakarta XXX for the Jakarta
EE 8 Release" with the following
content in your issue tracker:
-----
------
All the above need to be
done by July 15 in order to follow
the plan for the Jakarta EE 8
Release.
Ivar
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve
your password, or unsubscribe from this
list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
--
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
|