[JBoss JIRA] (JBIDE-13855) Invalid JPA Error message for Hibernate Joined inheritance
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13855?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-13855.
-------------------------------
Fix Version/s: (was: 4.1.x)
Resolution: Won't Fix
Given the fact that the issue is not reproduceable in 4.1.x, I'm resolving the issue as "Won't Fix"
> Invalid JPA Error message for Hibernate Joined inheritance
> ----------------------------------------------------------
>
> Key: JBIDE-13855
> URL: https://issues.jboss.org/browse/JBIDE-13855
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.0.0.Final
> Reporter: Cody Lerum
> Assignee: Koen Aers
>
> Discriminator column "DTYPE" cannot be resolved on table "Order_"
> In this case
> {code}
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @Table(name = "Order_")
> public abstract class Order implements Serializable
> {code}
> Hibernate does not require the use of a Discriminator column
--
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, 6 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-386:
------------------------------------------
All feedback incorporated in content spec. Marking as done for now.
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Attachments: MavenTools_contentspec.pdf
>
> Original Estimate: 1 hour
> Time Spent: 55 minutes
> Remaining Estimate: 0 minutes
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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, 6 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-386.
--------------------------------------
Resolution: Done
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Attachments: MavenTools_contentspec.pdf
>
> Original Estimate: 1 hour
> Time Spent: 55 minutes
> Remaining Estimate: 0 minutes
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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, 6 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-386:
-------------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Attachments: MavenTools_contentspec.pdf
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Martes Wigglesworth (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Martes Wigglesworth commented on JBIDE-15597:
---------------------------------------------
Thanks Andre.
On the first two, I can move now, but on your last recommendation, I was going to wait until I have a real variable populated for that type of change. (Since the length of the string will most likely need to be expanded with a scroll bar anyhow.)
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
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, 6 months
[JBoss JIRA] (JBDS-2787) prepare for JBDS 7.0.1 patch release
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2787?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2787:
---------------------------------------
[~nickboldt], should be:
"If you are using Oracle JDK or OpenJDK 1.7 update 40 ..."
"... please use an older Java developer kit ..."
^ OpenJDK is one word, name of community project
^ JDK as abbreviation can only be used to refer to Oracle's offering, so Java developer kit to refer to both Oracle's and OpenJDK's
> prepare for JBDS 7.0.1 patch release
> ------------------------------------
>
> Key: JBDS-2787
> URL: https://issues.jboss.org/browse/JBDS-2787
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.1.GA
>
> Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, jbds701ga-updates-avail.png, note-jdk7u40.png
>
>
> Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA:
> 1. branch jbosstools-central from 4.1.x to 4.1.0.x
> 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources)
> 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch
> 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg.,
> http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
> 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x
> 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0)
> 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration:
> {code}
> jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
> jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
> {code}
--
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, 6 months