[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13319:
-------------------------------------
Labels: respin-b (was: )
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2, 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13352) Should be able to remove cartridge with "Remove" in the context menu
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13352:
----------------------------------------
Summary: Should be able to remove cartridge with "Remove" in the context menu
Key: JBIDE-13352
URL: https://issues.jboss.org/browse/JBIDE-13352
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.x
Attachments: remove-embedded-cartridge.png
If you have a cartridge embedded to your application you'll see it listed as node below your application:
!remove-embedded-cartridge.png!
To remove it, you'll have to select your application and pick "Edit embeddable cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13352) Should be able to remove cartridge with "Remove" in the context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13352:
-------------------------------------
Attachment: remove-embedded-cartridge.png
> Should be able to remove cartridge with "Remove" in the context menu
> --------------------------------------------------------------------
>
> Key: JBIDE-13352
> URL: https://issues.jboss.org/browse/JBIDE-13352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.0.x
>
> Attachments: remove-embedded-cartridge.png
>
>
> If you have a cartridge embedded to your application you'll see it listed as node below your application:
> !remove-embedded-cartridge.png!
> To remove it, you'll have to select your application and pick "Edit embeddable cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13352) Should be able to remove cartridge with "Remove" in the context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13352:
-------------------------------------
Description:
If you have a cartridge embedded to your application you'll see it listed as node below your application:
!remove-embedded-cartridge.png!
To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
was:
If you have a cartridge embedded to your application you'll see it listed as node below your application:
!remove-embedded-cartridge.png!
To remove it, you'll have to select your application and pick "Edit embeddable cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
> Should be able to remove cartridge with "Remove" in the context menu
> --------------------------------------------------------------------
>
> Key: JBIDE-13352
> URL: https://issues.jboss.org/browse/JBIDE-13352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.0.x
>
> Attachments: remove-embedded-cartridge.png
>
>
> If you have a cartridge embedded to your application you'll see it listed as node below your application:
> !remove-embedded-cartridge.png!
> To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13320:
------------------------------------------
fix pushed in https://github.com/jbosstools/jbosstools-openshift/commit/0ec1462f1fe13be... to jbosstools-3.3.x
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-13320.
--------------------------------------
Resolution: Done
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-13326.
------------------------------
Verified. Closing.
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.0.Final, 4.0.1.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {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
13 years, 2 months
[JBoss JIRA] (JBIDE-13338) BrowserSim: integrate weinre functionality to BrowserSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13338?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-13338:
------------------------------------------------
{quote}this looks interesting but i'm not following what this feature does ?
Does it auto-inject some code or is it just auto-opening a weinre url ?{quote}
It auto-inject javascript library needed for highlighting(as shown in attachment) and opens a weinre url(connected with injected script)
> BrowserSim: integrate weinre functionality to BrowserSim
> --------------------------------------------------------
>
> Key: JBIDE-13338
> URL: https://issues.jboss.org/browse/JBIDE-13338
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Alpha1
>
> Attachments: example.png, weinre.bmml, weinre.png
>
>
> It will be good to have debug capabilities in browserSim. Weinre can provide it.
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2364.
-------------------------------
OK then. Closing.
> Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
> ----------------------------------------------------------------------------
>
> Key: JBDS-2364
> URL: https://issues.jboss.org/browse/JBDS-2364
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer, maven, updatesite
> Affects Versions: 5.0.0.GA, 5.0.1.GA
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 5.0.2.GA
>
> Attachments: install-error.png
>
>
> Steps to reproduce:
> 1. Clone git://github.com/jbossas/jboss-as.git somewhere
> 2. File -> Import -> Existing maven project
> 3. Select <jboss_git_checkout>/cmp/pom.xml and try to import
> 4. build-helper-maven-plugin will be required - try to have it resolved
> 5. build-helper-maven-plugin will fail on dependencies - cannot satisfy org.eclipse.m2e.jdt
> When you try to import for example the cmp project from as7 (git://github.com/jbossas/jboss-as.git) you will need to install build-helper-maven-plugin. But that will fail because of unsatisfied dependency for org.eclipse.m2e.jdt .
> The problem is that org.eclipse.m2e.jdt is available, but only in version 1.0.x whereas the required version is [1.1.0,2.0.0).
> This is the error message:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> Missing requirement: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper 0.15.0.201207090124) requires 'bundle org.eclipse.m2e.jdt [1.1.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> To: org.sonatype.m2e.buildhelper [0.15.0.201207090124]
> {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
13 years, 2 months