October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18658) Remove All embedded cartridges in New application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18658?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18658: ------------------------------------- Priority: Minor (was: Major) > Remove All embedded cartridges in New application wizard > -------------------------------------------------------- > > Key: JBIDE-18658 > URL: https://issues.jboss.org/browse/JBIDE-18658 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: application-wizard.png > > > We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). > But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. > !application-wizard.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18658) Remove All embedded cartridges in New application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18658?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18658: ------------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Alpha1) > Remove All embedded cartridges in New application wizard > -------------------------------------------------------- > > Key: JBIDE-18658 > URL: https://issues.jboss.org/browse/JBIDE-18658 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: 4.3.x > > Attachments: application-wizard.png > > > We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). > But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. > !application-wizard.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18658) Remove All embedded cartridges in New application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18658?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18658: ------------------------------------- Description: We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. !application-wizard.png! was: We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. > Remove All embedded cartridges in New application wizard > -------------------------------------------------------- > > Key: JBIDE-18658 > URL: https://issues.jboss.org/browse/JBIDE-18658 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Marián Labuda > Labels: application_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: application-wizard.png > > > We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). > But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. > !application-wizard.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18658) Remove All embedded cartridges in New application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18658?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18658: ------------------------------------- Attachment: application-wizard.png > Remove All embedded cartridges in New application wizard > -------------------------------------------------------- > > Key: JBIDE-18658 > URL: https://issues.jboss.org/browse/JBIDE-18658 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Marián Labuda > Labels: application_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: application-wizard.png > > > We have embedding cartridge In New application wizard on second wizard page. We allow user to add a new embeddable cartridge by clicking on button Add (it opens shell) and select a embeddable cartridge from the list of available (not yet embedded) cartridges in the shell. This shell contains also Deselect all which is not useful on this place (only use case is if user want to add new cartridges, he click on more cartridges and then he decide to undo it - this is not useful I think). > But the real improvement comes on the second wizard page in Embeddable cartridges section. There is a button Add (mentioned earlier) and a button Remove. There could be also button Remove All - to remove all selected embedded cartridges from the list of desired embeddable cartridges. > !application-wizard.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-339: ---------------------------------- That's perfect - thank you. > Support generation of update sites both with and without references to upstream TP content > ------------------------------------------------------------------------------------------ > > Key: JBTIS-339 > URL: https://issues.jboss.org/browse/JBTIS-339 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: content.xml.new, content.xml.orig > > > Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours: > * One plain content only, without any reference: for downstream project aggregation > * One that also references its dependencies for easy install and testers > Example: > {code} > /integration-stack <-- composited without side effects into /earlyaccess/development/luna/ > content.jar > artifacts.jar > /withdeps <--- good for testing/single installs > /compositeContent.xml -> ../ and ../targetplatform-link/ > /compositeArtifacts.xml > /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.] > content.xml -> associate pointer to TP using ONLY: > <references size="4"> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP) > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > </references> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBTIS-339: -------------------------------------- Yes 0.21.1-SNAPSHOT with this change is already available in JBoss Snapshot repo (https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... ). You can already use it. I can let you have fun with it and unless you find something wrong, I'll release it as 0.21.1 on Monday morning (european time). Is it good for you? > Support generation of update sites both with and without references to upstream TP content > ------------------------------------------------------------------------------------------ > > Key: JBTIS-339 > URL: https://issues.jboss.org/browse/JBTIS-339 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: content.xml.new, content.xml.orig > > > Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours: > * One plain content only, without any reference: for downstream project aggregation > * One that also references its dependencies for easy install and testers > Example: > {code} > /integration-stack <-- composited without side effects into /earlyaccess/development/luna/ > content.jar > artifacts.jar > /withdeps <--- good for testing/single installs > /compositeContent.xml -> ../ and ../targetplatform-link/ > /compositeArtifacts.xml > /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.] > content.xml -> associate pointer to TP using ONLY: > <references size="4"> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP) > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > </references> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-339: ---------------------------------- [~mickael_istria] - I see you've merged the PR for this feature in repository-utils 0.21.1-SNAPSHOT. I need to create the JBTIS 4.2.0.Beta1 release early next week so I'll need the updated tycho-plugins - is it available? I believe the withReferences vs "plain" approach satisfies the primary use case. Thanks! > Support generation of update sites both with and without references to upstream TP content > ------------------------------------------------------------------------------------------ > > Key: JBTIS-339 > URL: https://issues.jboss.org/browse/JBTIS-339 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: content.xml.new, content.xml.orig > > > Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours: > * One plain content only, without any reference: for downstream project aggregation > * One that also references its dependencies for easy install and testers > Example: > {code} > /integration-stack <-- composited without side effects into /earlyaccess/development/luna/ > content.jar > artifacts.jar > /withdeps <--- good for testing/single installs > /compositeContent.xml -> ../ and ../targetplatform-link/ > /compositeArtifacts.xml > /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.] > content.xml -> associate pointer to TP using ONLY: > <references size="4"> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP) > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > </references> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18551) New Hybrid Mobile dialog not working with proxy

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18551?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18551: --------------------------------- Fix Version/s: 4.2.1.Final > New Hybrid Mobile dialog not working with proxy > ----------------------------------------------- > > Key: JBIDE-18551 > URL: https://issues.jboss.org/browse/JBIDE-18551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR2 > Environment: JBT 4.2.0.CR2-v20141005-0541-B267, Linux setup to use proxy server for communication on all ports > Reporter: Vlado Pakan > Fix For: 4.2.1.Final > > > 0. Setup OS to use proxy server for networking > 1. Open New dialog > 2. Select Hybrid Mobile project > 3. Click next > ERROR: Mouse cursor is changed to waiting and dialog is not possible to cancel. JBT has the same behavior either Eclipse is set to use Native networking or proxy server is manually set up within Eclipse. > Would be nice to display some info about what's going on (probably checking web for available Cordova engines) and also allow users to cancel this operation -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) Some platform bundles comes from pre-SR1 build in CR2 builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-18571. ------------------------------------ Resolution: Done This appears to be fixed with Build #314 of devstudio-project_8.0.luna. > Some platform bundles comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: missing-bonus-jdt.core-hacked-by-otdt.png, p2diff_SR1_SR1a, SR1vSR1a.p2diff.txt > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18659) Deselecting embedded cartridges warning should be shown only if deselected catridges are embedded

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18659?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18659: ---------------------------------- Fix Version/s: 4.3.x > Deselecting embedded cartridges warning should be shown only if deselected catridges are embedded > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-18659 > URL: https://issues.jboss.org/browse/JBIDE-18659 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Marián Labuda > Labels: embed_wizard > Fix For: 4.3.x > > > In Edit Embedded Cartridges shell is a button to deselect all selected embeddable cartridges in the application. This button invoke a warning to let user know about possible data loss. The warning is shown regardless I selected embeddable catridge(s) in the currently opened shell (and they are not yet embedded into application) or they are already embedded. > This warning should be shown only in case if one of the selected embeddable cartridges is already embedded into application and there is really a possible data loss. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014