[JBoss JIRA] (JBDS-2755) For JBDS 7.1.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2755?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2755:
----------------------------------
Built locally successfully:
{code} mvn clean verify -Dtpc.version=4.31.0.Alpha1{code}
Branch jbosstools-4.1.1.Alpha1x created.
> For JBDS 7.1.0.Alpha1: Code Freeze + Branch
> -------------------------------------------
>
> Key: JBDS-2755
> URL: https://issues.jboss.org/browse/JBDS-2755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 7.1.0.Alpha1
>
>
> For JBDS 7.1.0.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.
> [Search for all 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, 7 months
[JBoss JIRA] (JBIDE-14406) Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
by Randall Hauch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14406?page=com.atlassian.jira.plugi... ]
Randall Hauch commented on JBIDE-14406:
---------------------------------------
As for the original problem, you need to provide some Java code that shows what you're doing. For example, in the above pseudo-code, you don't say that you're saving your session. This is very important, because JCR queries _never_ see the unsaved transient content/changes in your session, and _only_ see what has been saved/persisted.
> Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
> ------------------------------------------------------------
>
> Key: JBIDE-14406
> URL: https://issues.jboss.org/browse/JBIDE-14406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-platform, modeshape
> Affects Versions: 3.2.0.Final
> Environment: OSX 10.8.3 - JVM 1.7 - eclipse helios - Modeshape 3.2.0.Final
> Reporter: noah totti
> Assignee: Dan Florian
>
> Don't know if is a bug or I miss something, I use default configuration for in memory repo, this is the behavior:
> Create a tree of 3 node: '/a/b/c'
> Create a node 'tmp' under the root
> Query with SQL2 to get all ISCHILDNODE under path '/a/b' return node 'c'
> Move node 'b' under '/tmp'
> Call getNodes() on node '/tmp/b' return node 'c'
> Query with SQL2 to get all ISCHILDNODE under path '/tmp/b' return no node
> Query with SQL2 to get all ISCHILDNODE under path '/a/b' still return node 'c'
> Same behavior with ISDESCENDANTNODE.
> To return children with ISCHILDNODE or ISDESCENDANTNODE query, you have to update the children
--
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, 7 months
[JBoss JIRA] (JBIDE-14406) Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
by Randall Hauch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14406?page=com.atlassian.jira.plugi... ]
Randall Hauch commented on JBIDE-14406:
---------------------------------------
This sounds like it might be logged against the wrong JIRA project. ModeShape Tools is an Eclipse-based tooling for accessing a remote ModeShape, and therefore the JCR API cannot be involved.
If this is the case, then this needs to be moved to the MODE project (not JBIDE).
> Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
> ------------------------------------------------------------
>
> Key: JBIDE-14406
> URL: https://issues.jboss.org/browse/JBIDE-14406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-platform, modeshape
> Affects Versions: 3.2.0.Final
> Environment: OSX 10.8.3 - JVM 1.7 - eclipse helios - Modeshape 3.2.0.Final
> Reporter: noah totti
> Assignee: Dan Florian
>
> Don't know if is a bug or I miss something, I use default configuration for in memory repo, this is the behavior:
> Create a tree of 3 node: '/a/b/c'
> Create a node 'tmp' under the root
> Query with SQL2 to get all ISCHILDNODE under path '/a/b' return node 'c'
> Move node 'b' under '/tmp'
> Call getNodes() on node '/tmp/b' return node 'c'
> Query with SQL2 to get all ISCHILDNODE under path '/tmp/b' return no node
> Query with SQL2 to get all ISCHILDNODE under path '/a/b' still return node 'c'
> Same behavior with ISDESCENDANTNODE.
> To return children with ISCHILDNODE or ISDESCENDANTNODE query, you have to update the children
--
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, 7 months