[jira] [Commented] (NETBEANS-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-29 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-2015:
---

IMO, it's an issue with paths:

When editing, the Bundle.properties file is obviously found, otherwise parsing 
would show error bulbs. So I'd state "Source path includes resources".

When compiling the first time, resources are not available during compilation, 
so resources are obviously not part of the compile class path. On second 
compile, the Bundle.properties already have been copied to target/classes, so 
they're found there. So I'd state "Compile class path includes target/classes, 
but not src/main/resources".

So the problem here is missing resources in compilation phase.

> Bundle.properties not found in NB Module project using Maven infrastructure
> ---
>
> Key: NETBEANS-2015
> URL: https://issues.apache.org/jira/browse/NETBEANS-2015
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: Next
> Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
> build);
> also tested with NB 10 on JDK 9.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Ig ot problems using the following annotation (though it seems to be a 
> general annotation processing problem):
>  
> @TopComponent.OpenActionRegistration( 
>     displayName = "#CTL_CfgEdAction", 
>     preferredID = "CfgEdTopComponent" 
> ) 
> I removed the @NbBundle.Messages in the same source file as it seemed (not 
> further investigated that) to conflict with another one in another component, 
> adding the message to the Bundle.properties file in the same package (but of 
> course in src/main/resources folder).
> While it does not cause problems in the editor, for some unknown reason it 
> causes problems with Maven build structure. Even worse, annotation processing 
> stops after an exception is thrown (Bundle.properties not found), so also no 
> generated-layer.xml file is created.
> When I build my module again, the Build.properties file is found, but still 
> no layer file is generated.
> I've tried to work around the problem using this snippet in my POM, but it 
> failed to work for me: 
>       
> org.apache.maven.plugins 
> maven-resources-plugin 
>     3.1.0 
>      
>      
>     pre-merge-properties 
>     initialize 
>      
>     copy-resources 
>      
>      
> target/classes 
>      
>      
> src/main/resources 
>      
> *.properties 
>      
>      
>      
>      
>      
>      
>     



--
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-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-29 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-2015:
---

There's a side-effect of the workaround: After copying the properties files 
into the generated files, adding new properties automatically (i.e. by creating 
a new label) adds them to the copies instead of the original resources. 
Obviously the generated files take precedence over the resources - this should 
never happen. "Original" artifacts should always take precedence over generated 
ones.

> Bundle.properties not found in NB Module project using Maven infrastructure
> ---
>
> Key: NETBEANS-2015
> URL: https://issues.apache.org/jira/browse/NETBEANS-2015
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: Next
> Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
> build);
> also tested with NB 10 on JDK 9.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Ig ot problems using the following annotation (though it seems to be a 
> general annotation processing problem):
>  
> @TopComponent.OpenActionRegistration( 
>     displayName = "#CTL_CfgEdAction", 
>     preferredID = "CfgEdTopComponent" 
> ) 
> I removed the @NbBundle.Messages in the same source file as it seemed (not 
> further investigated that) to conflict with another one in another component, 
> adding the message to the Bundle.properties file in the same package (but of 
> course in src/main/resources folder).
> While it does not cause problems in the editor, for some unknown reason it 
> causes problems with Maven build structure. Even worse, annotation processing 
> stops after an exception is thrown (Bundle.properties not found), so also no 
> generated-layer.xml file is created.
> When I build my module again, the Build.properties file is found, but still 
> no layer file is generated.
> I've tried to work around the problem using this snippet in my POM, but it 
> failed to work for me: 
>       
> org.apache.maven.plugins 
> maven-resources-plugin 
>     3.1.0 
>      
>      
>     pre-merge-properties 
>     initialize 
>      
>     copy-resources 
>      
>      
> target/classes 
>      
>      
> src/main/resources 
>      
> *.properties 
>      
>      
>      
>      
>      
>      
>     



--
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-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-29 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-2015:
---

Copying Bundle.properties to target/generated-sources/annotations before 
compiling (using maven-resources-plugin) solved the problem. Obviously the 
annotions processors have problems with Maven's folder structure, so this needs 
to be fixed.

Another problem which should be fixed is aborting the whole generation process, 
if one generation fails. Either, every step should do its own error handling 
(so the process can continue), or there should be an explicit message like 
"Generating sources has been abandoned because of this exception" (usually it 
will follow an exception thrown from a generation step).

> Bundle.properties not found in NB Module project using Maven infrastructure
> ---
>
> Key: NETBEANS-2015
> URL: https://issues.apache.org/jira/browse/NETBEANS-2015
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: Next
> Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
> build);
> also tested with NB 10 on JDK 9.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Ig ot problems using the following annotation (though it seems to be a 
> general annotation processing problem):
>  
> @TopComponent.OpenActionRegistration( 
>     displayName = "#CTL_CfgEdAction", 
>     preferredID = "CfgEdTopComponent" 
> ) 
> I removed the @NbBundle.Messages in the same source file as it seemed (not 
> further investigated that) to conflict with another one in another component, 
> adding the message to the Bundle.properties file in the same package (but of 
> course in src/main/resources folder).
> While it does not cause problems in the editor, for some unknown reason it 
> causes problems with Maven build structure. Even worse, annotation processing 
> stops after an exception is thrown (Bundle.properties not found), so also no 
> generated-layer.xml file is created.
> When I build my module again, the Build.properties file is found, but still 
> no layer file is generated.
> I've tried to work around the problem using this snippet in my POM, but it 
> failed to work for me: 
>       
> org.apache.maven.plugins 
> maven-resources-plugin 
>     3.1.0 
>      
>      
>     pre-merge-properties 
>     initialize 
>      
>     copy-resources 
>      
>      
> target/classes 
>      
>      
> src/main/resources 
>      
> *.properties 
>      
>      
>      
>      
>      
>      
>     



--
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-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-29 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-2015:
---

The test project now is at 
[https://github.com/pnabbefeld/ApacheHttpdConfigurator]

It seems, annotations are being processed before resources are moved to the 
classes folder. And generated-layer.xml is not re-generated automatically, if 
auto-generated files have already been created in a previous build.

> Bundle.properties not found in NB Module project using Maven infrastructure
> ---
>
> Key: NETBEANS-2015
> URL: https://issues.apache.org/jira/browse/NETBEANS-2015
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: Next
> Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
> build);
> also tested with NB 10 on JDK 9.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Ig ot problems using the following annotation (though it seems to be a 
> general annotation processing problem):
>  
> @TopComponent.OpenActionRegistration( 
>     displayName = "#CTL_CfgEdAction", 
>     preferredID = "CfgEdTopComponent" 
> ) 
> I removed the @NbBundle.Messages in the same source file as it seemed (not 
> further investigated that) to conflict with another one in another component, 
> adding the message to the Bundle.properties file in the same package (but of 
> course in src/main/resources folder).
> While it does not cause problems in the editor, for some unknown reason it 
> causes problems with Maven build structure. Even worse, annotation processing 
> stops after an exception is thrown (Bundle.properties not found), so also no 
> generated-layer.xml file is created.
> When I build my module again, the Build.properties file is found, but still 
> no layer file is generated.
> I've tried to work around the problem using this snippet in my POM, but it 
> failed to work for me: 
>       
> org.apache.maven.plugins 
> maven-resources-plugin 
>     3.1.0 
>      
>      
>     pre-merge-properties 
>     initialize 
>      
>     copy-resources 
>      
>      
> target/classes 
>      
>      
> src/main/resources 
>      
> *.properties 
>      
>      
>      
>      
>      
>      
>     



--
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-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-29 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-2015:
---

I accidently deleted my sources when I tried to create a repository on Github 
and push them - rebased my local repository instead of merging.  :-/

So, here are the steps to reproduce:
 # Create a NB Module project with Maven infrastructure
 # Create a Window component.
 # Create a Bundle.properties file with CTL_CfgEdAction=Some text
 # Remove the NbBundle.Messages annotation.
 # Try to build.

First time, it will show error messages about the Bundle.properties file. 
Second build it will not show any errors, but also it won't generate a layer 
file.

> Bundle.properties not found in NB Module project using Maven infrastructure
> ---
>
> Key: NETBEANS-2015
> URL: https://issues.apache.org/jira/browse/NETBEANS-2015
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: Next
> Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
> build);
> also tested with NB 10 on JDK 9.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Ig ot problems using the following annotation (though it seems to be a 
> general annotation processing problem):
>  
> @TopComponent.OpenActionRegistration( 
>     displayName = "#CTL_CfgEdAction", 
>     preferredID = "CfgEdTopComponent" 
> ) 
> I removed the @NbBundle.Messages in the same source file as it seemed (not 
> further investigated that) to conflict with another one in another component, 
> adding the message to the Bundle.properties file in the same package (but of 
> course in src/main/resources folder).
> While it does not cause problems in the editor, for some unknown reason it 
> causes problems with Maven build structure. Even worse, annotation processing 
> stops after an exception is thrown (Bundle.properties not found), so also no 
> generated-layer.xml file is created.
> When I build my module again, the Build.properties file is found, but still 
> no layer file is generated.
> I've tried to work around the problem using this snippet in my POM, but it 
> failed to work for me: 
>       
> org.apache.maven.plugins 
> maven-resources-plugin 
>     3.1.0 
>      
>      
>     pre-merge-properties 
>     initialize 
>      
>     copy-resources 
>      
>      
> target/classes 
>      
>      
> src/main/resources 
>      
> *.properties 
>      
>      
>      
>      
>      
>      
>     



--
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-2015) Bundle.properties not found in NB Module project using Maven infrastructure

2019-01-28 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-2015:
-

 Summary: Bundle.properties not found in NB Module project using 
Maven infrastructure
 Key: NETBEANS-2015
 URL: https://issues.apache.org/jira/browse/NETBEANS-2015
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Maven
Affects Versions: Next
 Environment: Linux, release build 382 on JDK 11 (using JDK 8 for the 
build);
also tested with NB 10 on JDK 9.
Reporter: Peter Nabbefeld


Ig ot problems using the following annotation (though it seems to be a general 
annotation processing problem):
 
@TopComponent.OpenActionRegistration( 
    displayName = "#CTL_CfgEdAction", 
    preferredID = "CfgEdTopComponent" 
) 

I removed the @NbBundle.Messages in the same source file as it seemed (not 
further investigated that) to conflict with another one in another component, 
adding the message to the Bundle.properties file in the same package (but of 
course in src/main/resources folder).

While it does not cause problems in the editor, for some unknown reason it 
causes problems with Maven build structure. Even worse, annotation processing 
stops after an exception is thrown (Bundle.properties not found), so also no 
generated-layer.xml file is created.

When I build my module again, the Build.properties file is found, but still no 
layer file is generated.

I've tried to work around the problem using this snippet in my POM, but it 
failed to work for me: 
      
org.apache.maven.plugins 
maven-resources-plugin 
    3.1.0 
     
     
    pre-merge-properties 
    initialize 
     
    copy-resources 
     
     
target/classes 
     
     
src/main/resources 
     
*.properties 
     
     
     
     
     
     
    



--
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-2010) Asterisk in first position of .java file causes Exceptions

