January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16351: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 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 > Priority: Critical > Fix For: 4.1.2.CR1, 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15888: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Fred Bricon > Labels: spring > Fix For: 4.1.2.CR1 > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16292) Need to restore ability to select specific archetype version per runtime in Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16292: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Need to restore ability to select specific archetype version per runtime in Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-16292 > URL: https://issues.jboss.org/browse/JBIDE-16292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.2.CR1 > > > The changes done in JBIDE-15645 introduced a regression in the way archetypes are selected. > Basically, we can get different archetype versions depending on the EE version of the runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different archetype version between 2 different runtimes of the same product and same EE level (eg. EAP 6.1 vs EAP 6.2) > As a consequence, archetype versions designed to run on EAP 6.2 will be selected when EAP 6.1 is selected in the project wizard. > Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't be a problem, but we should fix that for the next minor release. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12370) Add a video that shows how to handle missing requirements on New Project Example screen

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12370?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-12370: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Add a video that shows how to handle missing requirements on New Project Example screen > --------------------------------------------------------------------------------------- > > Key: JBIDE-12370 > URL: https://issues.jboss.org/browse/JBIDE-12370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 3.3.0.Final > Reporter: Pete Muir > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.2.CR1 > > > If the user clicks on _JBoss Central | Java EE Web Project_ they are presented with this screen http://www.jboss.org/jdf/stage/quickstarts/jboss-as-quickstart/guide//gfx... - it would be nice to have a short video showing how people can solve missing requirements, e.g. by clicking the Install button. This can then be linked to from tutorials that use these wizards. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16177) Configure Maven Repositories Dialog Cancel

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16177?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16177: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Configure Maven Repositories Dialog Cancel > ------------------------------------------ > > Key: JBIDE-16177 > URL: https://issues.jboss.org/browse/JBIDE-16177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Fred Bricon > Labels: waitingforfeedback > Fix For: 4.1.2.CR1 > > > Hitting the Cancel button produces the following error: > An error has occurred. See error log for more details. > Argument cannot be null > http://screencast.com/t/8cNrfyB9A > Steps to Reproduce: > 1) While JDBS is running, edit your settings.xml to remove maven.repository.redhat.com - just remove it from <activeProfiles> > 2) Back in JBDS, hit HTML5 Project on JBoss Central > 3) Select EAP 6.1 in the Target Runtime > 4) Click on the word "repository" in the warning near the bottom of the dialog > 5) Click Cancel > and in some cases, I notice the error message might pop-up even before I can visit the subsequent dialog. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16397) Project created with Forge 1 not imported to Eclipse on Windows

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16397?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16397: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Project created with Forge 1 not imported to Eclipse on Windows > --------------------------------------------------------------- > > Key: JBIDE-16397 > URL: https://issues.jboss.org/browse/JBIDE-16397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Final > Environment: Windows 7 x86 > JBDS 7.1.0 > Reporter: Martin Malina > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > When you create a project in Forge on Windows, it is created alright, but the project is not imported to Eclipse so it does not appear in the project explorer. > Screencast here: http://screencast.com/t/9krBgXxz -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15934: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > 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.CR1 > > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16249) Offline groovy script not working - FileNotFoundException

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16249?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16249: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.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.CR1 > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15718) Add blank icon to align JBoss Welcome screen columns

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15718?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15718: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Add blank icon to align JBoss Welcome screen columns > ---------------------------------------------------- > > Key: JBIDE-15718 > URL: https://issues.jboss.org/browse/JBIDE-15718 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Catherine Robson > Assignee: Fred Bricon > Priority: Trivial > Fix For: 4.1.2.CR1 > > Attachments: central-columns.png > > > It really bothers me that the columns on JBoss Central do not properly align horizontally. Can we add a blank icon that links nowhere to the headers of "Tutorial" and "Other Resources" so these sections horizontally align with the sections to the left? > See areas of concern in screenshot: > https://www.evernote.com/shard/s230/sh/d7467a14-e89a-42d0-955c-d40a65e506... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14629: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.1.2.Final) > Errors when creating and deploying seam2 project with Seam 2.3.Final > --------------------------------------------------------------------- > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Rob Stryker > Priority: Critical > Labels: jbds711 > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014