►
From YouTube: Online Developer Meetup: Plugin Parent POM 4.0
Description
Maven is widely used for Jenkins plugin development, more than 90% of plugins use it. In order to simplify plugin development, the Jenkins project offers a standard Parent POM which defines the recommended build, verification and release flow. Such parent POM helps us to ensure quality of the Jenkins plugins. In April 2020 we released a new major release of the parent POM which includes a number of important and sometimes incompatible changes: Jenkins core Bill of materials, full migration to SpotBugs, etc.
In this presentation James Nord from CloudBees will talk about the changes introduced in Plugin POM 4.0. What do plugin developers and users get by upgrading? How to upgrade? What obstacles to expect, and how to resolve them?
Links:
* Slides: https://drive.google.com/file/d/1uQaEA_EYk3g1D_QoJXK_0VujQtnhD4zq/view?usp=sharing
* Plugin Parent POM repository: https://github.com/jenkinsci/plugin-pom
* 4.0 changelog: https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.0
A
A
Okay,
this
is
my
screen
yep,
so
quick,
introduction
to
the
Jenkins
online
Meetup.
We
are
doing
regular
sessions,
forging
users
developers
and
the
main
objective
is
to
share
any
kind
of
experiences
for
developer.
Meetups
are
what
is
about
contributors
for
contributors,
so
basically
we
do
a
really
relaxed
discussion.
The
main
focus
is
to
do
Chantal
and
wipe
them
as,
and
everybody
is
welcome,
to
participate
to
ask
questions.
We
are
ready
to
unmute
you
if
you
want
to
ask
questions.
Actually
it's
our
first
developer
meetup,
which
we
do
in
the
zoom
webinar.
A
A
So,
as
I
said,
everybody
is
welcome
to
participate
and
if
you
are
just
starting
to
join
case
or
if
you
interested
so
we
have
a
good
page
on
managing
you
say
your
website,
which
do
straps
various
ways
to
contribute.
So
if
you
are
interested
to
do
any
kind
of
contribution
like
submit
some
code
or
maybe
participate
in
design
with
speed
in
the
documentation,
please
refer
to
this
page
and
there
is
also
a
good
opportunity
to
contribute
next
week
because
we
are
starting.
You
are
you
a
hug
hug
fest.
A
It
will
be
a
week-long
event
where
everybody
just
works
on
user
interface,
the
communication
or
shares
experiences
about
Jenkins
and
which
is
a
bit
the
end
of
this
event.
You
can
get
special
Schwab
and
prizes,
and
so,
if
you're
interested,
there
is
online
page
for
that
on
the
jenkees
our
website,
we
are
still
working
on
a
final
list
of
project
ideas,
but
there
is
a
number
for
Guterres
if
you
have
plug-in
maintainer
you're
also
welcome
to
propose
stories
related
to
your
plugins.
A
A
Okay,
and
we
can
talk
a
bit
more
about
it
later
and
yeah
I'll
just
finish
a
slice.
So
if
you
can
just
present
anything
related
to
plug-in
development
or
development
in
general,
it
can
be
best
practices
like
how
to
do
static
code
analysis
or
how
to
properly
deliver
real
code
with
Java
or
with
Jenkins.
Please
let
us
know
we
are
looking
for
speakers
as
for
anything
else,
for
this
particular
meet
up
again.
It's
the
developers
meetup,
so
we
will
be
adding
everyone
finalists
or
finding
host
permissions
so
that
you
can
ask
questions
James.
B
A
Okay,
thank
you
and
beer
for
flying.
We
have
Jenkins
developer
demand
increased.
We
have
a
number
of
charts
where
you
can
ask
also
we'll
be
sending
our
feedback
form.
I
just
talked
some
additional
details,
so
everyone
is
welcome
to
attend
and
I
guess.
This
is
from
me.
So
please
welcome
James
Dorf
presentation
itself
are.
A
B
So
a
little
bit
about
me.
I
am
a
principal
software
engineer
at
cloudy's,
working
on
a
commercial
product
built
on
top
of
Jenkins
working,
a
team
that
is
responsible
for
over
50
plugins.
So
every
time
we
had
to
change
something,
and
if
you
look
after
one
or
two
plugins
in
open-source,
you
can
kind
of
scale
that
up
to
50
and
we
we
probably
hit
all
of
the
issues
much
more
frequently.
B
So
a
lot
of
that
was
the
driving
force
for
trying
to
address
all
the
problems
so
mentioned
some
problems,
but
kind
of
let's
just
explain
what
they
were.
So
we
actually
tried
to
do
what
we
did.
I
think
the
biggest
pain
that
we
all
face
is
every
time
we
change
the
Jenkins
version.
You
will
find
five
million
dependency
errors
caused
by
something
requiring
a
lower
version
or
a
higher
version
than
what
is
actually
included.
So
something
wants
to
use.
B
Commons
codec
1.9
something
else
once
use
1.12
you
end
up
using
the
1.9
and
then
that
can
cause
issues
just
when
running
your
unit
tests
with
things
not
working
correctly
or
kind
of
at
runtime.
The
worst
case
is
you,
you
burned
all
the
library
and
that
conflicts
with
something
else
in
a
different
plugin.
That's
expecting
something
to
come
from
core
has
an
optional
dependency
on
your
plug-in
and
then
doesn't
we
have
deprecated
tooling
in
the
plug-in
pom,
so
the
G
maven
plug-in
reached
end-of-life
and
wasn't
actively
developed.
B
If
you
were
new
to
Jenkins
plug-in
development
and
you
knew
maven
but
not
Jenkins,
plug-in
we'd,
quite
often
confuse
you,
we'd
use
a
flag
that
was
set
in
maven.
For
example,
skip
tests
is
commonly
used
to
skip
running
unit
tests
in
the
maven
surefire
plug-in,
but
if
you
did
that
in
a
Jenkins
plug-in,
it
also
wouldn't
run
your
fine
box
analysis
and
it
also
wouldn't
create
any
Javadoc.
B
So
say
you
wanted
to
create
a
bundle
quickly
to
give
to
someone
which
had
java,
dork
and
everything
else
running
MVM
package
d
skip
tests.
You
would
expect
that
to
happen,
but
it
didn't
another
way
that
we
would
confuse.
You
is
if
you
wanted
to
run
multiple
tests
in
parallel.
You
would
specify
that
with
concurrency,
but
surefire
already
has
a
way
of
doing
that,
and
it's
four
count.
B
If
you
didn't
know
maven,
there
was
a
little
bit
of
a
barrier
of
entry,
because
your
Google
searches
would
tell
you
how
to
do
something
in
maven
and
then,
when
you
use
the
plug-in
pomme,
it
would
actually
behave
slightly
different
and
kind
of
I.
Think
there's
something
that
was
a
little
bit.
It
was
a
great
intention,
but
unfortunately
it
had
a
lot
of
bad
consequences.
Was
the
plug-in
purim
allowed
you
to
do
bad
practices?
So
if
you
wrote
a
flaky
test
or
worse
still,
flaky
production
code,
the
the
unit
tests
would
actually
run
five
times.
B
So
if
it
failed
first
time
it
would
run
it
again
and
again
and
again
up
to
five
times,
and
it
would
only
fail
the
build
if
the
unit
has
failed
five
times
in
a
row.
So
this
had
a
couple
of
things.
It
allows
obviously
flaky
tests
and
flaky
production
code
to
come
in.
Nobody
really
looks
at
the
output
in
the
console
a
lot.
So
the
fact
that
you'd
introduce
some
flaky
tests
or
flaky
production
code
would
go
missed
and
it
allowed
race
conditions
to
be
accepted
as
the
norm
because
they
just
weren't
they
weren't
spotted.
B
And
last
but
least,
not
least,
there
was
some
unused
and
untested
complex
complexity
in
the
pond.
So
since
Jenkins
2.5
for
354,
it
is
required
to
Java
8
to
run
so
there
is
no
need
to
really
build
any
plugin
with
Java
7.
You
can
build
them
all
with
Java
right
if
you're
targeting
anything,
not
ancient,
and
if
you
are
targeting
something
agents,
then
you
don't
really
need
to
update
the
the
plug-in
parent,
the
jacott.
B
If
anyone
are
aware
of
Jake
it,
it
is
a
Java
implementation
of
git
provided
by
eclipse
and
it
used
or
had
a
profile
for
using
Jake
it
as
an
SEM,
as
opposed
to
using
the
native
get
tool
when
performing
releases
and
I.
Don't
think
I've
ever
come
across
any
need
of
any
plug-in
doing
that.
So
almost
everyone
has
got
get
installed,
I'd
be
surprised
if
it
even
still
worked.
B
Whatever
we've
just
released,
that
Friday
test
and
more
often
than
not,
we
would
find
we
were
being
hit
by
not
actual
production,
kodesh
issues,
but
the
the
library
conflicts
and
issues
so,
rather
than
actually
finding
issues
in
the
latest,
LTS
or
incompatibilities
sorry
incompatibilities
in
the
weeklies
with
our
plugins.
We
just
ended
up
finding
or
there's
another
library,
conflict,
there's
another
library
conflict
and
there
was
more
false
positives
than
there
were
real
positives.
B
B
So
a
bill
of
materials
allows
you
to
with
maven,
define
a
set
of
artifacts
and
their
versions,
and
you
can
define
that
in
a
project.
And
then
you
can
consume
that
in
all
other
projects.
So
it's
quite
common
to
do
with
spring.
If
you're
used
to
using
a
building
a
spring
boot
project,
you
can
just
import
the
spring
boot
bill
of
materials
and
then
all
of
the
spring
libraries
and
their
dependencies
will
be
set
to
the
correct
version
for
the
version
of
spring
boot
that
you
were
targeting.
B
So
the
bomb
was
first
introduced
in
Jenkins,
2.19
5
and
because
we
actually
want
people
to
be
able
to
use
the
plugin
pom
without
having
to
go
to
at
the
time
the
most
recent
and
weekly,
we
still
needed
people
to
be
able
to
target
older
LTS
releases.
We
especially
published
old
versions
on
all
the
LTS
lines
going
back
to
2.16
4.1.
B
We
still
have
a
few
core
libraries
missing,
so
Commons
codec
was
a
notable
one.
That's
missed
and
there's
a
peer
to
add
those
and
all
our
outstanding
libraries
into
the
latest
weekly
and
it's
not
just
plug-in
development
where
the
bomb
comes
in
handy,
so
the
jenkins
file,
runner
or
the
jar.
The
jenkins
were
packager
also
benefit
from
just
having
a
core
bomb.
B
So
the
Feinberg's,
given
it
was
dead
that
was
switched
over
to
spot
bugs
any
property
in
the
palm
that
was
using
Feinberg's
was
changed,
the
spot
bugs
and
the
exclusion
filter
was
renamed
as
well.
Excuse
me,
and
one
thing
to
note
here,
is
if
you're
targeting
a
recent
jenkins
core,
so
probably
one
that's
gone
in
in
I.
Think
the
last
four
weeks,
all
the
use
of
jsr,
three
or
five
annotations
have
been
removed.
So
it's
now
almost
in
its
entirety,
only
using
the
spot
bugs
annotations.
B
B
The
standard
maven
properties
have
now
been
switched
over
to
using.
So
there
is
no
more
concurrency
in
in
the
poem
it's
now
using
four
counts.
So
if
you
find
a
maven
property
documented
in
kind
of
a
maven
plug-in
or
anywhere
else
on
the
web
in
a
plugin
that
we
use,
setting
its
property
should
take
precedence
over
anything
else.
B
Skip
tests
now
only
skips
tests.
That
does
have
a
downside
and
one
of
the
downsides
for
having
that
is.
If
you
wanted
a
quick
build
and
people
did
you
skip
test
for
a
this
is
a
quick
build
because
I
don't
care
about
the
production
quality
of
it.
You
now
no
longer
have
that
by
just
using
skip
tests
so
because
of
that
we
introduced
a
new
profile.
So
if
you
actually
want
a
quick,
build,
I've
just
build
up
a
HPI,
so
I
can
run
it.
B
There's
a
profile,
quick
build,
so
NV
n
P,
quick,
build
that
will
give
you
a
build
or
obviously
package
at
the
end
of
that
that
will
kind
of
build
up
the
HPI
and
anything
else
that
would
produce
a
final
artifact
but
skipping
anything
that
does
not
affect
the
outcome
of
the
final
artifact.
So
the
enforcer
rules
will
be
skipped.
A
spot
bugs
will
be
skipped.
Unit
tests
won't
be
run.
If
you
use
the
maven
invoker
to
run
some
extra
tests,
they
will
be
skipped.
The
access,
modifier
checker
will
be
skipped.
B
So
now
we've
kind
of
gone
through
all
of
that,
it's
kind
of
like
okay.
What
do
you
need
to
do
so?
The
first
thing
you
need
to
do
is
obviously
use
it
so
update
your
parent
to
four
point.
Two
four
point
two
is:
is
the
latest
today,
so
it's
always
best
to
go
with
the
latest
rather
than
the
4.0.
A
couple
of
things
have
been
tweaked
and
fixed,
and
some
libraries
and
plugins
have
been
updated
as
well.
B
B
A
bit
more
manual
work
is
any
version
that
you've
specified
in
dependency
management
or
dependencies
that
is
now
coming
from
the
bomb
should
be
removed.
This
is,
is
legwork.
You
have
to
kind
of
go
into
the
bomb,
have
a
look
at
the
dependencies:
it's
specifying
there
for
all
the
artifacts
and
see
if
you've
declared
them.
If
you
have
safely
delete
it,
if
you
have
declared
them
in
the
dependency
section,
as
opposed
to
dependency
management,
section
and
they're,
using
the
clips,
eclipse
will
tell
you
you're
overriding
and
manage
dependency,
so
you
can
just
remove
it.
C
B
I
would
if
I,
can
you
see
the
gear
page
now
sure
can
right
so
inside.
Here
we
have
the
let
you
made
this
bigger,
so
people
can
actually
read
it
inside.
Here
we
have
the
dependency
management
section.
So
anything
that's
in
here
for
the
obviously
for
the
Jenkins
version
you're
targeting.
So
this
is
for
2.2
to
2.1
anything
in
the
dependency
management
section
so
spot
bugs
annotations,
jaesik,
annotations
and
commons
io
commons
line
anything
reported
here,
even
SSL
f4j.
B
If
it's
in
this
section,
you
can
remove
it
from
your
pond,
you
can
remove
the
version
from
your
pond.
So
if
it's
in
dependency,
if
it's
in
dependency
management,
you
can
remove
it
entirely.
If
it's
in
dependency,
if
it's
in
the
dependency
section,
you
can
remove
the
version,
so
you
would
still
end
up
with
Skoda
Commons
codec,
but
you
wouldn't
have
a
version
specified.
B
So
another
thing
that
has
changed
in
plugin,
poor,
the
plug-in
pom
4.2
was
htmlunit,
was
updated.
That
was
needed
to
fix
the
Jenkins
test
harness
and,
unfortunately,
htmlunit
is
not
backwards
compatible.
So
if
you're
using
web
client
based
tests,
you
will
likely
need
to
kind
of
fix
up
the
API
breakage
in
your
tasks.
A
B
So
any
properties
or
files
that
you
were
using
so
if
you
had
defined
concurrency,
so
you
run
by
default
with
two
forks,
as
opposed
to
one
you'll
need
to
change
that
to
fork
count
anyway.
You've
used
the
Feinberg's
properties.
You
will
need
to
replace
those
with
spot
bugs
and
if
you've
got
a
custom
spot
bugs
exclude
filter
in
your
project
source,
you
will
need
to
move
that
to
source
spot
bugs,
as
opposed
to
source,
find
bugs
and
yeah.
A
B
You'll
print
now
probably
see
them
more
often
than
not,
because
as
soon
as
the
test
fails,
it
will
fail
the
build
if
you
want
to
run
it
locally,
just
run
stuff
locally
overnight,
and
if
it
passes
every
single
time
whilst
running
overnight,
then
it's
probably
good
enough
easy
way
to
do
that.
If
you're
running
on
a
Linux,
Oh,
unix-like
operating
system
and
using
bash
well,
maven
tests
do
done
and
that
will
just
loop
and
run
maven
tests
forever
and
ever
until
you
either
interrupt
it
or
a
unit
test
fails.
B
So
this
was
all
I
needed
to
do
to
update
the
kubernetes
credential
provide
a
plug-in
from
3.49
24.2
I
chose
2.1
90.1
as
the
Jenkins
baseline
I
wanted
to
target,
mainly
because
of
commercial
reasons,
and
cloudy's
supports
some
older
versions
than
the
older
LTS.
So
that's
the
most.
That's
the
oldest
version
that
cloudy's
supports
I
removed
an
override
for
not
rerunning
flaky
test,
because
I
don't
need
that
anymore,
because
it's
it
does
that
automatically,
because
I
had
updated
the
Jenkins
version.
B
B
B
So
what
else
should
I
look
out
for,
if
you're
changing
your
dependencies?
It's
always
good.
The
first
time
you
run
it
locally
is
to
actually
see
what
is
included
inside
your
HP
I.
So
inside
your
plugin
make
sure
that
there's
nothing
there
that
you're
not
expecting
so,
for
example,
when
it
bundles
something
you
will
get
a
warning
output
from
the
maven
HPI
plug-in
telling
you
that
it
is
bundling
something.
B
C
B
As
perfectly
okay
I'm,
most
likely
a
transitive
dependency,
so
that's
a
dependency
of
something
that
you
depend
on,
so
you
may
only
use
an
API
or
you
need
an
implementation.
So
there's
an
API
in
an
implementation
and
you
depend
on
the
API
and
the
default
implementation
and
then
the
default
implementation,
because
it's
speaking
to
some
web
service
will
rely
on,
say
an
apache
HTTP
client,
which
is
a
great
one
to
choose.
B
B
But
you
know
you
don't
want
20-25
versions
of
the
apache
httpclient
in
use
and
then,
if
someone
else
depends
on
your
plug-in
and
the
apache
httpclient
as
well,
they're
gonna
get
the
version
of
the
Apache
HTTP
find
from
your
plug-in,
which,
if
you
don't
update
it,
could
be
outdated
and
might
not
have
the
library
that
they
need
to
satisfy
their
use
case.
So
for
the
HTTP
client
use
case,
there
is
actually
a
HTTP
client
plug-in
that
provides
the
Apache
HTTP
client.
B
C
A
A
transitive
dependency
is
all
we
see
Benja
and
that's
why
Bills
of
materials
are
generally
useful
because
it
increases
your
chances
of
avoiding
binary
conflict.
But
if
you
start
suppressing
issues
and
excluding
collab
ranging
this
is
basically
suppressing
Pichet
your
risk
of
getting
into
something
yeah.
B
And
because
of
where
the
dependency
for
jenkins
core
comes
in,
even
if
say,
you're
using
commons
io,
that
should
come
from
jenkins,
as
opposed
to
from
your
plugin.
If
you
bundle
it
in
your
plugin,
it
won't
be
loaded
unless
you
start
using
kind
of
the
plug-in
loader
hacks
that
are
out
of
scope
for
this
session.
B
B
So
it
might
be
that
you
know
you
look
at
them
and
go.
Oh,
it's
Commons,
I,
oh
I,
know
that
should
come
from
Jenkins,
but
due
to
the
way
that
HPI
plugin
has
seen
it
it's
coming
from
a
closer
dependency
in
my
dependency
chain
than
from
whatever
is
requiring
it
in
jenkins
core.
It
would
choose
to
package
it
inside
your
plugin,
arguably
something
that's
suboptimal
in
the
HPI
plugin,
but
also
it's
a
little
bit
out
of
scope
and
requires
a
lot
more
engineering
effort.
B
A
A
B
B
B
B
B
B
A
B
Think
that's
kind
of
where
I'm
in
my
head,
this
is
coming
from,
so
anything
that
would
be
an
API
for
Jenkins
or
be
exposed
in
an
API
for
Jenkins
should
be
managed
in
the
Bill
of
Materials.
Things
that
are
just
things
that
Jenkins
need
to
be
able
to
run
should
be
outside
of
the
Bill
of
Materials
and
shouldn't
even
be
exposed
to
plugins.
B
B
There
is
quite
a
bit
of
there's
a
couple
of
big
jurors
around
it,
as
well
as
making
the
Jenkins
test
harness
used
more
realistic
cross
loading
which
would
be
needed
as
well.
If
we
started
having
dependencies
that
Jenkins
had,
but
we
didn't
want
you
to
consume
with
your
plugin
as
well
as
then
going
well.
You
built
this
plug-in
on
the
Jenkins
before
this
came
in.
So
actually
we
want
to
expose
all
of
these
team.
A
B
It's
probably
one
of
the
the
biggest
reasons
why
people
don't
update
their
Jenkins
plugins
to
the
latest
Jenkins
version
or
a
more
modern
Jenkins
version
when
they
start
developing
the
plug-in
or
when
they
make
a
change.
It's
because.
Well,
if
I
do
this
I
know
everything's
going
to
break
and
I'm
going
to
have
to
spend
10
15
20
minutes
going
through
and
fixing
the
enforcer
issues
and
I
just
want
to
write
code.
B
So
this
should
hopefully
mean
that
at
some
point
we'll
be
able
to
go
through
and
all
these
plugins
that
have
been
detached
from
core
that
keep
coming
back
in
because
you
have
a
plug.
You
depend
on
a
plug-in
that
depends
on
an
earlier
version
of
Jenkins
core,
but
you
don't
actually
need
the
detached
plug-in.
It
should
make
it
simpler
and
the
less
plugins
you
have
in
Jenkins
the
quicker
it
is
to
startup
the
less
memory
it
uses.
B
A
B
So
if
you're
looking
at
you,
you
want
to
use
a
version
of
the
common
use
cases,
workflow
plugins.
You
need
to
pretend
on
workflow,
CPS
and
tesco,
but
you
also
want
to
have
the
workflow
step
API,
because
you're
implementing
the
step
and
you're
targeting
Jenkins
2.1
90.
You
know
which
versions
of
all
of
the
workflow
plugins
should
you
be
depending
on,
and
so
that
is
where
the
Jenkins
plug-in
bill
of
materials
comes
in,
which
is
what
jank,
what
Oleg
is
showing
now.
B
A
So
here
you
can
see
that
there
is
dependable,
are
basically
dependable
example,
dependency
updates
and
suggests
them.
Well,
usually,
it
fails
because
there
is
a
lot
of
integration
testing
setup
here.
So
when
you
see
a
dependency
which
is
not
merged
most
likely,
there
is
some
things
to
be
cleaned
up
before
it
can
actually
can
go
into
the
Bill
of
Materials,
but
the
good
news
so
that
this
representative
does
it
for
you,
because
otherwise
here's
a
plug-in
maintainer
would
have
had
a
serious
chance
of
hitting
the
same
mission.
A
B
C
B
Slightly
different
versions,
so
the
version
when
you're
setting
the
version
for
the
Jenkins
core
that
you
target
will
be
a
full
kind
of
LTS
release
for
the
plugin
bomb.
It
is
targeting
a
line,
so
your
target
in
the
2.16
fall
line
or
the
2.1
ninety
line.
So
you
need
to
say
which
artifacts.
So
thanks
so
much
for
highlighting
that
you've
got
the
artifact
ID,
which
is,
if
you
were
targeting
the
2.16
for
line.
B
Not
currently
I
know,
if
you're
trying
to
do
anything
on
blue
ocean.
That
is
a
particular
pain,
because
you
need
to
use
the
exact
same
version
of
everything.
That's
blue
ocean
is
using
to
make
it
compatible
I'm,
not
aware
of
any
blue
ocean
extensions
apart
from
one
proprietary,
one
that
isn't
in
the
main
blue
ocean
tree.
B
I
know
that
early
Hafner
has
been
working
on
having
kind
of
a
more
modern
front-end
for
some
other
plugins
he's
using
and
he's
actually
shipping
libraries
or
the
JavaScript
libraries
in
plugins
and
then,
depending
on
those
plugins
I,
think
there
was
a
talk
recently
about
that.
Oh,
like
it's
not
correct.
There.
B
A
A
So
you
can
read
the
blog
post
and
get
all
the
information,
and
if
you
want
to
see
we
life,
actually
you
have
an
opportunity
for
that
because
next
week
again
we
have
this
ui/ux
hackathon
during
the
expect
and
we
organized
a
number
of
sessions
for
developers
and
for
users,
and
here
you
can
see
that
just
in
one
week
we
will
be
presenting
the
same
talk
with
you.
Online
hug,
fest
and
you're
welcome
to
join.
A
B
A
A
We've
won
two
more
sessions
and
if
you
would
like
to
join
and
share
your
experiences
about
Jenkins
so
to
provide
it
show
it
and
tell
about
particular
his
keys,
how
we
develop
plugins
or
how
you
develop
pipelines
for
what
it
was.
Please
let
us
know
and
we
will
be
able
to
first
such
event.
So
thanks
a
lot
to
James
for
this
presentation,
it
was
really
useful
and
we
will
be
posting
it
on
my
youtube
channel
soon,
so
hopefully
other
beginning
as
you'll
be
able
to
see
that
and
update
to
clicking
on
photos
either
soon.
Thank.