You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Chuck Davis <cj...@gmail.com> on 2018/04/01 16:16:37 UTC
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: The Red Sea
Posted by Chuck Davis <cj...@gmail.com>.
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 <ni...@gmail.com> 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
Posted by Tim Boudreau <ni...@gmail.com>.
Performance wise you're definitely better off building once before opening
- scanning class files is much faster than sources.
-Tim
On Sun, Apr 1, 2018 at 12:16 PM Chuck Davis <cj...@gmail.com> wrote:
> 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.
>
--
http://timboudreau.com
Re: The Red Sea
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Great! Yes, would be excellent to all work on the site together and add
what we feel is missing.
Gj
On Mon, Apr 2, 2018 at 5:28 PM, Chuck Davis <cj...@gmail.com> wrote:
> 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.wielenga@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
Posted by Chuck Davis <cj...@gmail.com>.
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.wielenga@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
Posted by Geertjan Wielenga <ge...@googlemail.com>.
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.
Gj
On Monday, April 2, 2018, Chuck Davis <cj...@gmail.com> wrote:
> 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.wielenga@googlemail.com> wrote:
>
> > On Monday, April 2, 2018, Chuck Davis <cj...@gmail.com> 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
Posted by Chuck Davis <cj...@gmail.com>.
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.wielenga@googlemail.com> wrote:
> On Monday, April 2, 2018, Chuck Davis <cj...@gmail.com> 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
Posted by Geertjan Wielenga <ge...@googlemail.com>.
On Monday, April 2, 2018, Chuck Davis <cj...@gmail.com> 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
Posted by Chuck Davis <cj...@gmail.com>.
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
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hey Chuck,
Am Sonntag, den 01.04.2018, 09:16 -0700 schrieb Chuck Davis:
> articipate/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.
You don't need all projects (in fact it just distracts from the thinks
you want to work on). Open the projects you need (most times these are
one or two modules).
> I'm no Git ninja but I
> thought the master branch in Git was gold code.
Run a priming build (run ant in the checked out codebase). This will
build the necessary tools/utilities.
> Anyway, is this the expected outcome? Why are projects in "master" branch
> when they won't compile and build?
They do compile - that is what the jenkins + travis-ci jobs take care
of:
https://builds.apache.org/job/incubator-netbeans-linux/
https://travis-ci.org/apache/incubator-netbeans
HTH
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@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