2019-01-28 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-2010:
-

 Summary: Asterisk in first position of .java file causes Exceptions
 Key: NETBEANS-2010
 URL: https://issues.apache.org/jira/browse/NETBEANS-2010
 Project: NetBeans
  Issue Type: Bug
  Components: java - Editor
Affects Versions: Next
 Environment: Linux, JDK 8 or 11, release build 382;
Reporter: Peter Nabbefeld


When I remove the first slash character ("/") from a Java file (more exactly: 
from the comment used as licence header, usually), Exceptions are thrown. Thies 
does NOT happen in other text positions (in those position errors are shown, as 
expected).

When looking into IDE log of NetBeans 10.0 (running on JDK 9), I also  see 
those exceptions, but obviously they are not actively shown in a dialog.

 



--
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-2008) *.xml_hidden files deleted when selected

2019-01-27 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-2008:
-

 Summary: *.xml_hidden files deleted when selected
 Key: NETBEANS-2008
 URL: https://issues.apache.org/jira/browse/NETBEANS-2008
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Project
Affects Versions: Next
 Environment: Linux, release build 382 on JDK 9, using JDK 8 for the 
Maven Module project.
Reporter: Peter Nabbefeld


Tried with latest release build (382), but don't think it's only valid for this 
one:

I wanted to deactivate some module, so I added an xml_hidden file to my project 
(which is using Maven infrastructure, but this won't be related, as it seems a 
problem with the file type).

When I click on the file, it is silently deleted, without any message.

BTW, I've not yet found out how to get the file into the created module using 
nbm-maven-plugin (it's probably ignored), but it works when I "trick" it into 
the created nbm file, so this should be supported.



--
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-1638) OSGi support is broken

2018-12-26 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1638:
---

Sorry, I don't understand Your question: Why should OSGi support be disabled? 
My problem is that I want to implement a module which uses dependencies which 
are OSGi modules. For some reason they cannot be installed together with my 
module, and I don't know why.

> OSGi support is broken
> --
>
> Key: NETBEANS-1638
> URL: https://issues.apache.org/jira/browse/NETBEANS-1638
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 9.0, 10.0
>Reporter: Peter Nabbefeld
>Priority: Critical
> Attachments: 
> Updated_felix_to_5_6_10_to_enable_osgi_bundles_for_java_9_and_later_.patch
>
>
> The included Felix jar (in module lib.felix) is outdated and does not work 
> with JDK > 9.
> Included version: 4.2.1
> Current version: 6.0.1
> For a short discussion of the problem see: 
> https://github.com/mojohaus/nbm-maven-plugin/issues/52



--
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-1638) OSGi support is broken

2018-11-13 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1638:
--
Attachment: 
Updated_felix_to_5_6_10_to_enable_osgi_bundles_for_java_9_and_later_.patch

> OSGi support is broken
> --
>
> Key: NETBEANS-1638
> URL: https://issues.apache.org/jira/browse/NETBEANS-1638
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 9.0, 10.0
>Reporter: Peter Nabbefeld
>Priority: Critical
> Attachments: 
> Updated_felix_to_5_6_10_to_enable_osgi_bundles_for_java_9_and_later_.patch
>
>
> The included Felix jar (in module lib.felix) is outdated and does not work 
> with JDK > 9.
> Included version: 4.2.1
> Current version: 6.0.1
> For a short discussion of the problem see: 
> https://github.com/mojohaus/nbm-maven-plugin/issues/52



--
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-1638) OSGi support is broken

2018-11-13 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1638:
---

The patch does not seem to fix my problems, so probably there's also 
insufficient information about how to add OSGi modules. If OSGi dependencies 
work for someone, I'd be lucky to see an example pom file.

> OSGi support is broken
> --
>
> Key: NETBEANS-1638
> URL: https://issues.apache.org/jira/browse/NETBEANS-1638
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 9.0, 10.0
>Reporter: Peter Nabbefeld
>Priority: Critical
> Attachments: 
> Updated_felix_to_5_6_10_to_enable_osgi_bundles_for_java_9_and_later_.patch
>
>
> The included Felix jar (in module lib.felix) is outdated and does not work 
> with JDK > 9.
> Included version: 4.2.1
> Current version: 6.0.1
> For a short discussion of the problem see: 
> https://github.com/mojohaus/nbm-maven-plugin/issues/52



--
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-1638) OSGi support is broken

2018-11-13 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1638:
---

Attached a patch provided by Johannes Boesl on the dev mailing list.

> OSGi support is broken
> --
>
> Key: NETBEANS-1638
> URL: https://issues.apache.org/jira/browse/NETBEANS-1638
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 9.0, 10.0
>Reporter: Peter Nabbefeld
>Priority: Critical
> Attachments: 
> Updated_felix_to_5_6_10_to_enable_osgi_bundles_for_java_9_and_later_.patch
>
>
> The included Felix jar (in module lib.felix) is outdated and does not work 
> with JDK > 9.
> Included version: 4.2.1
> Current version: 6.0.1
> For a short discussion of the problem see: 
> https://github.com/mojohaus/nbm-maven-plugin/issues/52



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-09 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Closing this in favour of NETBEANS-1638 which just focusses on the outdated 
library.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-09 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld closed NETBEANS-1621.
-
Resolution: Invalid

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1638) OSGi support is broken

2018-11-09 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1638:
--
Description: 
The included Felix jar (in module lib.felix) is outdated and does not work with 
JDK > 9.

Included version: 4.2.1

Current version: 6.0.1

For a short discussion of the problem see: 
https://github.com/mojohaus/nbm-maven-plugin/issues/52

  was:
The included Felix jar (in module lib.felix) is outdated and does not work with 
JDK > 9.

Included version: 4.2.1

Current version: 6.0.1


> OSGi support is broken
> --
>
> Key: NETBEANS-1638
> URL: https://issues.apache.org/jira/browse/NETBEANS-1638
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 9.0, 10.0
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> The included Felix jar (in module lib.felix) is outdated and does not work 
> with JDK > 9.
> Included version: 4.2.1
> Current version: 6.0.1
> For a short discussion of the problem see: 
> https://github.com/mojohaus/nbm-maven-plugin/issues/52



--
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-1638) OSGi support is broken

2018-11-09 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1638:
-

 Summary: OSGi support is broken
 Key: NETBEANS-1638
 URL: https://issues.apache.org/jira/browse/NETBEANS-1638
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Module System
Affects Versions: 9.0, 10.0
Reporter: Peter Nabbefeld


The included Felix jar (in module lib.felix) is outdated and does not work with 
JDK > 9.

Included version: 4.2.1

Current version: 6.0.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] [Commented] (NETBEANS-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-08 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

+From nbm-maven-plugin issues:+

AFAIK the felix version currently intgerated with netbeans doesn't work with 
Java9 or later. I did update it in my application to 5.6.10 and now it works.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld edited comment on NETBEANS-1621 at 11/7/18 9:01 PM:


Sorry, but I've always told that there're only these two basic steps involved - 
repeating always the same statement "Provide the steps involved" doesn't change 
that, so I got the feeling to be cared like a child, and that's why You got the 
answer. We should both calm down.

At the end, it turned out, I've missed to check in the nb-configuration file 
containing the platform information needed to compile. The need for it is 
related to the situation described in NETBEANS-1609 (newer JDKs have the 
Generated annotation moved to a sub-package).


was (Author: epdv):
Sorry, but I've always told that there're only these two basic steps involved - 
and I'd expect everybody doing NetBeans development to know how to build and 
run a module. So discussing about wasting time IMHO is wasting time by itself; 
that's not only making You angry, but me too. Just describing every unrelated 
click isn't something professionals should need.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Sorry, but I've always told that there're only these two basic steps involved - 
and I'd expect everybody doing NetBeans development to know how to build and 
run a module. So discussing about wasting time IMHO is wasting time by itself; 
that's not only making You angry, but me too. Just describing every unrelated 
click isn't something professionals should need.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Sorry, nb-configuration file was still missing in repository. :-/

Currently, only using JDK plattform 9 works for me. Probably there could be 
some instructions about building with different JDKs placed at Apache?

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Sorry, accidently forgot to provide the environment: Arch Linux, NB 10.0vc3, 
JDK11 - but I had this problem with NB 9 on JDK 9, too, so it seems probably 
version-independent (probably it even has never been tested/tried).

Project link to github already provided - just build and run - no more specific 
steps.

Or just like for kids:
 # Download project from Github using this URL: 
"https://github.com/pnabbefeld/NbProjectManagement.git";
 # Open the project from its download location.
 # Right click on the main project and choose "Build with dependencies"
 # The project should build sufficiently, otherwise You probably changed the 
repository settings.
 # If You cannot build the project, clean Your repository and reinitialize it.
 # As the main project cannot be run, select the module project, right-click 
and select "Run".
 # You'll see the dialog as shown in the comment above.  :-/

 

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1621:
--
Environment: 
Arch Linux
JDK 11
NetBeans 10.0vc3 

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3 
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Sorry, what do You want from me? I've provided everything, the problem seems 
You cannot compile the module for some unknown reason, while it works fine for 
me.

The steps are simply:
 # Build the module: [https://github.com/pnabbefeld/NbProjectManagement]
 # Start it: An informational dialog appears, saying the (OSGi) modules  
!Bildschirmfoto_2018-11-07_10-09-14.png!

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1621:
--
Attachment: Bildschirmfoto_2018-11-07_10-09-14.png

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: Bildschirmfoto_2018-11-07_10-09-14.png
>
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld edited comment on NETBEANS-1621 at 11/7/18 8:53 AM:


Hm, this shouldn't happen - compiling is no problem at all for me. I only get 
problems starting (i.e. running the module) with the "usual" dialog listing the 
modules missing and two buttons for running without the modules or exiting, so 
no other steps to reproduce than building and running.

Did You build with dependencies? Or, did You by any chance change Your 
repository settings? "maven-compiler-plugin" version 3.8.0 is newer than the 
default value set when creating a module, so it usually needs to be loaded from 
remote repository first time.


was (Author: epdv):
Hm, this shouldn't happen - compiling is no problem at all for me. I only get 
problems starting (i.e. running the module) with the "usual" dialog listing the 
modules missing and two buttons for running without the modules or exiting, so 
no other steps to reproduce than building and running.

Did You build with dependencies? Or, did You by any chance change Your 
repository settings? "maven-compiler-plugin" version 3.8.0 is newer than the 
default value set when creating a module.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1621:
---

Hm, this shouldn't happen - compiling is no problem at all for me. I only get 
problems starting (i.e. running the module) with the "usual" dialog listing the 
modules missing and two buttons for running without the modules or exiting, so 
no other steps to reproduce than building and running.

Did You build with dependencies? Or, did You by any chance change Your 
repository settings? "maven-compiler-plugin" version 3.8.0 is newer than the 
default value set when creating a module.

> OSGi dependencies not loaded/installed together with (maven-based) module
> -
>
> Key: NETBEANS-1621
> URL: https://issues.apache.org/jira/browse/NETBEANS-1621
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 10.0
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Loading a module with OSGi dependencies does not work, the dependent modules 
> are missing.
> For an example, build and try to install this module:
> https://github.com/pnabbefeld/NbProjectManagement



--
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-1620) Reloading a module in Development IDE unloads compatibilty layers

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1620:
---

