January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13333?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13333: --------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 > Fixing Eclipse/Kepler > --------------------- > > Key: JBIDE-13333 > URL: https://issues.jboss.org/browse/JBIDE-13333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: UpStream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > "container" issue for issues related to fixes important to get into Kepler. > Please link your Eclipse/Kepler issue to this one instead of using subtasks. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12993) Cleanup/create plain checkout.sh script for jbosstools repos from github

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12993?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12993: ------------------------------------ Is this still important for 4.1? > Cleanup/create plain checkout.sh script for jbosstools repos from github > ------------------------------------------------------------------------ > > Key: JBIDE-12993 > URL: https://issues.jboss.org/browse/JBIDE-12993 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha1 > > > nick have done some work on the checkout script at: https://github.com/jbosstools/jbosstools-build/blob/master/scripts/checko... but it is assuming a bit too much IMO, at least more than we can currently assume. > I suggest: > cleanup to checkout as if you just did clones (i.e. no removal of jbosstools- prefix) > allow to do it to a directory > don't setup branches (not something that you necessarily want to do on all repos and can be done better by custom/specific scripting) > fix bootstrap profiles to use full names not the names done in this script. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11098) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11098?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11098: ------------------------------- Assignee: Rob Cernich (was: Douglas Palmer) > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBIDE-11098 > URL: https://issues.jboss.org/browse/JBIDE-11098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools, esb, jbpm, runtime-detection, SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Rob Cernich > Fix For: 4.0.x > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11098) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11098?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11098: ------------------------------- Fix Version/s: 4.0.0.Alpha1-SOA (was: 4.0.x) > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBIDE-11098 > URL: https://issues.jboss.org/browse/JBIDE-11098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools, esb, jbpm, runtime-detection, SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Rob Cernich > Fix For: 4.0.0.Alpha1-SOA > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11098) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11098?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11098: ------------------------------------ Assign to [~rcernich] -- I'm sure you already have a tracker JIRA for this, so feel free to close this when the drools, jbpm, and esb detectors are migrated into their respective projects. > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBIDE-11098 > URL: https://issues.jboss.org/browse/JBIDE-11098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools, esb, jbpm, runtime-detection, SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Rob Cernich > Fix For: 4.0.0.Alpha1-SOA > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13329: ------------------------------------ +1 to using them. They build fine via this matrix job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13232: ------------------------------------ Even better... 6 target platforms (eventually 8 when we add a 4.3.0.max one), 1 job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... > refactor target platforms' GAVs, names, labels (was target platforms has the same name) > --------------------------------------------------------------------------------------- > > Key: JBIDE-13232 > URL: https://issues.jboss.org/browse/JBIDE-13232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Environment: > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either. > Makes it hard to actually see which target platform to choose -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2038) JBDS installer should open JBDS upon completion

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ] Daniel Azarov updated JBDS-2038: -------------------------------- Attachment: RunJBDSAfterInstallation.png > JBDS installer should open JBDS upon completion > ----------------------------------------------- > > Key: JBDS-2038 > URL: https://issues.jboss.org/browse/JBDS-2038 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 5.0.0.Beta1 > Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar > Reporter: Fred Bricon > Assignee: Daniel Azarov > Fix For: 7.0.x > > Attachments: RunJBDSAfterInstallation.png > > > As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS. > On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13392) openshift tools should be version 2.3.2, not 2.3.1 in 3.3.x branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13392?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13392: ------------------------------------ Version bump verified. Just need to push bits to stable site to make this job turn 100% blue: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... > openshift tools should be version 2.3.2, not 2.3.1 in 3.3.x branch > ------------------------------------------------------------------ > > Key: JBIDE-13392 > URL: https://issues.jboss.org/browse/JBIDE-13392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 3.3.2 > > Attachments: JBIDE13392-upversion-only.patch.txt > > > JBT 3.3.x Indigo target platform includes egit 1.2. > org.jboss.tools.openshift.express.ui depends on org.eclipse.egit.ui;bundle-version="1.0.0", which means anyone with egit 2.x already installed won't be able to install the OpenShift tools: > {code} > Cannot complete the install because of a conflicting dependency. Software being installed: > JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) > Software currently installed: > Eclipse EGit 2.2.0.201212191850-r (org.eclipse.egit.feature.group 2.2.0.201212191850-r) > Only one of the following can be installed at once: > Git Team Provider UI 2.2.0.201212191850-r (org.eclipse.egit.ui 2.2.0.201212191850-r) > Git Team Provider UI 1.2.0.201112121913 (org.eclipse.egit.ui 1.2.0.201112121913) > Because: > org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final requires org.eclipse.egit.ui [1.0.0,2.0.0) > {code} > Can openshift tools run w/ egit 2.x? Can we simply extend the version compliance ranges in the plugins to allow [1.0.0,3.0.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13397) remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13397?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13397. -------------------------------- Resolution: Done Builds are blue in nightly 3.3.x aggregate build's tests. Need to re-run https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... after we publish to stable site to see entire job go blue. > remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files > ------------------------------------------------------------------------------------- > > Key: JBIDE-13397 > URL: https://issues.jboss.org/browse/JBIDE-13397 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Marketplace, maven > Affects Versions: 3.3.2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > Attachments: JBIDE13397.patch.bundle-version-to-1.0.0.txt > > > Looks like we need another fix here to make installation of org.jboss.tools.maven.* plugins possible when m2e > 1.1 is installed. -- 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, 5 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 January 2013