December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15388?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15388: ------------------------------------ Can the Jenkins Job segment that performs the `mvn deploy` be fired only the git revision check done in publish.sh sets PUBLISH_STATUS to include the string *"PUBLISHED"* ? I guess you'd need a shell wrapper to call maven, rather than just calling it as a job config segment. Something like this... {code} if [[ $\{PUBLISH_STATUS} ]] && [[ $\{PUBLISH_STATUS##\*PUBLISHED*} == "" ]]; then pushd $\{WORKSPACE}/sources /path/to/maven311 deploy popd fi {code} > Compute whether to publish or not based on output signature rather than commits > ------------------------------------------------------------------------------- > > Key: JBIDE-15388 > URL: https://issues.jboss.org/browse/JBIDE-15388 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: LATER > > > [Assuming we already have reproducible qualifiers...] > Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication. > However there are some case not correctly supported: > * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen > * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it. > instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15981) Create New and Noteworthy for 4.1.1.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15981?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15981. ----------------------------------------- Assignee: Max Rydahl Andersen Resolution: Done whoops - should have been resolved. is now done for all. > Create New and Noteworthy for 4.1.1.CR1 > --------------------------------------- > > Key: JBIDE-15981 > URL: https://issues.jboss.org/browse/JBIDE-15981 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16169) Release JBoss Central TP in prep for JBT 4.1.1 / JBDS 7.1.0

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16169: ---------------------------------- Summary: Release JBoss Central TP in prep for JBT 4.1.1 / JBDS 7.1.0 Key: JBIDE-16169 URL: https://issues.jboss.org/browse/JBIDE-16169 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, discovery, target-platform Affects Versions: 4.1.1.CR1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 4.1.1.Final Job is here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... Code is here: https://github.com/jbosstools/jbosstools-discovery/tree/jbosstools-4.1.1.x https://github.com/jbosstools/jbosstools-discovery/tree/jbosstools-4.1.x Currently built bits are here, as referenced by JBT 4.1.1.CR1 / JBDS 7.1.0.CR1: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3... Need to release that to Nexus and rebuild it as http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3... Then we can rebuild the discovery site to point to the new URL, using this job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery... and end up with this: http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/ which can then be published in a couple weeks to here: http://download.jboss.org/jbosstools/discovery/stable/ -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16137) webservices component build slow during tests on MacOSX 10.7

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16137: ------------------------------------------- Snjezana, thanks for looking into this. Xavier, can you verify this fix helps on Mac OS? I don't have a way to test it currently. > webservices component build slow during tests on MacOSX 10.7 > ------------------------------------------------------------ > > Key: JBIDE-16137 > URL: https://issues.jboss.org/browse/JBIDE-16137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, webservices > Affects Versions: 4.2.0.Alpha1 > Environment: Luna 4.4 M3 TP > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Attachments: jstack-43357.txt > > > when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build is *very* slow > {code} > [INFO] Command line: > /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16134) CordovaSim should start the livereload server

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16134: -------------------------------------- [~maxandersen] I guess the point I am trying to make is once we have the menu item for enabling livereload, whether the OSGi dependency exists or not, we have a dependency to livereload. If we can resolve the end users perception that [~burrsutter] described above, in a good way without adding dependencies that is great, but if we need to add them I do not think it is a big problem. > CordovaSim should start the livereload server > --------------------------------------------- > > Key: JBIDE-16134 > URL: https://issues.jboss.org/browse/JBIDE-16134 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > > CordovaSim should configure and start the livereload server when the livereload is enabled. > If starting the server from CordovaSim menu is a big problem, alternately, the server can always be configured and started before a CordovaSim launch. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16168) Server Adapter: Adapter should not publish if the application is not running

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16168: ---------------------------------------- Summary: Server Adapter: Adapter should not publish if the application is not running Key: JBIDE-16168 URL: https://issues.jboss.org/browse/JBIDE-16168 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Andre Dietisheim Fix For: 4.2.x If you pick "Publish" from the context menu of an OpenShift Server Adapter, then the adapter will git push to the OpenShift git repository. This makes no sense if the application, that holds the git repository, is not running. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15577) Hibernate Console problem while creating session factory

by Guillaume JOUVELOT (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15577?page=com.atlassian.jira.plugi... ] Guillaume JOUVELOT commented on JBIDE-15577: -------------------------------------------- Hi, sorry to respond just now. In fact, I made a test recently in order to find the problem root. In my hibernate.cfg.xml if I don't declare C3PO properties to manage the connections, the session factory doesn't issue. If I remember well, the last releases of C3PO are a bit different and the declaration of the plugin into the hibernate.cfg.xml is not the same : new property <property name="hibernate.connection.provider_class">org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider</property> old property <property name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property> Maybe the problem comes from here... I hope it would help you. > Hibernate Console problem while creating session factory > -------------------------------------------------------- > > Key: JBIDE-15577 > URL: https://issues.jboss.org/browse/JBIDE-15577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.x > Environment: Eclipse 4.3 (kepler), hibernate tools 3.7.0, Hibernate 4.2.2, jdk1.6.0.38 > Reporter: Guillaume JOUVELOT > Assignee: Koen Aers > Fix For: 4.2.x > > > When I try to use hibernate console in order to test HQL queries I've the following error message from eclipse : > {color:red}java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;{color} > And the eclipse log file : > !ENTRY org.hibernate.eclipse.console 4 4 2013-09-27 15:57:20.198 > !MESSAGE Problems while creating sessionfactory > !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198 > !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object; > !STACK 0 > java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object; > at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) > at java.lang.reflect.Constructor.newInstance(Unknown Source) > at java.lang.Class.newInstance0(Unknown Source) > at java.lang.Class.newInstance(Unknown Source) > at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174) > at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102) > at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84) > at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438) > at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91) > at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163) > at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383) > at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273) > at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198 > !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object; > !STACK 0 > java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object; > at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) > at java.lang.reflect.Constructor.newInstance(Unknown Source) > at java.lang.Class.newInstance0(Unknown Source) > at java.lang.Class.newInstance(Unknown Source) > at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174) > at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102) > at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84) > at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438) > at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91) > at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163) > at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383) > at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273) > at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > I've well configured my session factory. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16148) Enable/disable updating pom.xml when adding Arquillian support

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16148?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16148: ---------------------------------- Fix Version/s: 4.1.1.Final 4.2.0.Alpha1 > Enable/disable updating pom.xml when adding Arquillian support > -------------------------------------------------------------- > > Key: JBIDE-16148 > URL: https://issues.jboss.org/browse/JBIDE-16148 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16148) Enable/disable updating pom.xml when adding Arquillian support

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16148?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16148: ---------------------------------- Labels: respin-b (was: ) > Enable/disable updating pom.xml when adding Arquillian support > -------------------------------------------------------------- > > Key: JBIDE-16148 > URL: https://issues.jboss.org/browse/JBIDE-16148 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Max Rydahl Andersen > Labels: respin-b > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16151) Add m2e-apt 1.1.0 to JBT/JBDS TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16151?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16151: ---------------------------------------- [~fbricon] Can you please formalize the description of this request as explained in https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... ? > Add m2e-apt 1.1.0 to JBT/JBDS TP > -------------------------------- > > Key: JBIDE-16151 > URL: https://issues.jboss.org/browse/JBIDE-16151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha1 > > > m2e-apt 1.1.0 provides support for m2e 1.5 (previous m2e-apt version is totally incompatible) > Jenkins Job pending : > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/m2ec... > Once the job is finished, please use the latest http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.0-* 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

12 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 December 2013