Of course, other problems like unresolved dependencies MAY lead to the 
installed module causing problems, too. But install/reload should NEVER cause 
platform modules to be unloaded - not even compatibility layers.

> Reloading a module in Development IDE unloads compatibilty layers
> -
>
> Key: NETBEANS-1620
> URL: https://issues.apache.org/jira/browse/NETBEANS-1620
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Unloading of the compatibilty layers results in the IDE partially hanging.
> From IDE.log (logged while reloading module):
> INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
> WARNING [org.openide.filesystems.Ordering]: Not all children in Menu/Window/ 
> marked with the position attribute: 
> [org-netbeans-modules-pm-docstree-PMTopComponent.shadow], but some are: 
> [org-netbeans-modules-project-ui-logical-tab-action.shadow, 
> org-netbeans-modules-project-ui-physical-tab-action.shadow, 
> org-netbeans-modules-favorites-View.shadow, 
> org-netbeans-core-ide-ServicesTabAction.shadow, 
> org-netbeans-modules-navigator-ShowNavigatorAction.shadow, 
> org-netbeans-modules-tasklist-ui-TaskListAction.shadow, 
> org-netbeans-modules-tasks-ui-DashboardTopComponent.shadow, 
> org-netbeans-core-io-ui-IOWindowAction.shadow, 
> SwitchToRecentDocumentAction.shadow, Debug, Profile, Web, Tools, 
> Separator3.instance, ConfigureWindow, 
> org-netbeans-core-windows-actions-ResetWindowsAction.shadow, 
> Separator4.instance, CloseWindowAction.shadow, 
> CloseAllDocumentsAction.shadow, CloseAllButThisAction.shadow, 
> GroupsMenuAction.shadow, DocumentsAction.shadow]
> INFO [org.netbeans.core.startup.NbEvents]: Turning off modules:
>     org.netbeans.api.progress.compat8 [1.50.1 
> incubator-netbeans-release-365-on-20181105]
>     org.netbeans.modules.java.source.compat8 [9.6.1 
> incubator-netbeans-release-365-on-20181105]
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
>     org.netbeans.modules.project.ant.compat8/1 [1.70.1 
> incubator-netbeans-release-365-on-20181105]
>     org.openide.execution.compat8 [9.5.1 
> incubator-netbeans-release-365-on-20181105]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
> in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
> could not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
> in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
> could not be found in SystemClassLoader[671 modules]
> INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
>  
> As You can see, compatibility modules are unloaded but not reloaded (IMO, 
> they shouldn't even get unloaded).
> Since this, IDE doesn't provide Java functionality any more, CNFEs are 
> displayed, and I cannot even close NetBeans.
> The source code of my modules can be found at 
> [https://github.com/pnabbefeld/NbProjectManagement]
> For installation of the module, You'll need to remove the JAXB dependencies 
> (but, please, don't remove the antlr build step and its dependency, otherwise 
> the module won't compile).
> However, this bug should 

[jira] [Updated] (NETBEANS-1620) Reloading a module in Development IDE unloads compatibilty layers

2018-11-07 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1620:
--
Component/s: platform - Module System

> Reloading a module in Development IDE unloads compatibilty layers
> -
>
> Key: NETBEANS-1620
> URL: https://issues.apache.org/jira/browse/NETBEANS-1620
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 10.0
> Environment: Arch Linux
> JDK 11
> NetBeans 10.0vc3
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Unloading of the compatibilty layers results in the IDE partially hanging.
> From IDE.log (logged while reloading module):
> INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
> WARNING [org.openide.filesystems.Ordering]: Not all children in Menu/Window/ 
> marked with the position attribute: 
> [org-netbeans-modules-pm-docstree-PMTopComponent.shadow], but some are: 
> [org-netbeans-modules-project-ui-logical-tab-action.shadow, 
> org-netbeans-modules-project-ui-physical-tab-action.shadow, 
> org-netbeans-modules-favorites-View.shadow, 
> org-netbeans-core-ide-ServicesTabAction.shadow, 
> org-netbeans-modules-navigator-ShowNavigatorAction.shadow, 
> org-netbeans-modules-tasklist-ui-TaskListAction.shadow, 
> org-netbeans-modules-tasks-ui-DashboardTopComponent.shadow, 
> org-netbeans-core-io-ui-IOWindowAction.shadow, 
> SwitchToRecentDocumentAction.shadow, Debug, Profile, Web, Tools, 
> Separator3.instance, ConfigureWindow, 
> org-netbeans-core-windows-actions-ResetWindowsAction.shadow, 
> Separator4.instance, CloseWindowAction.shadow, 
> CloseAllDocumentsAction.shadow, CloseAllButThisAction.shadow, 
> GroupsMenuAction.shadow, DocumentsAction.shadow]
> INFO [org.netbeans.core.startup.NbEvents]: Turning off modules:
>     org.netbeans.api.progress.compat8 [1.50.1 
> incubator-netbeans-release-365-on-20181105]
>     org.netbeans.modules.java.source.compat8 [9.6.1 
> incubator-netbeans-release-365-on-20181105]
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
>     org.netbeans.modules.project.ant.compat8/1 [1.70.1 
> incubator-netbeans-release-365-on-20181105]
>     org.openide.execution.compat8 [9.5.1 
> incubator-netbeans-release-365-on-20181105]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
> in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
> could not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could 
> not be found in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
> in SystemClassLoader[671 modules]
> WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
> org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
> could not be found in SystemClassLoader[671 modules]
> INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
>     org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
>  
> As You can see, compatibility modules are unloaded but not reloaded (IMO, 
> they shouldn't even get unloaded).
> Since this, IDE doesn't provide Java functionality any more, CNFEs are 
> displayed, and I cannot even close NetBeans.
> The source code of my modules can be found at 
> [https://github.com/pnabbefeld/NbProjectManagement]
> For installation of the module, You'll need to remove the JAXB dependencies 
> (but, please, don't remove the antlr build step and its dependency, otherwise 
> the module won't compile).
> However, this bug should occur with any external module.
>  
> So, to reproduce this bug, try the following:
>  # Create/Load a NetBeans module (I'm using source/target 1.8, because AFAIK 
> it's not possible to use newer Java platforms for module developme

[jira] [Created] (NETBEANS-1621) OSGi dependencies not loaded/installed together with (maven-based) module

2018-11-07 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1621:
-

 Summary: OSGi dependencies not loaded/installed together with 
(maven-based) module
 Key: NETBEANS-1621
 URL: https://issues.apache.org/jira/browse/NETBEANS-1621
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Maven
Affects Versions: 10.0
Reporter: Peter Nabbefeld


Loading a module with OSGi dependencies does not work, the dependent modules 
are missing.

For an example, build and try to install this module:

https://github.com/pnabbefeld/NbProjectManagement



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-07 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1609:
--
Issue Type: Bug  (was: Improvement)

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Project, platform - Module System
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-07 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1609:
---

Obviously this bug is caused by unloading the compatibility layer modules, so 
it will be solved together with NETBEANS-1620.

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project, platform - Module System
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1620) Reloading a module in Development IDE unloads compatibilty layers

2018-11-07 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1620:
-

 Summary: Reloading a module in Development IDE unloads 
compatibilty layers
 Key: NETBEANS-1620
 URL: https://issues.apache.org/jira/browse/NETBEANS-1620
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 10.0
 Environment: Arch Linux
JDK 11
NetBeans 10.0vc3
Reporter: Peter Nabbefeld


Unloading of the compatibilty layers results in the IDE partially hanging.

>From IDE.log (logged while reloading module):

INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
    org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
WARNING [org.openide.filesystems.Ordering]: Not all children in Menu/Window/ 
marked with the position attribute: 
[org-netbeans-modules-pm-docstree-PMTopComponent.shadow], but some are: 
[org-netbeans-modules-project-ui-logical-tab-action.shadow, 
org-netbeans-modules-project-ui-physical-tab-action.shadow, 
org-netbeans-modules-favorites-View.shadow, 
org-netbeans-core-ide-ServicesTabAction.shadow, 
org-netbeans-modules-navigator-ShowNavigatorAction.shadow, 
org-netbeans-modules-tasklist-ui-TaskListAction.shadow, 
org-netbeans-modules-tasks-ui-DashboardTopComponent.shadow, 
org-netbeans-core-io-ui-IOWindowAction.shadow, 
SwitchToRecentDocumentAction.shadow, Debug, Profile, Web, Tools, 
Separator3.instance, ConfigureWindow, 
org-netbeans-core-windows-actions-ResetWindowsAction.shadow, 
Separator4.instance, CloseWindowAction.shadow, CloseAllDocumentsAction.shadow, 
CloseAllButThisAction.shadow, GroupsMenuAction.shadow, DocumentsAction.shadow]
INFO [org.netbeans.core.startup.NbEvents]: Turning off modules:
    org.netbeans.api.progress.compat8 [1.50.1 
incubator-netbeans-release-365-on-20181105]
    org.netbeans.modules.java.source.compat8 [9.6.1 
incubator-netbeans-release-365-on-20181105]
    org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]
    org.netbeans.modules.project.ant.compat8/1 [1.70.1 
incubator-netbeans-release-365-on-20181105]
    org.openide.execution.compat8 [9.5.1 
incubator-netbeans-release-365-on-20181105]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
not be found in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could not 
be found in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
could not be found in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$TreeLoaderRegistry could 
not be found in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$ContextEnhancer could not 
be found in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
in SystemClassLoader[671 modules]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.parsing.JavacParser$DuplicateClassRegistry 
could not be found in SystemClassLoader[671 modules]
INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
    org.netbeans.modules.pm.DocsTree [1.0 1.0-20181107 201811070731]

 

As You can see, compatibility modules are unloaded but not reloaded (IMO, they 
shouldn't even get unloaded).

Since this, IDE doesn't provide Java functionality any more, CNFEs are 
displayed, and I cannot even close NetBeans.

The source code of my modules can be found at 
[https://github.com/pnabbefeld/NbProjectManagement]

For installation of the module, You'll need to remove the JAXB dependencies 
(but, please, don't remove the antlr build step and its dependency, otherwise 
the module won't compile).

However, this bug should occur with any external module.

 

So, to reproduce this bug, try the following:
 # Create/Load a NetBeans module (I'm using source/target 1.8, because AFAIK 
it's not possible to use newer Java platforms for module development).
 # Build it, install it into NetBeans ("Install/reload in Development IDE"). 
First time this will work, as no unloading is done.
 # Reload it. Now, the compatibility layers are unloaded, the above described 
behavior can be seen.

If You're running the module, everything will be okay, because the "slave" IDE 
already starts with the updated version of the module.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-

[jira] [Commented] (NETBEANS-1609) @Messages annotation does not work with JDK version >= 10

2018-11-05 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1609:
---

2. Try to install the module into Your IDE - You'll see exceptions thrown in 
Your IDE log (now exception pops up, yet).

3. Try to open a "Project Management" window (first item in "Window" dialog).

4. Exceptions are notified.

5. In the navigation window, there is probably a window titled "PM", but its 
content is a "null" node only, because the Bundle could not be loaded.

6. From my IDE log:

INFO [org.netbeans.core.startup.NbEvents]: Turning off modules:
    org.netbeans.api.progress.compat8 [1.50.1 
incubator-netbeans-release-360-on-20181029]
    org.netbeans.modules.java.source.compat8 [9.6.1 
incubator-netbeans-release-360-on-20181029]
    org.netbeans.modules.pm.DocsTree [1.0 1.0-20181104 201811042218]
    org.netbeans.modules.project.ant.compat8/1 [1.70.1 
incubator-netbeans-release-360-on-20181029]
    org.openide.execution.compat8 [9.5.1 
incubator-netbeans-release-360-on-20181029]
WARNING [org.openide.util.lookup.MetaInfServicesLookup]: 
org.netbeans.modules.java.source.tasklist.CompilerSettings could not be found 
in SystemClassLoader[668 modules]
WARNING [null]: Last record repeated again.
INFO [org.netbeans.core.startup.NbEvents]: Turning on modules:
    org.netbeans.modules.pm.DocsTree [1.0 1.0-20181104 201811042218]

7. Java modules fail; on my Linux system, I cannot even close NetBeans, I've to 
kill it by SIGKILL

 

As You can see in [6], compatibility layer modules get unloaded together with 
my module, but obviously don't get reloaded.

 

 

 

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project, platform - Module System
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-04 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1609:
---

Already added:

https://github.com/pnabbefeld/NbProjectManagement

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project, platform - Module System
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-04 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1609:
--
Component/s: platform - Module System

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project, platform - Module System
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-04 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1609:
---

While NB seems to be happily starting with different JDKs, it has a problem 
with reloading - probably there's a compatibility layer involved, which is 
active only on startup? BTW, I've noticed in the IDE log some messages about 
reloading of one or two IDE modules together with mine (I doubt this should 
happen), and then NetBeans blocks Java development (e.g. cannot build, no code 
completion) because of CNFEs - some resources seem to be missing on 
initialization.

I'll push my project to Github this evening and post the link here.

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-04 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1609:
---

There're 2 possible solutions for the problem:
 # Make the annotation dependent on platform version.
 # Remove it at all. "Generated" has @Retention(SOURCE), so no behavior 
would change.

Well, if the first solution is used, the annotation should be usable for other 
annotation processors, too, so there should be a utility method implemented for 
creating the correct annotation.

TODO:

While this is not an issue for NetBeans, what could be done with sources 
generated by external tasks? Would it be possible to post-process such sources?

> @Messages annotation does not work with JDK version >= 10
> -
>
> Key: NETBEANS-1609
> URL: https://issues.apache.org/jira/browse/NETBEANS-1609
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project
>Affects Versions: 10.0
> Environment: I'm running NB 10.0vc2 on JDK 11.
>Reporter: Peter Nabbefeld
>Priority: Major
>
> The @Messages annotation creates a non-translatable Bundle file, because the 
> package of the @Generated annotation has changed:
>  
> @javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1609) @Messages annotation does not work with JDK version >= 10

2018-11-04 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1609:
-

 Summary: @Messages annotation does not work with JDK version >= 10
 Key: NETBEANS-1609
 URL: https://issues.apache.org/jira/browse/NETBEANS-1609
 Project: NetBeans
  Issue Type: Improvement
  Components: apisupport - Project
Affects Versions: 10.0
 Environment: I'm running NB 10.0vc2 on JDK 11.
Reporter: Peter Nabbefeld


The @Messages annotation creates a non-translatable Bundle file, because the 
package of the @Generated annotation has changed:

 

@javax.annotation.Generated  =>  @javax.annotation.processing.Generated



--
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-1279) Update Xerces Library

2018-09-21 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1279:
---

Hm, the replacement of the jar file is not an issue itself. But some questions 
about infrastructure:
 # It seems, the binaries list uses a key - how do I get this?
 # How do I upload the module after the change?

> Update Xerces Library
> -
>
> Key: NETBEANS-1279
> URL: https://issues.apache.org/jira/browse/NETBEANS-1279
> Project: NetBeans
>  Issue Type: Improvement
>  Components: java - Project
>Affects Versions: 9.0
>Reporter: Peter Nabbefeld
>Priority: Major
>
> When creating a maven plugin module, only xerces-2.8.0 is available, while 
> current version is 2.12.0. As the latest version supports XSD 1.1 features, 
> this is a great improvement which should be available for module development.
>  
> Should be easy to implement.



--
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-996) java.util.regex.PatternSyntaxException: Unexpected internal error near index 7

2018-09-21 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-996:
--

Not sure if that is related, but could You probably add Your .gitignore file 
here? Just asking because of this line:

at org.eclipse.jgit.ignore.IgnoreNode.parse(IgnoreNode.java:114)

> java.util.regex.PatternSyntaxException: Unexpected internal error near index 7
> --
>
> Key: NETBEANS-996
> URL: https://issues.apache.org/jira/browse/NETBEANS-996
> Project: NetBeans
>  Issue Type: Bug
>Reporter: chopin xiao
>Priority: Major
>
> \.idea\
>^
>   at java.base/java.util.regex.Pattern.error(Pattern.java:2010)
>   at java.base/java.util.regex.Pattern.compile(Pattern.java:1779)
>   at java.base/java.util.regex.Pattern.(Pattern.java:1422)
>   at java.base/java.util.regex.Pattern.compile(Pattern.java:1082)
>   at 
> org.eclipse.jgit.ignore.internal.Strings.convertGlob(Strings.java:352)
>   at 
> org.eclipse.jgit.ignore.internal.WildCardMatcher.(WildCardMatcher.java:66)
>   at 
> org.eclipse.jgit.ignore.internal.PathMatcher.createNameMatcher0(PathMatcher.java:145)
>   at 
> org.eclipse.jgit.ignore.internal.PathMatcher.createPathMatcher(PathMatcher.java:127)
>   at 
> org.eclipse.jgit.ignore.FastIgnoreRule.(FastIgnoreRule.java:114)
>   at org.eclipse.jgit.ignore.IgnoreNode.parse(IgnoreNode.java:114)
>   at 
> org.eclipse.jgit.treewalk.WorkingTreeIterator$PerDirectoryIgnoreNode.load(WorkingTreeIterator.java:1166)
>   at 
> org.eclipse.jgit.treewalk.WorkingTreeIterator.getIgnoreNode(WorkingTreeIterator.java:625)
>   at 
> org.eclipse.jgit.treewalk.WorkingTreeIterator.isEntryIgnored(WorkingTreeIterator.java:593)
>   at 
> org.eclipse.jgit.treewalk.WorkingTreeIterator.isEntryIgnored(WorkingTreeIterator.java:576)
>   at 
> org.eclipse.jgit.treewalk.WorkingTreeIterator.isEntryIgnored(WorkingTreeIterator.java:563)
>   at 
> org.netbeans.libs.git.jgit.commands.StatusCommand.run(StatusCommand.java:182)
>   at 
> org.netbeans.libs.git.jgit.commands.GitCommand$1.run(GitCommand.java:57)
>   at 
> org.netbeans.libs.git.jgit.commands.GitCommand$1.run(GitCommand.java:54)
>   at java.base/java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.netbeans.libs.git.jgit.commands.GitCommand.execute(GitCommand.java:54)
>   at org.netbeans.libs.git.GitClient.getStatus(GitClient.java:737)
>   at org.netbeans.modules.git.client.GitClient$26.call(GitClient.java:477)
>   at org.netbeans.modules.git.client.GitClient$26.call(GitClient.java:473)
>   at 
> org.netbeans.modules.git.client.GitClient$CommandInvoker$1$1.call(GitClient.java:933)
>   at 
> org.netbeans.modules.git.client.GitClient$CommandInvoker$1.call(GitClient.java:956)
>   at 
> org.netbeans.modules.git.client.GitClient$CommandInvoker.runMethodIntern(GitClient.java:968)
>   at 
> org.netbeans.modules.git.client.GitClient$CommandInvoker.runMethod(GitClient.java:897)
>   at 
> org.netbeans.modules.git.client.GitClient$CommandInvoker.access$300(GitClient.java:869)
>   at 
> org.netbeans.modules.git.client.GitClient.getStatus(GitClient.java:473)
>   at 
> org.netbeans.modules.git.client.GitClient.getStatus(GitClient.java:469)
>   at 
> org.netbeans.modules.git.FileStatusCache.refreshAllRoots(FileStatusCache.java:210)
>   at 
> org.netbeans.modules.git.FileStatusCache.refreshAllRoots(FileStatusCache.java:170)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor$RefreshTask.run(FilesystemInterceptor.java:669)
> Caused: org.openide.util.RequestProcessor$SlowItem: task failed due to
>   at 
> org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:1459)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor.reScheduleRefresh(FilesystemInterceptor.java:755)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor.access$3300(FilesystemInterceptor.java:73)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor$GitFolderEventsHandler.initializeFiles(FilesystemInterceptor.java:1023)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor$GitFolderEventsHandler.access$2500(FilesystemInterceptor.java:842)
>   at 
> org.netbeans.modules.git.FilesystemInterceptor$GitFolderEventsHandler$1.run(FilesystemInterceptor.java:854)
>   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)



--
This message was sent by A

[jira] [Created] (NETBEANS-1279) Update Xerces Library

2018-09-21 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1279:
-

 Summary: Update Xerces Library
 Key: NETBEANS-1279
 URL: https://issues.apache.org/jira/browse/NETBEANS-1279
 Project: NetBeans
  Issue Type: Improvement
  Components: java - Project
Affects Versions: 9.0
Reporter: Peter Nabbefeld


When creating a maven plugin module, only xerces-2.8.0 is available, while 
current version is 2.12.0. As the latest version supports XSD 1.1 features, 
this is a great improvement which should be available for module development.

 

Should be easy to implement.



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

2018-09-02 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1204:
---

Only differences I can see:
 # Wicket Quickstart uses iso8599-1 encoding instead of utf-8.
 # Wicket 8.0.0 uses web_app_3_1.xsd and version 3.0 instead of web_app_3_0.xsd 
and version 3.0.

> 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] [Updated] (NETBEANS-1204) Make Wicket generated Web-Apps work

2018-09-02 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1204:
--
Description: 
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.

  was:
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; 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.

Summary: Make Wicket generated Web-Apps work  (was: Add support for 
Glassfish 5)

> 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] [Created] (NETBEANS-1204) Add support for Glassfish 5

