May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14643) Usage needs to bump versions for each release currently

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-14643: ---------------------------------------- Summary: Usage needs to bump versions for each release currently Key: JBIDE-14643 URL: https://issues.jboss.org/browse/JBIDE-14643 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Reporter: Andre Dietisheim Assignee: Max Rydahl Andersen Fix For: 4.1.0.Beta1, 4.1.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14642: ------------------------------------ [~dgolovin] This issue could use some descriptive text and some suggestions for what is needed, what the issue is, and what might be done. > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13655) Usage needs to bump versions for each release currently - how to fix or automate ?

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13655?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13655: ------------------------------------- Fix Version/s: (was: 4.1.0.Beta2) > Usage needs to bump versions for each release currently - how to fix or automate ? > ---------------------------------------------------------------------------------- > > Key: JBIDE-13655 > URL: https://issues.jboss.org/browse/JBIDE-13655 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: respin-a > Fix For: 4.1.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13267) should have select/deselect all buttons in runtime detection dialog

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13267?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-13267. ----------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Beta2) Resolution: Duplicate Issue A duplicate of JBIDE-13518. > should have select/deselect all buttons in runtime detection dialog > ------------------------------------------------------------------- > > Key: JBIDE-13267 > URL: https://issues.jboss.org/browse/JBIDE-13267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > when pointing to a runtimes directory with many (>5) runtimes its annoying having to manually unselect everything when I just want a few few -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-89: --------------------------------- Hey Rob - One last favor - could you cut/paste in the xml fragment from the content.xml containing the jboss.org reference? Thanks! --paull > target platform repo should not contain repository references > ------------------------------------------------------------- > > Key: JBTIS-89 > URL: https://issues.jboss.org/browse/JBTIS-89 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Paul Leacu > Priority: Critical > > I don't see how this repo could be used in a jbds setting when it contains repository references to jbt repositories. My understanding was that this repo only contained the extra dependencies for jbt-is. By including these references, if this repo is used in jbds, all those linked repos will be available too, polluting the pool of available features/bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-88) Mirror EMF Compare 2.1 and Graphiti 0.10 on jboss.org requirements

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-88?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-88. ----------------------------- Resolution: Done > Mirror EMF Compare 2.1 and Graphiti 0.10 on jboss.org requirements > ------------------------------------------------------------------ > > Key: JBTIS-88 > URL: https://issues.jboss.org/browse/JBTIS-88 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: releng > Reporter: Rob Cernich > Assignee: Paul Leacu > Fix For: 4.0.1 > > > Hey Nick, > Could you please ensure mirrors exist on jboss.org for Graphiti 0.10 and EMF Compare 2.1? > EMF Compare has a release candidate here: http://download.eclipse.org/modeling/emf/compare/updates/milestones/2.1/S... > Graphiti's release candidate is here: http://download.eclipse.org/graphiti/updates/milestones/S-0.10.0RC1-20130... > Thanks in advance. > Rob -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-88) Mirror EMF Compare 2.1 and Graphiti 0.10 on jboss.org requirements

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-88?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-88: --------------------------------- Rob's commit: https://github.com/jbosstools/jbosstools-integration-stack/commit/7200c2f... New TP: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Mirror EMF Compare 2.1 and Graphiti 0.10 on jboss.org requirements > ------------------------------------------------------------------ > > Key: JBTIS-88 > URL: https://issues.jboss.org/browse/JBTIS-88 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: releng > Reporter: Rob Cernich > Assignee: Paul Leacu > Fix For: 4.0.1 > > > Hey Nick, > Could you please ensure mirrors exist on jboss.org for Graphiti 0.10 and EMF Compare 2.1? > EMF Compare has a release candidate here: http://download.eclipse.org/modeling/emf/compare/updates/milestones/2.1/S... > Graphiti's release candidate is here: http://download.eclipse.org/graphiti/updates/milestones/S-0.10.0RC1-20130... > Thanks in advance. > Rob -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s... ] Rob Cernich commented on JBTIS-89: ---------------------------------- Hey Nick, I think that's what I'm talking about. I'm talking about the p2 repository created using the mirror tp mojo. That repo has all the "extra" dependencies required by IS, above and beyond the core platform. The problem is, that repo contains references to repositories on jboss.org. Here's how I discovered this. I upgraded SwitchYard to use updated dependencies of Graphiti and EMF compare. I then took an instance of JBDS, added update sites pointing to my local SwitchYard site and the p2 TP mirror created by integration-stack/target-platform. After installing SwitchYard, I had two additional update sites in JBDS pointing to jboss.org. I removed the repository references from the p2 TP mirror's content.xml, tried the install again, and all was good. Hope that helps explain the situation better. Rob > target platform repo should not contain repository references > ------------------------------------------------------------- > > Key: JBTIS-89 > URL: https://issues.jboss.org/browse/JBTIS-89 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Paul Leacu > Priority: Critical > > I don't see how this repo could be used in a jbds setting when it contains repository references to jbt repositories. My understanding was that this repo only contained the extra dependencies for jbt-is. By including these references, if this repo is used in jbds, all those linked repos will be available too, polluting the pool of available features/bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-89: --------------------------------- Might want to look at what we do in JBT / JBDS. JBT: aggregate site is built w/ <references> to upstream sites (previously multiple sites, now really just the TP site) in the site's metadata, so that the single zip (or site) can be used to resolve all the upstream. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... JBDS: aggregate site is built using the TP as a baseline (via reference in the pom [1]), but we don't refer to it in the completed update site; rather, we composite the TP into the site [2] end users search for updates. [1] https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml (see tpc.group and tpc.version) [2] https://devstudio.jboss.com/updates/7.0-development/compositeContent.xml > target platform repo should not contain repository references > ------------------------------------------------------------- > > Key: JBTIS-89 > URL: https://issues.jboss.org/browse/JBTIS-89 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Paul Leacu > Priority: Critical > > I don't see how this repo could be used in a jbds setting when it contains repository references to jbt repositories. My understanding was that this repo only contained the extra dependencies for jbt-is. By including these references, if this repo is used in jbds, all those linked repos will be available too, polluting the pool of available features/bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14114) Some eclipse bundles versions are higher in JBT 4.0 than in 4.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14114?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14114: ------------------------------------ Fixed upstream: https://bugs.eclipse.org/406224 - Should org.eclipse.equinox.preferences be version 3.5.100 in Kepler? YES. Ignored upstream: https://bugs.eclipse.org/406225 - Should org.eclipse.cvs be version 1.2.100 in Kepler? TBD. > Some eclipse bundles versions are higher in JBT 4.0 than in 4.1 > --------------------------------------------------------------- > > Key: JBIDE-14114 > URL: https://issues.jboss.org/browse/JBIDE-14114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, forge, upstream > Affects Versions: 4.1.0.Alpha1 > Environment: Windows > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Fix For: 4.1.0.Beta2 > > Attachments: JBDS Version Watch.html > > > Some eclipse bundles have versions higher in JBT 4.0 than in 4.1. > There is a list: > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... *Eclipse version bug: https://bugs.eclipse.org/406225 * > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... *Eclipse version bug: https://bugs.eclipse.org/406224 * > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 2.0.108 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 3.0.401 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 2.1.401 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 1.2.2 OK in Alpha2 (maybe should be changed 1.2.200 or 1.3.0?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 May 2013