November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18736) create python tooling to create new sprint/milestone targets in JBIDE/JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18736: ---------------------------------- Summary: create python tooling to create new sprint/milestone targets in JBIDE/JBDS Key: JBIDE-18736 URL: https://issues.jboss.org/browse/JBIDE-18736 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.2.0.Final Reporter: Nick Boldt When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. As part of that build, we can now * generate updated Zimbra calendar * generate new PP In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18735) create python tooling to modify JBIDE/JBDS jiras programmatically via commandline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18735?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18735: ------------------------------- Description: We would like a way to be able to change fields associated w/ JIRA versions (description, start/end dates) programmatically via python using the REST api. For example: https://issues.jboss.org/rest/api/2/project/JBDS/versions -> {code} {"self":"https://issues.jboss.org/rest/api/2/version/12322458","id":"12322458","description":"based on JBoss Tools 4.2.0.Final, requires Eclipse 4.4.1 (Luna SR1)","name":"8.0.0.GA","archived":false,"released":false,"releaseDate":"2014-10-22","overdue":true,"userReleaseDate":"22/Oct/14","projectId":12310500} {code} --> version w/ ID = 12322458 https://issues.jboss.org/rest/api/2/version/12322458 Then we can do a PUT to change variables. Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2451 was: We would like a way to be able to change fields associated w/ JIRA versions (description, start/end dates) programmatically via python using the REST api. For example: https://issues.jboss.org/rest/api/2/project/JBDS/versions -> {code} {"self":"https://issues.jboss.org/rest/api/2/version/12322458","id":"12322458","description":"based on JBoss Tools 4.2.0.Final, requires Eclipse 4.4.1 (Luna SR1)","name":"8.0.0.GA","archived":false,"released":false,"releaseDate":"2014-10-22","overdue":true,"userReleaseDate":"22/Oct/14","projectId":12310500} {code} --> version w/ ID = 12322458 https://issues.jboss.org/rest/api/2/version/12322458 Then we can do a PUT to change variables. > create python tooling to modify JBIDE/JBDS jiras programmatically via commandline > --------------------------------------------------------------------------------- > > Key: JBIDE-18735 > URL: https://issues.jboss.org/browse/JBIDE-18735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > We would like a way to be able to change fields associated w/ JIRA versions (description, start/end dates) programmatically via python using the REST api. > For example: > https://issues.jboss.org/rest/api/2/project/JBDS/versions -> {code} > {"self":"https://issues.jboss.org/rest/api/2/version/12322458","id":"12322458","description":"based on JBoss Tools 4.2.0.Final, requires Eclipse 4.4.1 (Luna SR1)","name":"8.0.0.GA","archived":false,"released":false,"releaseDate":"2014-10-22","overdue":true,"userReleaseDate":"22/Oct/14","projectId":12310500} > {code} > --> version w/ ID = 12322458 > https://issues.jboss.org/rest/api/2/version/12322458 > Then we can do a PUT to change variables. > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2451 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18735) create python tooling to modify JBIDE/JBDS jiras programmatically via commandline

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18735: ---------------------------------- Summary: create python tooling to modify JBIDE/JBDS jiras programmatically via commandline Key: JBIDE-18735 URL: https://issues.jboss.org/browse/JBIDE-18735 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.0.Final Reporter: Nick Boldt We would like a way to be able to change fields associated w/ JIRA versions (description, start/end dates) programmatically via python using the REST api. For example: https://issues.jboss.org/rest/api/2/project/JBDS/versions -> {code} {"self":"https://issues.jboss.org/rest/api/2/version/12322458","id":"12322458","description":"based on JBoss Tools 4.2.0.Final, requires Eclipse 4.4.1 (Luna SR1)","name":"8.0.0.GA","archived":false,"released":false,"releaseDate":"2014-10-22","overdue":true,"userReleaseDate":"22/Oct/14","projectId":12310500} {code} --> version w/ ID = 12322458 https://issues.jboss.org/rest/api/2/version/12322458 Then we can do a PUT to change variables. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18595: --------------------------------------------- If we can't reproduce it we got a problem somehow since it fails on SR1 of base eclipse - so why don't it fail for us ? > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 4.2.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18731) Remove deprecated usecase of project archives run externally via ant

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18731?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18731: ---------------------------------------- Component/s: archives > Remove deprecated usecase of project archives run externally via ant > -------------------------------------------------------------------- > > Key: JBIDE-18731 > URL: https://issues.jboss.org/browse/JBIDE-18731 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: archives > Reporter: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > A legacy use case of running a jbt project archives descriptor file as an outside-eclipse build via an ant task should be removed. This would allow for archives.core to be packaged much more simply, following the structure of almost all other plugins. > See also: JBIDE-18008 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17058) Add new widgets to HTML 5.0 Palette

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17058?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17058: --------------------------------------------- Don't know of a good way to ensure that since you can use both in a page and it will be fine. We've talked about making it so that we will show just the type of elements that are actually already used on the page or have used before to reduce the redundancy of components. > Add new widgets to HTML 5.0 Palette > ----------------------------------- > > Key: JBIDE-17058 > URL: https://issues.jboss.org/browse/JBIDE-17058 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.x > > > Now HTML5 has only 5 elements: <form>, <label>, <audio>, <image>, <video>. > However, there are a lot of new elements in HTML 5.0 (http://www.w3schools.com/html/html5_new_elements.asp) <canvas>, <embed>, <datalist>, <keygen>, <output>, <header>, <nav>, <section>, <main>, <article>, <aside>, <footer>, <details>, <summary>, <figure>, <mark>, <time>, <bdi>, <wbr>, <dialog>, <meter>, <progress>. > Besides, some old elements, like <table> also can be added to the palette. > [~burrsutter], [~maxandersen], could you please advise, which elements may be nice to add to the HTML 5.0 palette. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by Nichola Moore (JIRA)

