August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2714) JBDS 7 Core refers to an installable package's category as "JBoss Data Services" - but this is not JBoss EDS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-2714?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-2714: ----------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 996622|https://bugzilla.redhat.com/show_bug.cgi?id=996622] from NEW to MODIFIED > JBDS 7 Core refers to an installable package's category as "JBoss Data Services" - but this is not JBoss EDS > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2714 > URL: https://issues.jboss.org/browse/JBDS-2714 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.1.GA > > Attachments: Screenshot-DS.png > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15289) Testing of WFK's Spring Getting Started, Petclinic and Travel

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15289?page=com.atlassian.jira.plugi... ] Jiri Peterka edited comment on JBIDE-15289 at 8/20/13 9:30 AM: --------------------------------------------------------------- After trying an exmamples on JBDS 7.0.0.GA with Spring IDE 3.3 installed from JBoss Central I've encountered these issues: https://issues.jboss.org/browse/JBDS-2716 https://issues.jboss.org/browse/JBDS-2718 https://issues.jboss.org/browse/JBDS-2717 https://issues.jboss.org/browse/JBIDE-15357 https://issues.jboss.org/browse/JBDS-2719 https://issues.jboss.org/browse/JBIDE-15289 Some of them are STS 3.3 specific, some of them are non-spring specific. Brief summary: * no code completion works for me in jsp files * lots of errors in error log and problems view (mainly comming from spring plugins) * pages are not 100% rendered correctly in Visual/Source editor * regardless to the issues above, projects can be imported and deployed successfully was (Author: jpeterka): After trying an exmamples on JBDS 7.0.0.GA with Spring IDE 3.3 installed from JBoss Central I've encountered these issues: https://issues.jboss.org/browse/JBDS-2716 https://issues.jboss.org/browse/JBDS-2718 https://issues.jboss.org/browse/JBDS-2717 https://issues.jboss.org/browse/JBIDE-15357 https://issues.jboss.org/browse/JBDS-2719 https://issues.jboss.org/browse/JBIDE-15289 Some of them are STS 3.3 specific, some of them are non-spring specific. Brief summary: * no code completion works for me in jsp files * lots of errors in error log and problems view (mainly comming from spring plugins) * pages are not 100% rendered correctly in Visual/Source editor * regardless to the issues above, projects can be imported and deployed and page > Testing of WFK's Spring Getting Started, Petclinic and Travel > ------------------------------------------------------------- > > Key: JBIDE-15289 > URL: https://issues.jboss.org/browse/JBIDE-15289 > Project: Tools (JBoss Tools) > Issue Type: Task > Reporter: Burr Sutter > Assignee: Jiri Peterka > > For validation of the visual page editor, maven-based build, deploy/undeploy, etc. > https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > 1) Import via File Maven Import > 1.1) Ignore cvc-complex-type.2.4.a: Invalid content error (or follow Denis' steps to ignore error) > 2) Open .jsp in Visual Page Editor > 3) Run As Run on Server > http://screencast.com/t/SIlyrb5iuCR8 > http://screencast.com/t/kfMfKJ93WC > http://screencast.com/t/FPgmE6Xm2bi > These steps should be recurring test cases for JBDS. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2716) NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2716?page=com.atlassian.jira.plugin.... ] Jiri Peterka edited comment on JBDS-2716 at 8/20/13 9:15 AM: ------------------------------------------------------------- Note: Spring IDE 3.3 is installed via JBoss Central was (Author: jpeterka): Note: Spring IDE 2.3 is installed via JBoss Central > NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2716 > URL: https://issues.jboss.org/browse/JBDS-2716 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyDependencies > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64 > Reporter: Jiri Peterka > Fix For: 7.0.1.GA > > Attachments: spring-internal-error.png > > > IDE reports error after importing getting-started spring wfk 2.3 demo project. Expecting this error is more general, not only this project specific. > {code} > java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) > at java.lang.Class.getDeclaredMethods(Class.java:1793) > at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:130) > at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:109) > at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:259) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:86) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:749) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:742) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:626) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:585) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:451) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 23 more > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-152) JBTIS lacks reference to orbit update site for dependency resolution

by Paul Richardson (JIRA)

