[JBoss JIRA] (JBIDE-14726) Cannot run Cordova project on iOS Emulator
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14726?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14726:
--------------------------------------
Is this on a 32bit or 64bit Mac?
> Cannot run Cordova project on iOS Emulator
> ------------------------------------------
>
> Key: JBIDE-14726
> URL: https://issues.jboss.org/browse/JBIDE-14726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Darwin machydra.brq.redhat.com 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
> Reporter: Stefan Bunciak
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: screenshot.png
>
>
> {code}
> dyld: Library not loaded: @rpath/iPhoneSimulatorRemoteClient.framework/Versions/A/iPhoneSimulatorRemoteClient
> Referenced from: /Users/jbossqa/Downloads/eclipse/configuration/org.eclipse.osgi/bundles/264/data//ios-sim
> Reason: image not found
> {code}
> The files seems to be present:
> !screenshot.png|thumbnail!
--
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, 10 months
[JBoss JIRA] (JBIDE-14726) Cannot run Cordova project on iOS Emulator
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14726?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-14726:
------------------------------------
Assignee: Gorkem Ercan
> Cannot run Cordova project on iOS Emulator
> ------------------------------------------
>
> Key: JBIDE-14726
> URL: https://issues.jboss.org/browse/JBIDE-14726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Darwin machydra.brq.redhat.com 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: screenshot.png
>
>
> {code}
> dyld: Library not loaded: @rpath/iPhoneSimulatorRemoteClient.framework/Versions/A/iPhoneSimulatorRemoteClient
> Referenced from: /Users/jbossqa/Downloads/eclipse/configuration/org.eclipse.osgi/bundles/264/data//ios-sim
> Reason: image not found
> {code}
> The files seems to be present:
> !screenshot.png|thumbnail!
--
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, 10 months
[JBoss JIRA] (JBIDE-14729) Move to Kepler RC2
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-14729:
--------------------------------------
Summary: Move to Kepler RC2
Key: JBIDE-14729
URL: https://issues.jboss.org/browse/JBIDE-14729
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.1.0.Beta2
Use Kepler RC2 in TP 4.30.5.Alpha6-SNAPSHOT and build master against it.
--
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, 10 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12815:
------------------------------------
If you pull the latest from master, you'll see we only now include the Juno site and the Orbit site, which, I agree, is MORE that we actually need.
Hence, we opened JBIDE-14716 to restrict the TP used to build these into a very short list of Eclipse and Orbit deps.
Once the TP is created, we can remove these:
{code:title=https://github.com/nickboldt/jbosstools-locus/blob/master/pom.xml#L265}
<!-- needed to resolve org.junit and org.apache.ant, org.eclipse.osgi, etc. -->
<repository>
<id>JBoss Tools Target Platform Site</id>
<url>http://download.jboss.org/jbosstools/updates/${targetEclipseVersionName}/</url>
<layout>p2</layout>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
<!-- needed to resolve org.apache.commons.beanutils -->
<repository>
<id>Orbit Update Site</id>
<url>http://download.jboss.org/jbosstools/updates/requirements/orbit/S20130427...</url>
<layout>p2</layout>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
{code}
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 10 months
[JBoss JIRA] (JBIDE-6368) Should nest categories in update site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin... ]
Nick Boldt closed JBIDE-6368.
-----------------------------
Resolution: Won't Fix
+1. No point now that we have Central and Marketplace options.
> Should nest categories in update site
> -------------------------------------
>
> Key: JBIDE-6368
> URL: https://issues.jboss.org/browse/JBIDE-6368
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: updatesite
> Affects Versions: 3.2.x
> Reporter: John Verhaeg
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.0.Beta2
>
> Attachments: nested-categories-p2-update-site.png
>
>
> As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our update site. So, instead of having lots of sibling categories for the various tools in JBT alongside a sibling "All JBoss Tools" category, the latter should be promoted to a parent category for the others (dropping the "All" prefix). For example:
> - JBoss Tools
> - SOA Development
> - JBoss ESB Tools
> - Drools Core
> ...
> - Data Services
> - Hibernate
> - ModeShape
> - Smooks
> - Teiid Data Tools Connectivity
> - Teiid Designer Design-Time
> - Teiid Designer Runtime
> BTW, IMO having features in multiple categories blows. I don't like seeing this with other Eclipse projects either. Just my 2 cents.
--
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, 10 months
[JBoss JIRA] (JBIDE-6368) Should nest categories in update site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-6368:
--------------------------------------------
I consider this issue outdate and not relevant anymore - at least I can't recall why we would want this anymore ? Isn't this issue outdated now we got central ?
> Should nest categories in update site
> -------------------------------------
>
> Key: JBIDE-6368
> URL: https://issues.jboss.org/browse/JBIDE-6368
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: updatesite
> Affects Versions: 3.2.x
> Reporter: John Verhaeg
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.0.Beta2
>
> Attachments: nested-categories-p2-update-site.png
>
>
> As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our update site. So, instead of having lots of sibling categories for the various tools in JBT alongside a sibling "All JBoss Tools" category, the latter should be promoted to a parent category for the others (dropping the "All" prefix). For example:
> - JBoss Tools
> - SOA Development
> - JBoss ESB Tools
> - Drools Core
> ...
> - Data Services
> - Hibernate
> - ModeShape
> - Smooks
> - Teiid Data Tools Connectivity
> - Teiid Designer Design-Time
> - Teiid Designer Runtime
> BTW, IMO having features in multiple categories blows. I don't like seeing this with other Eclipse projects either. Just my 2 cents.
--
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, 10 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-12815:
---------------------------------------------
[~nickboldt] none of your comments explain why you need *all* and not why you need both kepler and juno. The sites are listed multiple times.
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 10 months