[JBoss JIRA] (JBIDE-19498) docker container view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19498.
---------------------------------
Working except for the missing cpu/memory like Xavier says. Closing. Verified in JBDS 9.0.0.Beta1 B34
> docker container view
> ---------------------
>
> Key: JBIDE-19498
> URL: https://issues.jboss.org/browse/JBIDE-19498
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Beta1
>
> 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.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19979) New Docker connection wizard is confusing when no Docker is detected
by Martin Malina (JIRA)
Martin Malina created JBIDE-19979:
-------------------------------------
Summary: New Docker connection wizard is confusing when no Docker is detected
Key: JBIDE-19979
URL: https://issues.jboss.org/browse/JBIDE-19979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: docker, upstream
Affects Versions: 4.3.0.Beta1
Reporter: Martin Malina
When I open the new Docker Connection wizard (clicking on the link in Docker Explorer) and no running Docker daemon is detected, there is no way to know this. If I know how this works, then I will know that a detected docker would result in prefilled fields in the Wizard. But if I don't know this, I can be easily confused. There is no warning or anything. And what's worse, I can even click Finish to create the connection. It should be disabled unless I select custom values in case Docker was not detected.
Upstream bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469635
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19919:
------------------------------------
Still not done. Please fix ASAP.
https://github.com/jbosstools/jbosstools-base/commits/jbosstools-4.3.0.Be...
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-19919
> URL: https://issues.jboss.org/browse/JBIDE-19919
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19883:
-------------------------------
Fix Version/s: 4.3.0.Beta1
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Brian Fitzpatrick
> Fix For: 4.3.0.Beta1
>
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19883:
------------------------------------
OK, only one project left: ESB. Assigned to [~bfitzpat]. When done, please close this JIRA.
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Brian Fitzpatrick
> Fix For: 4.3.0.Beta1
>
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3455) Wrong version of playground components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3455?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3455:
---------------------------------
Summary: Wrong version of playground components (was: Wrong version of easymport components)
> Wrong version of playground components
> --------------------------------------
>
> Key: JBDS-3455
> URL: https://issues.jboss.org/browse/JBDS-3455
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Affects Versions: 9.0.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 9.0.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19883:
-------------------------------
Component/s: (was: jbpm)
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19883:
----------------------------------
Assignee: Brian Fitzpatrick (was: Nick Boldt)
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Brian Fitzpatrick
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Fix Version/s: 4.3.0.Beta2
> Connecting to a server configured for basic auth with Oauth scheme provides no indication
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19954:
------------------------------------------
Setting fixVersion to 4.3.0.Beta2 since this is annoying but not hurtful.
> Connecting to a server configured for basic auth with Oauth scheme provides no indication
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months