April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan reassigned ERT-132: -------------------------------- Assignee: Gorkem Ercan > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan reassigned ERT-132: -------------------------------- Assignee: (was: Gorkem Ercan) > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-132: ----------------------------- Flagged: Impediment > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-132: ----------------------------- Flagged: (was: Impediment) > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-131) Node.js launch should not be available on package.json [EBZ#491455]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-131?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-131. ------------------------------ Resolution: Done resolved upstream > Node.js launch should not be available on package.json [EBZ#491455] > ------------------------------------------------------------------- > > Key: ERT-131 > URL: https://issues.jboss.org/browse/ERT-131 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > It looks like Node launch on a package.json file should be disabled. Basically, there are 2 cases when Node lauch shoud be enabled: > 1) IProject with package.json > 2) js file (of the project with package.json) / excluding bower_component & n node_modules -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22208) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22208?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22208: ------------------------------------- ad7ea588f8f0bc32db1631ed6ce92a807eb6a182 - cherry-pick is empty c80d1a7bfc986f5d210cf4845101e4bad94d6ef1 - cherry-picked with merge errors 3fd35c68512402e60af5266f7e52dcef4a99dd64 - already present with different surrounding data a05bc5c15b4c29ff4333eb38791b2692427bfeb7- present in master with much longer commit message b4ab2ba6eace30e17c1aa7163c562b3dc35213ca - cherry-pick is empty, so must have been committed in pieces > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base] > ------------------------------------------------------------------------------------ > > Key: JBIDE-22208 > URL: https://issues.jboss.org/browse/JBIDE-22208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Base]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-base at https://github.com/jbosstools/jbosstools-base/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "3921b3" is the last common ancestor of jbosstools-4.3.x and master > 3921b3 is 58 commits ago in branch master > 3921b3 is 49 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-base//commit/baca71426ed2a9671af... > - https://github.com/jbosstools/jbosstools-base//commit/7de9cd6f3f900df915e... > - https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1... > - https://github.com/jbosstools/jbosstools-base//commit/436fd3abea851f273a5... > - https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210... > - https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af... > - https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff433... > - https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1... > - https://github.com/jbosstools/jbosstools-base//commit/ccf853567c6a4c21d52... > - https://github.com/jbosstools/jbosstools-base//commit/c8452d0c1ae1884777a... > - https://github.com/jbosstools/jbosstools-base//commit/f6a2717194354774fcb... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Base task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22208) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22208?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-22208. ------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base] > ------------------------------------------------------------------------------------ > > Key: JBIDE-22208 > URL: https://issues.jboss.org/browse/JBIDE-22208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Base]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-base at https://github.com/jbosstools/jbosstools-base/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "3921b3" is the last common ancestor of jbosstools-4.3.x and master > 3921b3 is 58 commits ago in branch master > 3921b3 is 49 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-base//commit/baca71426ed2a9671af... > - https://github.com/jbosstools/jbosstools-base//commit/7de9cd6f3f900df915e... > - https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1... > - https://github.com/jbosstools/jbosstools-base//commit/436fd3abea851f273a5... > - https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210... > - https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af... > - https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff433... > - https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1... > - https://github.com/jbosstools/jbosstools-base//commit/ccf853567c6a4c21d52... > - https://github.com/jbosstools/jbosstools-base//commit/c8452d0c1ae1884777a... > - https://github.com/jbosstools/jbosstools-base//commit/f6a2717194354774fcb... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Base task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22206) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22206?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22206: ------------------------------------- f8d95f7d1465dd60bed2f1df52ccca0173ee478e - can be ignored b1d95cd1ee50b92c1674e142f8ed5789b5dfcc2c - has matching patch 8b5b5bc4eb0c5ad2fd44410c7c417360ff45a9b8 (different based on surrounding version number) fdf66d3515c5f07829593c607dfd7b783415e17c - cherry-picked cleanly just now. bbf53cbb92c7cfc10805500ef399d4962341bc53 - seems to have been committed over 2 commits. cherry-pick was empty. > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22206 > URL: https://issues.jboss.org/browse/JBIDE-22206 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Server]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "ecbe98" is the last common ancestor of jbosstools-4.3.x and master > ecbe98 is 50 commits ago in branch master > ecbe98 is 52 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b... > - https://github.com/jbosstools/jbosstools-server//commit/122eb9e528632345c... > - https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1... > - https://github.com/jbosstools/jbosstools-server//commit/a9a35aee507b59453... > - https://github.com/jbosstools/jbosstools-server//commit/078a82d8f76cb02e3... > - https://github.com/jbosstools/jbosstools-server//commit/c1c87bd10ba0e9a2c... > - https://github.com/jbosstools/jbosstools-server//commit/784c82b35b3843f8e... > - https://github.com/jbosstools/jbosstools-server//commit/648b5425c80e6301d... > - https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782... > - https://github.com/jbosstools/jbosstools-server//commit/7d6b1b7e31194bf49... > - https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22206) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22206?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-22206. ------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22206 > URL: https://issues.jboss.org/browse/JBIDE-22206 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Server]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "ecbe98" is the last common ancestor of jbosstools-4.3.x and master > ecbe98 is 50 commits ago in branch master > ecbe98 is 52 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b... > - https://github.com/jbosstools/jbosstools-server//commit/122eb9e528632345c... > - https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1... > - https://github.com/jbosstools/jbosstools-server//commit/a9a35aee507b59453... > - https://github.com/jbosstools/jbosstools-server//commit/078a82d8f76cb02e3... > - https://github.com/jbosstools/jbosstools-server//commit/c1c87bd10ba0e9a2c... > - https://github.com/jbosstools/jbosstools-server//commit/784c82b35b3843f8e... > - https://github.com/jbosstools/jbosstools-server//commit/648b5425c80e6301d... > - https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782... > - https://github.com/jbosstools/jbosstools-server//commit/7d6b1b7e31194bf49... > - https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-672) JBTIS Stable EA site broken due to composite site listing p2.index file as if it's a child folder, and missing org.kie.eclipse features

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-672?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-672. ----------------------------------- Verified with installing from RH Central and the update site in Eclipse Mars-2 with JBT 4.3.1.FInal > JBTIS Stable EA site broken due to composite site listing p2.index file as if it's a child folder, and missing org.kie.eclipse features > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-672 > URL: https://issues.jboss.org/browse/JBTIS-672 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Labels: early-access > Fix For: 4.3.0.Final > > Attachments: where-is-kie.png, where-is-kie_2.png > > > http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... is broken, since it lists the p2.index file as if it's a child folder. > So, Eclipse complains: > {code} > eclipse.buildId=4.5.2.M20160212-1500 > java.version=1.8.0_60 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/nboldt/eclipse/workspace-clean45-2 -consolelog -product org.eclipse.epp.package.jee.product -data file:/home/nboldt/eclipse/workspace-clean45-2/ -consolelog > org.eclipse.equinox.p2.metadata.repository > Error > Mon Apr 18 18:59:56 EDT 2016 > No repository found at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac.... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016