April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-15884: ------------------------------------- [~vineet.reynolds], usage of the command: {code} <command required="false" serialization="org.jboss.tools.browsersim.eclipse.commands.runBrowserSimforCheatsheet(ur..."/> {code} Also want to give a heads up. I guess, cheatsheets which use browsersim command are broken for now, due to the fact that while refactoring redundant *vpe* name prefix was removed from plugins, packages, and commands declaration. If you point me to the repos where browsersim is used for cheatsheets I would provide PRs with fixes. > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18975) VPE Preview tab is always empty for HTML5 content

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18975?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18975: --------------------------------------- Works for me too! In JBDS 9.0.0.Alpha2 B24 BYOE on Mac. > VPE Preview tab is always empty for HTML5 content > ------------------------------------------------- > > Key: JBIDE-18975 > URL: https://issues.jboss.org/browse/JBIDE-18975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.1.Final > Environment: Ubuntu 14.10 / Fedora 20 Linux x86_64 OpenJDK 7 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- the above examples are the minority and most of these does *not* make sense to share the same root parent jbosstools pom. So I think we are comparing apple and oranges here and these are examples we should look at cleaning up/splitting out since we have over time added to much entangled info into that one single jbosstools parent pom. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-19343. ---------------------------------- Yes, let's close it. I'm not sure the applied patch is 100% perfect for the use-case, but it's not something that is easy to fixed on our side, as it's more because of Maven not allowing boolean expressions. > integration tests do not fetch their required runtimes if not present in the cache folder > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19343 > URL: https://issues.jboss.org/browse/JBIDE-19343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, build, server > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html ) > Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests. > There are a number of such phase bindings in this test: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/... > And I think this step can be skipped w/ *-DskipTests*. > But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder? > Here are some console log snipped from builds 119 - 123: > {code} > 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1] > 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1] > 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18987) [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18987?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18987. ------------------------------- Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25 > [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-18987 > URL: https://issues.jboss.org/browse/JBIDE-18987 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.2.1.Final > Environment: Ubuntu Linux x86_64 > OpenJDK 7 > SWT_GTK3=1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > {code}Exception in thread "Thread-902" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137) > at org.eclipse.core.internal.resources.Container.getFile(Container.java:208) > at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68) > at java.lang.Thread.run(Thread.java:745) > Exception in thread "Thread-905" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137) > at org.eclipse.core.internal.resources.Container.getFile(Container.java:208) > at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68) > at java.lang.Thread.run(Thread.java:745) > Exception in thread "Thread-919" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137) > at org.eclipse.core.internal.resources.Container.getFile(Container.java:208) > at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83) > at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68) > at java.lang.Thread.run(Thread.java:745){code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14610: --------------------------------------------- https://issues.jboss.org/browse/JBIDE-18236 is the issue we got about how best find builds etc. for modules. > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16755) Confirmation pop-up when installing JRebel from Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16755: --------------------------------------------- Great its solved! to clarify on [~nickboldt] question - if it was not fixed then the issue is an upstream issue, but it still affects us and our users so it should have stayed open in that case IMO. > Confirmation pop-up when installing JRebel from Central > ------------------------------------------------------- > > Key: JBIDE-16755 > URL: https://issues.jboss.org/browse/JBIDE-16755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.3.0.Alpha2 > > Attachments: install-grinder-takes-forever.png, JBIDE-16755.jpeg, testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg > > > (Previously discussed in JBIDE-16269) > These builds are timing out: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18975) VPE Preview tab is always empty for HTML5 content

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18975?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18975. ------------------------------- Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25 > VPE Preview tab is always empty for HTML5 content > ------------------------------------------------- > > Key: JBIDE-18975 > URL: https://issues.jboss.org/browse/JBIDE-18975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.1.Final > Environment: Ubuntu 14.10 / Fedora 20 Linux x86_64 OpenJDK 7 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to "templatize" CI jobs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16158: ---------------------------------------- Sprint: Sprint #2 April 2015 > Investigate tools/processes to "templatize" CI jobs > --------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Fix For: 4.3.x > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13372?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13372: ---------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.x) > improve usability of jiralint emails > ------------------------------------ > > Key: JBIDE-13372 > URL: https://issues.jboss.org/browse/JBIDE-13372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.0.Final > > > Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras? > Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana. > {code} > -------- Original Message -------- > Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable! > Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST) > From: ci-builds(a)redhat.com > To: external-exadel-list(a)redhat.com > This is the weekly check for jira problems. > Please fix the issues outlined below if there are any. Thank you! > jbosstools-jiralint - Build # 138 - Still Unstable: > Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results. > 1 tests 1 failure(s) / -2 > 1 tests failed. > FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza > Error Message: > https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions. > Stack Trace: > JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332) > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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