January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16388) Cordovasim does not use the Hybrid Mobile project's start page

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-16388: --------------------------------------- Summary: Cordovasim does not use the Hybrid Mobile project's start page Key: JBIDE-16388 URL: https://issues.jboss.org/browse/JBIDE-16388 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Final Reporter: Vineet Reynolds When I run a Hybrid Mobile project under CordovaSim, it does not use the start page defined in {{config.xml}}. If the application were to use a different application start page, say {{mobileapp.html}} in {{config.xml}}, CordovaSim reports the following error: http://www.screencast.com/t/8odNCS5FWK I'm forced to create a new runtime configuration that explicitly defines the start page again. This is not necessary for running under the Android emulator or device, and is a problem only under CordovaSim. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16377) Application wizard: wizard selects wrong existing application if I import from Explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16377?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16377: ------------------------------------- Assignee: Andre Dietisheim > Application wizard: wizard selects wrong existing application if I import from Explorer > --------------------------------------------------------------------------------------- > > Key: JBIDE-16377 > URL: https://issues.jboss.org/browse/JBIDE-16377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha2 > > Attachments: existing-application.png, import-application.png > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16286: ------------------------------------------ [~akazakov] RSE servers? If there any then they're of no use, just ignore them. > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, maven > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: performance > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16384) Unable to start JBoss AS 7.1 in Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16384?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16384: --------------------------------------------- Eclipse Indigo is 3 year old version of eclipse - JBoss 7 was just a tech preview launch at that time - I recommend you install latest JBoss Tools running on Kepler instead. That said, please try creating the JBoss AS 7 server in a new workspace to see if that fixes it (the issue seem to be some broken configuration that should go away if the server AND its runtime part is recreated) > Unable to start JBoss AS 7.1 in Eclipse > --------------------------------------- > > Key: JBIDE-16384 > URL: https://issues.jboss.org/browse/JBIDE-16384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows 7 > Reporter: Akshay Ballarpure > > Hello, > I am not able to start JBoss AS 7.1 in Eclipse Indigo (version 7.x). The error message is shown below. Can someone please help ? > An internal error occurred during: "Starting JBoss 7.1 Runtime Server". > classToLaunch cannot be null > Regards, > Akshay -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16384) Unable to start JBoss AS 7.1 in Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16384?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-16384. --------------------------------------- Resolution: Rejected please use jboss tools forum (https://community.jboss.org/en/tools) for user questions before opening bugs. Thank you. > Unable to start JBoss AS 7.1 in Eclipse > --------------------------------------- > > Key: JBIDE-16384 > URL: https://issues.jboss.org/browse/JBIDE-16384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows 7 > Reporter: Akshay Ballarpure > > Hello, > I am not able to start JBoss AS 7.1 in Eclipse Indigo (version 7.x). The error message is shown below. Can someone please help ? > An internal error occurred during: "Starting JBoss 7.1 Runtime Server". > classToLaunch cannot be null > Regards, > Akshay -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2635: ------------------------------------------- [~nickboldt] no, we are not going to install our plugins/features into dropins. Dropins are not possible for p2 to fully manage (i.e. it will not get garbage collected when you have plugins nothing is using anymore) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16355: --------------------------------------------- red.ht is made by using bit.ly to reference redhat.com urls. > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3113) Consolidation/clean up of preference pages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3113?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-3113: -------------------------------------------- [~mickael_istria] it does not help to just add it to the target-platform if the plugin does not have a dependency to a plugin it does not matter. > Consolidation/clean up of preference pages > ------------------------------------------ > > Key: JBIDE-3113 > URL: https://issues.jboss.org/browse/JBIDE-3113 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, drools, jbpm > Affects Versions: 3.0.0.cr1 > Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk > Reporter: John Graham > Assignee: Kris Verlaenen > Priority: Critical > Labels: usability > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > JBT currently has three preference page categories: > 1. Drools > 2. JBoss jBPM > 3. JBoss Tools > The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: > - JBoss > -- Drools > -- jBPM > Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-235) Feature request - include summary on-line help for all Integration Stack components supported in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-235?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-235: ------------------------------------------- JBIDE-2032 talks about at least providing a help context id for various plugins which a separate documentation plugin could provide the links for. That might be a nice short term fix/improvement. > Feature request - include summary on-line help for all Integration Stack components supported in JBDS > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-235 > URL: https://issues.jboss.org/browse/JBTIS-235 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Len DiMaggio > Assignee: Paul Leacu > > Teiid Designer is packaged with (12MB of) on-line help. Other projects (jBPM, Drools, ESB) do not have similar on-line help in JBDS. > This feature request is to add simplified Eclipse Help contribution for each project/feature. This could take the form of a summary/outline page which can include the JBoss HTTP site for docs. The help dialog could treat these pages as if they were local. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2877) Upgrade to use izpack 5

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2877: ----------------------------------------- Summary: Upgrade to use izpack 5 Key: JBDS-2877 URL: https://issues.jboss.org/browse/JBDS-2877 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: installer Reporter: Max Rydahl Andersen -- 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, 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 January 2014