[JBoss JIRA] (JBDS-2513) Error: Could not create the Java Virtual Machine
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2513?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2513:
-------------------------------------------
[~ryan.gourley] how much memory do you have on your machine ? Less than 1GB ?
265m is going to give you problems as soon as you start importing larger projects I would reckon.
> Error: Could not create the Java Virtual Machine
> ------------------------------------------------
>
> Key: JBDS-2513
> URL: https://issues.jboss.org/browse/JBDS-2513
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Environment: Windows 7 64-bit, Java 7 32-bit JVM
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 7.0.0.Beta2
>
> Attachments: 2012-11-30_1425.png, 2012-11-30_1425_001.png, Installer_JVM_Settings.png
>
>
> Running the installer with a JRE can create an improper installation. See screenshots
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17964:
---------------------------------------------
I don't think this jira is the right place to change installations mechanism or the exact feature list.
I at least I can't answer definitive on this list now for how it should be in future - way too early
> add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-17964
> URL: https://issues.jboss.org/browse/JBIDE-17964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 4.1.2.Final
> Reporter: Lars Heinemann
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
>
> Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17955) Application wizard: Opening quickstart link opens all previously selected quickstarts
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17955?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-17955:
----------------------------------------
Assignee: Andre Dietisheim
> Application wizard: Opening quickstart link opens all previously selected quickstarts
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17955
> URL: https://issues.jboss.org/browse/JBIDE-17955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
>
> In New application wizard Quickstarts contain details area. In this area is a link for each quickstart leading to website describing the given quickstart. After clicking on several quickstart (not links, just quickstarts in Tree) and then click on link, several web sites are opened (for each clicked quickstart).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17955) Application wizard: Opening quickstart link opens all previously selected quickstarts
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17955?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17955:
-------------------------------------
Summary: Application wizard: Opening quickstart link opens all previously selected quickstarts (was: Opening quickstart link opens all previously clicked quickstarts in OpenShift tools)
> Application wizard: Opening quickstart link opens all previously selected quickstarts
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17955
> URL: https://issues.jboss.org/browse/JBIDE-17955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Labels: application_wizard
>
> In New application wizard Quickstarts contain details area. In this area is a link for each quickstart leading to website describing the given quickstart. After clicking on several quickstart (not links, just quickstarts in Tree) and then click on link, several web sites are opened (for each clicked quickstart).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17955) Opening quickstart link opens all previously clicked quickstarts in OpenShift tools
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17955?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17955:
-------------------------------------
Summary: Opening quickstart link opens all previously clicked quickstarts in OpenShift tools (was: Opening quickstart link open all previously clicked quickstarts in OpenShift tools)
> Opening quickstart link opens all previously clicked quickstarts in OpenShift tools
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-17955
> URL: https://issues.jboss.org/browse/JBIDE-17955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Labels: application_wizard
>
> In New application wizard Quickstarts contain details area. In this area is a link for each quickstart leading to website describing the given quickstart. After clicking on several quickstart (not links, just quickstarts in Tree) and then click on link, several web sites are opened (for each clicked quickstart).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17984) Application wizard: dont commit nor push changes back to OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17984:
-------------------------------------
Description:
In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests.
We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.
was:
In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
This resulted in having a "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard). UX tests revealed that this dialog is disturbing to users, it is pretty much unexpected for them. We could solve this via automatic commit as we did so far but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.
> Application wizard: dont commit nor push changes back to OpenShift
> ------------------------------------------------------------------
>
> Key: JBIDE-17984
> URL: https://issues.jboss.org/browse/JBIDE-17984
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
>
> In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
> In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests.
> We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17942) tycho-plugins 0.19-snapshot is missing
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17942?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17942:
----------------------------------------
If we release 0.19.0, then 0.19.0-SNAPSHOT will disappear and all people consuming parent pom referencing it (prior to 4.2.0.CR1-SNAPSHOT) will see their build fail.
If we release 0.21.0, then 0.19.0-SNAPSHOT will still be there, and we put a release in parent pom. However, moving to newer Tycho requires some changes, so I find it safer to build and adopt a 0.21.0-SNAPSHOT for let's say a week and then release it within a few day (not to be forgotten!).
> tycho-plugins 0.19-snapshot is missing
> --------------------------------------
>
> Key: JBIDE-17942
> URL: https://issues.jboss.org/browse/JBIDE-17942
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Beta3
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> this morning reports were coming in builds were failing because org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT was missing.
> Turns out https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... failed to upload and then https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... ran but the machine running thought it was July 12th and not July 14th.
> To fix it I respun the build and not the urgent issue is fixed but:
> A) Why are we even using snapshots for this JBIDE-17941
> B) Why did the snapshot dissapear/why is jenkins build several days behind.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month