2018-09-01 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1204:
-

 Summary: Add support for Glassfish 5
 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


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



--
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-1060) Ant-Based Project Type without build script

2018-07-18 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1060:
-

 Summary: Ant-Based Project Type without build script
 Key: NETBEANS-1060
 URL: https://issues.apache.org/jira/browse/NETBEANS-1060
 Project: NetBeans
  Issue Type: Improvement
  Components: projects - Ant Project
Affects Versions: 8.2, 9.0
Reporter: Peter Nabbefeld


Just noticed it might be possible to have a project without any build, like 
some graphics editor.

Therefore, it may be useful to have some configuration data etc., but not a 
build script.

This could be handled using an ant-based project type - but is it also 
possible, to have just no build script? AFAIK, it must just be present.

One of the main advantages IMHO is having a clearly defined project type 
definition within project.xml instead of some other magic. So I'd really like 
to have this clarified, e.g. for this tutorial: 
[https://platform.netbeans.org/tutorials/nbm-projecttypeant.html] (which I'd 
also like to be moved to Apache, of course).

 



--
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-1044) Make bundle keys possible in PaletteItemRegistration

2018-07-14 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1044:
-

 Summary: Make bundle keys possible in PaletteItemRegistration
 Key: NETBEANS-1044
 URL: https://issues.apache.org/jira/browse/NETBEANS-1044
 Project: NetBeans
  Issue Type: Improvement
  Components: platform - Palette
