On Fri, 17 Jul 2020 at 17:05, Dennis Lundberg wrote:
> Den fre 17 juli 2020 kl 08:55 skrev Olivier Lamy :
>
> > On Fri, 17 Jul 2020 at 16:53, Dennis Lundberg
> > wrote:
> >
> > > Hi,
> > >
> > > Given that I've been gone for some time from this list things might
> have
> > > changed. If that's t
Den fre 17 juli 2020 kl 08:55 skrev Olivier Lamy :
> On Fri, 17 Jul 2020 at 16:53, Dennis Lundberg
> wrote:
>
> > Hi,
> >
> > Given that I've been gone for some time from this list things might have
> > changed. If that's the case I'm sure someone will correct me :)
> >
> > But it used to be the
On Fri, 17 Jul 2020 at 16:53, Dennis Lundberg
wrote:
> Hi,
>
> Given that I've been gone for some time from this list things might have
> changed. If that's the case I'm sure someone will correct me :)
>
> But it used to be the way to do things when you have a chain of related
> components, which
Hi,
Given that I've been gone for some time from this list things might have
changed. If that's the case I'm sure someone will correct me :)
But it used to be the way to do things when you have a chain of related
components, which is quite common in Maven. If we take
maven-resouces-plugin, which
yup it is and ease testing.
as long as you deploy manually the snapshot (but I remember to have
changed our jenkinsfile to deploy master automatically)
On Fri, 17 Jul 2020 at 01:04, Elliotte Rusty Harold
wrote:
> I happened to notice today that the maven-resources-plugin at HEAD in
> the repo
I happened to notice today that the maven-resources-plugin at HEAD in
the repo (not the released version) depends on the latest SNAPSHOT of
maven-filtering:
https://github.com/apache/maven-resources-plugin/blob/master/pom.xml
Is this generally OK? That is can we commit code to a repo that
depends
