Ahhh I see In fact the documentation is outdated https://bits.netbeans.org/mavenutilities/nb-repository-plugin/repository.html . I will try to have it publish on the netbeans website using git maven way so we will not have to think about it.
** How to populate, Ant phase You basically do that to prepare enough material from Apache NetBeans: ant build-nbms ant build-source-zips ant build-javadoc ** How to populate, Maven phase (Maven 3.3.9 required, not tested with modern Maven yet) and then you have maven part this is not nominal due to the fact I use SNAPSHOT version at the moment (to be able to release snapshot on apache infra) *- get the netbeans repository plugin localy (if 1.5 released this step is obsolete) mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.1:get -Dartifact=org.apache.netbeans.utilities:nb-repository-plugin:1.5-SNAPSHOT -DremoteRepositories=apache.snapshots.https::::https://repository.apache.org/snapshots *-download the index to make dependencies better (simplified but it's better to use maybe a separate local maven repo ) mvn org.apache.netbeans.utilities:nb-repository-plugin:1.5-SNAPSHOT:download -DnexusIndexDirectory=pathto/repoindex //(target of what is downloaded) -DrepositoryUrl=https://repo.maven.apache.org/maven2 //(repo to read) *-populate a repository (no need to have parent in this case as user will not be able to populate apache repos) *-populating is also variable, because you can only use a subset of the parameter mvn org.apache.netbeans.utilities:nb-repository-plugin:1.5-SNAPSHOT:populate -DnexusIndexDirectory=pathto/repodindex //index to read from -DnetbeansNbmDirectory=netbeansbasebuildpath/nbms //nbm -DnetbeansInstallDirectory= netbeansbasebuildpath /netbeans //jar and folder of install netbeans generated during ant -DnetbeansSourcesDirectory= netbeansbasebuildpath/build/source-zips // sources packaged -DnebeansJavadocDirectory= netbeansbasebuildpath /build/javadoc // javadoc -DforcedVersion=RELEASEVERSION11.11mine // a version you have to choose -DskipInstall=true // do not install localy -DdeployUrl=file://apath/dist/mavenrepository" // prepare a repository where all artefacts are. This is long cli but it works. ... ... And I am upset with myself, I guess since RELEASE90 we have no Javadoc maven artefacts, because netbeans get a t in this name Regards Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : mercredi 24 juillet 2019 12:34 À : dev <[email protected]> Objet : Re: Convenience binary policy? On Wed, 24 Jul 2019 at 10:41, Eric Barboni <[email protected]> wrote: > Disclamer :D > I'm not computer so I cannot be in stored in a data center with an air temp > at 22°C. Despite I melt, I hope to be understandable. Tell me about it! :-) Thanks for the information. It's useful to understand further, and I've also been looking through the Jenkins configuration of it a bit already. It's definitely a good step forward for 11.2. However, it's also not quite what I had in mind with my question (sorry!). At the moment, an end user can download the main release source and call - ant build-source-config -Dcluster.config=platform and they will get a source bundle like the platform sources we distribute. In other words, even though it's source, the platform source zip is a build artefact of the main source bundle and doesn't get voted on separately. The thing I'm wondering is about documenting how an *end user* can take our released sources and generate the same Maven artefacts locally. This to me is part of showing that they are purely artefacts of the sources we voted on. > It seems installer cannot be part of that. Probably not. Although Reema better to answer that. They are one reason I think we might not always have all convenience binaries ready at release vote time, or even want to, and should really keep the two things separate. Hence original question in this thread about how we oversee binaries in general. As we don't really seem to have come to a conclusion on that, for 11.1 I've tagged Reema and yourself on JIRA against installer and Maven tasks. From my perspective, upload at will when you're satisfied they're ready and meet PMC requirements. Once they're up we can close the parent JIRA task for NB 11.1. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
