[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15197:
--------------------------------------
Export application wizard is now available. It does not support code signing which will be another task.
> Wizard for exporting mobile application out of a Hybrid Mobile project
> ----------------------------------------------------------------------
>
> Key: JBIDE-15197
> URL: https://issues.jboss.org/browse/JBIDE-15197
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.1.x, 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries.
> We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further.
--
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
13 years
[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15197.
----------------------------------
Resolution: Done
> Wizard for exporting mobile application out of a Hybrid Mobile project
> ----------------------------------------------------------------------
>
> Key: JBIDE-15197
> URL: https://issues.jboss.org/browse/JBIDE-15197
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.1.x, 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries.
> We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further.
--
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
13 years
[JBoss JIRA] (JBIDE-14534) Errors in Spring project archetypes
by Mrinal Thigale (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14534?page=com.atlassian.jira.plugi... ]
Mrinal Thigale commented on JBIDE-14534:
----------------------------------------
Hi
I solved this problem by changing it to :
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">
<deployment>
<dependencies>
<module name="org.hibernate" export="true"></module>
<module name="javax.faces.api" export="true"></module>
<module name="com.sun.jsf-impl" export="true"></module>
<module name="org.dom4j" export="true"></module>
<module name="org.hibernate.validator" export="true"></module>
</dependencies>
</deployment>
</jboss-deployment-structure>
> Errors in Spring project archetypes
> -----------------------------------
>
> Key: JBIDE-14534
> URL: https://issues.jboss.org/browse/JBIDE-14534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.1.x
>
>
> There are 2 errors in Spring Project archetype:
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> {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
13 years
[JBoss JIRA] (TOOLSDOC-378) Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-378?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-378:
-------------------------------------
Re: anchor... as long as the #Section_Title anchor label matches the Section_Title.html page filename, I'm not concerned the appearance of content having moved. Then again, as long as the CONTENT is good (with screenshots and examples) then the URL is secondary. It was just something I noticed which seemed like a bug, not a feature. ;)
Currently, both the html and html-single content uses the same anchor / page title:
https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
vs.
https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
Perhaps [~rob.stryker] or [~maxandersen] have an opinion on the doc w.r.t runtime detection setup? I was simply noticing that the instructions varied between the Install and User guides and that it seemed the 6.0 doc was more complete (again, because of screenshots/examples, which you've noted are forthcoming).
> Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6
> -------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-378
> URL: https://issues.jboss.org/browse/TOOLSDOC-378
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide
> Affects Versions: 4.1.0
> Reporter: Nick Boldt
> Assignee: Michelle Murray
>
> For JBDS 6 we had this, complete with screenshots and example content:
> https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio...
> Now, we have this:
> {code:title=https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.0/html-single/Getting_Started_Guide/index.html#Set_Up_a_Runtime_Server_Using_Server_Manager}
> 5.2. Set Up a Server Using Runtime Detection
> Servers can be set up from within the Java EE Web Project wizard. But for the purposes of exploring JBoss Developer Studio the procedure below sets up the server first.
> Procedure 5.2. Set Up a Server Using Runtime Detection
> Click Window→Preferences, expand JBoss Tools and select JBoss Tools Runtime Detection.
> Click Add.
> Select the directory containing the JBoss Enterprise Application Platform 6.0 or JBoss Enterprise Application Platform 6.1 installation and click OK. The directory is now scanned for application servers and JBoss Enterprise Application Platform 6.x found.
> To create a server for JBoss Enterprise Application Platform 6.x, ensure the jboss-eap-6.x check box is selected and click OK.
> Click Apply and click OK to close the Preferences window. The server is listed in the Servers tab.
> The server is initially shown in stopped mode. To start the server, right-click jboss-eap-6.x and click Start. After a short pause, the view switches to the Console tab and shows the startup output of the server.
> {code}
> AND we have this, which is more verbose but fails to mention any EAP 6.x specific examples.
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> Additionally, the html anchor "Set_Up_a_Runtime_Server_Using_Server_Manager" for "5.2 Set Up a Server Using Runtime Detection" doesn't match the content.
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> -----
> Could the content in both places be updated/merged to equally complete, and could screenshots be added too?
--
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
13 years
[JBoss JIRA] (JBTIS-118) Inclusion of Aries plugins in Locus causing console errors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-118?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-118:
----------------------------------
[~phantomjinx]: Can you rebuild and reinstall Teiid Designer as you did initially, and report back if the above changes have helped to resolve the missing packages? If not, can you provide steps to reproduce the console messages?
> Inclusion of Aries plugins in Locus causing console errors
> ----------------------------------------------------------
>
> Key: JBTIS-118
> URL: https://issues.jboss.org/browse/JBTIS-118
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.0.Final
> Reporter: Paul Richardson
> Assignee: Paul Leacu
>
> Errors generated in the console when executing Eclipse IDE based on JBT-IS base.target target platform. This occurred while executing Teiid Designer, which makes no use of the Aries plugins.
> {code}
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.174
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.175
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.177
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.felix.configadmin_1.4.0.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)".
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.280
> !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.281
> !MESSAGE Bundle org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT [89] was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.281
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.284
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> {code}
> Understand that Fuse is the main beneficiary of these plugins. Are the Aries plugins essential to the Fuse project (or any other projects)?
> The missing imports all relate to the osgi jmx specification, which is implemented by the [Eclipse Gemini|http://eclipse.org/gemini] project. Can / should its plugins be included to satisfy the import errors or does Fuse rely on another implementation?
--
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
13 years
[JBoss JIRA] (JBTIS-118) Inclusion of Aries plugins in Locus causing console errors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-118?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-118:
----------------------------------
Rebuilt:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
Resulting site:
http://download.jboss.org/jbosstools/updates/integration/locus/ (1.0.0.Final-B31)
(Note that the previous build in /1.0.0.x/ has been renamed to /1.0.0.CR2-B29/ )
> Inclusion of Aries plugins in Locus causing console errors
> ----------------------------------------------------------
>
> Key: JBTIS-118
> URL: https://issues.jboss.org/browse/JBTIS-118
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.0.Final
> Reporter: Paul Richardson
> Assignee: Paul Leacu
>
> Errors generated in the console when executing Eclipse IDE based on JBT-IS base.target target platform. This occurred while executing Teiid Designer, which makes no use of the Aries plugins.
> {code}
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.174
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.175
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.177
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.felix.configadmin_1.4.0.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)".
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.280
> !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.281
> !MESSAGE Bundle org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT [89] was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.281
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.284
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> {code}
> Understand that Fuse is the main beneficiary of these plugins. Are the Aries plugins essential to the Fuse project (or any other projects)?
> The missing imports all relate to the osgi jmx specification, which is implemented by the [Eclipse Gemini|http://eclipse.org/gemini] project. Can / should its plugins be included to satisfy the import errors or does Fuse rely on another implementation?
--
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
13 years
[JBoss JIRA] (JBIDE-15191) Frozen dynamic web project wizard
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15191?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15191:
---------------------------------------
What kind of environment you use:
1. JVM version
2. Linux version
3. Is file system local or NFS?
Looking in dump it seems stuck in native call getting file attributes.
> Frozen dynamic web project wizard
> ---------------------------------
>
> Key: JBIDE-15191
> URL: https://issues.jboss.org/browse/JBIDE-15191
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives
> Affects Versions: 4.1.0.CR1
> Reporter: Jiri Peterka
> Priority: Critical
> Fix For: 4.1.1.Final
>
> Attachments: dump.txt, frozen-wizard.png
>
>
> IDE has frozen, when creating Dynamic web project, thread dump attached. Seeing some archives callings there.
--
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
13 years
[JBoss JIRA] (JBIDE-15256) Include tycho-source-feature-plugin and tycho-p2-plugin into parent/pom.xml/build/pluginManagement
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15256?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15256:
---------------------------------------
It is moving in pluginManagenent section not plugins sections and it means it is not going to be applied to every module.
Just try the PR and see if it works.
> Include tycho-source-feature-plugin and tycho-p2-plugin into parent/pom.xml/build/pluginManagement
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15256
> URL: https://issues.jboss.org/browse/JBIDE-15256
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.2.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.0.Alpha1
>
>
> Currently every feature's pom.xml includes the same code, which is code-duplication issue.
> {code}
> <plugin>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-source-feature-plugin</artifactId>
> <version>${tychoExtrasVersion}</version>
> <executions>
> <execution>
> <id>source-feature</id>
> <phase>package</phase>
> <goals>
> <goal>source-feature</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-p2-plugin</artifactId>
> <version>${tychoVersion}</version>
> <executions>
> <execution>
> <id>attached-p2-metadata</id>
> <phase>package</phase>
> <goals>
> <goal>p2-metadata</goal>
> </goals>
> </execution>
> </executions>
> </plugin>{code}
> It should be included into pluginManagement section of parent/pom.xml instead and that would reduce code duplication to
> {code}<plugin>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-source-feature-plugin</artifactId>
> </plugin>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-p2-plugin</artifactId>
> </plugin>{code}
> in every feture's pom.xml file.
> More over code above could be moved to to features/pom.xml as
> {code}<build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-source-feature-plugin</artifactId>
> </plugin>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-p2-plugin</artifactId>
> </plugin>
> </plugins>
> </build>{code}
> that would let keep pom.xml for every feature even cleaner.
--
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
13 years