April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2490: ---------------------------------- [~maxandersen] said in JBIDE-13804: {quote} https://github.com/jbosstools/jbosstools-discovery is now in place. has only one dir now, jbosstools; when adding the devstudio stuff put that in devstudio/<discovery plugin>. {quote} > migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery > ------------------------------------------------------------------------------- > > Key: JBDS-2490 > URL: https://issues.jboss.org/browse/JBDS-2490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > > Migrate 3 branches of git sources (including history): > https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... > and 3 branches of svn sources (including history): > http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... > http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... > http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... > to a new Github project called "jbosstools-discovery" under which there would be: > * plugins/ > ** com.jboss.jbds.central.discovery/ > ** org.jboss.tools.central.discovery/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13804) Remove discovery feature from central and JBT aggregate sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13804?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-13804: ------------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) back to you. once you are ok with jbosstools-discovery please redo the central PR's that removes it from central. > Remove discovery feature from central and JBT aggregate sites > ------------------------------------------------------------- > > Key: JBIDE-13804 > URL: https://issues.jboss.org/browse/JBIDE-13804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > Cloned from JBIDE-12389. > It's time to remove Central discovery plugin/feature from https://github.com/jbosstools/jbosstools-central (moved to https://svn.jboss.org/repos/devstudio/trunk/product/discovery/ until we have a project in github for it), and remove it from the category.xml files that contain it: > https://github.com/jbosstools/jbosstools-central/blob/master/site/categor... > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13804) Remove discovery feature from central and JBT aggregate sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13804?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13804: --------------------------------------------- https://github.com/jbosstools/jbosstools-discovery is now in place. has only one dir now, jbosstools; when adding the devstudio stuff put that in devstudio/<discovery plugin>. > Remove discovery feature from central and JBT aggregate sites > ------------------------------------------------------------- > > Key: JBIDE-13804 > URL: https://issues.jboss.org/browse/JBIDE-13804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > Cloned from JBIDE-12389. > It's time to remove Central discovery plugin/feature from https://github.com/jbosstools/jbosstools-central (moved to https://svn.jboss.org/repos/devstudio/trunk/product/discovery/ until we have a project in github for it), and remove it from the category.xml files that contain it: > https://github.com/jbosstools/jbosstools-central/blob/master/site/categor... > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13928: ------------------------------- Fix Version/s: 4.1.0.Beta1 > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-36) Remove all download.jboss.org references from devstudio side of the the integration stack aggregate build

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-36?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-36. ----------------------------- Resolution: Done Issue resolved - see commit: https://github.com/jbosstools/jbosstools-integration-stack/commit/20456f4... > Remove all download.jboss.org references from devstudio side of the the integration stack aggregate build > --------------------------------------------------------------------------------------------------------- > > Key: JBTIS-36 > URL: https://issues.jboss.org/browse/JBTIS-36 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.0.0 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13928: ------------------------------------- I don't see why we would need the sources *inside* JBDS. Except for m2e and its sdk (I wonder why it's there BTW), no m2e related plugins (m2e-* or org.jboss.tools.maven.*) are currently included in JBDS As for having the sources available in the TP for developer consumption, there's no reason why it should be treated differently than other plugins. > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13928: ------------------------------------ It's not built as part of the JBT maven project: http://download.jboss.org/jbosstools/builds/staging/jbosstools-central_ma... vs. http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.0.1... So... I suppose we could just aggregate it into the JBT project via this, treating it like one of our own (1rst party) instead of an upstream (3rd party) requirement: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13912) Build failures on the JAX-RS plugin after TP upgraded to Kepler M6

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13912?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13912: ------------------------------------------- You mean it was successful? The build was blue (no test failures) > Build failures on the JAX-RS plugin after TP upgraded to Kepler M6 > ------------------------------------------------------------------ > > Key: JBIDE-13912 > URL: https://issues.jboss.org/browse/JBIDE-13912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > All tests fail with NPE. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13375) 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS*

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13375?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13375: ------------------------------------------- Can we close this one then if it's no longer an issue? > 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS* > ------------------------------------------------------------------------- > > Key: JBIDE-13375 > URL: https://issues.jboss.org/browse/JBIDE-13375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.2.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--ws/156/testReport/} > Test Result > 6 failures (+6) , 13 skipped (±0) > 440 tests (±0) > Took 42 min. > add description > All Failed Tests > Test Name Duration Age > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 1 min 46 sec 1 > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 20 min 1 > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 15 ms 1 > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 7 ms 1 > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 7 ms 1 > >>> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1{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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13830) document reasons for using Eclipse Juno SR2 instead of earlier version on www.jboss.org install page for JBT 4.0.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13830?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13830: ------------------------------------ Thanks, [~rob.stryker]. So... "Web Tools 3.4.1 introduced a behaviour change (which some might consider a bug) such that it now ignores metadata files such as .project." Has this been reported to WTP and if so, do you know the bugzilla #? > document reasons for using Eclipse Juno SR2 instead of earlier version on www.jboss.org install page for JBT 4.0.1 > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13830 > URL: https://issues.jboss.org/browse/JBIDE-13830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite, website > Affects Versions: 4.0.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > When we release JBT 4.0.1, we should update https://www.jboss.org/tools/download/installation/update_4_0#installon420421 to include a blurb about why we encourage users to use Juno SR2 instead of R or SR1. > Reasons include: > a) performance patch, JBIDE-13326 / JBIDE-13335 > b) WTP bug / behaviour change between WTP 3.3.0 & 3.3.1: JBIDE-13821 -- 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, 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 April 2013