[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ]
Arun Gupta commented on JBDS-3256:
----------------------------------
Would also like to take an existing Maven or Eclipse project, figure out the dependencies, and create a Dockerfile
> JBoss specific Docker Tooling (Basic Integration)
> -------------------------------------------------
>
> Key: JBDS-3256
> URL: https://issues.jboss.org/browse/JBDS-3256
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
> Expected end-user flow 1:
> 0) Installation - assumes boot2docker pre-installed on the end-user's machine
> 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
> 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
> 3) I start (docker run) the image which auto-starts the embedded app server
> 4) I can then deploy my .war or .ear to the running app server
> 5) I can restart the running app server in debug mode and run the debugger
> 6) I can undeploy and redeploy my .war or .ear
> 7) I can stop/restart the running, embedded app server
> 8) I can then commit (docker commit)
> 9) then I can publish my changes (docker push)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ]
Arun Gupta commented on JBDS-3256:
----------------------------------
Here is some basic Docker tooling that would be helpful:
- Configure Docker Registries (public or private)
- Search images that on the configured registry
- Specify the name of an image that need to run the container. The image is downloaded, and possibly cached, if does not already exist.
- Like Servers tab at the bottom, it would be useful to have a Docker tab or provide a single UI to interact with everything Docker
- Orchestration of multiple Docker containers. For example, WildFly running in one container and MySQL in another one. Tooling can provide plumbing to make that happen.
[~maxandersen] Docker images already exist and defined at: http://www.jboss.org/docker/. As [~burrsutter] explained, app server-specific integration would be very useful, and much desirable by JBoss Tools.
> JBoss specific Docker Tooling (Basic Integration)
> -------------------------------------------------
>
> Key: JBDS-3256
> URL: https://issues.jboss.org/browse/JBDS-3256
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
> Expected end-user flow 1:
> 0) Installation - assumes boot2docker pre-installed on the end-user's machine
> 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
> 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
> 3) I start (docker run) the image which auto-starts the embedded app server
> 4) I can then deploy my .war or .ear to the running app server
> 5) I can restart the running app server in debug mode and run the debugger
> 6) I can undeploy and redeploy my .war or .ear
> 7) I can stop/restart the running, embedded app server
> 8) I can then commit (docker commit)
> 9) then I can publish my changes (docker push)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18869:
--------------------------------------
I prefer a single generic url and fresh mirror pull but I am lazy and don't like editing xml. If there is a good reason for not doing a generic one, I will play.
> migrate Thym from TP to being an aggregated component
> -----------------------------------------------------
>
> Key: JBIDE-18869
> URL: https://issues.jboss.org/browse/JBIDE-18869
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid, build, target-platform, updatesite
> Affects Versions: 4.2.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>
> Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP.
> This would allow it to be incorporated into builds more easily and would avoid TP churn.
> This should be fixed in master then backported for 4.2.2 (or 4.2.3).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-18983:
------------------------------------
[~nickboldt] v: is a locak drive. I'm using JBT installed from the marketplace.
Eclipse and workspace are both in V but my profile and .m2 are on c:\
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, jsp/jsf/xml/html source editing, updatesite
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Nick Boldt
> Fix For: 4.2.x, 4.3.x
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Cody Lerum edited comment on JBIDE-18983 at 12/23/14 12:07 PM:
---------------------------------------------------------------
[~nickboldt] v: is a local drive. I'm using JBT installed from the marketplace.
Eclipse and workspace are both in V but my profile and .m2 are on c:\
was (Author: clerum):
[~nickboldt] v: is a locak drive. I'm using JBT installed from the marketplace.
Eclipse and workspace are both in V but my profile and .m2 are on c:\
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, jsp/jsf/xml/html source editing, updatesite
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Nick Boldt
> Fix For: 4.2.x, 4.3.x
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months