December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1390) After removing maven dependency, JBDS does not `mvn clean` nor redeploy.

by Ondrej Zizka (JIRA)

After removing maven dependency, JBDS does not `mvn clean` nor redeploy. ------------------------------------------------------------------------ Key: JBDS-1390 URL: https://jira.jboss.org/browse/JBDS-1390 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Ondrej Zizka After removing maven dependency, JBDS does not `mvn clean` nor redeploy, so the dep stays in the deployed application when you do "Run As... -> Run at server". STR: 1) svn export -r12016 https://svn.devel.redhat.com/repos/jboss-qa/people/ozizka/VUTcourse/proje... 2) Import to JBDS with all the other stuff - m2eclipse etc. 3) Run at server. 4) In pom.xml, remove HSQL, and add <scope>provided</scope> to Hibernate. 5) Run at server. 6) Check the deployed app; it still has both jars inside. Shame :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1410) RichFaces don't work in portlet generated by JBDS

by Jan Jamrich (JIRA)

RichFaces don't work in portlet generated by JBDS ------------------------------------------------- Key: JBDS-1410 URL: https://jira.jboss.org/browse/JBDS-1410 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: jsf Affects Versions: 3.0.1.GA Environment: Linux (and portlet generated by JBDS tested on EPP-5.1.0-ER4 (and previous ER + GateIn-5.1.0.GA) Reporter: Jan Jamrich Assignee: Max Andersen RichFaces Portlet generated by JBDS don't display content of richFaces tags. (Added manually, with RF jars added manually as well) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
22
0 / 0

[JBoss JIRA] Created: (JBDS-1465) Internal error during "Loading Core Provider"

by Pavol Srna (JIRA)

Internal error during "Loading Core Provider" ---------------------------------------------- Key: JBDS-1465 URL: https://issues.jboss.org/browse/JBDS-1465 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.Beta2 Environment: JBDS 4.0.0.Beta2, SOA-5.1.ER5 + eds, linux 32bit Reporter: Pavol Srna Attachments: Screenshot.png Message: An internal error occurred during: "Loading Core provider". Exception Stack Trace: java.lang.NullPointerException at org.eclipse.datatools.connectivity.sqm.internal.core.definition.DatabaseDefinitionImpl.isAuthorizationIdentifierSupported(DatabaseDefinitionImpl.java:2014) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displayDatabaseChildren(ServerExplorerVNodeContentProviderNav.java:391) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:116) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:239) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractLayoutProviderNav.getChildren(AbstractLayoutProviderNav.java:85) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.impl.ServerExplorerContentProviderNav.load(ServerExplorerContentProviderNav.java:153) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.loading.LoadingJob.run(LoadingJob.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7814) User is not notified when deployment fails

by Libor Zoubek (JIRA)

User is not notified when deployment fails ------------------------------------------ Key: JBIDE-7814 URL: https://jira.jboss.org/browse/JBIDE-7814 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta2 Reporter: Libor Zoubek Assignee: Rob Stryker AFAIK when deploying we are calling server via JMX. What happens when JMX call is not successful? Nothing good. Studio shows project as deployed, but app server in worse case does not know about deployment (when target dir is set to workspace), in better case notices it after a few seconds. User than can only guess what and why is his project not deployed. This confusing behavior can be simply reproduced on any soa-p server, since you have to uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to make JMX working. If you do not do that, you'll reproduce. AS Adapter should warn user on JMX call errors. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
21
0 / 0

[JBoss JIRA] Created: (JBIDE-2708) Implement webbeans validation rules

by Max Rydahl Andersen (JIRA)

Implement webbeans validation rules ----------------------------------- Key: JBIDE-2708 URL: https://jira.jboss.org/jira/browse/JBIDE-2708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER See webbeans ref impl for static check* methods. Unittests has tests.broken which we can use as inspiration for tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7967) nonannotated classes without default constructor and no CDI scope or inject annotations on class or constructor should not be considered beans

by Max Andersen (JIRA)

nonannotated classes without default constructor and no CDI scope or inject annotations on class or constructor should not be considered beans ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7967 URL: https://issues.jboss.org/browse/JBIDE-7967 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Max Andersen Assignee: Alexey Kazakov Priority: Critical Fix For: 3.2.0.CR1 public interface Project { } public abstract class AbstractProject implements Project { } public class ProjectImpl extends AbstractProject { public ProjectImpl(final File rootDirectory) { projectRoot = rootDirectory; } } @Singleton public class CurrentProject { @Produces @Default @Dependent public Project getCurrent() } @Inject Project project; should in this case just consider getCurrent() the only injection source because Abstract class cannot be instantatiated nor can the PRojectImpl since it has no-noarg constructor but does have a constructor with arguments. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1382) No obvious icon is present to launch JBDS after installation on Mac

by John Verhaeg (JIRA)

No obvious icon is present to launch JBDS after installation on Mac ------------------------------------------------------------------- Key: JBDS-1382 URL: https://jira.jboss.org/browse/JBDS-1382 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.0.0.Beta1 Environment: Mac OS X 10.6 (Snow Leopard) w/ Cocoa Reporter: John Verhaeg After installation, I get the jbdevstudio folder, but nothing in it but other folders and a readme that talks about "clicking on the installed icon in your program menu or desktop" that doesn't exist. Just browsing for something to launch, my first inclination was to look in the studio subfolder, and only after discovering there's nothing appropriate there, and knowing, as a developer for Teiid Designer, that dev studio is an Eclipse application, did I deduce that I must have to launch the eclipse application under the eclipse subfolder. This definitely isn't intuitive, and especially wouldn't be for those new to dev studio and/or Eclipse. I'd want to see an app icon directly in my Applications folder, not even within the jbdevstudio folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
10
0 / 0

[JBoss JIRA] Created: (JBDS-1399) Make HTML-version of Welcome Screen

by Victor Rubezhny (JIRA)

Make HTML-version of Welcome Screen ----------------------------------- Key: JBDS-1399 URL: https://jira.jboss.org/browse/JBDS-1399 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: ui/branding Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 4.0.0.Beta2 Make the Welcome Screen to use HTML render when it shown due to exclude Universal Intro code overrides and make it extensible. Also, need to ensure that HTML-rendering will not conflict with XulRunner and VPE Editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
26
0 / 0

[JBoss JIRA] Created: (JBIDE-7721) CDI validator should be aware of custom decorators/interceptors/...

by Alexey Kazakov (JIRA)

CDI validator should be aware of custom decorators/interceptors/... ------------------------------------------------------------------- Key: JBIDE-7721 URL: https://jira.jboss.org/browse/JBIDE-7721 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x For example we have: class CustomDecoratorImplementation implements Decorator<VehicleDecorator> { ... } and class VehicleDecorator implements Vehicle { @Inject @Delegate Vehicle delegate; ... } Then is VehicleDecorator is a decorator though it doesn't have @Decorator annotation. So CDI validator should not treat @Inject @Delegate Vehicle delegate; as a definition error. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7961) Incremental validation doesn't work correctly if both Seam and CDI support enabled on the project.

by Alexey Kazakov (JIRA)

Incremental validation doesn't work correctly if both Seam and CDI support enabled on the project. -------------------------------------------------------------------------------------------------- Key: JBIDE-7961 URL: https://issues.jboss.org/browse/JBIDE-7961 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), Seam Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x Seam and CDI validators use KB validation context by default. It cause problems for incremental validation (CDI, Seam) since each validator clears the context during validation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
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 December 2010