Maven best practices for handling component releases?

[David Hoffer <dh...@gmail.com>]

We have about a dozen applications that use various in-house developed
components which are in a separate component repo.  The component repo has
all of the components (currently about a dozen) and is configured so we can
release each one independently from the others.  (Some components change
often, some rarely.)

If we make changes to a component it stays in SNAPSHOT until the next
application release cycle.  We release all components that changed when we
release the dozen applications.

Some of the components have dependencies on other components and the dozen
apps have various dependencies on the components.

So naturally our release process is a rollup of releases starting at the
bottom component and then updating all components/applications that have a
dependency to the just released version, this keeps going until the top
level apps are released.

So my question is are there tools/practices that can help automate this
release/roll-up process?

-Dave

Re: Maven best practices for handling component releases?

[Lasse Lindqvist <la...@gmail.com>]

Hi. One option to help with this is Dependabot or similar. It can also work
with internal Maven repositories and create PRs automatically when
dependencies have updates available.

to 21. lokak. 2021 klo 17.42 David Hoffer (dhoffer6@gmail.com) kirjoitti:

> We have about a dozen applications that use various in-house developed
> components which are in a separate component repo.  The component repo has
> all of the components (currently about a dozen) and is configured so we can
> release each one independently from the others.  (Some components change
> often, some rarely.)
>
> If we make changes to a component it stays in SNAPSHOT until the next
> application release cycle.  We release all components that changed when we
> release the dozen applications.
>
> Some of the components have dependencies on other components and the dozen
> apps have various dependencies on the components.
>
> So naturally our release process is a rollup of releases starting at the
> bottom component and then updating all components/applications that have a
> dependency to the just released version, this keeps going until the top
> level apps are released.
>
> So my question is are there tools/practices that can help automate this
> release/roll-up process?
>
> -Dave
>