Hi Hans, Agreed, the core jars will probably be a great start. Thanks for starting the discussion.
Regards, Bart On Tue, Aug 9, 2022 at 10:57 AM Matt Casters <[email protected]> wrote: > Absolutely, let's stick to the core modules and then pick up additional > requests via JIRA if there are any. > > On Tue, Aug 9, 2022 at 10:49 AM Sergio Ramazzina <[email protected]> > wrote: > > > Hi Hans, > > > > I think that publishing the "core" artifacts is more than enough. In my > > opinion, I don't foresee any need to have also the plugins artifacts > > published > > > > S > > > > > > On 2022/08/08 14:02:04 Hans Van Akelyen wrote: > > > Hello Hoppers, > > > > > > I would like to start a small thread to hear about your opinions on > > pushing > > > our artifacts to maven central... > > > > > > Currently we are releasing source code/client and docker images. As > there > > > are more people that are starting to develop against our codebase it > > might > > > also be useful to give them artifacts on maven central to use in their > > POM > > > (now they have to use snapshots or locally build our jars). > > > > > > The main thing I am struggling with is which artifacts should we > include > > in > > > this release? > > > Should we only publish our "core" components (core/engine/UI/RAP/RCP) > or > > > should we include all our plugins? > > > > > > I think we can all agree that the artifacts we make in our assembly > phase > > > should not be pushed (unless someone disagrees?) > > > > > > Would love to get your feedback to decide if we should start preparing > > this > > > for our next release. > > > > > > Cheers, > > > Hans > > > > > > > > -- > Neo4j Chief Solutions Architect > *✉ *[email protected] >
