[JBoss JIRA] Updated: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Alexander Lengson (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Alexander Lengson updated JBIDE-4706:
-------------------------------------
Attachment: without_vars_pure_maven.zip
Pure Maven project for importing to/exporting from SVN.
> 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: JBoss Tools
> Issue Type: Bug
> Components: maven
> 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.M3
>
> 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
14 years, 10 months
[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Alexander Lengson (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Alexander Lengson commented on JBIDE-4706:
------------------------------------------
>> One more observation - in both cases library 'prj-jar-1.0-SNAPSHOT.jar' appears in directory ...\standard\deploy\prj-ear.ear\lib\lib\'.
lib\ is duplicated, and prj-jar-1.0-SNAPSHOT.jar looks redundant there.
>This issue happens because your EAR project has an invalid settings. The prj-ear/.settings/org.eclipse.wst.common.components.xml >contains the following line:
>...
><dependent-module archiveName="lib/prj-jar-1.0-SNAPSHOT.jar" deploy-path="lib/" handle="module:/resource/prj-jar/prj-jar">
> ...
>
>The correct line would be:
>...
><dependent-module archiveName="prj-jar-1.0-SNAPSHOT.jar" deploy-path="lib/" handle="module:/resource/prj-jar/prj-jar">
> ...
>
>I am not sure how you did that line. Neither m2eclipse nor WTP adds it by default.
>Attached is the correct project (without_vars.zip).
Snjezana,
Settings file 'org.eclipse.wst.common.component' is generated automatically.
Line that you pointed out:
<dependent-module archiveName="lib/prj-jar-1.0-SNAPSHOT.jar" deploy-path="lib/" handle="module:/resource/prj-jar/prj-jar">
is generated when the project is checked out from SVN repository by "Check out as Maven Project"
What I did:
I removed all Eclipse settings from the archive you have attached, submitted it into SVN, then checked out, and that line appears again.
(pure Maven project for importing into SVN is attached to this issue)
The result is again the same issue I had described before.
Thus, this looks like issue of generating proper Eclipse project's settings from Maven project.
> 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: JBoss Tools
> Issue Type: Bug
> Components: maven
> 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.M3
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.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
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-4725) ClassCastException using CA for rich:page
by Yura Zhishko (JIRA)
ClassCastException using CA for rich:page
-----------------------------------------
Key: JBIDE-4725
URL: https://jira.jboss.org/jira/browse/JBIDE-4725
Project: JBoss Tools
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.0.M3
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
1) Import attached project into workspace
2) Open inputname.xhtml
3) Set cursor at the end of <rich:page> tag (see screenshot-1)
4) Press Ctrl+Space
ASSERT: CA for attributes of rich:page appears
ASSERT FAILED: CA doesn't appear with exception:
java.lang.ClassCastException: org.eclipse.wst.html.core.internal.document.DocumentStyleImpl
at org.jboss.tools.jst.jsp.contentassist.FaceletPageContectAssistProcessor.getTagName(FaceletPageContectAssistProcessor.java:273)
at org.jboss.tools.jst.jsp.contentassist.AbstractXMLContentAssistProcessor.getParent(AbstractXMLContentAssistProcessor.java:773)
at org.jboss.tools.jst.jsp.contentassist.XmlContentAssistProcessor.createKbQuery(XmlContentAssistProcessor.java:88)
at org.jboss.tools.jst.jsp.contentassist.JspContentAssistProcessor.addAttributeNameProposals(JspContentAssistProcessor.java:469)
at org.jboss.tools.jst.jsp.contentassist.FaceletPageContectAssistProcessor.addAttributeNameProposals(FaceletPageContectAssistProcessor.java:247)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractContentAssistProcessor.computeTagCloseProposals(AbstractContentAssistProcessor.java:1611)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractContentAssistProcessor.computeCompletionProposals(AbstractContentAssistProcessor.java:1302)
at org.jboss.tools.jst.jsp.contentassist.AbstractXMLContentAssistProcessor.computeCompletionProposals(AbstractXMLContentAssistProcessor.java:523)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractContentAssistProcessor.computeCompletionProposals(AbstractContentAssistProcessor.java:1407)
at org.jboss.tools.jst.jsp.contentassist.AbstractXMLContentAssistProcessor.computeCompletionProposals(AbstractXMLContentAssistProcessor.java:89)
at org.jboss.tools.common.text.xml.contentassist.SortingCompoundContentAssistProcessor.computeCompletionProposals(SortingCompoundContentAssistProcessor.java:234)
at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:303)
at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1832)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482)
at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1660)
at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:446)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$JSPStructuredTextViewer.doOperation(JSPTextEditor.java:669)
at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:131)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:129)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185)
at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1191)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1368)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4053)
at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:346)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3946)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2409)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3471)
at org.jboss.tools.vpe.editor.context.VpePageContext.processDisplayEvents(VpePageContext.java:282)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:439)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:280)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:666)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:578)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:280)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:1037)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.setAttribute(VpeVisualDomBuilder.java:1131)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:608)
at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:485)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
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
14 years, 10 months