[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-14642:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> How to automate process of bumping version for changed modules/submodules for every release
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14642
> URL: https://issues.jboss.org/browse/JBIDE-14642
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Optional
> Labels: versioning
> Fix For: 4.5.x
>
>
> The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped.
> We need two things:
> A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing)
> B) document/automate a process which every affected lead can follow to make this happen and if not See #A
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22860:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Application Wizard: Improve layout for templates
> ------------------------------------------------
>
> Key: JBIDE-22860
> URL: https://issues.jboss.org/browse/JBIDE-22860
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.5.x
>
>
> In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-19061) JAX-RS Web Services node sometimes does not show properly path changes
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19061?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-19061:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> JAX-RS Web Services node sometimes does not show properly path changes
> ----------------------------------------------------------------------
>
> Key: JBIDE-19061
> URL: https://issues.jboss.org/browse/JBIDE-19061
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: jax-rs
> Fix For: 4.5.x
>
>
> If I am using for @PathParam injection of fields, sometimes changes are not shown properly.
> First issue is with showing error validation mark. This mark (red cross in left bottom corner of Tree Item) is shown in case of deletion of injection field with their @PathParam annotations. If I have a method annotated with {code}@Path("{first}/{second}"){code} and I have fields annotated @PathParam("first") and @PathParam("second"), after removing those fields (holding backspace or marking whole area and delete) AND not saving opened java file in editor, then the mentioned marker is shown. After saving class, marker is removed, but nothing else is happened, even sometimes there should happen something (e.g. propagating of changes of path params types in real time).
> Second issue is showing correctly current content of editor in JAX-RS Web Services node. Sometimes the change are not progapated correctly in real time and type of one or both parameters are not correct. This is related to JBIDE-17663, but work flow in specified JIRA is working for that issue. This is more like "clicking and trying to break it" attempts which lead to inconsistencies. So far I have not noticed something what could me tell specific use case to get broken URI matching patterns in JAX-RS Web Services node.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Dmitrii Bocharov updated JBIDE-2720:
------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
> Attachments: .mozconfig, Unbenannt.PNG, Unbenannt.PNG, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-17442) BrowserSim crash on Fedora 20 when browsing jQuery Mobile app
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17442?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-17442:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> BrowserSim crash on Fedora 20 when browsing jQuery Mobile app
> -------------------------------------------------------------
>
> Key: JBIDE-17442
> URL: https://issues.jboss.org/browse/JBIDE-17442
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 20
> JBoss Developer Studio 8.0.0.Beta1
> webkitgtk-2.2.7-1.fc20.x86_64
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> BrowserSim crashes when launching the TicketMonster app (from WFK 2.6). The offending line of code seems to be :
> {noformat}
> $("#container").enhanceWithin();
> {noformat}
> in the mobile {{router.js}}. The [enhanceWithin API|http://api.jquerymobile.com/enhanceWithin/] is new in jQueryMobile 1.4.x. The same line works without any flaw in BrowserSim on Windows and Mac OS X. It also works without problems in Chrome 34 and Firefox 28 on Fedora 20.
> The crash occurred on both GTK2 and GTK3 engines.
> Additional notes - strace output reveals that BrowserSim is terminated due to a SIGTRAP event, which is a bit weird.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-10239) Support JAX-RS Path/PathParam refactoring
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10239?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-10239:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Support JAX-RS Path/PathParam refactoring
> -----------------------------------------
>
> Key: JBIDE-10239
> URL: https://issues.jboss.org/browse/JBIDE-10239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 3.3.0.M4
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: jax-rs
> Fix For: 4.5.x
>
>
> When refactoring code like the one below:
> {code}
> @GET
> @Path("{id}")
> public Response getCustomer(@PathParam("id") Integer id, @Context UriInfo uriInfo) {
> ResponseBuilder responseBuilder = Response.ok().entity(null);
> return responseBuilder.build();
> }
> {code}
> If changing the 'id' name of the first parameter, the user may also want to rename the @PathParam and @Path values to keep the consistency.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22953) FileNotFoundException below CordovaPluginXmlUtil.getPluginsfromFiles (thrown in FileInputStream.open0)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22953?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22953:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> FileNotFoundException below CordovaPluginXmlUtil.getPluginsfromFiles (thrown in FileInputStream.open0)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22953
> URL: https://issues.jboss.org/browse/JBIDE-22953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: java.io.FileNotFoundException: C:\vso-tfs\CareTrail\StatChat\plugins\cordova-plugin-ionic-keyboard\plugin.xml (The system cannot find the file specified)
> {noformat}
> java.io.FileNotFoundException: C:\vso-tfs\CareTrail\StatChat\plugins\cordova-plugin-ionic-keyboard\plugin.xml (The system cannot find the file specified)
> at java.io.FileInputStream.open0(null:-2)
> at java.io.FileInputStream.open(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at sun.net.www.protocol.file.FileURLConnection.connect(null:-1)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream(null:-1)
> at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(null:-1)
> at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(null:-1)
> at javax.xml.parsers.DocumentBuilder.parse(null:-1)
> at org.jboss.tools.cordovasim.eclipse.internal.util.CordovaPluginXmlUtil.getPluginsfromFiles(CordovaPluginXmlUtil.java:83)
> at org.jboss.tools.cordovasim.eclipse.servlet.internal.CordovaPluginJsServlet.doGet(CordovaPluginJsServlet.java:55)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:499)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | javax.servlet | 3.1.0.v201410161800 | 3.1.0.v201410161800 |
> | javax.xml | 1.3.4.v201005080400 | 1.3.4.v201005080400 |
> | org.eclipse.jetty.io | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.rewrite | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.server | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.servlet | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.util | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.jboss.tools.cordovasim.eclipse | 3.7.1.Final-v20160331-0435-B86 | 3.7.1.Final-v20160331-0435-B86 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5772820ce4b03c6ed0...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months