[JBoss JIRA] Resolved: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Snjezana Peco (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Snjezana Peco resolved JBIDE-4706.
----------------------------------
Resolution: Done
Fixed in m2eclipse 0.9.9.200911171109
> 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, 4 months
[JBoss JIRA] Created: (JBIDE-4293) Recreate message mechanism for wizards
by Yura Zhishko (JIRA)
Recreate message mechanism for wizards
--------------------------------------
Key: JBIDE-4293
URL: https://jira.jboss.org/jira/browse/JBIDE-4293
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JSF
Affects Versions: 3.1.0.M1
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
Well, my opinion according to file and project wizards, that they don't clearly correspond to Eclipse UI part (http://wiki.eclipse.org/User_Interface_Guidelines#Wizards).
1) First of all when we open any of our wizards, for example, JSP File wizard, we see Next validation message: Attribute Name must be set (screenshot-1). According to Eclipse UI user should see something like this: Create a new JSP file.
2) Now begin to print some name in corresponding field -> Result: there is no any validation message (screenshot-2). According to Eclipse UI user should see default message: Create a new JSP file, if the file name doesn't equal to exist page in project.
>From other aspects there are OK. You can exam Eclipse UI behavior of wizards, for example, using standard JSP wizard or wizard for folders' creating.
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-5146) xml mapping editor does not report erros against DTD, as opposed to the tree view which does.
by Elhanan Maayan (JIRA)
xml mapping editor does not report erros against DTD, as opposed to the tree view which does.
---------------------------------------------------------------------------------------------
Key: JBIDE-5146
URL: https://jira.jboss.org/jira/browse/JBIDE-5146
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Environment: windows XP sp2 , eclipse 3.5.1
Reporter: Elhanan Maayan
i'm not sure exactly what's my version, eclispe says hibernate tools is version 3.3.0v200910281724
the xml hibernate editor does not report required missing elements while the tree validator
for example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="com.pnx.underwrite.bo.letters" default-cascade="evict,merge,lock" default-access="property" auto-import="true">
<class name="Paragraph" table="underwrite_letter_paragraph" mutable="true" polymorphism="implicit" dynamic-update="false" dynamic-insert="false"
batch-size="10" select-before-update="false" optimistic-lock="version">
<cache usage="read-write" />
<id name="id" type="long" access="property" unsaved-value="-1">
<generator class="native" />
</id>
<property name="text" not-null="false" unique="false" update="true" insert="true" />
<property update="false" access="property" type="timestamp" name="created">
<column name="CREATED" sql-type="date" />
</property>
<property update="true" access="property" type="timestamp" name="modified">
<column name="MODIFIED" sql-type="date" />
</property>
<property update="true" not-null="true" access="property" type="boolean" column="DELETED" name="deleted" />
<set name="templates" access="field" table="underwrite_para_temp" >
<key column="template_Prm_Ref" foreign-key="uw_fk_para"/>
<many-to-many class="Paragraph" column="paragraph_prm_ref"/>
</set>
</class>
</hibernate-mapping>
if i remove the key columns the tree editor will report an error but the xml editor won't.
dito with using entity references with classpath, the tree editor reports an error, while xml does not (and this time the tree editor is wrong off course).
--
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, 4 months