May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17002: --------------------------------------------- You do not need to rebuild a new central target platform to add a url under our public URLs instead of having it under update/requirements which is *not* to be exposed. The original plan doesn't mention we would suddenly change to use internal urls for what we give to users. The effect on endusers are *not* identical since they now have a third different url than main updatesite and central and it implies other parts under updates/requirements are okey to use/expose when it is not. > Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2 > ----------------------------------------------------------- > > Key: JBIDE-17002 > URL: https://issues.jboss.org/browse/JBIDE-17002 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.2.Final > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 4.1.2.Final > > Attachments: java-8-in-kepler-central-site.png, java-8-in-kepler-central-site2.png, jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png > > > We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP. > * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/ > * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905 > * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032... > All 3 features should be available via a unique connector in JBoss Central > Software Updates -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17117) Simplify publish process

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17117: --------------------------------------------- about composite usage then i'm 99% it uses p2 since eclipse update is simply not packaged anymore. And http://download.eclipse.org/jetty/updates/jetty-wtp has no site.xml, it has a compositeContent.xml (http://download.eclipse.org/jetty/updates/jetty-wtp/compositeContent.xml) so somehow it seem to work for Jetty ? > Simplify publish process > ------------------------ > > Key: JBIDE-17117 > URL: https://issues.jboss.org/browse/JBIDE-17117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > > We could work on improving the publishing process. Some ideas: > * Why do we rename the files we pull on sf.net. Also, renaming files could happen on sf.net. > * Files from sf.net could be fetch after (for example in parallel with creating marketplace entry) > * webtools should be published in a similar way as other parts (moved to tools/static/releases and then referenced in the composite file) > * Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL segments, so one would only have to move a single folder instead of 4 ones. > * Identify things that can be done in parallel. > * ... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17238) Fix broken server build

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17238?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17238. --------------------------------- Resolution: Done THis is like the 10th time that I break a build because of @Override tags. The cause is that my required execution environment is too low, so I've changed it to java6. > Fix broken server build > ----------------------- > > Key: JBIDE-17238 > URL: https://issues.jboss.org/browse/JBIDE-17238 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Server build is broken. It fails with compilation errors. > {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.ide.eclipse.as.classpath.core: Compilation failure: Compilation failure: > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/RuntimeClasspathModelIO.java:[97] > [ERROR] IMemento[] children = parent.getChildren(); > [ERROR] ^^^^^^^^^^^ > [ERROR] The method getChildren(String) in the type XMLMemento is not applicable for the arguments () > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/RuntimeClasspathModelIO.java:[100] > [ERROR] String name = children[i].getNodeName(); > [ERROR] ^^^^^^^^^^^ > [ERROR] The method getNodeName() is undefined for the type IMemento > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/RuntimePathProviderFileset.java:[54] > [ERROR] public String getDisplayString() { > [ERROR] ^^^^^^^^^^^^^^^^^^ > [ERROR] The method getDisplayString() of type RuntimePathProviderFileset must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/RuntimePathProviderFileset.java:[59] > [ERROR] public void saveInMemento(XMLMemento memento) { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method saveInMemento(XMLMemento) of type RuntimePathProviderFileset must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[104] > [ERROR] public IRuntimePathProvider[] getStandardProviders() { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method getStandardProviders() of type InternalRuntimeClasspathModel must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[109] > [ERROR] public IRuntimePathProvider[] getProvidersForFacet(String id) { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method getProvidersForFacet(String) of type InternalRuntimeClasspathModel must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[115] > [ERROR] public IRuntimePathProvider[] getProvidersForFacet(String id, String version) { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method getProvidersForFacet(String, String) of type InternalRuntimeClasspathModel must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[66] > [ERROR] public void setVariableResolver(IVariableResolver resolver) { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method setVariableResolver(IVariableResolver) of type LayeredProductPathProvider must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[71] > [ERROR] public String getDisplayString() { > [ERROR] ^^^^^^^^^^^^^^^^^^ > [ERROR] The method getDisplayString() of type LayeredProductPathProvider must override a superclass method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[76] > [ERROR] public void saveInMemento(XMLMemento memento) { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The method saveInMemento(XMLMemento) of type LayeredProductPathProvider must override a superclass method > [ERROR] 10 problems (10 errors) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17053) images on whatssnew would be great to have an easy way to show "full resolution"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17053?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17053: ------------------------------------ How about something simpler in the .adoc? {code} .Thumbnail linked to full image image:/images/font/screen2-thumb.gif[ "My screenshot",width=128, link="/images/font/screen2-full.gif"] {code} Or, I have code here that has a "click to enlarge" feature: {code:title=https://devstudio.jboss.com/earlyaccess/7.1.1.GA.html} <script type="text/javascript">  </script> ... then ... <p align="center"><a href="javascript:toggle()"><img border="0" id="screenshot" src="https://devstudio.jboss.com/images/jbds7-screenshot-browsersim-540.png"/><br/><small>Click to enlarge</small></a></p> {code} Of course you could parameterize it so it works on any image, eg., toggle('screenshot'), which would pull the image's id and use that to get the filenames to toggle > images on whatssnew would be great to have an easy way to show "full resolution" > -------------------------------------------------------------------------------- > > Key: JBIDE-17053 > URL: https://issues.jboss.org/browse/JBIDE-17053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17242) HTML validation should allow the 'role' attribute.

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17242?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-17242: ----------------------------------------- An UpStream issue is created: [Bug 434381 - HTML5 validation should allow the 'role' and 'aria-*' attributes|https://bugs.eclipse.org/bugs/show_bug.cgi?id=434381] > HTML validation should allow the 'role' attribute. > -------------------------------------------------- > > Key: JBIDE-17242 > URL: https://issues.jboss.org/browse/JBIDE-17242 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Joshua Wilson > Assignee: Victor Rubezhny > Priority: Minor > Fix For: 4.2.0.Beta2 > > > I found this out when trying to implement jQuery Mobile 1.4.2. There is over 20 different docs where they use the attribute 'role'. After looking into it, this is something that should be allowed by the HTML validator. The validator produces this warning, "Undefined attribute name (role)." > http://www.w3.org/TR/html5/dom.html#global-attributes states "To enable assistive technology products to expose a more fine-grained interface than is otherwise possible with HTML elements and attributes, a set of http://www.w3.org/TR/html5/dom.html#wai-aria can be specified (the ARIA http://www.w3.org/TR/html5/infrastructure.html#attr-aria-role and aria-* attributes). http://www.w3.org/TR/html5/references.html#refsARIA" > this is how it is linked to HTML5 : http://www.w3.org/TR/html5/dom.html#sec-implicit-aria-semantics > also see: http://www.w3.org/WAI/PF/aria/usage#usage_intro > A working example can be found in [contacts-mobile-basic|https://github.com/joshuawilson/jboss-wfk-quickstar...] -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16931) Support for linked folders in cordovasim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16931?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16931: --------------------------------------------- with respect to ex/wildcards then yes you'll need to have logic in the controllors to look up these paths. and yes, I was suggesting to put the server inside eclipse since it has all the info...livereload already can do this so maybe we should reuse that ? about linked folders then then just try create one - you can point to remote system files too. Note - for our usecase this is probably not required so would be sufficient to support local files - but if the server was inside eclipse it would not have to do these "virtual" mappings. > Support for linked folders in cordovasim > ---------------------------------------- > > Key: JBIDE-16931 > URL: https://issues.jboss.org/browse/JBIDE-16931 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Alpha2 > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Linked folders are not honored when project is run on CordovaSim -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17151) Improve the "New Restful Web Service" wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17151?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17151: --------------------------------------------- have a checkbox stating somethng like: [X] Generate Application class and have it be disabled/unselected if it is not needed. And then remember last chosen option and users can then control if they want it or not. > Improve the "New Restful Web Service" wizard > -------------------------------------------- > > Key: JBIDE-17151 > URL: https://issues.jboss.org/browse/JBIDE-17151 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta2 > > Attachments: current wizard.png, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.png > > > The current wizard could be improved after feedback on JBIDE-13309, JBIDE-13310 and internal discussion: > {quote} > - Choosing the first wizard shows an option to edit "Web Service" and "Application Class Name" and have the same values. Why this value need to be entered twice and how is it used ? > - web.xml is generated even though "Update web.xml" was not selected. Why can't ApplicationPath be used instead of web.xml anyway ? > - Even in the generated web.xml, the mapped path is {{/*}}. This is not the recommended practice as none of the Servlets or other resources in the application would then be resolved correctly. The recommendation is to use something like {{/webresources}}, {{/resources}}, or {{/rest}} and have all the resources be accessed from there. > - The generation of REST resource did not added JAX-RS facet to my project. Does it have to be manually added ? If yes, then why ? > - Adding JAX-RS facet shows "Further configuration required" and require me to specify "JAX-RS Servlet class name". How is the user expected to know the class name ? This should not even be required for a Java EE 6 application. > - In pure Java EE 6, there should be no need to ask that information anyway. Instead use {{@ApplicationPath}} to specify the base path of JAX-RS. > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17236) Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17236?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17236: --------------------------------------------- the PR seem to already be applied ? I'm missing tests for this - can you point me to them ? > Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17236 > URL: https://issues.jboss.org/browse/JBIDE-17236 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Beta2 > > > Projects that have a manifest.mf which declares Dependencies as per https://docs.jboss.org/author/display/MODULES/Manifest+module+information should have those dependent modules added to the classpath. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17236) Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17236?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17236: ---------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) > Add jboss-modules classpath entries if project's manifest.mf has Dependencies: attribute > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17236 > URL: https://issues.jboss.org/browse/JBIDE-17236 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Projects that have a manifest.mf which declares Dependencies as per https://docs.jboss.org/author/display/MODULES/Manifest+module+information should have those dependent modules added to the classpath. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17242) HTML validation should allow the 'role' attribute.

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17242?page=com.atlassian.jira.plugi... ] Joshua Wilson updated JBIDE-17242: ---------------------------------- Description: I found this out when trying to implement jQuery Mobile 1.4.2. There is over 20 different docs where they use the attribute 'role'. After looking into it, this is something that should be allowed by the HTML validator. The validator produces this warning, "Undefined attribute name (role)." http://www.w3.org/TR/html5/dom.html#global-attributes states "To enable assistive technology products to expose a more fine-grained interface than is otherwise possible with HTML elements and attributes, a set of http://www.w3.org/TR/html5/dom.html#wai-aria can be specified (the ARIA http://www.w3.org/TR/html5/infrastructure.html#attr-aria-role and aria-* attributes). http://www.w3.org/TR/html5/references.html#refsARIA" this is how it is linked to HTML5 : http://www.w3.org/TR/html5/dom.html#sec-implicit-aria-semantics also see: http://www.w3.org/WAI/PF/aria/usage#usage_intro A working example can be found in [contacts-mobile-basic|https://github.com/joshuawilson/jboss-wfk-quickstar...] was: I found this out when trying to implement jQuery Mobile 1.4.2. There is over 20 different docs where they use the attribute 'role'. After looking into it, this is something that should be allowed by the HTML validator. The validator produces this warning, "Undefined attribute name (role)." http://www.w3.org/TR/html5/dom.html#global-attributes states "To enable assistive technology products to expose a more fine-grained interface than is otherwise possible with HTML elements and attributes, a set of http://www.w3.org/TR/html5/dom.html#wai-aria can be specified (the ARIA http://www.w3.org/TR/html5/infrastructure.html#attr-aria-role and aria-* attributes). http://www.w3.org/TR/html5/references.html#refsARIA" this is how it is linked to HTML5 : http://www.w3.org/TR/html5/dom.html#sec-implicit-aria-semantics also see: http://www.w3.org/WAI/PF/aria/usage#usage_intro > HTML validation should allow the 'role' attribute. > -------------------------------------------------- > > Key: JBIDE-17242 > URL: https://issues.jboss.org/browse/JBIDE-17242 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Joshua Wilson > Assignee: Victor Rubezhny > Priority: Minor > Fix For: 4.2.0.Beta2 > > > I found this out when trying to implement jQuery Mobile 1.4.2. There is over 20 different docs where they use the attribute 'role'. After looking into it, this is something that should be allowed by the HTML validator. The validator produces this warning, "Undefined attribute name (role)." > http://www.w3.org/TR/html5/dom.html#global-attributes states "To enable assistive technology products to expose a more fine-grained interface than is otherwise possible with HTML elements and attributes, a set of http://www.w3.org/TR/html5/dom.html#wai-aria can be specified (the ARIA http://www.w3.org/TR/html5/infrastructure.html#attr-aria-role and aria-* attributes). http://www.w3.org/TR/html5/references.html#refsARIA" > this is how it is linked to HTML5 : http://www.w3.org/TR/html5/dom.html#sec-implicit-aria-semantics > also see: http://www.w3.org/WAI/PF/aria/usage#usage_intro > A working example can be found in [contacts-mobile-basic|https://github.com/joshuawilson/jboss-wfk-quickstar...] -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2014