[JBoss JIRA] (JBIDE-19847) Central doesn't load - Exctract central page error - File name too long
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19847:
----------------------------------
Summary: Central doesn't load - Exctract central page error - File name too long
Key: JBIDE-19847
URL: https://issues.jboss.org/browse/JBIDE-19847
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.0.Beta1
Environment: Mars M7,
JBT nigtly from 2015-05-24
Reporter: Pavol Srna
Priority: Blocker
Fix For: 4.3.0.Beta1
Attachments: central-err.png
{code}
IO error
IO error
/home/psrna/data/testing/workspaces/e18/.metadata/.plugins/org.jboss.tools.foundation.core/ECF_REMOTE_CACHE/https___repository_jboss_org_nexus_content_groups_public_jboss_org_jboss_tools_central_jbosstools_central_webpage_0_0_1_SNAPSHOT_jbosstools_central_webpage_0_0_1_20150525_145248_3_zip-1043033484887124864.tmp (File name too long)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19847) Central doesn't load - Exctract central page error - File name too long
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19847?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19847:
-------------------------------
Attachment: central-err.png
> Central doesn't load - Exctract central page error - File name too long
> -----------------------------------------------------------------------
>
> Key: JBIDE-19847
> URL: https://issues.jboss.org/browse/JBIDE-19847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Environment: Mars M7,
> JBT nigtly from 2015-05-24
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: central-err.png
>
>
> {code}
> IO error
> IO error
> /home/psrna/data/testing/workspaces/e18/.metadata/.plugins/org.jboss.tools.foundation.core/ECF_REMOTE_CACHE/https___repository_jboss_org_nexus_content_groups_public_jboss_org_jboss_tools_central_jbosstools_central_webpage_0_0_1_SNAPSHOT_jbosstools_central_webpage_0_0_1_20150525_145248_3_zip-1043033484887124864.tmp (File name too long)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19846) Remove generated files after user decides to delete imported unuseful root
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-19846:
---------------------------------------
Summary: Remove generated files after user decides to delete imported unuseful root
Key: JBIDE-19846
URL: https://issues.jboss.org/browse/JBIDE-19846
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: easymport
Affects Versions: 4.3.0.Beta1
Reporter: Lucia Jelinkova
When user selects folder root that contains no real data (e.g. workspace root) importer asks if he wants to delete the project after import. However, even if the project is deleted from workspace, the generated files (e.g .settings, .project) still remain on the filesystem. These should be deleted as they are clearly not needed nor desired.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Xavier Coulon updated JBDS-3258:
--------------------------------
Fix Version/s: 9.0.0.Beta1
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: docker, requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17998.
---------------------------------
OK, thanks, Mickael. In that case I think it's fine to close this.
> Use better <name> in pom file
> -----------------------------
>
> Key: JBIDE-17998
> URL: https://issues.jboss.org/browse/JBIDE-17998
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be:
> * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server...
> * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TOOLSDOC-647) Update JBDS 9.0.0 Install doc with info for offline zip
by Supriya Bharadwaj (JIRA)
Supriya Bharadwaj created TOOLSDOC-647:
------------------------------------------
Summary: Update JBDS 9.0.0 Install doc with info for offline zip
Key: TOOLSDOC-647
URL: https://issues.jboss.org/browse/TOOLSDOC-647
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Components: Installation Guide
Reporter: Supriya Bharadwaj
Assignee: Supriya Bharadwaj
Change info in the Install JBoss Developer Studio BYOE when Offline section of the JBDS 9.0.0 Install guide to say that the user will need only one .zip (update archive) to install.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17998:
----------------------------------------
[~mmalina] So far, I'm ok with the current names. I'll create another Jira if I can think of good reasons to improve some other names.
> Use better <name> in pom file
> -----------------------------
>
> Key: JBIDE-17998
> URL: https://issues.jboss.org/browse/JBIDE-17998
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be:
> * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server...
> * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months