[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18862.
---------------------------------
I checked some use cases with JBDS 8.1.0.CR1 and 9.0.0.Alpha1, most notably that a dodeploy marker is removed when you publish to a stopped server and then remove the deployment before you start the server. And I believe that we're good to close this JIRA now. The special use case of incremental publish after full publish is tracked in JBIDE-19182 .
> when removing a module from AS runtime marker files are not removed automatically
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18862
> URL: https://issues.jboss.org/browse/JBIDE-18862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Windiws7 64bit, JDK 8u25
> Reporter: Darryl Miles
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> module removal does not delete the various marker files relating to it:
> *.undeployed
> *.dodeploy
> The same should be true when ADDING a module, it should clean out any marker files.
> Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written.
> Write out the*.ear file.
> Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19498) docker container view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-19498 at 3/23/15 7:59 AM:
----------------------------------------------------------------------
uploaded mockup for container. I think showing cpu/ram load fits much better into the table for an overview than full command/ports access.
Thus I would probably just have name, cpu, memory and state in the table and leave others for the detailed properties view.
was (Author: maxandersen):
uploaded mockup for container. I think showing cpu/ram load fits much better into the table for an overview than full command/ports access.
> docker container view
> ---------------------
>
> Key: JBIDE-19498
> URL: https://issues.jboss.org/browse/JBIDE-19498
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Reporter: Max Rydahl Andersen
> Attachments: container_mockup.bmml, container_mockup.png
>
>
> the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19498) docker container view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19498:
---------------------------------------------
uploaded mockup for container. I think showing cpu/ram load fits much better into the table for an overview than full command/ports access.
> docker container view
> ---------------------
>
> Key: JBIDE-19498
> URL: https://issues.jboss.org/browse/JBIDE-19498
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Reporter: Max Rydahl Andersen
> Attachments: container_mockup.bmml, container_mockup.png
>
>
> the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19498) docker container view
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19498:
-------------------------------------------
Summary: docker container view
Key: JBIDE-19498
URL: https://issues.jboss.org/browse/JBIDE-19498
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: docker
Reporter: Max Rydahl Andersen
the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19496) docker run wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-19496 at 3/23/15 7:38 AM:
----------------------------------------------------------------------
Create initial ideas/mockup for how run docker would work.
Nothing fancy here but novelties are that we could provide a docker cli parser to prefill settings from online examples that uses the cli to tell users what it should do. We could even go so far to use the cli syntax as the way we store the "run" allowing for co-sharing scripts.
making the mockup makes me also realize using launch configurations for definining/storing these launches probably makes alot of sense.
Still should try have as simple an experience so custom wizard is needed.
Also note that the dialogs are to be made so the *only* thing needed to fill out is the image - everything else should be defaulted so we can run a container by just pressing finish.
was (Author: maxandersen):
Create initial ideas/mockup for how run docker would work.
Nothing fancy here but novelties are that we could provide a docker cli parser.
> docker run wizard
> -----------------
>
> Key: JBIDE-19496
> URL: https://issues.jboss.org/browse/JBIDE-19496
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Reporter: Max Rydahl Andersen
> Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png
>
>
> should have a docker wizard to easily run images.
> The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases.
> For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19033) Prefix string too short prevents EL content assist with Seam taglib
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19033?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19033.
---------------------------------
Verified in JBDS 8.1.0.Beta1 by [~vpakan]. Thanks, Vlado!
> Prefix string too short prevents EL content assist with Seam taglib
> -------------------------------------------------------------------
>
> Key: JBIDE-19033
> URL: https://issues.jboss.org/browse/JBIDE-19033
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, seam2
> Affects Versions: 4.2.1.Final
> Environment: Plugin: Seam Tools 3.6.1.Final-v20141209-0505-B79
> OS: Windows 8.1 64bit
> Eclipse: 4.4.1.M20140925-0400 (Luna SR1)
> JVM: 1.8.0_25 (64bit, Oracle)
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.3.Beta1
>
>
> When Seam Tools is installed in Eclipse Luna SR1, Expression Language (EL) content assist in Visual Page Editor stopped working (no suggestion at all, JBoss related or not). This occurs only when xmlns:s="http://jboss.com/products/seam/taglib" tag library is used in a Facelet page.
> Eclipse log shows following stacktrace on any such content assist attempt:
> {quote}
> org.jboss.tools.common.validation.JBTValidationException: Prefix string too short
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
> at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
> at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
> at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
> Caused by: java.lang.IllegalArgumentException: Prefix string too short
> at java.io.File.createTempFile(File.java:2001)
> at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.convertUriToFile(TagLibraryManager.java:182)
> at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:100)
> at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44)
> at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135)
> at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getLibraries(TagLibraryManager.java:57)
> at org.jboss.tools.jst.web.kb.PageContextFactory.fillXMLNamespacesForNode(PageContextFactory.java:996)
> at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForNode(PageContextFactory.java:698)
> at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForChildNodes(PageContextFactory.java:687)
> at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:431)
> at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:236)
> at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:199)
> at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:184)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:253)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 10 more
> {quote}
> Digging more deeply into the cause, Eclipse loaded a plugin specified entry for this URI as:
> {quote}
> Entry element: URI
> Location: taglibs\tld\s.tld in jar file C:\DevTools\IDE\eclipse\eclipse-ee-luna-sr1-64bit\plugins\org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> URI: jar:file:/C:/DevTools/IDE/eclipse/eclipse-ee-luna-sr1-64bit/plugins/org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar!/taglibs/tld/s.tld
> Key type: URI
> Key: http://jboss.com/products/seam/taglib
> {quote}
> Line 182 of org.jboss.tools.jst.web.kb.taglib.TagLibraryManager shows the "too short" prefix is derived from the name of the file. Here, the culprit prefix is "s" (derived from "s.tld"). Temporary file prefix must be at least 3 characters long (javadoc: http://docs.oracle.com/javase/8/docs/api/java/io/File.html#createTempFile...).
> I managed to work around this issue temporarily by renaming s.tld and s.taglib.xml in org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar to seam.tld and seam.taglib.tld respectively. Then I changed the entry in JAR's plugin.xml accordingly and started eclipse with "-clean" option for the changes to take effect. Now, content assist runs expectedly.
> Either renaming the plugin's TLD file or ensuring the minimum prefix length in code should do the trick.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19496) docker run wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19496:
---------------------------------------------
Create initial ideas/mockup for how run docker would work.
Nothing fancy here but novelties are that we could provide a docker cli parser.
> docker run wizard
> -----------------
>
> Key: JBIDE-19496
> URL: https://issues.jboss.org/browse/JBIDE-19496
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Reporter: Max Rydahl Andersen
> Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png
>
>
> should have a docker wizard to easily run images.
> The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases.
> For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years