February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13669) add refactored m2e-wtp features to maven project examples feature as dependencies so they'll be installed OOTB

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13669?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13669: ------------------------------------ To verify, check latest nightly core trunk or 4.1.kepler site, install the whole AbridgedTools category, and see if org.eclipse.m2e.wtp.jsf.feature, org.eclipse.m2e.wtp.jaxrs.feature, org.eclipse.m2e.wtp.jpa.feature are installed. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ > add refactored m2e-wtp features to maven project examples feature as dependencies so they'll be installed OOTB > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13669 > URL: https://issues.jboss.org/browse/JBIDE-13669 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > > Must add these as requirements to org.jboss.tools.maven.project.examples.feature: > https://github.com/jbosstools/jbosstools-central/blob/master/maven/featur... > * org.eclipse.m2e.wtp.jsf.feature > * org.eclipse.m2e.wtp.jaxrs.feature > * org.eclipse.m2e.wtp.jpa.feature -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13672 at 2/28/13 1:45 AM: ------------------------------------------------------------- Need to update jobs in 40x, 41x, and master to optionally pass through skipRevisionCheckWhenPublishing=true flag to the script. was (Author: nickboldt): Need to update jobs in 40x, 41x, and master to optionall pass through skipRevisionCheckWhenPublishing=true flag to the script. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13672 at 2/28/13 1:46 AM: ------------------------------------------------------------- Need to update jobs in 40x, 41x, and master to optionally pass through skipRevisionCheckWhenPublishing=true flag to the script. Need to also verify this works when there's no pre-existing build folder. was (Author: nickboldt): Need to update jobs in 40x, 41x, and master to optionally pass through skipRevisionCheckWhenPublishing=true flag to the script. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13682 at 2/28/13 1:42 AM: ------------------------------------------------------------- Possible versions to investigate - both can be installed into Eclipse Kepler M5 JEE bundle eclipse-jee-kepler-M5-linux-gtk-x86_64.tar.gz: * 3.0.7.v20121218 from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 * 3.0.7.I20130224-0900 (or newer) from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8 was (Author: nickboldt): Possible versions to investigate: * 3.0.7.v20121218 from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 or * 3.0.7.I20130224-0900 (or newer) from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8 > Investigate use of Atlassian 3.0.7 in JBoss Central > --------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha1 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13670) Can't install some Atlassian connector from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13670?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13670 at 2/28/13 1:38 AM: ------------------------------------------------------------- Complication. There are 2 connectors in Central which depend on Altassian: {code:title=Mylyn Issue Tracker Connectors} <iu id="org.jboss.tools.common.mylyn.feature"/> <iu id="com.atlassian.connector.eclipse.jira"/> <iu id="com.atlassian.connector.eclipse.monitor"/> <iu id="org.eclipse.mylyn_feature"/> <iu id="org.eclipse.mylyn.ide_feature"/> <iu id="org.eclipse.mylyn.commons"/> <iu id="org.eclipse.mylyn.context_feature"/> <iu id="org.eclipse.mylyn.bugzilla_feature"/> <iu id="org.eclipse.mylyn.java_feature"/> <iu id="org.eclipse.mylyn.pde_feature"/> <iu id="org.eclipse.mylyn.team_feature"/> <iu id="org.eclipse.mylyn.versions"/> {code} {code:title=Atlassian Connector for Eclipse} <iu id="com.atlassian.connector.eclipse"/> {code} Note too that com.atlassian.connector.eclipse depends on com.atlassian.connector.eclipse.jira which depends on com.atlassian.connector.eclipse.monitor. So while I can remove the *Atlassian Connector for Eclipse* easily, I'm not sure that disabling PART of the *Mylyn Issue Tracker Connectors* feature group is a good idea. Will need to do some tests. Would prefer to have QE have a look at the latest Atlassian *3.0.7.v20121218* from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 or *3.0.7.I20130224-0900* from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8, and include that in the Central site instead of the 3.0.6 version that depends on the now-non-existant *org.eclipse.update.ui* plugin. was (Author: nickboldt): Complication. There are 2 connectors in Central which depend on Altassian: {code:title=Mylyn Issue Tracker Connectors} <iu id="org.jboss.tools.common.mylyn.feature"/> <iu id="com.atlassian.connector.eclipse.jira"/> <iu id="com.atlassian.connector.eclipse.monitor"/> <iu id="org.eclipse.mylyn_feature"/> <iu id="org.eclipse.mylyn.ide_feature"/> <iu id="org.eclipse.mylyn.commons"/> <iu id="org.eclipse.mylyn.context_feature"/> <iu id="org.eclipse.mylyn.bugzilla_feature"/> <iu id="org.eclipse.mylyn.java_feature"/> <iu id="org.eclipse.mylyn.pde_feature"/> <iu id="org.eclipse.mylyn.team_feature"/> <iu id="org.eclipse.mylyn.versions"/> {code} {code:title=Atlassian Connector for Eclipse} <iu id="com.atlassian.connector.eclipse"/> {code} So while I can remove the *Atlassian Connector for Eclipse* easily, I'm not sure that disabling PART of the *Mylyn Issue Tracker Connectors* feature group is a good idea. Will need to do some tests. Would prefer to have QE have a look at the latest Atlassian *3.0.7.v20121218* from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 or *3.0.7.I20130224-0900* from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8, and include that in the Central site instead of the 3.0.6 version that depends on the now-non-existant *org.eclipse.update.ui* plugin. > Can't install some Atlassian connector from Central > --------------------------------------------------- > > Key: JBIDE-13670 > URL: https://issues.jboss.org/browse/JBIDE-13670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Can't install Atlassian from Central > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * Contains: Missing requirement: Atlassian Connector for Eclipse Usage Monitoring 3.0.6.v20120628 (com.atlassian.connector.eclipse.monitor.feature.group 3.0.6.v20120628) requires 'org.eclipse.update.ui 0.0.0' but it could not be found > 2 solutions possible, by order of preference: > # Use a more recent version of Atlassian connectors compliant with Kepler > # Remove Atlassian stuff from Central until we have a good version -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13682: ------------------------------------ Possible versions to investigate: * 3.0.7.v20121218 from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 or * 3.0.7.I20130224-0900 (or newer) from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8 > Investigate use of Atlassian 3.0.7 in JBoss Central > --------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha1 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 in JBoss Central

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13682: ---------------------------------- Summary: Investigate use of Atlassian 3.0.7 in JBoss Central Key: JBIDE-13682 URL: https://issues.jboss.org/browse/JBIDE-13682 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13670) Can't install some Atlassian connector from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13670?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13670: ------------------------------------ Complication. There are 2 connectors in Central which depend on Altassian: {code:title=Mylyn Issue Tracker Connectors} <iu id="org.jboss.tools.common.mylyn.feature"/> <iu id="com.atlassian.connector.eclipse.jira"/> <iu id="com.atlassian.connector.eclipse.monitor"/> <iu id="org.eclipse.mylyn_feature"/> <iu id="org.eclipse.mylyn.ide_feature"/> <iu id="org.eclipse.mylyn.commons"/> <iu id="org.eclipse.mylyn.context_feature"/> <iu id="org.eclipse.mylyn.bugzilla_feature"/> <iu id="org.eclipse.mylyn.java_feature"/> <iu id="org.eclipse.mylyn.pde_feature"/> <iu id="org.eclipse.mylyn.team_feature"/> <iu id="org.eclipse.mylyn.versions"/> {code} {code:title=Atlassian Connector for Eclipse} <iu id="com.atlassian.connector.eclipse"/> {code} So while I can remove the *Atlassian Connector for Eclipse* easily, I'm not sure that disabling PART of the *Mylyn Issue Tracker Connectors* feature group is a good idea. Will need to do some tests. Would prefer to have QE have a look at the latest Atlassian *3.0.7.v20121218* from http://update.atlassian.com/atlassian-eclipse-plugin/e3.8 or *3.0.7.I20130224-0900* from http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.8, and include that in the Central site instead of the 3.0.6 version that depends on the now-non-existant *org.eclipse.update.ui* plugin. > Can't install some Atlassian connector from Central > --------------------------------------------------- > > Key: JBIDE-13670 > URL: https://issues.jboss.org/browse/JBIDE-13670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Can't install Atlassian from Central > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * Contains: Missing requirement: Atlassian Connector for Eclipse Usage Monitoring 3.0.6.v20120628 (com.atlassian.connector.eclipse.monitor.feature.group 3.0.6.v20120628) requires 'org.eclipse.update.ui 0.0.0' but it could not be found > 2 solutions possible, by order of preference: > # Use a more recent version of Atlassian connectors compliant with Kepler > # Remove Atlassian stuff from Central until we have a good version -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13681) compile failed in org.jboss.tools.jst.web.ui

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13681: ---------------------------------- Summary: compile failed in org.jboss.tools.jst.web.ui Key: JBIDE-13681 URL: https://issues.jboss.org/browse/JBIDE-13681 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.1.0.Alpha2 Reporter: Nick Boldt Assignee: Alexey Kazakov {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-jst_master/309/console} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.jst.web.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-jst_master/sources/plugins/org.jboss.tools.jst.web.ui/src/org/jboss/tools/jst/web/ui/palette/html/jquery/wizard/JQueryFieldEditorFactory.java:[84,0] [ERROR] text.setMessage("Generate"); [ERROR] ^^^^^^^^^^ [ERROR] The method setMessage(String) is undefined for the type TextFieldEditor [ERROR] 1 problem (1 error) {code} -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13662) Unhandled event loop exception when closing Fileset dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13662?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13662: ------------------------------------- wow you guys are really finding every bug :D thats great! > Unhandled event loop exception when closing Fileset dialog > ---------------------------------------------------------- > > Key: JBIDE-13662 > URL: https://issues.jboss.org/browse/JBIDE-13662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > -- 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, 4 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 February 2013