[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19045:
----------------------------------
Description:
We are going to update Tern to v0.7.0 for 4.2.x.
Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
p2diff output:
{code}
./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
< tern.eclipse.ide.tools.core [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
< tern.eclipse.ide.tools.ui [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
< tern-jsdt-feature.feature.jar [0.7.0.201412012159]
< tern.server.nodejs [0.7.0.201412012159]
< tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
< tern.core [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
< tern.eclipse.ide.core [0.7.0.201412012159]
< tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
< tern-feature.feature.group [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
< tern.eclipse.ide.ui [0.7.0.201412012159]
< tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
< tern-jsdt-feature.feature.group [0.7.0.201412012159]
< tern-feature.feature.jar [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
< tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
< tern.eclipse.ide.jsdt [0.7.0.201412012159]
< tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
< tern.eclipse [0.7.0.201412012159]
> tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> tern.eclipse.ide.core [0.6.0.201409231610]
> tern-feature.feature.jar [0.6.0.201409231610]
> tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> tern.server.nodejs [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> tern-feature.feature.group [0.6.0.201409231610]
> tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> tern-jsdt-feature.feature.group [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> tern.eclipse [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> tern.eclipse.ide.ui [0.6.0.201409231610]
> tern.core [0.6.0.201409231610]
> tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> tern.eclipse.ide.tools.core [0.6.0.201409231610]
> tern.eclipse.ide.jsdt [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
=== Summary ===
./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
{code}
was:
We are going to update Tern to v0.7.0 for 4.2.x.
Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
> -------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Final
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19056:
------------------------------------
Also getting lots of new built-time warnings. See https://github.com/jbosstools/jbosstools-build/pull/172/files#r23715475 for details.
Building Openshift:
{code}
[INFO] org.jboss.tools.openshift.egit.core ............... FAILURE [9.173s]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default)
on project org.jboss.tools.openshift.egit.core: Version of 'org.jboss.tools.openshift.egit.core/2.6.0.Alpha1-v20150128-1932) must be bigger
than baseline one (2.6.1.Final-v20141209-0337-B67) -> [Help 1]
{code}
Then after updating to latest in master ( https://github.com/jbosstools/jbosstools-openshift/commit/789667220e157a2... JBIDE-19076):
{code}
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [10.760s]
{code}
> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
> Key: JBIDE-19056
> URL: https://issues.jboss.org/browse/JBIDE-19056
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19056 at 1/28/15 2:30 PM:
-------------------------------------------------------------
Tested w/ older Forge in master:
{code}
cd jbosstools-forge; mvn clean install
[INFO] org.jboss.tools.aesh.runtime ...................... FAILURE [16.725s]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default)
on project org.jboss.tools.aesh.runtime: Version of 'org.jboss.tools.aesh.runtime/1.3.53.Alpha1-v20150128-1904)
must be bigger than baseline one (1.3.53.Final-v20150113-1315-B85) -> [Help 1]
{code}
Then run again after updating to latest in master:
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default)
on project org.jboss.tools.aesh.runtime:
Unless artifacts are identical, version of 'org.jboss.tools.aesh.runtime' must have
bigger x.y.z than what's available in baseline
(2.0.0.Alpha1-v20150128-1908) -> [Help 1]
{code}
So.. Forge is still broken, despite JBIDE-19077 being now resolved, with these changes: https://github.com/jbosstools/jbosstools-forge/commit/d671d50805e18348658...
Is that a problem w/ the mojo or with Forge?
was (Author: nickboldt):
Tested w/ older Forge in master:
{code}
cd jbosstools-forge; mvn clean install
[INFO] org.jboss.tools.aesh.runtime ...................... FAILURE [16.725s]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.aesh.runtime: Version of 'org.jboss.tools.aesh.runtime/1.3.53.Alpha1-v20150128-1904) must be bigger than baseline one (1.3.53.Final-v20150113-1315-B85) -> [Help 1]
{code}
Then run again after updating to latest in master:
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.aesh.runtime: Unless artifacts are identical, version of 'org.jboss.tools.aesh.runtime' must have bigger x.y.z than what's available in baseline (2.0.0.Alpha1-v20150128-1908) -> [Help 1]
{code}
So.. Forge is still broken, despite JBIDE-19077 being now resolved, with these changes: https://github.com/jbosstools/jbosstools-forge/commit/d671d50805e18348658...
Is that a problem w/ the mojo or with Forge?
> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
> Key: JBIDE-19056
> URL: https://issues.jboss.org/browse/JBIDE-19056
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19056:
------------------------------------
Tested w/ older Forge in master:
{code}
cd jbosstools-forge; mvn clean install
[INFO] org.jboss.tools.aesh.runtime ...................... FAILURE [16.725s]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.aesh.runtime: Version of 'org.jboss.tools.aesh.runtime/1.3.53.Alpha1-v20150128-1904) must be bigger than baseline one (1.3.53.Final-v20150113-1315-B85) -> [Help 1]
{code}
Then run again after updating to latest in master:
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.aesh.runtime: Unless artifacts are identical, version of 'org.jboss.tools.aesh.runtime' must have bigger x.y.z than what's available in baseline (2.0.0.Alpha1-v20150128-1908) -> [Help 1]
{code}
So.. Forge is still broken, despite JBIDE-19077 being now resolved, with these changes: https://github.com/jbosstools/jbosstools-forge/commit/d671d50805e18348658...
Is that a problem w/ the mojo or with Forge?
> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
> Key: JBIDE-19056
> URL: https://issues.jboss.org/browse/JBIDE-19056
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months