►
From YouTube: Jenkins & Java 10+ Hackathon. Day 3. Meeting with JDK Project Jigsaw committers and sync-up
Description
- Several key JDK Project Jigsaw committers will join us to talk about Java 10/11 migration aspects and Quality Outreach program
- Teams talks about the progress and experiment results
Slides: https://docs.google.com/presentation/d/1i0vZjCqHohCZ6oDL4wm_KveXDz-lwf1FGisAYwoywCU/edit
Project doc: https://docs.google.com/document/d/1ed6wFOlq4cWrSL6UkCSzFbaY80AT-sk8ncB4Fz5QXyM/edit?usp=sharing
A
C
Yes,
I
I'm,
Paul,
I
I
know
some
of
the
help
these
folks,
because
I
used
to
work
for
a
little
bit.
I
know
Casey
for
a
long
time
in
Sun
Microsystems
and
that's
been
I
reached
well
fairly.
The
past
couple
of
years
been
working
on
the
Java
platform
a
little
bit
on
jigsaw,
but
other
things
to
language
libraries
in
runtime,
so
I
spread
myself
around
the
whole
platform
and
I'm
happy
to
be
here
and
help
as
best
as
I
can.
D
C
B
Okay,
thanks
so
yeah
you'll
have
a
shot,
happy
tune.
Intro
for
those
who
just
joined
the
hackathon,
then
you
will
have
a
great
session
with
Paul
and
many
other
project
jigsaw
contributors
in
order
to
discuss
issues
me
heat
and
questions
about
future
of
Java
and
what
we
need
to
do
to
become
what
about
mr.
xi
beyond
and
then
we
will
have
a
regular
status
update
from
our
contributors.
So
this
is
the
current
one.
If
you
want
to
watch
this
presentation
afterwards,
here's
a
link-
and
we
post
a
lot
of
the
presentations
and
now
YouTube
channel.
B
So
you
can
join
and
get
all
the
content.
If
you
want
to
ask
any
question,
we
also
have
a
dieter
her
channel
and
you
can
just
go
and
ask
questions
to
them.
So
it's
a
Gita
jankoji
is
less
Jenkins.
I
will
be
monitoring
this
chat.
So
we've
the
right
any
questions.
You
will
be
able
to
answer
questions
today.
Okay,.
B
B
Thank
you
for
the
introduction.
Okay,
yeah
I'll
briefly
describe
the
current
status
and
the
background
yeah.
So
as
everybody
on
this
call
knows,
Java
11
comes
soon
and
it
will
be
LCS
version
so
as
Jenkins
project
very
interested
to
keep
it
up
to
date
and
we
want
to
adopt
Java
11.
So
that's
why
we
decided
to
invest
some
effort
in
order
to
explore
what's
missing
in
Java,
10
plus
support
and
maybe
fix
some
beads
attention.
B
B
B
D
Right
all
right,
yeah,
so
I
guess
the.
Let
me
see
yeah.
So
we
are
you
thinking
the
election
I
think
B.
Sometimes
we
divide
that
for
work
so
well
to
the
point
of
like
we
don't
of
neatly
work
collaboratively
right,
so
it's
kind
of
looking,
for
we
have
some
opportunities
that
we
know
people
together
to
work
on
the
same
thing.
D
So
I
thought
this
is
a
great
topic
and
if
this
works
that
well
I'd
like
to
be
more
close
and
then
today,
I
feel
targeted
way
to
have
some
like
a
guys
from
the
Java
Sea
team
people
from
diversity
in
joining
us
like
take.
They
care
greatly
about
the
movie
which
are
very
persistent
or
then
they
think
that
work
that's
happening
here
and
also
the
likely
changes
that
propagating
upstream
in
different
libraries
I
think
it's
a
region
I
think
we
did
working
with
Emma
would
help
us
move
that
needle
a
lot.
B
Thank
you
for
the
introduction,
so
this
stuff,
this
hackathon
on
Monday,
and
we
already
had
two
full
days
of
development
and
actually
will
go
to
some
important
progress.
So
just
to
summarize
the
status
justly,
we
have
good
packaging
work,
including
Java.
Ten
and
eleven
releases
water
packages
run
guidelines,
and
we
also
created
some
dog
packages,
for
example,
for
lotion
for
vanilla,
Jenkins.
So
early
adopters
can
try
these
images
and
get
them
running
and
one
of
the
major
updates
it
that
people
got
a
pipeline
running.
B
So
there
is
a
rain
screen
shot,
but
actually
pipeline
was
a
major
effort
because
we
needed
to
update
Jenkins
course
to
update
some
plugins
in
order
to
make
it
work
in,
and
yet
it's
a
great
progress
on
this
front,
because
it's
one
of
the
major
features
and
we
want
to
make
it
available
as
soon
as
possible.
Regarding
other
tivities,
we
have
posted
a
blog
post
yesterday,
so
you
can
go
to
Jenkins
tile,
slash
blog
and
you
can
find
it
on
the
top.
So
it's
a
summary
from
the
update.
B
Nilly
ability
to
flip
the
foxes
clean
up,
clean
up
new
tools
like
asthma
and
animal
sniffers.
We
needed
to
build
plugins,
vcgt
ki-10
and
there
are
many
other
activities
ongoing.
So
this
is
the
current
status
we'll
have
more
details
later
of
the
after
the
creation
and
yep.
Just
to
summarize
the
current
obstacles,
what
we
see
in
the
project,
actually,
we've
got
the
most
of
free
Jenkins
working,
including
all
foundation
features,
but
we
experienced
issues
with
development
to
him.
B
So,
for
example,
we
cannot
stop
contains
integration
for
cotton
plugins,
it's
working
progress,
somebody
we
need
to
fix
up
some,
our
tooling
and
one
of
the
main
obstacles
is
made
in
support
of
which
over
10
and
11
and
support
of
multi
release
jars.
So
we
have
Devon
nose,
mom
and
an
equal
Duluth
on
the
call.
Maybe
they
could
briefly
summarize
waterborne
on
with
this
effort.
B
And
Niccolo
was
working
on
my
illegal
access
cleanup
because
we
have
lots
of
libraries,
including
different
extreme
jackson
and
other
such
tools.
All
of
them
do
some
reflection
by
default
and
you
need
to
clean
up
that
and
finally,
we
just
need
to
build
some
libraries,
because
newer
versions
we
adopt
require
Java
and
compatibility.
They
are
multi
release.
So
then
it
limits
our
communities
to
test
plug-in,
builds
and
yeah.
B
H
Yeah
so
I
put
a
lot
of
work
into
a
streamlined
set
of
general
GC
settings
tuned
for
Jenkins.
We've
had
very
good
results
with
the
G,
wouldn't
garbage
collector,
so
I
think
that's
sort
of
a
feather
and
you
guys,
as
Catholic
as
you've
done
really
good
work.
There.
I
guess
that's
mostly
looking
to
see
what
new
new
settings
are
available
and
what
has
changed
with
regards
especially
to
the
g1
settings
that
we
should
be
aware
of.
It
might
want
to
take
advantage.
Oh.
C
So
there's
been
a
lot
of
incremental
improvements
going
forward
in
g1,
I,
don't
know
on
the
flags.
I
can
get
back
to
you
on
that.
There's
a
bunt.
There
should
be
a
bunch
of
yep,
so
plea
or
bunch
of
issues.
Pre-Release
notes
you
can
track,
but
I
can't
off
the
top.
My
head
sort
of
dictate
the
incremental
changes.
I
just
know,
there's
been
a
bunch
of
improvements
to
do.
You
want
to
improve
this
functionality
agenda.
E
E
C
C
I
G
G
B
Not
we
already
have
for
a
GDK
levin
packages
working
so
maybe
we
could
try
them
yeah.
Thank
you.
The
next
question
was
about
jigsaw
models,
but
maybe
we
could
put
it
for
a
while,
because
you
know
if
you
have
mark
on
the
call
later-
and
we
put
talked
about
it
in
detail
or
maybe
we
can
discuss
it
later
when
we
are
done
with
other
questions.
Yes,.
B
C
So
mark
gave
a
talk
at
devoxx
UK,
where
he
summarized
some
of
this.
It
would
be
if
you
haven't
seen
that
that
might
be
useful,
good
good
to
see
because
he
talks
about
that
has
a
bunch
of
technologies
that
have
shifted
there.
He
also
asked
people
to
tweet
about
this
and
I
think
you
I,
don't
if
he
kept
the
archives
of
those,
but
he.
C
D
C
They're
regularly
testing,
10
or
11
builds
now
Nettie
is
doing
well,
it's
it's
keeping
up
with
changes
by
the
tracking
in
11.
Just
talk
about
regressions
that
we're
fixing
I'm
trying
to
think
of
other
libraries.
Those
are
the
ones
off
the
top
of
my
head,
my
general
senses.
Things
are
moving
forward
faster
than
I
expected.
B
Yeah,
actually
it's
also
our
experience
because
year
when
we
were
prepared
to
the
hackathon,
we
expected
that
they
will
be
serious
obstacles
to
get
everything
running.
Yeah
nice
to
have
a
goal
was
to
maybe
get
some
bits
of
pipeline
working,
but
actually
after
few
patches,
we
that
the
most
of
the
infrastructure
working
so
forth.
Emigration
was
much
easier
than
we
expected
so
far.
Maybe.
C
J
A
C
C
B
B
B
B
Okay,
so
the
question
is:
had
we
had
this?
A
few
is
about
future
of
reflection,
because
in
original
Lloyd
gdk9
bills
will
prohibit
incredi
flexion
by
default,
and
it
caused
a
lot
of
issues
for
doctors.
So
then
it
has
been
reverted
and
yes,
so
far.
We
it's
still
not
mandatory
to
comply
with
reflective
access
requirements,
so
it
would
be
a
greater
understand
what
other
plans
for
the
future.
E
Okay,
the
illegal
access
is
still
permitted
in
eleven.
We
didn't
change
that
one,
so
we
always
encourage
the
application,
developers
or
library
developers
to
try
to
turn
on
denial
so
that
to
find
out
earlier,
both
libraries
doing
illegal
reef
active
access
so
that
they
can
report
to
the
library
others
to
fix
the
issues
yeah
earlier
to
prepare
yeah
when
we
disable
it
yeah
I
mean
when
we
turn
it
on
denial,
yeah.
B
It's
what
we
experienced
so
we
also
did
some
test
and
quiz
enabled
Diagnostics,
and
you
just
step
until
find
that
the
ticket
yeah
I,
guess
they
all
start
from
here,
and
then
you
find
it
so
yeah
for
Java
ten
compatibility.
We
have
lots
of
tickets
submitted
from
different
components.
Some
of
them
are
on
libraries.
Some
of
them
are
external
libraries
and
the
age
where
this
list
is
not
complete
so
and
if
you
wish
across
the
code
base,
you
can
may
see
hundreds
of
set
accessible
calls.
E
E
C
Know
I
think
it's
to
be
determined
based
on
feedback
really
I.
Think
that's
an
important
part
is
getting
feedback
from
the
community
to
decide
when
to
ratchet
this
up
and
so
what
to
what
extent,
whether
it
should
be
done
in
one
go
or
done
iteratively,
because
you
can,
you
can
sort
of
increase
the
strength
of
it
in
grades,
so
I
think
it's
to
be
determined
and
I
think
it's
dependent
on
the
reactions
in
the
community
and
if
major
libraries
already
or
not
hi,.
K
D
C
D
C
Might
have
done
this
because
they're
very
very
strict
in
what
they
do.
Neti
neti
look
needs
to
go
into
the
internals
of
the
kvk
and
they
can
operate
without
unsafe
access.
If
it's
not
there
and
they
fall
back
in
slower
mode,
but
for
SuperSpeed
they
want
to
go
into
the
JDK.
So
it
could
take
a
long
time
or
to
get
them
off
say
the
unsafe
thing,
which
is
like
a
separate
issue.
C
C
The
plan
is
to
remove
unsafe
when
we
we've
reached
safe,
supported
public
API
store.
All
that
could
take
a
long
time,
because
some
of
the
use
cases
that
people
use
unsafe
for
are
for
what
people,
what
we're
working
on
projects
like
Valhalla
for
value
types,
project,
cannon,
mark
the
better
native
interrupts.
C
So
we
these
are
is
a
long-term
investments
in
the
platform
and
until
those
get
integrated
into
the
platform
and
people
will
still
need
to
use
unsafe
for
things
in
it,
and
something
simple
is
a
bit
of
an
arms
race
as
we
we
produce
these
new
features
and
then
other
people
want
to
put
the
platform
even
further.
If
you
want
to
be
compared,
memory
unsafe
is
what
you've
got
and
there's
always
some
strange
use.
C
D
H
C
The
access
to
private
feels
really
dialing
dialing
up
and
if
we're
just
talking
about
the
classpath,
we're
really
restricting
access
to
stuff
within
the
JDK,
we
don't
want
people.
We
want
to
try
and
restrict
people
poking
around
into
the
JDK
internals,
because
it
limits
what
optimizations
we
can
do
and
it
limits
how
we
can
change
the
internals
going
forward.
So
that's
the
primary
focus
when
we're
dealing
with
modules,
there's
other
ways
to
express
that
you
allow
someone
to
do
reflective
access
to
you.
That's
called
open
modules.
So,
but
that's.
D
C
C
But
we're
primarily
a
Mandy
Mandy
can
correct
or
confirm
we're
primarily
trying
to
get
people
from
poking
around
in
the
internals
of
JDK,
for
example
extreme
poking
around
in
tree
set
or
tree
map.
To
do
some
optimization
cetera
it
does
some
pretty
and
if
we
refactor
tree
map
we've
broken
x3,
they
don't
know
about
it
and
then
the
libraries
that
users
find
this
out
through
you
know
all
sorts
of
means
and
I
think
it's
treatable.
I
can't
remember
exactly
is.
G
I
H
C
Because
it
because
there's
when
the
hotspot
compiler
has
certain
assumptions
layouts
and
classes
like,
for
example,
string,
you
know
we
change
the
internals
of
string
so
but
it
actually
is
a
byte
array,
not
a
char
array
and
some
people
poke
around
and
string
and
now
that
will
fail.
But
we've
made
some
optimizations
in
string
called
compact
strings.
So
we
use
less
memory
for
utf-8
to
ASCII
strings,
there's
other
areas
in
java.lang
endowed
with
method
handles
as
optimizations
around
final
fields
and
stuff
like
that.
H
C
I
mean
if
you're
poking
around
internals,
because
you're
working
around
the
bug
or
you
need
you
need
another
API
point.
This
is
what
we'd
love
to
hear
about,
because
it
may
be
able
to
provide
public
support
for
the
use
cases
that
aren't
available
at
the
moment.
Mm-Hmm
there's
certain
cases
that
are
harder
than
others.
For
example,
people
want
access
to
the
dress
of
the
direct
byte
buffer,
and
that
is
obviously
once
you've
got
that
and
you
pass
that
around.
That
is
obviously
unsafe.
C
B
E
For
class
loading
yep
it
one
use
case
we
found
is
people
like
some
libraries
poking
too
protected
in
fine
class
view
of
class
Rhoda.
They
don't,
they
don't
have
to
access
to
the
class
of
the
hierarchy,
the
class
itself,
so
they
cannot
extend
to
it
and
they
define
the
class.
So
what
we
add
in
nine
for
them
to
replace
it
is
lookup
define
class.
So
you
as
if
you
can
securely
get
your
lookup
to
define
a
class
in
your
runtime
package
of
the
looker
class
yeah,
then
you
can
use
this
new
API.
A
B
E
B
E
B
F
E
If
you
can
yeah,
that's
actually
what
we
want
to
do
to
provide
elect
little
access
warning
message
so
that
you
know
okay,
you're
refer
to
flee
accessing
some
private
or
method,
and
if
you
have
a,
we
want
to
hear
from
you
why
you
used
that
reflective
access
and
what
we
don't
have
in
the
public
API
to
achieve
that
yeah
then
we
should.
You
should
also
follow
GPS
issue
so
that
we
can
follow
up
yeah.
E
E
B
B
If
somebody
wants
to
ask
the
questions,
do
you
think
the
call
please
feel
free
to
just
propose
to
them
in
the
bottom
will
try
to
reach
them?
Okay,
then,
let's
move
on
mm.
Another
question
I
heard
was
about
Java
EE
models,
so
currently,
Jenkins
core
depends
on
MAGIX
B.
So
it
means
that
we
use
some
models
which
had
been
removed
from
Java
well
yeah.
E
B
E
B
B
Okay,
thank
you.
So
in
our
case
you
have
some
flexibility
because
we're
on
this
several
web
service
and
since
we
have
Jenkins,
was
holding
from
plugins,
we
have
a
choice
to
upload
these
libraries
to
a
particular
plugin
so
using
Jenkins
to
link.
We
have
a
way
to
approach
that,
but
you
may,
if
there
are
any
other
standard
tools,
it
will
be
great.
No,
yes,.
D
D
You
can
only
running
it
every
it's
great,
but
we
don't
need
to
immediately
expect
that
we
come
to,
but
maybe
yes,
but
then
we
also
have
to
run
almost
like
a
standalone
saga
container,
which
has
not
published
the
work
up
its
ass
as
I
walk
out
of
Albania
by
in
the
past,
I
feel
like
we
did
it.
I
can
basically
when
it
came
down
to
just
fun,
doing
it
and
then
kind
of
hope
that
the
use
of
the
container
I'd
be
able
to
recognize,
or
the
jacksie
in
this
case
that
we
can
correctly
review.
D
D
C
Try
and
make
that
easier,
I
think
the
assumption
was
but
you'd
be
in
some
incompatible
environment,
I
guess
in
that
perspective,
and
you
kind
of
having
to
do
probably
class
loading
tricks
or
something
like
that.
Didn't
you
do
that
for
ready
to
try
and
work
around
the
jacks
be
version
that
was
distributed
in
the
JDK
I
wanted
to
upgrade
it
to
a
newer
version
that
you.
I
C
Mean
this
is
kind
of
a
similar
problem
to
when,
because
Jack's
be
used
to
evolve
so
slowly
in
the
JDK
compared
to
Jack's,
be
outsider
and
people
want
to
distribute
their
own
versions
or
to
override
it,
and
that
problem
is
it's
probably
over
idea.
It
may
be,
it
may
be
there,
it
may
not
be
there.
You
don't
dealing
with
its
of
expanding,
but
the
problem
out
to
something
that
isn't
there
I'm
wondering
if
they're
fundamentally
the
same
problem.
Yes,
I
think
it
is.
C
What
yeah
I'm
sorry
about
that
I
mean
what
we
try
to
do
when
we
in
preparation
for
variables
make
sure
that
they're
not
there
by
default
when
you
run
it
so
that
it
highlights
fit
so
it
gets.
People
used
to
now,
LZ
10
I,
believe
no
11
they've
gone
to
Jakarta
EEE!
Isn't
that
right,
maybe
they've
gone
to
that
environment
to
be
maintained
and
developed.
C
B
Thanks,
okay,
thank
you.
Maybe
we
should
pick
some
questions
from
others
and
then
I
return
to
my
question,
see
ya,
perhaps
a
minute
a
lot
of
them
and
we
can
return
to
them
later.
One
of
the
question
were:
questions
was
from
went
in
Ian's
doctor.
What
would
be
the
replacement
of
some
misc
signal
donor?
Yes,
we.
E
A
E
E
One
use
case
we
believe
we
found
is
like
control
see
they
wants
to
intercept
a
signals
and
handle
it
things
like
that,
so
it
just
depends
on
the
use
case.
So
we
so
far
we
do
not
really
see
a
high
demand,
but
to
your
question
is,
is
still
supported
in
JDK,
I
mean
it's
still
available
as
a
internal
and
supporter
API
in
11.
D
K
D
Then
in
the
UNIX
land,
the
signal
these
are
kind
of
important
part
of
the
ecosystem.
Example,
like
you,
seem
to
see
how
badly
did
he
know
the
configuration?
Yes,
the
fact
that
you
know
in
a
way
like
the
way
I
think
of
it
is
the
active
the
Jenkins
is
implemented
in
Java
is
an
implementation
detail
for
the
developer,
something
that
I
didn't
want
users
to
camera.
So
that's
the
kind
of
an
overtime
so
I
mean.
If
you
ask
me,
can
we
work
that
around
it?
D
Yes,
like
know,
you
can
read
even
drop
it
and
it's
kind
of
not
the
end
of
the
world
I
suppose,
but
it
sort
of
like
a
moves
has
to
be
further
away
from
that.
If
this
process
functional
behaving
citizen
and
that's
sort
of
like
when
people
hate
I
like
we
have
no
more
hands-on
objections
on
the
behalf
of
the
users,
we
have
some
hostile
feel
into
Java,
and
then
this
is
not
behaving
like
other
tools
in
there
to
say
this.
One
yeah.
C
It's
it's
still
in
the
unsupported,
not
you
learn,
it
will
still
stay
there
until
I
think
we
can
work
out.
They
use
use
case
right
and
he's
right.
It's
kind
of
something
that's
not
as
heavily
used
as
others,
and
we
really
unsupportive
module.
But
it's
it's
used
nothing.
Some
areas,
I
think
we
kept
it
around
until
we
can
work
out.
C
Something
I
mean
problem
we
have
with
some
of
these
cases
is
that
we
have
Windows,
Mac
and
unit
variations
of
UNIX
to
support
their
job
and
often
the
challenge
with
these
cost
platform
uses
Windows
and
getting
that
it's
getting
better.
But
we
and
and
some
of
the
challenges
you
have
with
file
access
and
stuff
about,
is
windows,
and
this
is
one
one
reason
why
it
takes
a
while
and
then
people
come
out
to
say
they
don't
care
about
Windows
until
they
deploy.
C
C
C
So
another
area
we're
looking
at
in
terms
of
system
II
Java,
if
you
like
better,
is-
is
project
Panama.
We
want
to
get
better
at
interoperating
with
the
platform
and
interoperate
with
native
right,
I'm
I'm,
a
great
fan
of
having
like
kind
of
like
POSIX,
yes,
JRuby
does
that
well,
but
we
think
with
Panama
we
might
be
able
to
get
closer
to
a
POSIX
support
yeah
in
that
and
it's
interesting
to
see
where,
as
well
as
going
with
Windows
and
it
seems
like
Windows-
is
moving.
You.
I
I
C
H
E
Yeah,
you
could
send
it
to
car
library
call
lips
depth.
That's
one
thing:
the
other
I
I
can
send
you
their
JPS
issue
number
that
we
keep
track
of
all
this
information.
I
think
why
I
asked
for
use
cases
they're
we're
looking
to
do
like
we
look
into
a
API
to
support
the
POSIX
like
signal
handling
a
more
generic
one.
That's
one
thing,
but
it
involves
interaction
with
the
VM.
E
Vm
also
have
the
handlers
for
various
signals,
so
we
have
to
come
up
with
a
API
that
out
define
it
yeah,
it's
kind
of
very
tricky
to
define
an
API
of
such
a
generic
way
and
whether
it's
synchronous
or
asynchronous
it's
another
factor
to
consider.
So
if
we
know
only
specific
use
case
rather
than
generic
signal
handling,
then
it
might
be
faster
to
come
up
with
a
API
specific
for
that.
So
right,
but
I
hear
that.
E
B
B
C
So
that's
it
and
I,
don't
know
if
anyone
has
stepped
up
yet
or
is
interested
in
maintaining
it
outside
of
the
JDK.
That
is
one
way
of
deciding.
What
happens
in
the
future
is
whether
those
there's
enough,
if
community
interest
out
there
to
maintain
a
bit
like
JavaFX,
because
that
was
that's
that's
going
out
from
the
jdk,
but
there's
a
there's,
there's
a
set
of
interested
people,
both
companies
and
individuals,
and
open
source
interested
in
maintaining
this
going
forward.
The
interests,
if
is
there's
enough
interest,
didn't
ask
one
to
do
the
same.
C
If
there's
not
I
it's
likely
to
get
deprecated
in
it,
didn't
get
defecated
and
then
removed
from
the
jdk
in
the
source
will
be
there
somewhere.
So
one
alternative
is,
it
gets
picked
up
by
the
community.
The
other
alternatives
are
drought,
as
you
say,
I
don't
think,
there's
any
official
announcement
from
us
on
on
what
what
an
alternative.
C
C
C
C
So
one
thing
that
I
think
is
being
decided
or
is
was
for
the
last
one
depends
on
the
library
called
Dino
link
and
originally
dine
link
was
proposed
at
Nazca
land
to
be
deprecated.
But
the
original
engineer
who
did
Dino
link
is
he's
not
an
Oracle
anymore,
but
he
said
he's
willing
to
step
up
and
maintain
Dino
link.
So
that's
something,
but
we
I
don't
think
is
going
to
be
proposal.
Deprecation.
E
E
B
C
That's
a
presentation
that
Jake
from
the
last
by
Jin
Lasky
the
original
architect
and
that's
one.
It
talks
about
an
alternative
approach,
no
plans
on
whether
this
is
going
forward
or
not
it's
the
prototype
and
investigation
of
it
it
you
could
see
where
we
might
be
heading
with
this
or
not.
If
you
curious
about
how
to
integrate
alternative
ISM
into
the
JDK.
B
B
Okay,
so
we
have
something
like
five
minutes
left
for
Kui.
Actually,
we
have
several
another
rest
questions.
One
was
about
Java
Web,
Start
removal.
Then
there
was
a
question
about
quality
outreach
program
which
maybe
we
should
start
from
this
question,
because
it
seems
to
be
a
question
we
may
follow
or
if
we
continue
moving
on
John
10:11
supposed,
it
would
be
a
great
to
have
your
insights,
how
the
program
works
and
which
benefits
do
we
get,
and
how
could
we
contribute
and
how
can
we
get
contributions,
so
we
get
a
win-win
solution.
Well,
let
me.
B
C
B
C
C
B
It's
perfectly
fine,
or
at
least
we
have
a
contract.
So
then
maybe
we
can
follow
up
on
that
later.
Okay,
thank
you!
Okay,
so
if
we
continue
from
the
top
one
of
the
question,
maybe
half
is
Java
Web
Start
removal,
because
we
have
Java
Web
Start
being
used
for
Jenkins
core
itself
and
for
hijinks
agents.
B
D
C
I
D
D
So
I
mean
leads.
Yes,
the
whole
back
I
think
the
current
format,
if
I
understand
where
the
team
is
kind
of
about
this,
just
we're
gonna
have
to
ask
people
to
open
the
command
line
that
type
Java
download
some
files
and
stuff
like
that.
So
it's
not
the
end
of
the
world,
but
it's
not
only
a
digression.
The
usability
yes
Verena.
We
have
wasted
it.
People
still
click
around
a
few
times
to
run
a
program.
C
It's
important
prominently.
Your
use
case
is
great
when
there's
trust
involved
in
what's
going
on,
but
when
you
don't
have
trust
in
applets
and
all
this,
it's
a
really
hard
environment
to
secure
and
it's
it's
something
we
we're
trying
to
move
away
from
in
terms
of
distribution
of
applets
start
was
it
was.
It
was
a
key
part
of.
D
I
D
D
C
C
You
could
decide
to
package
but
whole
jdk
plus
the
bits
you
need
to
communicate
as
an
image,
and
you
can
put
that
in
a
docker
image.
If
you
want
it
doctor
gives
you
an
easier
way
to
do
strap
across
this
or
not
depends
a
capability
that
you
could
certainly
experiment
that
way.
So
everything
is
nicely
packaged
and
bunny
as
one
as
one
sort
of
degenerate,
a
plus
bits
you
need,
and
you
can
shrink
it
down
to
what
you
need.
C
So
you
don't
need
to
distribute
it
where
some,
what
is
it
I'm
going
to
think
of
other
packages
and
mask
on,
for
example,
if
it's
still
a
that
this
view
with
that
I
mean
you,
you
pretty
much
need
Java
base,
plus
the
slave,
don't
jar
or
whatever
it
is
I,
don't
know
whatever
depends
yeah,
but
a
lot
of
dependencies
come
through
your
remoting
and
you
lay
down
the
jars
of
the
other
penances
on
your
own
item
service
slave
me.
It's
like
a
shame.
C
Isn't
that
just
a
conduit
to
push
other
dependencies
their
answer,
you
could
probably
get
away
with
quite
a
minimal
runtime
here.
Here's
an
experiment
I'd
be
interested
in.
You
could
even
try
the
girl
runtime
to
shrink
down
that
an
executable
binary
and
straight
down
the
size
of
that
and
to
speed
up
the
startup
time
at
that
as
an
experiment,
a
separate
thing.
This
is
off
the
top
of
my
head,
but
it
allows
you
to
do
that
kind
of
experiment
going
forward.
It's
a
great
and.
B
C
E
C
K
E
B
C
B
B
Okay,
should
we
move
on
so
it's
settled
a
genetic
question:
are
there
any
other
incoming
changes
in
Java
11?
We
should
consider
so,
for
example,
if
you
open
change,
look
you
may
see
that
there
are
lots
of
changes
and
and
I'll
select
a
logic
so
yeah,
since
we
heavily
use
this
logic,
for
example,
for
the
motive
communication.
It
would
be
nice
to
get
your
insights
to
which
issues
should
be
prepared
and
how
should
be
tested
with
Java
11
when
we
can
get
to
that.
C
C
C
B
C
Yes,
that
is
a
great
use
case
for
this,
given
how
its
deployed
at
scale
the
another
area-
it's
not
just
related
to
not
related
to
neo,
is
HTTP
client.
So
there's
a
new
HTTP
client
it
was.
It
was
incubating
in
nine
and
now
and
ten
and
now
for
eleven,
it's
going
to
be
fully
supported,
API,
it's
much
better
than
HTTP
year.
Our
connection,
which
is
a
train
wreck
of
an
API
in
fire
pinion
and
it's
scales
as
well.
It
should
be
has
very
good
asynchronous
implementation,
underneath
it
might
be
something
you're
interested
in
yes,.
C
B
C
G
B
E
E
E
B
B
C
Don't
know
when
it
comes
into
talker,
my
current
remember
what
the
EA
release
naturalism
in
JDK,
but
but
rather
than
I,
have
a
problem
with
open,
JDK
or
JDK
images
on
docker
hub
I.
Don't
know
where
that
come
from
when
doctor
hub
there
who's
a
produced
by
is
that
produced
by
also
by
some
third
party.
C
C
C
Would
get
the
images
from
opening
openjdk
the
GPL
if
you
want
to
continue
kay
I,
think
someone's
getting
them
alright
anyway
and
build
your
own
docker
images?
Doesn't
my
personal
opinion
if
you're
going
to
distribute
your
own
docker
images,
and
so
you
can
serve
them
from
your
own
area
or
you
increase
the
trust
of
what
he's
contained.
I,
don't
know
this
is
coming
from
me
who
doesn't
have
a
lot
of
experience
in
the
container
and
docker
world
and
how
it
operates.
No.
B
C
F
C
B
G
C
B
D
H
Would
say
that
my
experience
with
Java
and
especially
Jenkins
and
docker
has
generally
been
good.
The
only
quirks
I've
seen
have
to
do
with
spec'ing
out
what
the
it.
What
the
job
instance
running
within
the
container
is
allowed
to
use
resource,
wise
and
I.
Think
a
lot
of
that
has
been
addressed
now.
Yes,
I
I
have
really
nothing
that's
safe,
but
so,
if
that's
good
feedback.
H
B
B
H
H
H
B
So
just
them
I
started
the
English
I
used
the
wrong
port,
but
it
shouldn't
matter
for
now
so
yeah
when
I
connect,
remote
debugger
means
Java
10.
For
me
just
feels
yeah.
It
is
something
like
that:
handshake,
failed
connection
prematurely
closed,
but
yeah.
If
you
take
a
look
at
the
English,
it
still
waits
for
connection.
C
B
C
If
we
know
roughly
what
JDK
versions
project
Panama
will
be
landing
in
or
is
it
likely
to
pre
spread
out
several?
So
we
don't
we
don't.
In
general,
we
don't
target
to
release
until
something
is.
We
think
something
is
ready,
but
what
we've?
Given
that
faster
release
cycle,
what
we
try
to
do
is
to
take
a
large
project
and
split
it
out
into
smaller
penny
pieces.
C
So
we
can
deliver
value
sooner
and
that's
a
hard
challenge
because
you
don't
want
to
live
with
something
sooner
and
then
it
becomes
broken
or
outdated
or
wrongly
design
compared
to
the
larger
picture.
So
we
do
have
to
balance
that
so
we
don't
have
it
don't
have
a
targeted
release
for
Panama.
Yet
that's
all
I
can
say
about
that.
C
C
B
C
C
Say
we
want
to
integrate
with
the
open
or
a
CUDA
or
OpenCL
GPU,
and
so
you
should
be
able
to
take
the
the
headers
and
run
at
all
over
it
to
generate
Java
interfaces
which
describe
the
methods
and
the
data
structures
and
then
at
runtime.
You
can
bind
those
interfaces
and
data
structures
so
that
it
calls
directly
through
to
that
library,
and
so
you
need.
You
need
a
notion
of
how
to
map
the
C
or
C++
model
into
Java
with
with
reasonable
accuracy.
C
So,
basically
that
takes
away
the
previously
to
do
that
by
hand.
You
had
to
write
a
whole
load
of
jet
Java,
J&I,
Duke
and
Java
and
C
or
C++
integration
group,
and
that's
very
error-prone.
So
it
takes
away
that
the
it
gives
you
a
huge
bootstrap
into
into
interoperating
and
as
part
of
this
API,
we
hope
to
improve
the
speed
of
the
Interop
speed
of
J&I.
Because
often
it
a
cost
to
go
into
the
native
boundary
between
the
DM
and
outside,
and
we
hope
to
optimize
that
as
well.
I.
C
We
want
to
use
it
ourselves
internally
too,
so
when
you
bind
to
anything
it
will
actually
bind
it
to
a
particular
platform.
It
won't
be
cross-platform.
It's
up
to
you
to
because
different
different
header
files
on
different
platforms
will
have
different
ways
of
expressing.
This
is
quite
subtle.
Sometimes
so
it
provides
you
about
that
layer
and
then,
if
you
want
to
go
a
layer
above,
you
may
have
to
write
your
own
interoperable
layer
above
that,
depending
on
them
how
cross-platform
header
files
are.