[JBoss JIRA] (JBIDE-23640) Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23640?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23640:
------------------------------------------
merged into jbosstools-integration-tests/master
QE verified the PR. Closing.
> Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23640
> URL: https://issues.jboss.org/browse/JBIDE-23640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.3.AM1
>
>
> PushImageTest is add a tag to an image. When looking at the images, it is comparing all of the decoration with the tag. This works fine as long as the image only has 1 tag, once it gets more, the lookup for the image starts to fail. The image is deleted later in the test, so if the image with the tag is not found, the delete wont happen and subsequent lookups will fail. This most likely wont happen if you run the complete suite because the suite is cleaning up, but it will happen if you run a single test.
> Another problem is that PushImageTest wont wait until the freshly tagged image was successfully pushed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23642) [baseline compare check] plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23642?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23642:
-------------------------------
Summary: [baseline compare check] plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site (was: plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site)
> [baseline compare check] plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23642
> URL: https://issues.jboss.org/browse/JBIDE-23642
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Building jbosstools-server from master branch, after releasing JBoss Tools 4.4.2.Final to the stable site [1] on Dec 8 last week:
> {code}
> mvn clean install -DskipTests -DskipBaselineComparison=false{code}
> {code}
> [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.ide.eclipse.archives.ui: Duplicate version but different content found for (org.jboss.ide.eclipse.archives.ui/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.archives.scanner.feature: Duplicate version but different content found for (org.jboss.tools.archives.scanner.feature.feature.jar/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.classpath.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.classpath.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.doc.user: Duplicate version but different content found for (org.jboss.ide.eclipse.as.doc.user/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.ui.mbeans: Duplicate version but different content found for (org.jboss.ide.eclipse.as.ui.mbeans/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.rse.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.rse.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.management.as7: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.as7/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.management.eap61plus: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.eap61plus/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.ide.eclipse.as.management.wildfly9: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.wildfly9/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.as.catalog: Duplicate version but different content found for (org.jboss.tools.as.catalog/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.jmx.local: Duplicate version but different content found for (org.jboss.tools.jmx.local/1.8.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.wtp.runtimes.tomcat: Duplicate version but different content found for (org.jboss.tools.wtp.runtimes.tomcat/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [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.wtp.server.launchbar.feature: Duplicate version but different content found for (org.jboss.tools.wtp.server.launchbar.feature.source.feature.jar/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> {code}
> [1] <lastStableRepository>http://download.jboss.org/jbosstools/neon/stable/updates/</lastStableRepository> - https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky edited comment on JBTIS-1003 at 12/13/16 9:58 AM:
--------------------------------------------------------------------
Hi [~pleacu], please have a look at
https://github.com/apodhrad/jbosstools-integration-stack/commit/6917af59e...
Ideally, add id to all repositories such as for bpel, bpmn2, birt, etc. It would be perfect to have composite sites in all locations but not all have it, e.g.
http://download.jboss.org/jbosstools/updates/requirements/bpel/
and I'm not sure whether we can create such composite sites and whether we can use them in TP definition.
EDIT: Note that it doesn't matter which name you choose for the id but it should be stable. I mean we cannot use id 'jbt-bpel' for
http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.5.Finala/
and then in the future just use the same id for
http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.6.Finala/
was (Author: apodhrad):
Hi [~pleacu], please have a look at
https://github.com/apodhrad/jbosstools-integration-stack/commit/6917af59e...
Ideally, add id to all repositories such as for bpel, bpmn2, birt, etc. It would be perfect to have composite sites in all locations but not all have it, e.g.
http://download.jboss.org/jbosstools/updates/requirements/bpel/
and I'm not sure whether we can create such composite sites and whether we can use them in TP definition.
> Add id to all repositories defined in target platform
> -----------------------------------------------------
>
> Key: JBTIS-1003
> URL: https://issues.jboss.org/browse/JBTIS-1003
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.0.CR1-TP
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Currently, the definition looks as follows
> {code:title=src/targets/integration-stack-base.target}
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> ...
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/>
> </location>
> {code}
> Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g.
> {code}
> http://download.jboss.org/jbosstools/updates/requirements/neon/
> {code}
> I think that the composite site should work without any problem since all needed versions are specified in each unit.
> Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1003:
------------------------------------------
Hi [~pleacu], please have a look at
https://github.com/apodhrad/jbosstools-integration-stack/commit/6917af59e...
Ideally, add id to all repositories such as for bpel, bpmn2, birt, etc. It would be perfect to have composite sites in all locations but not all have it, e.g.
http://download.jboss.org/jbosstools/updates/requirements/bpel/
and I'm not sure whether we can create such composite sites and whether we can use them in TP definition.
> Add id to all repositories defined in target platform
> -----------------------------------------------------
>
> Key: JBTIS-1003
> URL: https://issues.jboss.org/browse/JBTIS-1003
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.0.CR1-TP
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Currently, the definition looks as follows
> {code:title=src/targets/integration-stack-base.target}
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> ...
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/>
> </location>
> {code}
> Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g.
> {code}
> http://download.jboss.org/jbosstools/updates/requirements/neon/
> {code}
> I think that the composite site should work without any problem since all needed versions are specified in each unit.
> Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
by fede pia (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ]
fede pia commented on JBIDE-23641:
----------------------------------
[~jeffmaury], I can reproduce this issue with the newest version of STS, right now it is STS 3.8.2.RELEASE. The Mac OS Sierra version I have is 10.12.1. It is important to mention that only the option JBoss Web and Java EE Development -> JBoss AS Tools has to be checked.
When I open the STS I have a maven project connected to the SVN (with subclipse plugin) and also I have Jira Mylyn pluging installed (http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.7), and the project gets frozen in the building workspace status. This only happens when I install the JBoss AS Tools, since if I start STS with no plugins and uninstall Jboss then STS works well again.
> Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
> ----------------------------------------------------
>
> Key: JBIDE-23641
> URL: https://issues.jboss.org/browse/JBIDE-23641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM1
>
> Attachments: eclipse.log
>
>
> When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBTIS-1004) Integration Stack Installation Guide peer review
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1004?page=com.atlassian.jira.plugin... ]
Nick Boldt updated JBTIS-1004:
------------------------------
Project: JBoss Tools Integration Stack (was: Red Hat JBoss Developer Studio (devstudio))
Key: JBTIS-1004 (was: JBDS-4220)
Docs QE Status: (was: NEW)
Component/s: distribution
testing
(was: documentation)
(was: integration-platform)
Writer: (was: Misha Ali)
> Integration Stack Installation Guide peer review
> ------------------------------------------------
>
> Key: JBTIS-1004
> URL: https://issues.jboss.org/browse/JBTIS-1004
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, testing
> Reporter: Gemma Sheldon
> Priority: Minor
> Fix For: 10.0.0.GA
>
>
> General peer review stuff from the JBDIS Installation Guide.
> *Chapter 2:*
> - Oxford comma after "architecture" in the first para.
> *Chapter 4:*
> - "At the Select Additional Features to Install screen, select the required components: "
> This could be "Select the required components from the Select Additional Features to Install screen"?
> - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. "
> When complete? Once installed?
> - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. "
> Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe:
> The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect.
> *Chapter 6*
> - The sub-steps here could use a full stop based on the IBM style guide pp84-85.
> - Same Warning as in previous chapter
> *Chapter 7*
> - Same point about the sub-steps and full stops. Some have them here, some don't.
> - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal"
> *Chapter 8*
> - Several steps throughout the procedure are missing full stops at the end.
> - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step.
> - Same as above with Step 6, which is also missing the opening bracket.
> - Same Warning as in Chapters 5 and 6.
> - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects."
> This statement also appears in Chapter 6.
> *Chapter 9*
> - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint."
> 2x continued here. Could be "... provides continued stability and ensures optimal performance..."
> - " in an efficient manner" --> efficiently.
> - full stops at the end of the bullet points.
> - substeps of step 4 are missing full stops.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBTIS-1004) Integration Stack Installation Guide peer review
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1004?page=com.atlassian.jira.plugin... ]
Nick Boldt updated JBTIS-1004:
------------------------------
Fix Version/s: 10.0.0.GA
> Integration Stack Installation Guide peer review
> ------------------------------------------------
>
> Key: JBTIS-1004
> URL: https://issues.jboss.org/browse/JBTIS-1004
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, testing
> Reporter: Gemma Sheldon
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 10.0.0.GA
>
>
> General peer review stuff from the JBDIS Installation Guide.
> *Chapter 2:*
> - Oxford comma after "architecture" in the first para.
> *Chapter 4:*
> - "At the Select Additional Features to Install screen, select the required components: "
> This could be "Select the required components from the Select Additional Features to Install screen"?
> - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. "
> When complete? Once installed?
> - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. "
> Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe:
> The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect.
> *Chapter 6*
> - The sub-steps here could use a full stop based on the IBM style guide pp84-85.
> - Same Warning as in previous chapter
> *Chapter 7*
> - Same point about the sub-steps and full stops. Some have them here, some don't.
> - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal"
> *Chapter 8*
> - Several steps throughout the procedure are missing full stops at the end.
> - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step.
> - Same as above with Step 6, which is also missing the opening bracket.
> - Same Warning as in Chapters 5 and 6.
> - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects."
> This statement also appears in Chapter 6.
> *Chapter 9*
> - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint."
> 2x continued here. Could be "... provides continued stability and ensures optimal performance..."
> - " in an efficient manner" --> efficiently.
> - full stops at the end of the bullet points.
> - substeps of step 4 are missing full stops.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBTIS-1004) Integration Stack Installation Guide peer review
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1004?page=com.atlassian.jira.plugin... ]
Nick Boldt reassigned JBTIS-1004:
---------------------------------
Assignee: Paul Leacu
> Integration Stack Installation Guide peer review
> ------------------------------------------------
>
> Key: JBTIS-1004
> URL: https://issues.jboss.org/browse/JBTIS-1004
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, testing
> Reporter: Gemma Sheldon
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 10.0.0.GA
>
>
> General peer review stuff from the JBDIS Installation Guide.
> *Chapter 2:*
> - Oxford comma after "architecture" in the first para.
> *Chapter 4:*
> - "At the Select Additional Features to Install screen, select the required components: "
> This could be "Select the required components from the Select Additional Features to Install screen"?
> - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. "
> When complete? Once installed?
> - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. "
> Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe:
> The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect.
> *Chapter 6*
> - The sub-steps here could use a full stop based on the IBM style guide pp84-85.
> - Same Warning as in previous chapter
> *Chapter 7*
> - Same point about the sub-steps and full stops. Some have them here, some don't.
> - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal"
> *Chapter 8*
> - Several steps throughout the procedure are missing full stops at the end.
> - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step.
> - Same as above with Step 6, which is also missing the opening bracket.
> - Same Warning as in Chapters 5 and 6.
> - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects."
> This statement also appears in Chapter 6.
> *Chapter 9*
> - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint."
> 2x continued here. Could be "... provides continued stability and ensures optimal performance..."
> - " in an efficient manner" --> efficiently.
> - full stops at the end of the bullet points.
> - substeps of step 4 are missing full stops.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months