June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10964) use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10964: ---------------------------------- Summary: use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red Key: JBIDE-10964 URL: https://issues.jboss.org/browse/JBIDE-10964 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 3.3.0.CR1 We'd like to see "unstable" (yellow) when tests fail, not "failed" (red). This will also mean checking for missing TEXT-*.xml files (recursing through ${WORKSPACE}/sources/tests/ looking for plugins' target/ folders to see that every test plugin has at least 1 TEST-*.xml file) and generating empty ones should there be an eclipse crash before a test results file can be generated. An empty file should at least alert developers that there's a possible problem w/ their test (or more likely, it's a slave / vnc issue, like JBIDE-10960). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
12
0 / 0

[JBoss JIRA] (JBIDE-11778) Hudson-sync-plugin fails silently

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11778: -------------------------------------- Summary: Hudson-sync-plugin fails silently Key: JBIDE-11778 URL: https://issues.jboss.org/browse/JBIDE-11778 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 3.3.0.CR1 When using hudson-sync-plugin to get the latest version of jbpm component: {code:xml} <plugin> <groupId>org.jboss.maven.plugin</groupId> <artifactId>hudson-job-sync-plugin</artifactId> <version>0.0.1-SNAPSHOT</version> <executions> <execution> <phase>install</phase> <goals> <goal>run</goal> </goals> </execution> </executions> <configuration>  <verbose>true</verbose>  <hudsonURL>https://hudson.qa.jboss.com/hudson/</hudsonURL> <username>admin</username> <password>#############</password>  <viewFilter>view/DevStudio/view/DevStudio_Trunk/</viewFilter> <regexFilter>jbosstools-3.3_trunk.component--jbpm</regexFilter>  <overwriteExistingConfigXMLFile>true</overwriteExistingConfigXMLFile> <operation>pull</operation> </configuration> {code} I get {code} [INFO] --- hudson-job-sync-plugin:0.0.1-SNAPSHOT:run (default) @ sync --- [INFO] Hudson URL: https://hudson.qa.jboss.com/hudson/ [INFO] Operation: pull [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS {code} However my config.xml is not updated (when existing), or not created in case it's not existing. Something is wrong with this component. SOA jobs often loose sync between cache and Hudson. It could because they belong to several views. This bug in hudson-sync-plugin is the cause of several weird cases in Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-11860) Remove deps on requirements/ folder on job where it's not useful

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11860: -------------------------------------- Summary: Remove deps on requirements/ folder on job where it's not useful Key: JBIDE-11860 URL: https://issues.jboss.org/browse/JBIDE-11860 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.0.CR1 In order to prevent change on requirements/ to trigger builds on jobs that do not use requirements/ folder, we should remove this SVN dependency on modules where it's not accurate. Affected module, no requirements.properties found (before JBIDE-11714) * archives * birt * bpel * common * deltacloud * drools * flow * freemarker * gwt * hibernatetools * jmx * jst * modeshape * openshift * struts * tests * usage * xulrunner -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-11589) Get rid of the Text Finder plugin in Jenkins

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11589: -------------------------------------- Summary: Get rid of the Text Finder plugin in Jenkins Key: JBIDE-11589 URL: https://issues.jboss.org/browse/JBIDE-11589 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria As we improved Jenkins to support UNSTABLE build directly for JUnit Report plugin, we should get rid of the Text Finder plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-11615) Move repositories reference for each module to settings.xml

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11615: -------------------------------------- Summary: Move repositories reference for each module to settings.xml Key: JBIDE-11615 URL: https://issues.jboss.org/browse/JBIDE-11615 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Priority: Minor Fix For: 3.3.0.Beta3 As described here https://community.jboss.org/wiki/MavenGettingStarted-Developers , we should remove respositories definition from modules root poms and encourage people to use settings.xml instead. We'll probably need to update CI jobs to have those respositories in their settings.xml, but I think it is already the case. We'll need to update that page consequently: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-10596) Use eclipse-repository packaging type for repository in order to materialize-products from them

by Mickael Istria (Created) (JIRA)

Use eclipse-repository packaging type for repository in order to materialize-products from them ----------------------------------------------------------------------------------------------- Key: JBIDE-10596 URL: https://issues.jboss.org/browse/JBIDE-10596 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Affects Versions: 3.3.0.M5 Environment: any Reporter: Mickael Istria Assignee: Nick Boldt The eclipse-repository packaging type is a better way to go: * It reads "category.xml" files (renamed site.xml files) * It supports the materialize-products action to extract the products from it See http://wiki.eclipse.org/Tycho/Packaging_Types#Creating_Product_Zip_Files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
14
0 / 0