Affects Versions: 8.2, 9.0
Reporter: Peter Nabbefeld


Most annotations I'm aware of allow using bundle keys for display names, 
PaletteItemRegistration does not (i.e. doesn't repect them as key values).

I've created an experimental patch for this, but currently I'm not able to test 
it (because my module needs Web Application capabilities, I'm currently stuck 
at NB 8.2). So this is mostly documentational.



--
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-1035) Make HTML api public

2018-07-11 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-1035:
---

Thank You, Geertjan! I've not clearly enough expressed my point of view ... I 
was argueing from a community view. From that, a widely used module should be 
made available publicly. But You're also right, of course, from stability view 
a friend module isn't ready to be published. I guess, the right starting point 
for a discussion about this topic should be dev mailing list?

Another point is, I'd need friend relation also for NB 8.2, as I cannot develop 
a web plugin in 9.0.

Also, as I'm using Maven: Is there already a Maven repo for NB 9.0 available?

 

> Make HTML api public
> 
>
> Key: NETBEANS-1035
> URL: https://issues.apache.org/jira/browse/NETBEANS-1035
> Project: NetBeans
>  Issue Type: Wish
>  Components: web - HTML Editor
>Affects Versions: 8.2, 9.0
> Environment: Linux
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> There are already 21 "friends" using html.editor and html.editor.lib - IMHO a 
> good indicator it should be public.
>  
> However, I do need the API for implementing a Wicket module, so , if it will 
> take too long to make it public, probably make 
> org.netbeans.modules.web.wicket another friend of these modules and tell me 
> how to use it within a Maven based NetBeans module.



--
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-1035) Make HTML api public

2018-07-10 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-1035:
--
Issue Type: Wish  (was: Task)

> Make HTML api public
> 
>
> Key: NETBEANS-1035
> URL: https://issues.apache.org/jira/browse/NETBEANS-1035
> Project: NetBeans
>  Issue Type: Wish
>  Components: web - HTML Editor
>Affects Versions: 8.2, 9.0
> Environment: Linux
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> There are already 21 "friends" using html.editor and html.editor.lib - IMHO a 
> good indicator it should be public.
>  
> However, I do need the API for implementing a Wicket module, so , if it will 
> take too long to make it public, probably make 
> org.netbeans.modules.web.wicket another friend of these modules and tell me 
> how to use it within a Maven based NetBeans module.



--
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-1035) Make HTML api public

2018-07-10 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-1035:
-

 Summary: Make HTML api public
 Key: NETBEANS-1035
 URL: https://issues.apache.org/jira/browse/NETBEANS-1035
 Project: NetBeans
  Issue Type: Task
  Components: web - HTML Editor
Affects Versions: 8.2, 9.0
 Environment: Linux
Reporter: Peter Nabbefeld


There are already 21 "friends" using html.editor and html.editor.lib - IMHO a 
good indicator it should be public.

 

However, I do need the API for implementing a Wicket module, so , if it will 
take too long to make it public, probably make org.netbeans.modules.web.wicket 
another friend of these modules and tell me how to use it within a Maven based 
NetBeans module.



--
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-989) Exception in annotation processing

2018-06-24 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-989:
--

I've already fixed my problem with the plugin code, so I can say the exception 
is thrown because of my bug.

I've had accidently (by using replace for all source files) created this 
assignment:

public class WicketSupportConstants {

    public static final String MIME_TYPE_HTML = 
WicketSupportConstants.MIME_TYPE_HTML;

}

This is of course wrong. However, using this field in an annotation shouldn't 
throw any exception.

> Exception in annotation processing
> --
>
> Key: NETBEANS-989
> URL: https://issues.apache.org/jira/browse/NETBEANS-989
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
> Environment: Linux; Release build 316
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: WicketTagNavigator_31.dump
>
>
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Caused: java.lang.annotation.AnnotationTypeMismatchException: Incorrectly 
> typed data found for annotation element public abstract java.lang.String 
> org.netbeans.spi.navigator.NavigatorPanel$Registration.mimeType() (Found data 
> of type java.lang.String)
>     at 
> jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:270)
>     at 
> java.base/sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:85)
>     at com.sun.proxy.$Proxy76.mimeType(Unknown Source)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.register(NavigatorPanelRegistrationProcessor.java:92)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.handleProcess(NavigatorPanelRegistrationProcessor.java:76)
>     at 
> org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:968)
> Caused: com.sun.tools.javac.processing.AnnotationProcessingError
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:980)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:884)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:108)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1206)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1246)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavaCompiler.processAnnotations(NBJavaCompiler.java:56)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1143)
>     at 
> jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:332)
>     at 
> jdk.compiler/com.sun.tools.javac.api.JavacTa

[jira] [Updated] (NETBEANS-989) Exception in annotation processing

2018-06-24 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-989:
-
Priority: Major  (was: Critical)

> Exception in annotation processing
> --
>
> Key: NETBEANS-989
> URL: https://issues.apache.org/jira/browse/NETBEANS-989
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
> Environment: Linux; Release build 316
>Reporter: Peter Nabbefeld
>Priority: Major
> Attachments: WicketTagNavigator_31.dump
>
>
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Caused: java.lang.annotation.AnnotationTypeMismatchException: Incorrectly 
> typed data found for annotation element public abstract java.lang.String 
> org.netbeans.spi.navigator.NavigatorPanel$Registration.mimeType() (Found data 
> of type java.lang.String)
>     at 
> jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:270)
>     at 
> java.base/sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:85)
>     at com.sun.proxy.$Proxy76.mimeType(Unknown Source)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.register(NavigatorPanelRegistrationProcessor.java:92)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.handleProcess(NavigatorPanelRegistrationProcessor.java:76)
>     at 
> org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:968)
> Caused: com.sun.tools.javac.processing.AnnotationProcessingError
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:980)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:884)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:108)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1206)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1246)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavaCompiler.processAnnotations(NBJavaCompiler.java:56)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1143)
>     at 
> jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:332)
>     at 
> jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:266)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:620)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:481)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:135)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:608)
>     at 
> org.netbe

[jira] [Commented] (NETBEANS-989) Exception in annotation processing

2018-06-24 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-989:
--

I'm getting the above exception when opening the file (e.g. automatically after 
starting NB). It contains the following annotation:

@NavigatorPanel.Registration(
    mimeType = WicketSupportConstants.MIME_TYPE_HTML,
    displayName = "#LBL_NAME"
)

I've just noticed an error in the constant definition (which hasn't been shown, 
i.e. no red balloon), but that shouldn't cause an exception to be thrown, but 
it's not critical then, of course.

> Exception in annotation processing
> --
>
> Key: NETBEANS-989
> URL: https://issues.apache.org/jira/browse/NETBEANS-989
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
> Environment: Linux; Release build 316
>Reporter: Peter Nabbefeld
>Priority: Critical
> Attachments: WicketTagNavigator_31.dump
>
>
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Annotation: An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> An error occurred during parsing of 
> '/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
>  Please report a bug against java/source and attach dump file 
> '/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
> Caused: java.lang.annotation.AnnotationTypeMismatchException: Incorrectly 
> typed data found for annotation element public abstract java.lang.String 
> org.netbeans.spi.navigator.NavigatorPanel$Registration.mimeType() (Found data 
> of type java.lang.String)
>     at 
> jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:270)
>     at 
> java.base/sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:85)
>     at com.sun.proxy.$Proxy76.mimeType(Unknown Source)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.register(NavigatorPanelRegistrationProcessor.java:92)
>     at 
> org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.handleProcess(NavigatorPanelRegistrationProcessor.java:76)
>     at 
> org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:968)
> Caused: com.sun.tools.javac.processing.AnnotationProcessingError
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:980)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:884)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:108)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1206)
>     at 
> jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1246)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavaCompiler.processAnnotations(NBJavaCompiler.java:56)
>     at 
> jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1143)
>     at 
> jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:332)
>     at 
> jdk.compiler/co

[jira] [Created] (NETBEANS-989) Exception in annotation processing

2018-06-24 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-989:


 Summary: Exception in annotation processing
 Key: NETBEANS-989
 URL: https://issues.apache.org/jira/browse/NETBEANS-989
 Project: NetBeans
  Issue Type: Bug
  Components: java - Editor
 Environment: Linux; Release build 316
Reporter: Peter Nabbefeld
 Attachments: WicketTagNavigator_31.dump

Annotation: An error occurred during parsing of 
'/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
 Please report a bug against java/source and attach dump file 
'/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
Annotation: An error occurred during parsing of 
'/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
 Please report a bug against java/source and attach dump file 
'/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
Annotation: An error occurred during parsing of 
'/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
 Please report a bug against java/source and attach dump file 
'/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
An error occurred during parsing of 
'/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
 Please report a bug against java/source and attach dump file 
'/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
An error occurred during parsing of 
'/home/peter/NetBeansProjects/web.wicket/src/main/java/org/netbeans/modules/web/wicket/navigator/WicketTagNavigator.java'.
 Please report a bug against java/source and attach dump file 
'/home/peter/.netbeans/9.0rc/var/log/WicketTagNavigator_31.dump'.
Caused: java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed 
data found for annotation element public abstract java.lang.String 
org.netbeans.spi.navigator.NavigatorPanel$Registration.mimeType() (Found data 
of type java.lang.String)
    at 
jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:270)
    at 
java.base/sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:85)
    at com.sun.proxy.$Proxy76.mimeType(Unknown Source)
    at 
org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.register(NavigatorPanelRegistrationProcessor.java:92)
    at 
org.netbeans.modules.navigator.NavigatorPanelRegistrationProcessor.handleProcess(NavigatorPanelRegistrationProcessor.java:76)
    at 
org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:968)
Caused: com.sun.tools.javac.processing.AnnotationProcessingError
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:980)
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:884)
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:108)
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1206)
    at 
jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
    at 
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1246)
    at 
org.netbeans.lib.nbjavac.services.NBJavaCompiler.processAnnotations(NBJavaCompiler.java:56)
    at 
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1143)
    at 
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:332)
    at 
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:266)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:620)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:481)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:135)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:608)
    at 
org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:239)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:775)
    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:702)
[catch] at 
org.

