Hi Ricardo, If our focus is to provide scaffolding for new projects having standalone projects is the way to go. Having parent pom with dependencies will create a coupling between our examples and end user deployment. I can see some problems with that philosophy:
1. We cannot change our deps as we will create a dep between the projects and examples and end user 2. It will burden our examples as scaffolding as it cannot be changed among versions because of the dependency created. A middle ground wont be bom but some sort of starters or group dependencies pom. Other projects do not necessarily follow what we are trying to do here. They might have. Different philosophy El lun, 12 ago 2024, 19:29, ricardo zanini fernandes < [email protected]> escribió: > Every proposal to make it easier for users would have my +1. However, > removing parent/BOM is not one of them. Having a template like Francisco's > mentioned could be a good idea, too, or even importing the BOM like what > Nicolas mentioned. > > FWIW, SpringBoot uses parent: > > https://github.com/spring-guides/gs-spring-boot/blob/main/initial/pom.xml#L5-L10 > > On Fri, Aug 9, 2024 at 10:00 AM Martin Weiler <[email protected]> > wrote: > > > +1 to making it easier for users to consume and adapt our examples > > > > ________________________________________ > > From: Tibor Zimányi <[email protected]> > > Sent: Friday, August 9, 2024 5:54 AM > > To: [email protected] > > Subject: [EXTERNAL] Re: [PROPOSAL] Making individual kogito-examples > > standalone > > > > I will try to get an example of a standalone one. > > > > T. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
