[jira] [Comment Edited] (NETBEANS-6163) Maven does not set generated source roots correctly

2022-01-12 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474988#comment-17474988
 ] 

Steven Swor edited comment on NETBEANS-6163 at 1/12/22, 10:10 PM:
--

[~taps] thanks for the screenshot, but what I was really after was, "Is it 
written down somewhere *in the maven documentation* (i.e. a page under 
https://maven.apache.org) how plugins that generate sources should behave, or 
is this just 'common knowledge' among *maven* plugin developers?"


was (Author: sworisbreathing):
[~taps] thanks for the screenshot, but what I was really after was, "Is it 
written down somewhere *in the maven documentation* (i.e. a page under 
https://maven.apache.org) how plugins that generate sources should behave, or 
is this just 'common knowledge' among plugin developers?"

> Maven does not set generated source roots correctly
> ---
>
> Key: NETBEANS-6163
> URL: https://issues.apache.org/jira/browse/NETBEANS-6163
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
> Attachments: image-2022-01-12-16-50-02-502.png
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Clone and build [https://github.com/dsyer/native-image-debug]
> Open the project in NetBeans and see that under {{Generated Sources}} there 
> are packages like: {{src.main.java.org.springframework.aot}}, etc.
> The initial {{src/main/java}} should not be included in the source root.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6163) Maven does not set generated source roots correctly

2022-01-12 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474988#comment-17474988
 ] 

Steven Swor commented on NETBEANS-6163:
---

[~taps] thanks for the screenshot, but what I was really after was, "Is it 
written down somewhere *in the maven documentation* (i.e. a page under 
https://maven.apache.org) how plugins that generate sources should behave, or 
is this just 'common knowledge' among plugin developers?"

> Maven does not set generated source roots correctly
> ---
>
> Key: NETBEANS-6163
> URL: https://issues.apache.org/jira/browse/NETBEANS-6163
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
> Attachments: image-2022-01-12-16-50-02-502.png
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Clone and build [https://github.com/dsyer/native-image-debug]
> Open the project in NetBeans and see that under {{Generated Sources}} there 
> are packages like: {{src.main.java.org.springframework.aot}}, etc.
> The initial {{src/main/java}} should not be included in the source root.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6163) Maven does not set generated source roots correctly

2022-01-11 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473203#comment-17473203
 ] 

Steven Swor commented on NETBEANS-6163:
---

[~taps] Is the maven plugin really behaving inappropriately here? Is it written 
down somewhere how plugins that generate sources should behave, or is this just 
"common knowledge" among plugin developers? The maven build seems to be fine 
with how these plugins behave. It's only NetBeans that can't seem to make heads 
or tails of it.

What's wrong with having NetBeans pick up the generated sources from maven 
instead of making an assumption about how plugins are going to behave?

> Maven does not set generated source roots correctly
> ---
>
> Key: NETBEANS-6163
> URL: https://issues.apache.org/jira/browse/NETBEANS-6163
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Clone and build [https://github.com/dsyer/native-image-debug]
> Open the project in NetBeans and see that under {{Generated Sources}} there 
> are packages like: {{src.main.java.org.springframework.aot}}, etc.
> The initial {{src/main/java}} should not be included in the source root.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6163) Maven does not set generated source roots correctly

2022-01-10 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472445#comment-17472445
 ] 

Steven Swor edited comment on NETBEANS-6163 at 1/11/22, 4:28 AM:
-

There's a similar issue with openapi-generator-maven-plugin... it generates a 
full maven/gradle project structure under generated-sources (with both a 
build.gradle *and* a pom.xml). In that setup, netbeans completely barfs on the 
generated sources and doesn't render them at all in the projects window.

{quote}
In any case, netbeans shouldn't try to second guess the maven project 
configuration, but rather tap into the maven model intercepting the source 
roots during a 'priming build'.
{quote}

I believe this should fix the issue with the openapi generator plugin as well.


was (Author: sworisbreathing):
There's a similar issue with openapi-generator-maven-plugin... it generates a 
full maven/gradle project structure under generated-sources (with both a 
build.gradle *and* a pom.xml). In that setup, netbeans completely barfs on the 
generated sources and doesn't render them at all.

{quote}
In any case, netbeans shouldn't try to second guess the maven project 
configuration, but rather tap into the maven model intercepting the source 
roots during a 'priming build'.
{quote}

I believe this should fix the issue with the openapi generator plugin as well.

