[jira] [Comment Edited] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174426#comment-17174426
]
Pete Whelpton edited comment on NETBEANS-4559 at 8/10/20, 4:17 PM:
---
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code:java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects
[~jgauravgupta] can you offer any help? Can the MicroActionsProvider be
registered for only Payara Micro Projects...
was (Author: peedeeboy):
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code:java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects
[~jgauravgupta] can you offer any help?
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: ProjectPropertiesActionRun.png,
> ProjectPropertiesActionRun.png, ProjectPropertiesRun.png,
> PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip,
> image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png,
> messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174426#comment-17174426
]
Pete Whelpton edited comment on NETBEANS-4559 at 8/10/20, 4:16 PM:
---
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code:java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects
[~jgauravgupta] can you offer any help?
was (Author: peedeeboy):
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code::java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects
[~jgauravgupta] can you offer any help?
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: ProjectPropertiesActionRun.png,
> ProjectPropertiesActionRun.png, ProjectPropertiesRun.png,
> PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip,
> image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png,
> messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174426#comment-17174426
]
Pete Whelpton commented on NETBEANS-4559:
-
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code::java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects
[~jgauravgupta] can you offer any help?
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: ProjectPropertiesActionRun.png,
> ProjectPropertiesActionRun.png, ProjectPropertiesRun.png,
> PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip,
> image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png,
> messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[ https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173934#comment-17173934 ] Pete Whelpton commented on NETBEANS-4559: - Glad to hear that workaround works for you! Now we need to figure out which commit between NB 8.2 and NB 12.0 introduced this bug so we can fix it :) > Web Project Properties Dialog fails to save Relative URL > > > Key: NETBEANS-4559 > URL: https://issues.apache.org/jira/browse/NETBEANS-4559 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Bernard >Priority: Critical > Attachments: ProjectPropertiesActionRun.png, > ProjectPropertiesActionRun.png, ProjectPropertiesRun.png, > PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip, > image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png, > messages.log > > > Please see attached images and project. > In the project properties, there is a field "Relative URL" for the page to > load relative to the context path. > If I enter it and confirm the dialog, then after re-opening the dialog again, > the value is lost. > > The project is from > [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/] > - just adapted to run under NetBeans. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[ https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173802#comment-17173802 ] Pete Whelpton edited comment on NETBEANS-4559 at 8/9/20, 10:55 AM: --- Quick note: tested with a clean install of Netbeans 8.2, and that has the: netbeans.deploy=true set against the Run action on a fresh Maven Web Application project, so it would seem a commit since NB came over to Apache has introduced this bug. Time for more digging... !image-2020-08-09-11-54-50-908.png! was (Author: peedeeboy): Quick note: tested with a clean install of Netbeans 8.2, and that has the: netbeans.deploy=true set against the Run action on a fresh Maven Web Application project, so it would seem a commit since NB came over to Apache has introduced this bug. Time for more digging... !image-2020-08-09-11-54-16-915.png! > Web Project Properties Dialog fails to save Relative URL > > > Key: NETBEANS-4559 > URL: https://issues.apache.org/jira/browse/NETBEANS-4559 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Bernard >Priority: Critical > Attachments: ProjectPropertiesActionRun.png, > ProjectPropertiesActionRun.png, ProjectPropertiesRun.png, > PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip, > image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png, > messages.log > > > Please see attached images and project. > In the project properties, there is a field "Relative URL" for the page to > load relative to the context path. > If I enter it and confirm the dialog, then after re-opening the dialog again, > the value is lost. > > The project is from > [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/] > - just adapted to run under NetBeans. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[ https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173802#comment-17173802 ] Pete Whelpton commented on NETBEANS-4559: - Quick note: tested with a clean install of Netbeans 8.2, and that has the: netbeans.deploy=true set against the Run action on a fresh Maven Web Application project, so it would seem a commit since NB came over to Apache has introduced this bug. Time for more digging... !image-2020-08-09-11-54-16-915.png! > Web Project Properties Dialog fails to save Relative URL > > > Key: NETBEANS-4559 > URL: https://issues.apache.org/jira/browse/NETBEANS-4559 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Bernard >Priority: Critical > Attachments: ProjectPropertiesActionRun.png, > ProjectPropertiesActionRun.png, ProjectPropertiesRun.png, > PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip, > image-2020-08-07-15-48-32-635.png, messages.log > > > Please see attached images and project. > In the project properties, there is a field "Relative URL" for the page to > load relative to the context path. > If I enter it and confirm the dialog, then after re-opening the dialog again, > the value is lost. > > The project is from > [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/] > - just adapted to run under NetBeans. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173774#comment-17173774
]
Pete Whelpton commented on NETBEANS-4559:
-
Hi [~bht] . Apologies, I wasn't making myself clear.
I had a look at the NB source code, and it seems like there is a bug. The
*Relative URL* will only get saved if *Action -> Run Project* has the property:
{{netbeans.deploy=true}}
I think this should get set by default when a new Maven project is created.
However, at the moment that doesn't seem to be happening and I haven't found a
commit in the Netbeans history since the project moved to Apache that looks
like it would have changed/broken this.
In the meantime, you should be able to workaround your issue by manually adding
the property:
netbeans.deploy=true
to the Run Action and click OK. Then go back into the project properties and
setting the Relative URL should now correctly save the value (it also gets
saved as a property in the Run Actions).
Let us know if that works!
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: ProjectPropertiesActionRun.png,
> ProjectPropertiesActionRun.png, ProjectPropertiesRun.png,
> PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip,
> image-2020-08-07-15-48-32-635.png, messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173180#comment-17173180
]
Pete Whelpton edited comment on NETBEANS-4559 at 8/7/20, 3:04 PM:
--
{{[~bht] - what happens if you try *Project Properties -> Actions -> Run
project*}}
{{And add netbeans.deploy=true to the Properties, as per below and click OK?}}
Then go back into Project Properties and try to set the Relative URL
!image-2020-08-07-15-48-32-635.png!
was (Author: peedeeboy):
{{[~bht] - what happens if you try *Project Properties -> Actions -> Run
project*}}
{{And add netbeans.deploy=true to the Properties, as per below?}}
!image-2020-08-07-15-48-32-635.png!
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: PropertiesBefore.png, PropertiesBeforeAfter.png,
> WebSocketMovieTheater.zip, image-2020-08-07-15-48-32-635.png, messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173180#comment-17173180
]
Pete Whelpton commented on NETBEANS-4559:
-
{{[~bht] - what happens if you try *Project Properties -> Actions -> Run
project*}}
{{And add netbeans.deploy=true to the Properties, as per below?}}
!image-2020-08-07-15-48-32-635.png!
> Web Project Properties Dialog fails to save Relative URL
>
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.3
>Reporter: Bernard
>Priority: Critical
> Attachments: PropertiesBefore.png, PropertiesBeforeAfter.png,
> WebSocketMovieTheater.zip, image-2020-08-07-15-48-32-635.png, messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4559) Web Project Properties Dialog fails to save Relative URL
[ https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-4559: Attachment: image-2020-08-07-15-48-32-635.png > Web Project Properties Dialog fails to save Relative URL > > > Key: NETBEANS-4559 > URL: https://issues.apache.org/jira/browse/NETBEANS-4559 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Bernard >Priority: Critical > Attachments: PropertiesBefore.png, PropertiesBeforeAfter.png, > WebSocketMovieTheater.zip, image-2020-08-07-15-48-32-635.png, messages.log > > > Please see attached images and project. > In the project properties, there is a field "Relative URL" for the page to > load relative to the context path. > If I enter it and confirm the dialog, then after re-opening the dialog again, > the value is lost. > > The project is from > [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/] > - just adapted to run under NetBeans. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1456) Unsupported calc() function in CSS stylesheets
[
https://issues.apache.org/jira/browse/NETBEANS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173000#comment-17173000
]
Pete Whelpton commented on NETBEANS-1456:
-
I got somewhat stuck with this, as I can't figure out how to recursive grammar
for the calc(). The CSS specification states that implementers should handle
20 levels of depth (e.g. nested parenthesis), I tried to handle three without
using recursion, and performance STINKS.
It's not so noticeable on small .css files, but bootstrap.css (my go-to
performance benchmark) crawls.
I noticed that GrammarParser doesn't have any kind of caching, so it will try
and re-parse css psuedo-properties it has already parsed... I got a noticeable
performance against bootstrap.css by adding a "poor mans cache" of a hashmap to
the GrammarParser class.
However, looking at the profiler, it still seems like there are WAY too many
hashmap entries, and also GrammerParserTree$Entries and ResolvedProperties
objects and that probably needs to be sorted out.
I just don't think the css properties parser in NB was designed for multiple
properties sharing the same psuedo properties, and now our css properties
grammars are getting quite large/intertwined we see performance problems if we
add too much more complexity.
I've pushed where I am at here:
[https://github.com/peedeeboy/incubator-netbeans/tree/NETBEANS-1456] in case
anybody want to take a look from there, but I'm pretty stumped now on how to
take this further...
> Unsupported calc() function in CSS stylesheets
> --
>
> Key: NETBEANS-1456
> URL: https://issues.apache.org/jira/browse/NETBEANS-1456
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: css, easy
>
> The following code in CSS Editor shows as a warning:
> {code:java}
> .modal-dialog-centered {
> min-height: calc(100% - (0.5rem * 2));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3331) Deploy JavaEE8 applications to AWS
Pete Whelpton created NETBEANS-3331: --- Summary: Deploy JavaEE8 applications to AWS Key: NETBEANS-3331 URL: https://issues.apache.org/jira/browse/NETBEANS-3331 Project: NetBeans Issue Type: Improvement Components: javaee - Web Project Reporter: Pete Whelpton Now that we have JavaEE8 support in NetBeans, it should be possible to deploy JavaEE8 applications to AWS Elastic Beanstalk (currently the suitable container is running GlassFish 5) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3029) Configure a Selenium server on services tab
[
https://issues.apache.org/jira/browse/NETBEANS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933618#comment-16933618
]
Pete Whelpton commented on NETBEANS-3029:
-
I think Netbeans Selenium support was written for Selenium 2.x ?
Are you using Selenium 3.x? If you try using the
selenium-server-standalone-2.53.1.jar does it work?
> Configure a Selenium server on services tab
> ---
>
> Key: NETBEANS-3029
> URL: https://issues.apache.org/jira/browse/NETBEANS-3029
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - Code
>Affects Versions: 11.0
>Reporter: Rodrigo Teixeira Andreotti
>Priority: Minor
>
> When I try to add a new selenium server the server is not started and the IDE
> throws the exception below:
>
> {noformat}
> ---
> >Log Session: Monday, August 26, 2019 at 9:21:04 AM Brasilia Standard Time
> >System Info:
> Product Version = Apache NetBeans IDE 11.0 (Build
> incubator-netbeans-release-404-on-20190319)
> Operating System= Windows 10 version 10.0 running on amd64
> Java; VM; Vendor= 12.0.2; Java HotSpot(TM) 64-Bit Server VM
> 12.0.2+10; Oracle Corporation
> Runtime = Java(TM) SE Runtime Environment 12.0.2+10
> Java Home = C:\Program Files\Java\jdk-12.0.2
> System Locale; Encoding = pt_BR (nb); Cp1252
> Home Directory = D:\Users\Apartamento
> Current Directory = C:\Netbeans\bin
> User Directory = D:\Users\Apartamento\AppData\Roaming\NetBeans\11.0
> Cache Directory =
> D:\Users\Apartamento\AppData\Local\NetBeans\Cache\11.0
> Installation= C:\Netbeans\nb
> C:\Netbeans\ergonomics
> C:\Netbeans\ide
> C:\Netbeans\extide
> C:\Netbeans\java
> C:\Netbeans\apisupport
> C:\Netbeans\webcommon
> C:\Netbeans\websvccommon
> C:\Netbeans\enterprise
> C:\Netbeans\profiler
> C:\Netbeans\php
> C:\Netbeans\harness
> C:\Netbeans\groovy
> C:\Netbeans\javafx
> C:\Netbeans\platform
> Boot & Ext. Classpath =
> Application Classpath =
> C:\Netbeans\platform\lib\boot.jar;C:\Netbeans\platform\lib\org-openide-modules.jar;C:\Netbeans\platform\lib\org-openide-util-lookup.jar;C:\Netbeans\platform\lib\org-openide-util-ui.jar;C:\Netbeans\platform\lib\org-openide-util.jar
> Startup Classpath =
> C:\Netbeans\platform\core\asm-all-5.0.1.jar;C:\Netbeans\platform\core\core-base.jar;C:\Netbeans\platform\core\core.jar;C:\Netbeans\platform\core\org-netbeans-libs-asm.jar;C:\Netbeans\platform\core\org-openide-filesystems-compat8.jar;C:\Netbeans\platform\core\org-openide-filesystems.jar;C:\Netbeans\nb\core\org-netbeans-upgrader.jar;C:\Netbeans\nb\core\locale\core_nb.jar
> ---
> INFO [org.netbeans.modules.netbinox]: Install area set to file:/C:/Netbeans/
> WARNING [org.netbeans.core.modules]: the modules
> [org.netbeans.modules.java.editor.lib, org.netbeans.modules.xml.text] use
> org.netbeans.modules.editor.deprecated.pre65formatting which is deprecated.
> WARNING [org.netbeans.core.modules]: the modules
> [org.netbeans.modules.ide.kit, org.netbeans.modules.xml.text] use
> org.netbeans.modules.editor.structure which is deprecated.
> WARNING [org.netbeans.core.modules]: the modules
> [org.netbeans.modules.java.hints] use
> org.netbeans.modules.java.hints.legacy.spi which is deprecated: Use Java
> Hints SPI (org.netbeans.spi.java.hints) instead.
> WARNING [org.openide.filesystems.Ordering]: Not all children in
> Services/MIMEResolver/ marked with the position attribute:
> [org-netbeans-modules-gradle-GradleDataObject-Extension.xml], but some are:
> [org-openide-loaders-DataLoaderPool$InstanceLoaderSystem-Extension.xml,
> org-netbeans-core-startup-layers-SystemFileSystem-Extension.xml,
> org-netbeans-modules-java-JavaDataObject-Extension.xml,
> org-netbeans-modules-java-ClassDataObject-Extension.xml,
> org-netbeans-modules-image-ImageDataObject-serialVersionUID-Extension.xml,
> org-netbeans-modules-image-ImageDataObject-IMAGE_ICON_BASE-Extension.xml,
> org-netbeans-modules-image-ImageDataObject-openSupport-Extension.xml,
> org-netbeans-modules-image-ImageDataObject-printSupport-Extension.xml,
> org-netbeans-modules-properties-PropertiesDataObject-Extension.xml,
>
[jira] [Commented] (NETBEANS-581) Could not find an option named "cache-location".
[ https://issues.apache.org/jira/browse/NETBEANS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933528#comment-16933528 ] Pete Whelpton commented on NETBEANS-581: Netbeans SASS support was written for the original Ruby SASS. Modern SASS implementations (Dart SASS et al) are based on libsass. There is very limited/incomplete support for libsass already in Netbeans (command line flags are NOT supported - but it should compile). To implement the workaround: 1) Open your netbeans.conf file (/etc/netbeans.conf in the NB installation folder) 2) Add the following to the netbeans_default_options parameter: -J-Dnb.sass.libsass=true 3) Launch Netbeans, Tools -> Options -> HTML5/JS -> CSS PreProcessors and configure it to point to your libsass implementation (e.g. the sass.bat file in your dart-sass installation folder) > Could not find an option named "cache-location". > > > Key: NETBEANS-581 > URL: https://issues.apache.org/jira/browse/NETBEANS-581 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Preprocessors (SASS, LESS, ...) >Reporter: Bo Andersen >Priority: Minor > > When using the internal sass configuration, it calls the sass compiler with > the --cache-location command. It seems that this is not part of the current > sass compiler anymore. > > Sass error: > Could not find an option named "cache-location". > > I am using this release of sass compiler: > https://github.com/sass/dart-sass/releases/tag/1.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-588) Sass installed via Chocolatey not compiling
[
https://issues.apache.org/jira/browse/NETBEANS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933527#comment-16933527
]
Pete Whelpton commented on NETBEANS-588:
Netbeans SASS support was written for the original Ruby SASS. Modern SASS
implementations (Dart SASS et al) are based on libsass.
There is very limited/incomplete support for libsass already in Netbeans
(command line flags are NOT supported - but it should compile). To implement
the workaround:
1) Open your netbeans.conf file (/etc/netbeans.conf in the NB installation
folder)
2) Add the following to the netbeans_default_options parameter:
-J-Dnb.sass.libsass=true
3) Launch Netbeans, Tools -> Options -> HTML5/JS -> CSS PreProcessors and
configure it to point to your libsass implementation (e.g. the sass.bat file in
your dart-sass installation folder)
> Sass installed via Chocolatey not compiling
> ---
>
> Key: NETBEANS-588
> URL: https://issues.apache.org/jira/browse/NETBEANS-588
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 8.2
>Reporter: Óscar
>Priority: Major
>
> I installed Sass via Chocolatey and get this error in the Netbeans console:
> {color:#ff}"C:\ProgramData\chocolatey\lib\sass\tools\sass.bat"
> "-cache-location"
> "C:\Users\oxk4r\AppData\Local\NetBeans\Cache\8.2\sass-compiler" "debug-info"
> "-style" "compact" "C:\xampp\htdocs\SASS_01\scss\style.scss"
> "C:\xampp\htdocs\SASS_01\css\style.css" {color}
> {color:#ff}Could not find an option named "cache-location".{color}
> And no *.css file is generated at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2347) Could not find an option named "cache-location"
[ https://issues.apache.org/jira/browse/NETBEANS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933526#comment-16933526 ] Pete Whelpton commented on NETBEANS-2347: - Netbeans SASS support was written for the original Ruby SASS. Modern SASS implementations (Dart SASS et al) are based on libsass. There is very limited/incomplete support for libsass already in Netbeans (command line flags are NOT supported - but it should compile). To implement the workaround: 1) Open your netbeans.conf file (/etc/netbeans.conf in the NB installation folder) 2) Add the following to the netbeans_default_options parameter: -J-Dnb.sass.libsass=true 3) Launch Netbeans, Tools -> Options -> HTML5/JS -> CSS PreProcessors and configure it to point to your libsass implementation (e.g. the sass.bat file in your dart-sass installation folder) > Could not find an option named "cache-location" > --- > > Key: NETBEANS-2347 > URL: https://issues.apache.org/jira/browse/NETBEANS-2347 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Preprocessors (SASS, LESS, ...) >Affects Versions: 10.0, 11.0 > Environment: OS: Windows 10 > SOFTWARE VERSION: Apache Netbeans 10 >Reporter: ala >Priority: Critical > Labels: easyfix, usability > Fix For: Next > > > "C:\Users\Ala\AppData\Local\Yarn\bin\sass.cmd" "--cache-location" > "C:\Users\Ala\AppData\Local\NetBeans\Cache\10.0\sass-compiler" "--debug-info" > "C:\laragon\www\Pr\scss\stylesheet.scss" > "C:\laragon\www\Pr\css\stylesheet.css" > Could not find an option named "cache-location". > Usage: sass [output.css] > sass : : -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2347) Could not find an option named "cache-location"
[ https://issues.apache.org/jira/browse/NETBEANS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933522#comment-16933522 ] Pete Whelpton commented on NETBEANS-2347: - Duplicate of NETBEANS-581. > Could not find an option named "cache-location" > --- > > Key: NETBEANS-2347 > URL: https://issues.apache.org/jira/browse/NETBEANS-2347 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Preprocessors (SASS, LESS, ...) >Affects Versions: 10.0, 11.0 > Environment: OS: Windows 10 > SOFTWARE VERSION: Apache Netbeans 10 >Reporter: ala >Priority: Critical > Labels: easyfix, usability > Fix For: Next > > > "C:\Users\Ala\AppData\Local\Yarn\bin\sass.cmd" "--cache-location" > "C:\Users\Ala\AppData\Local\NetBeans\Cache\10.0\sass-compiler" "--debug-info" > "C:\laragon\www\Pr\scss\stylesheet.scss" > "C:\laragon\www\Pr\css\stylesheet.css" > Could not find an option named "cache-location". > Usage: sass [output.css] > sass : : -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3005) Error en Spring web.xml
[ https://issues.apache.org/jira/browse/NETBEANS-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927071#comment-16927071 ] Pete Whelpton commented on NETBEANS-3005: - Duplicate of NETBEANS-2875. > Error en Spring web.xml > --- > > Key: NETBEANS-3005 > URL: https://issues.apache.org/jira/browse/NETBEANS-3005 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 11.0, 11.1 >Reporter: Daniel Rodrigo Anccasi Huayllani >Priority: Major > Labels: patch > Fix For: 11.0, 11.1 > > Attachments: Error netbeans.PNG > > Original Estimate: 24h > Time Spent: 168h > Remaining Estimate: 0h > > # Cree un proyecto web vacío de categoría java maven > # Agregue al proyecto web el framework Spring 4.x > # Sale error en web.xml, es notorio ya que tiene un aspa de color rojo en la > parte inferior > El error menciona lo siguiente: cvc-elt.1: No se ha encontrado la declaración > del elemento 'web-app'. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-3005) Error en Spring web.xml
[ https://issues.apache.org/jira/browse/NETBEANS-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-3005. - Fix Version/s: (was: 11.1) (was: 11.0) Next Resolution: Fixed This was due to the Enterprise Catalog being broken. It will be fixed in 11.2 > Error en Spring web.xml > --- > > Key: NETBEANS-3005 > URL: https://issues.apache.org/jira/browse/NETBEANS-3005 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 11.0, 11.1 >Reporter: Daniel Rodrigo Anccasi Huayllani >Priority: Major > Labels: patch > Fix For: Next > > Attachments: Error netbeans.PNG > > Original Estimate: 24h > Time Spent: 168h > Remaining Estimate: 0h > > # Cree un proyecto web vacío de categoría java maven > # Agregue al proyecto web el framework Spring 4.x > # Sale error en web.xml, es notorio ya que tiene un aspa de color rojo en la > parte inferior > El error menciona lo siguiente: cvc-elt.1: No se ha encontrado la declaración > del elemento 'web-app'. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-2400. - Fix Version/s: Next Resolution: Fixed > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region, pull-request-available > Fix For: Next > > Time Spent: 6h > Remaining Estimate: 0h > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2888) Project Context Path problem for Java Maven Web Application
[ https://issues.apache.org/jira/browse/NETBEANS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926907#comment-16926907 ] Pete Whelpton commented on NETBEANS-2888: - I believe that all Netbeans ever did when changing the context path in a Maven project was: Check the version of GlassFish the Project is using: If < GF3.1, create a sun-web.xml file in WEB-INF with the context path setting If >= GF3.1, create a glassfish-web.xml file in WEB-INF with the context path setting However, the glassfish-web.xml templates weren't in the donation from Oracle, so Netbeans can't create the glassfish-web.xml file when the context path is changed. See Geertjan's comments on the related issue of the missing templates: https://issues.apache.org/jira/browse/NETBEANS-2951 There is a secondary issue, in that for GlassFish 5.0 and 5.1, Netbeans thinks they should have a sun-web.xml file, not a glassfish-web.xml. I suspect there is a hardcoded check somewhere that isn't taking the existance of GF > 4.x into account that needs to be found / fixed. Hope that helps :) > Project Context Path problem for Java Maven Web Application > --- > > Key: NETBEANS-2888 > URL: https://issues.apache.org/jira/browse/NETBEANS-2888 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven, apisupport - Project, javaee - > Maven, javaee - Web Project >Affects Versions: 11.0, 11.1 > Environment: Netbeans 11.1 with Java 8 or 11 (Windows 10 64 bit), > Eclipse GlassFish 5.1 or Payara app server for project app deployment >Reporter: SergeyT >Assignee: Josh Juneau >Priority: Blocker > Attachments: ctx_path_webapp.png > > > There is no possibility to save/change the Project property -> Run for Java > Maven Web Application: Context Path (see attach) > The context path in NB11.1 is always the same as the name of the project and > cannot be changed. > > Environment: JDK 64-Bit Server VM 8 or 11 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2951) There is no way to create glassfish-web.xml
[ https://issues.apache.org/jira/browse/NETBEANS-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926895#comment-16926895 ] Pete Whelpton commented on NETBEANS-2951: - The "Deployment Configuration for this project not found error" occurs only with later versions of GlassFish (5.0 & 5.1) - it is because NB is expecting/checking these versions of GlassFish to have a sun-web.xml file rather than a glassfish-web.xml file. GlassFish post 3.1 should use Glassfish-web.xml - I think there is probably a hard coded value somewhere that only went upto GF 4.x that I need to track down and fix for GlassFish 5.x > There is no way to create glassfish-web.xml > --- > > Key: NETBEANS-2951 > URL: https://issues.apache.org/jira/browse/NETBEANS-2951 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.0, 11.1 > Environment: JDK 64-Bit Server VM 8 or 11 (MS Windows 10 64 bit) >Reporter: SergeyT >Priority: Critical > Attachments: glassfish-web.png, ide_log.png, nb_about.png, > no_file.png, payara_is_ok.png > > > There is no way to create glassfish-web.xml file in Maven Web Application > project (attach) > After creation, this file does not appear in the project tree > > Environment: JDK 64-Bit Server VM 8 or 11 -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2875) Enterprise Catalog references broken
[
https://issues.apache.org/jira/browse/NETBEANS-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-2875.
-
Fix Version/s: Next
Resolution: Fixed
Merged via
[{{f1603f0}}|https://github.com/apache/netbeans/commit/f1603f06ea1033bec08e90c2a45585d8e1412c6f]
> Enterprise Catalog references broken
>
>
> Key: NETBEANS-2875
> URL: https://issues.apache.org/jira/browse/NETBEANS-2875
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
>Reporter: Pete Whelpton
>Priority: Minor
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> As reported by Thomas Kellerer on the Dev mailing list, XML files validated
> by schema in the Enterprise Catalog are failing to validate again in 11.1
> I believe this is because my commit to fix this (d172c20), was accidentally
> regressed.
>
> *EnterpriseCatalog.java*
> {{private static final String RESOURCE_PATH =
> "nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N}}
>
> got regressed back to:
> {{private static final String RESOURCE_PATH =
> "nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/"; //NO18N}}
>
> but the XSD files don't exist in that location anymore, hence the validation
> errors.
>
> *Steps to replicate:*
> 1) Create a new Maven Web Application project. Choose JavaEE7
> 2) Create a Standard Deployment Descriptor file (web.xml)
> 3) Netbeans will show a red X next to the web.xml node in Project explorer
> 4) Right clicking in the Editor for the web.xml file and choosing "Validate"
> will result in an XML validation error
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2951) There is no way to create glassfish-web.xml
[ https://issues.apache.org/jira/browse/NETBEANS-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907665#comment-16907665 ] Pete Whelpton commented on NETBEANS-2951: - Was able to to get NB to generate a glassfish-web.xml in a quick-and-dirty fix by: 1) Copying the /glassfish.eecommon/src/org/netbeans/modules/glassfish/eecommon/api/ddetemplates folder from the NB8.2 sources to my local dev branch sources 2) Uncommenting the lines that register the files in the /glassfish.eecommon/src/org/netbeans/modules/glassfish/eecommon/layer.xml So to move this forwards, we need to know the licensing status of those files... Also, after creating the glassfish-web.xml file, NB will show an error dialog "Deployment Configuration for this project not found. Deployment descriptor version could not be set properly." This is thrown due to the call to GlassfishConfiguration.getConfiguration() in SunDDWizardIterator.java (122) returning null - so this needs further investigation as it doesn't happen in NB8.2 > There is no way to create glassfish-web.xml > --- > > Key: NETBEANS-2951 > URL: https://issues.apache.org/jira/browse/NETBEANS-2951 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.0, 11.1 > Environment: JDK 64-Bit Server VM 8 or 11 (MS Windows 10 64 bit) >Reporter: SergeyT >Priority: Critical > Attachments: glassfish-web.png, ide_log.png, nb_about.png, > no_file.png, payara_is_ok.png > > > There is no way to create glassfish-web.xml file in Maven Web Application > project (attach) > After creation, this file does not appear in the project tree > > Environment: JDK 64-Bit Server VM 8 or 11 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2951) There is no way to create glassfish-web.xml
[ https://issues.apache.org/jira/browse/NETBEANS-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905635#comment-16905635 ] Pete Whelpton commented on NETBEANS-2951: - Had a very quick look. Here is what I think is going on: It seems like the getSunDDFromProjectsModuleVersion() method of org.netbeans.modules.glassfish.eecommon.api.Utils is responsible for retrieving the template file (e.g. glassfish-web.xml). It is trying to find the files in org-netbeans-modules-glassfish-eecommon-ddtemplates The folder exists in NB8.2: [http://hg.netbeans.org/core-main/file/tip/glassfish.eecommon/src/org/netbeans/modules/glassfish/eecommon/api/ddtemplates] We don't have this folder in NB11.x: [https://github.com/apache/netbeans/tree/master/enterprise/glassfish.eecommon/src/org/netbeans/modules/glassfish/eecommon/api] I think these files were possibly removed as part of the donation due to licensing issues? > There is no way to create glassfish-web.xml > --- > > Key: NETBEANS-2951 > URL: https://issues.apache.org/jira/browse/NETBEANS-2951 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.0, 11.1 > Environment: JDK 64-Bit Server VM 8 or 11 (MS Windows 10 64 bit) >Reporter: SergeyT >Priority: Critical > Attachments: glassfish-web.png, ide_log.png, nb_about.png, > no_file.png, payara_is_ok.png > > > There is no way to create glassfish-web.xml file in Maven Web Application > project (attach) > After creation, this file does not appear in the project tree > > Environment: JDK 64-Bit Server VM 8 or 11 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2882) Unrelated Payara icon in toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899601#comment-16899601 ] Pete Whelpton commented on NETBEANS-2882: - Hi Ghader :) Click *View* -> *Toolbars* -> *Customize*. Now drag the *Payara Reload* icon from the top toolbar onto the *Customize Toolbars* dialog that popped up (if you are doing it correctly, your cursor icon will change to a rubbish bin..) The icon will disappear from your toolbar :) > Unrelated Payara icon in toolbar > > > Key: NETBEANS-2882 > URL: https://issues.apache.org/jira/browse/NETBEANS-2882 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.1 > Environment: OS: win 10, JDK: 1.8.0_212 >Reporter: Ghader Arkani >Assignee: Gaurav Gupta >Priority: Minor > Attachments: pic.jpg > > > There is a Payara icon in my toolbar and I don't know how to remove it. I > don't use any Payara related project. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2875) Enterprise Catalog references broken
Pete Whelpton created NETBEANS-2875:
---
Summary: Enterprise Catalog references broken
Key: NETBEANS-2875
URL: https://issues.apache.org/jira/browse/NETBEANS-2875
Project: NetBeans
Issue Type: Bug
Affects Versions: 11.1
Reporter: Pete Whelpton
As reported by Thomas Kellerer on the Dev mailing list, XML files validated by
schema in the Enterprise Catalog are failing to validate again in 11.1
I believe this is because my commit to fix this (d172c20), was accidentally
regressed.
*EnterpriseCatalog.java*
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N }}
got regressed back to:
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/"; //NO18N}}
but the XSD files don't exist in that location anymore, hence the validation
errors.
*Steps to replicate:*
1) Create a new Maven Web Application project. Choose JavaEE7
2) Create a Standard Deployment Descriptor file (web.xml)
3) Netbeans will show a red X next to the web.xml node in Project explorer
4) Right clicking in the Editor for the web.xml file and choosing "Validate"
will result in an XML validation error
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2875) Enterprise Catalog references broken
[
https://issues.apache.org/jira/browse/NETBEANS-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2875:
Description:
As reported by Thomas Kellerer on the Dev mailing list, XML files validated by
schema in the Enterprise Catalog are failing to validate again in 11.1
I believe this is because my commit to fix this (d172c20), was accidentally
regressed.
*EnterpriseCatalog.java*
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N}}
got regressed back to:
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/"; //NO18N}}
but the XSD files don't exist in that location anymore, hence the validation
errors.
*Steps to replicate:*
1) Create a new Maven Web Application project. Choose JavaEE7
2) Create a Standard Deployment Descriptor file (web.xml)
3) Netbeans will show a red X next to the web.xml node in Project explorer
4) Right clicking in the Editor for the web.xml file and choosing "Validate"
will result in an XML validation error
was:
As reported by Thomas Kellerer on the Dev mailing list, XML files validated by
schema in the Enterprise Catalog are failing to validate again in 11.1
I believe this is because my commit to fix this (d172c20), was accidentally
regressed.
*EnterpriseCatalog.java*
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N }}
got regressed back to:
{{private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/"; //NO18N}}
but the XSD files don't exist in that location anymore, hence the validation
errors.
*Steps to replicate:*
1) Create a new Maven Web Application project. Choose JavaEE7
2) Create a Standard Deployment Descriptor file (web.xml)
3) Netbeans will show a red X next to the web.xml node in Project explorer
4) Right clicking in the Editor for the web.xml file and choosing "Validate"
will result in an XML validation error
> Enterprise Catalog references broken
>
>
> Key: NETBEANS-2875
> URL: https://issues.apache.org/jira/browse/NETBEANS-2875
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
>Reporter: Pete Whelpton
>Priority: Minor
>
> As reported by Thomas Kellerer on the Dev mailing list, XML files validated
> by schema in the Enterprise Catalog are failing to validate again in 11.1
> I believe this is because my commit to fix this (d172c20), was accidentally
> regressed.
>
> *EnterpriseCatalog.java*
> {{private static final String RESOURCE_PATH =
> "nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N}}
>
> got regressed back to:
> {{private static final String RESOURCE_PATH =
> "nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/"; //NO18N}}
>
> but the XSD files don't exist in that location anymore, hence the validation
> errors.
>
> *Steps to replicate:*
> 1) Create a new Maven Web Application project. Choose JavaEE7
> 2) Create a Standard Deployment Descriptor file (web.xml)
> 3) Netbeans will show a red X next to the web.xml node in Project explorer
> 4) Right clicking in the Editor for the web.xml file and choosing "Validate"
> will result in an XML validation error
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2846) Escape symbol brokes SQL file highlighting
[
https://issues.apache.org/jira/browse/NETBEANS-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884647#comment-16884647
]
Pete Whelpton commented on NETBEANS-2846:
-
Which RDBMS are you using? MySQL?
For most RDBMS, single quotes are escaped with another single quote. E.g.
{{UPDATE test SET val='test '' test' WHERE id = 1;}}
should lex/parse correctly. I think escaping with \' is specific to MySQL (and
perhaps a few others), but escaping with '' is more common/portable?
> Escape symbol brokes SQL file highlighting
> --
>
> Key: NETBEANS-2846
> URL: https://issues.apache.org/jira/browse/NETBEANS-2846
> Project: NetBeans
> Issue Type: Bug
> Components: db - SQL Editor
>Affects Versions: 11.0
>Reporter: Lobzek
>Priority: Minor
> Attachments: Untitled.png
>
>
> Escape symbol ' brakes SQL file highlighting when using inside string value.
> SQL query for example:
> {code:java}
> UPDATE test SET val='Test \' test' WHERE id = 1;
> {code}
> See also attached screenshot
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2617) Redraw common icons in SVG
[ https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870601#comment-16870601 ] Pete Whelpton commented on NETBEANS-2617: - [^ide.editor.macros.ai] [^ide.seperator.breadcrumbs.ai] > Redraw common icons in SVG > -- > > Key: NETBEANS-2617 > URL: https://issues.apache.org/jira/browse/NETBEANS-2617 > Project: NetBeans > Issue Type: Improvement > Components: platform - Other >Affects Versions: 11.0 > Environment: Windows, Linux, and MacOS >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: ide.editor.bookmarks.ai, ide.editor.macros.ai, > ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style > example.png > > > Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans > icons with SVG versions, for improved appearance on Retina/HiDPI displays. > With some practice, it takes on average 30 minutes to create an SVG version > of a typical icon in Adobe Illustrator. See the attached illustration and > Illustrator template. The Illustrator template includes a few icons which > have already been converted. > In NETBEANS-2605, the following prioritized list of icons to convert was > produced: > https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html > By redrawing the most commonly seen icons first, we can get the greatest > "bang for the buck" in terms of improving NetBeans' appearance on HiDPI > displays. Note that in cases where an icon file has been copied around to > various places in the NetBeans codebase, only one of the paths is shown in > the list above. > See also the overview page for HiDPI improvements on > https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements > . > h2. Proposed Style Guide for Vectorized Icons > * Vector icons should be drawn in Adobe Illustrator. Each icon should be one > named artboard, sized to the correct size in pixels. See the attached > Illustrator template. (Adobe Illustrator comes with a free 7-day trial, after > which it's $35/month. If cost is a problem but you want to contribute your > time to draw icons, ask Eirik...) > * For each icon to be vectorized, place the old bitmap version of the icon in > the "Old Bitmap Icons" layer in Illustrator. You can then draw the vectorized > version on top. > * Since most of the existing NetBeans icons follow a quite consistent visual > style, and to simplify the job of creating new icons, it is best to keep the > shape of the new vectorized icons the same as in the old bitmap icons. For > instance, a rectangle of size 5x4px in the bitmap icon should probably become > a rectangle of 5x4px in the vector version. > * Keep the same general colors in vectorized icons as in the corresponding > old bitmap icons. (The color scheme is not too hard to change later, but we > should do this only once most of the IDE icons have been vectorized.) > * If the old bitmap icon is complex, it is fine to simplify it a bit when > drawing vectorized versions. > * Omit gradients, bevels, and unnecessary drop shadows. They take more time > to draw, and with "flat design", they are now out of fashion in any case. > * Use a stroke width of 1px around the main shapes in the icon, like in the > existing bitmap icons. The new icons should look consistent with the existing > bitmap icons, especially since we may see bitmap icons and vector icons > side-by-side for a long time. Within shapes, 0.5px strokes can be used for > finer details. > * The 1px strokes that outline the icon's shapes should typically be 33% > transparent black on top of the shape's background color, or of similar > darkness. See the examples in the attached "style example.png" file. > * Horizontal and vertical strokes must be aligned to the pixel grid. > * While it may sometimes be necessary to "outline" strokes for the purposes > of applying boolean operations (e.g. subtracting another shape from the > stroke only), strokes should be left as strokes whenever possible, as this > leads to smaller SVG files, and makes shapes within the icon easier to modify. > * For toolbar icons, which exist in both 16x16 and 24x24 sizes, base the > vector version on the smaller 16x16 one, which is sometimes simpler. (This is > already done in the prioritized icon list above.) > If you wish to contribute to this effort, comment here; Eirik will coordinate > to make sure multiple people are not working on the same icons. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[ https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2617: Attachment: ide.seperator.breadcrumbs.ai > Redraw common icons in SVG > -- > > Key: NETBEANS-2617 > URL: https://issues.apache.org/jira/browse/NETBEANS-2617 > Project: NetBeans > Issue Type: Improvement > Components: platform - Other >Affects Versions: 11.0 > Environment: Windows, Linux, and MacOS >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: ide.editor.bookmarks.ai, ide.editor.macros.ai, > ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style > example.png > > > Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans > icons with SVG versions, for improved appearance on Retina/HiDPI displays. > With some practice, it takes on average 30 minutes to create an SVG version > of a typical icon in Adobe Illustrator. See the attached illustration and > Illustrator template. The Illustrator template includes a few icons which > have already been converted. > In NETBEANS-2605, the following prioritized list of icons to convert was > produced: > https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html > By redrawing the most commonly seen icons first, we can get the greatest > "bang for the buck" in terms of improving NetBeans' appearance on HiDPI > displays. Note that in cases where an icon file has been copied around to > various places in the NetBeans codebase, only one of the paths is shown in > the list above. > See also the overview page for HiDPI improvements on > https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements > . > h2. Proposed Style Guide for Vectorized Icons > * Vector icons should be drawn in Adobe Illustrator. Each icon should be one > named artboard, sized to the correct size in pixels. See the attached > Illustrator template. (Adobe Illustrator comes with a free 7-day trial, after > which it's $35/month. If cost is a problem but you want to contribute your > time to draw icons, ask Eirik...) > * For each icon to be vectorized, place the old bitmap version of the icon in > the "Old Bitmap Icons" layer in Illustrator. You can then draw the vectorized > version on top. > * Since most of the existing NetBeans icons follow a quite consistent visual > style, and to simplify the job of creating new icons, it is best to keep the > shape of the new vectorized icons the same as in the old bitmap icons. For > instance, a rectangle of size 5x4px in the bitmap icon should probably become > a rectangle of 5x4px in the vector version. > * Keep the same general colors in vectorized icons as in the corresponding > old bitmap icons. (The color scheme is not too hard to change later, but we > should do this only once most of the IDE icons have been vectorized.) > * If the old bitmap icon is complex, it is fine to simplify it a bit when > drawing vectorized versions. > * Omit gradients, bevels, and unnecessary drop shadows. They take more time > to draw, and with "flat design", they are now out of fashion in any case. > * Use a stroke width of 1px around the main shapes in the icon, like in the > existing bitmap icons. The new icons should look consistent with the existing > bitmap icons, especially since we may see bitmap icons and vector icons > side-by-side for a long time. Within shapes, 0.5px strokes can be used for > finer details. > * The 1px strokes that outline the icon's shapes should typically be 33% > transparent black on top of the shape's background color, or of similar > darkness. See the examples in the attached "style example.png" file. > * Horizontal and vertical strokes must be aligned to the pixel grid. > * While it may sometimes be necessary to "outline" strokes for the purposes > of applying boolean operations (e.g. subtracting another shape from the > stroke only), strokes should be left as strokes whenever possible, as this > leads to smaller SVG files, and makes shapes within the icon easier to modify. > * For toolbar icons, which exist in both 16x16 and 24x24 sizes, base the > vector version on the smaller 16x16 one, which is sometimes simpler. (This is > already done in the prioritized icon list above.) > If you wish to contribute to this effort, comment here; Eirik will coordinate > to make sure multiple people are not working on the same icons. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit:
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[ https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2617: Attachment: ide.editor.macros.ai > Redraw common icons in SVG > -- > > Key: NETBEANS-2617 > URL: https://issues.apache.org/jira/browse/NETBEANS-2617 > Project: NetBeans > Issue Type: Improvement > Components: platform - Other >Affects Versions: 11.0 > Environment: Windows, Linux, and MacOS >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: ide.editor.bookmarks.ai, ide.editor.macros.ai, > ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style > example.png > > > Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans > icons with SVG versions, for improved appearance on Retina/HiDPI displays. > With some practice, it takes on average 30 minutes to create an SVG version > of a typical icon in Adobe Illustrator. See the attached illustration and > Illustrator template. The Illustrator template includes a few icons which > have already been converted. > In NETBEANS-2605, the following prioritized list of icons to convert was > produced: > https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html > By redrawing the most commonly seen icons first, we can get the greatest > "bang for the buck" in terms of improving NetBeans' appearance on HiDPI > displays. Note that in cases where an icon file has been copied around to > various places in the NetBeans codebase, only one of the paths is shown in > the list above. > See also the overview page for HiDPI improvements on > https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements > . > h2. Proposed Style Guide for Vectorized Icons > * Vector icons should be drawn in Adobe Illustrator. Each icon should be one > named artboard, sized to the correct size in pixels. See the attached > Illustrator template. (Adobe Illustrator comes with a free 7-day trial, after > which it's $35/month. If cost is a problem but you want to contribute your > time to draw icons, ask Eirik...) > * For each icon to be vectorized, place the old bitmap version of the icon in > the "Old Bitmap Icons" layer in Illustrator. You can then draw the vectorized > version on top. > * Since most of the existing NetBeans icons follow a quite consistent visual > style, and to simplify the job of creating new icons, it is best to keep the > shape of the new vectorized icons the same as in the old bitmap icons. For > instance, a rectangle of size 5x4px in the bitmap icon should probably become > a rectangle of 5x4px in the vector version. > * Keep the same general colors in vectorized icons as in the corresponding > old bitmap icons. (The color scheme is not too hard to change later, but we > should do this only once most of the IDE icons have been vectorized.) > * If the old bitmap icon is complex, it is fine to simplify it a bit when > drawing vectorized versions. > * Omit gradients, bevels, and unnecessary drop shadows. They take more time > to draw, and with "flat design", they are now out of fashion in any case. > * Use a stroke width of 1px around the main shapes in the icon, like in the > existing bitmap icons. The new icons should look consistent with the existing > bitmap icons, especially since we may see bitmap icons and vector icons > side-by-side for a long time. Within shapes, 0.5px strokes can be used for > finer details. > * The 1px strokes that outline the icon's shapes should typically be 33% > transparent black on top of the shape's background color, or of similar > darkness. See the examples in the attached "style example.png" file. > * Horizontal and vertical strokes must be aligned to the pixel grid. > * While it may sometimes be necessary to "outline" strokes for the purposes > of applying boolean operations (e.g. subtracting another shape from the > stroke only), strokes should be left as strokes whenever possible, as this > leads to smaller SVG files, and makes shapes within the icon easier to modify. > * For toolbar icons, which exist in both 16x16 and 24x24 sizes, base the > vector version on the smaller 16x16 one, which is sometimes simpler. (This is > already done in the prioritized icon list above.) > If you wish to contribute to this effort, comment here; Eirik will coordinate > to make sure multiple people are not working on the same icons. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit:
[jira] [Updated] (NETBEANS-2634) Unicode-range unexpected token PLUS found
[
https://issues.apache.org/jira/browse/NETBEANS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2634:
Labels: css (was: )
> Unicode-range unexpected token PLUS found
> -
>
> Key: NETBEANS-2634
> URL: https://issues.apache.org/jira/browse/NETBEANS-2634
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 11.0
>Reporter: Joshua Bakker
>Priority: Major
> Labels: css
> Attachments: bug_netbeans_css.png
>
>
> I hope this issue is correctly created. So, I'm using Apache NetBeans 11.0
> for my webdevelopment. When I see red lines, I want to go ahead and fix the
> code. However, in one .css file I see red lines even under correct code.
> For example, I have this CSS:
> {code:java}
> @font-face {
> font-family: 'Open Sans';
> font-style: normal;
> font-weight: 300;
> src: local('Open Sans Light'), local('OpenSans-Light'),
> url(https://fonts.gstatic.com/s/opensans/v16/mem5YaGs126MiZpBA-UN_r8OX-hpOqc.woff2)
> format('woff2');
> font-display: swap;
> unicode-range: U+0460-052F, U+1C80-1C88, U+20B4, U+2DE0-2DFF, U+A640-A69F,
> U+FE2E-FE2F;
> }
> {code}
> According to W3C CSS validator, the unicode-range line is correct. However,
> NetBeans puts a red line underneath it with the error (example of the error
> of the red line underneath the first +: "unexpected token PLUS found")
> As far as I know, this could be maybe because of NetBeans using a too low CSS
> version but I'm not 100% sure. See the attachment for a better view of what I
> mean.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2663) CSS3 parsing CSS with var() functionality
[
https://issues.apache.org/jira/browse/NETBEANS-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870204#comment-16870204
]
Pete Whelpton commented on NETBEANS-2663:
-
CSS variable support was added by [https://github.com/apache/netbeans/pull/1172]
Should be available in NB11.1 very soon - or you can try a nightly build if you
need this urgently...
> CSS3 parsing CSS with var() functionality
> -
>
> Key: NETBEANS-2663
> URL: https://issues.apache.org/jira/browse/NETBEANS-2663
> Project: NetBeans
> Issue Type: Improvement
> Components: web - CSS Editor
>Affects Versions: 11.0
> Environment: Windows 10, JDK 8, NetBeans 11.0
>Reporter: Vlad Palnik
>Priority: Minor
> Labels: features
>
> {{css file with the following code shows parse errors}}
>
>
> {code:java}
> :root {
> --first-color: #488cff;
> --second-color: #8c;
> }
> #firstParagraph {
> background-color: var(--first-color);
> color: var(--second-color);
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-1204) Make Wicket generated Web-Apps work
[ https://issues.apache.org/jira/browse/NETBEANS-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton closed NETBEANS-1204. --- Resolution: Not A Bug I submitted a fix to the Apache Wicket project. This will be fixed in Wicket 8.6.0, so I'm closing this ticket as Not A Bug. > Make Wicket generated Web-Apps work > --- > > Key: NETBEANS-1204 > URL: https://issues.apache.org/jira/browse/NETBEANS-1204 > Project: NetBeans > Issue Type: Improvement > Components: serverplugins - GlassFish >Affects Versions: 8.2 >Reporter: Peter Nabbefeld >Priority: Major > > Could not yet test with NB 9.0, so added only version 8.2. > Added Glassfish 5 as a Glassfish server type, but when I try to run my > project, I get the following error: > java.io.IOException: org.xml.sax.SAXParseExceptionpublicId: > [file:/opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd|file:///opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd]; > lineNumber: 8; columnNumber: 27; Deployment descriptor file WEB-INF/web.xml > in archive [PrivateCookingReceipes-1.0-SNAPSHOT]. TargetNamespace.1: > Namespace 'http://java.sun.com/xml/ns/javaee' wird erwartet, aber der > Ziel-Namespace des Schemadokuments ist '[http://xmlns.jcp.org/xml/ns/javaee'.] > Sorry for the German message. It says the target namespace of the web.xml > schema does not fit, obviously this is checked by the glassfish plugin > (expected 'http://java.sun.com/xml/ns/javaee' but found > '[http://xmlns.jcp.org/xml/ns/javaee'|http://xmlns.jcp.org/xml/ns/javaee'.]). > Probably it'd be sufficient to just test for both namespaces depending on > glassfish version. > > While I first thought it's a problem with the Glassfish version, it turns out > to be a problem with the web.xml generated by Wicket Quickstart. I replaced > the schema declaration with another one copied from a web.xml generated by > NetBeans, after this change I can start my web app. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863106#comment-16863106 ] Pete Whelpton edited comment on NETBEANS-2400 at 6/14/19 9:02 AM: -- I think the code changes are pretty straightforward and not much work. The dependency management, however, is a bit of a minefield - probably need some guidance from the NB gurus: e.g. should we a) update the org.apache.commons.codec & org.apache.commons.logging modules with newer versions of their .jars (and risk breaking other modules dependent on them) or b) break the dependency on those modules and have the Amazon SDK have its own version of those jars Also, the current Amazon SDK module in NB has the entire 1.2.1 Amazon SDK, however only around six of its packages are publicly exposed. The entire 1.11.x Amazon SDK jar is much, much bigger - around 400MB bigger, so which modules should we include? try to include all the packages in the current Amazon SDK (in case any platform apps out there are dependent on it) or just the ones publicly exposed (e.g. auth, Elastic Beanstalk, S3)? And if we include the all the SDK modules the match what we currently have, those will also come with their own dependencies... Plus, once that's agreed upon, I'd need someone to upload the binaries to OSUOSL for me :) was (Author: peedeeboy): I think the code changes are pretty straightforward and not much work. The dependency management, however, is a bit of a minefield - probably need some guidance from the NB gurus: e.g. should we a) update the org.apache.commons.codec & org.apache.commons.logging modules with newer versions of their .jars (and risk breaking other modules dependent on them) or b) break the dependency on those modules and have the Amazon SDK have its own version of those jars Also, the current Amazon SDK module in NB has the entire 1.2.1 Amazon SDK, however only around six of its packages are publicly exposed. The entire 1.11.x Amazon SDK jar is much, much bigger - around 400MB bigger, so which modules should we include? try to include all the packages in the current Amazon SDK (in case any platform apps out there are dependent on it) or just the ones publicly exposed (e.g. auth, Elastic Beanstalk, S3)? Plus, once that's agreed upon, I'd need someone to upload the binaries to OSUOSL for me :) > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863106#comment-16863106 ] Pete Whelpton edited comment on NETBEANS-2400 at 6/14/19 8:59 AM: -- I think the code changes are pretty straightforward and not much work. The dependency management, however, is a bit of a minefield - probably need some guidance from the NB gurus: e.g. should we a) update the org.apache.commons.codec & org.apache.commons.logging modules with newer versions of their .jars (and risk breaking other modules dependent on them) or b) break the dependency on those modules and have the Amazon SDK have its own version of those jars Also, the current Amazon SDK module in NB has the entire 1.2.1 Amazon SDK, however only around six of its packages are publicly exposed. The entire 1.11.x Amazon SDK jar is much, much bigger - around 400MB bigger, so which modules should we include? try to include all the packages in the current Amazon SDK (in case any platform apps out there are dependent on it) or just the ones publicly exposed (e.g. auth, Elastic Beanstalk, S3)? Plus, once that's agreed upon, I'd need someone to upload the binaries to OSUOSL for me :) was (Author: peedeeboy): I think the code changes are pretty straightforward and not much work. The dependency management, however, is a bit of a minefield - probably need some guidance from the NB gurus: e.g. should we a) update the org.apache.commons.codec & org.apache.commons.logging modules with newer versions of their .jars or b) break the dependency on those modules and have the Amazon SDK have its own version of those jars Also, the current Amazon SDK module in NB has the entire 1.2.1 Amazon SDK, however only around six of its packages are publicly exposed. The entire 1.11.x Amazon SDK jar is much, much bigger - around 400MB bigger, so which modules should we include? try to include all the packages in the current Amazon SDK (in case any platform apps out there are dependent on it) or just the ones publicly exposed (e.g. auth, Elastic Beanstalk, S3)? Plus, once that's agreed upon, I'd need someone to upload the binaries to OSUOSL for me :) > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863106#comment-16863106 ] Pete Whelpton commented on NETBEANS-2400: - I think the code changes are pretty straightforward and not much work. The dependency management, however, is a bit of a minefield - probably need some guidance from the NB gurus: e.g. should we a) update the org.apache.commons.codec & org.apache.commons.logging modules with newer versions of their .jars or b) break the dependency on those modules and have the Amazon SDK have its own version of those jars Also, the current Amazon SDK module in NB has the entire 1.2.1 Amazon SDK, however only around six of its packages are publicly exposed. The entire 1.11.x Amazon SDK jar is much, much bigger - around 400MB bigger, so which modules should we include? try to include all the packages in the current Amazon SDK (in case any platform apps out there are dependent on it) or just the ones publicly exposed (e.g. auth, Elastic Beanstalk, S3)? Plus, once that's agreed upon, I'd need someone to upload the binaries to OSUOSL for me :) > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862901#comment-16862901 ] Pete Whelpton edited comment on NETBEANS-2400 at 6/13/19 10:15 AM: --- So the crux of the failure is that the version of the AWS SDK that NB11.0 uses (1.2.1) doesn't support signing requests with the AWS SDK Sginature v4, which is needed for newer regions (Ohio, Central, Mumbai, Seoul, Frankfurt, London, Beijing) as described here: [https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html] To use the lasted v1 Amazon SDK module in NB would need to be updated to include the following libraries/dependencies: * aws-java-sdk-elasticbeanstalk-1.11.569 * aws-java-sdk-core-1.11.569 * commons-codec-1.10 * commons-logging-1.1.3 * httpclient-4.5.5 * httpcore-4.4.9 * ion-java-1.0.2 * jackson-annotations-2.6.0 * jackson-core-2.6.7 * jackson-databind-2.6.7.2 * jackson-dataformat-cbor-2.6.7 * jmespath-java-1.11.569 * joda-time-2.8.1 commons-codec is currently provided via the org.apache.commons.codec module, but it is an older version (1.3) commons-logging is currently provided by org.apache.commons.logging module, but it is an older version (1.1.1) was (Author: peedeeboy): So the crux of the failure is that the version of the AWS SDK that NB11.0 uses (1.2.1) doesn't support signing requests with the AWS SDK Sginature v4, which is needed for newer regions (Ohio, Central, Mumbai, Seoul, Frankfurt, London, Beijing) as described here: [https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html] The use the lasted v1 Amazon SDK module in NB would need to be updated to include the following libraries/dependencies: * aws-java-sdk-elasticbeanstalk-1.11.569 * aws-java-sdk-core-1.11.569 * commons-codec-1.10 * commons-logging-1.1.3 * httpclient-4.5.5 * httpcore-4.4.9 * ion-java-1.0.2 * jackson-annotations-2.6.0 * jackson-core-2.6.7 * jackson-databind-2.6.7.2 * jackson-dataformat-cbor-2.6.7 * jmespath-java-1.11.569 * joda-time-2.8.1 commons-codec is currently provided via the org.apache.commons.codec module, but it is an older version (1.3) commons-logging is currently provided by org.apache.commons.logging module, but it is an older version (1.1.1) > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862901#comment-16862901 ] Pete Whelpton commented on NETBEANS-2400: - So the crux of the failure is that the version of the AWS SDK that NB11.0 uses (1.2.1) doesn't support signing requests with the AWS SDK Sginature v4, which is needed for newer regions (Ohio, Central, Mumbai, Seoul, Frankfurt, London, Beijing) as described here: [https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html] The use the lasted v1 Amazon SDK module in NB would need to be updated to include the following libraries/dependencies: * aws-java-sdk-elasticbeanstalk-1.11.569 * aws-java-sdk-core-1.11.569 * commons-codec-1.10 * commons-logging-1.1.3 * httpclient-4.5.5 * httpcore-4.4.9 * ion-java-1.0.2 * jackson-annotations-2.6.0 * jackson-core-2.6.7 * jackson-databind-2.6.7.2 * jackson-dataformat-cbor-2.6.7 * jmespath-java-1.11.569 * joda-time-2.8.1 commons-codec is currently provided via the org.apache.commons.codec module, but it is an older version (1.3) commons-logging is currently provided by org.apache.commons.logging module, but it is an older version (1.1.1) > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1204) Make Wicket generated Web-Apps work
[
https://issues.apache.org/jira/browse/NETBEANS-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858713#comment-16858713
]
Pete Whelpton commented on NETBEANS-1204:
-
I think this is really a bug/oversight with the Wicket Quickstart Archetype.
If you compile the quickstart generated application and try to deploy to
GlassFish via the GlassFish admin GUI, you will get the same error:
{{Error occurred during deployment: Exception while deploying the app
[myproject-1.0-SNAPSHOT] : org.xml.sax.SAXParseExceptionpublicId:
file:/C:/apps/glassfish51/glassfish/lib/schemas/web-app_3_1.xsd; lineNumber:
26; columnNumber: 27; Deployment descriptor file WEB-INF/web.xml in archive
[myproject-1.0-SNAPSHOT]. TargetNamespace.1: Expecting namespace
'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema
document is 'http://xmlns.jcp.org/xml/ns/javaee'.. Please see server.log for
more details.}}
GlassFish appears to validate the web.xml before it will accept it. The
problem is that in the Wicket quickstart web.xml they have:
{{http://java.sun.com/xml/ns/javaee"}}
But as per [Java EE: XML Schemas for Java EE Deployment
Descriptors|[https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html]]:
{{All new schemas are in the [http://xmlns.jcp.org/xml/ns/javaee/] namespace.
Most older schemas remain in the [http://java.sun.com/xml/ns/javaee/]
namespace.}}
So any web.xml referencing web_app_3_1.xsd or web_app_4_0.xsd should be:
{{http://xmlns.jcp.org/xml/ns/javaee/]"}}
Making this simple change means GlassFish will accept the .war file for
deployment
> Make Wicket generated Web-Apps work
> ---
>
> Key: NETBEANS-1204
> URL: https://issues.apache.org/jira/browse/NETBEANS-1204
> Project: NetBeans
> Issue Type: Improvement
> Components: serverplugins - GlassFish
>Affects Versions: 8.2
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Could not yet test with NB 9.0, so added only version 8.2.
> Added Glassfish 5 as a Glassfish server type, but when I try to run my
> project, I get the following error:
> java.io.IOException: org.xml.sax.SAXParseExceptionpublicId:
> [file:/opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd|file:///opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd];
> lineNumber: 8; columnNumber: 27; Deployment descriptor file WEB-INF/web.xml
> in archive [PrivateCookingReceipes-1.0-SNAPSHOT]. TargetNamespace.1:
> Namespace 'http://java.sun.com/xml/ns/javaee' wird erwartet, aber der
> Ziel-Namespace des Schemadokuments ist '[http://xmlns.jcp.org/xml/ns/javaee'.]
> Sorry for the German message. It says the target namespace of the web.xml
> schema does not fit, obviously this is checked by the glassfish plugin
> (expected 'http://java.sun.com/xml/ns/javaee' but found
> '[http://xmlns.jcp.org/xml/ns/javaee'|http://xmlns.jcp.org/xml/ns/javaee'.]).
> Probably it'd be sufficient to just test for both namespaces depending on
> glassfish version.
>
> While I first thought it's a problem with the Glassfish version, it turns out
> to be a problem with the web.xml generated by Wicket Quickstart. I replaced
> the schema declaration with another one copied from a web.xml generated by
> NetBeans, after this change I can start my web app.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2306) Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text
[ https://issues.apache.org/jira/browse/NETBEANS-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-2306. - Resolution: Fixed Fix Version/s: Next Hopefully fixed by [https://github.com/apache/netbeans/pull/1282] > Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text > > > Key: NETBEANS-2306 > URL: https://issues.apache.org/jira/browse/NETBEANS-2306 > Project: NetBeans > Issue Type: Bug > Components: javaee - Code >Affects Versions: 11.0 >Reporter: Antonio Vieiro >Priority: Major > Labels: pull-request-available > Fix For: Next > > Attachments: netbeans-missing-resource-amazon.txt > > Time Spent: 40m > Remaining Estimate: 0h > > This is for NetBeans 11.0 vc4 running on OpenJDK8 on Linux. > Create a new JavaEE Application (ant based). Then choose to add a server and > select "Amazon Beanstalk" as a target. > An exception is thrown stating a missing resource (attached exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2398) Netbeans 11 + web.xml = Cannot find declaration of element 'web-app'
[
https://issues.apache.org/jira/browse/NETBEANS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-2398.
-
Resolution: Fixed
Fix Version/s: Next
Fixed by https://github.com/apache/netbeans/pull/1266
> Netbeans 11 + web.xml = Cannot find declaration of element 'web-app'
>
>
> Key: NETBEANS-2398
> URL: https://issues.apache.org/jira/browse/NETBEANS-2398
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 11.0
> Environment: Windows 10 64-Bit OpenJDK 11.0.2 (also tested with same
> results using Oracle JDK 8).
>Reporter: Ryan
>Priority: Major
> Fix For: Next
>
> Attachments: Screenshot.png
>
>
> I'm taking Netbeans 11 for a spin and now see my project web.xml file has red
> x in bottom corner of Projects window icon. Everything seems to work fine
> despite the validation error. If I open project in Netbeans 8.2 no issue.
> The hover (tooltip) message is:
> {quote}
> cvc-elt.1.a: Cannot find the declaration of element 'web-app'
>
> {quote}
> If I right click on web.xml file in Projects window and click Validate XML
> the error is displayed in the Output window along with:
> {quote}schema_reference.4: Failed to read schema document
> 'nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/web-app_3_1.xsd',
> because 1) could not find the document; 2) the document could not be read;
> 3) the root element of the document is not
> {quote}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2172) web.xml issue creating a webapp with java server faces
[
https://issues.apache.org/jira/browse/NETBEANS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-2172.
-
Resolution: Fixed
Fix Version/s: Next
Fixed by https://github.com/apache/netbeans/pull/1266
> web.xml issue creating a webapp with java server faces
> --
>
> Key: NETBEANS-2172
> URL: https://issues.apache.org/jira/browse/NETBEANS-2172
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 11.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-release-384-on-20190213)
> Java: 12; OpenJDK 64-Bit Server VM 12+32
> Runtime: OpenJDK Runtime Environment 12+32
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
>Reporter: Giuseppe Tino
>Priority: Major
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Steps to reproduce:
> # Create a new "Maven / Web Application" project:
> ** "Project Name": {{firstcup}}
> ** "Server": {{GlassFish Server 5.0}}
> ** "Java EE Version": {{Java EE 7 Web}}
> ** "Context Path": {{/firstcup}}
> # After the project is created, invoke pop-up menu on it's root node and
> select *Properties*.
> # Select the "Frameworks" category in the "Project Properties" manager.
> # Push the *Add...* button and choose "JavaServer Faces" framework.
> # In "Configuration" tab, set "JSF Servlet URL Pattern" to:
> {{/firstcupWeb/*}} and push *OK*.
> # Delete generated web pages.
> Expected result:
> * The project is created and no errors are displayed
> Actual result:
> * In the project panel the file Web pages > WEB-INF > web.xml is marked with
> a red x. On mouse hover the following message is shown "cvc-elt.1.a: Cannot
> find the declaration of element 'web-app'. "
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2306) Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text
[
https://issues.apache.org/jira/browse/NETBEANS-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854117#comment-16854117
]
Pete Whelpton edited comment on NETBEANS-2306 at 6/2/19 9:22 PM:
-
Came across this bug whilst looking into NETBEANS-2400
It is caused by this line:
AmazonJ2EEServerWizardComponent.envFullURLLabel.text=\ \
in
{{/enterprise/cloud.amazon/src/org/netbeans/modules/cloud/amazon/ui/serverplugin/Bundle.properties}}
The backslash causes the following line:
AmazonJ2EEServerWizardComponent.containerLabel.text=Container Type:
{{to be treated as the part of the value for envFullURLLabel.text}}
I'm not sure there is any reason that the \ \ value simply can't be removed?
That will enable the dialog to display without error.
was (Author: peedeeboy):
Came across this bug whilst looking into NETBEANS-2400
It is caused by this line:
{{AmazonJ2EEServerWizardComponent.envFullURLLabel.text=\ \}}
in
{{/enterprise/cloud.amazon/src/org/netbeans/modules/cloud/amazon/ui/serverplugin/Bundle.properties}}
{{The backslash causes the following line:
AmazonJ2EEServerWizardComponent.containerLabel.text=Container Type: }}
{{to be treated as the part of the value for envFullURLLabel.text}}
I'm not sure there is any reason that the \ \ value simply can't be removed?
That will enable the dialog to display without error.
> Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text
>
>
> Key: NETBEANS-2306
> URL: https://issues.apache.org/jira/browse/NETBEANS-2306
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Code
>Affects Versions: 11.0
>Reporter: Antonio Vieiro
>Priority: Major
> Attachments: netbeans-missing-resource-amazon.txt
>
>
> This is for NetBeans 11.0 vc4 running on OpenJDK8 on Linux.
> Create a new JavaEE Application (ant based). Then choose to add a server and
> select "Amazon Beanstalk" as a target.
> An exception is thrown stating a missing resource (attached exception).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2306) Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text
[
https://issues.apache.org/jira/browse/NETBEANS-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854117#comment-16854117
]
Pete Whelpton commented on NETBEANS-2306:
-
Came across this bug whilst looking into NETBEANS-2400
It is caused by this line:
{{AmazonJ2EEServerWizardComponent.envFullURLLabel.text=\ \}}
in
{{/enterprise/cloud.amazon/src/org/netbeans/modules/cloud/amazon/ui/serverplugin/Bundle.properties}}
{{The backslash causes the following line:
AmazonJ2EEServerWizardComponent.containerLabel.text=Container Type: }}
{{to be treated as the part of the value for envFullURLLabel.text}}
I'm not sure there is any reason that the \ \ value simply can't be removed?
That will enable the dialog to display without error.
> Missing resource AmazonJ2EEServerWizardComponent.containerLabel.text
>
>
> Key: NETBEANS-2306
> URL: https://issues.apache.org/jira/browse/NETBEANS-2306
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Code
>Affects Versions: 11.0
>Reporter: Antonio Vieiro
>Priority: Major
> Attachments: netbeans-missing-resource-amazon.txt
>
>
> This is for NetBeans 11.0 vc4 running on OpenJDK8 on Linux.
> Create a new JavaEE Application (ant based). Then choose to add a server and
> select "Amazon Beanstalk" as a target.
> An exception is thrown stating a missing resource (attached exception).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-39) No code completion in Jade files while typing
[ https://issues.apache.org/jira/browse/NETBEANS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-39. --- Resolution: Fixed Fix Version/s: Next Should be fixed by https://github.com/apache/netbeans/pull/1261 > No code completion in Jade files while typing > - > > Key: NETBEANS-39 > URL: https://issues.apache.org/jira/browse/NETBEANS-39 > Project: NetBeans > Issue Type: Bug > Components: javascript - Jade >Affects Versions: 8.2 >Reporter: Christian Lenz >Priority: Major > Labels: pull-request-available > Fix For: Next > > Attachments: jade-no-code-completion.gif > > Time Spent: 0.5h > Remaining Estimate: 0h > > As you can see it in my screencapture, there is no code completion while > typing. It only appears after using ctrl + space, but I don't have to use it > in other languages. It should appear right after hitting one character. Only > after using <, the code completion for html is comming up immediately. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2398) Netbeans 11 + web.xml = Cannot find declaration of element 'web-app'
[
https://issues.apache.org/jira/browse/NETBEANS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849076#comment-16849076
]
Pete Whelpton commented on NETBEANS-2398:
-
Should be / hopefully is fixed by:
[https://github.com/apache/netbeans/pull/1266]
> Netbeans 11 + web.xml = Cannot find declaration of element 'web-app'
>
>
> Key: NETBEANS-2398
> URL: https://issues.apache.org/jira/browse/NETBEANS-2398
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 11.0
> Environment: Windows 10 64-Bit OpenJDK 11.0.2 (also tested with same
> results using Oracle JDK 8).
>Reporter: Ryan
>Priority: Major
> Attachments: Screenshot.png
>
>
> I'm taking Netbeans 11 for a spin and now see my project web.xml file has red
> x in bottom corner of Projects window icon. Everything seems to work fine
> despite the validation error. If I open project in Netbeans 8.2 no issue.
> The hover (tooltip) message is:
> {quote}
> cvc-elt.1.a: Cannot find the declaration of element 'web-app'
>
> {quote}
> If I right click on web.xml file in Projects window and click Validate XML
> the error is displayed in the Output window along with:
> {quote}schema_reference.4: Failed to read schema document
> 'nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/web-app_3_1.xsd',
> because 1) could not find the document; 2) the document could not be read;
> 3) the root element of the document is not
> {quote}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2172) web.xml issue creating a webapp with java server faces
[
https://issues.apache.org/jira/browse/NETBEANS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849051#comment-16849051
]
Pete Whelpton commented on NETBEANS-2172:
-
Same root cause
> web.xml issue creating a webapp with java server faces
> --
>
> Key: NETBEANS-2172
> URL: https://issues.apache.org/jira/browse/NETBEANS-2172
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 11.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-release-384-on-20190213)
> Java: 12; OpenJDK 64-Bit Server VM 12+32
> Runtime: OpenJDK Runtime Environment 12+32
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
>Reporter: Giuseppe Tino
>Priority: Major
>
> Steps to reproduce:
> # Create a new "Maven / Web Application" project:
> ** "Project Name": {{firstcup}}
> ** "Server": {{GlassFish Server 5.0}}
> ** "Java EE Version": {{Java EE 7 Web}}
> ** "Context Path": {{/firstcup}}
> # After the project is created, invoke pop-up menu on it's root node and
> select *Properties*.
> # Select the "Frameworks" category in the "Project Properties" manager.
> # Push the *Add...* button and choose "JavaServer Faces" framework.
> # In "Configuration" tab, set "JSF Servlet URL Pattern" to:
> {{/firstcupWeb/*}} and push *OK*.
> # Delete generated web pages.
> Expected result:
> * The project is created and no errors are displayed
> Actual result:
> * In the project panel the file Web pages > WEB-INF > web.xml is marked with
> a red x. On mouse hover the following message is shown "cvc-elt.1.a: Cannot
> find the declaration of element 'web-app'. "
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-188) Please add support for code completion while typing
[ https://issues.apache.org/jira/browse/NETBEANS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847857#comment-16847857 ] Pete Whelpton commented on NETBEANS-188: Had a look through the code, and there is auto Code Completion - of a fashion. It is configured to only pop-up after a . character. E.g. SELECT c.CUSTOMER_ID, c.CUSTOMER_NAME FROM CUSTOMERS c; will invoke the Code Completion pop-up for the column names of the aliased table. Does anybody know if there is a historical reason why it was configured this way? Is it ok to change it to pop-up after 1st character typed? > Please add support for code completion while typing > --- > > Key: NETBEANS-188 > URL: https://issues.apache.org/jira/browse/NETBEANS-188 > Project: NetBeans > Issue Type: Improvement > Components: db - SQL Editor >Affects Versions: Next >Reporter: Christian Lenz >Priority: Major > Attachments: sqlCodeCompletion.gif > > > Afaik, the SQL Editor, is the only one, where you don't have code completion, > while typing. It only appears after you hit ctrl + space, which is weird. It > should be there per default. If not, there should be an option that code > completion should always be possible, in any cases and you can deactivate it, > if you don't want it. > For each keyword, table, view whatever, I have to type a character and hit > ctrl + space. It would be very nice to have the same code completion feature > as in java or other languages, that the code completion comes up, while > typing. For example: > Type "S" -> code completion should come immediately and should show you the > results. Same for everything like tables, views, databases, aliases and > columns. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2544) Unexcepted token WS (@import rule)
[
https://issues.apache.org/jira/browse/NETBEANS-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840236#comment-16840236
]
Pete Whelpton edited comment on NETBEANS-2544 at 5/15/19 9:40 AM:
--
if import at-rules are used, they *must* be the first declarations in the
stylesheet. If you move your import rules to the top of your stylesheet, can
you confirm that the parser error goes away (it does for me with the example
you provided):
W3C: [https://drafts.csswg.org/css-cascade-3/#at-ruledef-import]
MDN: [https://developer.mozilla.org/en-US/docs/Web/CSS/@import]
>From W3C spec "Any @import rules must precede all other at-rules and style
>rules in a style sheet (besides @charset, which must be the first thing in the
>style sheet if it exists), or else the @import rule is invalid."
If the error still occurs for you, are you able to share your .css ?
was (Author: peedeeboy):
if import state at-rules are used, they *must* be the first declarations in the
stylesheet. If you move your import rules to the top of your stylesheet, can
you confirm that the parser error goes away (it does for me with the example
you provided):
W3C: [https://drafts.csswg.org/css-cascade-3/#at-ruledef-import]
MDN: [https://developer.mozilla.org/en-US/docs/Web/CSS/@import]
>From W3C spec "Any @import rules must precede all other at-rules and style
>rules in a style sheet (besides @charset, which must be the first thing in the
>style sheet if it exists), or else the @import rule is invalid."
> Unexcepted token WS (@import rule)
> --
>
> Key: NETBEANS-2544
> URL: https://issues.apache.org/jira/browse/NETBEANS-2544
> Project: NetBeans
> Issue Type: Bug
>Reporter: Joshua Bakker
>Priority: Minor
> Attachments: bug_netbeans.PNG, nb-10-css-import.png
>
>
> When an "@import" is used in CSS files, the CSS files will mark it as an
> error.
> For example, the following line:
> {code:java}
> @import
> url("//netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.css");
> {code}
> Will result in a red line between @import and url, saying the error
> "Unexcepted token WS", when the line in fact is a valid line. Even Internet
> Explorer 5.5 has full support for it, meaning that it's fully supported and
> should be marked as valid in Netbeans.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2544) Unexcepted token WS (@import rule)
[
https://issues.apache.org/jira/browse/NETBEANS-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840236#comment-16840236
]
Pete Whelpton commented on NETBEANS-2544:
-
if import state at-rules are used, they *must* be the first declarations in the
stylesheet. If you move your import rules to the top of your stylesheet, can
you confirm that the parser error goes away (it does for me with the example
you provided):
W3C: [https://drafts.csswg.org/css-cascade-3/#at-ruledef-import]
MDN: [https://developer.mozilla.org/en-US/docs/Web/CSS/@import]
>From W3C spec "Any @import rules must precede all other at-rules and style
>rules in a style sheet (besides @charset, which must be the first thing in the
>style sheet if it exists), or else the @import rule is invalid."
> Unexcepted token WS (@import rule)
> --
>
> Key: NETBEANS-2544
> URL: https://issues.apache.org/jira/browse/NETBEANS-2544
> Project: NetBeans
> Issue Type: Bug
>Reporter: Joshua Bakker
>Priority: Minor
> Attachments: bug_netbeans.PNG, nb-10-css-import.png
>
>
> When an "@import" is used in CSS files, the CSS files will mark it as an
> error.
> For example, the following line:
> {code:java}
> @import
> url("//netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.css");
> {code}
> Will result in a red line between @import and url, saying the error
> "Unexcepted token WS", when the line in fact is a valid line. Even Internet
> Explorer 5.5 has full support for it, meaning that it's fully supported and
> should be marked as valid in Netbeans.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1849) Checkmark for Active plugins not working
[ https://issues.apache.org/jira/browse/NETBEANS-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837935#comment-16837935 ] Pete Whelpton commented on NETBEANS-1849: - Had a look at the code. For a plugin to get the green Active checkmark, all of its constituent components and dependencies must also be active. The reason Groovy doesn't get the green Active checkmark is because it depends on the Java SE module, and Java SE contains the Java Shell component, and unless one is running NB on JDK9+, Java Shell can't be enabled. Hence Java SE doesn't show as enabled, hence Groovy doesn't show as enabled. Not sure if this would be considered a bug or working as intended? There's a similar thing with PHP. It depends on HTML5, so unless all HTML5 components are enabled, PHP won't show as enabled either. There perhaps needs to be a 'partially enabled' status? > Checkmark for Active plugins not working > > > Key: NETBEANS-1849 > URL: https://issues.apache.org/jira/browse/NETBEANS-1849 > Project: NetBeans > Issue Type: Bug > Components: ide - Features On Demand, ide - UI >Affects Versions: 10.0 >Reporter: Charles George >Priority: Trivial > Labels: easyfix > Fix For: Next > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Tools>Plugins>Installed is not properly reporting which plugins are active. > Specifically, after activating the Groovy and Java SE plugins there is no > green checkmark next to them. This seems to work, however, for Base IDE and > Tools. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2534) Add support for parsing / code completion of draft CSS properties
Pete Whelpton created NETBEANS-2534: --- Summary: Add support for parsing / code completion of draft CSS properties Key: NETBEANS-2534 URL: https://issues.apache.org/jira/browse/NETBEANS-2534 Project: NetBeans Issue Type: Improvement Reporter: Pete Whelpton Browser vendors are now adding support for new CSS feature often whilst the CSS specification is still in its draft / experimental phase. Netbeans needs to be able to support draft CSS properties / values, whilst making it obvious that those properties are in a *draft* state. What I would propose: 1) The CSS module properties files netbeans/ide/css.editor/src/org/netbeans/modules/css/editor/module/main/properties/ need some kind of flag, e.g. a tilde symbol ~ before each draft property to flag it 2) GrammarParser in the CSS Lib module needs to be aware of this symbol, and the parseElement method would then create a new DraftModuleProperty (or similarly named) class, or the existing Property class would have a isDraft boolean property added to it 3) Code Completion for CSS would be updated so that draft module properties / values used the spanner icon [https://github.com/apache/netbeans/blob/master/ide/web.common.ui/src/org/netbeans/modules/web/common/ui/resources/config-badge.gif] As always, more than willing to help in any way possible -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2533) Update CSS browser compatibility help - include version number
[ https://issues.apache.org/jira/browse/NETBEANS-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2533: Labels: browser css web (was: ) > Update CSS browser compatibility help - include version number > -- > > Key: NETBEANS-2533 > URL: https://issues.apache.org/jira/browse/NETBEANS-2533 > Project: NetBeans > Issue Type: Improvement > Components: web - CSS Editor >Reporter: Pete Whelpton >Priority: Minor > Labels: browser, css, web > > PropertyCompatibilityHelpResolver.java parse the .properties files in: > netbeans/ide/css.editor/src/org/netbeans/modules/css/editor/module/main/browsers/ > > > and then sets the appropriate browser icon (Safari, Chrome, Firefox etc.) as > active (colourful) or inactive (greyscale) in the Code Completion help > depending on whether or not the CSS property is found in each browsers > .property file. > > The problems are: > 1) These .properties files haven't been updated for a very long time, so > several properties show as not supported by browsers which have now supported > them for ages. > 2) Unlike the old days, browsers are pretty quick to implement support, so a > straight forward supported/not-supported is not so useful now. It would be > more useful to show which version of a browser support for a CSS feature was > implemented > 3) These .properties files are also used to create browser specific version > of CSS properties e.g. -moz or -webkit properties. As these files have not > been updated for a long time, Netbeans will not create a lot of browser > specific properties that are not available > > My proposal is: > 1) The properties files need updating with the latest support for each browser > 2) Edge needs adding in - this should be a simple case of a new EdgeModule > class, icons, properties file > 3) The supported version number for each CSS property should be part of the > .properties file. The BrowserSpecificDefinitionParser class would need > updating to parse the properties file for these version numbers > 4) PropertyCompatibilityHelpResolver.java would need updating to create an > extra row of HTML in the table containing the browser icons, with the > supported version number for the property in > > The main thing holding me back is finding a good, reliable source of CSS > browser compatibility that is compatible with the Apache licence / not going > to cause copyright problems. That seems to rule out MDN etc. and also the > web pages for each browser that Netbeans original compatibility information > was taken from no longer exist... -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2533) Update CSS browser compatibility help - include version number
Pete Whelpton created NETBEANS-2533: --- Summary: Update CSS browser compatibility help - include version number Key: NETBEANS-2533 URL: https://issues.apache.org/jira/browse/NETBEANS-2533 Project: NetBeans Issue Type: Improvement Components: web - CSS Editor Reporter: Pete Whelpton PropertyCompatibilityHelpResolver.java parse the .properties files in: netbeans/ide/css.editor/src/org/netbeans/modules/css/editor/module/main/browsers/ and then sets the appropriate browser icon (Safari, Chrome, Firefox etc.) as active (colourful) or inactive (greyscale) in the Code Completion help depending on whether or not the CSS property is found in each browsers .property file. The problems are: 1) These .properties files haven't been updated for a very long time, so several properties show as not supported by browsers which have now supported them for ages. 2) Unlike the old days, browsers are pretty quick to implement support, so a straight forward supported/not-supported is not so useful now. It would be more useful to show which version of a browser support for a CSS feature was implemented 3) These .properties files are also used to create browser specific version of CSS properties e.g. -moz or -webkit properties. As these files have not been updated for a long time, Netbeans will not create a lot of browser specific properties that are not available My proposal is: 1) The properties files need updating with the latest support for each browser 2) Edge needs adding in - this should be a simple case of a new EdgeModule class, icons, properties file 3) The supported version number for each CSS property should be part of the .properties file. The BrowserSpecificDefinitionParser class would need updating to parse the properties file for these version numbers 4) PropertyCompatibilityHelpResolver.java would need updating to create an extra row of HTML in the table containing the browser icons, with the supported version number for the property in The main thing holding me back is finding a good, reliable source of CSS browser compatibility that is compatible with the Apache licence / not going to cause copyright problems. That seems to rule out MDN etc. and also the web pages for each browser that Netbeans original compatibility information was taken from no longer exist... -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2532) Update CSS help
[ https://issues.apache.org/jira/browse/NETBEANS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2532: Labels: css help web (was: ) > Update CSS help > --- > > Key: NETBEANS-2532 > URL: https://issues.apache.org/jira/browse/NETBEANS-2532 > Project: NetBeans > Issue Type: Improvement > Components: web - CSS Editor >Affects Versions: 11.0 >Reporter: Pete Whelpton >Priority: Minor > Labels: css, help, web > > CSS help (as displayed in Code Completion help window) is derived from two > .zip files: > > css21-spec.zip > css3-spec.zip > > which are downloaded from OSUOSL at build time. The .zips contain the html > pages of the official CSS specs from the W3C website. > > Also, NB decides which zip to check by parsing the module URL in > DefaultCssEditorModule.java. If the URL contains css3, then the > css3-spec.zip folder is search for the appropriate HTML page, otherwise the > css21-spec.zip is search. > > There are three problems: > > 1) Both of these .zip files contain really old versions of the specs! > 2) W3C no longer put css3 in the URL of module web pages. E.g. > [https://www.w3c.ord/TR/css3-values] is now > [https://www.w3c.org/TR/css-values-3/] > 3) This logic doesn't take into account new modules that have started back at > Level 1 again, or new versions of existing modules that are now on Level 4 > > My proposal would be to create one .zip file of the latest versions of the > specs, update DefaultCssEditorModule.java with the current URLs for the specs > on the w3c site, and then have just one help resolver that parsed that one > .zip file. > > I'd be happy to do a lot of this work - although I don't have access to > upload binaries to OSUOSL, so if somebody who does gets in touch we can get > cracking -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2532) Update CSS help
Pete Whelpton created NETBEANS-2532: --- Summary: Update CSS help Key: NETBEANS-2532 URL: https://issues.apache.org/jira/browse/NETBEANS-2532 Project: NetBeans Issue Type: Improvement Components: web - CSS Editor Affects Versions: 11.0 Reporter: Pete Whelpton CSS help (as displayed in Code Completion help window) is derived from two .zip files: css21-spec.zip css3-spec.zip which are downloaded from OSUOSL at build time. The .zips contain the html pages of the official CSS specs from the W3C website. Also, NB decides which zip to check by parsing the module URL in DefaultCssEditorModule.java. If the URL contains css3, then the css3-spec.zip folder is search for the appropriate HTML page, otherwise the css21-spec.zip is search. There are three problems: 1) Both of these .zip files contain really old versions of the specs! 2) W3C no longer put css3 in the URL of module web pages. E.g. [https://www.w3c.ord/TR/css3-values] is now [https://www.w3c.org/TR/css-values-3/] 3) This logic doesn't take into account new modules that have started back at Level 1 again, or new versions of existing modules that are now on Level 4 My proposal would be to create one .zip file of the latest versions of the specs, update DefaultCssEditorModule.java with the current URLs for the specs on the w3c site, and then have just one help resolver that parsed that one .zip file. I'd be happy to do a lot of this work - although I don't have access to upload binaries to OSUOSL, so if somebody who does gets in touch we can get cracking -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2530) Optimize GrammarParser.java in CSS Lib module
[ https://issues.apache.org/jira/browse/NETBEANS-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2530: Labels: css performance web (was: css performance) > Optimize GrammarParser.java in CSS Lib module > - > > Key: NETBEANS-2530 > URL: https://issues.apache.org/jira/browse/NETBEANS-2530 > Project: NetBeans > Issue Type: Improvement > Components: web - CSS Editor >Affects Versions: 11.0 >Reporter: Pete Whelpton >Priority: Major > Labels: css, performance, web > > Trying to bring the CSS module grammar (the .properties files in the CSS > Editor module) up to date causes severe performance issues in NB due to the > recursive nature of the parseElements() method of the GrammarParser class. > > 1) Recursive grammar (such as that of the calc() function in css) will cause > a stack overflow as parseElements() will keep calling itself to resolve > references until the stack is blown > 2) Not using recursive grammar will still cause major performance issues will > more than 1/2 levels of references, as memory gets eaten due to the > parseElements() method not having a cache (e.g. it will call itself to try > and resolve a reference it has already resolved previously, doing a lot of > unnecessary work). In its current implementation it can blow the Java heap. > > I have grammar pretty much ready to go to implement CSS Values and Modules > function in NB (e.g. proper implementation of calc(), min(), max(), attr() > etc.), and have got 2) to be less of an issue by using a HashMap to cached > reference properties so they don't get resolved again. Performance is still > "stutery" at best - at NB memory still gets used up, but then reclaimed by > the GC. Could really use some help properly optimizing this class. > > I think this should be fairly straightforward for somebody who knows what > they are doing! I'd love to help bring CSS support up to date! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2530) Optimize GrammarParser.java in CSS Lib module
[ https://issues.apache.org/jira/browse/NETBEANS-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2530: Labels: css performance (was: ) > Optimize GrammarParser.java in CSS Lib module > - > > Key: NETBEANS-2530 > URL: https://issues.apache.org/jira/browse/NETBEANS-2530 > Project: NetBeans > Issue Type: Improvement > Components: web - CSS Editor >Affects Versions: 11.0 >Reporter: Pete Whelpton >Priority: Major > Labels: css, performance > > Trying to bring the CSS module grammar (the .properties files in the CSS > Editor module) up to date causes severe performance issues in NB due to the > recursive nature of the parseElements() method of the GrammarParser class. > > 1) Recursive grammar (such as that of the calc() function in css) will cause > a stack overflow as parseElements() will keep calling itself to resolve > references until the stack is blown > 2) Not using recursive grammar will still cause major performance issues will > more than 1/2 levels of references, as memory gets eaten due to the > parseElements() method not having a cache (e.g. it will call itself to try > and resolve a reference it has already resolved previously, doing a lot of > unnecessary work). In its current implementation it can blow the Java heap. > > I have grammar pretty much ready to go to implement CSS Values and Modules > function in NB (e.g. proper implementation of calc(), min(), max(), attr() > etc.), and have got 2) to be less of an issue by using a HashMap to cached > reference properties so they don't get resolved again. Performance is still > "stutery" at best - at NB memory still gets used up, but then reclaimed by > the GC. Could really use some help properly optimizing this class. > > I think this should be fairly straightforward for somebody who knows what > they are doing! I'd love to help bring CSS support up to date! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2530) Optimize GrammarParser.java in CSS Lib module
Pete Whelpton created NETBEANS-2530: --- Summary: Optimize GrammarParser.java in CSS Lib module Key: NETBEANS-2530 URL: https://issues.apache.org/jira/browse/NETBEANS-2530 Project: NetBeans Issue Type: Improvement Components: web - CSS Editor Affects Versions: 11.0 Reporter: Pete Whelpton Trying to bring the CSS module grammar (the .properties files in the CSS Editor module) up to date causes severe performance issues in NB due to the recursive nature of the parseElements() method of the GrammarParser class. 1) Recursive grammar (such as that of the calc() function in css) will cause a stack overflow as parseElements() will keep calling itself to resolve references until the stack is blown 2) Not using recursive grammar will still cause major performance issues will more than 1/2 levels of references, as memory gets eaten due to the parseElements() method not having a cache (e.g. it will call itself to try and resolve a reference it has already resolved previously, doing a lot of unnecessary work). In its current implementation it can blow the Java heap. I have grammar pretty much ready to go to implement CSS Values and Modules function in NB (e.g. proper implementation of calc(), min(), max(), attr() etc.), and have got 2) to be less of an issue by using a HashMap to cached reference properties so they don't get resolved again. Performance is still "stutery" at best - at NB memory still gets used up, but then reclaimed by the GC. Could really use some help properly optimizing this class. I think this should be fairly straightforward for somebody who knows what they are doing! I'd love to help bring CSS support up to date! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2400) AWS Cloud missing Region: US East(OHIO) Region
[ https://issues.apache.org/jira/browse/NETBEANS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817070#comment-16817070 ] Pete Whelpton commented on NETBEANS-2400: - I had a very quick / little look into this, and I think what needs to be done to fix this is; 1) The regions and endpoints need updating in enterprise/cloud.amazon/src/org/netbeans/modules/cloud/amazon/ui/AmazonWizardComponent.java 2) I think a newer version of the aws-java-sdk.jar that supports the newer Regions needs to be compiled with the necessary modules for EBS and uploaded to the NB binary dependency server 3) /enterprise/libs.amazon/external/binaries-list needs updating to download above file during build 4) The bundle file enterprise/cloud.amazon/src/org/netbeans/modules/cloud/amazon/ui/serverplugin/Bundle.properties needs updating to remove the "\ \" as it is causing a property to be treated as a value and means that NB crashed when right clicking -> properties on the Tomcat server node in the Services panel > AWS Cloud missing Region: US East(OHIO) Region > -- > > Key: NETBEANS-2400 > URL: https://issues.apache.org/jira/browse/NETBEANS-2400 > Project: NetBeans > Issue Type: Bug > Components: core >Affects Versions: 11.0 > Environment: Windows 10 >Reporter: Robert Campbell >Priority: Major > Labels: AWS, Region > > in Add Cloud Provider Step 2 "Amazon Beanstalk" The Region: "US East (OHIO) > Region" is not available as an option. Is there an XML file or configuration > file I need to update to get this option ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1456) Unsupported calc() function in CSS stylesheets
[
https://issues.apache.org/jira/browse/NETBEANS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816081#comment-16816081
]
Pete Whelpton commented on NETBEANS-1456:
-
Had a crack at this last night, adding the calc() function grammar into the
properties. Ran into the issue that calc() allows nested functions and
recursive grammar causes GrammarParser to overflow as it will try and resolve
the grammar until it blows the stack...
More thought required.
> Unsupported calc() function in CSS stylesheets
> --
>
> Key: NETBEANS-1456
> URL: https://issues.apache.org/jira/browse/NETBEANS-1456
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: css, easy
>
> The following code in CSS Editor shows as a warning:
> {code:java}
> .modal-dialog-centered {
> min-height: calc(100% - (0.5rem * 2));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-1456) Unsupported calc() function in CSS stylesheets
[
https://issues.apache.org/jira/browse/NETBEANS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816081#comment-16816081
]
Pete Whelpton edited comment on NETBEANS-1456 at 4/12/19 8:24 AM:
--
Had a crack at this last night, adding the calc() function grammar into the
properties. Ran into the issue that calc() allows nested functions and
recursive grammar causes GrammarParser to overflow as it will try and
recursively resolve the grammar until it blows the stack...
More thought required.
was (Author: peedeeboy):
Had a crack at this last night, adding the calc() function grammar into the
properties. Ran into the issue that calc() allows nested functions and
recursive grammar causes GrammarParser to overflow as it will try and resolve
the grammar until it blows the stack...
More thought required.
> Unsupported calc() function in CSS stylesheets
> --
>
> Key: NETBEANS-1456
> URL: https://issues.apache.org/jira/browse/NETBEANS-1456
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: css, easy
>
> The following code in CSS Editor shows as a warning:
> {code:java}
> .modal-dialog-centered {
> min-height: calc(100% - (0.5rem * 2));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-1456) Unsupported calc() function in CSS stylesheets
[
https://issues.apache.org/jira/browse/NETBEANS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814328#comment-16814328
]
Pete Whelpton edited comment on NETBEANS-1456 at 4/10/19 11:40 AM:
---
Can you provide some examples?
cal() is supported (in a very basic way), but I've done some digging and I can
see straight away that there is a problem with nested parenthesis. Before I go
too much further, I'm curious if this is the only issue.
At the moment, when calc() is parsed, processing the contents of the
parenthesis is delegated to the TokenAcceptor$GenericFunctionContent which
seems to allow any token up until it hits a right parenthesis. This is why
nested parenthesis fail parsing.
I think there are two possible solutions:
1) Add a new method to TokenAcceptor to handle the specific case of calc()
2) Add the proper parsing rules to the default_module.properties file. The
problem with this approach is that GrammarParser treats + - * etc. as
multiplicity modifiers to the grammer. There already appears to be some logic
to escape such characters in GrammarParser (by using ' or "), but from a little
testing, doesn't seem to work how I thought it should so need to check /
amend...
2) Is probably the more future proof solution...
was (Author: peedeeboy):
Can you provide some examples?
cal() is supported (in a very basic way), but I've done some digging and I can
see straight away that there is a problem with nested parenthesis. Before I go
too much further, I'm curious if this is the only issue.
At the moment, when calc() is parsed, processing the contents of the
parenthesis is delegated to the TokenAcceptor$GenericFunctionContent which
seems to allow any token up until it hits a right parenthesis. This is why
nested parenthesis fail parsing.
I think there are two possible solutions:
1) Add a new method to TokenAcceptor to handle the specific case of calc()
2) Add the proper parsing rules to the default_module.properties file. The
problem with this approach is that GrammarParser treats + - * etc. as modifiers
to the grammer. There already appears to be some logic to escape such
characters in GrammarParser (by using ' or "), but from a little testing,
doesn't seem to work how I thought it should so need to check / amend...
2) Is probably the more future proof solution...
> Unsupported calc() function in CSS stylesheets
> --
>
> Key: NETBEANS-1456
> URL: https://issues.apache.org/jira/browse/NETBEANS-1456
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: css, easy
>
> The following code in CSS Editor shows as a warning:
> {code:java}
> .modal-dialog-centered {
> min-height: calc(100% - (0.5rem * 2));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1456) Unsupported calc() function in CSS stylesheets
[
https://issues.apache.org/jira/browse/NETBEANS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814328#comment-16814328
]
Pete Whelpton commented on NETBEANS-1456:
-
Can you provide some examples?
cal() is supported (in a very basic way), but I've done some digging and I can
see straight away that there is a problem with nested parenthesis. Before I go
too much further, I'm curious if this is the only issue.
At the moment, when calc() is parsed, processing the contents of the
parenthesis is delegated to the TokenAcceptor$GenericFunctionContent which
seems to allow any token up until it hits a right parenthesis. This is why
nested parenthesis fail parsing.
I think there are two possible solutions:
1) Add a new method to TokenAcceptor to handle the specific case of calc()
2) Add the proper parsing rules to the default_module.properties file. The
problem with this approach is that GrammarParser treats + - * etc. as modifiers
to the grammer. There already appears to be some logic to escape such
characters in GrammarParser (by using \' or "), but from a little testing,
doesn't seem to work how I thought it should so need to check / amend...
2) Is probably the more future proof solution...
> Unsupported calc() function in CSS stylesheets
> --
>
> Key: NETBEANS-1456
> URL: https://issues.apache.org/jira/browse/NETBEANS-1456
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: css, easy
>
> The following code in CSS Editor shows as a warning:
> {code:java}
> .modal-dialog-centered {
> min-height: calc(100% - (0.5rem * 2));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1409) Unexpected token SEMI found
[ https://issues.apache.org/jira/browse/NETBEANS-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-1409. - Resolution: Fixed CSS variable support added by: [https://github.com/apache/incubator-netbeans/pull/1172] CSS @supports rule support added by: [https://github.com/apache/incubator-netbeans/pull/1181] Hopefully, these will make it into NB11.1 > Unexpected token SEMI found > --- > > Key: NETBEANS-1409 > URL: https://issues.apache.org/jira/browse/NETBEANS-1409 > Project: NetBeans > Issue Type: New Feature > Components: web - CSS Editor >Affects Versions: 8.2, 9.0, 10.0 >Reporter: Dhanush Pavadai >Priority: Critical > Labels: cssnext, cssvariable > Attachments: ddd.png, phpstorm_css.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1691) Error in css syntax
[
https://issues.apache.org/jira/browse/NETBEANS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-1691.
-
Resolution: Fixed
Assignee: Pete Whelpton
Should be resolved by [https://github.com/apache/incubator-netbeans/pull/1181]
Hopefully, this will make it into NB11.1
> Error in css syntax
> ---
>
> Key: NETBEANS-1691
> URL: https://issues.apache.org/jira/browse/NETBEANS-1691
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 10.0
>Reporter: Los Vitaly
>Assignee: Pete Whelpton
>Priority: Major
> Labels: pull-request-available
> Attachments: netbeans_css.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Reproducible code
> {code:java}
> @supports ((perspective: 10px) or (-moz-perspective: 10px) or
> (-webkit-perspective: 10px) or
> (-ms-perspective: 10px) or (-o-perspective: 10px)) {
> … /* CSS applied when 3D transforms, prefixed or not, are supported */
> }
> {code}
>
> I get example from here.
> [https://developer.mozilla.org/en-US/docs/Web/CSS/@supports]
> And give screenshot from my NB10
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2006) Support of CSS media query @supports
[ https://issues.apache.org/jira/browse/NETBEANS-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-2006. - Resolution: Fixed @supports support is added by [https://github.com/apache/incubator-netbeans/pull/1181|https://github.com/apache/incubator-netbeans/pull/1181.] Hopefully this will make it into NB11.1 > Support of CSS media query @supports > > > Key: NETBEANS-2006 > URL: https://issues.apache.org/jira/browse/NETBEANS-2006 > Project: NetBeans > Issue Type: Wish >Reporter: Arnaud BERNARD >Priority: Major > > Main feature of CSS 4 that can be already used safley in a production > environment. Thx! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2182) Display correct licence (Oracle / Eclipse Foundation) depending on version of GlassFish to download
[ https://issues.apache.org/jira/browse/NETBEANS-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-2182: Labels: api-change pull-request-available (was: pull-request-available) > Display correct licence (Oracle / Eclipse Foundation) depending on version of > GlassFish to download > --- > > Key: NETBEANS-2182 > URL: https://issues.apache.org/jira/browse/NETBEANS-2182 > Project: NetBeans > Issue Type: Improvement > Components: serverplugins - GlassFish >Affects Versions: 11.0 >Reporter: Pete Whelpton >Priority: Minor > Labels: api-change, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A follow up to https://issues.apache.org/jira/browse/NETBEANS-2130 > > The link for "I have read and understand the license..." should change > dynamically between the Oracle license (GF <= 5.0) and EF license (GF >= 5.1) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-2182) Display correct licence (Oracle / Eclipse Foundation) depending on version of GlassFish to download
Pete Whelpton created NETBEANS-2182: --- Summary: Display correct licence (Oracle / Eclipse Foundation) depending on version of GlassFish to download Key: NETBEANS-2182 URL: https://issues.apache.org/jira/browse/NETBEANS-2182 Project: NetBeans Issue Type: Improvement Components: serverplugins - GlassFish Affects Versions: 11.0 Reporter: Pete Whelpton A follow up to https://issues.apache.org/jira/browse/NETBEANS-2130 The link for "I have read and understand the license..." should change dynamically between the Oracle license (GF <= 5.0) and EF license (GF >= 5.1) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have released GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
*enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java*
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1_STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
* Update Glassfish Common module. Add new string value to Bundle
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties*
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
* Update Server Details so NB knows where to download GF 5.1 from
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java*
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something like:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have released GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have released GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
*enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java*
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
* Update Glassfish Common module. Add new string value to Bundle
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties*
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
* Update Server Details so NB knows where to download GF 5.1 from
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java*
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something like:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
*enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java*
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
* Update Glassfish Common module. Add new string value to Bundle
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties*
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
* Update Server Details so NB knows where to download GF 5.1 from
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java*
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something like:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
* Update Glassfish Common module. Add new string value to Bundle
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
* Update Server Details so NB knows where to download GF 5.1 from
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something link:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
# Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
*enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java*
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
* Update Glassfish Common module. Add new string value to Bundle
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties*
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
* Update Server Details so NB knows where to download GF 5.1 from
Modify
*enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java*
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something link:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
* Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF
[jira] [Updated] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
[
https://issues.apache.org/jira/browse/NETBEANS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-2130:
Description:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like:
# Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
{code:java}
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
{code}
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
{code:java}
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
{code}
Add the above values to the Map (below GF 5.0 entry) :
{code:java}
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
{code}
# Update Glassfish Common module. Add new string value to Bundle
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties
to add a string value for GF 5.1 below GF 5.0
{code:java}
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
{code}
# Update Server Details so NB knows where to download GF 5.1 from
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java
and add an entry for GF5.1 below GF5.0
{code:java}
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
{code}
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
{code:java}
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
{code}
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
{code:java}
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
{code}
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something link:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
was:
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like
# Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an
[jira] [Created] (NETBEANS-2130) Add support to download/install/register GlassFish 5.1
Pete Whelpton created NETBEANS-2130:
---
Summary: Add support to download/install/register GlassFish 5.1
Key: NETBEANS-2130
URL: https://issues.apache.org/jira/browse/NETBEANS-2130
Project: NetBeans
Issue Type: Improvement
Components: serverplugins - GlassFish
Affects Versions: 11.0
Reporter: Pete Whelpton
Eclipse Foundation have release GlassFish 5.1. Netbeans should add support to
download, install and register, as per previous versions of GlassFish.
Based on my work on GF 4.1.2 & GF 5.0, the steps need should be something like
# Update Glassfish Tooling module so that NB will recognise GF 5.1 as a
distinct version (rather than reporting an instance of GF 5.1 as GF 5.0)
Modify
enterprise/glassfish.tooling/src/org/netbeans/modules/glassfish/tooling/data/GlassFishVersion.java
Add value for GF 5.1 to bottom of Enum values (below GF5.0 entry):
[code]
/** GlassFish 5. */
GF_5 ((short) 5, (short) 0, (short) 0, (short) 0, GlassFishVersion.GF_5_STR);
/** GlassFish 5.1 */
GF_5_1 ((short) 5, (short) 1, (short) 0, (short) 0,
GlassFishVersion.GF_5_1_STR);
[/code]
Add a constant for the string value of GF 5.1 (below GF 5.0 entry)
[code]
/** A String representation of GF_5 value. */
static final String GF_5_STR = "5";
/** Additional String representations of GF_5 value. */
static final String GF_5_STR_NEXT[] = {"5.0", "5.0.0", "5.0.0.0"};
/** A String representation of GF_5_1 value. */
static final String GF_5_1)STR = "5.1";
/** Additional String representations of GF_5_1 value. */
static final String GF_5_1_STR_NEXT[] = {"5.1.0", "5.1.0.0"};
[/code]
Add the above values to the Map (below GF 5.0 entry) :
[code]
initStringValuesMapFromArray(GF_5, GF_5_STR_NEXT);
initStringValuesMapFromArray(GF_5_1, GF_5_1_STR_NEXT);
[/code]
# Update Glassfish Common module. Add new string value to Bundle
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/Bundle.properties
to add a string value for GF 5.1 below GF 5.0
[code]
STR_50_SERVER_NAME=GlassFish Server 5.0
STR_51_SERVER_NAME=GlassFish Server 5.1
[/code]
# Update Server Details so NB knows where to download GF 5.1 from
Modify
enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java
and add an entry for GF5.1 below GF5.0
[code]
/**
* details for an instance of GlassFish Server 5
*/
GLASSFISH_SERVER_5_0(NbBundle.getMessage(ServerDetails.class,
"STR_50_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
500,
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip;, //
NOI18N
"https://download.oracle.com/glassfish/5.0/release/glassfish-5.0.zip; //
NOI18N
);
/**
* details for an instance of GlassFish Server 5.1
*/
GLASSFISH_SERVER_5_1(NbBundle.getMessage(ServerDetails.class,
"STR_51_SERVER_NAME", new Object[]{}), // NOI18N
"deployer:gfv3ee6wc", // NOI18N
510,
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;,
// NOI18N
"https://www.eclipse.org/downloads/download.php?file=/glassfish/glassfish-5.1.0.zip_id=492;
// NOI18N
);
[/code]
Add GF 5.1 to the top of the Server Details iterator (the "top half" should be
all supported GF versions, the bottom half is those that can be installed via
NB UI - OPTIONALLY remove GF 3.1.2.2 from the bottom half):
[code]
return new ServerWizardIterator(new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2,
GLASSFISH_SERVER_3_1_2,
GLASSFISH_SERVER_3_1_1,
GLASSFISH_SERVER_3_1,
GLASSFISH_SERVER_3_0_1,
GLASSFISH_SERVER_3,},
new ServerDetails[]{
GLASSFISH_SERVER_5_1,
GLASSFISH_SERVER_5_0,
GLASSFISH_SERVER_4_1_2,
GLASSFISH_SERVER_4_1_1,
GLASSFISH_SERVER_4_1,
GLASSFISH_SERVER_4_0,
GLASSFISH_SERVER_3_1_2_2});
}
[/code]
Add GF5.1 version to list of recognised installed GF versions (below GF 5.0):
[code]
case GF_5: return GLASSFISH_SERVER_5_0.getVersion();
case GF_5_1: return GLASSFISH_SERVER_5_1.getVersion();
[/code]
The other thing that would need doing would be pointing to the Ecilpse Licence,
rather than the Oracle one. I was thinking of something link:
* Adding the licence location for each GF version to the enum in ServerDetails
* Moving the checkbox and link to the licence to the dialog box where the user
chooses the glassfish version
* Updating the licence link based on which version of GF is selected in the
dropdown by querying the ServerDetails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail:
[jira] [Commented] (NETBEANS-1455) CSS3 property user-select unsupported
[ https://issues.apache.org/jira/browse/NETBEANS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767262#comment-16767262 ] Pete Whelpton commented on NETBEANS-1455: - I feel that the ideal solution would be for Code Completion in NB to have a warning icon next to non-standard/draft Properties. VSCode already does something similar: !User-select-warning.PNG! The NB CSS parser could use quite a bit of TLC :( I think I've figured it out enough to add in support for user-select, but not yet for updating code completion to show a warning for it still being draft status. I think that would require: * Flagging non-standard properties in the Properties files and updating the Grammar Parser to recognize aforementioned flag * OR creating a seperate Properties file of non-standard/draft properties (the existing Properties files closely follow the W3C grammar specifications, so may be better not to pollute them with other meanings) * Update the CodeCompletion provider to use a warning icon for those non-standard properties > CSS3 property user-select unsupported > - > > Key: NETBEANS-1455 > URL: https://issues.apache.org/jira/browse/NETBEANS-1455 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Editor >Affects Versions: 9.0 > Environment: Windows 10 >Reporter: Artur Stępień >Priority: Minor > Labels: easyfix > Attachments: User-select-warning.PNG > > > CSS3 user-select property is unsupported and shows as a warning -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1455) CSS3 property user-select unsupported
[ https://issues.apache.org/jira/browse/NETBEANS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton updated NETBEANS-1455: Attachment: User-select-warning.PNG > CSS3 property user-select unsupported > - > > Key: NETBEANS-1455 > URL: https://issues.apache.org/jira/browse/NETBEANS-1455 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Editor >Affects Versions: 9.0 > Environment: Windows 10 >Reporter: Artur Stępień >Priority: Minor > Labels: easyfix > Attachments: User-select-warning.PNG > > > CSS3 user-select property is unsupported and shows as a warning -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-965) does not load GlassFish
[ https://issues.apache.org/jira/browse/NETBEANS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-965. Resolution: Fixed Fix Version/s: 11.0 Pretty sure this is the same problem as NETBEANS-997, which is resolved by https://github.com/apache/incubator-netbeans/pull/1119 > does not load GlassFish > --- > > Key: NETBEANS-965 > URL: https://issues.apache.org/jira/browse/NETBEANS-965 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish > Environment: OS: Manjaro 17.1.10 Hakoila > Kernel: x86_64 Linux 4.14.48-2-MANJARO > DE: Xfce4 > WM: Xfwm4 >Reporter: Kron22 >Priority: Major > Fix For: 11.0 > > Attachments: error-glassfish.png > > > does not load GlassFish server -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-997) Unable to download and create GlassFish server
[
https://issues.apache.org/jira/browse/NETBEANS-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-997.
Resolution: Fixed
Fix Version/s: 11.0
Should be fixed in NB 11.0 by
https://github.com/apache/incubator-netbeans/pull/1119
> Unable to download and create GlassFish server
> ---
>
> Key: NETBEANS-997
> URL: https://issues.apache.org/jira/browse/NETBEANS-997
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - GlassFish
>Affects Versions: 8.2, 9.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-release-302-on-20180517)
> Updates: Updates available
> Java: 1.8.0_172-ea; Java HotSpot(TM) 64-Bit Server VM 25.172-b03
> Runtime: Java(TM) SE Runtime Environment 1.8.0_172-ea-b03
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
> User directory: C:\Users\johndoe\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\johndoe\AppData\Local\NetBeans\Cache\dev
>Reporter: Rick Hegarty
>Priority: Minor
> Labels: pull-request-available
> Fix For: 11.0
>
> Attachments: installGlassfish1.png, installGlassfish2.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> [1] Add a Glassfish server: *Services Panel > Servers >* right-click *> Add
> Server... > GlassFish Server > Next >*
> [2] On the *Add Server* screen:
> * In *Installation Location* enter a valid directory name that does not
> exist.
> * Check the _I have read_ checkbox.
> * Click *Download Now...* and then select _Glassfish Server 4.1.1_ as the
> server to be downloaded.
> * See attached screenshot *installGlassfish1.png*
> [3] The download appears to be successful but there is an error at the bottom
> of the *Add Server Instance* window: *! Does not exist.* See attached
> screenshot *installGlassfish2.png*
> [4] The target folder does not get created. Also, if an empty target folder
> is pre-created the same error occurs, and the target folder remains empty.
> [5] This error occurs with both NB 8.2 and NB 9.0 RC1.
> [6] Priority is minor since the simple workaround is to download Glassfish
> first outside of NetBeans, and then select that downloaded folder within the
> *Add Server* wizard.
> [7] Possible duplicate of NETBEANS-965 ("does not load GlassFish"), but there
> is no description for that bug and the screenshot information is in Russian.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1148) Trying to add several jigsaw modules to modulepath at once will add one; the rest goes to classpath
[ https://issues.apache.org/jira/browse/NETBEANS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-1148. - Resolution: Fixed Fix Version/s: 11.0 Should be fixed by https://github.com/apache/incubator-netbeans/commit/a760f722373cff71180b0a5c9843373dabb19e95 > Trying to add several jigsaw modules to modulepath at once will add one; the > rest goes to classpath > --- > > Key: NETBEANS-1148 > URL: https://issues.apache.org/jira/browse/NETBEANS-1148 > Project: NetBeans > Issue Type: Bug >Affects Versions: 9.0 >Reporter: Andreas Eckstein >Priority: Major > Labels: pull-request-available > Fix For: 11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I have java modular projects A and B, where A contains jigsaw modules A1, A2, > ... > Now I want to add all modules A* to B via 'Right-click on B' > Properties > > Libraries > Modulepath > 'Add Project...'. With the pop-up file picker, I can > select project A, and then any number of its modules. However, only the first > of those will be added to to the Modulepath list, all others are added to > Classpath instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1458) CSS3 perspective property doesn't support pixels value
[
https://issues.apache.org/jira/browse/NETBEANS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-1458.
-
Resolution: Fixed
Fix Version/s: 11.0
Perspective property and perspective function fixed by [GitHub Pull Request
#1103|https://github.com/apache/incubator-netbeans/pull/1103]
> CSS3 perspective property doesn't support pixels value
> --
>
> Key: NETBEANS-1458
> URL: https://issues.apache.org/jira/browse/NETBEANS-1458
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix, pull-request-available
> Fix For: 11.0
>
> Attachments: perspectiveerror.PNG
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following code causes warning cause of pixels value in perspective
> attribute
> {code:java}
> .carousel-item {
> perspective: 1000px;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-997) Unable to download and create GlassFish server
[
https://issues.apache.org/jira/browse/NETBEANS-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753140#comment-16753140
]
Pete Whelpton commented on NETBEANS-997:
I figured out what is happening and got Glassfish 4.1.1 to download and install
via the NB installer.
What is happening is:
1) NB first looks for the .txt file for the relevant Glassfish version on
[serverplugins.netbeans.org|http://serverplugins.netbeans.org/] (it will follow
redirects to try and find it).
2) If NB finds the txt file, it reads the first line, which contains the
directory path for that version of glassfish (see
[http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt] which is still
up!)
2a) The directory path is appended to the hardcoded base URL,
[http://download.java.net|http://download.java.net/]
2b) NB will then try and download the glassfish .zip from this URL (but
won't follow redirects!)
3) If NB fails to find/parse the .txt file, it will try and download the .zip
from the direct [download.java.net|http://download.java.net/] link (the one
with the ?nbretriever=fallback querystring), but won't follow redirects
Because there are now 301 redirects on the
[download.java.net|http://download.java.net/] URLs from http to https, even the
fallback was failing. Changing the fallback URL for GF4.1.1. to https meant
that it downloaded correctly.
Questions:
a) Do we want to keep this logic, and host .txt files with the download path on
[netbeans.apache.org|http://netbeans.apache.org/]? Probably the least
intrusive way to get things working again
b) If not, what to do with this logic? Delete it? comment it out and just the
fallback URL? or leave it in and allow NB to waste a few cycles trying to find
a .txt file that doesn't exist?
c) Do we want to take this opportunity to update the
[java.download.net|http://java.download.net/] hostname to
[download.oracle.com|http://download.oracle.com/], as that seems to be where
the main Glassfish web page links to now for downloads?
d) Should the fallback URL also follow redirects?
> Unable to download and create GlassFish server
> ---
>
> Key: NETBEANS-997
> URL: https://issues.apache.org/jira/browse/NETBEANS-997
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - GlassFish
>Affects Versions: 8.2, 9.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-release-302-on-20180517)
> Updates: Updates available
> Java: 1.8.0_172-ea; Java HotSpot(TM) 64-Bit Server VM 25.172-b03
> Runtime: Java(TM) SE Runtime Environment 1.8.0_172-ea-b03
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
> User directory: C:\Users\johndoe\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\johndoe\AppData\Local\NetBeans\Cache\dev
>Reporter: Rick Hegarty
>Priority: Minor
> Attachments: installGlassfish1.png, installGlassfish2.png
>
>
> [1] Add a Glassfish server: *Services Panel > Servers >* right-click *> Add
> Server... > GlassFish Server > Next >*
> [2] On the *Add Server* screen:
> * In *Installation Location* enter a valid directory name that does not
> exist.
> * Check the _I have read_ checkbox.
> * Click *Download Now...* and then select _Glassfish Server 4.1.1_ as the
> server to be downloaded.
> * See attached screenshot *installGlassfish1.png*
> [3] The download appears to be successful but there is an error at the bottom
> of the *Add Server Instance* window: *! Does not exist.* See attached
> screenshot *installGlassfish2.png*
> [4] The target folder does not get created. Also, if an empty target folder
> is pre-created the same error occurs, and the target folder remains empty.
> [5] This error occurs with both NB 8.2 and NB 9.0 RC1.
> [6] Priority is minor since the simple workaround is to download Glassfish
> first outside of NetBeans, and then select that downloaded folder within the
> *Add Server* wizard.
> [7] Possible duplicate of NETBEANS-965 ("does not load GlassFish"), but there
> is no description for that bug and the screenshot information is in Russian.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1458) CSS3 perspective property doesn't support pixels value
[
https://issues.apache.org/jira/browse/NETBEANS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752648#comment-16752648
]
Pete Whelpton commented on NETBEANS-1458:
-
Added PR [https://github.com/apache/incubator-netbeans/pull/1103] which changes
perspective property parser rule to:
none |
and the perspective() function parser rule to:
perspective()
> CSS3 perspective property doesn't support pixels value
> --
>
> Key: NETBEANS-1458
> URL: https://issues.apache.org/jira/browse/NETBEANS-1458
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix, pull-request-available
> Attachments: perspectiveerror.PNG
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following code causes warning cause of pixels value in perspective
> attribute
> {code:java}
> .carousel-item {
> perspective: 1000px;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1457) CSS text-align poroperty value start is unsupported
[
https://issues.apache.org/jira/browse/NETBEANS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton resolved NETBEANS-1457.
-
Resolution: Fixed
Fixed by https://github.com/apache/incubator-netbeans/pull/1093
> CSS text-align poroperty value start is unsupported
> ---
>
> Key: NETBEANS-1457
> URL: https://issues.apache.org/jira/browse/NETBEANS-1457
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix, pull-request-available
> Attachments: textalignerror.PNG
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The following code shows as a warning cause of start value for text-align
> property
> {code:java}
> .tooltip {
> text-align: start;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1454) Editor marks word-break: break-word CSS rule as warning
[
https://issues.apache.org/jira/browse/NETBEANS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748553#comment-16748553
]
Pete Whelpton commented on NETBEANS-1454:
-
Probably one to take to the mailing list for guidance?
A new hint/warning for non-standard properties would seem inherently sensible
to me - sadly, this intrusive of a change is probably beyond my current
comfort/competence levels with NB source.
The waters get muddied further as whilst break-word is not in the W3C spec, the
W3C online validator will accept it as valid CSS
> Editor marks word-break: break-word CSS rule as warning
> ---
>
> Key: NETBEANS-1454
> URL: https://issues.apache.org/jira/browse/NETBEANS-1454
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
>
> CSS Editor showing following css atributes in a rule as a warning:
>
> {code:java}
> .someClass{
> word-break: break-word;
> }
> {code}
> *break-word* value for the *word-break* shows as unsupported.
> https://www.w3schools.com/cssref/css3_pr_word-break.asp
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-1613) "Select in projects" has no effect
[ https://issues.apache.org/jira/browse/NETBEANS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Whelpton resolved NETBEANS-1613. - Resolution: Fixed Fixed by PR #1082 > "Select in projects" has no effect > -- > > Key: NETBEANS-1613 > URL: https://issues.apache.org/jira/browse/NETBEANS-1613 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Project >Affects Versions: 10.0 >Reporter: Heiko Wenzel >Priority: Minor > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > When using a "Java Modular Project" the editor - context menu action "Select > in Projects" has no effect, i.e. the file is not selected in the > Projects-Navigator. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1454) Editor marks word-break: break-word CSS rule as warning
[
https://issues.apache.org/jira/browse/NETBEANS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748266#comment-16748266
]
Pete Whelpton commented on NETBEANS-1454:
-
break-word is non-standard.
It's not in the CSS3 Text Module specification for word-break:
[https://www.w3.org/TR/css-text-3/#word-break-property]
And Mozilla describe it as being non-standard:
[https://developer.mozilla.org/en-US/docs/Web/CSS/word-break]
Should it be recognised by the parser? My version of FF (64) doesn't appear to
support it yet.
> Editor marks word-break: break-word CSS rule as warning
> ---
>
> Key: NETBEANS-1454
> URL: https://issues.apache.org/jira/browse/NETBEANS-1454
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
>
> CSS Editor showing following css atributes in a rule as a warning:
>
> {code:java}
> .someClass{
> word-break: break-word;
> }
> {code}
> *break-word* value for the *word-break* shows as unsupported.
> https://www.w3schools.com/cssref/css3_pr_word-break.asp
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1455) CSS3 property user-select unsupported
[ https://issues.apache.org/jira/browse/NETBEANS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748255#comment-16748255 ] Pete Whelpton commented on NETBEANS-1455: - I can't see *user-select* in the latest published CSS3 Basic User Interface module spec: [https://www.w3.org/TR/css-ui-3/] It appears in the draft CSS4 Basic User Interface module spec: [https://drafts.csswg.org/css-ui-4/#propdef-user-select] Some browsers appear to have already added support, see MDN: [https://developer.mozilla.org/en-US/docs/Web/CSS/user-select] > CSS3 property user-select unsupported > - > > Key: NETBEANS-1455 > URL: https://issues.apache.org/jira/browse/NETBEANS-1455 > Project: NetBeans > Issue Type: Bug > Components: web - CSS Editor >Affects Versions: 9.0 > Environment: Windows 10 >Reporter: Artur Stępień >Priority: Minor > Labels: easyfix > > CSS3 user-select property is unsupported and shows as a warning -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1457) CSS text-align poroperty value start is unsupported
[
https://issues.apache.org/jira/browse/NETBEANS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748245#comment-16748245
]
Pete Whelpton commented on NETBEANS-1457:
-
Added PR: https://github.com/apache/incubator-netbeans/pull/1093
> CSS text-align poroperty value start is unsupported
> ---
>
> Key: NETBEANS-1457
> URL: https://issues.apache.org/jira/browse/NETBEANS-1457
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix, pull-request-available
> Attachments: textalignerror.PNG
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following code shows as a warning cause of start value for text-align
> property
> {code:java}
> .tooltip {
> text-align: start;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1458) CSS3 perspective property doesn't support pixels value
[
https://issues.apache.org/jira/browse/NETBEANS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748131#comment-16748131
]
Pete Whelpton commented on NETBEANS-1458:
-
Able to replicate in NB 10.0
NB's CSS parser seems to be based on an early version of the CSS3 3D Transforms
specification:
[http://www.w3.org/TR/2009/WD-css3-3d-transforms-20090320/#perspective-property]
and accepts *none* | **
This was changed in a later specification,
[http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/#perspective-property|http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/#perspective-property,]
to be *none* | **
_However_, the perspective property appears to have been removed from the
latest 3D Transforms specification entirely?
Does anybody know if the perspective property is still in CSS3 specification,
perhaps moved to another module?
Even if the perspective property is out of spec now, a lot of browsers seem to
support the perspective property already, so should NB?
!perspectiveerror.PNG!
> CSS3 perspective property doesn't support pixels value
> --
>
> Key: NETBEANS-1458
> URL: https://issues.apache.org/jira/browse/NETBEANS-1458
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
> Attachments: perspectiveerror.PNG
>
>
> The following code causes warning cause of pixels value in perspective
> attribute
> {code:java}
> .carousel-item {
> perspective: 1000px;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1458) CSS3 perspective property doesn't support pixels value
[
https://issues.apache.org/jira/browse/NETBEANS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-1458:
Attachment: perspectiveerror.PNG
> CSS3 perspective property doesn't support pixels value
> --
>
> Key: NETBEANS-1458
> URL: https://issues.apache.org/jira/browse/NETBEANS-1458
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
> Attachments: perspectiveerror.PNG
>
>
> The following code causes warning cause of pixels value in perspective
> attribute
> {code:java}
> .carousel-item {
> perspective: 1000px;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1457) CSS text-align poroperty value start is unsupported
[
https://issues.apache.org/jira/browse/NETBEANS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Whelpton updated NETBEANS-1457:
Attachment: textalignerror.PNG
> CSS text-align poroperty value start is unsupported
> ---
>
> Key: NETBEANS-1457
> URL: https://issues.apache.org/jira/browse/NETBEANS-1457
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
> Attachments: textalignerror.PNG
>
>
> The following code shows as a warning cause of start value for text-align
> property
> {code:java}
> .tooltip {
> text-align: start;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1457) CSS text-align poroperty value start is unsupported
[
https://issues.apache.org/jira/browse/NETBEANS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748015#comment-16748015
]
Pete Whelpton commented on NETBEANS-1457:
-
Able to replicate in NB 10.0.
According to the W3C CSS3 spec
[https://www.w3.org/TR/css-text-3/#text-align-property] text-align can have the
following values:
start | end | left | right | center | justify | match-parent | justify-all
(as well as the standard values of inherit | initial)
The NB css parser seems configured for:
[ [ start | !string ]? [ start | end | left | right | center | justify |
match-parent ] ] | inherit | initial
i.e in NB, *text-align: start right;* will not show valid CSS, but *text-align:
start;* will show as an error. This appears to be the wrong way around.
Confirmed via W3C validator that what NB allows, *text-align: start right;*, is
invalid CSS. Suspect the NB parser was based on an earlier draft of the CSS3
spec
!textalignerror.PNG! ?
> CSS text-align poroperty value start is unsupported
> ---
>
> Key: NETBEANS-1457
> URL: https://issues.apache.org/jira/browse/NETBEANS-1457
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
> Attachments: textalignerror.PNG
>
>
> The following code shows as a warning cause of start value for text-align
> property
> {code:java}
> .tooltip {
> text-align: start;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-1457) CSS text-align poroperty value start is unsupported
[
https://issues.apache.org/jira/browse/NETBEANS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748015#comment-16748015
]
Pete Whelpton edited comment on NETBEANS-1457 at 1/21/19 3:15 PM:
--
Able to replicate in NB 10.0.
According to the W3C CSS3 spec
[https://www.w3.org/TR/css-text-3/#text-align-property] text-align can have the
following values:
start | end | left | right | center | justify | match-parent | justify-all
(as well as the standard values of inherit | initial)
The NB css parser seems configured for:
[ [ start | !string ]? [ start | end | left | right | center | justify |
match-parent ] ] | inherit | initial
i.e in NB, *text-align: start right;* will show as valid CSS, but *text-align:
start;* will show as an error. This appears to be the wrong way around.
Confirmed via W3C validator that what NB allows, *text-align: start right;*, is
invalid CSS. Suspect the NB parser was based on an earlier draft of the CSS3
spec
!textalignerror.PNG! ?
was (Author: peedeeboy):
Able to replicate in NB 10.0.
According to the W3C CSS3 spec
[https://www.w3.org/TR/css-text-3/#text-align-property] text-align can have the
following values:
start | end | left | right | center | justify | match-parent | justify-all
(as well as the standard values of inherit | initial)
The NB css parser seems configured for:
[ [ start | !string ]? [ start | end | left | right | center | justify |
match-parent ] ] | inherit | initial
i.e in NB, *text-align: start right;* will not show valid CSS, but *text-align:
start;* will show as an error. This appears to be the wrong way around.
Confirmed via W3C validator that what NB allows, *text-align: start right;*, is
invalid CSS. Suspect the NB parser was based on an earlier draft of the CSS3
spec
!textalignerror.PNG! ?
> CSS text-align poroperty value start is unsupported
> ---
>
> Key: NETBEANS-1457
> URL: https://issues.apache.org/jira/browse/NETBEANS-1457
> Project: NetBeans
> Issue Type: Bug
> Components: web - CSS Editor
>Affects Versions: 9.0
> Environment: Windows 10
>Reporter: Artur Stępień
>Priority: Minor
> Labels: easyfix
> Attachments: textalignerror.PNG
>
>
> The following code shows as a warning cause of start value for text-align
> property
> {code:java}
> .tooltip {
> text-align: start;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-1613) "Select in projects" has no effect
[ https://issues.apache.org/jira/browse/NETBEANS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747947#comment-16747947 ] Pete Whelpton commented on NETBEANS-1613: - PR has been merged. So hopefully this can be marked as Resolved? > "Select in projects" has no effect > -- > > Key: NETBEANS-1613 > URL: https://issues.apache.org/jira/browse/NETBEANS-1613 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Project >Affects Versions: 10.0 >Reporter: Heiko Wenzel >Priority: Minor > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > When using a "Java Modular Project" the editor - context menu action "Select > in Projects" has no effect, i.e. the file is not selected in the > Projects-Navigator. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-1807) PHP Debugging with Chrome ClassNotFoundException Issue
[ https://issues.apache.org/jira/browse/NETBEANS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747455#comment-16747455 ] Pete Whelpton edited comment on NETBEANS-1807 at 1/20/19 12:55 PM: --- I was able to replicate, to a degree. In my case, the exception is only thrown the *first* time a PHP statement is running in debug mode in Chrome w/ PHP internal webserver. Debugging still seems to work despite the exception. Subsequent debugging sessions in Chrome work without issue Netbeans: Apache NetBeans IDE 10.0 (Build incubator-netbeans-release-380-on-20181217) Java: OpenJDK 11.0.1+13 PHP: 7.3.1 XDebug: xdebug-2.7.0beta1-7.3-vc15-nts-x86_64 Steps to replicate: # Install PHP 7.3.1 with XDebug .dll in the /ext directory # Create amend php.ini file with standard XDebug settings # Create a new PHP project in NB 10.0 with an index.php file # index.php should be a basic HTML5 page with in the # Amend project properties > run configuration to use PHP Built - in webserver on localhost:9000 # Start debugging index.php file # Step through over statements -> as soon as the phpinfo(); statement is stepped over, the Exception will be thrown. It is silent, so keep an eye on notifications window # Subsequent runs through will not throw Exception was (Author: peedeeboy): I was able to replicate, to a degree. In my case, the exception is only thrown the *first* time a PHP statement is running in debug mode in Chrome w/ PHP internal webserver. Debugging still seems to work despite the exception. Subsequent debugging sessions in Chrome Netbeans: Apache NetBeans IDE 10.0 (Build incubator-netbeans-release-380-on-20181217) Java: OpenJDK 11.0.1+13 PHP: 7.3.1 XDebug: xdebug-2.7.0beta1-7.3-vc15-nts-x86_64 Steps to replicate: # Install PHP 7.3.1 with XDebug .dll in the /ext directory # Create amend php.ini file with standard XDebug settings # Create a new PHP project in NB 10.0 with an index.php file # index.php should be a basic HTML5 page with in the # Amend project properties > run configuration to use PHP Built - in webserver on localhost:9000 # Start debugging index.php file # Step through over statements -> as soon as the phpinfo(); statement is stepped over, the Exception will be thrown. It is silent, so keep an eye on notifications window # Subsequent runs through will not throw Exception > PHP Debugging with Chrome ClassNotFoundException Issue > -- > > Key: NETBEANS-1807 > URL: https://issues.apache.org/jira/browse/NETBEANS-1807 > Project: NetBeans > Issue Type: Bug > Components: php - Debugger >Affects Versions: 10.0 > Environment: Product Version = Apache NetBeans IDE 10.0 (Build > incubator-netbeans-release-380-on-20181217) > Operating System = Windows 10 version 10.0 running on amd64 > Java; VM; Vendor = 11.0.1; Java HotSpot(TM) 64-Bit Server VM 11.0.1+13-LTS; > Oracle Corporation > Runtime = Java(TM) SE Runtime Environment 11.0.1+13-LTS > Java Home = C:\Program Files\Java\jdk-11.0.1 >Reporter: Shannon Cole >Priority: Minor > > When attempting to launch debugging with chrome the following error occurs. > Debugging does work with Internet Explorer. > SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor > org.netbeans.modules.netserver.websocket.WebSocketServerImpl > java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:197) > Caused: java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter > starting from ModuleCL@36584abc[org.netbeans.modules.netserver] with possible > defining loaders [ModuleCL@5255cea7[org.netbeans.modules.xml.jaxb.api]] and > declared parents [org.netbeans.JarClassLoader@5c484e64, > ModuleCL@390f8b48[org.netbeans.api.annotations.common]] > at org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:199) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > Caused: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter > at > org.netbeans.modules.netserver.websocket.AbstractWSHandler7.generateAcceptKey(AbstractWSHandler7.java:231) > at > org.netbeans.modules.netserver.websocket.WebSocketHandler7.createAcceptKey(WebSocketHandler7.java:116) > at > org.netbeans.modules.netserver.websocket.WebSocketHandler7.sendHandshake(WebSocketHandler7.java:44) > at >
[jira] [Commented] (NETBEANS-1807) PHP Debugging with Chrome ClassNotFoundException Issue
[ https://issues.apache.org/jira/browse/NETBEANS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747455#comment-16747455 ] Pete Whelpton commented on NETBEANS-1807: - I was able to replicate, to a degree. In my case, the exception is only thrown the *first* time a PHP statement is running in debug mode in Chrome w/ PHP internal webserver. Debugging still seems to work despite the exception. Subsequent debugging sessions in Chrome Netbeans: Apache NetBeans IDE 10.0 (Build incubator-netbeans-release-380-on-20181217) Java: OpenJDK 11.0.1+13 PHP: 7.3.1 XDebug: xdebug-2.7.0beta1-7.3-vc15-nts-x86_64 Steps to replicate: # Install PHP 7.3.1 with XDebug .dll in the /ext directory # Create amend php.ini file with standard XDebug settings # Create a new PHP project in NB 10.0 with an index.php file # index.php should be a basic HTML5 page with in the # Amend project properties > run configuration to use PHP Built - in webserver on localhost:9000 # Start debugging index.php file # Step through over statements -> as soon as the phpinfo(); statement is stepped over, the Exception will be thrown. It is silent, so keep an eye on notifications window # Subsequent runs through will not throw Exception > PHP Debugging with Chrome ClassNotFoundException Issue > -- > > Key: NETBEANS-1807 > URL: https://issues.apache.org/jira/browse/NETBEANS-1807 > Project: NetBeans > Issue Type: Bug > Components: php - Debugger >Affects Versions: 10.0 > Environment: Product Version = Apache NetBeans IDE 10.0 (Build > incubator-netbeans-release-380-on-20181217) > Operating System = Windows 10 version 10.0 running on amd64 > Java; VM; Vendor = 11.0.1; Java HotSpot(TM) 64-Bit Server VM 11.0.1+13-LTS; > Oracle Corporation > Runtime = Java(TM) SE Runtime Environment 11.0.1+13-LTS > Java Home = C:\Program Files\Java\jdk-11.0.1 >Reporter: Shannon Cole >Priority: Minor > > When attempting to launch debugging with chrome the following error occurs. > Debugging does work with Internet Explorer. > SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor > org.netbeans.modules.netserver.websocket.WebSocketServerImpl > java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:197) > Caused: java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter > starting from ModuleCL@36584abc[org.netbeans.modules.netserver] with possible > defining loaders [ModuleCL@5255cea7[org.netbeans.modules.xml.jaxb.api]] and > declared parents [org.netbeans.JarClassLoader@5c484e64, > ModuleCL@390f8b48[org.netbeans.api.annotations.common]] > at org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:199) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > Caused: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter > at > org.netbeans.modules.netserver.websocket.AbstractWSHandler7.generateAcceptKey(AbstractWSHandler7.java:231) > at > org.netbeans.modules.netserver.websocket.WebSocketHandler7.createAcceptKey(WebSocketHandler7.java:116) > at > org.netbeans.modules.netserver.websocket.WebSocketHandler7.sendHandshake(WebSocketHandler7.java:44) > at > org.netbeans.modules.netserver.websocket.WebSocketServerImpl$WebSocketHandler.initHandler(WebSocketServerImpl.java:226) > at > org.netbeans.modules.netserver.websocket.WebSocketServerImpl$WebSocketHandler.handshake(WebSocketServerImpl.java:197) > at > org.netbeans.modules.netserver.websocket.WebSocketServerImpl$WebSocketHandler.read(WebSocketServerImpl.java:186) > at > org.netbeans.modules.netserver.SocketFramework.readData(SocketFramework.java:155) > at > org.netbeans.modules.netserver.SocketFramework.process(SocketFramework.java:129) > at org.netbeans.modules.netserver.SocketServer.process(SocketServer.java:82) > at > org.netbeans.modules.netserver.SocketFramework.doRun(SocketFramework.java:113) > at org.netbeans.modules.netserver.SocketServer.run(SocketServer.java:53) > at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) > at > org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) > [catch] at > org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) > INFO [org.netbeans.core.execution.Install]: KILL_PENDING_TASKS > INFO [org.netbeans.core.netigso.Netigso]: bundle >
