[JBoss JIRA] (JBIDE-19125) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19125?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19125:
-------------------------------
Description:
For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]
> --------------------------------------------------------------------
>
> Key: JBIDE-19125
> URL: https://issues.jboss.org/browse/JBIDE-19125
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19149) forge.core tests failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-19149:
--------------------------------------
Summary: forge.core tests failure
Key: JBIDE-19149
URL: https://issues.jboss.org/browse/JBIDE-19149
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.3.Beta1
Reporter: Alexey Kazakov
Assignee: Koen Aers
Priority: Critical
Fix For: 4.2.3.Beta1
{code}
testGetDefaultInitialCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.002 sectestGetDefaultAndGetInstallationsAlternativeCase(org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest) Time elapsed: 0.008 sec <<< FAILURE!
java.lang.AssertionError: expected:<org.jboss.tools.forge.core.internal.runtime.ForgeEmbeddedRuntime@291bc55> but was:<null>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.verifyEmbedded(ForgeRuntimesPreferencesTest.java:179)
at org.jboss.tools.forge.core.preferences.ForgeRuntimesPreferencesTest.testGetDefaultAndGetInstallationsAlternativeCase(ForgeRuntimesPreferencesTest.java:163)
{code}
{code}
testForgeEmbeddedRuntime(org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest) Time elapsed: 0.001 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<1.[4.4].Final - embedded> but was:<1.[3.3].Final - embedded>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.tools.forge.core.process.ForgeEmbeddedRuntimeTest.testForgeEmbeddedRuntime(ForgeEmbeddedRuntimeTest.java:47)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19125) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19125?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19125 at 2/2/15 8:00 PM:
------------------------------------------------------------
[~gercan]: Thanks for applying that PR.
Now we just need the version bump (and to use the latest parent pom version), especially since you have a fresh commit since 4.2.2 from JBIDE-18989 now built in the 4.2.x branch.
See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_... or https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_...
was (Author: nickboldt):
Thanks for apply that PR. Now we just need the version bump, especially since you have a fresh commit since 4.2.2 from JBIDE-18989 now built in the 4.2.x branch.
See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_... or https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_...
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]
> --------------------------------------------------------------------
>
> Key: JBIDE-19125
> URL: https://issues.jboss.org/browse/JBIDE-19125
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19142) HTML5 Palette: UI cleanup
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19142?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19142:
----------------------------------
Attachment: Palette_UI_Cleanup_2.png
Palette_UI_Cleanup_1.png
Palette_UI_Cleanup_4.png
> HTML5 Palette: UI cleanup
> -------------------------
>
> Key: JBIDE-19142
> URL: https://issues.jboss.org/browse/JBIDE-19142
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Alpha1
>
> Attachments: Palette_UI_Cleanup_1.png, Palette_UI_Cleanup_2.png, Palette_UI_Cleanup_4.png
>
>
> 1. Create menu which allow to clean "Most Popular/Last Used" palette group
> 2. Move button "Show only palette groups for which libraries are defined on the page" to the top of Palette View
> 3. Show message like "No \"Last Used/Most Popular\" items yet. Start using Palette to add items to this group." in "Most Popular/Last Used" palette group, if there are no items to show.
> 4. Show message like "No items found" in all palette group, if there are no items to show according to search pattern
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-14978) Detect availability of new version of maven dependencies/plugins
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14978?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-14978.
-------------------------------
Resolution: Deferred
Deferred indefinitely. Until we find the bandwidth and motivation to work on that matter
> Detect availability of new version of maven dependencies/plugins
> ----------------------------------------------------------------
>
> Key: JBIDE-14978
> URL: https://issues.jboss.org/browse/JBIDE-14978
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> I think it'd be nice to be able to have an eclipse-like version of http://mojo.codehaus.org/versions-maven-plugin/ allowing to detect and update new versions of maven plugins and dependencies.
> versions-maven-plugin would be invoked under the hood (if possible), so as to minimize code duplication.
> * versions:display-dependency-updates scans a project's dependencies and produces a report of those dependencies which have newer versions available.
> * versions:display-plugin-updates scans a project's plugins and produces a report of those plugins which have newer versions available.
> results could be displayed either as Warning markers in the pom.xml or in a dedicated view (similar to what a sonatype plugin did 2 years ago -don't remember the name).
> Quick-fixes would be available to actually update the versions to the latest ones. The feature should also be able to cope with versions defined as maven properties
> We should check if/how this feature is implemented in other IDEs (see what works or doesn't) from a UI standpoint.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-17237) when urls fails to download we end up with 0 size content
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17237?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-17237.
-------------------------------
Resolution: Won't Fix
No plans for 4.1.x maintenance. Already fixed in 4.2.x which is in maintenance mode already
> when urls fails to download we end up with 0 size content
> ---------------------------------------------------------
>
> Key: JBIDE-17237
> URL: https://issues.jboss.org/browse/JBIDE-17237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, project-examples
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Fix For: 4.1.3.Final
>
>
> due to a crash files end up being 0 sized resulting in this stack trace:
> STACK 0
> 18:14 java.util.zip.ZipException: zip file is empty
> 18:14 at java.util.zip.ZipFile.open(Native Method)
> 18:14 at java.util.zip.ZipFile.<init>(ZipFile.java:215)
> 18:14 at java.util.zip.ZipFile.<init>(ZipFile.java:145)
> 18:14 at java.util.jar.JarFile.<init>(JarFile.java:153)
> 18:14 at java.util.jar.JarFile.<init>(JarFile.java:117)
> 18:14 at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundle(DiscoveryRegistryStrategy.java:137)
> 18:14 at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundles(DiscoveryRegistryStrategy.java:126)
> 18:14 at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.onStart(DiscoveryRegistryStrategy.java:78)
> 18:14 at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725)
> 18:14 at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:125)
> files shoulnd't be put into cache before completely downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
[~mmurray] once you ack that one I'll resolve it.
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 8.1.0.Beta1
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2727:
-------------------------------
CDW qa_ack: + (was: ?)
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 8.1.0.Beta1
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months