October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15483) generate content in staging/_composite_/core/{trunk, 4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15483?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15483: ---------------------------------------- Component/s: build > generate content in staging/_composite_/core/{trunk,4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1} > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15483 > URL: https://issues.jboss.org/browse/JBIDE-15483 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > Because the content in builds/staging/\{JOB_NAME}/all/repo/ and builds/staging.previous/\{JOB_NAME}/all/repo/ is moving to builds/staging/\{JOB_NAME}/\{BUILD_ID_N} and builds/staging/\{JOB_NAME}/\{BUILD_ID_N-1}, we need to generate a list of matching build URLs for inclusion in the composite*.xml files, perhaps based on a template that's stored in github (to define which projects to include). > Parameters to the generation would need to be: > a) template > b) number of builds per project to include (1, for stable_branch or 2, for trunk) > Constraints: > * Need to ensure that the generated files are always fresher than anything pulled from github via rsync, so templates should not be called "compositeContent.xml" but rather "compositeContent.template.xml" > * Need to be able to run this regeneration as a Jenkins job, perhaps as the first step in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Worries: > * What happens if the regen happens and then a jbosstools-cleanup.sh fires minutes later, wiping out that N-1 build? Does jbosstools-cleaup.sh need to regen these files too? > Default operation of jbosstools-cleanup.sh as called from publish_new.sh and publish.sh is to keep the last 5 builds and anything newer than 5 days old; if there are no such builds, it will always keep the last build in a folder: > {code}./jbosstools-cleanup.sh --keep 5 --age-to-delete 5 --childFolderSuffix /all/repo/{code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15627) ORM Bug Loading Entity with Two ID Properties

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15627?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-15627. --------------------------------------- Resolution: Rejected no worries - closing this as rejected on request of [~gregmoser] > ORM Bug Loading Entity with Two ID Properties > --------------------------------------------- > > Key: JBIDE-15627 > URL: https://issues.jboss.org/browse/JBIDE-15627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Mac OSX, MySQL > Reporter: Greg Moser > > When an entity is defined with two columns as the ID it is able to be saved fine, however whenever an entity is loaded with either entityLoad() or ormExecuteQuery() neither of the properties are populated. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2760) openshift keyword in Eclipse Marketplace

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2760?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2760: -------------------------------------- Component/s: updatesite > openshift keyword in Eclipse Marketplace > ---------------------------------------- > > Key: JBDS-2760 > URL: https://issues.jboss.org/browse/JBDS-2760 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Burr Sutter > > The openshift keyword search should yield results for JBoss Tools & JBoss Developer Studio > http://screencast.com/t/VEn8EdAPT8U -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2780) Welcome page "Show on startup" option is grey

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2780?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2780: -------------------------------------- Component/s: central > Welcome page "Show on startup" option is grey > --------------------------------------------- > > Key: JBDS-2780 > URL: https://issues.jboss.org/browse/JBDS-2780 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.GA > Environment: Kubuntu 64 bits > Reporter: Emmanuel Hugonnet > Priority: Minor > Attachments: jboss_central.png > > > The option "show on startup" is displayed with a grey background instead of the default one. Changing theme doesn't affect it. > 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15482: --------------------------------------------- isn't it pretty easy to distinguish which is what based on wether they have staging.previous or not ? > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12812) Provide user-friendly way to increase Git timeout

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12812?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12812: --------------------------------------------- so sounds like the proper solution is we add a preference for these timeouts and set their default values high allowing users to extend them further if they absolutely must (because their app have much longer startup times etc.) > Provide user-friendly way to increase Git timeout > ------------------------------------------------- > > Key: JBIDE-12812 > URL: https://issues.jboss.org/browse/JBIDE-12812 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: pushtimeout.png > > > With the default timeout (30s) everytime I follow these steps I get an TimoutException: > * Import rich-faces project from JBoss Central > * Create application on OpenShift and merge it with the rich-faces project > * Select the project - context menu - Team - Push to Upstream > * Timeout Exception: > !pushtimeout.png|thumbnail! > So we should provide a link to > {code}Preferences - Team - Git - Remote connection timeout{code} to prevent JBIDE-12430 with some basic explanation of the most probable situation - that the timeout is set too small (like when timed out while creating app). -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15606: --------------------------------------------- About knowing which features will change/stay - that is impossible to know. Base stayed stable in this lastest 4.1.1.1 release. In a next update Base might be the only thing that needs an update - and the rest on top does not/should not need rebuilding just because it has an update/bugfix. Thus I'm not following why you would not want to simply keep each released site. > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15606: --------------------------------------------- Since we are just talking about using these nexus published sites for non-aggregated-releases nexus uptime is more than sufficient. If nexus is down - we can't build the projects anyway. I don't understand why you would like to have a mix of some sites being published and others aggregated directly into the site. Uniformity seems better and unless i'm missing something simpler and faster to do and maintain. About what is pushed I honestly don't see how https://github.com/jbosstools/jbosstools-build-sites/pull/108/files is supposed to work. It just declares an empty directory and a pom that moves/copies a category.xml. i.e. where is the "tool" that is referenced in this jira that actually does the "job" > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15625) Faces-config validation wrongly reports a warning for two renderers with the same renderer-type

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15625?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15625: --------------------------------------------- Is this a regression or new issue ? Sounds like an issue we should fix in 4.1.1 if possible. > Faces-config validation wrongly reports a warning for two renderers with the same renderer-type > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-15625 > URL: https://issues.jboss.org/browse/JBIDE-15625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > > https://community.jboss.org/message/840399?et=watches.email.thread#840399 > Validation should take into account both renderer-type and component-family. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15625) Faces-config validation wrongly reports a warning for two renderers with the same renderer-type

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15625?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15625: ---------------------------------------- Fix Version/s: (was: 4.2.0.Alpha1) > Faces-config validation wrongly reports a warning for two renderers with the same renderer-type > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-15625 > URL: https://issues.jboss.org/browse/JBIDE-15625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > > https://community.jboss.org/message/840399?et=watches.email.thread#840399 > Validation should take into account both renderer-type and component-family. -- 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, 6 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 October 2013