On Mon, Feb 1, 2021 at 5:11 AM Neil C Smith <[email protected]> wrote:
> On Mon, 1 Feb 2021 at 10:27, Lars Bruun-Hansen <[email protected]> > wrote: > > Yep. I was considering that the right place for such internal > > artifacts might be ASF's Maven Repo. The problem I see with that one > > is that it is meant for _released_ artifacts meaning official ASF > > releases. They need to go through the voting process. This is not the > > case for these particular artifacts, they are in effect interim, and I > > don't think the community need more artifacts that we need to vote > > on?. > > Firstly, let's separate out sources and binary artefacts here - > sources *require* votes, although we do generally vote on binary > artefacts too. > > IMO, if a pre-built binary is being consumed by an end-user building > our sources or a platform developer building their project, then we > should be treating it as a released artefact, and it might be a lot > less complicated if we did. > > I would note that the Windows launchers are built as part of the > release process on Jenkins. There may be pros and cons to that in > terms of being in sync with people building locally? Having all the > native binaries released officially via ASF Maven repos (or dist.a.o) > might actually be better, and people can still check out their sources > and build locally if they want. > > Taking a step back (and expanding a little), I'm trying to understand the use cases, scope and usage of the artifacts Assume there are: (1) netbeans sources code for building (a) IDE/Platform (b) Installers, plugins, etc. (c) Netbeans Platform Applications (i.e. apps built on top of Netbeans Platforms) (2) For build of the above, there are dependencies such as (a) internal dependencies - [artifacts built during normal build; i.e. dependency project/clusters/modules produced during build time of NBs], (b) external dependencies - Artifacts pull for use during normal builds https://netbeans.osuosl.org/binaries/ . - Not fully sure what the difference between b and c are here. - Assume b artifacts are dependencies which may not be available directly due to for license distribution constraints or artifacts not yet published or not still available on official channels like at c. - Or maybe some of this is an ASF constrain on what can and cannot be used during build and delivery] (c) "Official repository - Artifacts pulled from official published artifacts, possibly publish by other projects, for use during build and/or runtime - i.e. ASF Maven, Maven Central, etc.) (d) Assume during build testing there may also be further "test dependencies" [i.e. JUnit, etc.] which also may fall into a variation of the above b or c (3) For runtime there are (a) Installers for a given application (b) Applications themselves (i.e Netbeans IDE or Netbeans Platform) (c) Each of which may have runtime dependencies or can have plugins available - [published to Netbeans plugin site; or maybe alternative sites] I guess some of this also is dependant on the mechanism used to pull these - ant build [not sure how dependencies are pulled here], - maven build pulling from maven applicable repositories, - pulled via some get / download mechanism, or - a "plugin pull/install" mechanisms. - Each of these assume would depend on different publishers sites Assume the Github packages would be usable during some parts of this (i.e. as part of 2 b and c as alternatives) but I'm guessing here Eric Bresie [email protected]
