►
From YouTube: JCasC Office Hours (Aug 29, 2018)
Description
JCasC plugin status update and discussions.
B
B
A
B
Then
I
misunderstood
the
decision,
so
I
started
creating
mailing
least
get
ur
chat
rooms
and
everything,
and
then
I
like
made
me
aware
of
the
fact
that
it's
not
what
we
decided
so
I
have
a
better
internet
connection.
Now
so
maybe
we
can.
We
can
make
sure
that
we
all
understand
each
other
this
time.
So
what
you're,
suggesting
and
I
assume
what
others
agreed
on
is
that
we
stay
at
the
cloud
native
see
we
don't
create
separate.
The
configuration
is
called
seek.
B
B
C
A
B
Okay,
an
inflection
point
was
yeah.
Alexandra
was
working
on
two
issues
in
one
PR,
one
was
regarding
introducing
text
fields
under
configuration
is
called
sub
page
in
managing
Keynes,
so
we
can
provide
a
new
configuration
source,
and
that
was
my
request.
I
was
having
trouble
when
I
was
you
Jenkins
local
installed
locally,
like
just
a
nap,
not
not
a
docker
container
and
since
I
want
I
want
to
work
on
a
blog
post,
where
I
describe
two
use.
B
Cases
for
running
drinking
this
code
and
I
want
to
make
it
as
easy
as
possible
for
people
that
are
not
very
fluent
with
terminal,
yet
they
are
just
starting.
Then
I
I
really
wanted
to
have
a
possibility
to
manage
the
location
of
configuration
so
source
via
UI,
and
it's
done
the
other
one
was
dry,
run
and
I.
Don't
think
that
one
is
finished,
we
will
hopefully
discuss
that
today.
B
Then
I
was
supposed
to
release
new
alpha.
Oh
that
was
a
long
time
ago.
We
in
pragma
had
messed
up
something
with
our
release
mechanism,
so
Nicola
released
a
couple
of
times
alpha
and
then
released
candidate.
One
and
last
week
mus
released
released
candidates.
Two
because
we
wanted
to
have
this
thing
implemented
that
Alexandra
the
UI
text
field
for
configuration
source
location,
so
that
one
is
done
and
then
oh
yeah
I
did
not
discuss
merging
to
master.
B
Maybe
there
is
a
enough
of
us
now
at
the
meeting,
so
we
can
talk
about
that
and
somebody
to
fix
the
master
branch
while
master
branch
was
fixed,
so
more
or
less
good,
hey,
Oleg!
You
were
attending
the
previous
meeting.
Is
there
anything
else
you
wanna
mention
regarding
that
one,
or
should
we
move
on.
B
Very
good
so
well,
the
next
point
in
the
India
agenda
is
really
status,
but
it's
basically
dead
take
ask
status.
We
we
had
planned
to
release
official
one
zero
sometime
in
the
middle
of
August.
It
didn't
happen
and-
and
that's
that's,
not
a
huge
problem,
but
we
definitely
want
to
have
it
before
drinking's
world
sometime
next
week
or
or
yeah
of
the
following
week.
That's
that's
my
opinion.
So
I'm
looking
at
the
release,
one
zero,
milestone
and
I
hope
you
can
see
that
we
only
have
one.
A
A
C
So
I
was
thinking
that
his
main
concern
was
that
once
we
shed
sneaky
mo,
if
we
have
reference
in
the
API,
then
it
will
change
the
API.
That's
a
reason.
I
was
lowering
priority
because
we
don't
have
any
more
reference
to
sneaking
mo
in
the
public
API,
it's
just
a
bundle
dependency.
So
for
sure
we
are
some
other
plugins
that
rely
on
configures
code
to
get
this
dependency
in
class
pass,
which
is
probably
the
worst
way
to
manage
dependencies,
and
then
there
is
some
compatibility
risk.
A
A
Yes,
so
my
preference
would
be
to
shade
it
anyway.
Alternative
option
would
be
to
just
at
section
about
that
to
developer
documentation
so
that
it's
explicit
that
snake
Jamal
shouldn't
be
used
from
the
plug-in.
It
won't
help
much
because
people
will
be
still
implementing
that
they
potentially
getting
into
upper
bound
dependency
issues.
If
the
Yama
plug-in
stratum
came
in
Jake
asked
and
also
have
their
own
functionality
so
shading
before
the
release
looks
like
the
most
safe
approach
to
me
and.
B
A
B
B
A
So
there
are
several
examples
of
shading
libraries
and
Jenkins
so,
for
example,
in
dr.
traceability
and
yet
another
docker,
plugin,
etc.
The
main
problem
that
currently
you
cannot
shade
libraries
in
plugin
poem.
So
you
need
to
create
another
model
which
which
just
does
a
library,
shading
and
then
tied
it
as
a
dependency
way.
It's
a
bit
weird,
but
you
haven't
fixed
it
yet
right.
C
A
B
A
A
B
A
B
A
B
B
B
And
prep
emigration
description,
that's
that's
also
documentation
and
it
it
will
be
part
of
what
I
will
working
out,
and
this
is
just
a
cosmetic
change
in
the
contribute
code
text
in
managing
keys.
So
that
friend
that's
a
piece
of
cake.
Okay
and
then,
let's
see
what
we
have
here,
Jenkins
down
after
installing
planning.
C
B
A
A
B
A
B
A
A
Well,
from
what
you
may
see
in
the
walk,
the
wrists,
a
plug-in
emission
needs
to
be
updated,
so
two
relations
so
yeah
the
the
real
problem
that
he
gets
into
issues
when
there
is
a
restart.
So
it's
not
a
problem
that
such
thing
happens,
the
reinstallation
it
happens
when
you
obey
the
dependencies,
but
concurrent
modification
in
a
reactor
yeah.
This
is
something
weird
I
understand
why
it
might
happen,
but
yeah
whatever
happens
here
is
a
Jenkins
mask.
Okay,.
B
A
B
And
then
you
see
that
we
can
keep
plugging
like
in
installation
as
beta
and
then
just
down
prioritize
plug
in
with
a
pregnant
one
date
related
issues
right,
yeah
and
is
anyone
a
objecting
because
I
I
want
to
release
one
zero
and
I'm
happy
to
release
it
without
some
features?
I'm
not
happy
to
release
it
without
features
that
that
don't
really
work
so
I'm,
okay
with
the
plug-in
management
in
the
first
two
days.
C
C
B
Like
don't
have
to
watch
I
think
I
honestly
think
it
won't
be
the
end
of
the
world
if
we
have
it
as
that
and
yes
develop
it
only
export
I'm,
not
crazy
conference
period
and
and
and
it
has
added
dysfunction
well
as
soon
as
we
have
it,
got
big
attraction
and
then,
as
documented
on
Peter
as
the
plugin
is
Skype,
you
should
really
sitting
his
opinions.
I.
B
C
I'm,
pretty
sure
that
we
will
discover
some
other
bugs
in
other
places.
So
we
know
this
one
might
be
broken
at
some
point
and
we
probably
will
discover
there
is
some
other
corner
cases
and
in
other
places,
on
this
plugin.
So
it's
a
fact
that
really
is
one
dot.
O
doesn't
mean
it's
just
perfect
and
we
won't
discover
any
issue.
C
Yes,
Pacific
one
is
a
bit
confusing
because
once
a
cloud
plug-in
has
created,
notes
to
absorb
load,
those
nodes
are
registered
on
Jenkins
and
we
can't
distinguish
with
standard
notes.
So
we
will
try
to
export
them
as
a
list
image
notes
and
indicate
of
the
specific
easy
to
plug
in.
There
is
some
blocker
for
it,
but
we
we
would
have
to
exclude
them
and
I
don't
know
yet
how
we
can
do.
Okay,.
B
B
B
Okay,
I
understand
someone
any
of
you
as
strong
opinion
about
like
yeah,
that
we
should
do
something
else,
but
I
just
I'm
just
trying
to
be
reasonable,
like
we
want
to
make
it
perfect.
First,
let's
let's
as
long
as
it
was
mentioned,
it's
stable
enough
I
might
try
to,
and
there
is
another
safety
expert
and
yeah,
so
it
generates
llamo.
There
is
just
an
error.
Yeah.
C
B
C
B
B
B
A
B
A
A
B
A
B
B
B
A
A
B
That's
why
I
wanted
to
do
it
here
and
we're
traveling
like
around
here
mm-hmm
I
mean
I.
I
am
not
safe
in
countries
it's
everywhere,
I'm
just
think
I'm
gonna
be
able
to
reduce
it
in
this
week.
If
you
have
a
have
issues
solved,
I
can
probably
answer
mail
every
now
and
then
that's,
but
that's
it
and
I
think
we
really
wanted
to
have
it
before
drinking
rolls.
A
C
B
Thanks
we
were
having
this
meeting
every
second
week
and
we
shifted
because
last
week
almost
no
one
was
available.
So
I
suggest
let's
have
another
meeting
two
weeks
after
that's
that
one.
So
it
will
be
like
twelve
of
September
unless,
unless
there
is
an
urgent
issue
to
have
a
meeting
earlier
than
let's
just
get
her
and
see.
A
A
A
A
B
A
B
B
Nice,
yes,
we
we
are
considering
different
formats.
So
as
soon
as
we
have
some
more
clarified,
ID
I
will
I
will
contact.
You,
ok
and
the
meetup
will
be
so
so
at
this
meter
before
they
are
drinking
the
scouts
and
well,
we
don't
want
to
repeat
the
same.
Material
will
have
at
the
conference
the
day
after
and
it
will
be
open
for
anyone.
So
so.