October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-182) Publish to ModeShape: Finish Button Disabled

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/JBTIS-182?page=com.atlassian.jira.plugin.... ] Dan Florian updated JBTIS-182: ------------------------------ Issue Type: Bug (was: Feature Request) A workaround exists: After creating the publish area, reselect either the workspace or repository combo selections. This will then enable the "Finish" button and allow publishing of the resources. > Publish to ModeShape: Finish Button Disabled > -------------------------------------------- > > Key: JBTIS-182 > URL: https://issues.jboss.org/browse/JBTIS-182 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 4.1.3 > Environment: JBDS 7.0.0.GA, JBoss Tools 4.1.3.Beta3, EAP 6.1 (in DV 6.0.0) > Reporter: Lucie Fabrikova > Assignee: Dan Florian > Attachments: modeshape.png > > > If no publish area is created, it cannot be created in dialog "Publish to ModeShape", via rght-click Modeshape->Publish. > 1. start EAP 6.1 server > 2. create new Modeshape server (http://localhost:8080/modeshape-rest, admin/admin) > 3. rght-click a project, Modeshape -> Publish > 4. dialog "Publish to ModeShape" appears, with warning "A publish area must be selected. If there aren't any to choose from, you can create one here or in the ModeShape View" > 5. click to add new Publish Area > 6. button "Finish" is still disabled -- 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-2790) "JBoss Tools" themes should not be part of JBDS

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2790: ----------------------------------------- Summary: "JBoss Tools" themes should not be part of JBDS Key: JBDS-2790 URL: https://issues.jboss.org/browse/JBDS-2790 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 7.0.1.GA, 6.0.1.GA Reporter: Max Rydahl Andersen Assignee: Mickael Istria "JBoss Tools" themes seem to be included in JBDS even though JBDS-2631 was rejected and not supposed to be included. Now users are reporting issues on them in JBDS-2781 and JBDS-2782 we'll need to decide what to with them. My suggestion is we remove them in JBDS 8 and if a missing theme does not affect a user having already used these themes I suggest we remove them in JBDS 7.1 too. Thus setting suggested release target to 7.1 but if investigation shows it will hurt update path then at least remove them in 8.0. WDYT ? -- 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-2790) "JBoss Tools" themes should not be part of JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2790?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2790: ----------------------------- CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > "JBoss Tools" themes should not be part of JBDS > ----------------------------------------------- > > Key: JBDS-2790 > URL: https://issues.jboss.org/browse/JBDS-2790 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA, 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > "JBoss Tools" themes seem to be included in JBDS even though JBDS-2631 was rejected and not supposed to be included. > Now users are reporting issues on them in JBDS-2781 and JBDS-2782 we'll need to decide what to with them. > My suggestion is we remove them in JBDS 8 and if a missing theme does not affect a user having already used these themes I suggest we remove them in JBDS 7.1 too. > Thus setting suggested release target to 7.1 but if investigation shows it will hurt update path then at least remove them in 8.0. > WDYT ? -- 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-2789) ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2789?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-2789. --------------------------------------- Resolution: Done > ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0 > ----------------------------------------------------------------------- > > Key: JBDS-2789 > URL: https://issues.jboss.org/browse/JBDS-2789 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.1.GA > > Attachments: 15509_JBDS701.CR2-installed.png, 15509_JBDS701.CR2.png > > > Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1, so when you update using the 7.0.1.CR1 site, you get this: > !https://issues.jboss.org/secure/attachment/12364790/12364790_15509_JBDS701.CR1.png! > {code} > $➔ find . -name com.jboss.jbds.all\* > ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4 > ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364 > {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] (JBDS-2789) ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2789?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2789: -------------------------------------- Component/s: build > ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0 > ----------------------------------------------------------------------- > > Key: JBDS-2789 > URL: https://issues.jboss.org/browse/JBDS-2789 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.1.GA > > Attachments: 15509_JBDS701.CR2-installed.png, 15509_JBDS701.CR2.png > > > Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1, so when you update using the 7.0.1.CR1 site, you get this: > !https://issues.jboss.org/secure/attachment/12364790/12364790_15509_JBDS701.CR1.png! > {code} > $➔ find . -name com.jboss.jbds.all\* > ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4 > ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364 > {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] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2555: -------------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip > ---------------------------------------------------------------------------- > > Key: JBDS-2555 > URL: https://issues.jboss.org/browse/JBDS-2555 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, updatesite > Reporter: Jiri Pallich > Fix For: 7.1.0.Beta1 > > > Offline Usage of JBoss Central (Customers without or very slow Internet access) > On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline). > Related to: https://issues.jboss.org/browse/JBDS-2535 -- 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-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 updated JBDS-2635: -------------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > 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: 7.1.0.Beta1 > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2623: -------------------------------------- Fix Version/s: (was: 7.1.0.Alpha2) > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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-2696) Could not load repository template extension error message after spring is installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2696?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2696: -------------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > Could not load repository template extension error message after spring is installed > ------------------------------------------------------------------------------------ > > Key: JBDS-2696 > URL: https://issues.jboss.org/browse/JBDS-2696 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Victor Rubezhny > Fix For: 7.1.0.Beta1 > > Attachments: 2696.png > > > There is this error message after spring is installed: > {code} > Could not load repository template extension contributed by org.eclipse.mylyn.bugzilla.ide with connectorKind bugzilla > {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] (JBDS-2712) Typo in installer: Ok > OK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2712?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2712: -------------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > Typo in installer: Ok > OK > -------------------------- > > Key: JBDS-2712 > URL: https://issues.jboss.org/browse/JBDS-2712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 7.1.0.Beta1 > > Attachments: Installer_Ok1.png, Installer_Ok2.png > > > In step 5 of the installer (Select Platforms and Servers), two child windows have 'Ok', which should be 'OK'. > 1. At step 5, click Add. > 2. Click Browse. > 3. Select location and click *Ok*. > 4. Click *Ok* to close the Add Location window. > Screen captures attached. -- 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