April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14310) generate JIRAs when it's time to bump projects' root poms to point at newer parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14310?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14310: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > generate JIRAs when it's time to bump projects' root poms to point at newer parent pom > -------------------------------------------------------------------------------------- > > Key: JBIDE-14310 > URL: https://issues.jboss.org/browse/JBIDE-14310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > [~maxandersen], please consider spawning a version of this [1] which can be used to JIRA-nag people about the need to update their root poms to the latest parent pom version. > [1] https://github.com/jbosstools/jbosstools-documentation/blob/563b823b98975... -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14310) generate JIRAs when it's time to bump projects' root poms to point at newer parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14310?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14310: --------------------------------------------- I'll prepare script - got a suggestion for what should be put in the description field ? > generate JIRAs when it's time to bump projects' root poms to point at newer parent pom > -------------------------------------------------------------------------------------- > > Key: JBIDE-14310 > URL: https://issues.jboss.org/browse/JBIDE-14310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > [~maxandersen], please consider spawning a version of this [1] which can be used to JIRA-nag people about the need to update their root poms to the latest parent pom version. > [1] https://github.com/jbosstools/jbosstools-documentation/blob/563b823b98975... -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13773) Clean-Up New Context Menu

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13773?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13773: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > Clean-Up New Context Menu > ------------------------- > > Key: JBIDE-13773 > URL: https://issues.jboss.org/browse/JBIDE-13773 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Burr Sutter > Fix For: 4.1.0.Beta1 > > Attachments: Screen Shot 2013-03-12 at 11.52.38 AM.png > > > The New context-menu in the JBoss Perspective has too many options, several of which are not valuable to the average end-user. > Possible Removals: > - Project > - SQL File > - Annotation > - Enum > - Dynamic Web Project > - Enterprise Application Project > - JSP File > - Filter > - Listener > - Servlet > - Decorator > - Interceptor > - Example... -- 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

12 years, 11 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13282: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > 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 > Fix For: 4.1.0.Beta1 > > > 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

12 years, 11 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13282: --------------------------------------------- putting on beta1 since I agree - need to get these things assembled somewhere. My suggestion is to put it in asciidoc on a jbosstools-developerdoc or similar repository. Then it can be edited locally, PR'ed and published anywhere - maybe even just as github pages? > 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 > Fix For: 4.1.0.Beta1 > > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-67) JBDSIS - Add support in Jenkins to promote the zite zip file.

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-67: ------------------------------- Summary: JBDSIS - Add support in Jenkins to promote the zite zip file. Key: JBTIS-67 URL: https://issues.jboss.org/browse/JBTIS-67 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0 Reporter: Paul Leacu Assignee: Paul Leacu Enhance the publich Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publ... to publish the update site zip file as well as the update site itself. (10:01:01 AM) nboldt: pleacu: would expect to see a zip somewhere like in here, next to the unpacked site: http://download.jboss.org/jbosstools/updates/integration/juno/integration... ... (10:08:25 AM) nboldt: pleacu: re: https://issues.jboss.org/browse/JBDS-2556?page=com.atlassian.jira.plugin.... (10:08:27 AM) jbott_rhat: Feature Request: [JBDS-2556] JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip [Open, Major, (central), nickboldt] https://issues.jboss.org/browse/JBDS-2556 ref JBDS-2556: For production of an update site zip for JBDS, we already do that (and put it on the Early Access site). Only thing to do is ensure it's pushed to CSP this time around. For production of a update site zip for JBDS-IS (Integration Stack / SOA-P/BRMS-P Tooling), I believe that's already being done. Paul Leacu can comment if that's not the case. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2486: ---------------------------------- Today, we: * mirror the individual upstream projects on into /updates/requirements/<project> [on dl.jb.org] [283M] * mirror the individual upstream projects on into /updates/requirements/<project> [on www.qa] [283M] * mirror the individual upstream projects on into /updates/requirements/<project> [on ds.jb.com] [283M] * have a composite to combine them into a single site for use by Central [on dl.jb.org] [<0.2M] * have a composite to combine them into a single site for use by Central [on ds.jb.com] [<0.2M] * add only the new content that has changed, eg., when we moved from Extras 4.30.2 to 4.30.3, the only difference was the addition of VJET (47M) Total for 4.30.2: 3 x (283-47) = 708M Total for 4.30.3: 3 x 283 = 849M In future, we would: * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] [283M] * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] [283M] * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] [283M] * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] [283M] * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] [283M] * add a whole new aggregate for old + new content, eg., a new version of GWT will add another 283M each time, not 166M. Total for 4.30.2: 5 x (283-47) = 1180M Total for 4.30.3: 5 x 283 + 1180 = 2595M So... definitely more disk space is being used. But we will end up with an "offline" Central update site zip (minus Android and JRebel, of course) which we can choose to publish if we want to. And we'll know exactly which IUs in the zip and on Central. > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Beta1 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13286) jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13286: ---------------------------------------- Fix Version/s: 4.1.x > jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13286 > URL: https://issues.jboss.org/browse/JBIDE-13286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > Is it possible to pull the git hash value used for a given build, look into github for the matching JIRA #, and drop a comment into the JIRA to the tune of: > "Spinning in <buildURL> >= BUILD_NUMBER" -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13286) jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13286: --------------------------------------------- You would put a comment on every jira mentioned in the change log ? won't that pollute jira very fast ? Another related interest would be to have jenkins kick of builds against pullrequests and report if it makes the build fail or not. > jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13286 > URL: https://issues.jboss.org/browse/JBIDE-13286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > Is it possible to pull the git hash value used for a given build, look into github for the matching JIRA #, and drop a comment into the JIRA to the tune of: > "Spinning in <buildURL> >= BUILD_NUMBER" -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13832) MD5 sometimes not correct

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13832?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13832: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 4.1.0.Beta2 > MD5 sometimes not correct > ------------------------- > > Key: JBIDE-13832 > URL: https://issues.jboss.org/browse/JBIDE-13832 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1, 4.1.0.Beta2 > > > If you look for instance at this repo: http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_... , you'll notice that the .MD5 files contains string that don't match the actual files md5 checksum, which is accurate in the log files (checksum.txt). > This is most likely an issue in the publish script. -- 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

12 years, 11 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