[jira] [Commented] (NETBEANS-963) java.lang.AssertionError: Debugger lock taken in AWT Event Queue!

2018-06-19 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-963:
--

Did You use the "String value" column in variables view? The Exception is only 
thrown, if this column is active. You need to either move the cursor over the 
string value and wait as You'd do for tooltips or to click on the edit button 
of the string value. Also, it must be a string value of an object, primitive 
data types don't have problems.

> java.lang.AssertionError: Debugger lock taken in AWT Event Queue!
> -
>
> Key: NETBEANS-963
> URL: https://issues.apache.org/jira/browse/NETBEANS-963
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 9.0
> Environment: Linux; Release Build 316
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> When I've selected the "String Value" column in Variables view of the Java 
> debugger, the following exception is thrown even if I just move the cursor 
> over the string value.
> This does only happen for object values; primitive values do not seem to be 
> affected.
> Probably it's related to tooltips, as those are shown for primitive values, 
> while object values throw an exception.
> As this makes it impossible to show and review large strings and thus makes 
> debugging harder, I've set the status to "Blocker".
>  
> java.lang.AssertionError: Debugger lock taken in AWT Event Queue!
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl$DebuggerReentrantReadWriteLock$DebuggerReadLock.lock(JPDADebuggerImpl.java:2675)
>     at 
> org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl$ThreadReentrantReadWriteLock$ThreadWriteLock.lock(JPDAThreadImpl.java:2555)
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1066)
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1008)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:496)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:460)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:424)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.VariablesTableModel.getValueAt(VariablesTableModel.java:108)
>     at 
> org.netbeans.spi.viewmodel.Models$DelegatingTableModel.getValueAt(Models.java:2249)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.NumericDisplayFilter.getValueAt(NumericDisplayFilter.java:112)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.VariablesTreeModelFilter.getValueAt(VariablesTreeModelFilter.java:530)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.PendingActionsFilter.getValueAt(PendingActionsFilter.java:108)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundModel.getValueAt(Models.java:4566)
>     at 
> org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.updateShortDescription(TreeModelNode.java:2102)
>     at 
> org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.getShortDescription(TreeModelNode.java:2084)
>     at 
> org.openide.explorer.view.SheetCell.getTableCellRendererComponent(SheetCell.java:276)
>     at 
> org.openide.explorer.view.SheetCell$OutlineSheetCell.getTableCellRendererComponent(SheetCell.java:737)
>     at 
> org.netbeans.modules.viewmodel.DelegatingCellRenderer.getTableCellRendererComponent(DelegatingCellRenderer.java:66)
>     at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5758)
>     at org.netbeans.swing.outline.Outline.getToolTipText(Outline.java:393)
>     at 
> java.desktop/javax.swing.ToolTipManager$insideTimerAction.actionPerformed(ToolTipManager.java:675)
>     at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:317)
>     at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:249)
>     at 
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
>     at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
>     at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97)
>     at java.desktop/java.awt.EventQueue$3.r

[jira] [Updated] (NETBEANS-963) java.lang.AssertionError: Debugger lock taken in AWT Event Queue!

2018-06-19 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-963:
-
Priority: Critical  (was: Blocker)

> java.lang.AssertionError: Debugger lock taken in AWT Event Queue!
> -
>
> Key: NETBEANS-963
> URL: https://issues.apache.org/jira/browse/NETBEANS-963
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Affects Versions: 9.0
> Environment: Linux; Release Build 316
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> When I've selected the "String Value" column in Variables view of the Java 
> debugger, the following exception is thrown even if I just move the cursor 
> over the string value.
> This does only happen for object values; primitive values do not seem to be 
> affected.
> Probably it's related to tooltips, as those are shown for primitive values, 
> while object values throw an exception.
> As this makes it impossible to show and review large strings and thus makes 
> debugging harder, I've set the status to "Blocker".
>  
> java.lang.AssertionError: Debugger lock taken in AWT Event Queue!
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl$DebuggerReentrantReadWriteLock$DebuggerReadLock.lock(JPDADebuggerImpl.java:2675)
>     at 
> org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl$ThreadReentrantReadWriteLock$ThreadWriteLock.lock(JPDAThreadImpl.java:2555)
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1066)
>     at 
> org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1008)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:496)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:460)
>     at 
> org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:424)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.VariablesTableModel.getValueAt(VariablesTableModel.java:108)
>     at 
> org.netbeans.spi.viewmodel.Models$DelegatingTableModel.getValueAt(Models.java:2249)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.NumericDisplayFilter.getValueAt(NumericDisplayFilter.java:112)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.VariablesTreeModelFilter.getValueAt(VariablesTreeModelFilter.java:530)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.modules.debugger.jpda.ui.models.PendingActionsFilter.getValueAt(PendingActionsFilter.java:108)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
>     at 
> org.netbeans.spi.viewmodel.Models$CompoundModel.getValueAt(Models.java:4566)
>     at 
> org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.updateShortDescription(TreeModelNode.java:2102)
>     at 
> org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.getShortDescription(TreeModelNode.java:2084)
>     at 
> org.openide.explorer.view.SheetCell.getTableCellRendererComponent(SheetCell.java:276)
>     at 
> org.openide.explorer.view.SheetCell$OutlineSheetCell.getTableCellRendererComponent(SheetCell.java:737)
>     at 
> org.netbeans.modules.viewmodel.DelegatingCellRenderer.getTableCellRendererComponent(DelegatingCellRenderer.java:66)
>     at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5758)
>     at org.netbeans.swing.outline.Outline.getToolTipText(Outline.java:393)
>     at 
> java.desktop/javax.swing.ToolTipManager$insideTimerAction.actionPerformed(ToolTipManager.java:675)
>     at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:317)
>     at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:249)
>     at 
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
>     at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
>     at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97)
>     at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:717)
>     at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:711)
>     at java.base/java.security.AccessController.doPrivileged(Native Method)
>     at 
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
>     at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.jav

[jira] [Created] (NETBEANS-964) Incorrect formatting for constructor calls in array definition

2018-06-16 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-964:


 Summary: Incorrect formatting for constructor calls in array 
definition
 Key: NETBEANS-964
 URL: https://issues.apache.org/jira/browse/NETBEANS-964
 Project: NetBeans
  Issue Type: Bug
  Components: java - Editor
Affects Versions: 9.0
 Environment: Linux; Release build 316
Reporter: Peter Nabbefeld


When creating an array of objects constructed in place, the constructor 
parameters are not indented:


    private static final TestData[] TEST_DATA = new TestData[]{
    new TestData(
    "",
    "1111",
    false, false, 16L, 50L, 16L, 8L
    ),



--
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-963) java.lang.AssertionError: Debugger lock taken in AWT Event Queue!

2018-06-16 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-963:


 Summary: java.lang.AssertionError: Debugger lock taken in AWT 
Event Queue!
 Key: NETBEANS-963
 URL: https://issues.apache.org/jira/browse/NETBEANS-963
 Project: NetBeans
  Issue Type: Bug
  Components: debugger - Java
Affects Versions: 9.0
 Environment: Linux; Release Build 316
Reporter: Peter Nabbefeld


When I've selected the "String Value" column in Variables view of the Java 
debugger, the following exception is thrown even if I just move the cursor over 
the string value.

This does only happen for object values; primitive values do not seem to be 
affected.

Probably it's related to tooltips, as those are shown for primitive values, 
while object values throw an exception.

As this makes it impossible to show and review large strings and thus makes 
debugging harder, I've set the status to "Blocker".

 

java.lang.AssertionError: Debugger lock taken in AWT Event Queue!
    at 
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl$DebuggerReentrantReadWriteLock$DebuggerReadLock.lock(JPDADebuggerImpl.java:2675)
    at 
org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl$ThreadReentrantReadWriteLock$ThreadWriteLock.lock(JPDAThreadImpl.java:2555)
    at 
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1066)
    at 
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1008)
    at 
org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:496)
    at 
org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:460)
    at 
org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.getToStringValue(AbstractObjectVariable.java:424)
    at 
org.netbeans.modules.debugger.jpda.ui.models.VariablesTableModel.getValueAt(VariablesTableModel.java:108)
    at 
org.netbeans.spi.viewmodel.Models$DelegatingTableModel.getValueAt(Models.java:2249)
    at 
org.netbeans.modules.debugger.jpda.ui.models.NumericDisplayFilter.getValueAt(NumericDisplayFilter.java:112)
    at 
org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
    at 
org.netbeans.modules.debugger.jpda.ui.models.VariablesTreeModelFilter.getValueAt(VariablesTreeModelFilter.java:530)
    at 
org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
    at 
org.netbeans.modules.debugger.jpda.ui.models.PendingActionsFilter.getValueAt(PendingActionsFilter.java:108)
    at 
org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1439)
    at 
org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
    at 
org.netbeans.spi.viewmodel.Models$CompoundTableModel.getValueAt(Models.java:1441)
    at 
org.netbeans.spi.viewmodel.Models$CompoundModel.getValueAt(Models.java:4566)
    at 
org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.updateShortDescription(TreeModelNode.java:2102)
    at 
org.netbeans.modules.viewmodel.TreeModelNode$MyProperty.getShortDescription(TreeModelNode.java:2084)
    at 
org.openide.explorer.view.SheetCell.getTableCellRendererComponent(SheetCell.java:276)
    at 
org.openide.explorer.view.SheetCell$OutlineSheetCell.getTableCellRendererComponent(SheetCell.java:737)
    at 
org.netbeans.modules.viewmodel.DelegatingCellRenderer.getTableCellRendererComponent(DelegatingCellRenderer.java:66)
    at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5758)
    at org.netbeans.swing.outline.Outline.getToolTipText(Outline.java:393)
    at 
java.desktop/javax.swing.ToolTipManager$insideTimerAction.actionPerformed(ToolTipManager.java:675)
    at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:317)
    at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:249)
    at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
    at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
    at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97)
    at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:717)
    at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:711)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
    at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:734)
    at 
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
[catch] at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
    at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java

[jira] [Updated] (NETBEANS-910) Editing annotation parameters results in Exceptions thrown

2018-06-14 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-910:
-
Component/s: apisupport - Maven

> Editing annotation parameters results in Exceptions thrown
> --
>
> Key: NETBEANS-910
> URL: https://issues.apache.org/jira/browse/NETBEANS-910
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 9.0
> Environment: Linux
>Reporter: Peter Nabbefeld
>Priority: Major
>
> I got these exceptions when editing a @TemplateRegistration in a 
> package-info.java file:
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data 
> found for annotation element public abstract java.lang.String 
> org.netbeans.api.templates.TemplateRegistration.description() (Found data of 
> type )
>     at 
> com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:275)
>     at 
> sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84)
>     at com.sun.proxy.$Proxy60.description(Unknown Source)
>     at 
> org.netbeans.modules.templates.TemplateProcessor.process(TemplateProcessor.java:128)
>     at 
> org.netbeans.modules.templates.TemplateProcessor.handleProcess(TemplateProcessor.java:82)
>     at 
> org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
> [catch] at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:856)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:752)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:99)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1081)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1157)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1210)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1099)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:374)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:311)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:630)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:496)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:163)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:631)
>     at 
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:262)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:798)
>     at org.openide.util.lookup.Lookups.executeWith(Lookups.java:304)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:725)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:686)
>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>     at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
>     at 
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
>     at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
>     at 
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data 
> found for annotation element public abstract java.lang.String 
> org.netbeans.api.templates.TemplateRegistration.scriptEngine() (Found data of 
> type )
>     at 
> com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:275)
>     at 
> sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84)
>     at com.sun.proxy.$Proxy60.scriptEngine(Unknown Source)
>     at 
> org.netbeans.modules.templates.TemplateProcessor.process(TemplateProcessor.java:153)
>     at 
> org.netbeans.modules.templates.TemplateProcessor.handleProcess(TemplateProcessor.java:82)
>     at 
> org.openide.filesystems.annotations.LayerGeneratingProcesso