Paul Richardson created JBTIS-152: ------------------------------------- Summary: JBTIS lacks reference to orbit update site for dependency resolution Key: JBTIS-152 URL: https://issues.jboss.org/browse/JBTIS-152 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Components: distribution Affects Versions: 4.1.2 Reporter: Paul Richardson Priority: Critical Fix For: 4.1.2 Teiid Designer plugins have dependencies available in the JBT Orbit repository. However, this is not advertised as available when installing Designer plugins from JBT-IS hence installation fails unless orbit is added as an update site separately. Add orbit to list of associated site so that dependencies can be properly resolved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-152) JBTIS lacks reference to orbit update site for dependency resolution

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBTIS-152?page=com.atlassian.jira.plugin.... ] Paul Richardson commented on JBTIS-152: --------------------------------------- Pull request created [https://github.com/jbosstools/jbosstools-integration-stack/pull/84] > JBTIS lacks reference to orbit update site for dependency resolution > -------------------------------------------------------------------- > > Key: JBTIS-152 > URL: https://issues.jboss.org/browse/JBTIS-152 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.2 > Reporter: Paul Richardson > Priority: Critical > Fix For: 4.1.2 > > > Teiid Designer plugins have dependencies available in the JBT Orbit repository. However, this is not advertised as available when installing Designer plugins from JBT-IS hence installation fails unless orbit is added as an update site separately. > Add orbit to list of associated site so that dependencies can be properly resolved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- It does not seem safe to assume that all maven-download-plugin executions are for test and all maven-dependency-plugin exectuins are for populating a bundle. Removing <skip>${skipRequirements}</skip> from parent and moving it to relevant places would be better. As for usage of maven-dependency-plugin in test context, see https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- or simply change those downloads to use the non-maven-dependency plugins to get it. I couldn't find any using maven-dependency-plugin on first look; do you know which has it ? > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-145) bad label / description on generated update site's index.html page

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-145?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-145: ------------------------------------------- the fuseIDE banner in here isn't the opensource project name - that is the product is it not ? the one published to JBTIS shouldn't use product branding. This is in context of https://github.com/jbdevstudio/jbdevstudio-website/commit/7e2abd98ec72ab3... which referenced this jira. > bad label / description on generated update site's index.html page > ------------------------------------------------------------------ > > Key: JBTIS-145 > URL: https://issues.jboss.org/browse/JBTIS-145 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 4.1.2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > > The description/label for your update site [1] says: > "This is the http://fuse.fusesource.org/org.fusesource.ide.updatesite/ Update Site for Fuse :: Update Site. " > [1] http://download.jboss.org/jbosstools/updates/development/kepler/integrati... > I'll attach a PR for your site/pom.xml which should fix this, as well as some other enhancements to the way the html is generated. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15340: --------------------------------------------- seems my nice jira client didn't get the last few comments in - so I can see that Rob basically said the same as me. no associate site links in locus, those who use it gets other deps from their own associate sites. Thanks Rob :) > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.1.0-LOCUS > > Attachments: 15340_locus110CI-full-install.png > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15340: --------------------------------------------- No, none of these associate sites are needed to be referenced by locus; none of the component on the locus should have dependencies *outside* of very basic org.eclipse stuff. if tycho, a user or whatever needs some other dependency (like org.osgi.core.whatever) then that is something the build/user/other updatesite decides where it comes from. Locus is like a lowest component site that is *only* use at build time for other builds to get from. Yes, it needs its own dependencies during build time - that does not mean it should be part of associate sites. This rule about not having associate sites applies equally well to any of our sub-component builds - they are *not* supposed to have *any* external references - it is the build, the aggregating updatesite etc. that gets to decide how it is assembled. We've had plenty of discussions and scenarioes where this have been a problem (i.e. testing and combining updatesites becomes very tricky if a site refers to multiple eclipse release trains). Associate sites are 99.9% only relevant for end-user updatesites - like JBT, JBTIS or complete separate updatesite sites (even in JBTIS case it would be better if it didn't linked back to JBT so it could be combined with any release of JBT - but that is something we do right now since no better solution). We have to stop mingling up enduser and internal build sites needs/requirements. > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.1.0-LOCUS > > Attachments: 15340_locus110CI-full-install.png > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 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 August 2013