January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10230) Plugins are missing Description

by Aslak Knutsen (Created) (JIRA)

Plugins are missing Description ------------------------------- Key: JBIDE-10230 URL: https://issues.jboss.org/browse/JBIDE-10230 Project: Tools (JBoss Tools) Issue Type: Bug Components: Cleanup Affects Versions: 3.3.0.M4 Reporter: Aslak Knutsen Assignee: Max Rydahl Andersen Using the Plugin name as description is not very informative Plugins missing proper Description: * Context and Dependency Injection Tools * JBoss Central * JBoss JAX-RS Tools * JBoss Portlet * JBoss Runtime AS Detector * JBoss Runtime Detector Core * JBoss Runtime Seam Detector * JBoss Tools Community Project Examples * JBoss Tools Java Standard Tools * JBoss Tools JSF * JBoss Tools Usage Reporting * JBoss WebServices Tools * Project Examples * Seam 3 Tools * Struts Tools * JBoss GWT Integration (Experimental) * JBoss Tools Community Project Examples * JBoss BIRT Integration * Deltacloud Development Tools (Experimental) * JBoss Maven CDI Configurator * JBoss Maven Hibernate Configurator * JBoss Maven JAX-RS Configurator * JBoss Maven JSF Configurator * JBoss Maven Portlet Configurator * JBoss Maven Seam Integration * JBoss Maven Integration * JBoss WebServices Tools Plugins with poor description: * Seam 2 Tools * JBoss AS Tools Server / EGit integration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
10
0 / 0

[JBoss JIRA] (JBIDE-10712) When creating a domain, the openshift-java-client is not waiting for the domain to get propagated

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10712: ---------------------------------------- Summary: When creating a domain, the openshift-java-client is not waiting for the domain to get propagated Key: JBIDE-10712 URL: https://issues.jboss.org/browse/JBIDE-10712 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta2 The rhc-tooling is waiting for the namespace to propagate when it creates a domain: https://github.com/openshift/os-client-tools/blob/master/express/bin/rhc-... {code} if !app_info.empty? && opt['namespace'] != user_info['user_info']['namespace'] # # Confirm that the host(s) exist in DNS # puts "Now your new domain name(s) are being propagated worldwide (this might take a minute)..." # Allow DNS to propogate sleep 15 app_info.each_key do |appname| fqdn = "#{appname}-#{opt['namespace']}.#{user_info['user_info']['rhc_domain']}" # Now start checking for DNS loop = 0 sleep_time = 2 while loop < RHC::MAX_RETRIES && !RHC::hostexist?(fqdn) sleep sleep_time loop+=1 puts " retry # #{loop} - Waiting for DNS: #{fqdn}" sleep_time = RHC::delay(sleep_time) end if loop >= RHC::MAX_RETRIES puts "Host could not be found: #{fqdn}" dns_success = false end end puts "You can use rhc-domain-info to view any url changes. Be sure to update any links" puts "including the url in your local git config: <local_git_repo>/.git/config" end if dns_success puts "Alteration successful." else puts "Alteration successful but at least one of the urls is still updating in DNS." end puts "" {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] (JBIDE-10624) Implement 'force push' in EgitUtils

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-10624: ----------------------------------- Summary: Implement 'force push' in EgitUtils Key: JBIDE-10624 URL: https://issues.jboss.org/browse/JBIDE-10624 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Inside EgitUtils, the method signatures for push have been changed to support a "force" flag. However the guts of the method have not been modified to respect this parameter. private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException { -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] (JBIDE-10664) Cannot deploy GWT project to OpenShift: SSH key problems

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10664: ---------------------------------------- Summary: Cannot deploy GWT project to OpenShift: SSH key problems Key: JBIDE-10664 URL: https://issues.jboss.org/browse/JBIDE-10664 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
13
0 / 0

[JBoss JIRA] (JBIDE-10719) WizardUtils#runInWizard returns a Future<IStatus> but is process synchronously (not asynchronously as the signature would suggest)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10719: ---------------------------------------- Summary: WizardUtils#runInWizard returns a Future<IStatus> but is process synchronously (not asynchronously as the signature would suggest) Key: JBIDE-10719 URL: https://issues.jboss.org/browse/JBIDE-10719 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 WizardUtils#runInWizard is returning a Future<IStatus> as if the method would not wait for it's job to get finished. This is actually not the case. The job is joined and the method is only returning when the job was executed. {code} public static Future<IStatus> runInWizard(final Job job, final DelegatingProgressMonitor delegatingMonitor, IWizardContainer container) throws InvocationTargetException, InterruptedException { JobResultFuture future = new JobResultFuture(job); container.run(true, false, new IRunnableWithProgress() { @Override public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException if (delegatingMonitor == null) { monitor.beginTask(job.getName(), IProgressMonitor.UNKNOWN); } else { delegatingMonitor.add(monitor); delegatingMonitor.beginTask(job.getName(), IProgressMonitor.UNKNOWN); } job.schedule(); job.join(); if (delegatingMonitor == null) { monitor.done(); } else { delegatingMonitor.done(); } } }); return future; } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBIDE-10289) create composite reqs site for Indigo SR2