[ https://issues.jboss.org/browse/JBTIS-348?page=com.atlassian.jira.plugin.... ] Nichola Moore commented on JBTIS-348: ------------------------------------- Paul Leacu - I've created a version of the Release Notes using our usual style sheet. I know Michelle uses a specific release notes style sheet so hers looks slightly different, but this has all we need (plus a few bits we don't but I can't get rid of those!). What we need now is to update the JBoss Developer Studio splash page so that the customer can see the link to the release notes. Are the JDBS and JDBSIS releases numbered the same? I'm afraid I can't even send you a link so you can have a look. There's no presence on our stage server to link to. I'll try to work it out on Monday. I'm just letting you know that work is in progress and it's all not too far away! Regards, Nichola > User can not download the release note from Red Hat Customer Portal > ------------------------------------------------------------------- > > Key: JBTIS-348 > URL: https://issues.jboss.org/browse/JBTIS-348 > Project: JBoss Tools Integration Stack > Issue Type: Documentation > Environment: JBDSIS 7.0.3.GA > Reporter: hisao furuichi > Assignee: Paul Leacu > > From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. > [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... > [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... > [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-318) Generate source bundles for IS component features.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-318?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-318: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 1150805|https://bugzilla.redhat.com/show_bug.cgi?id=1150805] from ASSIGNED to MODIFIED > Generate source bundles for IS component features. > -------------------------------------------------- > > Key: JBTIS-318 > URL: https://issues.jboss.org/browse/JBTIS-318 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM > Affects Versions: 8.0.0.Alpha1, 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > jBPM/ Drools must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS. > Courtesy [~nickboldt]: > How to make maven/tycho build source bundles and features: > In the upstream projects: > http://wiki.eclipse.org/Minerva#Source > Then in the aggregator for JBTIS/JBSIS update site: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > As a result, users can install sources from within JBDS rather than > needing a separate source zip with .java files. Way more useful, if > you're a java developer using JBDS/Eclipse. > If you also want to produce a zip of *actual source files* as pulled > from github, I have a script for that, too. > See: > 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources > Produces a zip of the contents of the JBDS product build, so people can > build it offline. Does NOT include upstream sources. > Result: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... > (2.4M) > 2. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > Produces a zip of upstream sources based on upstream project zips. This > is the old approach, since pulling a previously-built zip doesn't 100% > guarantee you're getting the correct version AND it requires that the > upstream project produce a source zip. > -OR- > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Fetches sources directly from github based on the source-reference in > the specified plugins' manifest.mf files, then collates those sources > into a single zip. > Results: > http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al... > (35M) > Ref: > (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide. > (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct? > (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it. > (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that > (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience. > (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles > (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources > (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized" > (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu ) > Components that generate source bundles: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > Some that don't: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-332) Generate source bundles for IS component features - bpmn2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-332?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-332: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 1150805|https://bugzilla.redhat.com/show_bug.cgi?id=1150805] from ASSIGNED to MODIFIED > Generate source bundles for IS component features - bpmn2 > --------------------------------------------------------- > > Key: JBTIS-332 > URL: https://issues.jboss.org/browse/JBTIS-332 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2 > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > > I have the fix for this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-318) Generate source bundles for IS component features.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-318?page=com.atlassian.jira.plugin.... ] Kris Verlaenen commented on JBTIS-318: -------------------------------------- Fixed by https://github.com/droolsjbpm/droolsjbpm-tools/commit/156de8ab39f9953b4c3... > Generate source bundles for IS component features. > -------------------------------------------------- > > Key: JBTIS-318 > URL: https://issues.jboss.org/browse/JBTIS-318 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM > Affects Versions: 8.0.0.Alpha1, 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > jBPM/ Drools must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS. > Courtesy [~nickboldt]: > How to make maven/tycho build source bundles and features: > In the upstream projects: > http://wiki.eclipse.org/Minerva#Source > Then in the aggregator for JBTIS/JBSIS update site: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > As a result, users can install sources from within JBDS rather than > needing a separate source zip with .java files. Way more useful, if > you're a java developer using JBDS/Eclipse. > If you also want to produce a zip of *actual source files* as pulled > from github, I have a script for that, too. > See: > 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources > Produces a zip of the contents of the JBDS product build, so people can > build it offline. Does NOT include upstream sources. > Result: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... > (2.4M) > 2. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > Produces a zip of upstream sources based on upstream project zips. This > is the old approach, since pulling a previously-built zip doesn't 100% > guarantee you're getting the correct version AND it requires that the > upstream project produce a source zip. > -OR- > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Fetches sources directly from github based on the source-reference in > the specified plugins' manifest.mf files, then collates those sources > into a single zip. > Results: > http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al... > (35M) > Ref: > (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide. > (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct? > (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it. > (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that > (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience. > (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles > (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources > (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized" > (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu ) > Components that generate source bundles: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > Some that don't: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014