[JBoss JIRA] (JBIDE-13643) Create/Modify XCode projects for Apache Cordova
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13643?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-13643:
--------------------------------------
resolving.... This is implemented now
> Create/Modify XCode projects for Apache Cordova
> -----------------------------------------------
>
> Key: JBIDE-13643
> URL: https://issues.jboss.org/browse/JBIDE-13643
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Aerogear-hybrid tools should be able to generate XCode projects and modify them. This is needed for
> 1. Generate a temporary XCode Cordova project to build and run
> 2. Export a XCode Cordova project that will be used on XCode
> 3. Modify existing Cordova projects in response to changes/refactorings
--
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, 11 months
[JBoss JIRA] (JBIDE-13643) Create/Modify XCode projects for Apache Cordova
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13643?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-13643:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
> Create/Modify XCode projects for Apache Cordova
> -----------------------------------------------
>
> Key: JBIDE-13643
> URL: https://issues.jboss.org/browse/JBIDE-13643
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Aerogear-hybrid tools should be able to generate XCode projects and modify them. This is needed for
> 1. Generate a temporary XCode Cordova project to build and run
> 2. Export a XCode Cordova project that will be used on XCode
> 3. Modify existing Cordova projects in response to changes/refactorings
--
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, 11 months
[JBoss JIRA] (JBIDE-14387) Extract hybrid Aerogear project from JEE project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14387?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-14387:
------------------------------------
Assignee: Gorkem Ercan
> Extract hybrid Aerogear project from JEE project
> ------------------------------------------------
>
> Key: JBIDE-14387
> URL: https://issues.jboss.org/browse/JBIDE-14387
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Sebastien Blanc
> Assignee: Gorkem Ercan
>
> Often, especially when using Forge scaffolding facilities, you started with a complete JEE project. After that, you may want to start an hybrid project.
> It should be nice if we had an option (right clicking on the JEE project) to extract the src/main/webapp folder and create a new Aerogear Hybrid project and feed the www folder.
> As a bonus, there should be an option to keep in sync the webapp folder from the JEE project and the www folder from the hybrid project.
>
--
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, 11 months
[JBoss JIRA] (JBIDE-14406) Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
by noah totti (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14406?page=com.atlassian.jira.plugi... ]
noah totti updated JBIDE-14406:
-------------------------------
Issue Type: Bug (was: Feature Request)
> 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: 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, 11 months
[JBoss JIRA] (JBIDE-14406) Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
by noah totti (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14406?page=com.atlassian.jira.plugi... ]
noah totti updated JBIDE-14406:
-------------------------------
Description:
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
was:
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.
> Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
> ------------------------------------------------------------
>
> Key: JBIDE-14406
> URL: https://issues.jboss.org/browse/JBIDE-14406
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: 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, 11 months
[JBoss JIRA] (JBIDE-14406) Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
by noah totti (JIRA)
noah totti created JBIDE-14406:
----------------------------------
Summary: Sql2 query ISCHILDNODE / ISDESCENDANTNODE after session.move
Key: JBIDE-14406
URL: https://issues.jboss.org/browse/JBIDE-14406
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: 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.
--
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, 11 months
[JBoss JIRA] (JBIDE-14405) WaitJob inside ECFTransport is not safe and is impossible to be interrupted
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14405:
-----------------------------------
Summary: WaitJob inside ECFTransport is not safe and is impossible to be interrupted
Key: JBIDE-14405
URL: https://issues.jboss.org/browse/JBIDE-14405
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
The WaitJob in ECFTransport is not safe and is impossible to be interrupted. This has to do with eclipse's internal implementation of Job.join(), however there are ways to work around it.
The internal implementation of Job.join() has special logic IGNORING interrupts specifically for the case where the job being joined requires Display.syncExec implementations. Since WaitJob does not require any UI or syncExec, we can work around this by carefully implementing our own join-like method.
See also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=293312
--
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, 11 months