[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19759:
-------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Application wizard: cannot launch v3 application wizard via File->New->OpenShift
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19759
> URL: https://issues.jboss.org/browse/JBIDE-19759
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-v2-wizard-page.png, no-application-wizard.png
>
>
> If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19817:
------------------------------------------
We went out of time for this in 4.3.0.Beta1
> Application wizard: v3 application wizard needs to be able to react to changing connections
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19817
> URL: https://issues.jboss.org/browse/JBIDE-19817
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19939) Validate basic auth prompt with initial eclipse session an expired token
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19939:
-------------------------------------
Summary: Validate basic auth prompt with initial eclipse session an expired token
Key: JBIDE-19939
URL: https://issues.jboss.org/browse/JBIDE-19939
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Jeff Cantrill
Validate that a user is properly prompted for credentials when the server is configured for Basic Auth and the user opens a new eclipse session and has an expired/invalid token loaded from storage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19817 at 6/4/15 1:52 PM:
------------------------------------------------------------------
We went out of time for this in 4.3.0.Beta1. Postponing.
was (Author: adietish):
We went out of time for this in 4.3.0.Beta1
> Application wizard: v3 application wizard needs to be able to react to changing connections
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19817
> URL: https://issues.jboss.org/browse/JBIDE-19817
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19817:
-------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Application wizard: v3 application wizard needs to be able to react to changing connections
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19817
> URL: https://issues.jboss.org/browse/JBIDE-19817
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19914) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19914?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19914.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JBT Update Sites]
> --------------------------------------------------------------
>
> Key: JBIDE-19914
> URL: https://issues.jboss.org/browse/JBIDE-19914
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [JBT Update Sites]: 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 JBT Update Sites 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-19916) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19916?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19916:
------------------------------------
Done for jbosstools-download.jboss.org and jbosstools-devdoc.
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central Discovery]
> ---------------------------------------------------------------
>
> Key: JBIDE-19916
> URL: https://issues.jboss.org/browse/JBIDE-19916
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central Discovery]: 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 Central Discovery 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-19916) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19916?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19916:
------------------------------------
Done for jbosstools-build-ci and jbosstools-maven-plugins.
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central Discovery]
> ---------------------------------------------------------------
>
> Key: JBIDE-19916
> URL: https://issues.jboss.org/browse/JBIDE-19916
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central Discovery]: 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 Central Discovery 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-19938) java.io.FileNotFoundException when batch feature installed
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-19938:
--------------------------------------
Summary: java.io.FileNotFoundException when batch feature installed
Key: JBIDE-19938
URL: https://issues.jboss.org/browse/JBIDE-19938
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Beta2
I have a bunch of JavaEE projects in my workspace.
When opening that workspace I saw the following exception in the log:
{code}
java.io.FileNotFoundException: /home/igels/Java/eclipse-mars/workspace/runtime/SeamTest/WebContent/WEB-INF/classes (Is a directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:220)
at java.util.zip.ZipFile.<init>(ZipFile.java:150)
at java.util.jar.JarFile.<init>(JarFile.java:166)
at java.util.jar.JarFile.<init>(JarFile.java:130)
at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:47)
at org.jboss.tools.common.core.jandex.JandexUtil.hasSubtypes(JandexUtil.java:123)
at org.jboss.tools.batch.internal.core.scanner.BatchArchiveDetector.computeIsJarBatchArchive(BatchArchiveDetector.java:278)
{code}
WEB-INF/classes or any other bin folder should not been scanned by Batch JAR scanner.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-19933 at 6/4/15 1:19 PM:
---------------------------------------------------------------
Good suggestion, Nick :) Seems like the easiest way, why not.
(Although the originally proposed solution - copy over content from master at the time of code freeze - is more correct - master can start moving right away after code freeze and theoretically some change in master could break the build until Beta1 would point to 4.3.mars.)
was (Author: mmalina):
Good suggestion, Nick :) Seems like the easiest way, why not.
> Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months