> Maven does not set generated source roots correctly
> ---
>
> Key: NETBEANS-6163
> URL: https://issues.apache.org/jira/browse/NETBEANS-6163
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Clone and build [https://github.com/dsyer/native-image-debug]
> Open the project in NetBeans and see that under {{Generated Sources}} there 
> are packages like: {{src.main.java.org.springframework.aot}}, etc.
> The initial {{src/main/java}} should not be included in the source root.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-6163) Maven does not set generated source roots correctly

2022-01-10 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472445#comment-17472445
 ] 

Steven Swor commented on NETBEANS-6163:
---

There's a similar issue with openapi-generator-maven-plugin... it generates a 
full maven/gradle project structure under generated-sources (with both a 
build.gradle *and* a pom.xml). In that setup, netbeans completely barfs on the 
generated sources and doesn't render them at all.

{quote}
In any case, netbeans shouldn't try to second guess the maven project 
configuration, but rather tap into the maven model intercepting the source 
roots during a 'priming build'.
{quote}

I believe this should fix the issue with the openapi generator plugin as well.

> Maven does not set generated source roots correctly
> ---
>
> Key: NETBEANS-6163
> URL: https://issues.apache.org/jira/browse/NETBEANS-6163
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Reporter: Martin Entlicher
>Assignee: Martin Entlicher
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Clone and build [https://github.com/dsyer/native-image-debug]
> Open the project in NetBeans and see that under {{Generated Sources}} there 
> are packages like: {{src.main.java.org.springframework.aot}}, etc.
> The initial {{src/main/java}} should not be included in the source root.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
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-4997) MS Edge defaultBrowserExecutable command not working with file schema in the url

2021-10-05 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424769#comment-17424769
 ] 

Steven Swor edited comment on NETBEANS-4997 at 10/6/21, 2:18 AM:
-

I've just raised a [PR #3215|https://github.com/apache/netbeans/pull/3215] to 
update the command for opening URLs in Edge Chromium.

Note that my solution is somewhat different from the workaround offered in the 
JIRA description.


was (Author: sworisbreathing):
I've just raised a [PR #3215|https://github.com/apache/netbeans/pull/3215] to 
update the command for opening URLs in Edge Chromium.

> MS Edge defaultBrowserExecutable command not working with file schema in the 
> url
> 
>
> Key: NETBEANS-4997
> URL: https://issues.apache.org/jira/browse/NETBEANS-4997
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Niya Omerska
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When using Microsoft Edge as browser for loading help content and passing URL 
> which points to a local file (i.e. of the type 
> *file:///C:*) the browser is opened but the HTML is not 
> loaded. 
> *Root cause*: 
>  * Library:  org-netbeans-modules-extbrowser-RELEASE112.jar
>  * Class: MicrosoftEdgeBrowser.java
>  * Method: defaultBrowserExecutable
>  * params is set to */C start microsoft-edge:\{URL}*. However this command 
> does not work for file: scheme (for reference: 
> [https://stackoverflow.com/questions/31164253/how-to-open-url-in-microsoft-edge-from-the-command-line]
>  )
>  
> *Workaround:*
> Params is set to: */C start 
> shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge \{URL}* 
> (for reference: 
> [https://stackoverflow.com/questions/44155087/how-to-open-local-html-file-with-ms-edge]
>  )



--
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-4997) MS Edge defaultBrowserExecutable command not working with file schema in the url

2021-10-05 Thread Steven Swor (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424769#comment-17424769
 ] 

Steven Swor commented on NETBEANS-4997:
---

I've just raised a [PR #3215|https://github.com/apache/netbeans/pull/3215] to 
update the command for opening URLs in Edge Chromium.

> MS Edge defaultBrowserExecutable command not working with file schema in the 
> url
> 
>
> Key: NETBEANS-4997
> URL: https://issues.apache.org/jira/browse/NETBEANS-4997
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Niya Omerska
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When using Microsoft Edge as browser for loading help content and passing URL 
> which points to a local file (i.e. of the type 
> *file:///C:*) the browser is opened but the HTML is not 
> loaded. 
> *Root cause*: 
>  * Library:  org-netbeans-modules-extbrowser-RELEASE112.jar
>  * Class: MicrosoftEdgeBrowser.java
>  * Method: defaultBrowserExecutable
>  * params is set to */C start microsoft-edge:\{URL}*. However this command 
> does not work for file: scheme (for reference: 
> [https://stackoverflow.com/questions/31164253/how-to-open-url-in-microsoft-edge-from-the-command-line]
>  )
>  
> *Workaround:*
> Params is set to: */C start 
> shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge \{URL}* 
> (for reference: 
> [https://stackoverflow.com/questions/44155087/how-to-open-local-html-file-with-ms-edge]
>  )



--
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