[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15934:
---------------------------------------------
[~gercan] mentioned this commit was done on master: https://github.com/jbosstools/jbosstools-aerogear/commit/3909ee743c854286...
if that works we should get it in.
> Run on Android Device does not work on OS X
> -------------------------------------------
>
> Key: JBIDE-15934
> URL: https://issues.jboss.org/browse/JBIDE-15934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: jbds711
> Fix For: 4.1.2.Final
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16286:
---------------------------------------------
JBIDE-16351 probably plays part in slow wildfly and other projects builds - but its not the full story.
> 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, maven
> 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, full-bundle-listing.txt, 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, 5 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16351:
----------------------------------------
Priority: Critical (was: Major)
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16351:
---------------------------------------------
I've added 4.1.2 as fix version - [~snjeza] can you create PR for the branch too or does this apply equally well ?
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16351:
----------------------------------------
Fix Version/s: 4.1.2.Final
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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-16249) Offline groovy script not working - FileNotFoundException
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16249?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16249:
----------------------------------------
Fix Version/s: 4.1.2.Final
(was: 4.1.1.Final)
> Offline groovy script not working - FileNotFoundException
> ----------------------------------------------------------
>
> Key: JBIDE-16249
> URL: https://issues.jboss.org/browse/JBIDE-16249
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0.CR1a B560
> OS X
> Groovy Version: 2.1.8 JVM: 1.7.0_45 Vendor: Oracle Corporation OS: Mac OS X (installed via mac ports)
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.1.2.Final
>
> Attachments: groovy.log
>
>
> I tried to run the offline examples groovy script today (Preferences -> JBoss Tools -> Project Examples -> Offline Support).
> When I ran the script I saw a couple of errors along the way, see at the end of email. I was told that it could have to do with WFK 2.4 not being available in the online repo yet.
> But ultimately the script failed this exception:
> java.io.FileNotFoundException: /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype
> I had jboss nexus and http://maven.repository.redhat.com/techpreview/all/ in my settings.xml. After the script finished, the offline dir was 536M big.
--
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