[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16286:
----------------------------------------
I still can't reproduce the issue :(
I have tried:
1. Eclipse Kepler SR1 JavaEE
2. -Xmx2048m
3. JBT 4.1.1.Final installed from market place
4. m2e 1.15 installed from http://download.eclipse.org/technology/m2e/milestones/1.5
5. git@github.com:undertow-io/undertow.git imported into workspace as maven project
6. git@github.com:wildfly/wildfly.git imported into workspace as maven project
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: performance
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
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-16213) Prohibit deployments to AVDs and devices that do not support the minimum SDK version
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16213?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-16213:
-----------------------------------------
I noticed that ADT relies on the minimum SDK version if it were to automatically deploy to an emulator. Emulators with a lower SDK version are ignored.
> Prohibit deployments to AVDs and devices that do not support the minimum SDK version
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16213
> URL: https://issues.jboss.org/browse/JBIDE-16213
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Vineet Reynolds
>
> Based on the comment in JBIDE-16212 it would be useful to prohibit the "Run on Android emulator" (and possibly "Run on Android device") actions from attempting to perform a deployment of an APK on a device/AVD with a lower runtime version.
> The {{AndroidManifest.xml}} in the generated Android project had a min SDK version of 10. Deployments to AVDs/devices with a lower API version should not have been allowed. At the very least, we could display a more meaningful message instead of the current one: http://www.screencast.com/t/eG8pWIP9
--
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 updated JBIDE-16312:
------------------------------------
Description:
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.
was:
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.
> 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
>
> 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-16312) Support importing of Hybrid Mobile projects into workspace
by Vineet Reynolds (JIRA)
Vineet Reynolds created JBIDE-16312:
---------------------------------------
Summary: 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
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.
--
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:
-----------------------------------------
Also see JBIDE-16305 for the related documentation 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
>
> 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.
--
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