July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22673: ---------------------------------------- I had a look and it seems like P2Resolver#resolve(....) doesn't fail in case of multiple versions of a singleton. We should find a way to turn this resolution result into a Provisioning action, that would then most likely fail. > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Fix For: 4.4.1.AM1 > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22689) enable baselineRepositories check to ensure timestamps increment for meta-changes too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22689?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22689: ------------------------------------ Buildflow job to verify nothing is broken: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... Should see ": FAILURE" if any jobs break. > enable baselineRepositories check to ensure timestamps increment for meta-changes too > ------------------------------------------------------------------------------------- > > Key: JBIDE-22689 > URL: https://issues.jboss.org/browse/JBIDE-22689 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM2 > > > To make sure to report a problem if we need to upversion for a meta-change (eg., build configuration) and there's no accompanying new commit to force the timestamp to increment: > From https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers > {code:xml} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > <version>${tycho.version}</version> > <configuration> > <baselineRepositories> > <repository> > <url>[some url]</url> > </repository> > </baselineRepositories> > </configuration> > </plugin> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3962) Blog post about DevSuite installer on developers.redhat.com

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3962: ----------------------------------- Summary: Blog post about DevSuite installer on developers.redhat.com Key: JBDS-3962 URL: https://issues.jboss.org/browse/JBDS-3962 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.0.1.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.0.1.AM2 We should draw more attention to DevSuite Installer and put more content about it on http://developers.redhat.com/blog/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22673: ---------------------------------------- I thought the TP resolution would fail when trying to resolve 2 different singletons. Maybe there's a flag for that to enable in the target-platform-validation-mojo > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Fix For: 4.4.1.AM1 > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-798) Remove JBDS-IS from ide-config for Devstudio 10

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-798?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-798. ------------------------------ Fix Version/s: 10.0.0.Alpha1 Resolution: Done [~nickboldt] [~apodhrad] Hey - I've commented out the IS from devstudiio 10.0.0.GA discovery. The 10.0.0.Alpha1-SNAPSHOT version has not yet been vetted and is missing SwitchYard. I'll try out the latest core TP from Nick: https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... ref https://issues.jboss.org/browse/JBIDE-22633 If I can build SY and Teiid Des I'll respin 10.0.0.Alpha1 TP and IS for QE to chew on. Until then IS tooling is disabled. > Remove JBDS-IS from ide-config for Devstudio 10 > ----------------------------------------------- > > Key: JBTIS-798 > URL: https://issues.jboss.org/browse/JBTIS-798 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > The file at > http://download.jboss.org/jbosstools/configuration/ide-config.properties > specifies url to JBDS-IS 9 for Devstudio 10. > This is wrong since there is no release of JBDS-IS / Devstudio IS for Devstudio 10. > Note that SwitchYard is not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22633) jbosstools-multiple.target has multiple incompatible IUs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22633?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22633: ---------------------------------------- Does the TP validation pass even with 2 versions of a singleton bundle? > jbosstools-multiple.target has multiple incompatible IUs > -------------------------------------------------------- > > Key: JBIDE-22633 > URL: https://issues.jboss.org/browse/JBIDE-22633 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Reporter: Paul Leacu > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM1 > > > Please correct the jbosstools-multiple.target to avoid the duplication of the IU as this is causing build failures in both SwitchYard and Fuse Tooling (development). > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > org.eclipse.egit.ui.smartimport is defined twice with two different versions: > {code} > [ERROR] Resolution failed: > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22689) enable baselineRepositories check to ensure timestamps increment for meta-changes too

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22689?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22689: ---------------------------------------- Both aren't checking the same thing, so it makes sense to have different properties. Also, the tycho.baseline can have 4 different values, whereas the skip one is a boolean. The first one verifies that we do not create some artifact with same fully-qualified versions and different content compared to last build, whereas the later one checks that we didn't forget to bump versions compared to previous release. > enable baselineRepositories check to ensure timestamps increment for meta-changes too > ------------------------------------------------------------------------------------- > > Key: JBIDE-22689 > URL: https://issues.jboss.org/browse/JBIDE-22689 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM2 > > > To make sure to report a problem if we need to upversion for a meta-change (eg., build configuration) and there's no accompanying new commit to force the timestamp to increment: > From https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers > {code:xml} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > <version>${tycho.version}</version> > <configuration> > <baselineRepositories> > <repository> > <url>[some url]</url> > </repository> > </baselineRepositories> > </configuration> > </plugin> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22689) enable baselineRepositories check to ensure timestamps increment for meta-changes too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22689?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22689: ------------------------------------ I've added some inline doc (read: comments) into the parent pom to state more clearly that for THIS check, we can use *-Dtycho.baseline=disable*... unlike the other baseline check, which uses *-DskipBaselineComparison=true*. Because consistency. :( > enable baselineRepositories check to ensure timestamps increment for meta-changes too > ------------------------------------------------------------------------------------- > > Key: JBIDE-22689 > URL: https://issues.jboss.org/browse/JBIDE-22689 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM2 > > > To make sure to report a problem if we need to upversion for a meta-change (eg., build configuration) and there's no accompanying new commit to force the timestamp to increment: > From https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers > {code:xml} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > <version>${tycho.version}</version> > <configuration> > <baselineRepositories> > <repository> > <url>[some url]</url> > </repository> > </baselineRepositories> > </configuration> > </plugin> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3883) "Download & install" button is enabled during detection after going back and forth again

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3883?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3883: -------------------------------- Sprint: (was: devex #116 June 2016) > "Download & install" button is enabled during detection after going back and forth again > ---------------------------------------------------------------------------------------- > > Key: JBDS-3883 > URL: https://issues.jboss.org/browse/JBDS-3883 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.1.AM2 > > > Normally, the user cannot proceed with the installation on the confirm page until component detection has finished. If after that they click back and continue again, the detection is launched again, but it allows the user to continue anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Sprint: (was: devex #116 June 2016) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.1.AM2 > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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