July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-14610 at 7/15/15 2:54 PM: ------------------------------------------------------------- JBIDE-18846 (was JBIDE-18236, which is a dupe) is the issue we got about how best find builds etc. for modules. [edited by Nick to link to correct associated JIRA, not the dupe/closed one] was (Author: maxandersen): https://issues.jboss.org/browse/JBIDE-18236 is the issue we got about how best find builds etc. for modules. > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: documentation > Fix For: 4.3.0.CR1 > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14610: ------------------------------- Priority: Major (was: Blocker) > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: documentation > Fix For: 4.3.0.CR1 > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20272) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20272?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20272. ------------------------------ Assignee: Nick Boldt Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20272 > URL: https://issues.jboss.org/browse/JBIDE-20272 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20211) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Freemarker]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20211?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20211: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.CR1) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Freemarker] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20211 > URL: https://issues.jboss.org/browse/JBIDE-20211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [Freemarker]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20269) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20269?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20269. ------------------------------ Assignee: Nick Boldt Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central Discovery] > --------------------------------------------------------------- > > Key: JBIDE-20269 > URL: https://issues.jboss.org/browse/JBIDE-20269 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: discovery > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Central Discovery]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3483) For JBDS 9.0.0.Beta2: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3483?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3483. ---------------------------- Resolution: Done > For JBDS 9.0.0.Beta2: Code Freeze + Branch > ------------------------------------------ > > Key: JBDS-3483 > URL: https://issues.jboss.org/browse/JBDS-3483 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 9.0.0.Beta2 > > > For JBDS 9.0.0.Beta2: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20284) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20284?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20284: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian] > -------------------------------------------------------- > > Key: JBIDE-20284 > URL: https://issues.jboss.org/browse/JBIDE-20284 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Arquillian]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20147) Batch Property mapping issue with reference

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20147?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20147: ----------------------------------------------- Fixed - https://github.com/jbosstools/jbosstools-javaee/pull/362 Alexey, is it possible to merge it to Beta2? > Batch Property mapping issue with reference > ------------------------------------------- > > Key: JBIDE-20147 > URL: https://issues.jboss.org/browse/JBIDE-20147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Environment: Mars > Tools 4.3.0 Beta1 > Reporter: Cody Lerum > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > After upgrading to Mars and JBT I started getting a validation warning on my batch configuration > If I have the following I get an error {{Property "INVOICE_JOB_ID" is not found in artifact "invoiceCreateBatchlet" and is not used in other properties.}} > {code} > @Inject > @BatchProperty(name = InvoiceCreatePartitionMapper.INVOICE_JOB_ID_KEY) > private String invoiceJobId; > {code} > In a different class > {code} > public static final String INVOICE_JOB_ID_KEY = "INVOICE_JOB_ID"; > {code} > However if have the following there is no warning. > {code} > @Inject > @BatchProperty(name = "INVOICE_JOB_ID") > private String invoiceJobId; > {code} > It appears that the validation logic cannot follow the reference -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20281) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Birt]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20281?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20281: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Birt] > -------------------------------------------------- > > Key: JBIDE-20281 > URL: https://issues.jboss.org/browse/JBIDE-20281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Birt]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20261) Need to create features for JavaScript tools (org.jboss.tools.jst.js)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20261?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20261: ------------------------------------ {quote}[2:24:54 PM] Nick Boldt: so this is only for JBoss Tools? [2:25:33 PM] Denis Golovin: for now - yes, if QA says it works, it goes to jbds also {quote} > Need to create features for JavaScript tools (org.jboss.tools.jst.js) > --------------------------------------------------------------------- > > Key: JBIDE-20261 > URL: https://issues.jboss.org/browse/JBIDE-20261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.Beta1 > Reporter: Ilya Buziuk > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > > There is no proper feature infrastructure for JavaScript Tools (org.jboss.tools.jst.js plugin) in jbosstools-jst -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 July 2015