January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2180) Document the fact that Oracle OSX Java 7 is not supported by JBDS 5

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ] Michelle Murray edited comment on JBDS-2180 at 1/21/13 7:30 PM: ---------------------------------------------------------------- [~nickboldt] * Does this mean that JDK 1.7 can be used with JBDS 5 in general (i.e. for most operating systems)? And just OS X will have an issue? * And the release notes for 5.0.1 say "JBDS 5 requires JDK 1.6". So I have taken this to mean that users need 1.6 at a minimum? So I could include some text to the effect "JBDS 5 requires a Java developer kit of version 1.6 at a minimum. Although Oracle JDK 1.7 for Mac OS X is incompatible with JBDS 5, it is expected that Oracle JDK 1.7 for all other operating systems is compatible." was (Author: mmurray): [~nickboldt] * Does this mean that JDK 1.7 can be used with JBDS 5 in general (i.e. for most operating systems)? And just OS X will have an issue? * And the release notes for 5.0.1 say "JBDS requires JDK 1.6". So I have taken this to mean that users need 1.6 at a minimum? So I could include some text to the effect "JBDS 5 requires a Java developer kit of version 1.6 at a minimum. Although Oracle JDK 1.7 for Mac OS X is incompatible with JBDS 5, it is expected that Oracle JDK 1.7 for all other operating systems is compatible." > Document the fact that Oracle OSX Java 7 is not supported by JBDS 5 > ------------------------------------------------------------------- > > Key: JBDS-2180 > URL: https://issues.jboss.org/browse/JBDS-2180 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation, installer > Affects Versions: 5.0.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 5.0.2.GA > > > I accidentally had my java set to java 1.7 on my mac computer: > vokuro:5.0.0.CR1 rasp$ java -version > java version "1.7.0_04" > Java(TM) SE Runtime Environment (build 1.7.0_04-b21) > Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode) > When you then launch the installer using > java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar > everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed. > Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit? > FYI, on Mac OS X Lion, there are currently these jdk versions: > Apple JDK 1.6 32-bit > Apple JDK 1.6 64-bit > Oracle JDK 1.7 64-bit > I don't expect there will ever be Oracle JDK 1.7 32-bit available. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13232: ------------------------------------ Next, we need to refactor */multiple/multiple.target files as follows: {code} -<target includeMode="feature" name="jbdevstudio-4.2.1.a"> +<target includeMode="feature" name="jbdevstudiotarget-4.21.3.Final"> -<target includeMode="feature" name="jbosstools-4.2.1.a"> +<target includeMode="feature" name="jbosstoolstarget-4.21.3.Final"> {code} --- Currently publishing to nexus as follows: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (and the same again replacing /multiple/ for /unified/. Can't remove the SNAPSHOT suffix due to publishing problem - nexus rejects the `deploy` step.) One might also argue that these URLs should be more consistent w/ the paths on download.jboss.org, eg: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... should be https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... to more closely align with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... Do we need to publish both unified and multiple? Or is unified the only one that needs to be in Nexus? [~mickael_istria], [~maxandersen] what do you think? > refactor target platforms' GAVs, names, labels (was target platforms has the same name) > --------------------------------------------------------------------------------------- > > Key: JBIDE-13232 > URL: https://issues.jboss.org/browse/JBIDE-13232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Environment: > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either. > Makes it hard to actually see which target platform to choose -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13329: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... is all blue! Next step... integrating these TPs into the builds. Presume that just means updating the 40x and master (41x) versions of the parent pom? > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13355: ------------------------------------------- Long story short, it's the deletes when the tests try to clean up after themselves that are causing issues. I suspect the only way around it will be to totally restructure the tests. But it's an intermittent failure. IBM has run into it: http://www-01.ibm.com/support/docview.wss?uid=swg21316377 Spring has run into it: https://issuetracker.springsource.com/browse/STS-3007?page=com.atlassian.... Sonatype has run into it: https://issues.sonatype.org/browse/MNGECLIPSE-1809 If it's intermittent, as it appears to be on Jenkins, can we simply kick off a new build until it all works fine? We can certainly look at revising the tests in github to try and avoid this, but I'd just as soon not reinvent the wheel with redoing tests on 3.3.x too. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13263: ------------------------------------- I keep adding these gliffys to the wrong jira. What a pain ;) > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick edited comment on JBIDE-13355 at 1/21/13 1:51 PM: -------------------------------------------------------------------- I am definitely hitting the same issues Nick & Jaroslav ran into when I try to build and test the 3.3.x stream from SVN. All sorts of "Problems encountered while deleting resources" messages. And the tests freeze somewhere in executing org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite. was (Author: bfitzpat): I am definitely hitting the same issues Nick & Jaroslav ran into when I try to build and test the 3.3.x stream from SVN. All sorts of "Problems encountered while deleting resources" messages. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13355: ------------------------------------------- I am definitely hitting the same issues Nick & Jaroslav ran into when I try to build and test the 3.3.x stream from SVN. All sorts of "Problems encountered while deleting resources" messages. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13386) Create dedicated Git rep for target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13386?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13386: ------------------------------------ We can't publish to Nexus public repo, only the snapshot repo. See https://github.com/nickboldt/jbosstools-target-platforms/commit/d14d79e71... [~maxandersen] can we get a new repo called https://github.com/jbosstools/jbosstools-target-platforms/ ? Said [~mickael_istria]: {quote} it's just a matter of asking him to clone, push --all and push --tags {quote} > Create dedicated Git rep for target platforms > --------------------------------------------- > > Key: JBIDE-13386 > URL: https://issues.jboss.org/browse/JBIDE-13386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Since target platforms follow their own schedule, independently of JBT/JBDS and we maintain many streams, it would be more convenient to have them in their own Git repo. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13355: ------------------------------------------- That said, it seems we're failing in 3.3.x, not on 4.x, so I'm at a loss. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13383) Support running on Eclipse Kepler (4.3) platform

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13383?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-13383: ------------------------------------------------ Also one VPE test works unstable, I've created PR for it. > Support running on Eclipse Kepler (4.3) platform > ------------------------------------------------ > > Key: JBIDE-13383 > URL: https://issues.jboss.org/browse/JBIDE-13383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, target-platform, updatesite > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > Attachments: full-reactor-summary-with-compilation-errors.txt > > > Kepler is coming and it have many improvements performance wise over Juno and is the only version certified to run on Windows 8 afaics. It is also the first version where WTP static web project becomes more usable. and of course the general notion that Kepler is the only version we can actually get fixes into. > Migration guide for Eclipse Platform (currently empty - I've posted question on http://dev.eclipse.org/mhonarc/lists/eclipse-dev/ to check if better new doc) > http://htmlpreview.github.com/?https://github.com/eclipse/eclipse.platfor... > Migration tips for WTP (this time there are *Actual* changes!) > http://wiki.eclipse.org/New_Help_for_Old_Friends_VIII > Last years migration: JBIDE-11549 (Juno), JBIDE-8624 (Indigo). > Please link related Kepler runtime/build issues to this issue. -- 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, 2 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 January 2013