You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/10/31 10:30:33 UTC
[jira] Created: (MNG-1377) Planning support for wtp 1.0
Planning support for wtp 1.0
----------------------------
Key: MNG-1377
URL: http://jira.codehaus.org/browse/MNG-1377
Project: Maven 2
Type: Improvement
Components: maven-eclipse-plugin
Reporter: fabrizio giustina
Priority: Minor
while approaching the 1.0 release WTP changed completely the project descriptors for modules.
The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
Changes tracked for wtp 1.0 (partially working in current WTP builds):
- ".wtpmodules" is renamed to ".component" and moved to the .settings folder
- the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
- a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1377) Planning support for wtp 1.0
Posted by "Brian Bonner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1377?page=comments#action_52912 ]
Brian Bonner commented on MNG-1377:
-----------------------------------
Fabrizio, where are you finding the info for which files are changing in the WTP?
Brian
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MNG-1377
> URL: http://jira.codehaus.org/browse/MNG-1377
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Reporter: fabrizio giustina
> Priority: Minor
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "St?phane Toussaint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54701 ]
Stéphane Toussaint commented on MECLIPSE-47:
--------------------------------------------
Ok, I just thought that 1.0 was the default...
Thanks
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Michael Schnake (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_55290 ]
Michael Schnake commented on MECLIPSE-47:
-----------------------------------------
The cause for the project properties tab "Project facets" being empty and the need to kill the eclipse process after displaying the tab "J2EE module Dependencies" seems to be the same:
In org.eclipse.wst.common.project.facet.core.xml the "version" attribute of the "jst.java" facet *must* be "5.0" for JDK 5.0. Using either "1.5" or "5" will result in the errors named above.
Currently the value for the jst.java version is taken from either the "target" or the "source" attribute (in that order) configured for the compiler plugin, or "1.4" as default. Unfortunally simply setting them to "5.0" does not work, because javac only accepts "1.5" or "5" here.
So perhaps the eclipse plugin should do some version name mangling ("1.5" or "5" -> "5.0") in AbstractWtpResourceWriter.resolveJavaVersion()?
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=all ]
fabrizio giustina closed MECLIPSE-47:
-------------------------------------
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.1
WTP 1.0 support is complete and will be released shortly.
The plugin will require a working WTP (one without the external dependencies bug) and this has been added to the documentation. The patch for copying jars to WEB-INF/lib has been removed (too many problems with jars checked in to svn, removed dependencies leftovers, etc).
Newer WTP builds don't have this bug anymore: from http://download.eclipse.org/webtools/downloads/ you can get a working WTP 1.x release for eclipse 3.1 (Released Maintenance) or for eclipse 3.2 (Integration Build)
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Assignee: fabrizio giustina
> Priority: Minor
> Fix For: 2.1
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Rahul Thakur (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54699 ]
Rahul Thakur commented on MECLIPSE-47:
--------------------------------------
Maven-Eclipse-Plugin by default generates an Eclipse project targeted at WTP 0.7 (refer to Fabrizio's comments in the thread above).
There have been changes/factorings from WTP version 0.7 to 1.0. So, you need to run the maven-eclipse-plugin as follows:
> mvn eclipse:eclipse -Dwtpversion=1.0
to generate Eclipse project resources for WTP 1.0
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Alfie Kirkpatrick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54754 ]
Alfie Kirkpatrick commented on MECLIPSE-47:
-------------------------------------------
Just a quick note. When I originally found these differences between the maven eclipse plugin and WTP 1.0 I wrote a little maven plugin myself called eclipse-util to fix the issues. This has goals copy-local and convert-wtp. A couple of things I noticed:
- The format of .wtpmodules and .component did not appear to be exactly the same. I wrote a little XSL to convert from one to the other
- I did not want the dependent jars in my src tree, so I copied them to target/WEB-INF/lib and added the following line to .component during the conversion:
<wb-resource deploy-path="/WEB-INF/lib" source-path="/target/WEB-INF/lib"/>
Drop me a note if you'd like the Mojo/XSL but they were pretty trivial...
Also, when will the plugin supporting wtpversion="1.0" be available on ibiblio?
Regards, Alfie.
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=all ]
fabrizio giustina updated MECLIPSE-47:
--------------------------------------
Version: 2.0
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Rahul Thakur (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=all ]
Rahul Thakur updated MECLIPSE-47:
---------------------------------
Attachment: MECLIPSE-47.patch
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Rahul Thakur (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54390 ]
Rahul Thakur commented on MECLIPSE-47:
--------------------------------------
Sorry about the code formatting (not sure why that would've happened I am positive I am using the Maven code style for eclipse).
I have made a note of your notes about formatting/imports/unit tests and will be careful with patches this time on.
Thanks for fixing and applying the patch, appreciate it!
Cheers.
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "St?phane Toussaint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54743 ]
Stéphane Toussaint commented on MECLIPSE-47:
--------------------------------------------
1) According to WTP 1.0 package, defaults builders to set in .project differ from R7 revision. There is no more org.eclipse.wst.common.modulecore.ComponentStructuralBuilder nor org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver builder.
If that can be confirm by someone else, I can submit a patch.
2) After updating my .project with mvn eclipse:eclipse -Dwtpversion=1.0, I can see some problems when looking at my project properties.
- The tab "Project Facets" display nothing.
- The tab "J2EE module Dependencies" throw an error :
!SESSION 2006-01-03 11:33:45.681 -----------------------------------------------
eclipse.buildId=M20050929-0840
java.version=1.5.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.jface 4 2 2006-01-03 11:56:07.00
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jst.j2ee.internal.J2EEDependenciesPage.setVisible(J2EEDependenciesPage.java:172)
at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1196)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:351)
at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:638)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1042)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1062)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:231)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:226)
at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:392)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
at org.eclipse.jface.window.Window.open(Window.java:787)
at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
This is a fatal crash because I can't do anything else than kill my eclipse process.
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_56594 ]
fabrizio giustina commented on MECLIPSE-47:
-------------------------------------------
WTP 1.0 support seems to be working properly with the current svn revision.
Waiting for wtp 1.0.1 to be out before a release (external dependencies should be fixed in wtp 1.0.1).
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1377) Planning support for wtp 1.0
Posted by "david varnes (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1377?page=comments#action_53119 ]
david varnes commented on MNG-1377:
-----------------------------------
Note that the WTP team have deferred fixing eclipse bug 116783 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 ) until post wtp-1.0 (maybe wtp-1.0.1 but they have not investigated yet, see comments in bug). Anyone know when they plan 1.0.1 ?
This bug relates to a failure to deploy "externally defined" artifacts to the the target WEB-INF/lib in server container. Thus it is a regression from m6, IIRC. In other words project dependency jars that are defined to be in MAVEN_REPO are not deployed to server using "Publish" action. You might want to add a comment regarding importance to maven users or add a vote.
IMHO this is a show stopper for easy (ie parrallel) use of m2 and wtp-1.0. As a work around can we extend the standard maven 'deploy' to doa specific 'clean' and then 'resource' copy of the required artifacts to a nominated server location eg for Tomcat 5.5 it is WORKSPACE/.metadata/.plugins/org.eclipse.wst.server.core/tmpN/webapps/<finalName>/WEB-INF/lib ?
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MNG-1377
> URL: http://jira.codehaus.org/browse/MNG-1377
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Reporter: fabrizio giustina
> Priority: Minor
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "St?phane Toussaint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54697 ]
Stéphane Toussaint commented on MECLIPSE-47:
--------------------------------------------
After reading this thread, I try to test the svn version with a fresh install of WTP 1.0 (wtp-all-in-one-sdk-1.0-win32.zip).
After building a project with mvn eclipse:eclipse, this is what I find in eclipse log :
!SESSION 2006-01-02 17:26:23.609 -----------------------------------------------
eclipse.buildId=M20050929-0840
java.version=1.5.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.core.resources 2 1 2006-01-02 17:26:33.222
!MESSAGE Skipping builder org.eclipse.wst.common.modulecore.ComponentStructuralBuilder for project atoutfiat. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 2006-01-02 17:26:33.383
!MESSAGE Skipping builder org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver for project atoutfiat. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
modulecore.ComponentStructuralBuilder* aren't found any more, Comparing org.eclipse.wst.common.modulecore_0.7.0 and org.eclipse.wst.common.modulecore_1.0.0.
Is it a real problem ? Is it directly the fact of recent changes in maven-eclipse-plugin ?
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54327 ]
fabrizio giustina commented on MECLIPSE-47:
-------------------------------------------
Patch committed to svn, with a few changes. R7 is left as the default since there are some left for wtp 1.0, see the following comments.
> 1) Plugin now generates WTP settings only if packaging was set to WAR or EAR.
this broke the wtp 0.7 support! The .wtpmodules file is required also for utility projects. I am not sue if this is required for 1.0 too, at the moment I re-enabled it only for R7, we will need to check it
> 4) Project sanity is now validated before defaults (Default Natures, Builders, classpath containers) are generated by EclipsePlugin.
be careful, the order of project builders/natures is really important, the previous order has been restored
> 6) PATCH for WTP1.0 bug:
good, but it should be made optional, maybe we could start defining a 1.0.1 WTP version and enable/disable the workaround based on the version
> 7) Fixed Unit Tests. Note that these still run for R7.
ok, now they are fixed, but don't change the expected result (see 1 and 4) if you are not absolutely sure the previous result was wrong.
What is missing before enabling wtp 1.0 support by default:
- unit tests for wtp 1.0 should be added. All the existing unit tests have been set to use R7
- the wtp settings writer writes the wrong version for java (it was always set to 5.0, now I changed it to 1.4), servlet, and j2ee. It should use the java version defined in pom.xml and the servlet version extracted from dependencies (the settings/WtpModules writers already do that).
... and a few additional notes:
- please use the provided eclipse formatter configuration, your patch had a lot of formatting changes which make it harder to read and to apply
- log messages should be externalized (see the existing code), and NLS markers should be set properly
I am leaving the issue open till everything is resolved.
thanks for the help Rahul!
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Minor
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Barry Kaplan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_58873 ]
Barry Kaplan commented on MECLIPSE-47:
--------------------------------------
This bug is not quite fixed. See my comment at the end.
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Assignee: fabrizio giustina
> Priority: Minor
> Fix For: 2.1
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
Posted by "Rahul Thakur (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_58880 ]
Rahul Thakur commented on MECLIPSE-47:
--------------------------------------
Barry, where is your comment?
> Planning support for wtp 1.0
> ----------------------------
>
> Key: MECLIPSE-47
> URL: http://jira.codehaus.org/browse/MECLIPSE-47
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: fabrizio giustina
> Assignee: fabrizio giustina
> Priority: Minor
> Fix For: 2.1
> Attachments: MECLIPSE-47.patch
>
>
> while approaching the 1.0 release WTP changed completely the project descriptors for modules.
> The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans)
> Changes tracked for wtp 1.0 (partially working in current WTP builds):
> - ".wtpmodules" is renamed to ".component" and moved to the .settings folder
> - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9)
> - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org