February 2013 - jbosstools-issues

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13282: ------------------------------------ These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > 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 > > https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 needs updating -- 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-13282) JBT Wiki build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Description: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 was:https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 needs updating > 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 -- 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-13282) JBT Wiki build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Comment: was deleted (was: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3) > 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 -- 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-13282) JBT Wiki & build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Summary: JBT Wiki & build docs need updating (was: JBT Wiki build docs need updating) > 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 -- 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-13282) JBT Wiki build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Description: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 was: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > 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 -- 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-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11065: ---------------------------------------- The Mojo needs to support a statUrl as well. > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha1 > > Attachments: jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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-13463) Replace eclipse-update-site for aggregator by eclipse-repository

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13463?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13463: ---------------------------------------- Looks like post-build steps perform a "fetchZip" in build.xml. Need to verify whether this can be applied to eclipse-repository. > Replace eclipse-update-site for aggregator by eclipse-repository > ---------------------------------------------------------------- > > Key: JBIDE-13463 > URL: https://issues.jboss.org/browse/JBIDE-13463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > The "eclipse-update-site" packaging type we've been using for aggregate sites is deprecated. Moreover it now shows some limitations (doesn't support pack.gz and other new Tycho stuff) that make it worth migrating to "eclipse-repository". -- 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-13316) Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13316 at 2/1/13 12:38 PM: ------------------------------------------------------------- +1, this looks like a solution to this jira and to JBIDE-13408, too: a) push to staging automatically by CI build b) then get someone w/ access to push from staging to production (manually). Ref: https://community.jboss.org/wiki/MavenDeployingARelease was (Author: nickboldt): +1, this looks like a solution to JBIDE-13408. > Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) > ------------------------------------------------------------------------------------ > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13408: ------------------------------------ @mistria proposes this change: https://github.com/mickaelistria/jbosstools-target-platforms/commit/2f62a... which looks like a reasonable solution to this issue. Therefore new workflow for publishing non-SNAPSHOT stuff to JBoss Nexus is: a) push to staging automatically by CI build b) then get someone w/ access to push from staging to production (manually). Ref: https://community.jboss.org/wiki/MavenDeployingARelease > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {quote} -- 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-13316) Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13316: ------------------------------------ +1, this looks like a solution to JBIDE-13408. > Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) > ------------------------------------------------------------------------------------ > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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 February 2013