October 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss

by Denis Golovin (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-4706: --------------------------------- Fix Version/s: 3.1.0.CR1 (was: 3.1.0.M4) > Maven integration issues: setting facets on maven projects and deploying ear on JBoss > ------------------------------------------------------------------------------------- > > Key: JBIDE-4706 > URL: https://jira.jboss.org/jira/browse/JBIDE-4706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Environment: Eclipse 3.5 > m2eclipse (0.9.9.20090720) > JBoss Tools AS M3 developer version > Subclipse SVN plugin 1.6.3 > Reporter: Alexander Lengson > Assignee: Snjezana Peco > Fix For: 3.1.0.CR1 > > Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip > > > Using Maven command line, I created four projects: > container - the parent Maven project. It also serves as a container for other projects > prj-jar - a shared library used by all other EJBs > prj-ejb - sample EJB > prj-ear - EE container for jar and ejb > Apache plugins for Maven (both for ejb and ear) are used. > I've performed the following steps: > * imported container into SVN > * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720) > * right-clicked on container and chosen "Checkout as Maven project" > * waited for the process to be finished > And the following likely are bugs and/or open questions: > * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ear: the same. > * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements? > * for prj-ejb: there is no Project Facet checked at all. > * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled) > * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed) > * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View: > EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart > * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml) > * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory: > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ear-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <includeLibInApplicationXml>true</includeLibInApplicationXml> > ... > That builds the EAR which contains lib/ folder inside and all references libs like: > drools-api-5.0.1.jar > drools-core-5.0.1.jar > hsqldb-1.8.0.10.jar > joda-time-1.6.jar > mvel2-2.0.10.jar > prj-jar-1.0-SNAPSHOT.jar > That can be assured by running command: > container>mvn install > Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors. > It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.

by Mario Balaban (JIRA)

AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings. ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2050 URL: http://jira.jboss.com/jira/browse/JBIDE-2050 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.0.1 Environment: Linux 2.6.22-14-generic, Eclipse Europa Version: 3.3.2, JbossToolsPlugin 2.0.1GA-ALL linux, JbossAS 4.2.2.GA Reporter: Mario Balaban On the same machine I had to create 2 instances of JbossAS, one for testing and another for development. The instance used for testing is using the "default" configuration. The test (default) instance I am able to start and to stop correctly from the Eclipse IDE. The "devel" instance that is a copy of the "default" configuration but has different port bindings (modified jboss-service.xml by uncommenting the tag <mbean code="org.jboss.services.binding.ServiceBindingManager"..../> ) has problems when starting and stopping from eclipse IDE. In the console window of IDE I see " [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:993ms" but the state of the server in the "Servers" window of the IDE is Starting... It remains "Starting..." till an OutOfMemory is visualized in the IDE. This error happens even when no applications are deployed to the deploy directory of the "devel" configuration. It seems that the problem is associated to different port bindings used by "devel" configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5050) Cover "Generate Hibernate/JPA Annotation for several classes in java file" functionality with JUnit tests

by Vitali Yemialyanchyk (JIRA)

Cover "Generate Hibernate/JPA Annotation for several classes in java file" functionality with JUnit tests --------------------------------------------------------------------------------------------------------- Key: JBIDE-5050 URL: https://jira.jboss.org/jira/browse/JBIDE-5050 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M4, 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.CR1 -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3563) Code assist for "class" and "styleClass" attributes for html and jsf tags.

by Alexey Kazakov (JIRA)

Code assist for "class" and "styleClass" attributes for html and jsf tags. -------------------------------------------------------------------------- Key: JBIDE-3563 URL: https://jira.jboss.org/jira/browse/JBIDE-3563 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 It should show proposals for all classes that are defined in linked css which are available in design time. -- 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

16 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-899) Mapping diagram restoring and "save as" functionality

by Svetlana mukhina (JIRA)

Mapping diagram restoring and "save as" functionality ----------------------------------------------------- Key: JBDS-899 URL: https://jira.jboss.org/jira/browse/JBDS-899 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Hibernate Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.1.0-doc Check that in hibernate guide we take into account that "After Eclipse restart all opened editor are restored beside Mapping Diagram" and mention that it's possible to save diagram into workspace file and load diagram from the file -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4866) After Eclipse restart all opened editor are restored beside Mapping Diagram

by Vitali Yemialyanchyk (JIRA)

After Eclipse restart all opened editor are restored beside Mapping Diagram --------------------------------------------------------------------------- Key: JBIDE-4866 URL: https://jira.jboss.org/jira/browse/JBIDE-4866 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M4 Mapping Diagram should also be restotred in this case. -- 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

16 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4964) "Save As" should be workable for Mapping Diagram - should be possible to save diagram into workspace file and load diagram from the file

by Vitali Yemialyanchyk (JIRA)

"Save As" should be workable for Mapping Diagram - should be possible to save diagram into workspace file and load diagram from the file ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4964 URL: https://jira.jboss.org/jira/browse/JBIDE-4964 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M4 firstly if diagram created from console config - it should be saved into eclipse workspace settings, but "Save As" should allow the user save the diagram in the project workspace, file extension should be "*.hdg"; for generated diagram the title should consists from concateted item names (now it is); for diagram from the file diagram title should include file name (and (???) may be concateted item names); -- 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

16 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4965) WSDL Editor - Declaring bindings

by Edgar Silva (JIRA)

WSDL Editor - Declaring bindings -------------------------------- Key: JBIDE-4965 URL: https://jira.jboss.org/jira/browse/JBIDE-4965 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M3 Environment: Fedora 11, Eclipse 3.5 Reporter: Edgar Silva Priority: Minor When I declare a binding like that (visually or in source directly): <soap:binding required="true" style="document" transport="http://schemas.xmlsoap.org/soap/http"/></binding> <service name="reviewcontract"> If I select required="true", the WSDL editors says that there is an error into WSDL file. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-887) overwriting of resources is disabled when generate code via New Seam Action/Entity/Conversation Wizards

by Svetlana mukhina (JIRA)

overwriting of resources is disabled when generate code via New Seam Action/Entity/Conversation Wizards -------------------------------------------------------------------------------------------------------- Key: JBDS-887 URL: https://jira.jboss.org/jira/browse/JBDS-887 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc check that there is no wizard on screens warning about resources ovewriting -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDS-358) Screenshots

by Svetlana mukhina (JIRA)

Screenshots ------------ Key: JBDS-358 URL: http://jira.jboss.com/jira/browse/JBDS-358 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Priority: Minor Fix For: 2.0.0.alpha Sometime screen name (title in guide) doesn't correspond its content, plz try to make titles more informative -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
10
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 October 2009