May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14417) Project Archives affects deletion event

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14417?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič updated JBIDE-14417: -------------------------------------- Steps to Reproduce: STEP: create simple java project and try to delete it (via menu or del key) ASSERT: Dialog with title "Delete Resources" is correctly invoked, project can be deleted with the provided dialog STEP: add project archives support into project STEP: click on project archives explorer treeitem in project explorer view - very IMPORTANT STEP STEP: invoke deletion event on project (via menu or del key) FAIL: dialog "Delete selected nodes" is invoked, after pressing OK button, nothing happens was: STEP: create simple java project and try to delete it (via menu or del key) ASSERT: Dialog with title "Delete Resources" is correctly invoked, project can be deleted with the provided dialog STEP: add project archives support into project STEP: click on project archives explorer treeitem in project explorer view STEP: invoke deletion event on project (via menu or del key) FAIL: dialog "Delete selected nodes" is invoked, after pressing OK button, nothing happens > Project Archives affects deletion event > --------------------------------------- > > Key: JBIDE-14417 > URL: https://issues.jboss.org/browse/JBIDE-14417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Priority: Critical > Fix For: 4.1.x > > -- 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-14417) Project Archives affects deletion event

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-14417: ----------------------------------------- Summary: Project Archives affects deletion event Key: JBIDE-14417 URL: https://issues.jboss.org/browse/JBIDE-14417 Project: Tools (JBoss Tools) Issue Type: Bug Components: archives Affects Versions: 4.1.0.Beta1 Reporter: Jaroslav Jankovič Priority: Critical Fix For: 4.1.x -- 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-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13977: ---------------------------------------- Isn't there a way to fetch .pack.gz files from remote repo while mirroring repo instead of re-packing locally? Which repositories show this error? Although Tycho can be configured to ignore md5 issue, it's not possible in IDE, so this change ends in IDE with slower resolution (instead of downloading *.jar, IDE first gets *.jar.pack.gz, checks signature, which is wrong, and then downloads pack). > updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13977 > URL: https://issues.jboss.org/browse/JBIDE-13977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform, updatesite, upstream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from Eclipse.org and other places should be updated to generate .pack.gz artifacts too. > {code}<p2.process.artifacts pack="true" repositoryPath="file:/${repoDirLocation}" />{code} > Refs: > * http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.... > * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.... -- 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] (TOOLSDOC-321) NeedInfo: Why might users want to change the order of navigation rules or managed beans?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-321?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-321: ------------------------------------- Summary: NeedInfo: Why might users want to change the order of navigation rules or managed beans? (was: NeedInfo: Why might users want to change the order of navigation rules?) > NeedInfo: Why might users want to change the order of navigation rules or managed beans? > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-321 > URL: https://issues.jboss.org/browse/TOOLSDOC-321 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JSF Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Alexey Kazakov > Attachments: JSF_UpDownRules.png > > > Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. > Why might a user need this function? When would they need to use it? > Similarly, why might a user want to change the order of the managed beans? -- 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] (TOOLSDOC-321) NeedInfo: Why might users want to change the order of navigation rules?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-321?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-321: ------------------------------------- Description: Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. Why might a user need this function? When would they need to use it? Similarly, why might a user want to change the order of the managed beans? was: Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. Why might a user need this function? When would they need to use it? > NeedInfo: Why might users want to change the order of navigation rules? > ----------------------------------------------------------------------- > > Key: TOOLSDOC-321 > URL: https://issues.jboss.org/browse/TOOLSDOC-321 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JSF Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Alexey Kazakov > Attachments: JSF_UpDownRules.png > > > Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. > Why might a user need this function? When would they need to use it? > Similarly, why might a user want to change the order of the managed beans? -- 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-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13977: ------------------------------------ new FAQ entry "How do I ignore MD5sum checks when resolving dependencies or building?" added to https://community.jboss.org/wiki/HowToBuildJBossTools41FAQ: {quote} If for some reason the site against which you're buidling has invalid metadata (perhaps because the site's IUs were pack200'd AFTER the artifacts.xml / content.xml metadata was created) you may get errors like "MD5 hash is not as expected". To ignore these errors, simply build like this: {code}mvn install -Declipse.p2.MD5ArtifactCheck=false -Declipse.p2.MD5Check=false{code} {quote} Meanwhile, still regenerating packed artifacts and then metadata for Kepler site. All others have been fixed (I hope). > updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13977 > URL: https://issues.jboss.org/browse/JBIDE-13977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform, updatesite, upstream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from Eclipse.org and other places should be updated to generate .pack.gz artifacts too. > {code}<p2.process.artifacts pack="true" repositoryPath="file:/${repoDirLocation}" />{code} > Refs: > * http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.... > * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.... -- 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-11348) Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11348?page=com.atlassian.jira.plugi... ] Joseph Hwang resolved JBIDE-11348. ---------------------------------- Resolution: Done > Not generate clientsample codes in user-created folder on JBoss web services, only in src folder. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-11348 > URL: https://issues.jboss.org/browse/JBIDE-11348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.0.M5 > Environment: Eclipse Indigo 3.7.2, JBossTools 3.3 > Reporter: Joseph Hwang > Assignee: Brian Fitzpatrick > Priority: Minor > Fix For: 4.0.x > > Attachments: 1_buildpath.jpg, 2_no_folder_choice.jpg, 3_generate_user_defined_folder.jpg, 4_choose_user_defined_folder.jpg, 5_generate_ws_client_code.jpg, 6_no_client_sample.jpg, 7_choose_src_folder.jpg, client_2.jpg, client_3.jpg, client_4.jpg, generating_client.doc, HelloWorld.zip, readme_pls.docx > > > Web Services deployment is ok! But generating clientsample codes is failed in user-created folder. > clientsample codes is generated only in default 'src' folder. > Pls, check this thread https://community.jboss.org/thread/196669?start=0&tstart=0 . -- 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-2625) Provide on-line installer launchable via JNLP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2625?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2625: -------------------------------- Fix Version/s: 8.0.x > Provide on-line installer launchable via JNLP > --------------------------------------------- > > Key: JBDS-2625 > URL: https://issues.jboss.org/browse/JBDS-2625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.x > > > Instead of always downloading offline installer and then run installation manually, would be good to have online version of installer that would let: > # start installer via JNLP > # select if EAP/WildFly should be installed too > (1) Should be easy to implement, because it requires only excluding update site bits from jar, provide URL for update site and create JNLP configuration; > (2) Requires EAP download integration into IzPack (would be good if IzPack has supported online installation itself) -- 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-14411) Internal interface constant used by seam tests

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14411?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14411: ----------------------------------- Component/s: runtime-detection > Internal interface constant used by seam tests > ---------------------------------------------- > > Key: JBIDE-14411 > URL: https://issues.jboss.org/browse/JBIDE-14411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, Seam 2 > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta1 > > > It seems you're pulling a string "EAP" from an interface which was not meant to be public. > It'd be better to use JBossServerType.EAP.getId() instead. > org.jboss.tools.runtime.seam.detector.test/src/org/jboss/tools/runtime/seam/detector/test/SeamRuntimeDetectionTest.java:import org.jboss.ide.eclipse.as.core.runtime.IJBossRuntimePluginConstants -- 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-14363) Creation of 'core' component in base

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14363: ------------------------------------- Ok, so Denis thinks we need a name other than 'core', which makes sense. Proposing these names: base: org.jboss.tools.base.wtp.ui frameworks: org.jboss.tools.frameworks.wtp.ui util / utilities: org.jboss.tools.util.wtp.ui bedrock: org.jboss.tools.bedrock.wtp.ui basis: org.jboss.tools.basis.wtp.ui backbone: org.jboss.tools.backbone.wtp.ui ground: org.jboss.tools.ground.wtp.ui foundation: org.jboss.tools.foundation.wtp.ui tfc (tools foundation classes): org.jboss.tools.tcf.wtp.ui nucleus: org.jboss.tools.nucleus.wtp.ui atom: org.jboss.tools.atom.wtp.ui hub: org.jboss.tools.hub.wtp.ui crux: org.jboss.tools.crux.wtp.ui cadre: org.jboss.tools.cadre.wtp.ui boson: org.jboss.tools.boson.wtp.ui I'm sure there may be others. I do undertand denis' complaint, though, and we should find a good name for it. > Creation of 'core' component in base > ------------------------------------ > > Key: JBIDE-14363 > URL: https://issues.jboss.org/browse/JBIDE-14363 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements: > 1) Only code designed for re-use can live there > 2) Only fully and properly java-doc'd code can live there > 3) Only code for use by TWO OR MORE components can live there. > 4) Addition of dependencies for this component will be strictly regulated > 5) Code must be properly tested and have tests cases demonstrating it. > 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example: > {code} > org.jboss.tools.core.platform > org.jboss.tools.core.platform.ui > org.jboss.tools.core.wtp > org.jboss.tools.core.wtp.ui > {code} > Bundles such as these would require test bundles, as well as features that keep them separate. > {code} > org.jboss.tools.core.platform.feature > org.jboss.tools.core.wtp.feature > {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, 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 May 2013