December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Marek Goldmann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Marek Goldmann commented on JBIDE-3509: --------------------------------------- [~nickboldt] The eclipse-jbosstools package is a meta package that pulls other packages (as you already pointed out). Good idea is to look at Requires section here: https://apps.fedoraproject.org/packages/eclipse-jbosstools/relationships/ It's probably missing some features, but please bear in mind, that this package is created and maintained by Gerard Ryan - a Fedora community member (not employed by RH). The initial stuff was done as part of Fedora GSoC. We should really thank him for this great job and time he spent on this. We should be able to add new subprojects, at least hibernate. +137 for removing SNAPSHOT. > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-12109. ----------------------------------- Fix Version/s: 4.1.1.Final (was: 4.1.x) Resolution: Cannot Reproduce Bug I cannot replicate this either (on JBDS 7.1.0). > JMX connection to AS7/EAP6 not working if server started with Java 1.7 > ---------------------------------------------------------------------- > > Key: JBIDE-12109 > URL: https://issues.jboss.org/browse/JBIDE-12109 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar > Mac OS X 10.7 Lion > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.1.Final > > > When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897 > !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1 > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > ... 6 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897 > !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > !STACK 0 > java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > This has several consequences: > - server cannot be connected in MBean Explorer > - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below) > - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully > Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-12109: ------------------------------------- [~rob.stryker]unable to replicate and this jira was based on JBDS 5 > JMX connection to AS7/EAP6 not working if server started with Java 1.7 > ---------------------------------------------------------------------- > > Key: JBIDE-12109 > URL: https://issues.jboss.org/browse/JBIDE-12109 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar > Mac OS X 10.7 Lion > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.x > > > When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897 > !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1 > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > ... 6 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897 > !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > !STACK 0 > java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > This has several consequences: > - server cannot be connected in MBean Explorer > - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below) > - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully > Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-12109: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) [~burrsutter] To be clear, you're saying you're unable to replicate? > JMX connection to AS7/EAP6 not working if server started with Java 1.7 > ---------------------------------------------------------------------- > > Key: JBIDE-12109 > URL: https://issues.jboss.org/browse/JBIDE-12109 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar > Mac OS X 10.7 Lion > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.x > > > When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897 > !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1 > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > ... 6 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897 > !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property > !STACK 0 > java.lang.RuntimeException: Operation failed with status WAITING > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > This has several consequences: > - server cannot be connected in MBean Explorer > - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below) > - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully > Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16220: ------------------------------------ Job times out after 720 minutes, with test failures. [~dgolovin] any idea why this takes so long in Jenkins but can complete in a few hours locally? > create an all-in-one build for JBT projects, using submodules > ------------------------------------------------------------- > > Key: JBIDE-16220 > URL: https://issues.jboss.org/browse/JBIDE-16220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > Attachments: buildlog_maven311.txt > > > Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs. > {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} > "git submodule" started learning a new mode to integrate with the > tip of the remote branch (as opposed to integrating with the commit > recorded in the superproject's gitlink). > {code} > Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. > If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16269?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16269: ------------------------------------ _42 and _master are timing out. Also noticed some job misconfigs in both discovery and install-tests jobs, which I've fixed. Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=11 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=1531 Tests are still timing out, now even with 10hrs of runtime. This needs to be investigated more fully. [~mickael_istria] can you take a look? > Parameterize URL from which to install SWTBot with install-grinder is setting up > -------------------------------------------------------------------------------- > > Key: JBIDE-16269 > URL: https://issues.jboss.org/browse/JBIDE-16269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, testing-tools > Affects Versions: 4.1.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. > {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} > proc.setArgs("-application org.eclipse.equinox.p2.director " + > "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + > {code} > Latest stable release of SWTBot is mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16269?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-16269 at 12/21/13 12:44 PM: --------------------------------------------------------------- _42 and _master are timing out. Also noticed some job misconfigs in both discovery and install-tests jobs, which I've fixed. Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=14 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=1540 Tests are still timing out, now even with 10hrs of runtime. This needs to be investigated more fully. [~mickael_istria] can you take a look? was (Author: nickboldt): _42 and _master are timing out. Also noticed some job misconfigs in both discovery and install-tests jobs, which I've fixed. Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=11 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=1531 Tests are still timing out, now even with 10hrs of runtime. This needs to be investigated more fully. [~mickael_istria] can you take a look? > Parameterize URL from which to install SWTBot with install-grinder is setting up > -------------------------------------------------------------------------------- > > Key: JBIDE-16269 > URL: https://issues.jboss.org/browse/JBIDE-16269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, testing-tools > Affects Versions: 4.1.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. > {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} > proc.setArgs("-application org.eclipse.equinox.p2.director " + > "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + > {code} > Latest stable release of SWTBot is mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16269?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-16269 at 12/21/13 12:45 PM: --------------------------------------------------------------- Tests are still timing out, now even with 10hrs of runtime. This needs to be investigated more fully. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=14 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=1540 [~mickael_istria] can you take a look? was (Author: nickboldt): _42 and _master are timing out. Also noticed some job misconfigs in both discovery and install-tests jobs, which I've fixed. Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=14 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... >=1540 Tests are still timing out, now even with 10hrs of runtime. This needs to be investigated more fully. [~mickael_istria] can you take a look? > Parameterize URL from which to install SWTBot with install-grinder is setting up > -------------------------------------------------------------------------------- > > Key: JBIDE-16269 > URL: https://issues.jboss.org/browse/JBIDE-16269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, testing-tools > Affects Versions: 4.1.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. > {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} > proc.setArgs("-application org.eclipse.equinox.p2.director " + > "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + > {code} > Latest stable release of SWTBot is mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- How about using *com.jboss.devstudio.product* for the product (previously com.jboss.jbds.all), and *com.jboss.devstudio.core* for the core features (previously com.jboss.jbds.product*) > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-3509: ----------------------------------- I wonder if we need to revisit how we build/version these plugins so that the -SNAPSHOT is not in their versions, but rather the actual timestamp/qualifier/version of the artifacts? > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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, 3 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