[jira] [Updated] (NETBEANS-914) Generated WizardDescriptor.InstantiatingIterator contains suspicious code

2018-06-14 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-914:
-
Component/s: apisupport - Project

> Generated WizardDescriptor.InstantiatingIterator contains suspicious code
> -
>
> Key: NETBEANS-914
> URL: https://issues.apache.org/jira/browse/NETBEANS-914
> Project: NetBeans
>  Issue Type: Improvement
>  Components: apisupport - Project
>Affects Versions: 9.0
> Environment: Linux
>Reporter: Peter Nabbefeld
>Priority: Minor
>
> The InstantiatingIterator contains following code:
>     String[] steps = createSteps();
>     for (int i = 0; i < panels.size(); i++) {
>     Component c = panels.get(i).getComponent();
>     if (steps[i] == null) {
>     // Default step name to component name of panel. Mainly
>     // useful for getting the name of the target chooser to
>     // appear in the list of steps.
>     steps[i] = c.getName();
>     }
> Here, "steps" is used as a zero-based array.
> It uses following method:
> private String[] createSteps() {
>     String[] beforeSteps = 
> (String[])wizard.getProperty("WizardPanel_contentData");
>     assert beforeSteps != null : "This wizard may only be used embedded in 
> the template wizard";
>     String[] res = new String[(beforeSteps.length - 1) + panels.size()];
>     for (int i = 0; i < res.length; i++) {
>     if (i < (beforeSteps.length - 1)) {
>     res[i] = beforeSteps[i];
>     } else {
>     res[i] = panels.get(i - beforeSteps.length + 
> 1).getComponent().getName();
>     }
>     }
>     return res;
> }
> Here, "steps" has a bias-value (the size of beforeSteps - 1), which seems to 
> be zero in most cases, but the different usage may cause errors if bias > 0.
> Probably it should be made clear, what this bias value exactly is, and then 
> it should also be used in the code above, if needed.



--
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-911) generated-layer.xml not rebuilt after annotation changes

2018-06-14 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-911:
-
Component/s: apisupport - Maven

> generated-layer.xml not rebuilt after annotation changes
> 
>
> Key: NETBEANS-911
> URL: https://issues.apache.org/jira/browse/NETBEANS-911
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 9.0
>Reporter: Peter Nabbefeld
>Priority: Major
>
> I've created a module for a new file type, containing a package-info.java 
> file with a @TemplateRegistration annotation.
> When I change the parameters of this annotation, the generated-layer.xml 
> isn't rebuilt, thus changes are ignored.
> When I change some target directories (I don't want to do a clean build 
> because I don't want to remove userdir), I sometimes get Exceptions when I 
> try running after rebuilding, so removing is not really a good workaround. As 
> it doesn't happen always, I had to investigate, when this happens, but it's 
> also useless, if this bug gets fixed.



--
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-885) NPE on invalid Java source code

2018-06-08 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-885:
-
Component/s: java - Editor

> NPE on invalid Java source code
> ---
>
> Key: NETBEANS-885
> URL: https://issues.apache.org/jira/browse/NETBEANS-885
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: Linux, NetBeans 9.0 RC1 (and predecessors).
>Reporter: Peter Nabbefeld
>Priority: Major
>
> I sometimes like to write some code using hints for completion like this:
> package test;
> import java.io.File;
> public class Test {
>     public void test() {
>     File[] files = new File[0];
>     for (file : files)
>     }
> }
> This results in NullPointerExceptions on editing, formatting, or even just 
> re-opening the file.
> Additionally to bug resolution I'd like to know how to write tests for such 
> situations, so I'd be glad if You could append a diff for the changes.
> Relevant part of stacktrace:
> java.lang.NullPointerException
> SEVERE [org.openide.util.Exceptions]
> java.lang.NullPointerException
>     at 
> jdk.compiler/com.sun.tools.javac.tree.Pretty.visitVarDef(Pretty.java:636)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:950)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:194)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:209)
>     at jdk.compiler/com.sun.tools.javac.tree.JCTree.toString(JCTree.java:429)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.createBreadcrumbs(BreadCrumbsNodeImpl.java:260)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:535)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:90)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitBlock(TreeScanner.java:248)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:86)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:539)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:544)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:514)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
>     at 
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
>     at 
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
>     at 
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.getChildren(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.rootAndSelection(BreadCrumbsScanningTask.java:114)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.run(BreadCrumbsScanningTask.java:82)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
> [catch] at 
> org.netbeans.modules.

[jira] [Updated] (NETBEANS-885) NPE on invalid Java source code

2018-06-08 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-885:
-
Priority: Critical  (was: Major)

> NPE on invalid Java source code
> ---
>
> Key: NETBEANS-885
> URL: https://issues.apache.org/jira/browse/NETBEANS-885
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: Linux, NetBeans 9.0 RC1 (and predecessors).
>Reporter: Peter Nabbefeld
>Priority: Critical
>
> I sometimes like to write some code using hints for completion like this:
> package test;
> import java.io.File;
> public class Test {
>     public void test() {
>     File[] files = new File[0];
>     for (file : files)
>     }
> }
> This results in NullPointerExceptions on editing, formatting, or even just 
> re-opening the file.
> Additionally to bug resolution I'd like to know how to write tests for such 
> situations, so I'd be glad if You could append a diff for the changes.
> Relevant part of stacktrace:
> java.lang.NullPointerException
> SEVERE [org.openide.util.Exceptions]
> java.lang.NullPointerException
>     at 
> jdk.compiler/com.sun.tools.javac.tree.Pretty.visitVarDef(Pretty.java:636)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:950)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:194)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:209)
>     at jdk.compiler/com.sun.tools.javac.tree.JCTree.toString(JCTree.java:429)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.createBreadcrumbs(BreadCrumbsNodeImpl.java:260)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:535)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:90)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitBlock(TreeScanner.java:248)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:86)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:539)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:544)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:514)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
>     at 
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
>     at 
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
>     at 
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.getChildren(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.rootAndSelection(BreadCrumbsScanningTask.java:114)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.run(BreadCrumbsScanningTask.java:82)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
> [catch] at 
> org.netbeans

[jira] [Updated] (NETBEANS-886) Code completion does not work in "if" statement

2018-06-08 Thread Peter Nabbefeld (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Nabbefeld updated NETBEANS-886:
-
Component/s: java - Editor

> Code completion does not work in "if" statement
> ---
>
> Key: NETBEANS-886
> URL: https://issues.apache.org/jira/browse/NETBEANS-886
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: Linux, NB 9.0 RC1 (and predecessors)
>Reporter: Peter Nabbefeld
>Priority: Major
>
> package org.example.ds;
> public class Test {
>     public void test() {
>     String test = "abcd";
>     // [1] test.contains("a");
>     // [2] if (test.contains("a"));
>     }
> }
>  
> When writing Java code, in case [1] code completion works, case [2] not (just 
> typing "test.c" gives me correct correct list of proposals in the first case, 
> but weird ones like "continue" in the second).



--
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-938) Navigating JDK Sources not possible

2018-06-08 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-938:


 Summary: Navigating JDK Sources not possible
 Key: NETBEANS-938
 URL: https://issues.apache.org/jira/browse/NETBEANS-938
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
 Environment: Linux
Reporter: Peter Nabbefeld


When doing Ctrl+MouseClick to go to some imported source, I cannot navigate in 
JDK sources (i.e. java.io.File).

That's rather strange, as I can e.g. navigate in sources of Maven dependencies.

To be exact: I can go to the source of every import (if available, of course). 
But when I click on a method name in the navigator panel, I can only navigate 
to a method in external dependencies, but not inside a JDK source.



--
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-914) Generated WizardDescriptor.InstantiatingIterator contains suspicious code

2018-06-04 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-914:


 Summary: Generated WizardDescriptor.InstantiatingIterator contains 
suspicious code
 Key: NETBEANS-914
 URL: https://issues.apache.org/jira/browse/NETBEANS-914
 Project: NetBeans
  Issue Type: Improvement
Affects Versions: 9.0
 Environment: Linux
Reporter: Peter Nabbefeld


The InstantiatingIterator contains following code:

    String[] steps = createSteps();
    for (int i = 0; i < panels.size(); i++) {
    Component c = panels.get(i).getComponent();
    if (steps[i] == null) {
    // Default step name to component name of panel. Mainly
    // useful for getting the name of the target chooser to
    // appear in the list of steps.
    steps[i] = c.getName();
    }

Here, "steps" is used as a zero-based array.

It uses following method:

private String[] createSteps() {
    String[] beforeSteps = 
(String[])wizard.getProperty("WizardPanel_contentData");
    assert beforeSteps != null : "This wizard may only be used embedded in the 
template wizard";
    String[] res = new String[(beforeSteps.length - 1) + panels.size()];
    for (int i = 0; i < res.length; i++) {
    if (i < (beforeSteps.length - 1)) {
    res[i] = beforeSteps[i];
    } else {
    res[i] = panels.get(i - beforeSteps.length + 
1).getComponent().getName();
    }
    }
    return res;
}

Here, "steps" has a bias-value (the size of beforeSteps - 1), which seems to be 
zero in most cases, but the different usage may cause errors if bias > 0.

Probably it should be made clear, what this bias value exactly is, and then it 
should also be used in the code above, if needed.



--
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-911) generated-layer.xml not rebuilt after annotation changes

2018-06-03 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-911:


 Summary: generated-layer.xml not rebuilt after annotation changes
 Key: NETBEANS-911
 URL: https://issues.apache.org/jira/browse/NETBEANS-911
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
Reporter: Peter Nabbefeld


I've created a module for a new file type, containing a package-info.java file 
with a @TemplateRegistration annotation.

When I change the parameters of this annotation, the generated-layer.xml isn't 
rebuilt, thus changes are ignored.

When I change some target directories (I don't want to do a clean build because 
I don't want to remove userdir), I sometimes get Exceptions when I try running 
after rebuilding, so removing is not really a good workaround. As it doesn't 
happen always, I had to investigate, when this happens, but it's also useless, 
if this bug gets fixed.



--
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-910) Editing annotation parameters results in Exceptions thrown

2018-06-03 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-910:


 Summary: Editing annotation parameters results in Exceptions thrown
 Key: NETBEANS-910
 URL: https://issues.apache.org/jira/browse/NETBEANS-910
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
 Environment: Linux
