Hi Dimitry, I personally setup an Apache Archiva (can be done with nexus or others) that cache maven central and others repository(need configuration).
Other idea You build your application using RELEASE112, all the bits needed will go to your local repo. Once stable you can edit settings.xml and put <offline>true</offline> so maven will not try to go to internet. Only when you add a dependency you need a connection to download a missing one and put false to offline. It's possible to change the way we detect NetBeans artefacts but that needs coding with a new algorithm that IMHO will be insecure (org.netbeans.clusters:platform are known that us, my.company.clusters:platform may be a dangerous software that is build with artefatcs to mimic NetBeans) Regards Eric -----Message d'origine----- De : Eric Bresie <[email protected]> Envoyé : mardi 19 novembre 2019 20:08 À : [email protected] Objet : Re: Re: Clarify how to use locally built platform with maven Don’t suppose any of this would help... https://maven.apache.org/guides/introduction/introduction-to-repositories.html Eric Bresie [email protected] > On November 19, 2019 at 5:30:39 AM CST, Dmitry Avtonomov > <[email protected]> wrote: > Hi Eric, > Nothing to be sorry about, but I didn't quite understand your point. > It does feel like you know much about the topic though. > So imagine there's me, wanting to develop a NBP app with maven. How do > I go about it without a reliable internet connection? Why is the scan > only done on Central and local is skipped? What if Central doesn't exist > anymore. > It's the same situation like it is now with the old Oracle > infrastructure, is it?. I have basically experienced that myself. I'm > still scrambling to revive the development of my old app now. And I'm > still hoping that npb can be used instead of going Electron with a > whole shitload of headache to make this happen. > > On Tue, Nov 19, 2019 at 2:23 AM Eric Barboni <[email protected]> wrote: > > > Hi, > > Sorry to insist but the wizard will not find your version of NetBeans. > > Because the scan is done on central only, not in the local repository. > > The reference version are taken from the following artefatct > > org.netbeans.cluster:platform. It doesn't scan the former > > bits.netbeans repo too. > > > > A user that build his own NetBeans mavenized is not supposed to use > > groups like org.netbeans. or org.apache.netbeans because > > synchronization with central is limited to Apache NetBeans. That’s > > why wizard not have to scan locally because your group should differ. > > > > However the nbm-plugin has some hardcoded detection that make it > > hard to use (util a fix) outside org.netbeans so keep org.netbeans > > group for your own release. > > > > Best Regards > > Eric > > > > > > -----Message d'origine----- > > De : Tim Boudreau <[email protected]> Envoyé : mardi 19 novembre > > 2019 03:02 À : [email protected] Objet : Re: Clarify how to > > use locally built platform with maven > > > > Regardless, all you have to do is set it in the parent pom (ideally > > with a good <dependencyManagement> section with everything you're > > going to use), and then if the IDE adds <version> to anything, > > delete it (really, I think the dependency adding feature should > > detect if the library is already referenced from the parent's > > <dependencyManagement> section - but Maven can get really weird > > about dependencies [add a library with a <scope>provided</scope> > > library you already depend on, and it can make the library disappear > > from your runtime classpath), so I can imagine that might break things once > > in a while). > > > > -Tim > > > > On Mon, Nov 18, 2019 at 8:54 PM Dmitry Avtonomov < > > [email protected]> wrote: > > > > > Thanks for the suggestion John, I tried both buttons - nothing > > > worked for me. I also tried building the complete NBP: > > > > > > *ant -Dcluster.config=full build-nozip build-nbms > > > build-source-zips > > > build-javadoc* > > > > > > Tried building just the platform: > > > > > > *ant -Dcluster.config=platform build-nozip build-nbms > > > build-source-zips > > > build-javadoc* > > > > > > None worked. > > > And I do see the built artifacts in ~/.m2/repository. They are > > > right there next to RELEASE110, RELEASE111 etc downloaded by maven > > > when I tried building a test app after first installing netbeans. > > > > > > The only difference between the downloaded artifacts (like > > > RELEASE112) compared to my built ones is that the downloaded ones' > > > pom files had the > > > *<parent>* entry: > > > > > > *<parent> <groupId>org.apache.netbeans</* *groupId> > > > <artifactId>netbeans-parent</* > > > > > > *artifactId> <version>2</version></parent>* > > > > > > That parent pom doesn't seem to add anything build-related, it's > > > mostly license notices etc. But in the end I added parentGAV > > > configuration entry to nb-repository-plugin like this: > > > > > > > > > > > > > > > > > > > > > *<plugin> <groupId>org.apache.netbeans.utilities</groupId> > > > <artifactId>nb-repository-plugin</artifactId> > > > <version>1.4</version> <configuration> > > > <parentGAV>org.apache.netbeans:netbeans-parent:2</parentGAV> ....* > > > > > > Now the NetBeans wizard (New Project -> Java with Maven -> > > > NetBeans > > > Application) still does not see my artifacts. But if I still > > > create an app with one of the RELEASExxx versions it does see and > > > change RELEASExxx in the parent project pom to my version, it seems to > > > work. > > > At least I don't get build errors as before. I frankly don't know > > > what might have changed except for me adding the praentGAV, but it > > > does seem to work. In the pom.xml of *...-parent* project created > > > by the wizard set netbeans.version to RELEASE1236 (which is locally > > > built): > > > > > > > > > > > > *<properties> <netbeans.version>RELEASE1236</netbeans.version> > > > <brandingToken>mavenproject4</brandingToken> </properties>* > > > > > > This is a new computer with a fresh install of everything, > > > including the OS, so hard to tell. > > > I also didn't have any luck building+running with Java 11 (tried > > > zulu and > > > adoptopenjdk) so switched everything back to 8. > > > > > > > > > > > > > > > On Sun, Nov 17, 2019 at 10:43 AM John Neffenger <[email protected]> > > wrote: > > > > > > > On 11/17/19 2:06 AM, Dmitry Avtonomov wrote: > > > > > I did do that - there's a button to re-index maven repos afair. > > > > > > > > If that's the button in the Options under Java > Maven, I think > > > > that just pulls down the latest list from Maven Central again. > > > > > > > > Instead, open the Services Window (Ctrl-5), expand Maven > > > > Repositories, right-click the entry for Local, and select Update > > > > Index to re-index the local repository and save it in the > > > > NetBeans > > cache. > > > > > > > > That's how I got NetBeans to recognize the artifacts that I had > > > > copied into the local Maven cache when working around NETBEANS-1396. > > > > > > > > John > > > > > > > > ---------------------------------------------------------------- > > > > ---- > > > > - 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+lis > > > > ts > > > > > > > > > > > > > > > > > > > > > > > > > -- > > http://timboudreau.com > > > > > > -------------------------------------------------------------------- > > - 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
