[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss
by Gerard Ryan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ]
Gerard Ryan edited comment on JBIDE-3509 at 12/23/13 11:51 AM:
---------------------------------------------------------------
Hi guys,
Yeah, it's more or less just myself that has been working on this so far. I 100% intend to complete it, and make it as good as it can be in Fedora. The main problem that I run into though, is time, since I've got a full time job now that means that I only really get to look at this at the weekend. When I do get to look at the eclipse-jbosstools package, a lot of that time is spent looking at its dependencies, such as wtp and m2e, since I'm really the only person maintaining those packages. As you can guess, it's not too often that I'm in a position to look at adding more of the subprojects of JBoss Tools (even though I really want to get to that point, and fully intend to). There are quite a few moving pieces that have to be more or less in line for it, and because I usually work on it outside the hours of most of the Fedora Java guys from RH, sometimes there are stumbling blocks that I'll need them to clear, so things go quite slowly!
Anyway, now that I've got holidays for a while, I should get some time to look at it. There are a few problems with our m2e-core package that will have to take priority for the moment.
[~nickboldt]: Regarding the version, -SNAPSHOT only shows up in the naming on the filesystem, when loaded in Eclipse, the timestamp/qualifier is shown. Max also got me to add Fedora version to the end of the usual <version>.v<timestamp>.-<build-alias>. Example: org.jboss.tools.openshift.egit.core-2.5.0-SNAPSHOT.jar in Fedora 20 is loaded with version 2.0.5.v20131002-2156-Final-F20. I think this is mostly for usage reporting, and in case there are bug reports here that are specific to Fedora builds.
Most of the information I've given here is probably useless, but feel free to contact me any time if you want any more info on anything about this! :)
was (Author: grdryn):
Hi guys,
Yeah, it's more or less just myself that has been working on this so far. I 100% intend to complete it, and make it as good as it can be in Fedora. The main problem that I run into though, is time, since I've got a full time job now that means that I only really get to look at this at the weekend. When I do get to look at the eclipse-jbosstools package, a lot of that time is spent looking at its dependencies, such as wtp and m2e, since I'm really the only person maintaining those packages. As you can guess, it's not too often that I'm in a position to look at adding more of the subprojects of JBoss Tools (even though I really want to get to that point, and fully intend to). There are quite a few moving pieces that have to be more or less in line for it, and because I usually work on it outside the hours of most of the Fedora Java guys from RH, sometimes there are stumbling blocks that I'll need them to clear, so things go quite slowly!
Anyway, now that I've got holidays for a while, I should get some time to look at it. There are a few problems with our m2e-core package that will have to take priority for the moment.
[~nickboldt]: Regarding the version, -SNAPSHOT only shows up in the naming on the filesystem, when loaded in Eclipse, the timestamp/qualifier is shown. Max also got me to add Fedora version to the end of the usual <version>.v<timestamp>.-<build-alias>. Example: org.jboss.tools.openshift.egit.core-2.5.0-SNAPSHOT.jar in Fedora 20 is loaded with version 2.0.5.v20131002-2156-Final-F20 -- I think this is mostly for usage reporting, and in case there are bug reports here that are specific to Fedora builds.
Most of the information I've given here is probably useless, but feel free to contact me any time if you want any more info on anything about this! :)
> 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
10 years, 5 months
[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss
by Gerard Ryan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ]
Gerard Ryan commented on JBIDE-3509:
------------------------------------
Hi guys,
Yeah, it's more or less just myself that has been working on this so far. I 100% intend to complete it, and make it as good as it can be in Fedora. The main problem that I run into though, is time, since I've got a full time job now that means that I only really get to look at this at the weekend. When I do get to look at the eclipse-jbosstools package, a lot of that time is spent looking at its dependencies, such as wtp and m2e, since I'm really the only person maintaining those packages. As you can guess, it's not too often that I'm in a position to look at adding more of the subprojects of JBoss Tools (even though I really want to get to that point, and fully intend to). There are quite a few moving pieces that have to be more or less in line for it, and because I usually work on it outside the hours of most of the Fedora Java guys from RH, sometimes there are stumbling blocks that I'll need them to clear, so things go quite slowly!
Anyway, now that I've got holidays for a while, I should get some time to look at it. There are a few problems with our m2e-core package that will have to take priority for the moment.
[~nickboldt]: Regarding the version, -SNAPSHOT only shows up in the naming on the filesystem, when loaded in Eclipse, the timestamp/qualifier is shown. Max also got me to add Fedora version to the end of the usual <version>.v<timestamp>.-<build-alias>. Example: org.jboss.tools.openshift.egit.core-2.5.0-SNAPSHOT.jar in Fedora 20 is loaded with version 2.0.5.v20131002-2156-Final-F20 -- I think this is mostly for usage reporting, and in case there are bug reports here that are specific to Fedora builds.
Most of the information I've given here is probably useless, but feel free to contact me any time if you want any more info on anything about this! :)
> 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
10 years, 5 months
[JBoss JIRA] (JBIDE-16324) Refactor Arquillian validator
by Snjezana Peco (JIRA)
Snjezana Peco created JBIDE-16324:
-------------------------------------
Summary: Refactor Arquillian validator
Key: JBIDE-16324
URL: https://issues.jboss.org/browse/JBIDE-16324
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing-tools
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 4.2.0.Alpha2
While fixing https://issues.jboss.org/browse/JBIDE-14525, I had to change the way in which the Arquillian validator works because compiling a class doesn't solve dependent classes.
Because of that, we don't have to create archive anymore. We only need the structure of an archive that can be got using Archive.toString(true) which will significantly improve performance.
--
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
10 years, 5 months
[JBoss JIRA] (JBIDE-16324) Refactor Arquillian validator
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16324?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16324:
----------------------------------
Description:
While fixing JBIDE-14525, I had to change the way in which the Arquillian validator works because compiling a class doesn't solve dependent classes.
Because of that, we don't have to create archive anymore. We only need the structure of an archive that can be got using Archive.toString(true) which will significantly improve performance.
was:
While fixing https://issues.jboss.org/browse/JBIDE-14525, I had to change the way in which the Arquillian validator works because compiling a class doesn't solve dependent classes.
Because of that, we don't have to create archive anymore. We only need the structure of an archive that can be got using Archive.toString(true) which will significantly improve performance.
> Refactor Arquillian validator
> -----------------------------
>
> Key: JBIDE-16324
> URL: https://issues.jboss.org/browse/JBIDE-16324
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
>
> While fixing JBIDE-14525, I had to change the way in which the Arquillian validator works because compiling a class doesn't solve dependent classes.
> Because of that, we don't have to create archive anymore. We only need the structure of an archive that can be got using Archive.toString(true) which will significantly improve performance.
--
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
10 years, 5 months
[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
10 years, 5 months
[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
10 years, 5 months
[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
10 years, 5 months
[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
10 years, 5 months