by Nick Boldt (Created) (JIRA)

create composite reqs site for Indigo SR2 ----------------------------------------- Key: JBIDE-10289 URL: https://issues.jboss.org/browse/JBIDE-10289 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite, UpStream Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 Need to pull a new SR2 update site from maintenance bits to facilitate testing. http://download.eclipse.org/releases/maintenance/ --> http://download.jboss.org/jbosstools/updates/indigo/SR2/, http://download.jboss.org/jbosstools/updates/indigo/extras/SR2/ Prolly need to spin new jobs w/ new parameters passed in to permit creating differently-named TPs. http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platform -> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/ http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.target-platform -> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in... http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.target... -> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/ http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.target-... -> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in... And need to fix linkages in Hudson so that component and aggregate jobs depend on stable_branch or trunk as appropriate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
11
0 / 0

[JBoss JIRA] (JBIDE-10670) JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10670: ---------------------------------- Summary: JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build Key: JBIDE-10670 URL: https://issues.jboss.org/browse/JBIDE-10670 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1 Currently, SOA Tooling aggregate build for JBT builds based on upstream components and also duplicates some content in JBT Core (see JBDS-1993). In future, we should make the JBT SOA Tooling aggregate build simply reuse content from the upstream JBT Core aggregate build. 1. link Jenkins jobs so Core causes SOA to fire 2. remove common components like Runtime and Usage from build/soa-site/site.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
13
0 / 0

[JBoss JIRA] (JBIDE-10607) Cannot import application if I previously killed and recreated it

by Andre Dietisheim (Created) (JIRA)

Cannot import application if I previously killed and recreated it ----------------------------------------------------------------- Key: JBIDE-10607 URL: https://issues.jboss.org/browse/JBIDE-10607 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
13
0 / 0

[JBoss JIRA] (JBIDE-10647) document how to switch between branches when building JBT locally

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10647: ---------------------------------- Summary: document how to switch between branches when building JBT locally Key: JBIDE-10647 URL: https://issues.jboss.org/browse/JBIDE-10647 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 (2012-01-16 12:09:33) maxandersen: nboldt: if I build parent and say jmx from trunk, then switch to branch it will pick that up if i'm not rebuilding everything. 12:10 (2012-01-16 12:10:11) nboldt: ah, true (2012-01-16 12:10:32) nboldt: but that's an osgi issue (2012-01-16 12:11:36) nboldt: eg., if tycho sees locally jmx_3.3.0.....Beta1 (built from trunk) and you switch to branch and rebuild something that needs jmx, it'll look at staging/_composite_/3.3.indigo/ site for a newer version of jmx (with M5 suffix) and compare that to your locally-build version (2012-01-16 12:12:09) nboldt: I can't solve that w/ diffferent parent poms in nexus, even if they're differently versioned 3.3.M5 vs. 3.3.trunk (2012-01-16 12:12:21) nboldt: instead of both having 0.0.3-SNAPSHOT (2012-01-16 12:13:03) nboldt: the problem there is that your ~/.m2 cache contains a newer version of the plugin/feature than what's on the site from which upstream bits are sourced, so Tycho picks the local bits (and throws a warning in your build log) (2012-01-16 12:13:25) maxandersen: that is not happening when building full via mvn - then it uses the local ones over the remote ones. (2012-01-16 12:13:33) nboldt: so, yes, in that scenario, you DO have to nuke the ~/.m2 folder (or better, move it so you can have two versions of the ~/.m2 cache for trunk vs. branch) (2012-01-16 12:13:58) nboldt: maxandersen: of course, because you asked it to rebuild locally from source rather than resolving from binary) (2012-01-16 12:14:34) nboldt: so there are two workarounds to the "multiple component build dependencies across branch/trunk" -- a) have two different ~/.m2 caches and switch them as you switch parent poms (2012-01-16 12:14:50) nboldt: b) rebuild everything locally when you switch branches 12:15 (2012-01-16 12:15:23) nboldt: I feel like this should be documented somewhere -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBIDE-10671) [performance tuning] create separate jbosstools-nightly-staging-composite site for SOA Tooling

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10671: ---------------------------------- Summary: [performance tuning] create separate jbosstools-nightly-staging-composite site for SOA Tooling Key: JBIDE-10671 URL: https://issues.jboss.org/browse/JBIDE-10671 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1 To speed up SOA Tooling aggregate build, source from a new URL instead of http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no metadata for content that will ultimately not be included in the site will be downloaded -- only metadata for staged SOA nightlies will be read/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
10
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 January 2012