[JBoss JIRA] (JBIDE-16352) iOS bundle identifier not escaped when exporting project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16352?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-16352:
------------------------------------
Assignee: Gorkem Ercan (was: Max Rydahl Andersen)
> iOS bundle identifier not escaped when exporting project
> --------------------------------------------------------
>
> Key: JBIDE-16352
> URL: https://issues.jboss.org/browse/JBIDE-16352
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Tadeas Kriz
> Assignee: Gorkem Ercan
>
> When the project is exported as native xcode project, and the application name contains for example a space, this space is then exported in the bundle identifier, which then makes the compilation of the project fail. For example, if the name is "My Application", the bundle ID becomes "My Application" as well, even though it should be for example "MyApplication" (underscore is illegal character as well).
--
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, 5 months
[JBoss JIRA] (JBIDE-16352) iOS bundle identifier not escaped when exporting project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16352?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16352:
--------------------------------------
This also effects the "Run On iOS Simulator" feature as well.
> iOS bundle identifier not escaped when exporting project
> --------------------------------------------------------
>
> Key: JBIDE-16352
> URL: https://issues.jboss.org/browse/JBIDE-16352
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Tadeas Kriz
> Assignee: Gorkem Ercan
>
> When the project is exported as native xcode project, and the application name contains for example a space, this space is then exported in the bundle identifier, which then makes the compilation of the project fail. For example, if the name is "My Application", the bundle ID becomes "My Application" as well, even though it should be for example "MyApplication" (underscore is illegal character as well).
--
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, 5 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2852:
------------------------------------
13) And... drop and recreate the tables
14) And... delete the contents of the tables
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
>
> Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge.
> Forge is involved as it can generate entities from schema
> Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy
> Persistence.xml may needed to be tweaked for the datasource
> End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed.
> What happens when a project that needs a database connection is imported into the IDE?
> This was partially addressed with
> https://issues.jboss.org/browse/JBIDE-15263
> Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow.
--
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, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-2635 at 1/24/14 2:14 PM:
--------------------------------------------------------------
{quote}Okey, but we would need similar mechanisms that izpack provides. splashscreen, legal text, panels etc.{quote}
Current solution is a hack into IzPack which runs p2Director app as external process, reads process output, analyze it and reports progress in IzPack panel. It also checks process return code to see if it is finished correctly or failed. All this is working fine in most cases but:
1. It is slower than just running installation process inside the same JVM
2. It doesn't support Unicode names for target folder under windows (see JBDS-2260)
3. It is a hack done in forked class that needs migration every time we migrate to new IzPack.
Why Eclipse RCP? Because we know how eclipse works and can match every feature IzPack has like:
1. Multi-platform support
2. Panels are just wizards steps
3. What is going to be installed should be provided as p2repository instead of IzPack packs (additional files can be delivered as root file features (?))
4. UI translation do different languages (can be done, but we're not using it)
5. Splashscreen
What is missing in eclipse (n):
1. Support for creating Groups and Launchers in menu under windows and linux
2. Native installers (but we don't use it)
3. Launching eclipse RCP from jar file
{quote}Just trying to understand what the value we get by reimplementing these ?{quote}
We would have everything eclipse based, even installer (y)
Installation would be faster (y)
Installer would be smaller if packed pack200 (y)
We can handle JBDS-2874 and make BYOE happened (y)
was (Author: dgolovin):
{quote}Okey, but we would need similar mechanisms that izpack provides. splashscreen, legal text, panels etc.{quote}
Current solution is a hack into IzPack which runs p2Director app as external process, reads process output, analyze it and reports progress in IzPack panel. It also checks process return code to see if it is finished correctly or failed. All this is working fine in most cases but:
1. It is slower than just running installation process inside the same JVM
2. It doesn't support Unicode names for target folder under windows (see JBDS-2260)
3. It is a hack done in forked class that needs migration every time we migrate to new IzPack.
Why Eclipse RCP? Because we know how eclipse works and can match every feature IzPack has like:
1. Multi-platform support
2. Panels are just wizards steps
3. What is going to be installed should be provided as p2repository instead of IzPack packs (additional files can be delivered as root file features (?))
4. UI translation do different languages (can be done, but we're not using it)
5. Splashscreen
What is missing in eclipse (n):
1. Support for creating Groups and Launchers in menu under windows and linux
2. Native installers (but we don't use it)
3. Launching eclipse RCP from jar file
{quote}Just trying to understand what the value we get by reimplementing these ?{quote}
We would have everything eclipse based, even installer (y)
Installation would be faster (y)
Installer would be smaller if packed pack200 (y)
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {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, 5 months
[JBoss JIRA] (JBDS-2492) JBDS Icon problems in Gnome 3.6 Application Switcher
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2492?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2492:
--------------------------------
Fix Version/s: 7.1.1.GA
> JBDS Icon problems in Gnome 3.6 Application Switcher
> ----------------------------------------------------
>
> Key: JBDS-2492
> URL: https://issues.jboss.org/browse/JBDS-2492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 6.0.1.GA
> Environment: Ubuntu Linux x86_64
> Gnome 3.6.0
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: app-switcher.png, appnamefixed.png, appnamexfce.png
>
>
> Problems are:
> # Icon Resolution is to low
> # No application name under icon
> !app-switcher.png!
--
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, 5 months
[JBoss JIRA] (JBDS-2492) JBDS Icon problems in Gnome 3.6 Application Switcher
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2492?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2492:
-------------------------------------
Should be fixed in 7.1.x Stream as well
> JBDS Icon problems in Gnome 3.6 Application Switcher
> ----------------------------------------------------
>
> Key: JBDS-2492
> URL: https://issues.jboss.org/browse/JBDS-2492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 6.0.1.GA
> Environment: Ubuntu Linux x86_64
> Gnome 3.6.0
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: app-switcher.png, appnamefixed.png, appnamexfce.png
>
>
> Problems are:
> # Icon Resolution is to low
> # No application name under icon
> !app-switcher.png!
--
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, 5 months
[JBoss JIRA] (JBDS-2879) org.eclipse.core.net bundle is not included in p2director
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2879?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2879:
--------------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> org.eclipse.core.net bundle is not included in p2director
> ---------------------------------------------------------
>
> Key: JBDS-2879
> URL: https://issues.jboss.org/browse/JBDS-2879
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
>
> Missing bundle triggers ClassNotFoundExceptions during installation:
> {code}!ENTRY org.eclipse.ecf.provider.filetransfer 4 0 2014-01-16 16:34:37.018
> !MESSAGE org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.provider.filetransfer;code=4;message=Warning: Platform proxy API not available;severity2;exception=java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService;children=[]]
> !STACK 0
> java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setupProxies(AbstractRetrieveFileTransfer.java:946)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:878)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:668)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:590)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:287)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:267)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:208)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:162)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.core.net.proxy.IProxyService cannot be found by org.eclipse.ecf.provider.filetransfer_3.2.0.v20130604-1622
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 18 more{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, 5 months
[JBoss JIRA] (JBDS-2879) org.eclipse.core.net bundle is not included in p2director
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2879?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2879:
-------------------------------------
It doesn't affect installation result, so installer just works, but log looks ugly.
I agree it worth to fix in 7.1.x as well.
> org.eclipse.core.net bundle is not included in p2director
> ---------------------------------------------------------
>
> Key: JBDS-2879
> URL: https://issues.jboss.org/browse/JBDS-2879
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
>
> Missing bundle triggers ClassNotFoundExceptions during installation:
> {code}!ENTRY org.eclipse.ecf.provider.filetransfer 4 0 2014-01-16 16:34:37.018
> !MESSAGE org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.provider.filetransfer;code=4;message=Warning: Platform proxy API not available;severity2;exception=java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService;children=[]]
> !STACK 0
> java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setupProxies(AbstractRetrieveFileTransfer.java:946)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:878)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:668)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:590)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:287)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:267)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:208)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:162)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.core.net.proxy.IProxyService cannot be found by org.eclipse.ecf.provider.filetransfer_3.2.0.v20130604-1622
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 18 more{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, 5 months