September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-913) Cannot install RHDS-IS 10.0.0.Alpha1 from Central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-913?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-913: ----------------------------------------- Ok, this is probably a one time issue. Now, I was again able to install all features from Central > Cannot install RHDS-IS 10.0.0.Alpha1 from Central > ------------------------------------------------- > > Key: JBTIS-913 > URL: https://issues.jboss.org/browse/JBTIS-913 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > Priority: Critical > > The following error occurs when installing the Integration Stack from Central > {code} > An error occurred during the org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase. > session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust, operand=, action=). > Could not create profile data area /home/apodhrad/Projects/jbds-installer/rhds-10.0.0.GA/target/jbdevstudio/studio/p2/org.eclipse.equinox.p2.engine/profileRegistry/devstudio.profile/.datafor: devstudio > Could not create profile data area /home/apodhrad/Projects/jbds-installer/rhds-10.0.0.GA/target/jbdevstudio/studio/p2/org.eclipse.equinox.p2.engine/profileRegistry/devstudio.profile/.datafor: devstudio > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23203) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23203?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23203: ---------------------------------- Assignee: Jeff MAURY (was: Xavier Coulon) > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload] > -------------------------------------------------------------------- > > Key: JBIDE-23203 > URL: https://issues.jboss.org/browse/JBIDE-23203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [LiveReload]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-913) Cannot install RHDS-IS 10.0.0.Alpha1 from Central

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-913: --------------------------------------- Summary: Cannot install RHDS-IS 10.0.0.Alpha1 from Central Key: JBTIS-913 URL: https://issues.jboss.org/browse/JBTIS-913 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 10.0.0.Alpha1 Reporter: Andrej Podhradsky Priority: Critical The following error occurs when installing the Integration Stack from Central {code} An error occurred during the org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase. session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust, operand=, action=). Could not create profile data area /home/apodhrad/Projects/jbds-installer/rhds-10.0.0.GA/target/jbdevstudio/studio/p2/org.eclipse.equinox.p2.engine/profileRegistry/devstudio.profile/.datafor: devstudio Could not create profile data area /home/apodhrad/Projects/jbds-installer/rhds-10.0.0.GA/target/jbdevstudio/studio/p2/org.eclipse.equinox.p2.engine/profileRegistry/devstudio.profile/.datafor: devstudio {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23212: ---------------------------------------- @Jeff: can you please open a bug for that to Tycho directly and make me a CC ? > 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.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

1
0
0 / 0

[JBoss JIRA] (JBTIS-912) Some BPMN2 bundles have incorrect versions

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-912?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-912: ----------------------------------------- The first three are from a different project than the others. It's the model vs. the editor. So I'm not sure whether Bob has the ability to update that project or not. > Some BPMN2 bundles have incorrect versions > ------------------------------------------ > > Key: JBTIS-912 > URL: https://issues.jboss.org/browse/JBTIS-912 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > > Some BPMN2 bundles have incorrect versions (missing build number) > {code} > org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 > {code} > Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. > EDIT: Note that all BPMN2 bundles in JBDS-IS 9.0.2.CR1 have correct versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-912) Some BPMN2 bundles have incorrect versions

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-912?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-912: ------------------------------------ Description: Some BPMN2 bundles have incorrect versions (missing build number) {code} org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 {code} Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. EDIT: Note that all BPMN2 bundles in JBDS-IS 9.0.2.CR1 have correct versions. was: Some BPMN2 bundles have incorrect versions (missing build number) {code} org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 {code} Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. > Some BPMN2 bundles have incorrect versions > ------------------------------------------ > > Key: JBTIS-912 > URL: https://issues.jboss.org/browse/JBTIS-912 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > > Some BPMN2 bundles have incorrect versions (missing build number) > {code} > org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 > {code} > Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. > EDIT: Note that all BPMN2 bundles in JBDS-IS 9.0.2.CR1 have correct versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-912) Some BPMN2 bundles have incorrect versions

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-912: --------------------------------------- Summary: Some BPMN2 bundles have incorrect versions Key: JBTIS-912 URL: https://issues.jboss.org/browse/JBTIS-912 Project: JBoss Tools Integration Stack Issue Type: Bug Components: BPMN2 Affects Versions: 10.0.0.Alpha1 Reporter: Andrej Podhradsky Some BPMN2 bundles have incorrect versions (missing build number) {code} org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 {code} Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[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: ------------------------------- Summary: when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines (was: Baseline check does not seem to work with features) > 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.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23212: ------------------------------------ But you're right... the build fails with verify, and passes with install. {code} mvn clean verify ... [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.maven.feature: Duplicate version but different content found for (org.jboss.tools.maven.feature.source.feature.jar/1.8.1.v20160614-2136). Also exists in baseline, but its content is different. -> [Help 1] {code} > Baseline check does not seem to work with features > -------------------------------------------------- > > 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.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

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/22/16 9:48 AM: ------------------------------------------------------------- [~nickboldt] [~mickael_istria] verify is required for the baseline check to run was (Author: jeffmaury): [~nickboldt] [~mickael_istria]] verify is required for the baseline check to run > Baseline check does not seem to work with features > -------------------------------------------------- > > 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.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

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 September 2016