[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16312:
--------------------------------------
OK improved the description of JBIDE-13649 to include the HMT generated projects that are suffering from amnesia. Closing as duppo.
> Support importing of Hybrid Mobile projects into workspace
> ----------------------------------------------------------
>
> Key: JBIDE-16312
> URL: https://issues.jboss.org/browse/JBIDE-16312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures.
> If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated.
> It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu.
--
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, 3 months
[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16696?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16696:
---------------------------------------
{quote}
By default, all relative paths are relative to current directory. Scanning could not fix that.
{quote}
Shrinkwrap resolver could search for relative paths in the current working directory and, in case the requested path isn't found, in the directory mentioned in the shrinkwrap.project.home system property.
Arquillian Eclipse would set the shrinkwrap.project.home property to the project's home before executing a deployment method.
{quote}
However, what we could do is to use Maven.configureResolverViaPlugin(). This way Eclipse/JBDS will need just to setup a few system properties (pom.xml file, settings.xml file, active profiles etc) and user does not have to handle with it anymore.
{quote}
That won't solve the issue if a user uses the loadPomFromFile method.
BTW, the maven.execution.pom-file property isn't mentioned in the documentation.
{quote}
where did you got your pom.xml file? Depchain should be used, see adding shrinkwrap resolvers to your project at - https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc - this is also related to missing Service.
{quote}
I have used the code described in the description of this jira.
> IllegalStateException when Arquillian deployment uses Maven resolver
> --------------------------------------------------------------------
>
> Key: JBIDE-16696
> URL: https://issues.jboss.org/browse/JBIDE-16696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
>
> In an Arquillian test class, if the @Deployment method uses the ShrinkWrap Maven Resolver API, the method will be marked with the following warning and the Arquillian Cruiser view does not show the deployment:
> {noformat}
> java.lang.IllegalStateException: There is more then a one service for serviceClass org.jboss.shrinkwrap.resolver.api.maven.MavenResolverSystem(project=arquillian-bug-test)
> {noformat}
> There is no stack trace to indicate how the problem might be happening. At first, I thought this might be a ShrinkWrap bug, but this exception doesn't occur when I actually run the test. Eclipse shows only one implementation of MavenResolverSystem on the classpath.
> Example test class to reproduce the problem:
> {code}
> package test;
> import org.jboss.arquillian.container.test.api.Deployment;
> import org.jboss.arquillian.junit.Arquillian;
> import org.jboss.shrinkwrap.api.Archive;
> import org.jboss.shrinkwrap.api.ShrinkWrap;
> import org.jboss.shrinkwrap.api.spec.WebArchive;
> import org.jboss.shrinkwrap.resolver.api.maven.Maven;
> import org.junit.Test;
> import org.junit.runner.RunWith;
> @RunWith(Arquillian.class)
> public class ARQJBTBugTest {
> @Test
> public void test() {
>
> }
>
> @Deployment
> public static Archive<?> createDeployment() {
> return ShrinkWrap.create(WebArchive.class)
> .addAsLibraries(Maven.resolver()
> .loadPomFromFile("pom.xml")
> .importRuntimeDependencies()
> .resolve()
> .withTransitivity()
> .asFile());
> }
>
> }
> {code}
> And the POM to go with it:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.lapis.throwaway</groupId>
> <artifactId>arquillian-bug-test</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <packaging>war</packaging>
> <properties>
> <project.build.sourceEncoding>
> UTF-8
> </project.build.sourceEncoding>
> <version.arquillian_core>1.1.3.Final</version.arquillian_core>
> </properties>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.10</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.shrinkwrap.resolver</groupId>
> <artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId>
> <scope>test</scope>
> </dependency>
> </dependencies>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>${version.arquillian_core}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.5.1</version>
> <configuration>
> <source>1.7</source>
> <target>1.7</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.12</version>
> </plugin>
> </plugins>
> </build>
> </project>
> {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, 3 months
[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-16312.
----------------------------------
Resolution: Duplicate Issue
> Support importing of Hybrid Mobile projects into workspace
> ----------------------------------------------------------
>
> Key: JBIDE-16312
> URL: https://issues.jboss.org/browse/JBIDE-16312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures.
> If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated.
> It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu.
--
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, 3 months
[JBoss JIRA] (JBIDE-13649) Import cordova-cli created projects
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13649?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-13649:
---------------------------------
Description:
We should be able to import a project that was generated by cordova-cli tools and work on it.
Optionally, project should be kept compatible with cordova-cli so that a developer can use it at any time.
Also the import feature should be able to import an existing Hybrid mobile project that does not have a .project file.
was:We should be able to import a project that was generated by cordova-cli tools and work on it. Moreover project should be kept compatible with cordova-cli so that a developer can use it at any time.
> Import cordova-cli created projects
> -----------------------------------
>
> Key: JBIDE-13649
> URL: https://issues.jboss.org/browse/JBIDE-13649
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We should be able to import a project that was generated by cordova-cli tools and work on it.
> Optionally, project should be kept compatible with cordova-cli so that a developer can use it at any time.
> Also the import feature should be able to import an existing Hybrid mobile project that does not have a .project file.
--
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, 3 months
[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-16312:
-----------------------------------------
The intention was to allow import of HMT projects that were once created in JBDS. Right now, I need to store the .project file in SCM (to retain the HMT nature), and {{import as an existing project}} (supplying the root directory). From the point of view of an end-user it would be great to find an "Import as HMT project" in the Eclipse Import dialog.
It does look similar to importing projects with the structure generated by Cordova-CLI. You could mark this as a duplicate of JBIDE-13649 if both of these issues would be served by the same feature.
> Support importing of Hybrid Mobile projects into workspace
> ----------------------------------------------------------
>
> Key: JBIDE-16312
> URL: https://issues.jboss.org/browse/JBIDE-16312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures.
> If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated.
> It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu.
--
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, 3 months
[JBoss JIRA] (JBDS-2839) Hybrid/Cordova Usability
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2839?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan commented on JBDS-2839:
------------------------------------
I want to make sure that we are covering everything listed on the description.
[~burrsutter] Can you detail the goal with 5.) Import projects? Looking at ticket monster does not give me much clues. It now has a .project file it can be imported into Eclipse as an existing project. Is this request for importing projects that do not have .project file. Assuming that is the case, do we want to be able to import Cordova CLI created projects (JBIDE-13649) or anything that has a bunch of web artifacts (JBIDE-16312)?
6 and 7) what exactly "_works with_" mean? One may interpret this a request for templates that uses JQM and/or Angular. Or there is something in the current template, which is the [cordova hello world | https://github.com/apache/cordova-app-hello-world] with branding, that prevents their use. If it is latter than we just need to fix the existing template.
> Hybrid/Cordova Usability
> ------------------------
>
> Key: JBDS-2839
> URL: https://issues.jboss.org/browse/JBDS-2839
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Priority: Blocker
>
> Areas to review:
> 1) Auto setup of the LiveReload Server (JBIDE-16134)
> 2) Run As on Android Device - often fails to find the plugged in device - need better instructions on now to "debug" this issue (adb devices, etc)
> 3) Add project wizard to JBoss Central
> 4) Promote from Tech Preview
> 5) Import an existing Cordova project (e.g. TicketMonster: WFK2-168)
> 6) New project works with jQuery Mobile Palette + Backbone
> 7) New project works with AngularJS-based project
> 8) Install Cordova Plugin dialog is slow for scrolling the list of plugins, slow for typing in the project field - focus should not default to project field when the dialog is launched from a specific project (right-click on plugins, Install Cordova Plugin)
--
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, 3 months
[JBoss JIRA] (JBDS-2840) Java 8
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2840?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2840:
------------------------------------
So - users must run the IDE with Java 7?
> Java 8
> ------
>
> Key: JBDS-2840
> URL: https://issues.jboss.org/browse/JBDS-2840
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, upstream
> Reporter: Burr Sutter
> Priority: Critical
> Labels: JBDS80_Approved_Scope
>
> Support for Java 8
> - The IDE running with Java 8 on all OS platforms
> - The capabilities in Eclipse Luna for code editing/support
> - EAP 6.3 with Java 8 (start, stop,deploy, debug, etc)
--
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, 3 months
[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16312:
--------------------------------------
An Android project or a maven project has a defined runtime structure. In the case of Cordova every platform has a different structure so it is hard to come up with a logic to decide on what to import. The only project structure related to Cordova is Cordova CLIs structure. If this is a request to import CLI projects I will mark this as a duplicate of JBIDE-13649.
If the intention is to be able to create a cordova project from a bunch of web artifacts and optionally a config.xml then this is a new and large request.
> Support importing of Hybrid Mobile projects into workspace
> ----------------------------------------------------------
>
> Key: JBIDE-16312
> URL: https://issues.jboss.org/browse/JBIDE-16312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures.
> If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated.
> It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu.
--
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, 3 months
[JBoss JIRA] (JBIDE-16477) Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16477?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-16477.
-----------------------------------
Verified in JBDS 7.1.1 GA-v20140303-1841-B672
> Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16477
> URL: https://issues.jboss.org/browse/JBIDE-16477
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.Final
> Environment: Eclipse 4.3.1 EE bundle + JBoss Tools 4.1.1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.1.2.CR1
>
>
> JAX-RS resource methods are often declared in classes, but it is also valid to declare them in interfaces. Methods in classes have to be explicitly declared public (and that's what this validator method checks for -- good), but methods in Java interfaces are implicitly public; explicitly writing "public" just adds clutter.
> The JAX-RS validator does discover resource methods in interfaces and validates them (good), but if the methods aren't explicitly labelled public then a couple of minor bugs surface in this validator method:
> (1) It adds a RESOURCE_METHOD_NO_PUBLIC_MODIFIER problem marker, and
> (2) The Description that's displayed for the marker is "The method '{0}' should be public.", i.e. the "{0}" isn't replaced with a method name
> (Yes, I can certainly dodge this by changing the "Missing 'public' method modifier" preference from Warning to Ignore, but I'm definitely a fan of having the validators there to save me from myself).
--
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, 3 months