[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17741:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.3.x
>
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as on other places for tree items (e.g. cartridges). E.g. in following table could be for Cron cartridge label like "Cron 1.4" as non-styled text (classic font, black color) and "(cron-1.4)" could be brown/grey/... as styled text, bcs. it´s description/inner representation of cartridge.
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17741:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.CR1)
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as on other places for tree items (e.g. cartridges). E.g. in following table could be for Cron cartridge label like "Cron 1.4" as non-styled text (classic font, black color) and "(cron-1.4)" could be brown/grey/... as styled text, bcs. it´s description/inner representation of cartridge.
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17760) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17760?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-17760.
----------------------------------
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-17760
> URL: https://issues.jboss.org/browse/JBIDE-17760
> 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.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta3x
> git push origin jbosstools-4.2.0.Beta3x
> {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.2.0.Beta3-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 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.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17740) Cannot deploy git-based project to OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17740:
-------------------------------------
Fix Version/s: 4.2.0.Beta3
Labels: respin-a (was: )
> Cannot deploy git-based project to OpenShift
> --------------------------------------------
>
> Key: JBIDE-17740
> URL: https://issues.jboss.org/browse/JBIDE-17740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.Beta3
>
> Attachments: import.png
>
>
> It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
> See log
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
> !MESSAGE Could not import project to the workspace.
> !STACK 0
> org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> Error shell:
> !import.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17741:
-------------------------------------
Fix Version/s: 4.2.0.CR1
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as on other places for tree items (e.g. cartridges). E.g. in following table could be for Cron cartridge label like "Cron 1.4" as non-styled text (classic font, black color) and "(cron-1.4)" could be brown/grey/... as styled text, bcs. it´s description/inner representation of cartridge.
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17765) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17765?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17765:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JavaEE]
> ----------------------------------------------------
>
> Key: JBIDE-17765
> URL: https://issues.jboss.org/browse/JBIDE-17765
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [JavaEE]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta3x
> git push origin jbosstools-4.2.0.Beta3x
> {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.2.0.Beta3-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 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 JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17760) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17760?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-17760.
------------------------------------
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-17760
> URL: https://issues.jboss.org/browse/JBIDE-17760
> 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.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta3x
> git push origin jbosstools-4.2.0.Beta3x
> {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.2.0.Beta3-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 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.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17479) Add reference to JS/CSS dialog is empty
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17479?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-17479:
---------------------------------------
Verified on Windows and Mac. It works fine
> Add reference to JS/CSS dialog is empty
> ---------------------------------------
>
> Key: JBIDE-17479
> URL: https://issues.jboss.org/browse/JBIDE-17479
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Fedora 18 64bit KDE
> Java Oracle 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
> Attachments: blankjscssdialog.png
>
>
> 1. Create new empty HTML file
> 2. Try to insert tag from JQuery Mobile Palette
> 3. Check checkbox Add Reference to JS/CSS
> 4. Click Next >
> ERROR: Wizard page is empty no widgets present
> 5. Click < Back
> 6. Click Hide Preview
> 7. Click Show Preview
> 8. Click Next >
> ASSERT: Now wizard page has proper content
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17733:
------------------------------------
What about if a user is NOT running the JEE bundle? Do we assume that org.eclipse.egit and org.eclipse.jgit will be installed on demand of some other part of JBT that requires it?
> Remove EGit from Central Discovery
> ----------------------------------
>
> Key: JBIDE-17733
> URL: https://issues.jboss.org/browse/JBIDE-17733
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta3
>
>
> Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed.
> So we should remove EGit from our Central discovery catalogs.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months