March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2484: ----------------------------- Description: For JBDS 7, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682 * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486 * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395 * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485 * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415 These are currently unchanged since December when we released JBDS 6.0.0: * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28 * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28 * pmd/3.2.6 - nothing new as of 2013.02.28 Additionally: * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core) Latest sites: http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... was: For JBDS 7, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682 * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 - JBDS-2486 * springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395 * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485 * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415 These are currently unchanged since December when we released JBDS 6.0.0: * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28 * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28 * pmd/3.2.6 - nothing new as of 2013.02.28 Additionally: * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core) Latest sites: http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... > 3rd party certification for JBDS 7.x (JBDS70_1211) > -------------------------------------------------- > > Key: JBDS-2484 > URL: https://issues.jboss.org/browse/JBDS-2484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements > Affects Versions: 7.0.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > For JBDS 7, we need to ensure this list is as current and up to date as possible. > The current list of Extras/Central connectors that we mirror are: > * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682 > * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486 > * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395 > * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485 > * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415 > These are currently unchanged since December when we released JBDS 6.0.0: > * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28 > * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28 > * pmd/3.2.6 - nothing new as of 2013.02.28 > Additionally: > * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core) > Latest sites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13842) Project examples that depend on GPE/GWT 3.1 will need to be updated if we include GPE/GWT 3.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13842?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13842. ------------------------------ Fix Version/s: 4.0.1.Final 4.1.0.Alpha2 Resolution: Done Correction. We've already updated the connectorIds to be more generic, so this isn't a problem: {code:title=project-examples-shared-4.0.GA.xml, project-examples-shared-4.1.Alpha2.xml, project-examples-maven-4.1.Alpha2.xml, project-examples-maven-4.0.GA.xml, project-examples-jbds60.xml} <property name="connectorIds">com.google.gpe.gwt</property> {code} > Project examples that depend on GPE/GWT 3.1 will need to be updated if we include GPE/GWT 3.2 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-13842 > URL: https://issues.jboss.org/browse/JBIDE-13842 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: GWT, project-examples > Affects Versions: 4.0.1.Final, 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > jbosstools-download.jboss.org/jbosstools/examples/project-examples-maven-... and project-examples-shared-4.0.Beta1.xml for refer to com.google.gwt.eclipse.sdkbundle.e42.feature. But in GWT 3.2, this feature has been renamed to com.google.gwt.eclipse.sdkbundle.feature (no more e42 segment). > So, if we decide to include GWT 3.2 in JBoss Tools 4.0.x / JBDS 6.0.x, we will need to update this. > Additionally, when we roll out a new project-examples-maven-4.1.*.xml for JBT 4.1 / JBDS 7, we need to ensure we're pointing at the correct connectorId. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13842) Project examples that depend on GPE/GWT 3.1 will need to be updated if we include GPE/GWT 3.2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13842: ---------------------------------- Summary: Project examples that depend on GPE/GWT 3.1 will need to be updated if we include GPE/GWT 3.2 Key: JBIDE-13842 URL: https://issues.jboss.org/browse/JBIDE-13842 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT, project-examples Affects Versions: 4.0.1.Final, 4.1.0.Alpha2 Reporter: Nick Boldt Assignee: Denis Golovin jbosstools-download.jboss.org/jbosstools/examples/project-examples-maven-... and project-examples-shared-4.0.Beta1.xml for refer to com.google.gwt.eclipse.sdkbundle.e42.feature. But in GWT 3.2, this feature has been renamed to com.google.gwt.eclipse.sdkbundle.feature (no more e42 segment). So, if we decide to include GWT 3.2 in JBoss Tools 4.0.x / JBDS 6.0.x, we will need to update this. Additionally, when we roll out a new project-examples-maven-4.1.*.xml for JBT 4.1 / JBDS 7, we need to ensure we're pointing at the correct connectorId. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2486 at 3/22/13 9:17 AM: ----------------------------------------------------------- The latest nightly build of Central (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... >=78) should properly install GWT 3.2 now as I've fixed the plugin.xml to point to the correct (renamed) sdkbundle feature. To test: {code} eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbosstools-directory.xml or jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml {code} was (Author: nickboldt): The latest nightly build of Central (>=78) should properly install GWT 3.2 now as I've fixed the plugin.xml to point to the correct (renamed) sdkbundle feature. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... >=78 --> http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbossto... or http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstu... > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Alpha2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13599: ------------------------------------ [~maxandersen] or [~dgolovin] ... any progress on committing this PR? > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2486. ------------------------------ Release Notes Docs Status: Not Yet Documented Release Notes Text: Include GWT 3.2 in JBoss Central (JBT 4.0/JBDS 6.0 still have GWT 3.1) Resolution: Done The latest nightly build of Central (>=78) should properly install GWT 3.2 now as I've fixed the plugin.xml to point to the correct (renamed) sdkbundle feature. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... >=78 --> http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbossto... or http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstu... > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Alpha2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2395 at 3/22/13 9:03 AM: ----------------------------------------------------------- Something is missing from our target platform to allow SpringIDE 3.2 to be installed: Zest. {code} Software being installed: Spring IDE OSGi Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.osgi.feature.feature.group 3.2.0.201301251408-M2) Missing requirement: Spring IDE Live Beans Graph 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.beans.ui.livegraph 3.2.0.201301251408-M2) requires 'bundle org.eclipse.zest.core [1.0.0,2.0.0)' but it could not be found {code} Temporary workaround: add this site to Eclipse/JBDS to allow dependency resolution: http://download.jboss.org/jbosstools/updates/requirements/kepler/20130208... Zest has been added to the next TP along with the move to Kepler M6. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... was (Author: nickboldt): Something is missing from our target platform to allow SpringIDE 3.2 to be installed: Zest. {code} Software being installed: Spring IDE OSGi Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.osgi.feature.feature.group 3.2.0.201301251408-M2) Missing requirement: Spring IDE Live Beans Graph 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.beans.ui.livegraph 3.2.0.201301251408-M2) requires 'bundle org.eclipse.zest.core [1.0.0,2.0.0)' but it could not be found {code} Temporary workaround: add this site to Eclipse/JBDS to allow dependency resolution: http://download.jboss.org/jbosstools/updates/requirements/kepler/20130208... Zest will be added into the next TP iteration (4.30.6) when we move to Kepler M6. > Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central > ----------------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jaroslav Jankovič > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ - 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ - 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1946) Investigate use of jRebel in JBT/JBDS

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-1946?page=com.atlassian.jira.plugin.... ] Martin Malina resolved JBDS-1946. --------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 5.x) Resolution: Done The issue with port detection is still not happening for me. So let's verify this again in 7.0.0.Alpha2. > Investigate use of jRebel in JBT/JBDS > ------------------------------------- > > Key: JBDS-1946 > URL: https://issues.jboss.org/browse/JBDS-1946 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite > Affects Versions: 5.0.0.M5 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 7.0.0.Alpha2 > > Attachments: jrebelinstallscreenshot.png > > > Download: http://zeroturnaround.com/jrebel/current/ > License: http://zeroturnaround.com/jrebel/end-user-license-agreement/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13824) update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13824?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13824. ------------------------------ Fix Version/s: 4.0.1.Final 4.1.0.Alpha2 Resolution: Done Jobs are bluer than before (timeouts and incompatible installs are separate problems) so closing. > update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13824 > URL: https://issues.jboss.org/browse/JBIDE-13824 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing-tools > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.upgrade-tests.matrix/7/console} > Started by user nboldt(a)REDHAT.COM > [EnvInject] - Loading node environment variables. > [EnvInject] - Preparing an environment for the build. > [EnvInject] - Keeping Jenkins system variables. > [EnvInject] - Keeping Jenkins build variables. > [EnvInject] - Adding build parameters as variables. > [EnvInject] - Evaluation the following Groovy script content: > // Horrible hack to set PRODUCT ! > import hudson.model.* > def thr = Thread.currentThread() > def build = thr?.executable > def resolver = build.buildVariableResolver > def url = resolver.resolve("INSTALL_URL") > String product = url.contains("devstudio") ? "devstudio" : "jbosstools" > String proto = url.contains("devstudio.jboss.com") ? "https" : "http" > [PRODUCT: product, PROTO: proto] > [EnvInject] - [ERROR] - SEVERE ERROR occurs: No such property: executable for class: hudson.model.OneOffExecutor > Notifying upstream projects of job completion > Finished: FAILURE > {code} > Similar problem (which I worked around by removing the check on url and just hardcoding the values of product and proto): > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/77/console} > Started by user nboldt(a)REDHAT.COM > [EnvInject] - Loading node environment variables. > [EnvInject] - Preparing an environment for the build. > [EnvInject] - Keeping Jenkins system variables. > [EnvInject] - Keeping Jenkins build variables. > [EnvInject] - Adding build parameters as variables. > [EnvInject] - Evaluation the following Groovy script content: > // Horrible hack to set PRODUCT ! > import hudson.model.* > def thr = Thread.currentThread() > def build = thr?.getCurrentExecutable() > def resolver = build.buildVariableResolver > def url = resolver.resolve("INSTALL_URL") > String product = url.contains("devstudio") ? "devstudio" : "jbosstools" > String proto = url.contains("devstudio.jboss.com") ? "https" : "http" > [PRODUCT: product, PROTO: proto] > [EnvInject] - [ERROR] - SEVERE ERROR occurs: Cannot invoke method contains() on null object > Notifying upstream projects of job completion > Finished: FAILURE{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13841) Fix ModeShape bot tests to run with Java 7

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-13841: ----------------------------------------- Summary: Fix ModeShape bot tests to run with Java 7 Key: JBIDE-13841 URL: https://issues.jboss.org/browse/JBIDE-13841 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 4.0.0.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Priority: Minor ModeShape bot tests fail with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 March 2013