[JBoss JIRA] (JBIDE-11370) Get all components to have tests, and get rid of the "in case there is not test" build steps

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11370: -------------------------------------- Summary: Get all components to have tests, and get rid of the "in case there is not test" build steps Key: JBIDE-11370 URL: https://issues.jboss.org/browse/JBIDE-11370 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.x Since tests are pretty easy to set up and run with Tycho, we should force all projects to have at least a dummy test. Hence we could remove in build jobs and scripts everything related to the "no test" case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-12125) Cannot invoke New Portlet wizard if no Dynamic Web Project is present

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12125: --------------------------------------- Summary: Cannot invoke New Portlet wizard if no Dynamic Web Project is present Key: JBIDE-12125 URL: https://issues.jboss.org/browse/JBIDE-12125 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.3.0.CR1 Reporter: Lucia Jelinkova Assignee: Snjezana Peco Priority: Critical Fix For: 3.3.1 Invoking new portlet wizard does not work when there are only non dynamic web projects in the workspace. The wizard is not shown and the following error is logged: {code} java.lang.NullPointerException at org.jboss.tools.portlet.ui.PortletUIActivator.getPortletXmlFile(PortletUIActivator.java:86) at org.jboss.tools.portlet.ui.internal.wizard.NewPortletClassDataModelProvider.validate(NewPortletClassDataModelProvider.java:353) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.validate(DataModelImpl.java:377) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.isValid(DataModelImpl.java:423) at org.eclipse.jst.servlet.ui.internal.wizard.NewWebArtifactWizard.canFinish(NewWebArtifactWizard.java:66) at org.eclipse.jface.wizard.WizardDialog.updateButtons(WizardDialog.java:1345) at org.eclipse.jface.wizard.WizardPage.setPageComplete(WizardPage.java:299) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizardPage.validatePage(DataModelWizardPage.java:342) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizardPage.enter(DataModelWizardPage.java:214) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizardPage.setVisible(DataModelWizardPage.java:312) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1260) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:257) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
8
0 / 0

[JBoss JIRA] (JBDS-2204) JBoss Maven GWT Connector brings in dozens of eclipse.org sites when resolving dependencies from JBDS Central

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2204: -------------------------------- Summary: JBoss Maven GWT Connector brings in dozens of eclipse.org sites when resolving dependencies from JBDS Central Key: JBDS-2204 URL: https://issues.jboss.org/browse/JBDS-2204 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central, maven Affects Versions: 5.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.GA Attachments: JBDS-cr1-only-two-sites-enabled.png, JBDS-cr1-tons-of-eclipse.org-sites-listed-several-enabled-02.png, JBDS-cr1-tons-of-eclipse.org-sites-listed-several-enabled.png Because we provide a connector for the JBoss Maven GWT Configurator from the http://download.jboss.org/jbosstools/updates/development/indigo/central/c... and not devstudio.jboss.com site... {code:title=https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plugins/com.jboss.jbds.central.discovery/plugin.xml} <connectorDescriptor categoryId="org.jboss.tools.central.discovery.maven" groupId="org.jboss.tools.central.discovery.maven.configurators" description="JBoss Maven GWT Configurator" id="org.jboss.tools.maven.gwt.feature" kind="task" license="Free, EPL" name="JBoss Maven GWT Configurator" provider="JBoss by Red Hat" siteUrl="http://download.jboss.org/jbosstools/updates/development/indigo/central/c..."> <iu id="org.jboss.tools.maven.gwt.feature"/> <iu id="com.google.gdt.eclipse.suite.e37.feature"/> <icon image32="images/jbosstools_icon32.png"> </icon> <overview url="http://www.jboss.org/tools"> </overview> </connectorDescriptor> {code} ... we end up providing metadata links to all the upstream eclipse.org sites that make up Indigo. Out of the box, this is what's available in JBDS for updates: !JBDS-cr1-only-two-sites-enabled.png! But if you select the JBoss Maven GWT Configurator connector, you get this: !JBDS-cr1-tons-of-eclipse.org-sites-listed-several-enabled.png! !JBDS-cr1-tons-of-eclipse.org-sites-listed-several-enabled-02.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
8
0 / 0

[JBoss JIRA] (JBIDE-11644) Fix detail description text format for JBT update site categories

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11644: ------------------------------------- Summary: Fix detail description text format for JBT update site categories Key: JBIDE-11644 URL: https://issues.jboss.org/browse/JBIDE-11644 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Denis Golovin Assignee: Nick Boldt Fix For: 3.3.0.Beta3 Attachments: DetailDescrAbridgedJBossTools3.3.png, DetailDescrJBossBusinessIntelligenceReportingAndCharting.png, DetailDescrJBossMavenSupport.png, DetailDescrJBossWebAndJavaEEDevCategory.png Affected categories are: # Abridged JBoss Tools 3.3 !DetailDescrAbridgedJBossTools3.3.png! # JBoss Business Intelligence, Reporting and Charting !DetailDescrJBossBusinessIntelligenceReportingAndCharting.png! # JBoss Maven Support !DetailDescrJBossMavenSupport.png! # JBoss Web and Java EE Development !DetailDescrJBossWebAndJavaEEDevCategory.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
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 June 2012