Re: [VOTE] PMC chair for Apache NetBeans
+1 On Fri, Mar 1, 2019 at 6:41 AM Mr_Krava wrote: > +1 > > On Saturday, 2 March 2019, 1:29:07 am AEDT, Glenn Holmer > wrote: > > This voting thread is to confirm Geertjan Wielenga as the first PMC > chair of NetBeans as we leave incubation and begin our journey as a > top-level Apache project. As an Oracle employee, Geertjan has been in a > unique position to help guide the project to independence and is the > best choice to complete that process. > > >
Re: What NetBeans is on front page
Christian: Nice concept. What about if the editor view was broken into 6 or 8 pieces and all converged to make the final image (your initial image smacks at the idea of fitting pieces together along with the verbiage)? Browsers are good at that kind of thing. I generally don't like things moving and bobbing on a web site but in line with my peculiarities https://www.lwjgl.org is one of the most impressive landing pages I've ever seen. Perhaps there is a js library that can accomplish something like that? On Wed, Feb 20, 2019 at 9:49 AM Christian Lenz wrote: > Hey all, > > would be great if we can have a live session together. I mean of course > not all the members are needed but some of them who wants to change the > layout of the page. Dave, for you and all others, please see > https://netbeans.puls-webagentur.de/ All Information about the IDE is > still there and present. What languages we have as a native support. A > screenshot of the light and the darkula laf, which frameworks and > technologies we support natively and what makes it customizable. I know > that it not fits in the page anymore but those Information is important for > our users of the NetBeans IDE to know WOW there is far more than only Java. > Maybe smth has to be changed but yeah. This is more or less complete. > > And to say it again, we need the info which IDE Version is the current one > and a easy download link to them and not via the slider. > > > Cheers > > Chris > > > > Von: David Schulz > Gesendet: Mittwoch, 20. Februar 2019 03:32 > An: Geertjan Wielenga; dev > Betreff: RE: What NetBeans is on front page > > Great ideas, we should collect them! > I plan to do a live design session at the upcoming weekend (no details > yet). > Feel free to send me all the input and ideas you have, or join our session > if possible đ > > All the best, > Dave > > > > From: Geertjan Wielenga > Sent: Mittwoch, 20. Februar 2019 06:56 > To: dev; David Schulz > Subject: Re: What NetBeans is on front page > > Agree completely, both with Antonio and Ondro. > > Re the redesign plans, see this: > https://twitter.com/Dave_UX/status/1096385375273013248 > > Gj > > On Tue, Feb 19, 2019 at 11:17 PM Ondro MihĂĄlyi > wrote: > Hi, just my 2 cents: Netbeans is first and foremost an IDE, which means you > can do all the development inside it, including coding, running, debugging, > testing, and even running a terminal. The current page doesn't explain > that, it only stresses that it's more than an editor. Nothing about running > and debugging apps which is the essential difference between IDEs and > editors. > > Ondro > > ut 19. 2. 2019 o 22:20 Antonio napĂsal(a): > > > Hi, > > > > Form: > > > > netbeans.apache.org needs some design love, I think. > > http://www.groovy-lang.org/ may be a good source of inspiration. I heard > > there were some design ideas floating around for the website, but we've > > been hearing that since 2017-2018. I can give the design a go during the > > next week (but I'm not very good at that). > > > > Content: > > > > I think Ate meant to explain a little bit more what NetBeans is to all > > users: what you can do with the platform, what you can do with the IDE, > > how is being donated to Apache, etc. > > > > Maybe we can use Confluence to discuss about the content. Let's create a > > web page with the texts that should go into the front page, and then > > subpages in Confluence that expand on that. Screenshots will be > > appreciated. We can users for screenshots, for instance. > > > > What say? > > > > Cheers, > > Antonio > > > > > > El 19/02/2019 a las 20:28, Geertjan Wielenga escribiĂł: > > > Hi all, > > > > > > I noticed this by our mentor Ate: > > > > > > Somehow I don't see this mentioned/used anywhere on the > > > currentnetbeans.apache.org website though. > > >> Nor any other description of what NetBeans is, which seems odd... > > >> > > >> > > > Here: > > > > > > > > > https://lists.apache.org/list.html?d...@netbeans.apache.org:lte=1M:After%20again%20checking%20the%20other%20parts > > > > > > So, I tweaked the front page a bit: > > > > > > https://netbeans.apache.org/ > > > > > > I added 'Fits the pieces together' as well as the three things that > > > NetBeans is. > > > > > > Thoughts? Comments? > > > > > > Gjk > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > >
Re: Apache NetBeans 11 or 11.0 ?
On Sun, Jan 27, 2019 at 10:28 AM Christian Lenz wrote: > > TLDR; > Please everyone, go away from Connection JDK/Java with NetBeans. NetBeans is > for years an IDE for a lot more languages. Java should not anymore the main > Language that is full featured supported in NetBeans than others that > NetBeans supports out of the box. First NetBeans can handle PHP very well, > better than JS or other Frameworks like Angularjs, Angular, React or > unfortunately Vue which is not supported. It can handle HTML/CSS/LESS/SCSS > and C/C++ and Assembler too. NetBeans is an IDE not only for Java developer > anymore. > > Yes, I can understand that binding was in the past but that doesnât make > sense anymore nowadays. Totally disagree. NB __IS__ Java -- not PHP, not JS. That plugins can be written to allow NB to do wonderful things for those other languages is irrelevant to NB versioning. As a developer I want to know that with NB20 I can use all the features of JDK20 in my code. Java will be changing significantly in the future. We need to remember that code written for JDK 11 will not run, in many instances, on JDK 8. Should that be reflected in NB numbering? Me thinks so. At least I would like it so. Without that relationship developers will be required to do research to find out what features can be used with the version of NB they may be planning to use. - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [VOTE] Apache NetBeans Version Number: 2019.03
Since the number is no longer associated with the level of Java it supports the number is meaningless. At least this scheme indicates when it was released. +1 On Fri, Jan 25, 2019 at 7:51 PM Laszlo Kishalmi wrote: > > Dear all, > > Well, it is time to finalize out version scheme for a while. There will > be three voting threads created on this topic with subjects: > > * [VOTE] Apache NetBeans Version Number: 11 > * [VOTE] Apache NetBeans Version Number: 11.0 > * [VOTE] Apache NetBeans Version Number: 2019.03 > > Everyone from the community can cast his/her own vote on each thread as: > > +1 I like it, let's do this way > 0I'm Ok with it, does not particularly like it, but won't mind it > -1 I do not like it at all. > > Each thread is going to be open for 72+ hours and going to be closed at > the same time. Regardless from the number of votes, that version number > would win which has the greatest sum of the vote values. > > Voting is a community event! Be a proud community member and cast your > vote! > > Thank you! > > Laszlo Kishalmi > > Volunteer Release Manager of Apache NetBeans 2019.03 > > P.S.: Please keep this thread for voting only! > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: OSGi support for maven-based plugins
Wildfly is also running on OSGi as I recall. On Sat, Dec 15, 2018 at 12:18 PM Matthias Bläsing wrote: > Hi, > > Am Samstag, den 15.12.2018, 22:04 +0200 schrieb Emilian Bold: > > I have not heard of any open-source projects with OSGi modules... > > JDeveloper uses this but I believe it's proprietary. > > Glassfish/Payara are JavaEE/JakartaEE servers using OSGI. if I'm not > mistaken Eclipse is also using OSGI modules (Equinox). > > Greetings > > Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: How important is OSGi support?
My understanding is that OSGi was developed as a client side technology for small form factor devices. It's easy to think of it as a server technology since all the current app servers are based on OSGi. Since NB is only for Swing I have started looking at the possibility of creating a JFX client running on Felix. It's not difficult to do and provides all the support of the OSGi platform to a very nice client (automatic updating of bundles, etc.). Unfortunately I have not gotten past the proof-of-concept stage (last tried on 8.2) due to other distractions but I plan to get back to it soon. For that reason I personally am very interested in NB having good support for creating OSGi bundles (assuredly different from integrating with NB which I presume Peter is saying is broken). I haven't tried to create an OSGi bundle with 9 or 10 but hope creating bundles for Felix is not broken. Fortunately, it is a technology very usable on both client and server. Just my $.02. On Fri, Nov 9, 2018 at 4:23 AM Peter Nabbefeld wrote: > > Hello, > > OSGi support is obviously broken since NB 9, see > https://github.com/mojohaus/nbm-maven-plugin/issues/52 for details. I've > created NETBEANS-1638 as a critical bug. > > The question here is, how important is OSGi for functionality of > NetBeans itself (e.g. JEE support), i.e. does it probably need to be a > blocker? > > Kind regards > > Peter > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: JDK requirements for building NB
With enough work NB could be written in assembly and produce anything but the burden to do it would not be worth the cost probably. There is such a huge architectural difference between JDK8 and JDK11 that to expect developers to accommodate both is unrealistic -- at least is seems many work-arounds will be required and put a lot of strain on developers for very limited benefit. But you are, of course, correct, with enough work anything can be accomplished. Yes, I realize any JDK can be used to compile something to byte code. But do you remember all the confusion, even on this list, about why NB9 had to be compiled on JDK8? It's far from intuitive. I'm simple minded I know but a ratio of 1:1 is a good thing to my simple mind. NB9 for JDK9; NB11 for JDK11. And synched with the LTS JDKs. By the way, Gj, your link to the 100 points/7 silver bullets presentation was awesome. What a great presentation/presenter! On Tue, Aug 21, 2018 at 3:37 PM Geertjan Wielenga wrote: > > Do you understand that Apache NetBeans can provide features for JDK 8, 9, > 10, 11, and 12, all at the same time? > > Do you also understand that whether or not NetBeans provides features for > working with a particular JDK is a completely different question to which > JDK is needed to build the sources of Apache NetBeans? > > Gj > > >
Re: JDK requirements for building NB
Quite right and eloquently put, Scott. If people don't want the feature-set of JDK9 continue using NB8.2. For those of us who want the feature-set (in particular HTTPClient) of JDK11 we need NB11 sooner rather than later. We need it to work with the OpenJFX11 modules in Maven central (which NB9 does not do) the day OpenJDK hits 11GA. Thank you, Scott!! On Tue, Aug 21, 2018 at 11:11 AM Scott Palmer wrote: > > > Yes, and Iâm saying the latest Netbeans requiring the latest released JDK > to build is a good thing. It means the latest Java features can be used. > If you donât want or need them, use an older NetBeans platform - donât hold > everyone else back. > > Scott > - > T >
Re: JDK requirements for building NB
And this brings us back the the whole question of how to number NB releases. In my opinion the NB version should reflect the JDK it supports. NB is a Java application that just happens to provide facilities for people to write plug-ins who want to do non-Java stuff like c/c++, Python, PHP, ecmascript, etc. etc. Those plugins can be numbered any way the author wants to number them. I assume NB9 will be forked as the starting point for NB11. That does not imply that NB9 will go away or cease to exist. Anybody who wants to back-port features for NB9 may do so but NB11 should be an advertisement that it will build on and develop for the JDK11 feature-set and VM. There is no reason NB versioning needs to reflect non-Java plug-in versioning. And there should be no assumption that a plug-in for NB9 will build or run on NB11. As the Java feature-set expands/contracts moving forward, breakage is bound to happen and backward compatibility will have to break as well. The feature-set differences between 8 and 9 are a very good example. The new HTTPClient class in 11 is another very good example. I can't tell at a glance if something called NB9 or NB2018.3 or will develop or build on the current JDK if the versioning does not make it clear. On the other hand, if NB9.2 includes features from JDK12 that do not break backward compatibility before NB12 is released what's not to like? Perhaps I'm too naive about git but from what I've read this seems like a relatively simple and intuitive way to move NB forward as the pace of Java development increases and versions move forward. I've read all the other positions in the previous thread and none of them is convincing in my opinion. Releasing often is good and version numbers should have meaning. On Mon, Aug 20, 2018 at 10:39 AM Svata Dedic wrote: > Hi, > > we / you should also consider, before dropping JDK8 as a runtime > platform, that applications that build ON TOP of NetBeans platform may > have a way conservative requirements than developers who strive to use > the bleeding technology edge. > > > >
Re: Apache NetBeans Release Cycle
Just saying that with early releases of JDK12 now shipping I don't see the point of a NB10. The versions of NB9 I'm using already have JDK11 features being included. Further, NB is Java. While it may provide functions to other languages, so far it IS Java. So Java implementation level still makes a lot of sense to me. Just my $.02. On Tue, Aug 7, 2018 at 7:22 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com.invalid> wrote: > Just as a quick FYI: Both JDK 9 and JDK 10 are supported in Apache NetBeans > 9, i.e., no, we've not skipped JDK 10. > > Gj >
Re: Apache NetBeans Release Cycle
To me it makes sense to have NB reflect the level of Java implemented. For example, features of JDK 11 can be added incrementally to NB 9.1, 9.2, etc. (schedule is irrelevant to me -- every 3 months is fine) but when the full function of JDK 11 is included then NB 11 should be released. I assume we're going to skip JDK 10 at this point. Releases like 2018.3 tell me nothing about what the product includes. But if Java moves to that naming scheme then NB should move to that scheme to indicate what is implemented. On Tue, Aug 7, 2018 at 1:46 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com.invalid> wrote: > Hi all, > > We've discussed this informally, i.e., the topic of the release > cycle/cadence, a few times over the past months. > > Let's nail it down as far as possible so that we can give clarity to our > users about our intentions and also to enable us to organize features > coming in through donations and otherwise into releases. > > https://cwiki.apache.org/confluence/display/NETBEANS/ > Apache+NetBeans+Release+Cycle > > Right now, we have a clear suggestion around in which month of the year we > will release. I.e., the Apache NetBeans (incubating) 9.0 release was our > August release (and we even managed to release it a few days early, in > July, hurray!). So, this year, we will have another release in November, > that's our next big target, if we agree with the above proposal. > > However, a separate discussion is about release numbers. Our current > release is 9.0. How do we decide to number the other releases? A simple > proposal might be to have our major release in August of each year and then > all then make all the other releases minor. However, that's just a thought, > another one could be that we should simply consider how large the features > are that we have added and base major/minor on that. Or we could try to > follow the JDK release numbering more or less. > > Anyway, thoughts welcome, > > Gj >
Re: Nightly builds
That link takes me to build 334. The current build is 496. There is a 497 but it has some kind of problem. The link I use: https://builds.apache.org/job/incubator-netbeans-linux/ On Tue, Jul 31, 2018 at 9:10 AM, ehsavoie wrote: > https://builds.apache.org/view/Incubator%20Projects/job/ > incubator-netbeans-release/lastSuccessfulBuild/artifact// > which is the link from http://netbeans.apache.org/ > download/index.html#latest > I could download the linux build. > Emmanuel > > > On Tue, Jul 31, 2018 at 6:08 PM Geertjan Wielenga > wrote: > > > Can you provide a link to what you're referring to? > > > > Gj > > > > On Tue, Jul 31, 2018 at 5:57 PM, ehsavoie > > wrote: > > > > > Hi, > > > The nightly builds haven't been updated since the 8th of July. > > > Is the link still correct ? Why don't we have updates since then, all > the > > > more so with the 2nd donation going to be merged in. > > > Cheers > > > Emmanuel > > > > > >
Re: [DISCUSS] Proposed Release ProcessWAS: Merging back netcat@ into the dev@ mailing list
One of the really nice features of NB has been the fact that you can run dozens of versions installed in parallel (I usually only have not more than four). I grew accustomed to living on the nightly builds and, fortunately, if one doesn't work you run "uninstall" and wait a couple of days and try again...assuming you are interested in the new feature usually announced by Gj in one of his blog entries. Seems like a few days before a new "version" release the nightly builds were not available while the release version was pulled together. I found this procedure to be very handy. Seems like this process could still be done with Git/Apachewhy not? I think it's unique and I'm not aware any of the competitors who provide that service (maybe Eclipse does -- not sure). As I write Jenkins is building #473 and I'm running on #470. Maybe we just need to make the Jenkins builds more obvious for those of us who like to bleed and keep the "versions" on a cadence that is convenient for developers. What is best for developers? My $.02. On Tue, Jun 26, 2018 at 2:12 PM, Sven Reimers wrote: > Hi all, > > I like the overall concept - just some small things. > > 1. Having people wait for critical bugfixes for 6 months is quite long - > can we do better? > > 2. Do we plan to do update releases, e.g. 9.1, or 9.0 patch 1 (as before) > with just some cherrypicked stuff onto the existing release base branch? > How does this fit in with NetCAT, e.g. just do some sanity checks for the > patch release? > > Just my 2âŹc > > -Sven >
Re: Microsoft buys GitHub
Do we need to be reminded that IBM had a 32 bit desktop OS a year and a half before MS could muster one up? They finally (20 years late) gave Windows 10 users two huge benefits millions of us have been enjoying for more that 20 years: virtual desktops (a VERY clumsy implementation to be sure) and a usable command prompt window. Even at this time they are using their ridiculous "software patents" to prevent innovation and hold back the advance of the industry. Microsoft is and always has been a poison to technology. Everything they have has been acquired either through purchasing or bankrupting the innovator. There's a lot of stuff on GitHub MS can now steal and market like they invented it...welcome to the Windows World. They've never invented anything but they sure know how to market other people's innovations. The sooner NB liberates itself from GitHub the better off we'll be. If Git is the tool of choice I say let Apache set up it's own Git repositories for Apache projects. On Wed, Jun 6, 2018 at 12:46 AM, Tim Boudreau wrote: Honestly, when I think of Microsoft, I think of the immeasurable harm they > did to progress in computing. There was going to be a PC on every desktop > regardless. They just ensured that PC ran a horrifically flawed, > vulnerable, broken by design OS. >
Re: How to participate in Apache NetBeans without a GitHub account?
+1 On Wed, Jun 6, 2018 at 6:30 AM, Glenn Holmer wrote: > On 06/06/2018 08:13 AM, Emilian Bold wrote: > > GitHub should just be one venue where we engage with the community > > and contributors but we should have other workflows in place, > > preferably that depend on Apache infrastructure only. > +1 > > -- > Glenn Holmer (Linux registered user #16682) > >
Re: IntelliJ IDEA vs Netbeans
Intellij integration with Maven is quite poor and indexing, in my experience, takes much longer than NB. Strangely enough, since [NETBEANS-655] is a show-stopper for me I decided to try Intellij yesterday. It's quite weak. While it does create the Maven project it does not produce a *.jar file with the default set-up, installs very old plugins, and even after fixing the packaging xml does not produce a packaging component. Inellij does not manage projects as well as NB does (i.e. delete, close) The NB editor provides some really convenient features such as imports (Ctrl+Shift+i) which are useful when starting to develop a class. Other editor features appear to be comparable. I've also recently looked (again) at Eclipse -- now there's a total train wreck if anybody wants to see one. I always keep an eye on the competition but keep running back to NB for the nice productivity features. On Fri, Apr 20, 2018 at 8:21 AM, Neil C Smith wrote: > On Fri, 20 Apr 2018 at 15:29 John Leon wrote: > > >- Add more padding/borders to the Darcula L&F as it feels crowded to > me > > > > > Funnily enough just been doing exactly that for Praxis LIVE (image at > https://twitter.com/PraxisLIVE/status/984810937159995392 ), and making it > a > bit more responsive to --fontsize. Definitely be interested in helping out > with this. > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
Re: The Red Sea
Edit rights to this: https://netbeans.apache.org/participate/submit-pr.html So I followed the link and this time I saw the link at the bottom of the page that says "See this page in Github". Now I see why you mention PRs to change the website. Thanks. On Mon, Apr 2, 2018 at 7:50 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Edit rights to what exactly? You or anyone can get edit rights or do pull > requests. The best person to make the changes you find important is you. > >
Re: The Red Sea
If somebody with edit rights to the site wants to converse with me off-list I'll be happy to document my experience with some verbiage they can include. On Mon, Apr 2, 2018 at 12:21 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > On Monday, April 2, 2018, Chuck Davis wrote: > > > Thanks Metthias. > > > > I'm now down to 10 marked projects after building externally with Ant and > > then building with NB those projects still marked as errors. The strange > > thing is that even though they are marked with errors they seem to build. > > I've noticed there are a lot of warnings but I don't see the errors > except > > in cases where NB can't find the class (which it seems to find -- maybe > > just a marking issue?). > > > > I think whoever is in charge of the page at the link in my first message > > > We all are in charge, together. So, please feel free to change/edit/improve > yourself. > > Gj > > > > > should include the procedure to clone and prime with NB for those of us > who > > are..lazy. As soon as I did the external build with Ant, NB started > > it's background scanning of projects during which I got messages about > > being low on memory. Checking the log I saw that NB was only allocating > > 1GB. I increased to 5GB and didn't see the message again. So a note on > > the site indicating the memory may need to be increased might be helpful. > > Of course, nobody else is probably going to be stupid enough to open all > > the projects at the same time.duh. Well, what can I say, NB DID ask > -- > > I just gave it my answer. > > > > Documenting these steps on the web site might help some other poor > > knucklehead who gets the fancy to look at the code; seeing the > > documentation how to do it with NB he/she won't have to bother the list. > > >
Re: The Red Sea
To say nothing of all the gigs Ant downloads in the process I'm still getting "resolve" problems with Jetty and uh, uh, can't remember at the moment. But I assume when the JEE stuff gets added those issues will resolve themselves. There is also one issue that will resolve itself when I move to jdk9 on that machine. At this time it's working well enough that I can look at code -- the original intent. Mission accomplished. Thanks for your interest, Tim. On Sun, Apr 1, 2018 at 6:40 PM, Tim Boudreau wrote: > Performance wise you're definitely better off building once before opening > - scanning class files is much faster than sources. > > -Tim > >
Re: The Red Sea
Thanks Metthias. I'm now down to 10 marked projects after building externally with Ant and then building with NB those projects still marked as errors. The strange thing is that even though they are marked with errors they seem to build. I've noticed there are a lot of warnings but I don't see the errors except in cases where NB can't find the class (which it seems to find -- maybe just a marking issue?). I think whoever is in charge of the page at the link in my first message should include the procedure to clone and prime with NB for those of us who are..lazy. As soon as I did the external build with Ant, NB started it's background scanning of projects during which I got messages about being low on memory. Checking the log I saw that NB was only allocating 1GB. I increased to 5GB and didn't see the message again. So a note on the site indicating the memory may need to be increased might be helpful. Of course, nobody else is probably going to be stupid enough to open all the projects at the same time.duh. Well, what can I say, NB DID ask -- I just gave it my answer. Documenting these steps on the web site might help some other poor knucklehead who gets the fancy to look at the code; seeing the documentation how to do it with NB he/she won't have to bother the list.
Re: The Red Sea
So I decided to look at NB code base. Followed the "bootstrap" section here: https://netbeans.apache.org/participate/submit-pr.html except that I used NB8.2 to do the Git things. When NB asked if I wanted to open a project I selected them all and clicked "Yes". After cranking several minutes nearly all the projects have errors. I'm no Git ninja but I thought the master branch in Git was gold code. Anyway, is this the expected outcome? Why are projects in "master" branch when they won't compile and build? I presume the next step is attempting to get rid of the sea of red? Or have I screwed up something? If I have to work on getting rid of the sea of red I think I'll just go off and work on my own stuff and leave NB to be tended by people who know what they are doing. Thanks for any guidance on what I've done wrong.
Re: Usability study was: Think Java, not Electron! was: Apache HTML/Java UI
Oh, I'm sorry. I was under the impression that with JS you had to write functions to do all those things. My ignorance showing On Fri, Mar 16, 2018 at 2:28 PM, Dmitry Avtonomov < dmitriy.avtono...@gmail.com> wrote: > @Chuck > Yes and no. I mean HTML+JS+CSS. I'm still struggling with something like > the attached image (hopefully the attached image won't get cut out). > There's mig layout that sort of comes close, but overall my experience > with swing (including its layouts) is that it's fine as long as I need to > position a few elements here and there (and I definitely like it more than > WinForms). But overall the amount of configuration, clicking in netbeans, > adding libraries for validation balloon popups etc, adding listeners for > focus lost, writing methods for programmatically updating fields and making > sure that the same logic as onFocusLost is executed, listening to document > changes on text fields etc is just enormous. Maybe there's some silver > bullet that I don't know of. > > And you might say that I'll get all the same problems with an html/js/css > solution. But there are probably 2 billion devs working on the tech every > day, pushing dozens of libs every year. How much progress is there in the > Java Swing world? We're stuck with solutions a decade old (I might be wrong > though). > > PS: I haven't tried javafx. I tried to try it once a very long time ago > (when I knew much less than now), didn't get it, stuck with swing. Started > using NBP - looked like swing was the first class citizen, so again that > was my choice. > > > > > On Fri, Mar 16, 2018 at 11:50 AM, Chuck Davis wrote: > >> Dmitry, that is the whole purpose of Swing layouts. HTML tables cannot >> compare with the functionality of layouts. >> >> >> I also constantly find myself struggling with creating forms in swing that >> > are just used to represent parameters for command line programs, it's >> > always tricky for me to make everything aligned and resize nicely. Form >> > validation is yet another pain in the ass, especially when it comes to >> the >> > visual part of notifying the user what's wrong in which part of the >> form. >> > It would be so nice if all of this could just be rendered as a simple >> html >> > table with my choice of js validation framework and that I didn't have >> to >> > think about layouts etc too much. >> > >> > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
Re: Usability study was: Think Java, not Electron! was: Apache HTML/Java UI
P.S. And JavaFX layouts are an order of magnitude better than Swing layouts. On Fri, Mar 16, 2018 at 11:50 AM, Chuck Davis wrote: > Dmitry, that is the whole purpose of Swing layouts. HTML tables cannot > compare with the functionality of layouts. > > > I also constantly find myself struggling with creating forms in swing that >> are just used to represent parameters for command line programs, it's >> always tricky for me to make everything aligned and resize nicely. Form >> validation is yet another pain in the ass, especially when it comes to the >> visual part of notifying the user what's wrong in which part of the form. >> It would be so nice if all of this could just be rendered as a simple html >> table with my choice of js validation framework and that I didn't have to >> think about layouts etc too much. >> >>
Re: Usability study was: Think Java, not Electron! was: Apache HTML/Java UI
Dmitry, that is the whole purpose of Swing layouts. HTML tables cannot compare with the functionality of layouts. I also constantly find myself struggling with creating forms in swing that > are just used to represent parameters for command line programs, it's > always tricky for me to make everything aligned and resize nicely. Form > validation is yet another pain in the ass, especially when it comes to the > visual part of notifying the user what's wrong in which part of the form. > It would be so nice if all of this could just be rendered as a simple html > table with my choice of js validation framework and that I didn't have to > think about layouts etc too much. > >
Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFXfromOracle JDK
Gili: So now that they are no longer in charge (it's open source now) let's fix AWT/Swing/FX and start marketing. We're in charge now. Or did I take a nap and miss something? Ultimately, perhaps not in the short term, you get market share by providing a demonstrably better alternative. We agree on one thing and that is how horrible are browsers for getting real work done and the level of coding skills -- anybody can make a web site these days -- and they look like it. It's like VBA making everybody who writes a macro in excel think they are a programmer. I've heard that in offices: "I'm programming an excel sheet." The only reason I've heard for using HTML is it looks better. Well, if you don't like the looks of Swing change the L&F! If there's no L&F you like, create one. Don't throw the baby out with the bath water as they say. Maybe NB needs to start a L&F contest? One of the problems with this whole discussion is that there is such a wide variety of interests. I happen to be from a business background and specifically financial interests. I got into programming because the software I had to use (MOST accounting software) was so poor. I learned what I needed to get the job done (I wasn't being paid to be a programmer) and, unfortunately, because of that I never got the academic background the smart people here have about render pipelines, etc. But I know VERY well what business users need; browsers can't cut it but Swing provides everything the financial side of businesses need and want. Now if your use case is disseminating information to either internal or external users and providing file downloads there is no better tool than a browser. For doing company handbooks, training films, etc. NOBODY wants to use Swing in that case. Things that move and bob are not welcome in a business use case but they're all the rage (and appropriate) for information dissemination. For business use cases "pretty" and "cute" are unwelcome -- we want functionality. For a browser "pretty" and "cute" are what it's all about -- HTML is the right tool. The corollary to that is the audience. There is a vast difference between 250 people placing an order at a web site in a day (a browser is quite appropriate here) and the AP clerk who has to record 250 AP invoices every day (or even one day!). With a heads down, efficient data entry Swing dialog that clerk can process 250 invoices in a relatively short time (and time IS money). Giving that poor clerk a browser interface to struggle with is a mean thing to do to an employee. Swing provides a great focus traversal policy -- FX is even easier and better. Use the right tool for the use case. I do desktop apps -- give me Swing/FX. Christian does web apps -- give him a browser. NB can handle them both and handle them nicelyer, well, at least as nicely as HTML/browsers can be made to work. On Wed, Mar 14, 2018 at 5:58 PM, cowwoc wrote: > Chuck, I appreciate free software as much as the next guy. But I still > blame Sun and Oracle for killing AWT/Swing. > > If they wanted more community contributions they could have opened up the > bug reporting system, faciliated pull requests, and shown that they are > acting in good faith. They chose to pursue a one-way conversation and it > cost them the market. > > So yes, I appreciate what we got but ultimately Oracle bares the > responsibility for AWT/Swing/JavaFX dying. Oracle is not a B2C company and > these technologies requires a company that excels at marketing to end-users. > > Gili > >
Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFXfromOracle JDK
So, what are you waiting for? https://wiki.openjdk.java.net/display/OpenJFX/Main will be more than happy to suck up some energy from you. Sorry, I guess I'm in a snarky mood today but I just get so tired of everybody ragging on Oracle. How long has OpenJDK been the source and Oracle has been doctoring it to make it usable? Now it has a shiny, new rendering engine for AWT/Swing; they don't have to screw around upgrading rendering with every release. What else should we (the Community) be doing for Java to make it more usable? What bugs have any of us here fixed (I know some of you have done many and you are herewith thanked for your efforts)? Same can be said for OpenJFX. As far as I know Oracle and IBM are the only companies that have been taking OpenJDK and doctoring it to improve it enough to be released (and IBM has never included JFX). Maybe they're tired of the drag we've been. PS I am not and never have been an Oracle employee. I don't get commissions for sales of their products. I'm just another freeloader like the rest of you whiners and complainers (trust me, I've done my share). PPS Doubly snarky benefits being dished out today -- free as in beer. On Wed, Mar 14, 2018 at 11:53 AM, Norquay wrote: > JavaFX would be faster than WebGL if it got some developer energy pumped > into it. O is so fucking brain dead... >
Re: NB9
I stumbled onto a tutorial for NB binding a couple of days ago. I looked for it in NB9 and it is missing (present in 8.2). I don't see a plugin either. Is this an oversight or by design? I've never actually used it but it seems relevant to JSE. Anybody know?
Re: My Personal UI Rant, Was: Think Java, not Electron! was: Apache HTML/Java UI instead of
Scott, thanks for saying it so well. I absolutely loathe and despise trying to get any real work done with a browser interface. On Tue, Mar 13, 2018 at 8:06 AM, Scott Palmer wrote: > Sometimes I think the world has gone crazy. > > Here are a few simple observations: > - JavaFX is the best UI tech that Java has going for it these days. > - Swing/AWT has been heading towards obsolescence for several years now. > It works, but the future of desktop UI with Java is JavaFX. > - HTML is a HORRIBLE way to render an application. It works very poorly, > if at all, and not consistently across browsers. (Look what people have to > go through to try to get something as simple as a table with scrolling data > and static column headers, for example.) > - Javascript is junk. The interesting thing about stuff like Electron is > that they managed to get it to work at all. We give it extra credit simply > because it was done with technologies that make it so much harder to do. > (It also tends to be slow IMO.) Thatâs cute and all, but ultimately wasted > time. It would be that much better and cheaper to develop if done with > better tech like Java/JavaFX. > - The popularity of Web UIs has done a disservice to the development > community. They have lowered the bar so far that we accept the utter > rubbish and awful user experience of most web apps as ânormalâ. We have a > generation of developers that donât even understand why Javascript is > garbage or how crippled applications are that run in a browser. Have you > noticed when you see an interesting web app that you are more impressed > because it is a web app? If it were a desktop app you wouldnât give it a > second thought. > - I donât know why anyone would want to bring HTML UI into a Java > application (when they donât have to) as it is such a massive step > backwards. > > > So stopping running around like the sky is falling. Swing/AWT, JavaFX > arenât going to disappear. Oracle wasnât doing anything significant with > Swing. If they stop, we arenât likely to notice. JavaFX is the greater > concern, because it is the better tech and still needs feature > development. The community around it can keep it going as long as there is > a consistent vision for it Ideas of using HTML for UI on a desktop app > programmed in Java are ridiculously insane. We already have a much better > cross-platform UI technology, no need to put work in to move backwards to > an inferior UI tech. > > Scott > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Think Java, not Electron! was: Apache HTML/Java UI instead of
[2] does not build on release 219 with jdk9
> [1] Plus few minutes of Maven plugins initial download time...
> [2] Have you noticed that the wizard ("New Project", "JavaFX", "Java HTML5
> Application") is written in HTML UI? I hope the transition from the Swing
> to the HTML UI was smooth enough to not be really noticeable.
>
Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX from Oracle JDK
I can't be the only person who has noticed that jdk8 had 15 HTML classes/interfaces and jdk9 has 74 HTML classes/interfaces? Does this tell us something? Sure looks to me like HTML is coming to Java in a big way. Is there anything a browser can render that Java cannot render? If so, what is the point of all the HTML creeping into Java? On Mon, Mar 12, 2018 at 11:26 AM, Kenneth Fogel wrote: > As far as I can tell Swing and AWT were pretty much abandoned years ago > except for maintenance. > > Ken > > -Original Message- > From: Matthias Bläsing [mailto:mblaes...@doppel-helix.eu] > Sent: March 12, 2018 1:37 PM > To: dev@netbeans.incubator.apache.org > Subject: Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX > from Oracle JDK > > Am Montag, den 12.03.2018, 17:26 + schrieb Neil C Smith: > > On Mon, 12 Mar 2018 at 17:12 Geertjan Wielenga < > > geertjan.wiele...@googlemail.com> wrote: > > > > > I really wouldn't be worried at all about something that will be > > > supported "through at least 2026". > > > > > > > In a public, freely available JDK? > > > > I did not see Swing or AWT marked as deprecated in OpenJDK. So removal > at this point is out of the question. I doubt that Oracle will remove > the whole desktop module from their JDK, so even Oracle JDK will most > probably carry AWT+Swing. > > My reading is a bit less *heaven will fall*: > > * The java plugin is dead (thanks go to the browser makers) > * Java Web Start is mostly dead and was never open source. Interested >parties could place their money on Red Hat, which might have its >open source successor (Iced Tea Web) > * JavaFX is not part of the Oracle JDK anymore > * The future of Swing and AWT is not yet decided > > To read more into the white-paper is just reading tea-leaves. It might > be fun, but the future is not told there. > > Greetings > > Matthias > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
Re: Oracle will remove JavaFX from Oracle JDK (was: Re: Noticed Oracle is Working to Remove Java FX, AWT, and Swing from Base Java/JDK)
If I understood the message of the white paper NB will have to be distributed through MS and Apple's app stores (I have no idea what the process for getting their approval or the cost of doing that may be) and that it will have to be shipped as a containerized application that includes the jdk. Java (as we know it) will not be running on either platform. Java will continue as "multi-platform" but it will most certainly no longer be cross-platform. This is as C/C++ is multi-platform but not cross-platform. Docker is going over big because it solves some problems. Shortly, nothing may be running on any computer except as a container. And that has huge implications not only for NB but for every Apache product and lots of other products (including internally developed business apps). Oracle is simply responding to the realities of the industry. We're not living in the decade of 2000 anymore. Things have changed. Oracle is responding to that change. Apache is going to have to respond to that change. NB is going to have to respond to that change. The white paper states strongly that packaging must change. Jlink is the current packaging of the future for Java (sounds like it just creates a container but doesn't say so in so many words). Will it be possible to package Java as a container and continue to use it as such?? Who can tell? The white paper sounds like Java will only be available if containerized with your application: i.e. each Java application will be running a separate instance of the new modularized jre with only those modules your application needs. Jdk11 will be supported for 8 years. Oracle said they will continue to develop Swing during those years. JavaFX has some very nice features I would expect will bleed into Java/Swing but JavaFX also has some ugly warts. Swing has been very good for many years and it sounds like will get better during the next 8. If you look at the build dependencies for OpenJFX it's easy to see why Oracle would not want Java to be dependent on all those other open source projects over which they have no control -- it's very logical for Oracle to spin off JavaFX and keep it separate from Java proper. Gluon is a logical perpetrator for such a mission. They've done a pretty good job with SceneBuilder. Will there be a jdk12, 13, etc? A lot will change before 2026 when jdk11 support ends. By then Docker may be a thing of the past, replaced by latest and greatest. All the operating systems will be entirely different. Many other companies have HUGE investments in Java -- Oracle is not the Lone Ranger. Indeed, I believe every major player other than Microsoft and Apple are at the table of OpenJDK. The message is clear: Java will be changing. How and into what nobody knows at this point. The industry is in transition and will never stop transitioning. Nobody should be blaming Oracle for that. Will Java die? I doubt it. The alternatives are not attractive (at least to me). Will it morph? Definitely.Jdk11 will probably be the last Java we would recognize at this point. At some point Java will no longer run as Java even on Linux. I'm an old geezer who doesn't much care for the changes but the changes will come. Security is essential and will drive the changes of the industry. Containers address that concern. Us old geezers get brittle and a day will come when the next change "breaks the camel's back" as the saying goes. We'll drop out but you young bucks will adapt and continue driving the industry (and Java) forward into a more secure digital world. I wouldn't say with Geertjan, "It's all good" but it IS probably all necessary Now, as for "web first" that's a discussion for another day! > > > Maybe, but all the more reason for the stewards they mention. One can > > certainly run servers and services as Java applications on those systems > > too. But, yes, not directly making any money for Oracle. But SMBs can > > definitely make money off these things, and if the community wants to > keep > > this stuff going, then theyâll have to chip in on the bits they care > about. > > This was the main point of my writing in the first place; to figure out > > what we can do to support it. I imagine JetBrains will be involved as > well. > > They are very dependent with their current products. > > > > > > > > > âExcludeâ seems overkill considering other environments/runtimes exist on > > both; Node, Qt, Rust, Go, etc.. .Net even exists on Mac. Them not > shipping > > something directly is not the same as exclude. > > > > > > > The browsers everyone is using on those platforms are not written in the > > languages you mention, so I donât see that as the show stopper. > > > > > > I donât see that as a goal of the NB community, and it certainly doesnât > > do anything for all the consumer devices. I do think we can help support > > desktop Java since we highly depend on it. > > > > Wade > > >
Re: Oracle will remove JavaFX from Oracle JDK (was: Re: Noticed Oracle is Working to Remove Java FX, AWT, and Swing from Base Java/JDK)
That white paper says to me jdk11 is the end of the road for JSE at Oracle. Without Swing/JavaFX I can't think of a single reason to have JSE on a computer. The message of the white paper was clear: both Apple and Microsoft own their platforms and the day is not too distant when both will exclude Java from running on their platform. Apple already stopped shipping Java. The message is clear: migrate to .net for windows or swift for mac. Java will only be running on Linux in the near future and that market is not big enough to be attractive to Oracle. There will be no more cross-platform Java (or anything else) development. Browsers will continue to be available on all platforms -- if you want to play on somebody else's platform you will abide by their rules. It is a sad day but, admittedly, exclusivity is not a new idea to either Apple or Microsoft. What is the remedy? Make alternatives so attractive IT managers will CHOOSE to leave either MS or Apple for the alternative.
Re: build 211
Having issues with 205 so updated to 211 this a.m. I'm refactoring a project to use jdk9 on the referenced build. It is a Maven/JavaFX project. I've added the module-info class and the project compiles fine. The first issue was that the project couldn't find HttpClient (in the incubator). I appear to have gotten that fixed. The next problem is when I try to execute the project it can't find the main class anymore. As soon as I click the run arrow the main class selection dialog pops up but is totally unusable -- I think this is a bug that needs to be fixed before release. ?? I've googled and researched a considerable amount. I've added --main-class to the vm options so that for the release configuration my vm options look as follows though there appears to be no difference between "release" and "default" configurations: --add-modules=jdk.incubator.httpclient --main-class=com.yakridge.client.MainApp I assume the problem arises somewhere between the classpath and module path revisions but I don't know that for a fact. I just know I'm stuck. The big question is how do I set the main class for a jdk9/Maven project? It's specified correctly in the POM. Thanks for any guidance. - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: info requested regarding build fail
Yeah, I've been thinking about that. Don't understand how SUSE can screw-up Ant but since it apparently happened and even Apache Ant 1.9.9 didn't seem to work for me maybe just increment the readme to require Apache Ant 1.10.1 ?? Obviously, Fedora did something to ant as well. I agree with John that we don't want to start listing a bunch of exceptions for various operating platforms. Just update the readme to require Apache Ant with, perhaps, a note that other sources of Ant are unreliable; perhaps a broad statement like "Ant from Linux repositories has not worked in some cases" -- get the real thing from Apache ?? On Sat, Jan 20, 2018 at 12:08 AM, Antonio wrote: > So build fails with openSuse's Ant 1.9.9, doesn't it? > > If so maybe we want to add a small comment in NetBeans' README... > > Cheers, > Antonio > >
Re: info requested regarding build fail
Your suggestion worked Gj. Success at last! I've both cloned and used the source zip successfully with Apache Ant 1.10.1. Must be something wrong with openSUSE's compilation of Ant 1.9.9. Haven't tried to run the results yet because this machine does not yet have jdk9 on board. But I assume I've joined the success crowd at this point and feel comfortable that NB would "just work" since the binaries have been so smooth. Thanks to all who have helped find the problem. On Fri, Jan 19, 2018 at 12:39 PM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Iâd start by recloning from scratch, i.e., delete everything you have right > now. Clone from scratch then run Ant 1.10.1 again. > > Gj > > On Friday, January 19, 2018, Chuck Davis wrote: > > > Just tried with Apache Ant 1.10.1 and got this fail point: > > > > > > build-init: > > > > -javac-init-nbjdk: > > > > -javac-init-bootclasspath-prepend: > > > > -javac-init-no-bootclasspath-prepend: > > > > -javac-init: > > > > -init-proxy: > > > > projectized.init: > > > > init: > > > > fake-jdbc-40: > > > > compile-lib: > > > > jar-lib: > > [jar] Building jar: > > /downloads/netbeans_9/nbbuild/netbeans/ide/modules/ext/ddl.jar > > > > up-to-date: > > > > projectized-common.compile: > >[depend] Deleted 180 out of date files in 0 seconds > > [nbmerge] Failed to build target: all-db > > > > BUILD FAILED > > /downloads/netbeans_9/nbbuild/build.xml:480: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/build.xml:475: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/build.xml:522: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/templates/common.xml:201: could not delete > > /downloads/netbeans_9/db/build/classes/org/netbeans/ > > modules/db/explorer/node/ProcedureNodeProvider$1.class > > > > Total time: 21 seconds > > chuck@Dell7720:/downloads/netbeans_9> > > > > > > On Fri, Jan 19, 2018 at 12:21 PM, Geertjan Wielenga < > > geertjan.wiele...@googlemail.com> wrote: > > > > > Definitely looks like a problem with your version of Ant. Thanks also > to > > > John for the related reference as well. > > > > > > Gj > > > > > > On Friday, January 19, 2018, John McDonnell > > > wrote: > > > > > > > Hi Chuck, > > > > > > > > Have a look at this thread: > > > > https://lists.apache.org/thread.html/51dad1ca86facf5b5244ec7136d7e3 > > > > 0d42915fbb7899e38345ee95f6@%3Cdev.netbeans.apache.org%3E > > > > > > > > It seems the initial poster had a similar issue? > > > > > > > > Regards > > > > > > > > John > > > > > > > > On 19 January 2018 at 19:49, Chuck Davis wrote: > > > > > > > > > Following information as requested. I can provide any other of the > > Ant > > > > > output anybody wants to see if it will help (it scrolls way too > fast > > to > > > > get > > > > > a clue). But I seem to be the only one not experiencing success so > > > I've > > > > > contented myself to use the binaries others produce. > > > > > > > > > > LINK TO SOURCES I USED: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > > > > incubating-netbeans-java/incubating-9.0-beta-rc2/ > > > > > incubating-netbeans-java-9.0-beta-source.zip > > > > > > > > > > MY JAVA VERSION INFO: > > > > > > > > > > chuck@Dell7720:~> java -version > > > > > java version "1.8.0_152" > > > > > Java(TM) SE Runtime Environment (build 1.8.0_152-b16) > > > > > Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) > > > > > chuck@Dell7720:~> > > > > > > > > > > ANT VERSION: > > > > > > > > > > chuck@Dell7720:~> ant -version > > > > > Apache Ant(TM) version 1.9.9 compiled on October 28 2017 > > > > > chuck@Dell7720:~> > > > > > > > > > > > > > > > > > > > > MESSAGE WHERE BUILD FAILS: > > > > > > > > > > > > > > > compile: > > > > > > > > > > jar-prep: > > > > > > > > > > jar: > > > > > [jarwithmoduleattributes] Building jar: > > > > > /downloads/netbeans_9/nbbuild/netbeans/websvccommon/modules/ > > > > > org-netbeans-modules-websvc-saas-api.jar > > > > > [nbmerge] Failed to build target: all-websvc.saas.api > > > > > > > > > > BUILD FAILED > > > > > /downloads/netbeans_9/nbbuild/build.xml:480: The following error > > > > occurred > > > > > while executing this line: > > > > > /downloads/netbeans_9/nbbuild/build.xml:475: The following error > > > > occurred > > > > > while executing this line: > > > > > /downloads/netbeans_9/nbbuild/build.xml:522: The following error > > > > occurred > > > > > while executing this line: > > > > > /downloads/netbeans_9/nbbuild/templates/common.xml:252: Could not > > find > > > > > default manifest: /org/apache/tools/ant/defaultManifest.mf > > > > > > > > > > Total time: 3 minutes 19 seconds > > > > > chuck@Dell7720:/downloads/netbeans_9> > > > > > > > > > > > > > > >
Re: info requested regarding build fail
Just tried with Apache Ant 1.10.1 and got this fail point: build-init: -javac-init-nbjdk: -javac-init-bootclasspath-prepend: -javac-init-no-bootclasspath-prepend: -javac-init: -init-proxy: projectized.init: init: fake-jdbc-40: compile-lib: jar-lib: [jar] Building jar: /downloads/netbeans_9/nbbuild/netbeans/ide/modules/ext/ddl.jar up-to-date: projectized-common.compile: [depend] Deleted 180 out of date files in 0 seconds [nbmerge] Failed to build target: all-db BUILD FAILED /downloads/netbeans_9/nbbuild/build.xml:480: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:475: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:522: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/templates/common.xml:201: could not delete /downloads/netbeans_9/db/build/classes/org/netbeans/modules/db/explorer/node/ProcedureNodeProvider$1.class Total time: 21 seconds chuck@Dell7720:/downloads/netbeans_9> On Fri, Jan 19, 2018 at 12:21 PM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Definitely looks like a problem with your version of Ant. Thanks also to > John for the related reference as well. > > Gj > > On Friday, January 19, 2018, John McDonnell > wrote: > > > Hi Chuck, > > > > Have a look at this thread: > > https://lists.apache.org/thread.html/51dad1ca86facf5b5244ec7136d7e3 > > 0d42915fbb7899e38345ee95f6@%3Cdev.netbeans.apache.org%3E > > > > It seems the initial poster had a similar issue? > > > > Regards > > > > John > > > > On 19 January 2018 at 19:49, Chuck Davis wrote: > > > > > Following information as requested. I can provide any other of the Ant > > > output anybody wants to see if it will help (it scrolls way too fast to > > get > > > a clue). But I seem to be the only one not experiencing success so > I've > > > contented myself to use the binaries others produce. > > > > > > LINK TO SOURCES I USED: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > > incubating-netbeans-java/incubating-9.0-beta-rc2/ > > > incubating-netbeans-java-9.0-beta-source.zip > > > > > > MY JAVA VERSION INFO: > > > > > > chuck@Dell7720:~> java -version > > > java version "1.8.0_152" > > > Java(TM) SE Runtime Environment (build 1.8.0_152-b16) > > > Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) > > > chuck@Dell7720:~> > > > > > > ANT VERSION: > > > > > > chuck@Dell7720:~> ant -version > > > Apache Ant(TM) version 1.9.9 compiled on October 28 2017 > > > chuck@Dell7720:~> > > > > > > > > > > > > MESSAGE WHERE BUILD FAILS: > > > > > > > > > compile: > > > > > > jar-prep: > > > > > > jar: > > > [jarwithmoduleattributes] Building jar: > > > /downloads/netbeans_9/nbbuild/netbeans/websvccommon/modules/ > > > org-netbeans-modules-websvc-saas-api.jar > > > [nbmerge] Failed to build target: all-websvc.saas.api > > > > > > BUILD FAILED > > > /downloads/netbeans_9/nbbuild/build.xml:480: The following error > > occurred > > > while executing this line: > > > /downloads/netbeans_9/nbbuild/build.xml:475: The following error > > occurred > > > while executing this line: > > > /downloads/netbeans_9/nbbuild/build.xml:522: The following error > > occurred > > > while executing this line: > > > /downloads/netbeans_9/nbbuild/templates/common.xml:252: Could not find > > > default manifest: /org/apache/tools/ant/defaultManifest.mf > > > > > > Total time: 3 minutes 19 seconds > > > chuck@Dell7720:/downloads/netbeans_9> > > > > > >
Re: info requested regarding build fail
Hi John: I uninstalled openSUSE Ant and installed Apache Ant 1.9.9. At least I get a different failure.and a lot sooner in the process -- 33 seconds as opposed to 3+ minutes. I'll study the rest of that thread more thoroughly. It is little comfort to know that poor soul had a similar problem but at least I'm not alone anymore.and maybe Ant is the problem MY NEW FAILURE MESSAGE USING APACHE ANT 1.9.9 up-to-date: projectized-common.compile: compile: jar-prep: jar: netbeans-extra: javahelp: module-auto-deps: projectized-common.release: [copy] Copying 1 file to /downloads/netbeans_9/nbbuild/netbeans/websvccommon release: -init-startlevel: module-xml-regular: [nbmerge] Failed to build target: all-websvc.saas.api BUILD FAILED /downloads/netbeans_9/nbbuild/build.xml:480: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:475: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:522: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/templates/common.xml:267: Missing manifest tag OpenIDE-Module; /downloads/netbeans_9/nbbuild/netbeans/websvccommon/modules/org-netbeans-modules-websvc-saas-api.jar is not a module Total time: 33 seconds chuck@Dell7720:/downloads/netbeans_9> On Fri, Jan 19, 2018 at 11:54 AM, John McDonnell wrote: > Hi Chuck, > > Have a look at this thread: > https://lists.apache.org/thread.html/51dad1ca86facf5b5244ec7136d7e3 > 0d42915fbb7899e38345ee95f6@%3Cdev.netbeans.apache.org%3E > > It seems the initial poster had a similar issue? > > Regards > > John > > On 19 January 2018 at 19:49, Chuck Davis wrote: > > > Following information as requested. I can provide any other of the Ant > > output anybody wants to see if it will help (it scrolls way too fast to > get > > a clue). But I seem to be the only one not experiencing success so I've > > contented myself to use the binaries others produce. > > > > LINK TO SOURCES I USED: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > incubating-netbeans-java/incubating-9.0-beta-rc2/ > > incubating-netbeans-java-9.0-beta-source.zip > > > > MY JAVA VERSION INFO: > > > > chuck@Dell7720:~> java -version > > java version "1.8.0_152" > > Java(TM) SE Runtime Environment (build 1.8.0_152-b16) > > Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) > > chuck@Dell7720:~> > > > > ANT VERSION: > > > > chuck@Dell7720:~> ant -version > > Apache Ant(TM) version 1.9.9 compiled on October 28 2017 > > chuck@Dell7720:~> > > > > > > > > MESSAGE WHERE BUILD FAILS: > > > > > > compile: > > > > jar-prep: > > > > jar: > > [jarwithmoduleattributes] Building jar: > > /downloads/netbeans_9/nbbuild/netbeans/websvccommon/modules/ > > org-netbeans-modules-websvc-saas-api.jar > > [nbmerge] Failed to build target: all-websvc.saas.api > > > > BUILD FAILED > > /downloads/netbeans_9/nbbuild/build.xml:480: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/build.xml:475: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/build.xml:522: The following error > occurred > > while executing this line: > > /downloads/netbeans_9/nbbuild/templates/common.xml:252: Could not find > > default manifest: /org/apache/tools/ant/defaultManifest.mf > > > > Total time: 3 minutes 19 seconds > > chuck@Dell7720:/downloads/netbeans_9> > > >
Re: info requested regarding build fail
Following information as requested. I can provide any other of the Ant output anybody wants to see if it will help (it scrolls way too fast to get a clue). But I seem to be the only one not experiencing success so I've contented myself to use the binaries others produce. LINK TO SOURCES I USED: https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta-rc2/incubating-netbeans-java-9.0-beta-source.zip MY JAVA VERSION INFO: chuck@Dell7720:~> java -version java version "1.8.0_152" Java(TM) SE Runtime Environment (build 1.8.0_152-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) chuck@Dell7720:~> ANT VERSION: chuck@Dell7720:~> ant -version Apache Ant(TM) version 1.9.9 compiled on October 28 2017 chuck@Dell7720:~> MESSAGE WHERE BUILD FAILS: compile: jar-prep: jar: [jarwithmoduleattributes] Building jar: /downloads/netbeans_9/nbbuild/netbeans/websvccommon/modules/org-netbeans-modules-websvc-saas-api.jar [nbmerge] Failed to build target: all-websvc.saas.api BUILD FAILED /downloads/netbeans_9/nbbuild/build.xml:480: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:475: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/build.xml:522: The following error occurred while executing this line: /downloads/netbeans_9/nbbuild/templates/common.xml:252: Could not find default manifest: /org/apache/tools/ant/defaultManifest.mf Total time: 3 minutes 19 seconds chuck@Dell7720:/downloads/netbeans_9>
Re: NB 178 of 2018.01.14
I followed the directions you've provided @ https://github.com/apache/incubator-netbeans/blob/master/README.md Unzip the file. Run Ant. -- running 1.9.9 and openSUSE's Tumbleweed version 1.9.9-8.2 is installed My last attempt ran about 5 minutes and failed. I have to go out for about 3 hours now but when I return I will get the source again (I deleted it) and run Ant on it. I will then post the output (there will be a lot of it) on google drive and anybody who wishes can look through it. Later On Fri, Jan 19, 2018 at 9:33 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > So describe in detail why youâre not able to build the source so someone > can help. > > Gj > > On Friday, January 19, 2018, Chuck Davis wrote: > > > Results of trying the nbm. > > > > I uninstalled JShell. > > Tried to install the downloaded one but NB complained JShell was already > > installed. > > Searched "available" and noted the one in plugins is dated today so > figured > > it was your update and installed it. > > JShell is not on the tools menu and reset is not on the edit menu. > > JShell status is not "activated" and I don't know how to "activate" it > > since the "activate" button is greyed out. > > > > So now NB (and I've since upgraded to 183 binary) has no JShell though it > > is installed but not active. > > > > Sorry to be such a pain in the butt. Probably user error. Everybody > else > > is building the source but I haven't been able to build it yet. I just > > live under a black cloud I think. > > > > P. S. That's an interesting "feature" of creating a sql.Date object! > But > > it DOES work Thanks. Makes me wonder how many other "gotchas" there > > may be lurking in JShell??? > > > > > > On Fri, Jan 19, 2018 at 8:59 AM, Svata Dedic > > wrote: > > > > > Dne 19.1.2018 v 17:46 Chuck Davis napsal(a): > > > > > >> > > >> jshell> System.out.println(new java.sql.Date(1415980523459). > > toString()); > > >> | Error: > > >> | integer number too large: 1415980523459 > > >> | System.out.println(new java.sql.Date(1415980523459).toString()); > > >> | ^ > > >> I think it's been a LONG time since we could create a date with an > > >> integer!! > > >> > > > > > > Add "l" suffix at the end of that big number. Without it, it parses to > > > integer literal and overflows. > > > > > > -S > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: dev-help@netbeans.incubator. > apache.org > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > >
Re: NB 178 of 2018.01.14
Results of trying the nbm. I uninstalled JShell. Tried to install the downloaded one but NB complained JShell was already installed. Searched "available" and noted the one in plugins is dated today so figured it was your update and installed it. JShell is not on the tools menu and reset is not on the edit menu. JShell status is not "activated" and I don't know how to "activate" it since the "activate" button is greyed out. So now NB (and I've since upgraded to 183 binary) has no JShell though it is installed but not active. Sorry to be such a pain in the butt. Probably user error. Everybody else is building the source but I haven't been able to build it yet. I just live under a black cloud I think. P. S. That's an interesting "feature" of creating a sql.Date object! But it DOES work Thanks. Makes me wonder how many other "gotchas" there may be lurking in JShell??? On Fri, Jan 19, 2018 at 8:59 AM, Svata Dedic wrote: > Dne 19.1.2018 v 17:46 Chuck Davis napsal(a): > >> >> jshell> System.out.println(new java.sql.Date(1415980523459).toString()); >> | Error: >> | integer number too large: 1415980523459 >> | System.out.println(new java.sql.Date(1415980523459).toString()); >> | ^ >> I think it's been a LONG time since we could create a date with an >> integer!! >> > > Add "l" suffix at the end of that big number. Without it, it parses to > integer literal and overflows. > > -S > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: NB 178 of 2018.01.14
Hi Svata:
After NB failed I did try the command line. You're going to get a kick out
of this! I store all my dates as a long in the database and I wanted to
know what one was so I copied it and pasted into JShell:
chuck@localhost:~> jshell
| Welcome to JShell -- Version 9.0.1
| For an introduction type: /help intro
jshell> import java.sql.*;
jshell> System.out.println(new java.sql.Date(1415980523459).toString());
| Error:
| integer number too large: 1415980523459
| System.out.println(new java.sql.Date(1415980523459).toString());
| ^
jshell>
I think it's been a LONG time since we could create a date with an
integer!!
Will try your nbm soon.
Thanks.
On Fri, Jan 19, 2018 at 6:19 AM, Svata Dedic
wrote:
> Hi,
>
> thanks a lot for the reminder. I've updated https://issues.apache.org/jira
> /browse/NETBEANS-133 with a convenience NBM for testing. Make sure that
> jshell JDK tool works on your setup; just launch jshell from commandline
> and execute e.g. System.err.println("Hello"); which should launch the user
> code VM.
>
> -Svata
>
> Dne 18.1.2018 v 05:38 Chuck Davis napsal(a):
>
> Using binary build as referenced..
>>
>> I wanted to use JShell so tried to open it and received the following:
>>
>>
>> Could not initialize JShell: Launching JShell execution engine threw:
>> Failed remote launch: java.util.concurrent.TimeoutException @
>> com.sun.jdi.CommandLineLaunch (defaults: home=/usr/java/jdk-9.0.1,
>> options=, main=, suspend=true, quote=", vmexec=java) --
>> {home=home=/usr/java/latest, options=options=-classpath
>> /sata2/Downloads/NetbeansRC2/netbeans/java/modules/ext/nb-mo
>> d-jshell-probe.jar:,
>> main=main=org.netbeans.lib.jshell.agent.AgentWorker 44793,
>> suspend=suspend=true, quote=quote=", vmexec=vmexec=java}
>> | caused by: Failed remote launch: java.util.concurrent.TimeoutEx
>> ception
>> @ com.sun.jdi.CommandLineLaunch (defaults: home=/usr/java/jdk-9.0.1,
>> options=, main=, suspend=true, quote=", vmexec=java) --
>> {home=home=/usr/java/latest, options=options=-classpath
>> /sata2/Downloads/NetbeansRC2/netbeans/java/modules/ext/nb-mo
>> d-jshell-probe.jar:,
>> main=main=org.netbeans.lib.jshell.agent.AgentWorker 44793,
>> suspend=suspend=true, quote=quote=", vmexec=vmexec=java}
>> | caused by: null
>>
>> Running on Linux with Oracle jdk9. I see similar reported previously
>> related to Mac @ NETBEANS-133. My host is defined as follows:
>>
>> 127.0.0.1localhost
>>
>> # special IPv6 addresses
>> ::1 localhost ipv6-localhost ipv6-loopback
>>
>> Does anybody recognize what I've screwed up? Does this need to be
>> reported
>> again?
>>
>> Thanks for any pointers.
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: NB 178 of 2018.01.14
Using binary build as referenced..
I wanted to use JShell so tried to open it and received the following:
Could not initialize JShell: Launching JShell execution engine threw:
Failed remote launch: java.util.concurrent.TimeoutException @
com.sun.jdi.CommandLineLaunch (defaults: home=/usr/java/jdk-9.0.1,
options=, main=, suspend=true, quote=", vmexec=java) --
{home=home=/usr/java/latest, options=options=-classpath
/sata2/Downloads/NetbeansRC2/netbeans/java/modules/ext/nb-mod-jshell-probe.jar:,
main=main=org.netbeans.lib.jshell.agent.AgentWorker 44793,
suspend=suspend=true, quote=quote=", vmexec=vmexec=java}
| caused by: Failed remote launch: java.util.concurrent.TimeoutException
@ com.sun.jdi.CommandLineLaunch (defaults: home=/usr/java/jdk-9.0.1,
options=, main=, suspend=true, quote=", vmexec=java) --
{home=home=/usr/java/latest, options=options=-classpath
/sata2/Downloads/NetbeansRC2/netbeans/java/modules/ext/nb-mod-jshell-probe.jar:,
main=main=org.netbeans.lib.jshell.agent.AgentWorker 44793,
suspend=suspend=true, quote=quote=", vmexec=vmexec=java}
| caused by: null
Running on Linux with Oracle jdk9. I see similar reported previously
related to Mac @ NETBEANS-133. My host is defined as follows:
127.0.0.1localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
Does anybody recognize what I've screwed up? Does this need to be reported
again?
Thanks for any pointers.
Re: Build failed - linux
Thanks for the explanation. May try it again soon though there's not a lot of motivation since I haven't experienced a hickup yet. Looking forward to FCS. And, by the way, thanks to you and all the others who have been working so hard to get the move to Apache accomplished. I don't often feel I have anything valuable to contribute to the list but I read it religiously and have been following the progressso thanks to you Geertjan and all others working so diligently. I'm using the 12/26 build and it's a GREAT start. On Tue, Jan 2, 2018 at 11:51 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Well, it depends which ZIP file you mean, but probably you downloaded > the ZIP that simply contains the binary -- i.e., after unzipping, you > have the installation directory and you just startup the NetBeans > binary in the bin folder, as always. > > Gj > > On Tue, Jan 2, 2018 at 8:50 PM, Chuck Davis wrote: > > Oh, that might explain why it didn't build!! đ I thought it was the > > source tarball. Didin't see anything that indicated differently. At > least > > I have it working and it's working well so far. > > > > On Tue, Jan 2, 2018 at 11:47 AM, Geertjan Wielenga < > > geertjan.wiele...@googlemail.com> wrote: > > > >> The ZIP file will not build, it is not supposed to build, it is > >> already built -- all you need to do is start it up/ > >> > >> Gj > >> > >> On Tue, Jan 2, 2018 at 8:43 PM, Chuck Davis wrote: > >> > Gilberto: > >> > > >> > Last week I got my courage up to try to build NB9. I first downloaded > >> the > >> > zip file from github. It would not build -- failed miserably. > >> > > >> > Then I tried the instructions for cloning/building with NB8.2 and it > >> worked > >> > flawlessly. I've been using it since working on a JavaFX project with > >> jdk > >> > 9 and it's working flawlessly so far. I suggest you follow the NB8.2 > >> build > >> > instructions and get on the road to success with NB9. I also use a > brand > >> > of Linux as my development environment so I can assure you it works > fine > >> on > >> > Linux. > >> > > >> > > >> > > >> > > >> > > >> > On Tue, Jan 2, 2018 at 11:24 AM, Gilberto > wrote: > >> > > >> >> Hello everyone, happy new year!! > >> >> > >> >> I would like to resuscitate this post/discussion. Setting a new > machine > >> and > >> >> this problem came up again. It only occurs while using the openjdk > 1.8 > >> >> version. > >> >> I know the build activate the BUILD-OPENJFX because openjdk doesn't > >> bring > >> >> the javafx with it, but I don't understand why it download a very old > >> >> version of it (rt-f89b7dc932af)[1] > >> >> And as you can see it can't build by the newer java 8 versions. > >> >> > >> >> Regards, > >> >> > >> >> Gilberto > >> >> > >> >> [1] http://hg.openjdk.java.net/openjfx/8/master/rt/log?rev= > f89b7dc932af > >> >> > >> >> 2017-11-14 13:39 GMT-03:00 Gilberto : > >> >> > >> >> > Hi, > >> >> > > >> >> > I've just forked the netbeans repository on github and tried to > build > >> it > >> >> > but without success: > >> >> > > >> >> > -define-custom-javac-task: > >> >> >> > >> >> >> projectized.build-init: > >> >> >> > >> >> >> -check-openjfx: > >> >> >> > >> >> >> -build-openjfx: > >> >> >> [unzip] Expanding: /home/gilberto.andrade/tmp/ > >> >> >> incubator-netbeans/libs.javafx/external/openjfx-master-rt-8.zip > into > >> >> >> /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> >> >> javafx/build/openjfx-src > >> >> >> [javac] Compiling 2184 source files to > >> /home/gilberto.andrade/tmp/ > >> >> >> incubator-netbeans/libs.javafx/build/openjfx-classes > >> >> >>[repeat] /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> >> >> javafx/build/openjfx-src/rt-f89b7dc932af/modules/swing/ > >> >> &g
Re: Build failed - linux
Oh, that might explain why it didn't build!! đ I thought it was the source tarball. Didin't see anything that indicated differently. At least I have it working and it's working well so far. On Tue, Jan 2, 2018 at 11:47 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > The ZIP file will not build, it is not supposed to build, it is > already built -- all you need to do is start it up/ > > Gj > > On Tue, Jan 2, 2018 at 8:43 PM, Chuck Davis wrote: > > Gilberto: > > > > Last week I got my courage up to try to build NB9. I first downloaded > the > > zip file from github. It would not build -- failed miserably. > > > > Then I tried the instructions for cloning/building with NB8.2 and it > worked > > flawlessly. I've been using it since working on a JavaFX project with > jdk > > 9 and it's working flawlessly so far. I suggest you follow the NB8.2 > build > > instructions and get on the road to success with NB9. I also use a brand > > of Linux as my development environment so I can assure you it works fine > on > > Linux. > > > > > > > > > > > > On Tue, Jan 2, 2018 at 11:24 AM, Gilberto wrote: > > > >> Hello everyone, happy new year!! > >> > >> I would like to resuscitate this post/discussion. Setting a new machine > and > >> this problem came up again. It only occurs while using the openjdk 1.8 > >> version. > >> I know the build activate the BUILD-OPENJFX because openjdk doesn't > bring > >> the javafx with it, but I don't understand why it download a very old > >> version of it (rt-f89b7dc932af)[1] > >> And as you can see it can't build by the newer java 8 versions. > >> > >> Regards, > >> > >> Gilberto > >> > >> [1] http://hg.openjdk.java.net/openjfx/8/master/rt/log?rev=f89b7dc932af > >> > >> 2017-11-14 13:39 GMT-03:00 Gilberto : > >> > >> > Hi, > >> > > >> > I've just forked the netbeans repository on github and tried to build > it > >> > but without success: > >> > > >> > -define-custom-javac-task: > >> >> > >> >> projectized.build-init: > >> >> > >> >> -check-openjfx: > >> >> > >> >> -build-openjfx: > >> >> [unzip] Expanding: /home/gilberto.andrade/tmp/ > >> >> incubator-netbeans/libs.javafx/external/openjfx-master-rt-8.zip into > >> >> /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> >> javafx/build/openjfx-src > >> >> [javac] Compiling 2184 source files to > /home/gilberto.andrade/tmp/ > >> >> incubator-netbeans/libs.javafx/build/openjfx-classes > >> >>[repeat] /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> >> javafx/build/openjfx-src/rt-f89b7dc932af/modules/swing/ > >> >> src/main/java/javafx/embed/swing/JFXPanel.java:663: error: cannot > find > >> >> symbol > >> >>[repeat] newScaleFactor = ((SunGraphics2D)g). > >> >> surfaceData.getDefaultScale(); > >> >>[repeat] > >> >> ^ > >> >>[repeat] symbol: method getDefaultScale() > >> >>[repeat] location: variable surfaceData of type SurfaceData > >> >>[repeat] Note: Some input files use or override a deprecated API. > >> >>[repeat] Note: Recompile with -Xlint:deprecation for details. > >> >>[repeat] Note: Some input files use unchecked or unsafe > operations. > >> >>[repeat] Note: Recompile with -Xlint:unchecked for details. > >> >>[repeat] 1 error > >> >> [nbmerge] Failed to build target: all-libs.javafx > >> >> > >> >> BUILD FAILED > >> >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:436: > >> The > >> >> following error occurred while executing this line: > >> >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:431: > >> The > >> >> following error occurred while executing this line: > >> >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:466: > >> The > >> >> following error occurred while executing this line: > >> >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:449: > >> The > >> >> following error occurred while executing thi
Re: Build failed - linux
Gilberto: Last week I got my courage up to try to build NB9. I first downloaded the zip file from github. It would not build -- failed miserably. Then I tried the instructions for cloning/building with NB8.2 and it worked flawlessly. I've been using it since working on a JavaFX project with jdk 9 and it's working flawlessly so far. I suggest you follow the NB8.2 build instructions and get on the road to success with NB9. I also use a brand of Linux as my development environment so I can assure you it works fine on Linux. On Tue, Jan 2, 2018 at 11:24 AM, Gilberto wrote: > Hello everyone, happy new year!! > > I would like to resuscitate this post/discussion. Setting a new machine and > this problem came up again. It only occurs while using the openjdk 1.8 > version. > I know the build activate the BUILD-OPENJFX because openjdk doesn't bring > the javafx with it, but I don't understand why it download a very old > version of it (rt-f89b7dc932af)[1] > And as you can see it can't build by the newer java 8 versions. > > Regards, > > Gilberto > > [1] http://hg.openjdk.java.net/openjfx/8/master/rt/log?rev=f89b7dc932af > > 2017-11-14 13:39 GMT-03:00 Gilberto : > > > Hi, > > > > I've just forked the netbeans repository on github and tried to build it > > but without success: > > > > -define-custom-javac-task: > >> > >> projectized.build-init: > >> > >> -check-openjfx: > >> > >> -build-openjfx: > >> [unzip] Expanding: /home/gilberto.andrade/tmp/ > >> incubator-netbeans/libs.javafx/external/openjfx-master-rt-8.zip into > >> /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> javafx/build/openjfx-src > >> [javac] Compiling 2184 source files to /home/gilberto.andrade/tmp/ > >> incubator-netbeans/libs.javafx/build/openjfx-classes > >>[repeat] /home/gilberto.andrade/tmp/incubator-netbeans/libs. > >> javafx/build/openjfx-src/rt-f89b7dc932af/modules/swing/ > >> src/main/java/javafx/embed/swing/JFXPanel.java:663: error: cannot find > >> symbol > >>[repeat] newScaleFactor = ((SunGraphics2D)g). > >> surfaceData.getDefaultScale(); > >>[repeat] > >> ^ > >>[repeat] symbol: method getDefaultScale() > >>[repeat] location: variable surfaceData of type SurfaceData > >>[repeat] Note: Some input files use or override a deprecated API. > >>[repeat] Note: Recompile with -Xlint:deprecation for details. > >>[repeat] Note: Some input files use unchecked or unsafe operations. > >>[repeat] Note: Recompile with -Xlint:unchecked for details. > >>[repeat] 1 error > >> [nbmerge] Failed to build target: all-libs.javafx > >> > >> BUILD FAILED > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:436: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:431: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:466: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:449: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:431: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/nbbuild/build.xml:478: > The > >> following error occurred while executing this line: > >> /home/gilberto.andrade/tmp/incubator-netbeans/libs.javafx/build.xml:35: > >> Compile failed; see the compiler error output for details. > >> > >> Total time: 59 seconds > >> [13:31] gilberto.andrade@BEM-INF007:incubator-netbeans (master u=) $ > >> javac -version > >> javac 1.8.0_151 > >> [13:32] gilberto.andrade@BEM-INF007:incubator-netbeans (master u=) $ > cat > >> /etc/os-release > >> NAME="openSUSE Leap" > >> VERSION="42.3" > >> ID=opensuse > >> ID_LIKE="suse" > >> VERSION_ID="42.3" > >> PRETTY_NAME="openSUSE Leap 42.3" > >> ANSI_COLOR="0;32" > >> CPE_NAME="cpe:/o:opensuse:leap:42.3" > >> BUG_REPORT_URL="https://bugs.opensuse.org"; > >> HOME_URL="https://www.opensuse.org/"; > >> [13:32] gilberto.andrade@BEM-INF007:incubator-netbeans (master u=) > >> > > > > I've tried ant and ant -Dcluster.config=platform . > > > > Regards, > > > > Gilberto > > >
Re: Possible new splashscreen for NetBeans 9.0
Also like the first one best. Big improvement over so-called modern "flat" / "material" in my opinion! On Fri, Jul 7, 2017 at 11:09 PM, Siddhesh Rane wrote: > Hi, > I might be a bit late here but the topic is of importance to me. I > personally don't want netbeans to go down the windows metro look just > because everyone else is doing it. > > To summarize people here can be divided into following opinion groups: > > * Those who like the old colorful and vibrant splash screens > > * Those who like "modern" flat, single color designs, mainly to promote > netbeans as modern > > * Those who want it to be "netbeans" instead of "NetBeans", or the middle > ground of "Netbeans" > > * Those that want the Apache feather > > Based on these constraints I have come up with some splash screens at > https://github.com/SiddheshRane/apache-netbeans-9.0-spash/ > > I'm fully in favour of crowd sourcing designs and the community voting for > it. > > I feel more emphasis must be placed on netbeans being an apache project > rather than some cosmetic changes to indicate modernity. > > Regards > Siddhesh Rane
Re: AW: Possible new splashscreen for NetBeans 9.0
+1 So-called "flat" or "material" design is so last century -- right out of the 80's. On Thu, Jun 29, 2017 at 10:41 AM, Glenn Holmer wrote: > On 06/28/2017 04:38 AM, Christian Lenz wrote: > > Sure, I forgot it, sry. > > Here is the link: https://drive.google.com/open?id= > 0B5EDo2BFcCwXRndEZzlYTTNWWGM > Hate 'em. The NetBeans splash images have always been artful and > inventive. Don't go with the "modern" "flat" look just because designers > are telling us it's fashionable. We aren't using 4.77MHz PCs any more, > it's OK to use a nice-looking image. > > -- > Glenn Holmer (Linux registered user #16682) > "After the vintage season came the aftermath -- and Cenbe." >
