March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13885) directory.xml should work with any url, not just http

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13885?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13885: ---------------------------------------- Component/s: central > directory.xml should work with any url, not just http > ----------------------------------------------------- > > Key: JBIDE-13885 > URL: https://issues.jboss.org/browse/JBIDE-13885 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > > Creating a jbosstools-directory.xml with: > <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> > <entry url="file:///Users/max/code/jbosstools/jbosstools-central/central/plugins/org.jboss.tools.central.discovery/target/org.jboss.tools.central.discovery-1.2.0-SNAPSHOT.jar" permitCategories="true"/> > </directory> > loads, but fails to fetch the directory.xml content in this jar on central update page. > It should not be necessary to use http:// for testing this. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13885) directory.xml should work with any url, not just http

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13885: ------------------------------------------- Summary: directory.xml should work with any url, not just http Key: JBIDE-13885 URL: https://issues.jboss.org/browse/JBIDE-13885 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Creating a jbosstools-directory.xml with: <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="file:///Users/max/code/jbosstools/jbosstools-central/central/plugins/org.jboss.tools.central.discovery/target/org.jboss.tools.central.discovery-1.2.0-SNAPSHOT.jar" permitCategories="true"/> </directory> loads, but fails to fetch the directory.xml content in this jar on central update page. It should not be necessary to use http:// for testing this. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13884) JBoss Central new look'n feel

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13884: ----------------------------------- Summary: JBoss Central new look'n feel Key: JBIDE-13884 URL: https://issues.jboss.org/browse/JBIDE-13884 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 4.0.0.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.1.0.Alpha2 -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13884) JBoss Central new look'n feel

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13884?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13884: -------------------------------- Issue Type: Enhancement (was: Feature Request) > JBoss Central new look'n feel > ----------------------------- > > Key: JBIDE-13884 > URL: https://issues.jboss.org/browse/JBIDE-13884 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.0.Alpha2 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13883) Externalize Runtime Detection plugins

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13883: ------------------------------------- Summary: Externalize Runtime Detection plugins Key: JBIDE-13883 URL: https://issues.jboss.org/browse/JBIDE-13883 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Affects Versions: 4.1.0.Alpha1 Reporter: Snjezana Peco Assignee: Snjezana Peco -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2506) Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBDS-2506?page=com.atlassian.jira.plugin.... ] Douglas Palmer updated JBDS-2506: --------------------------------- Fix Version/s: 5.0.4.GA-SOA > Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x > ---------------------------------------------------------- > > Key: JBDS-2506 > URL: https://issues.jboss.org/browse/JBDS-2506 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Reporter: Douglas Palmer > Assignee: Nick Boldt > Priority: Blocker > Fix For: 5.0.4.GA-SOA > > > The target platforms (target-platform_3.3.indigo.SR2 and jbds-target-platform_3.3.indigo.SR2), required to build maintenance releases, have been removed from /home/hudson/static_build_env/jbds. Can you please restore them ASAP? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2506) Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x

by Douglas Palmer (JIRA)

Douglas Palmer created JBDS-2506: ------------------------------------ Summary: Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x Key: JBDS-2506 URL: https://issues.jboss.org/browse/JBDS-2506 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Reporter: Douglas Palmer Assignee: Nick Boldt Priority: Blocker The target platforms (target-platform_3.3.indigo.SR2 and jbds-target-platform_3.3.indigo.SR2), required to build maintenance releases, have been removed from /home/hudson/static_build_env/jbds. Can you please restore them ASAP? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13411: ----------------------------------- CI job for server test succeeds to make a full build (including dependency resolution fetched from download.jboss.org) in 4 to 20 minutes. For this job, we are speaking of several hours. That shows dependency resolution is the bottleneck of this job. Tests by themselves take long time. Isn't there a way to speed the up (using java.nio or some other code optimizations) ? > JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13411 > URL: https://issues.jboss.org/browse/JBIDE-13411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, Visual Page Editor Templates > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.x > > Attachments: tests-vs-tycho-build-time.png > > > On a good day, tests will run and all pass in under 4hrs. > On a grey day, tests will have failures but complete in under 6hrs. > On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Surely some of these tests are: > a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ? > b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2460) replace included p2-director.zip with upstream version from tycho-standalone-p2-director

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2460?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2460: --------------------------------- [~dgolovin]: I'd like to move the sources from your repo to the JBDS repo, and make them built at the same time as installer, and then fetched by installer from current build at dev-tine. Do you see any objection? > replace included p2-director.zip with upstream version from tycho-standalone-p2-director > ---------------------------------------------------------------------------------------- > > Key: JBDS-2460 > URL: https://issues.jboss.org/browse/JBDS-2460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyDependencies, Build, installer > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 7.0.0.Alpha2 > > > To build JBDS installer we need p2-director.zip [0], which is 9M and doesn't include sources. Ideally, we could just use something from Eclipse.org at build-time, and COULD include sources. > [0] https://svn.jboss.org/repos/devstudio/trunk/product/installer/p2-director... > I looked at tycho-standalone-p2-director [1,2] but it's only an update site -- it lacks equinox.launcher fragments for the various platforms on which we run. > [1] https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo... > [2] http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st... > So... maybe we need to do something similar but include the binary bits too, so that we can produce something similar to what's in this zip [3] ? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13869: ----------------------------------- > yes we can run those tests but is it not about time we get a way to run a list of test bundles against an already installed version of eclipse/JBT/JBDS ? As I already explained several times, this is already possible to do this with Eclipse headless tests. We can set up on "test jobs" that: * Take Eclipse * Install JBT or JBDS * Install Tests from any update-site * Run tests. So it's just a matter of actually doing it. What scenario do you want me to set up first (version of Eclipse, of JBT, of tests, which test suite) ? > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.0.2.Final, 4.1.0.Alpha2 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013