Reporter: Peter Nabbefeld


I got these exceptions when editing a @TemplateRegistration in a 
package-info.java file:

INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
processing error:
java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data 
found for annotation element public abstract java.lang.String 
org.netbeans.api.templates.TemplateRegistration.description() (Found data of 
type )
    at 
com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:275)
    at 
sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84)
    at com.sun.proxy.$Proxy60.description(Unknown Source)
    at 
org.netbeans.modules.templates.TemplateProcessor.process(TemplateProcessor.java:128)
    at 
org.netbeans.modules.templates.TemplateProcessor.handleProcess(TemplateProcessor.java:82)
    at 
org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
[catch] at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:856)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:752)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:99)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1081)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1157)
    at 
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1210)
    at 
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1099)
    at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:374)
    at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:311)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:630)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:496)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:163)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:631)
    at 
org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:262)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:798)
    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:304)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:725)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:686)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
    at 
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
    at 
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
processing error:
java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data 
found for annotation element public abstract java.lang.String 
org.netbeans.api.templates.TemplateRegistration.scriptEngine() (Found data of 
type )
    at 
com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor$1AnnotationTypeMismatchExceptionProxy.generateException(AnnotationProxyMaker.java:275)
    at 
sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84)
    at com.sun.proxy.$Proxy60.scriptEngine(Unknown Source)
    at 
org.netbeans.modules.templates.TemplateProcessor.process(TemplateProcessor.java:153)
    at 
org.netbeans.modules.templates.TemplateProcessor.handleProcess(TemplateProcessor.java:82)
    at 
org.openide.filesystems.annotations.LayerGeneratingProcessor.process(LayerGeneratingProcessor.java:122)
[catch] at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:856)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:752)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2200(JavacProcessingEnvironment.java:99)
    at 
com.sun.tools.javac.process

[jira] [Commented] (NETBEANS-885) NPE on invalid Java source code

2018-06-03 Thread Peter Nabbefeld (JIRA)


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

Peter Nabbefeld commented on NETBEANS-885:
--

I've installed JDK 1.8 and 1.7, too, so I guess, nbjavac is installed.

 

> NPE on invalid Java source code
> ---
>
> Key: NETBEANS-885
> URL: https://issues.apache.org/jira/browse/NETBEANS-885
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 9.0
> Environment: Linux, NetBeans 9.0 RC1 (and predecessors).
>Reporter: Peter Nabbefeld
>Priority: Major
>
> I sometimes like to write some code using hints for completion like this:
> package test;
> import java.io.File;
> public class Test {
>     public void test() {
>     File[] files = new File[0];
>     for (file : files)
>     }
> }
> This results in NullPointerExceptions on editing, formatting, or even just 
> re-opening the file.
> Additionally to bug resolution I'd like to know how to write tests for such 
> situations, so I'd be glad if You could append a diff for the changes.
> Relevant part of stacktrace:
> java.lang.NullPointerException
> SEVERE [org.openide.util.Exceptions]
> java.lang.NullPointerException
>     at 
> jdk.compiler/com.sun.tools.javac.tree.Pretty.visitVarDef(Pretty.java:636)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:950)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:194)
>     at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:209)
>     at jdk.compiler/com.sun.tools.javac.tree.JCTree.toString(JCTree.java:429)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.createBreadcrumbs(BreadCrumbsNodeImpl.java:260)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:535)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:90)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>     at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitBlock(TreeScanner.java:248)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:86)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:539)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:544)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:514)
>     at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:514)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
>     at 
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
>     at 
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
>     at 
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
>     at 
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
>     at 
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
>     at 
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.getChildren(BreadCrumbsNodeImpl.java:503)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.rootAndSelection(BreadCrumbsScanningTask.java:114)
>     at 
> org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.run(BreadCrumbsScanningTask.java:82)
>     at 
> org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTa

[jira] [Created] (NETBEANS-886) Code completion does not work in "if" statement

2018-05-29 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-886:


 Summary: Code completion does not work in "if" statement
 Key: NETBEANS-886
 URL: https://issues.apache.org/jira/browse/NETBEANS-886
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
 Environment: Linux, NB 9.0 RC1 (and predecessors)
Reporter: Peter Nabbefeld


package org.example.ds;

public class Test {

    public void test() {
    String test = "abcd";
    // [1] test.contains("a");
    // [2] if (test.contains("a"));
    }
}

 

When writing Java code, in case [1] code completion works, case [2] not (just 
typing "test.c" gives me correct correct list of proposals in the first case, 
but weird ones like "continue" in the second).



--
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-885) NPE on invalid Java source code

2018-05-29 Thread Peter Nabbefeld (JIRA)
Peter Nabbefeld created NETBEANS-885:


 Summary: NPE on invalid Java source code
 Key: NETBEANS-885
 URL: https://issues.apache.org/jira/browse/NETBEANS-885
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
 Environment: Linux, NetBeans 9.0 RC1 (and predecessors).
Reporter: Peter Nabbefeld


I sometimes like to write some code using hints for completion like this:

package test;
import java.io.File;

public class Test {

    public void test() {
    File[] files = new File[0];
    for (file : files)
    }
}

This results in NullPointerExceptions on editing, formatting, or even just 
re-opening the file.

Additionally to bug resolution I'd like to know how to write tests for such 
situations, so I'd be glad if You could append a diff for the changes.

Relevant part of stacktrace:

java.lang.NullPointerException
SEVERE [org.openide.util.Exceptions]
java.lang.NullPointerException
    at jdk.compiler/com.sun.tools.javac.tree.Pretty.visitVarDef(Pretty.java:636)
    at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:950)
    at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:194)
    at jdk.compiler/com.sun.tools.javac.tree.Pretty.printExpr(Pretty.java:209)
    at jdk.compiler/com.sun.tools.javac.tree.JCTree.toString(JCTree.java:429)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.createBreadcrumbs(BreadCrumbsNodeImpl.java:260)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:535)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:514)
    at 
jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:90)
    at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
    at 
jdk.compiler/com.sun.source.util.TreeScanner.visitBlock(TreeScanner.java:248)
    at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
    at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:86)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:539)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:544)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.visitMethod(BreadCrumbsNodeImpl.java:514)
    at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:514)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3.run(BreadCrumbsNodeImpl.java:503)
    at 
org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
    at 
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
    at 
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
    at 
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
    at 
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
    at 
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.getChildren(BreadCrumbsNodeImpl.java:503)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.rootAndSelection(BreadCrumbsScanningTask.java:114)
    at 
org.netbeans.modules.java.navigation.BreadCrumbsScanningTask.run(BreadCrumbsScanningTask.java:82)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
[catch] at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:786)
    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:702)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:663)
    at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Exe

[jira] [Commented] (NETBEANS-595) OSGI Project unable to compile

2018-05-25 Thread Peter Nabbefeld (JIRA)

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

Peter Nabbefeld commented on NETBEANS-595:
--

Hm, when there's only one comment added, the problem must be caused by sth. 
else but the plugin. Probably testing has changed some internal state, which 
caused the properties to be added. I must admit, I couldn't find any template 
for the addition of source/target properties. However, this makes fixing more 
complex, of course.

> OSGI Project unable to compile
> --
>
> Key: NETBEANS-595
> URL: https://issues.apache.org/jira/browse/NETBEANS-595
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: upstream-issue
>
> Unable to compile Wizard created project.
> {noformat}
> COMPILATION ERROR : 
> -
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> 2 errors 
> -
> 
> BUILD FAILURE
> 
> Total time: 2.703 s
> Finished at: 2018-04-04T12:47:54-05:00
> Final Memory: 14M/60M
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project TestPlatformOSGIBundle: Compilation failure: 
> Compilation failure: 
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> -> [Help 1]{noformat}



--
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-595) OSGI Project unable to compile

2018-05-25 Thread Peter Nabbefeld (JIRA)

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

Peter Nabbefeld commented on NETBEANS-595:
--

The problem starts with Java 9 - as the source and target properties aren't set 
when the OSGi bundle is created, the build process assumes 1.5 - starting with 
Java 9, this isn't supported anymore.

> OSGI Project unable to compile
> --
>
> Key: NETBEANS-595
> URL: https://issues.apache.org/jira/browse/NETBEANS-595
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: upstream-issue
>
> Unable to compile Wizard created project.
> {noformat}
> COMPILATION ERROR : 
> -
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> 2 errors 
> -
> 
> BUILD FAILURE
> 
> Total time: 2.703 s
> Finished at: 2018-04-04T12:47:54-05:00
> Final Memory: 14M/60M
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project TestPlatformOSGIBundle: Compilation failure: 
> Compilation failure: 
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> -> [Help 1]{noformat}



--
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-595) OSGI Project unable to compile

2018-05-25 Thread Peter Nabbefeld (JIRA)

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

Peter Nabbefeld commented on NETBEANS-595:
--

Seems version 1.5 has not been finished and probably never will be, as latest 
activity was in 2013. So, either the SNAPSHOT version has to be used, or 
somebody needs to fork it, if legally possible (didn't find a license). Another 
option might be to use templates for POM creation.

> OSGI Project unable to compile
> --
>
> Key: NETBEANS-595
> URL: https://issues.apache.org/jira/browse/NETBEANS-595
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: upstream-issue
>
> Unable to compile Wizard created project.
> {noformat}
> COMPILATION ERROR : 
> -
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> 2 errors 
> -
> 
> BUILD FAILURE
> 
> Total time: 2.703 s
> Finished at: 2018-04-04T12:47:54-05:00
> Final Memory: 14M/60M
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project TestPlatformOSGIBundle: Compilation failure: 
> Compilation failure: 
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> -> [Help 1]{noformat}



--
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-595) OSGI Project unable to compile

2018-05-25 Thread Peter Nabbefeld (JIRA)

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

Peter Nabbefeld commented on NETBEANS-595:
--

Hi, I got the same problem. IMHO, this is primarily a Maven problem (as the 
generated POM is not setting the appropriate properties). The archetype seems 
to be outdated, probably an archetype directory should be supported:

"Archetype repository not defined. Using the one from 
[org.codehaus.mojo.archetypes:osgi-archetype:1.4] found in catalog remote".

I then downloaded the sources from Github 
([https://github.com/mojohaus/osgi-archetype)] and built the project, so the 
archetype has been deployed locally; this solved the problem for me.

However, I don't know, which of the changes caused the appropriate properties 
to be set now.

 

> OSGI Project unable to compile
> --
>
> Key: NETBEANS-595
> URL: https://issues.apache.org/jira/browse/NETBEANS-595
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>
> Unable to compile Wizard created project.
> {noformat}
> COMPILATION ERROR : 
> -
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> 2 errors 
> -
> 
> BUILD FAILURE
> 
> Total time: 2.703 s
> Finished at: 2018-04-04T12:47:54-05:00
> Final Memory: 14M/60M
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project TestPlatformOSGIBundle: Compilation failure: 
> Compilation failure: 
> Source option 5 is no longer supported. Use 6 or later.
> Target option 1.5 is no longer supported. Use 1.6 or later.
> -> [Help 1]{noformat}



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