January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21392) Composite install job is disabled and also component jobs are disabled therefore there is no nightly build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21392: --------------------------------------- [~nickboldt], there is now a new build, but it's still Beta1. Looking at a random job [1], I can see it still uses the jbosstools-4.3.1.Beta1x branch, which seems wrong, no? I'm not saying that everybody has updated their 4.3.x branch yet, but updating the jobs is a good start. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Composite install job is disabled and also component jobs are disabled therefore there is no nightly build > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21392 > URL: https://issues.jboss.org/browse/JBIDE-21392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > Job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... is marked as disabled and also component jobs such as http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... and others are disabled. There was no build since 2015-12-16. Maybe it was disabled as a consequence/side effect of JBIDE-21145. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) ReLicense JBDS Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3557: -------------------------------- Sprint: Sprint #10 January 2016 > ReLicense JBDS Installer > ------------------------ > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Denis Golovin > Fix For: 9.1.0.Beta2 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20387: ---------------------------------- Sprint: (was: Sprint #10 January 2016) > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20442: ---------------------------------- Sprint: (was: Sprint #10 January 2016) > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-651) Update support matrix for JBDS 9.0 with latest Linux distros

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-651?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-651. ------------------------------ Resolution: Done Resolving old JIRAs. This task was duplicated and reviewed/approved by the QE team in another JIRA earlier. > Update support matrix for JBDS 9.0 with latest Linux distros > ------------------------------------------------------------ > > Key: TOOLSDOC-651 > URL: https://issues.jboss.org/browse/TOOLSDOC-651 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Martin Malina > Assignee: Misha Ali > > For JBDS 9.0 we should support these: > - RHEL 6 & 7 > - Fedora 22 and 21 (Fedora 20 & 19 to be dropped) 22 is due May 2015 [1] > - Ubuntu 14.04 LTS and 14.10. All the older Ubuntu versions can be dropped. Note: 15.04 would replace 14.10 if it lands in time. > The support matrix doc is here: https://access.redhat.com/articles/427493 > [1] http://fedoraproject.org/wiki/Releases/22/Schedule -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-2044: -------------------------------- > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) stop linking skipRequirements and tests.skip to download of requirements

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15332: ---------------------------------- Sprint: Sprint #10 January 2016 > stop linking skipRequirements and tests.skip to download of requirements > ------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.4.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) stop linking skipRequirements and tests.skip to download of requirements

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-15332: ------------------------------------- Assignee: Denis Golovin (was: Mickael Istria) > stop linking skipRequirements and tests.skip to download of requirements > ------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.4.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) stop linking skipRequirements and tests.skip to download of requirements

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15332: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: LATER) > stop linking skipRequirements and tests.skip to download of requirements > ------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: 4.4.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-667) Document how to use the EAP online maven repo

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-667?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-667: ---------------------------------- Assignee: Supriya Bharadwaj (was: Misha Ali) > Document how to use the EAP online maven repo > --------------------------------------------- > > Key: TOOLSDOC-667 > URL: https://issues.jboss.org/browse/TOOLSDOC-667 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Affects Versions: 4.3.0.Final > Reporter: Martin Malina > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > In TOOLSDOC-499 it was mentioned that we have a guide that explains how to add jboss enterprise maven repositories, but it would be nice to also mention the alternative of using the online repo. > From TOOLSDOC-499: > {quote} > Alternatively, you can use the online repository: In the Add Maven Repository dialog, in the Profile ID field at the top, select "redhat-techpreview-all-repository" in the drop down menu. This will add http://maven.repository.redhat.com/techpreview/all/ to your settings.xml and that should satisfy the dependencies. > {quote} > Something similar could be added in a box in this doc: > https://access.redhat.com/articles/1160993#ConfigureMaven > (or a similar doc for JBDS 9 once it's ready) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016