[JBoss JIRA] (JBIDE-12972) Add FestAssert to the TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12972?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-12972:
----------------------------------------
Ok, I'll investigate later whether packaging can be improved without risk.
> Add FestAssert to the TP
> ------------------------
>
> Key: JBIDE-12972
> URL: https://issues.jboss.org/browse/JBIDE-12972
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.0.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> It would be great if we could use in our tests. We would have to add it to our target platform (TP) for our plugins to use it.
> Reason: FestAssert provides us with a Fluent API to write test assertions.
> License and owner: Apache License 2.0 / http://code.google.com/p/fest/
> Original repository: (not an Eclipse bundle yet). Source and binaries available on Maven (https://repository.jboss.org/nexus/content/groups/public/org/easytesting/... and https://repository.jboss.org/nexus/content/groups/public/org/easytesting/...)
> JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/fest-assert ?
> Source: https://github.com/alexruiz/fest-assert-1.x
> Affected projects: LiveReload for now, JAX-RS in the future
> Required in devstudio: No for now (if LiveReload is considered incubation)
> Type of dependency: testing
> List of bundles added/removed: fest-assert, fest-util
> Fest-assert provides a fluent API to perform asertions in JUnit tests. It is also nice to use when the objects to tests are collections.
> To convince you of the interest of fest-assert, here are a few syntax examples:
> - In LiveReload-test plugin:
> {code}
> assertThat(new String(modifiedContent)).doesNotContain(addition + "</body>");
> {code}
> - a more complete example of usage in openShift-java-client (not an Eclipse plugin, though, but it gives an idea of the chained assertions that can be performed)
> {code}
> assertThat(new GearGroupsAssert(gearGroups))
> .assertGroup(0).hasUUID().hasGears()
> .assertGear(0).hasId().hasState();
> {code}
> - in case of assertion failure on such a statement:
> {code}
> Assertions.assertThat(commands).hasSize(2);
> {code}
> the exception message will look like this:
> {code}
> java.lang.AssertionError: expected size:<2> but was:<1> for <['{"command":"reload","path":null,"liveCSS":true}']>
> at org.fest.assertions.Fail.failure(Fail.java:228)
> at org.fest.assertions.Assert.failure(Assert.java:149)
> at org.fest.assertions.GroupAssert.hasSize(GroupAssert.java:89)
> at org.jboss.tools.livereload.internal.service.LiveReloadCommandGeneratorTestCase.shouldGenerateCommandForIndexHtmlFileAfterSingleChange(LiveReloadCommandGeneratorTestCase.java:45)
> at ...
> {code}
> See more examples here: http://code.google.com/p/fest/#Fluent_Assertions
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17209:
-------------------------------------
[~akazakov] Do you plan on working on this issue? If not, please retarget to proper version. Thanks.
> only product for mylyn integration is JBossAS Server
> ----------------------------------------------------
>
> Key: JBIDE-17209
> URL: https://issues.jboss.org/browse/JBIDE-17209
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, common/jst/core, server
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server.
> I would have expected Developer Studio too at least, and a few more key components.
> Note: this might not be something base should add, but put it into central or jbds product makes sense I think.
> -- Configuration Details --
> Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product)
> Installed Features:
> org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-17213) Improve the default value of Download folder in the download runtimes wizard
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17213?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17213.
---------------------------------
Assignee: Rob Stryker (was: Snjezana Peco)
Resolution: Done
We currently *do* use java.io.tempdir, but we appear to be saving the value whether the user has changed it or not. So, if a user runs first in an OS where /tmp is valid, and downloads a runtime, it will persist /tmp as the user's choice, and, on next load, will use that saved value rather than the OS default.
I've made a very small patch to not save the value if the value is equal to the java.io.tempdir value.
> Improve the default value of Download folder in the download runtimes wizard
> ----------------------------------------------------------------------------
>
> Key: JBIDE-17213
> URL: https://issues.jboss.org/browse/JBIDE-17213
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta1
> Environment: Kubuntu 13.10
> Reporter: Lars Heinemann
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
> Attachments: jbt_downloadruntime.png
>
>
> The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS.
> I would propose to use java.io.tmpdir for the default value if possible and check if that is writable for the user. If thats not the case we should have some fallback folder.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18008:
-------------------------------------
Sorry I didn't get back to you. No. I have absolutely no intention on changing this until next major. I encourage you to move this issue forward.
> Nested jars prevent SonarQube/FindBugs from running
> ---------------------------------------------------
>
> Key: JBIDE-18008
> URL: https://issues.jboss.org/browse/JBIDE-18008
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes).
> Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1]
> {code}
> This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest
> Also, the jvmmonitor bundles use nested jars. We should avoid that too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov commented on JBIDE-8874:
-----------------------------------------------
[~dgolovin], your idea will work with this case, but I thing will broke webroot paths. Looks like a big risk.
> Support XML documents for XSLT compliant browser
> ------------------------------------------------
>
> Key: JBIDE-8874
> URL: https://issues.jboss.org/browse/JBIDE-8874
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot59.png, wecandoit.png, xml-xsl.png
>
>
> Would be good to have support to show documents for XSLT compliant browser like
> {code:title=cdcatalog.xsl|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!-- Edited by XMLSpy® -->
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/">
> <html>
> <body>
> <h2>My CD Collection</h2>
> <table border="1">
> <tr bgcolor="#9acd32">
> <th>Title</th>
> <th>Artist</th>
> </tr>
> <xsl:for-each select="catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:for-each>
> </table>
> </body>
> </html>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {code:title=page.xml|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?>
> <!-- Edited by XMLSpy® -->
> <catalog>
> <cd>
> <title>Empire Burlesque</title>
> <artist>Bob Dylan</artist>
> <country>USA</country>
> <company>Columbia</company>
> <price>10.90</price>
> <year>1985</year>
> </cd>
> <cd>
> <title>Hide your heart</title>
> <artist>Bonnie Tyler</artist>
> <country>UK</country>
> <company>CBS Records</company>
> <price>9.90</price>
> <year>1988</year>
> </cd>
> <cd>
> <title>Greatest Hits</title>
> <artist>Dolly Parton</artist>
> <country>USA</country>
> <company>RCA</company>
> <price>9.90</price>
> <year>1982</year>
> </cd>
> </catalog>
> {code}
> Visual part of editor would look like:
> !screenshot59.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-17934) cordova-3.5.0.jar missing when exporting andriod project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17934?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-17934.
----------------------------------
Resolution: Cannot Reproduce Bug
> cordova-3.5.0.jar missing when exporting andriod project
> --------------------------------------------------------
>
> Key: JBIDE-17934
> URL: https://issues.jboss.org/browse/JBIDE-17934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OSx 10.9.4, Eclipse Luna (4.4.0), Jboss Tools for Luna (4.2.0.Beta2), with Jboss Hybrid Mobile Tools + CordovaSim.
> Reporter: Asif Kilwani
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
>
> When trying to test "run on Andriod device" or export native platform project
> Error generating the native android project
> /Users/Administrator/.cordova/lib/android/cordova/3.5.0/framework/cordova-3.5.0.jar (No such file or directory)
> I deleted framework and downloaded again from properties, but same.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-18100) Application wizard, server adapter: Wizard choose existing application from server adapter selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18100?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18100:
-------------------------------------
Description:
This is happening only in wizard opened via shell menu (File - New - OpenShift Application). Opening New application wizard via Central and OpenShift explorer works fine (probably because of view focus).
Issue is preselected existing application in New application wizard although I had no intentions to do it. If I have selected a server adapter and then I opened New application wizard via shell menu and go via wizard to the third wizard page, where the field for using an existing project is placed, there is used project from existing selected server adapter. For better and more obvious explanation see attached video: [^out-1.ogv]
was:
This is happening only in wizard opened via shell menu (File - New - OpenShift Application). Opening New application wizard via Central and OpenShift explorer works fine (probably because of view focus).
Issue is preselected existing application in New application wizard although I had no intentions to do it. If I have selected a server adapter and then I opened New application wizard via shell menu and go via wizard to the third wizard page, where the field for using an existing project is placed, there is used project from existing selected server adapter. For better and more obvious explanation see attached video.
> Application wizard, server adapter: Wizard choose existing application from server adapter selection
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18100
> URL: https://issues.jboss.org/browse/JBIDE-18100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: out-1.ogv, selected-server-adapter.png, used-existing-project.png
>
>
> This is happening only in wizard opened via shell menu (File - New - OpenShift Application). Opening New application wizard via Central and OpenShift explorer works fine (probably because of view focus).
> Issue is preselected existing application in New application wizard although I had no intentions to do it. If I have selected a server adapter and then I opened New application wizard via shell menu and go via wizard to the third wizard page, where the field for using an existing project is placed, there is used project from existing selected server adapter. For better and more obvious explanation see attached video: [^out-1.ogv]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-18100) Application wizard, server adapter: Wizard choose existing application from server adapter selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18100?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18100:
-------------------------------------
Attachment: used-existing-project.png
selected-server-adapter.png
> Application wizard, server adapter: Wizard choose existing application from server adapter selection
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18100
> URL: https://issues.jboss.org/browse/JBIDE-18100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: out-1.ogv, selected-server-adapter.png, used-existing-project.png
>
>
> This is happening only in wizard opened via shell menu (File - New - OpenShift Application). Opening New application wizard via Central and OpenShift explorer works fine (probably because of view focus).
> Issue is preselected existing application in New application wizard although I had no intentions to do it. If I have selected a server adapter and then I opened New application wizard via shell menu and go via wizard to the third wizard page, where the field for using an existing project is placed, there is used project from existing selected server adapter. For better and more obvious explanation see attached video.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months