Re: Compile on Save in web applications no longer works for NB > 11.0
My memory failed me, it's not a dialog, but a notification: https://lists.apache.org/thread.html/r3743d8d20e8760be2c91da7c236382a63d60358aca4415ba5743b7a3%40%3Cusers.netbeans.apache.org%3E I believe it's not installed by default because it wasn't donated (and won't be apparently) to Apache, and also because some users report issues caused by it when not running on JDK 8: https://lists.apache.org/thread.html/r3743d8d20e8760be2c91da7c236382a63d60358aca4415ba5743b7a3%40%3Cusers.netbeans.apache.org%3E Here's an overview of nb-javac https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac What I gather from the mailing list is that Netbeans is clearly moving away from nb-javac. What I don't understand is if it's also moving away from CoS and "Copy Static Resources" or maybe implement it in a more maintainable way (like, only for Maven/not-JDK8 users) I personally run netbeans 11.3 on OpenJDK 11.0.7 and my ant web project is compiled with that same JDK using --source 8, and haven't encountered any issues. Out of curiosity can I know what type of project, JDK version, and source level you are using? On Tue, May 5, 2020 at 10:02 PM Juan Algaba wrote: > > I'm on 11.3, ant-based web app, and do have CoS. > Make sure nb-javac plugin is installed in Plugins -> Installed -> > Search nb-javac > NB should offer you to install it, but IIRC it may not if you open an > existing project, if that's the case try creating a new java web > project to see if it triggers that dialog. > > > On Tue, May 5, 2020 at 7:27 PM Brett Ryan wrote: > > > > Hi all, I've been wanting to switch off of NB 11.0 for some time, however; > > the one thing that is stopping me is CoS is not working for web > > applications. > > > > Since moving from 11.0 the Build > Compile > Compile On Save is now greyed > > out. > > > > Run > "Deploy on Save" is enabled but appears to do nothin, as is "Copy > > Static Resources". > > > > > > > -- > -Juan Algaba -- -Juan Algaba - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Compile on Save in web applications no longer works for NB > 11.0
I'm on 11.3, ant-based web app, and do have CoS. Make sure nb-javac plugin is installed in Plugins -> Installed -> Search nb-javac NB should offer you to install it, but IIRC it may not if you open an existing project, if that's the case try creating a new java web project to see if it triggers that dialog. On Tue, May 5, 2020 at 7:27 PM Brett Ryan wrote: > > Hi all, I've been wanting to switch off of NB 11.0 for some time, however; > the one thing that is stopping me is CoS is not working for web applications. > > Since moving from 11.0 the Build > Compile > Compile On Save is now greyed > out. > > Run > "Deploy on Save" is enabled but appears to do nothin, as is "Copy > Static Resources". > > -- -Juan Algaba - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Compile on Save in web applications no longer works for NB > 11.0
Hi all, I've been wanting to switch off of NB 11.0 for some time, however; the one thing that is stopping me is CoS is not working for web applications. Since moving from 11.0 the Build > Compile > Compile On Save is now greyed out. Run > "Deploy on Save" is enabled but appears to do nothin, as is "Copy Static Resources".
Re: Changing comment character
I think I see your problem now :) Within your /* */ comment block, you
have a #{} block. Dart Sass will still try and perform interpolation on a
#{} block within a /* */ comment block, but not on a line comment //
https://sass-lang.com/documentation/syntax/comments
You should only need to // comment any blocks that contain #{}. Your
solution of creating a custom macro in Netbeans to do // comments is
probably the best workaround :)
CC'ing to the NB mailing list so we have this for future reference if it
comes up again...
Have an awesome day!
P
On Tue, May 5, 2020 at 10:14 AM letrollpoilu
wrote:
> Hi!
>
> Thanks a lot for your help, this really touches me :)
>
> The thing is that sometimes I got bugs in my sass code, so I want to
> comment parts/blocks to see where the issue is. Or simply comment old code
> and keep it there
> So I use Netbeans CTRL+SHFT+C to comment.
> But this is commenting with /**/ and this is still being compiled even
> though this is later stripped on a compressed mode (I always compile in
> compressed mode).
> So Dart Sass is giving me a compiling error because some buggy code
> commented with /**/ was compiled even in compressed mode...
>
> The best would be that CTRL+SHIT+C in .scss files would comment with //
> Just like for .sh files it comments with #
>
> So I would like to change the default way of commenting (actually the
> symbol) for .scss files.
> I figured out that this is not easy and I don't even know if I can look
> deeply into a config file and manually change a setting.
> I don't want to create a module and so on
>
> For now I created custom macros that are adding // to a line so that I can
> quickly comment blocks of code with // instead of the default /**/
>
> For example you can in the following example test1 works but not test2.
>
> //.test1 {
> //width: (#{$undefinedvar1} + 3em);
> //}
>
> /*.test2 {
> width: (#{$undefinedvar2} + 3em);
> } */
>
>
> As it is sometimes quite annoying to manually comment with // and that
> CTRL+SHIT+C really did save me hours in my life, I wanted to know if there
> was anyway to configure it :)
>
> --
> I don't have -J-Dnb.sass.libsass=true in my netbeans.conf file but I'm
> only compiling with an external script. This way I can compile and send the
> files via ssh directly. I'm using the module RunMyScript to start a .sh
> script compiling sass here is an extract:
>
> cd '[...]/sources/themes/[...]'
> echo "Compiling [...] scss..."
>
> [...]/dart-sass/sass scss/main_frontend.scss css/frontend.css
> --style=compressed
>
> echo ""
> echo "Sending to server..."
> scp css/* [...]@[...]:[...]/css
>
> ---
>
> I really thank you for your time, I really appreciate it, it's great to be
> able to talk to someone about those kind of issues :)
>
> Have a nice day !
>
>
>
>
>
>
>
> On 04/05/2020 22:08, Pete Whelpton wrote:
>
> Hi!
>
> Sorry to hear you are having problems. When you say you are having
> errors, do you mean a) Netbeans highlights errors in the compiled CSS file
> b) the Dart Sass compiler throws errors or c) the compiled CSS is invalid?
>
> Can you provide examples of the errors? If a), then it is most likely
> because the CSS grammar in Netbeans is not totally up-to-date. The grammar
> file also include Sass (scss) and Less grammar so is a total monster.
>
> if b) or c) then when Netbeans compiles a .scss file, all it does is pass
> the file to the Sass pre-compiler you specify in Netbeans options.
> According to Dart-Sass, " If a multi-line comment is written somewhere that
> a statement is allowed, it’s compiled to a CSS comment "
>
> If I create a file:
> @mixin test {
> /*color:red;
> font-size: #{var}*10;*/
> color:blue;
> }
>
> p {
> @include test;
> }
>
> This will compile to:
> p {
> /*color:red;
> font-size: var*10;*/
> color: blue;
> }
>
> As per Dart-Sass documentation, it compiles the comments to CSS comments
> (whether I compile via Netbeans or directly at the Command Line). If you
> want to surpress the comments totally, you can use Dart Sass' Compress
> Mode. This will compile to:
> p{color:blue}/*# sourceMappingURL=TestSass.css.map */
>
> Here's how to do it:
>
> 1) Make sure you have Netbeans configured to use a libsass
> implementation. Open /etc/netbeans.conf in a text editor and make sure
> -J-Dnb.sass.libsass=true
>
> is in your netbeans_default_options
>
> 2) Launch Netbeans. Open Menu->Tools->Options->HTML/JavaScript and make
> sure Sass path points to your dart-sass execuatble (e.g. sass.bat on
> Windows)
>
> 3) Tell your project to add the Compressed mode flag when calling
> dart-sass. Right click on your Project Node->Properties->CSS Preprocessors
> and in Compiler Options add:
> --style=compressed
>
> Next time your .scss compiles, in the Output window you should see the
> parameter pass to the Dart-Sass executable like
unsubscribe
unsubscribe - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: C++ compiler gone weird, flags errors
I'm pretty sure there was no C++ release from NetBeans in the past week. It
was a fluke on your machine.
--emi
On Mon, May 4, 2020 at 9:17 PM Brenden Towey wrote:
>
> And thank you to whoever released the new C++ patch for Netbeans this
> morning. The errors have disappeared and all seems to be working. :-)
>
> Brenden
>
>
> Forwarded Message
> Subject: C++ compiler gone weird, flags errors
> Date: Tue, 28 Apr 2020 08:36:46 -0700
> From: Brenden Towey
> To: users@netbeans.apache.org
>
> Hi folks, I wonder if I could get some help with an issue I'm having. I
> have NetBeans 11.1 and the C++ module installed for Cygwin. I think at
> some point I updated my Cygwin installation (using the standard install
> tool for Cygwin) and now NetBeans reports errors everywhere.
>
> For example, this code example with errors marked as comments:
>
> #include // cannot find include file
> #include // cannot find include file
>
> using namespace std; // Unable to resolve identifier std
>
> /*
> *
> */
> int main(int argc, char** argv) {
>cout << "Hello world."; // Unable to resolve identifier cout
>return 0;
> }
>
>
> The thing is the code compiles and runs just fine. It's just the editor
> window that is getting all of these errors. Help? What would I look for
> to tell the editor to resolve these errors when the compiler is working
> just fine?
>
> Thanks!
>
>
>
