I had a v. quick skim through the NB CSS parser code, and at first glance
it appears that there might be two problems:
1) The parser doesn't seem to support custom attributes (those starting --
e.g. --blue)
2) The parser doesn't seem to support the @supports Conditional "at rule"
If you would be
hi
In a spring boot project, I use bootstrap 4.
In netbeans in bootstrap.min.js it complain about css error
@supports (flex-wrap: wrap) { }
Unexpected token LPAREN found
Unexpected token WS found
Unexpected token RPAREN found
@supports not (flex-wrap: wrap) { }
Unexpected token NOT found
Just "gradle" should be fine.
Gj
On Mon, Feb 11, 2019 at 4:00 PM Peter Steele wrote:
> Yes sure, I'll try and consolidate all my feedback in to one jira issue.
> Are there any specific tags required in the Jira to flag it as a new
> gradle issue?
>
> On Mon, 11 Feb 2019, 14:38 Geertjan
New build equals the new builds with the new gradle functionality built in
rather than the gradle plugin. You sent another email previously asking for
testers and I have been testing and providing feedback.
To avoid making the other email trail too large I started a separate email
trail with some
Yes, these are completely different supports for Gradle in Apache NetBeans.
Can you explain in detail what is missing, ideally via an issue, so that it
can be added?
Yes, feedback is great, an issue with full description will help Laszlo and
others working on this support to understand what is
I don't really understand the context -- what is "the new gradle build",
for example? Do note that the Gradle support that is in the Apache NetBeans
GitHub is different to the Gradle plugin -- i.e., this is a long story, but
the point is that if you've been using the external Gradle plugin by
