[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23157:
----------------------------------------
I would prefer to rename common/jst/core to common and create a new for jst. It's not a big deal if all the old 807 issues will be in common. And I can take care of the unresolved one as soon as jst is created.
> rename component "common/jst/core" to "base" or "foundation" or add new components
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23157
> URL: https://issues.jboss.org/browse/JBIDE-23157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.4.2.AM2
>
>
> The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation".
> We should either fix that component, or add new one(s).
> This will impact *.py scripts in jbosstools-build-ci.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23212 at 9/26/16 1:43 PM:
-------------------------------------------------------------
Given the schedule of Tycho releases to date [1] (once every 4-5 months), I'd assume that we won't have 0.27 in time for devstudio 10.2 / jbt 4.4.2, as it's likely that 0.27 will arrive in mid December.
[1] https://wiki.eclipse.org/Tycho/Release_Notes
Therefore slipping this to 4.4.x / 4.5.0 (depends on when we move to Oxygen).
Fix should be available for the March 2017 release, whatever that becomes (4.4.3 / 10.3.0 or 4.5.0 / 11.0.0).
was (Author: nickboldt):
Given the schedule of Tycho releases to date, I'd assume that we won't have 0.27 in time for devstudio 10.2 / jbt 4.4.2, as it's likely that 0.27 will arrive in mid December.
Therefore slipping this to 4.4.x / 4.5.0 (depends on when we move to Oxygen).
Fix should be available for the March 2017 release, whatever that becomes (4.4.3 / 10.3.0 or 4.5.0 / 11.0.0).
> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho,
> Fix For: 4.4.x, 4.5.0.AM1
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23212:
------------------------------------
Given the schedule of Tycho releases to date, I'd assume that we won't have 0.27 in time for devstudio 10.2 / jbt 4.4.2, as it's likely that 0.27 will arrive in mid December.
Therefore slipping this to 4.4.x / 4.5.0 (depends on when we move to Oxygen).
Fix should be available for the March 2017 release, whatever that becomes (4.4.3 / 10.3.0 or 4.5.0 / 11.0.0).
> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho,
> Fix For: 4.4.x, 4.5.0.AM1
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23212:
-------------------------------
Fix Version/s: 4.4.x
4.5.0.AM1
(was: 4.4.2.AM2)
> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho,
> Fix For: 4.4.x, 4.5.0.AM1
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23212:
------------------------------------
Please note that provided patch has been merged in upstream master so this will be available to use with Tycho 0.27.0
> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho,
> Fix For: 4.4.2.AM2
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20904:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> automate publishing latest CI build to staging, then from staging to development (or stable)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20904
> URL: https://issues.jboss.org/browse/JBIDE-20904
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM2
>
>
> Suggestion:
> rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed.
> So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion.
> [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui...
> Examples of using a series of commands in parallel w/ a wait at the end:
> http://stackoverflow.com/questions/19543139/bash-script-processing-comman...
> {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code}
> echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $#
> {code}
> More discussion:
> {quote}
> [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions
> [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just:
> * add && after the 1st rsync in each loop
> * add & after the last one
> * put a wait after the last loop
> * give the big piece of code to procede directly to bash
> {quote}
> After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template.
> And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job.
> Scary, but much faster!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23212:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho,
> Fix For: 4.4.2.AM2
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4049:
----------------------------------
Blocked by JBIDE-22581
> Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4049
> URL: https://issues.jboss.org/browse/JBDS-4049
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream
> Affects Versions: 10.1.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
> Attachments: 4049-better-but-not-perfect.png, ds10.1_on_neon.1.RC3_remediation_needed.png
>
>
> Steps to repro:
> 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
> 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA
> 3. Remediation needed:
> {code}Cannot complete the install because of a conflicting dependency.
> Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> Only one of the following can be installed at once:
> JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403)
> JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529)
> JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059)
> JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930)
> JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700)
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725]
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725)
> To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059]
> {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23143:
-------------------------------
Fix Version/s: 4.4.2.AM2
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Fix For: 4.4.2.AM2
>
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months