[JBoss JIRA] (JBIDE-16219) Errors about Hibernate console configuration, with no easy way to resolve
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16219?page=com.atlassian.jira.plugi... ]
Pete Muir commented on JBIDE-16219:
-----------------------------------
If there was a quick fix for this, it would make the problem much less severe, as it would be trivial to sort it out.
> Errors about Hibernate console configuration, with no easy way to resolve
> -------------------------------------------------------------------------
>
> Key: JBIDE-16219
> URL: https://issues.jboss.org/browse/JBIDE-16219
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Environment: JBDS 7.0.1.GA
> Reporter: Pete Muir
> Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip
>
>
> In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem.
> I haven't tested whether newer dot-files will cause the problem, or not.
> Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated).
--
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-16217) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16217?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16217:
-------------------------------
Description:
For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0.
{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-SNAPSHOT;
{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 jbosstools-4.1.x 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 (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...]
was:
For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0.
{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.1.1.Beta1-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-SNAPSHOT;
{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 jbosstools-4.1.x 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 (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...]
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]
> ---------------------------------------------------------
>
> Key: JBIDE-16217
> URL: https://issues.jboss.org/browse/JBIDE-16217
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: livereload
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> 1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0.
> {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-SNAPSHOT;
> {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 jbosstools-4.1.x 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 (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...]
--
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-16219) Errors about Hibernate console configuration, with no easy way to resolve
by Pete Muir (JIRA)
Pete Muir created JBIDE-16219:
---------------------------------
Summary: Errors about Hibernate console configuration, with no easy way to resolve
Key: JBIDE-16219
URL: https://issues.jboss.org/browse/JBIDE-16219
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: hibernate
Environment: JBDS 7.0.1.GA
Reporter: Pete Muir
Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip
In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem.
I haven't tested whether newer dot-files will cause the problem, or not.
Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated).
--
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-16217) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16217?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16217:
-------------------------------
Description:
For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0.
{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.1.1.Beta1-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-SNAPSHOT;
{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 jbosstools-4.1.x 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 (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...]
was:
For JBIDE 4.1.1.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*.
Otherwise:
1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT;
2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1;
3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch;
4. Close (not resolve) this JIRA when done. [LiveReload]
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]
> ---------------------------------------------------------
>
> Key: JBIDE-16217
> URL: https://issues.jboss.org/browse/JBIDE-16217
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> 1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0.
> {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.1.1.Beta1-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-SNAPSHOT;
> {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 jbosstools-4.1.x 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 (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...]
--
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-2843) AngularJS Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2843:
-----------------------------
CDW devel_ack: ?
CDW qa_ack: ?
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
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-2843) AngularJS Usability
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-2843:
------------------------------
CDW pm_ack: + (was: ?)
Status: New (was: New)
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
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