March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12973: --------------------------------------- thanks, Mickael. I removed the separate emails feature and also added the launch of the window manager and the last run is at 35 failures, so it helped a lot. now I need to push our team to fix the rest :) the last build didn't publish anything to http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ because there were no changes in git. > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing-tools, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13782) Finish implementation of EsbHandler

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-13782: ----------------------------------- Summary: Finish implementation of EsbHandler Key: JBIDE-13782 URL: https://issues.jboss.org/browse/JBIDE-13782 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb Affects Versions: 4.1.0.Alpha1 Reporter: Rob Stryker Assignee: Brian Fitzpatrick Fix For: 4.1.0.Alpha2 The esb handler is only organized in a way to accept input from the installer. It does nothing at all in the case of the runtime detection pointing to, for example, a soa-p installation. Also, the esb runtime preference page does not update its UI if, in the background, something updates hte model by adding or removing an esb runtime to the core model. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13781) Add maven-acr-plugin when converting project with app-client dependency

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13781?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-13781: ------------------------------------- Description: When converting project with dependency to another project with app-client packaging we should also add {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-acr-plugin</artifactId> <version>1.0</version> <extensions>true</extensions> </plugin> {code} in order to make sure that converted project is buildable. WDYT ? was: When converting project with dependency to another project with app-client packaging we should also add {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-acr-plugin</artifactId> <version>1.0</version> <extensions>true</extensions> </plugin> {code} in order to make sure that converted EAR project is buildable. WDYT ? > Add maven-acr-plugin when converting project with app-client dependency > ----------------------------------------------------------------------- > > Key: JBIDE-13781 > URL: https://issues.jboss.org/browse/JBIDE-13781 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > When converting project with dependency to another project with app-client packaging we should also add > {code} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-acr-plugin</artifactId> > <version>1.0</version> > <extensions>true</extensions> > </plugin> > {code} > in order to make sure that converted project is buildable. > WDYT ? -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13781) Add maven-acr-plugin when converting project with app-client dependency

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-13781: ---------------------------------------- Summary: Add maven-acr-plugin when converting project with app-client dependency Key: JBIDE-13781 URL: https://issues.jboss.org/browse/JBIDE-13781 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.1.0.Alpha1 Reporter: Rastislav Wagner Assignee: Fred Bricon Fix For: 4.1.0.Beta1 When converting project with dependency to another project with app-client packaging we should also add {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-acr-plugin</artifactId> <version>1.0</version> <extensions>true</extensions> </plugin> {code} in order to make sure that converted EAR project is buildable. WDYT ? -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13476) Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13476 at 3/13/13 4:17 AM: ----------------------------------------------------------------- Still to process: * https://github.com/jbosstools/jbosstools-gwt/pull/4 * https://github.com/jbosstools/jbosstools-freemarker/pull/5 * https://github.com/jbosstools/jbosstools-runtime-soa/pull/10 * https://github.com/jbosstools/jbosstools-bpel/pull/8 [~dgolovin], [~nickboldt]: Are you gatekeepers for these repositories? Could you process those PR so we can mark this issue as done? was (Author: mickael_istria): Still to process: * https://github.com/jbosstools/jbosstools-gwt/pull/4 * https://github.com/jbosstools/jbosstools-freemarker/pull/5 * https://github.com/jbosstools/jbosstools-runtime-soa/pull/10 * https://github.com/jbosstools/jbosstools-bpel/pull/8 [~dgolovin], [~nickboldt]: Are you gatekeepers for these repositories? Could you process those PR so we can mark this issue as done? > Get rid of bootstrap profiles in root poms for JBT projects (no longer needed) > ------------------------------------------------------------------------------ > > Key: JBIDE-13476 > URL: https://issues.jboss.org/browse/JBIDE-13476 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, Visual Page Editor core > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > It seens like the bootstrap profiles are not used by developers. > The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone. > We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms. > Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13476) Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13476: ---------------------------------------- Still to process: * https://github.com/jbosstools/jbosstools-gwt/pull/4 * https://github.com/jbosstools/jbosstools-freemarker/pull/5 * https://github.com/jbosstools/jbosstools-runtime-soa/pull/10 * https://github.com/jbosstools/jbosstools-bpel/pull/8 [~dgolovin], [~nickboldt]: Are you gatekeepers for these repositories? Could you process those PR so we can mark this issue as done? > Get rid of bootstrap profiles in root poms for JBT projects (no longer needed) > ------------------------------------------------------------------------------ > > Key: JBIDE-13476 > URL: https://issues.jboss.org/browse/JBIDE-13476 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, Visual Page Editor core > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > It seens like the bootstrap profiles are not used by developers. > The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone. > We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms. > Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13476) Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13476: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > Get rid of bootstrap profiles in root poms for JBT projects (no longer needed) > ------------------------------------------------------------------------------ > > Key: JBIDE-13476 > URL: https://issues.jboss.org/browse/JBIDE-13476 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, Visual Page Editor core > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > It seens like the bootstrap profiles are not used by developers. > The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone. > We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms. > Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-11558) Repositories are missing source feature titles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11558: ----------------------------------- Fix Version/s: 4.1.x (was: LATER) > Repositories are missing source feature titles > ---------------------------------------------- > > Key: JBIDE-11558 > URL: https://issues.jboss.org/browse/JBIDE-11558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, UpStream > Affects Versions: 3.3.0.Beta3 > Environment: jbt33beta3-trunk,L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.1.x > > Attachments: empty-list.png, JBIDE-11558_empty_names.png, missing-names.png, missing-titles.png > > > While updating JBT 3.3. trunk there are missing titles in dialog (see screenshot) -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13282) JBT Wiki & build docs need updating

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-13282. ---------------------------------- Resolution: Done > JBT Wiki & build docs need updating > ----------------------------------- > > Key: JBIDE-13282 > URL: https://issues.jboss.org/browse/JBIDE-13282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > These docs need updates / new screenshots: > https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment > https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > http://download.jboss.org/jbosstools/builds/cascade/swimlanes.html (JavaEE (maven) depends on Hibernate) -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13452 at 3/13/13 3:52 AM: ----------------------------------------------------------------- JBDS_VERSION version is already removed JBT_VERSION should be put into aggregate site (it's the only place where it's used), and could even be replaced by the "project.version" of the aggregate pom. TARGET_PLATFORM_VERSION should be kept as we want the default "mvn clean verify" to still work. was (Author: mickael_istria): JBDS_VERSION version is already removed JBT_VERSION should be put into aggregate site (it's the only place where it's used), and could even be replaced by the ${project.version} of the aggregate pom. TARGET_PLATFORM_VERSION should be kept as we want the default "mvn clean verify" to still work. > investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom > ------------------------------------------------------------------------------------------- > > Key: JBIDE-13452 > URL: https://issues.jboss.org/browse/JBIDE-13452 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom > Can we switch to using dynamic maven variables like project.version instead? > Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes). -- 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 month

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