[JBoss JIRA] (JBDS-3167) Include EGit 3.5.0 in JBDS 8
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBDS-3167:
--------------------------------------
Summary: Include EGit 3.5.0 in JBDS 8
Key: JBDS-3167
URL: https://issues.jboss.org/browse/JBDS-3167
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: target-platform
Affects Versions: 8.0.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17882) Validate remote server dir before start/stop/deploy operations
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17882?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17882:
--------------------------------
Fix Version/s: 4.2.x
> Validate remote server dir before start/stop/deploy operations
> --------------------------------------------------------------
>
> Key: JBIDE-17882
> URL: https://issues.jboss.org/browse/JBIDE-17882
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> Max said this on irc today:
> {quote}
> strykerawb: i got some really weird behavior 12:56:27
> maxandersen strykerawb: see this video: http://screencast.com/t/uSDT1EoS 12:56:31
> jbossbot Title: 014-07-15_1255 - max.rydahl.andersen's library 12:56:31
> maxandersen what is it doing? 12:56:34
> maxandersen this is me dragging a project to wildfly server 12:56:42
> maxandersen ah the server is configured as remote with blank remote server home... 12:57:05
> maxandersen seems that result in complete funky endless loop..
> {quote}
> The problem is that he had an empty dir set up on a remote server. So when he tried to publish, this resulted in some unexpected behavior (endless copy progress in this case).
> Currently, when you create a remote server, the dialog will not let you leave the server home dir empty. But that is not enough. You can still change it in the server editor to be empty. Rob says he wants to remove this field from the server editor and only use the wizard, but that is still not enough - the user can remote the folder on the remote system at a later time.
> We probably don't need to check the folder every time we use it, but at least at the start of each operation such as start/stop server, publish to server.
> Also, the New server dialog checks for empty string, but I'm not 100 % sure if it actually checks that the folder exists.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17315) Investigate org.eclipse.jst.server.core.serverProfilers ext.pt.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17315?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17315:
--------------------------------
Fix Version/s: 4.3.0.Alpha1
> Investigate org.eclipse.jst.server.core.serverProfilers ext.pt.
> ---------------------------------------------------------------
>
> Key: JBIDE-17315
> URL: https://issues.jboss.org/browse/JBIDE-17315
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx, server
> Reporter: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
>
> The extension point provided in upstream WTP for declaring server profilers is called org.eclipse.jst.server.core.serverProfilers.
> The primary function of the implementation class org.eclipse.jst.server.core.ServerProfilerDelegate is adding arguments to launches in order to enable the proper agent.
> If used with other profilers, arguments may need to be appended to the launch in order to enable the profiling.
> If used via JVM Monitor, though, no real arguments are required, as JVM Monitor can install its agent directly without any changes on the part of the launch.
> However, if we assume that JBIDE-17313 is solved and we can detect the duplicates, we could prevent the agent from being installed. We would be preventing the auto-detector from being added to the view. On our server startup, then, and only when profiling is enabled, we would connect the underlying jvmmonitor's agent and allow profiling.
> This could be accomplished via a custom attribute on the launch configuration which could be flipped by the user via a radio / check button to enable or disable the profiler.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18389) Newly created web page has content of previously deleted web page
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18389?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18389:
------------------------------------------------
Try to reproduce everything with CR1 on fresh Fedora 20 KDE - no success.
> Newly created web page has content of previously deleted web page
> -----------------------------------------------------------------
>
> Key: JBIDE-18389
> URL: https://issues.jboss.org/browse/JBIDE-18389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Environment: Linux, JBT 4.2.0.CR1-v20140914-0645-B242
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.x
>
> Attachments: chachexhtml.mp4
>
>
> 1. Create JSF 1.2 Kickstart project
> 2. Create empty new XHTML page within WebContent folder do not use any template
> ASSERT: Opened page has empty content
> 3. Add some text to page and save
> 4. Delete created page
> 5. Repeat step 2. using the same name and location of created page
> ERROR: Opened page is not empty but has content of previously created page
> ERROR: Created page is empty on file system therefore content of VPE and file on file system is different.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months