[JBoss JIRA] (JBIDE-17764) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [BrowserSim]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17764?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-17764.
---------------------------------
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [BrowserSim]
> --------------------------------------------------------
>
> Key: JBIDE-17764
> URL: https://issues.jboss.org/browse/JBIDE-17764
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [BrowserSim]: 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 BrowserSim 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-17756) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [VPE]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17756?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-17756.
---------------------------------
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [VPE]
> -------------------------------------------------
>
> Key: JBIDE-17756
> URL: https://issues.jboss.org/browse/JBIDE-17756
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [VPE]: 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 VPE 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-17774) Search results on market place show inconsistent results
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17774?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17774:
------------------------------------
Searching for "jboss" and "jboss tools" both work. Why do you need to be able to search for "jbosstools" when the other two options work?
I've added "jbosstools" as both an anchor tag in the HTML and a keyword so maybe that will help in 24-48hrs whenever the database refreshes.
> Search results on market place show inconsistent results
> --------------------------------------------------------
>
> Key: JBIDE-17774
> URL: https://issues.jboss.org/browse/JBIDE-17774
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.2.0.Beta2
> Reporter: Arun Gupta
>
> In Luna, Help, Eclipse Marketplace, search on "jbosstools" shows "JBoss Tools (Kepler) 4.1.2 Final" and "JBoss Tools (Indigo) 3.3.2".
> Searching on "jboss" shows correct results.
> All the tools should be searchable on both "jboss" and "jbosstools".
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17763) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17763?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-17763.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Forge]
> ---------------------------------------------------
>
> Key: JBIDE-17763
> URL: https://issues.jboss.org/browse/JBIDE-17763
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Forge]: 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 Forge 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-17774) Search results on market place show inconsistent results
by Arun Gupta (JIRA)
Arun Gupta created JBIDE-17774:
----------------------------------
Summary: Search results on market place show inconsistent results
Key: JBIDE-17774
URL: https://issues.jboss.org/browse/JBIDE-17774
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: marketplace
Affects Versions: 4.2.0.Beta2
Reporter: Arun Gupta
In Luna, Help, Eclipse Marketplace, search on "jbosstools" shows "JBoss Tools (Kepler) 4.1.2 Final" and "JBoss Tools (Indigo) 3.3.2".
Searching on "jboss" shows correct results.
All the tools should be searchable on both "jboss" and "jbosstools".
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3072) Cannot update from JBDS 8.0.0.Beta1 to Beta2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3072?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3072.
----------------------------
Verified with these two versions of JBDS installed via installer, then adding nightly core site to available software sites, and Help > Check for updates:
{code}
jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar
and
jboss-devstudio-8.0.0.Beta2-v20140617-2058-B166-installer-standalone.jar
{code}
In both cases, Beta3 nightly version of Branded Product feature was presented when I checked for updates:
{code}
JBoss Developer Studio (Branded Product) 8.0.0.Beta3-v20140702-2244-B2265
{code}
Closing, fixed. Thx again to [~mickael_istria] for figuring out which file was causing the problem here. :)
> Cannot update from JBDS 8.0.0.Beta1 to Beta2
> --------------------------------------------
>
> Key: JBDS-3072
> URL: https://issues.jboss.org/browse/JBDS-3072
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 8.0.0.Beta2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.Beta3
>
> Attachments: beta2c-site-added.png, update-beta1-to-beta2c.png
>
>
> {code}
> Your original request has been modified.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Seam Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Portlet" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "Maven Integration for Eclipse JDT APT" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration (Experimental)" is already installed, so an update will be performed instead.
> "JBoss OpenShift Tools" is already installed, so an update will be performed instead.
> "JBoss Runtime Seam Detector" is already installed, so an update will be performed instead.
> "Seam 3 Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> Only one of the following can be installed at once:
> JBoss Developer Studio Project Examples 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.project.examples 8.0.0.Beta1-v20140408-2350-B93)
> JBoss Developer Studio Project Examples 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.project.examples 8.0.0.Beta2-v20140613-0252-B130)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta1-v20140408-2350-B93]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta2-v20140613-0252-B130]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Beta1-v20140408-2350-B93]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17773) Misaligned buttons
by Arun Gupta (JIRA)
Arun Gupta created JBIDE-17773:
----------------------------------
Summary: Misaligned buttons
Key: JBIDE-17773
URL: https://issues.jboss.org/browse/JBIDE-17773
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Reporter: Arun Gupta
4.2 beta2 + Luna
Adding a new WildFly server
Buttons to specify configuration file are misaligned, as shown in the snapshot.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months