[JBoss JIRA] (JBIDE-16232) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16232?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-16232.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Hibernate]
> --------------------------------------------------------
>
> Key: JBIDE-16232
> URL: https://issues.jboss.org/browse/JBIDE-16232
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Hibernate]: 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.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. 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 Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2857) Add OS X Mavericks to the support matrix
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2857:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Add OS X Mavericks to the support matrix
> ----------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2857) Add OS X Mavericks to the support matrix
by Martin Malina (JIRA)
Martin Malina created JBDS-2857:
-----------------------------------
Summary: Add OS X Mavericks to the support matrix
Key: JBDS-2857
URL: https://issues.jboss.org/browse/JBDS-2857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: requirements
Affects Versions: 7.1.0.CR1
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
I know this comes very late, so you may want to just push this to 8.0.0 immediately.
However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16252) Deployed module on OpenShift (server adapter) should be associated with '/'
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16252?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16252:
---------------------------------------------
I cannot reproduce this. When I select the magic project/module under the server it uses /
That is how we made it a while back for openshift.
> Deployed module on OpenShift (server adapter) should be associated with '/'
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16252
> URL: https://issues.jboss.org/browse/JBIDE-16252
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
>
> The deployed project on OpenShift is a module of the OpenShift Application Server Adapter.
> When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'.
> Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/
> Furthermore, when the user is used to select the module under a classic JBossAS 7 server adapter, he gets confused if he needs to select the server for the OpenShift deployed application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16260) Typo in JBoss Central Software/Update tab: plugins > plug-ins
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-16260:
---------------------------------------
Summary: Typo in JBoss Central Software/Update tab: plugins > plug-ins
Key: JBIDE-16260
URL: https://issues.jboss.org/browse/JBIDE-16260
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.1.1.CR1
Reporter: Michelle Murray
JBIDE-15874 missed a plug-in typo
Open JBoss Central, Software/Update tab
In Find field, type ABC
Table text shows 'There are no matching *plugins*. Please clear the filter text or try again later'
Should read: 'There are no matching *plug-ins*.'
And should end with fullstop: '... try again later*.*'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months