[jira] [Commented] (NETBEANS-5585) Cannot create Maven web project with EE 5
[
https://issues.apache.org/jira/browse/NETBEANS-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1743#comment-1743
]
Nicola Isotta commented on NETBEANS-5585:
-
Moved to GitHub: https://github.com/apache/netbeans/issues/3681
> Cannot create Maven web project with EE 5
> -
>
> Key: NETBEANS-5585
> URL: https://issues.apache.org/jira/browse/NETBEANS-5585
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.3
>Reporter: Nicola Isotta
>Priority: Major
>
> Steps to reproduce:
> New Project > [Java with Maven] > [Web Application] > Next
> Choose a name then > Next
> Select [Java EE 5] then > Finish
> An exception is thrown and the project is not created.
> Stack trace:
> {{java.lang.IllegalStateException: No archetype defined for profile 1.5 in
> class
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
> check whether all possible pairs have been
> addedjava.lang.IllegalStateException: No archetype defined for profile 1.5 in
> class
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
> check whether all possible pairs have been added at
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.BaseJ2eeArchetypeProvider.getArchetypeFor(BaseJ2eeArchetypeProvider.java:128)
> at
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory.findArchetypeFor(J2eeArchetypeFactory.java:79)
> at
> org.netbeans.modules.maven.j2ee.ui.wizard.EEWizardIterator.instantiate(EEWizardIterator.java:102)
> at
> org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1050)
> at
> org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:602)
> at
> org.netbeans.modules.project.ui.NewProjectWizard.handleInstantiate(NewProjectWizard.java:51)
> at
> org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:436)
> at
> org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizardIterImpl.java:223)
> at
> org.openide.loaders.TemplateWizardIteratorWrapper.instantiate(TemplateWizardIteratorWrapper.java:135)
> at
> org.openide.WizardDescriptor.callInstantiateOpen(WizardDescriptor.java:1605)
> at org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:1546)
> at org.openide.WizardDescriptor.access$2300(WizardDescriptor.java:67)[catch]
> at org.openide.WizardDescriptor$Listener$2$1.run(WizardDescriptor.java:2233)
> 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) at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5585) Cannot create Maven web project with EE 5
[
https://issues.apache.org/jira/browse/NETBEANS-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-5585:
External issue URL: https://github.com/apache/netbeans/issues/3681
> Cannot create Maven web project with EE 5
> -
>
> Key: NETBEANS-5585
> URL: https://issues.apache.org/jira/browse/NETBEANS-5585
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.3
>Reporter: Nicola Isotta
>Priority: Major
>
> Steps to reproduce:
> New Project > [Java with Maven] > [Web Application] > Next
> Choose a name then > Next
> Select [Java EE 5] then > Finish
> An exception is thrown and the project is not created.
> Stack trace:
> {{java.lang.IllegalStateException: No archetype defined for profile 1.5 in
> class
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
> check whether all possible pairs have been
> addedjava.lang.IllegalStateException: No archetype defined for profile 1.5 in
> class
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
> check whether all possible pairs have been added at
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.BaseJ2eeArchetypeProvider.getArchetypeFor(BaseJ2eeArchetypeProvider.java:128)
> at
> org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory.findArchetypeFor(J2eeArchetypeFactory.java:79)
> at
> org.netbeans.modules.maven.j2ee.ui.wizard.EEWizardIterator.instantiate(EEWizardIterator.java:102)
> at
> org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1050)
> at
> org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:602)
> at
> org.netbeans.modules.project.ui.NewProjectWizard.handleInstantiate(NewProjectWizard.java:51)
> at
> org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:436)
> at
> org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizardIterImpl.java:223)
> at
> org.openide.loaders.TemplateWizardIteratorWrapper.instantiate(TemplateWizardIteratorWrapper.java:135)
> at
> org.openide.WizardDescriptor.callInstantiateOpen(WizardDescriptor.java:1605)
> at org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:1546)
> at org.openide.WizardDescriptor.access$2300(WizardDescriptor.java:67)[catch]
> at org.openide.WizardDescriptor$Listener$2$1.run(WizardDescriptor.java:2233)
> 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) at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-3611) No library found for namespace http://omnifaces.org/ui
[
https://issues.apache.org/jira/browse/NETBEANS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441799#comment-17441799
]
Nicola Isotta edited comment on NETBEANS-3611 at 2/17/22, 2:22 PM:
---
As of NetBeans 12.5 the problem persists.
I had to downgrade to OminFaces 2.* to get rid of those annoying red badges.
was (Author: nicolaisotta):
As of NetBeans 12.5 the problem persists.
I had to downgrade to OminFaces 2.* to get rid of those annoying red badged.
> No library found for namespace http://omnifaces.org/ui
> --
>
> Key: NETBEANS-3611
> URL: https://issues.apache.org/jira/browse/NETBEANS-3611
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - JSF
>Affects Versions: 11.1, 11.2
>Reporter: Ömer Faruk Kurt
>Priority: Major
> Attachments: 47298773-eab3a100-d618-11e8-849e-627e6507ee97.png
>
>
> With OmniFace 3.2 you get an error message in a facelet
> {{No library found for namespace http://omnifaces.org/ui}}
> With NetBeans 8.2 en 9.0 you can only have the 8.2 JEE plugins.
> You can actually make JSF2.3 work but adding OmniFaces to a facelet then
> renders the error.
> I managed to get rid of the error by unpacking the omnifaces-3.2.jar to a
> directory and add that directory to the libraries of the project and remove
> the omnifaces-3.2.jar from the libraries.
> After that I changed the XML tag facelet-taglib to a signature as used in
> mojarra_ext.taglib.xml of javax.faces-2.3.7.jar the error is going away from
> the facelet.
> I saw a closed issue about a namespace not found in NetBeans 8.2 and I have
> the same problem.
> [https://github.com/omnifaces/omnifaces/issues/442|https://github.com/omnifaces/omnifaces/issues/url]
> I think the NetBeans webproject is not able to see the new signature of the
> omnifaces-ui.taglib.xml version 2.3.
> The NetBeans IDE is making a transition to Apache and until Feb. 2019 there
> will not any renewal on the Jakarta EE plugins for NetBeans supporting JSF 2.3
> [https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Roadmap|https://github.com/omnifaces/omnifaces/issues/url]
> So what I did was to uncheck the package checkbox of the changed directory in
> the library settings and in the web build/packaging to add the
> omnifaces-3.2.jar.
> Actually I think it is a NetBeans problem but until feb. 2019 no updates on
> Jakarta EE to expect from there.
> A picture of 2 projects, 1 with problem and the second with solved problem of
> the index.xhtml
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3611) No library found for namespace http://omnifaces.org/ui
[
https://issues.apache.org/jira/browse/NETBEANS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441799#comment-17441799
]
Nicola Isotta commented on NETBEANS-3611:
-
As of NetBeans 12.5 the problem persists.
I had to downgrade to OminFaces 2.* to get rid of those annoying red badged.
> No library found for namespace http://omnifaces.org/ui
> --
>
> Key: NETBEANS-3611
> URL: https://issues.apache.org/jira/browse/NETBEANS-3611
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - JSF
>Affects Versions: 11.1, 11.2
>Reporter: Ömer Faruk Kurt
>Priority: Major
> Attachments: 47298773-eab3a100-d618-11e8-849e-627e6507ee97.png
>
>
> With OmniFace 3.2 you get an error message in a facelet
> {{No library found for namespace http://omnifaces.org/ui}}
> With NetBeans 8.2 en 9.0 you can only have the 8.2 JEE plugins.
> You can actually make JSF2.3 work but adding OmniFaces to a facelet then
> renders the error.
> I managed to get rid of the error by unpacking the omnifaces-3.2.jar to a
> directory and add that directory to the libraries of the project and remove
> the omnifaces-3.2.jar from the libraries.
> After that I changed the XML tag facelet-taglib to a signature as used in
> mojarra_ext.taglib.xml of javax.faces-2.3.7.jar the error is going away from
> the facelet.
> I saw a closed issue about a namespace not found in NetBeans 8.2 and I have
> the same problem.
> [https://github.com/omnifaces/omnifaces/issues/442|https://github.com/omnifaces/omnifaces/issues/url]
> I think the NetBeans webproject is not able to see the new signature of the
> omnifaces-ui.taglib.xml version 2.3.
> The NetBeans IDE is making a transition to Apache and until Feb. 2019 there
> will not any renewal on the Jakarta EE plugins for NetBeans supporting JSF 2.3
> [https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Roadmap|https://github.com/omnifaces/omnifaces/issues/url]
> So what I did was to uncheck the package checkbox of the changed directory in
> the library settings and in the web build/packaging to add the
> omnifaces-3.2.jar.
> Actually I think it is a NetBeans problem but until feb. 2019 no updates on
> Jakarta EE to expect from there.
> A picture of 2 projects, 1 with problem and the second with solved problem of
> the index.xhtml
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5585) Cannot create Maven web project with EE 5
[
https://issues.apache.org/jira/browse/NETBEANS-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-5585:
Description:
Steps to reproduce:
New Project > [Java with Maven] > [Web Application] > Next
Choose a name then > Next
Select [Java EE 5] then > Finish
An exception is thrown and the project is not created.
Stack trace:
{{java.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been
addedjava.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been added at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.BaseJ2eeArchetypeProvider.getArchetypeFor(BaseJ2eeArchetypeProvider.java:128)
at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory.findArchetypeFor(J2eeArchetypeFactory.java:79)
at
org.netbeans.modules.maven.j2ee.ui.wizard.EEWizardIterator.instantiate(EEWizardIterator.java:102)
at
org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1050)
at
org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:602)
at
org.netbeans.modules.project.ui.NewProjectWizard.handleInstantiate(NewProjectWizard.java:51)
at
org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:436)
at
org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizardIterImpl.java:223)
at
org.openide.loaders.TemplateWizardIteratorWrapper.instantiate(TemplateWizardIteratorWrapper.java:135)
at
org.openide.WizardDescriptor.callInstantiateOpen(WizardDescriptor.java:1605) at
org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:1546) at
org.openide.WizardDescriptor.access$2300(WizardDescriptor.java:67)[catch] at
org.openide.WizardDescriptor$Listener$2$1.run(WizardDescriptor.java:2233) 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) at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)}}
was:
Steps to reproduce:
New Project -> [Java with Maven] -> [Web Application] -> Next
Choose a name then -> Next
Select [Java EE 5] then -> Finish
Then an exception is thrown and the project is not created.
Stack trace:
{{java.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been
addedjava.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been added at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.BaseJ2eeArchetypeProvider.getArchetypeFor(BaseJ2eeArchetypeProvider.java:128)
at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory.findArchetypeFor(J2eeArchetypeFactory.java:79)
at
org.netbeans.modules.maven.j2ee.ui.wizard.EEWizardIterator.instantiate(EEWizardIterator.java:102)
at
org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1050)
at
org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:602)
at
org.netbeans.modules.project.ui.NewProjectWizard.handleInstantiate(NewProjectWizard.java:51)
at
org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:436)
at
org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizardIterImpl.java:223)
at
org.openide.loaders.TemplateWizardIteratorWrapper.instantiate(TemplateWizardIteratorWrapper.java:135)
at
org.openide.WizardDescriptor.callInstantiateOpen(WizardDescriptor.java:1605) at
org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:1546) at
org.openide.WizardDescriptor.access$2300(WizardDescriptor.java:67)[catch] at
org.openide.WizardDescriptor$Listener$2$1.run(WizardDescriptor.java:2233) 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) at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)}}
Summary: Cannot create Maven web project with EE 5 (was: Cannot create)
> Cannot create Maven web project with EE 5
> -
>
> Key: NETBEANS-5585
> URL: https://issues.apache.org/jira/browse/NETBEANS-5585
> Project: NetBeans
> Issue
[jira] [Created] (NETBEANS-5585) Cannot create
Nicola Isotta created NETBEANS-5585:
---
Summary: Cannot create
Key: NETBEANS-5585
URL: https://issues.apache.org/jira/browse/NETBEANS-5585
Project: NetBeans
Issue Type: Bug
Components: projects - Maven
Affects Versions: 12.3
Reporter: Nicola Isotta
Steps to reproduce:
New Project -> [Java with Maven] -> [Web Application] -> Next
Choose a name then -> Next
Select [Java EE 5] then -> Finish
Then an exception is thrown and the project is not created.
Stack trace:
{{java.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been
addedjava.lang.IllegalStateException: No archetype defined for profile 1.5 in
class
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory$WebArchetypes;
check whether all possible pairs have been added at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.BaseJ2eeArchetypeProvider.getArchetypeFor(BaseJ2eeArchetypeProvider.java:128)
at
org.netbeans.modules.maven.j2ee.ui.wizard.archetype.J2eeArchetypeFactory.findArchetypeFor(J2eeArchetypeFactory.java:79)
at
org.netbeans.modules.maven.j2ee.ui.wizard.EEWizardIterator.instantiate(EEWizardIterator.java:102)
at
org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1050)
at
org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:602)
at
org.netbeans.modules.project.ui.NewProjectWizard.handleInstantiate(NewProjectWizard.java:51)
at
org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:436)
at
org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizardIterImpl.java:223)
at
org.openide.loaders.TemplateWizardIteratorWrapper.instantiate(TemplateWizardIteratorWrapper.java:135)
at
org.openide.WizardDescriptor.callInstantiateOpen(WizardDescriptor.java:1605) at
org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:1546) at
org.openide.WizardDescriptor.access$2300(WizardDescriptor.java:67)[catch] at
org.openide.WizardDescriptor$Listener$2$1.run(WizardDescriptor.java:2233) 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) at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143067#comment-17143067 ] Nicola Isotta commented on NETBEANS-4490: - Backtetsted the project, 8.1 is the last working version. From 8.2 on the bug is present, just like NETBEANS-2277 > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 8.2, 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6132 / PWC6169 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Affects Version/s: 8.2 > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 8.2, 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6132 / PWC6169 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142238#comment-17142238 ] Nicola Isotta commented on NETBEANS-4490: - This is really puzzling me. I've copied index.jsp to index.jspx, they have exactly the same content (xml syntax). TLD loading works only for the jspx file, but debugging I found out the classloader jasper receives is exactly the same for the two files! Even funnier, if .jspx file is open first, the error on .jsp file is different ( PWC6032: Unable to load tag handler class "com.sun.faces.taglib.jsf_core.ViewTag" for tag "f:view"). I've tried to create a Maven web project, but the errors are the same. Any hint is appreciated. > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6132 / PWC6169 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142019#comment-17142019 ] Nicola Isotta commented on NETBEANS-4490: - Seems like jasper cannot find the validator class defined in the jsf_core.tld file (com.sun.faces.taglib.jsf_core.CoreValidator) in the classloader received. > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6132 / PWC6169 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Description: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6132 / PWC6169 from jasper compiler. !bug.jpg! Example project attached was: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. !bug.jpg! Example project attached > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6132 / PWC6169 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Attachment: JSF12JSPBug.zip > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6226 from jasper compiler. > !bug.jpg! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Description: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. !bug.jpg! Example project attached was: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. !bug.jpg! > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6226 from jasper compiler. > !bug.jpg! Example project attached -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Attachment: bug.jpg > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6226 from jasper compiler. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
[ https://issues.apache.org/jira/browse/NETBEANS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-4490: Description: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. !bug.jpg! was: When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. > "Could not add one or more tag libraries" when jsp file uses xml syntax > --- > > Key: NETBEANS-4490 > URL: https://issues.apache.org/jira/browse/NETBEANS-4490 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 12.0 >Reporter: Nicola Isotta >Priority: Major > Attachments: bug.jpg > > > When a .jsp uses xml syntax, tld loading breaks. > Root cause seems to be PWC6226 from jasper compiler. > !bug.jpg! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-4490) "Could not add one or more tag libraries" when jsp file uses xml syntax
Nicola Isotta created NETBEANS-4490: --- Summary: "Could not add one or more tag libraries" when jsp file uses xml syntax Key: NETBEANS-4490 URL: https://issues.apache.org/jira/browse/NETBEANS-4490 Project: NetBeans Issue Type: Bug Components: javaee - JSP, javaee - Web Project Affects Versions: 12.0 Reporter: Nicola Isotta When a .jsp uses xml syntax, tld loading breaks. Root cause seems to be PWC6226 from jasper compiler. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2277) Unable to load TLD, when jsp-config is defined
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-2277: Summary: Unable to load TLD, when jsp-config is defined (was: Unable to load TLD) > Unable to load TLD, when jsp-config is defined > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 8.2, 11.0, 12.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > When jsp-config is added to web.xml, TLD loading breaks with root cause > PWC6169 > !netbeans-bug.jpg|width=833,height=457! > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-2277: Component/s: javaee - JSP Description: The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the last version I can use with this type of projects). When jsp-config is added to web.xml, TLD loading breaks with root cause PWC6169 !netbeans-bug.jpg|width=833,height=457! was: The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the last version I can use with this type of projects). !netbeans-bug.jpg|width=833,height=457! I've attached a zipped project affected by the bug, because I was not able to reproduce the problem with a project created from scratch. > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - JSP, javaee - Web Project >Affects Versions: 8.2, 11.0, 12.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > When jsp-config is added to web.xml, TLD loading breaks with root cause > PWC6169 > !netbeans-bug.jpg|width=833,height=457! > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141891#comment-17141891 ] Nicola Isotta commented on NETBEANS-2277: - Renaming to better explain the issue. > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0, 12.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2277) Unable to load TLD
[
https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138477#comment-17138477
]
Nicola Isotta edited comment on NETBEANS-2277 at 6/17/20, 3:24 PM:
---
Seems like the cause is the jsp-config part in web.xml
If I comment this:
{code:java}
*.jspf
true
{code}
TLD loading works fine.
The problems is that my .jspf and .jsp are actually using xml syntax :(
was (Author: nicolaisotta):
Seems like the problem is the jsp-config part in web.xml
If I comment this:
{code:java}
*.jspf
true
{code}
TLD loading works fine.
The problems is that my jsp fragments are actually using xml syntax :(
> Unable to load TLD
> --
>
> Key: NETBEANS-2277
> URL: https://issues.apache.org/jira/browse/NETBEANS-2277
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 8.2, 11.0, 12.0
> Environment: Windows 10, JDK 8, Netbeans 11.0 vc3
>Reporter: Nicola Isotta
>Assignee: Nicola Isotta
>Priority: Major
> Attachments: JSF12JSPBug.zip, netbeans-bug.jpg
>
>
> The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the
> last version I can use with this type of projects).
> !netbeans-bug.jpg|width=833,height=457!
> I've attached a zipped project affected by the bug, because I was not able to
> reproduce the problem with a project created from scratch.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2277) Unable to load TLD
[
https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138477#comment-17138477
]
Nicola Isotta commented on NETBEANS-2277:
-
Seems like the problem is the jsp-config part in web.xml
If I comment this:
{code:java}
*.jspf
true
{code}
TLD loading works fine.
The problems is that my jsp fragments are actually using xml syntax :(
> Unable to load TLD
> --
>
> Key: NETBEANS-2277
> URL: https://issues.apache.org/jira/browse/NETBEANS-2277
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 8.2, 11.0, 12.0
> Environment: Windows 10, JDK 8, Netbeans 11.0 vc3
>Reporter: Nicola Isotta
>Assignee: Nicola Isotta
>Priority: Major
> Attachments: JSF12JSPBug.zip, netbeans-bug.jpg
>
>
> The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the
> last version I can use with this type of projects).
> !netbeans-bug.jpg|width=833,height=457!
> I've attached a zipped project affected by the bug, because I was not able to
> reproduce the problem with a project created from scratch.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-2277) Unable to load TLD
[
https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135785#comment-17135785
]
Nicola Isotta edited comment on NETBEANS-2277 at 6/15/20, 1:20 PM:
---
Unfortunately not.
was (Author: nicolaisotta):
Unfortunately not.
Howerever, I think I found out the cause: if I remove this part from the
web.xml, TLD loading works flawlessly:
{{}}
{{ }}
{{ *.jspf}}
{{ true}}
{{ }}
{{}}
> Unable to load TLD
> --
>
> Key: NETBEANS-2277
> URL: https://issues.apache.org/jira/browse/NETBEANS-2277
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 8.2, 11.0, 12.0
> Environment: Windows 10, JDK 8, Netbeans 11.0 vc3
>Reporter: Nicola Isotta
>Assignee: Nicola Isotta
>Priority: Major
> Attachments: JSF12JSPBug.zip, netbeans-bug.jpg
>
>
> The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the
> last version I can use with this type of projects).
> !netbeans-bug.jpg|width=833,height=457!
> I've attached a zipped project affected by the bug, because I was not able to
> reproduce the problem with a project created from scratch.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2277) Unable to load TLD
[
https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135785#comment-17135785
]
Nicola Isotta commented on NETBEANS-2277:
-
Unfortunately not.
Howerever, I think I found out the cause: if I remove this part from the
web.xml, TLD loading works flawlessly:
{{}}
{{ }}
{{ *.jspf}}
{{ true}}
{{ }}
{{}}
> Unable to load TLD
> --
>
> Key: NETBEANS-2277
> URL: https://issues.apache.org/jira/browse/NETBEANS-2277
> Project: NetBeans
> Issue Type: Bug
> Components: javaee - Web Project
>Affects Versions: 8.2, 11.0, 12.0
> Environment: Windows 10, JDK 8, Netbeans 11.0 vc3
>Reporter: Nicola Isotta
>Assignee: Nicola Isotta
>Priority: Major
> Attachments: JSF12JSPBug.zip, netbeans-bug.jpg
>
>
> The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the
> last version I can use with this type of projects).
> !netbeans-bug.jpg|width=833,height=457!
> I've attached a zipped project affected by the bug, because I was not able to
> reproduce the problem with a project created from scratch.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135607#comment-17135607 ] Nicola Isotta commented on NETBEANS-2277: - 12.0 is affected too. Any hint on how to solve? I cannot move from 8.1 because of this. > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0, 12.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-2277: Affects Version/s: 12.0 > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0, 12.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
[
https://issues.apache.org/jira/browse/NETBEANS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-3920:
Description:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), and has some known problems (e.g. the build
may fail in Windows if the project path contains spaces).
Plugin development is now on Github
([https://github.com/eclipse-ee4j/metro-jax-ws]) and new plugin version have
been published under the com.sun.xml.ws groupId
([https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]).
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
was:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmantained (see on maven) and has some known
problems (e.g. the build may fail in Windows if the project path contains
spaces).
Plugin development is now on Github
([https://github.com/eclipse-ee4j/metro-jax-ws]) and new plugin version have
been published under the com.sun.xml.ws groupId
([https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]).
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
> JAX-WS: old version of maven plugin is used
> ---
>
> Key: NETBEANS-3920
> URL: https://issues.apache.org/jira/browse/NETBEANS-3920
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - Maven, webservices - JAX-WS
>Affects Versions: 11.2
>Reporter: Nicola Isotta
>Priority: Minor
>
> When importing a WSDL in a Maven Project using the "Web Service Client"
> option, a plugin is added to the POM:
> {code:java}
>
> org.jvnet.jax-ws-commons
> jaxws-maven-plugin
> 2.3
> ...
>
> {code}
> This version is very old (2013), and has some known problems (e.g. the build
> may fail in Windows if the project path contains spaces).
> Plugin development is now on Github
> ([https://github.com/eclipse-ee4j/metro-jax-ws]) and new plugin version have
> been published under the com.sun.xml.ws groupId
> ([https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]).
> The aren't breaking changes in plugin configuration so I thinink it's safe to
> move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
[
https://issues.apache.org/jira/browse/NETBEANS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-3920:
Description:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmantained (see on maven) and has some known
problems (e.g. the build may fail in Windows if the project path contains
spaces).
Plugin development is now on Github
([https://github.com/eclipse-ee4j/metro-jax-ws]) and new plugin version have
been published under the com.sun.xml.ws groupId
([https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]).
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
was:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmantained (see on maven) and has some known
problems (e.g. the build may fail in Windows if the project path contains
spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
> JAX-WS: old version of maven plugin is used
> ---
>
> Key: NETBEANS-3920
> URL: https://issues.apache.org/jira/browse/NETBEANS-3920
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - Maven, webservices - JAX-WS
>Affects Versions: 11.2
>Reporter: Nicola Isotta
>Priority: Minor
>
> When importing a WSDL in a Maven Project using the "Web Service Client"
> option, a plugin is added to the POM:
> {code:java}
>
> org.jvnet.jax-ws-commons
> jaxws-maven-plugin
> 2.3
> ...
>
> {code}
> This version is very old (2013), unmantained (see on maven) and has some
> known problems (e.g. the build may fail in Windows if the project path
> contains spaces).
> Plugin development is now on Github
> ([https://github.com/eclipse-ee4j/metro-jax-ws]) and new plugin version have
> been published under the com.sun.xml.ws groupId
> ([https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]).
> The aren't breaking changes in plugin configuration so I thinink it's safe to
> move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
[
https://issues.apache.org/jira/browse/NETBEANS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-3920:
Description:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmatained (see [on
maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
was:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
org.jvnet.jax-ws-commons
jaxws-maven-plugin 2.3 ...
This version is very old (2013), unmatained (see [on
maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
> JAX-WS: old version of maven plugin is used
> ---
>
> Key: NETBEANS-3920
> URL: https://issues.apache.org/jira/browse/NETBEANS-3920
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - Maven, webservices - JAX-WS
>Affects Versions: 11.2
>Reporter: Nicola Isotta
>Priority: Minor
>
> When importing a WSDL in a Maven Project using the "Web Service Client"
> option, a plugin is added to the POM:
> {code:java}
>
> org.jvnet.jax-ws-commons
> jaxws-maven-plugin
> 2.3
> ...
>
> {code}
> This version is very old (2013), unmatained (see [on
> maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
> and has some known problems (e.g. the build may fail in Windows if the
> project path contains spaces).
> Plugin development is now on
> [GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin
> versions have been published under the [com.sun.xml.ws
> groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
> The aren't breaking changes in plugin configuration so I thinink it's safe to
> move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
[
https://issues.apache.org/jira/browse/NETBEANS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-3920:
Description:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmantained (see on maven) and has some known
problems (e.g. the build may fail in Windows if the project path contains
spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
was:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{code:java}
org.jvnet.jax-ws-commons
jaxws-maven-plugin
2.3
...
{code}
This version is very old (2013), unmatained (see [on
maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
> JAX-WS: old version of maven plugin is used
> ---
>
> Key: NETBEANS-3920
> URL: https://issues.apache.org/jira/browse/NETBEANS-3920
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - Maven, webservices - JAX-WS
>Affects Versions: 11.2
>Reporter: Nicola Isotta
>Priority: Minor
>
> When importing a WSDL in a Maven Project using the "Web Service Client"
> option, a plugin is added to the POM:
> {code:java}
>
> org.jvnet.jax-ws-commons
> jaxws-maven-plugin
> 2.3
> ...
>
> {code}
> This version is very old (2013), unmantained (see on maven) and has some
> known problems (e.g. the build may fail in Windows if the project path
> contains spaces).
> Plugin development is now on
> [GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin
> versions have been published under the [com.sun.xml.ws
> groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
> The aren't breaking changes in plugin configuration so I thinink it's safe to
> move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
[
https://issues.apache.org/jira/browse/NETBEANS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Isotta updated NETBEANS-3920:
Description:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
org.jvnet.jax-ws-commons
jaxws-maven-plugin 2.3 ...
This version is very old (2013), unmatained (see [on
maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
was:
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{{}}
{{ org.jvnet.jax-ws-commons}}
{{ jaxws-maven-plugin}}
{{ 2.3}}{{...}}{{ }}
This version is very old (2013), unmatained (see
[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
> JAX-WS: old version of maven plugin is used
> ---
>
> Key: NETBEANS-3920
> URL: https://issues.apache.org/jira/browse/NETBEANS-3920
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - Maven, webservices - JAX-WS
>Affects Versions: 11.2
>Reporter: Nicola Isotta
>Priority: Minor
>
> When importing a WSDL in a Maven Project using the "Web Service Client"
> option, a plugin is added to the POM:
> org.jvnet.jax-ws-commons
> jaxws-maven-plugin 2.3
> ...
> This version is very old (2013), unmatained (see [on
> maven|[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/]])
> and has some known problems (e.g. the build may fail in Windows if the
> project path contains spaces).
> Plugin development is now on
> [GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin
> versions have been published under the [com.sun.xml.ws
> groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
> The aren't breaking changes in plugin configuration so I thinink it's safe to
> move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3920) JAX-WS: old version of maven plugin is used
Nicola Isotta created NETBEANS-3920:
---
Summary: JAX-WS: old version of maven plugin is used
Key: NETBEANS-3920
URL: https://issues.apache.org/jira/browse/NETBEANS-3920
Project: NetBeans
Issue Type: Improvement
Components: javaee - Maven, webservices - JAX-WS
Affects Versions: 11.2
Reporter: Nicola Isotta
When importing a WSDL in a Maven Project using the "Web Service Client" option,
a plugin is added to the POM:
{{}}
{{ org.jvnet.jax-ws-commons}}
{{ jaxws-maven-plugin}}
{{ 2.3}}{{...}}{{ }}
This version is very old (2013), unmatained (see
[https://repo.maven.apache.org/maven2/org/jvnet/jax-ws-commons/jaxws-maven-plugin/])
and has some known problems (e.g. the build may fail in Windows if the project
path contains spaces).
Plugin development is now on
[GitHub|[https://github.com/eclipse-ee4j/metro-jax-ws]] and new plugin versions
have been published under the [com.sun.xml.ws
groupId|[https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-maven-plugin]].
The aren't breaking changes in plugin configuration so I thinink it's safe to
move to the new plugin version by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta reassigned NETBEANS-2277: --- Assignee: Nicola Isotta > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Assignee: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- 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-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835443#comment-16835443 ] Nicola Isotta commented on NETBEANS-2277: - Bugzilla similar issue: https://netbeans.org/bugzilla/show_bug.cgi?id=268678 > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- 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-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799581#comment-16799581 ] Nicola Isotta commented on NETBEANS-2277: - Using the JSF 1.2 library Netbeans provides doesn't fix the issue. > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- 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-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-2277: Priority: Major (was: Minor) > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Priority: Major > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- 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-2277) Unable to load TLD
[ https://issues.apache.org/jira/browse/NETBEANS-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Isotta updated NETBEANS-2277: Description: The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the last version I can use with this type of projects). !netbeans-bug.jpg|width=833,height=457! I've attached a zipped project affected by the bug, because I was not able to reproduce the problem with a project created from scratch. was: The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the last version I can use with this type of projects). !netbeans-bug.jpg|width=833,height=457! I've attached a zipped project which _should_ be affected by the bug, because I was not able to reproduce the problem with a project created from scratch. > Unable to load TLD > -- > > Key: NETBEANS-2277 > URL: https://issues.apache.org/jira/browse/NETBEANS-2277 > Project: NetBeans > Issue Type: Bug > Components: javaee - Web Project >Affects Versions: 8.2, 11.0 > Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 >Reporter: Nicola Isotta >Priority: Minor > Attachments: JSF12JSPBug.zip, netbeans-bug.jpg > > > The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the > last version I can use with this type of projects). > !netbeans-bug.jpg|width=833,height=457! > I've attached a zipped project affected by the bug, because I was not able to > reproduce the problem with a project created from scratch. > -- 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-2277) Unable to load TLD
Nicola Isotta created NETBEANS-2277: --- Summary: Unable to load TLD Key: NETBEANS-2277 URL: https://issues.apache.org/jira/browse/NETBEANS-2277 Project: NetBeans Issue Type: Bug Components: javaee - Web Project Affects Versions: 8.2, 11.0 Environment: Windows 10, JDK 8, Netbeans 11.0 vc3 Reporter: Nicola Isotta Attachments: JSF12JSPBug.zip, netbeans-bug.jpg The issue affects Ant Web project, and appeared in version 8.2 (8.1 is the last version I can use with this type of projects). !netbeans-bug.jpg|width=833,height=457! I've attached a zipped project which _should_ be affected by the bug, because I was not able to reproduce the problem with a project created from scratch. -- 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-2257) Cannot close ant web project
Nicola Isotta created NETBEANS-2257:
---
Summary: Cannot close ant web project
Key: NETBEANS-2257
URL: https://issues.apache.org/jira/browse/NETBEANS-2257
Project: NetBeans
Issue Type: Bug
Components: projects - Ant Project
Affects Versions: 11.0
Environment: Windows 10, JDK 8
Reporter: Nicola Isotta
Attachments: messages.log
{color:#33}I get this: {color}
{code:java|bgColor=#f5f5f5}
java.lang.IllegalArgumentException: more than one element with same name
found{code}
when trying to close an ant web project. messages.log attached.
(It happens in 8.1 too)
--
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
