[ 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)
[ 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)
[ 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)
[ 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)
[ 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)
[ 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)
[ https://issues.jboss.org/browse/TOOLSDOC-667?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-667:
-------------------------------
Sprint: 04-Jan >> 17-Jan 2016-JBDS/JBT
> 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: Misha Ali
> 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)
[ https://issues.jboss.org/browse/TOOLSDOC-691?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-691:
----------------------------------
Description: Review and update install guide for Beta 1
Assignee: Supriya Bharadwaj (was: Misha Ali)
Closing this as [~supriya.bharadwaj] has already taken care of this task. If this is not the case, Supriya, please reopen this JIRA.
> JBDS 9.1 Beta1: Install Guide Review
> ------------------------------------
>
> Key: TOOLSDOC-691
> URL: https://issues.jboss.org/browse/TOOLSDOC-691
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
>
> Review and update install guide for Beta 1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)