Re: [ANN] Maven Eclipse Plugin 2.6 Released
dear，although the maven throws exception when i ran the cmd mvn clean eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true with the log i have shown in my last send email, but the maven eclipse(version) plugin generated my project actually successfully while i have not change the charset of my eclipse's workspace. i have not just got why it happend to me ! in the way, thanks for Barrie Treloar reply! the maven runs well with me! On Thu, Apr 2, 2009 at 6:12 PM, Barrie Treloar baerr...@gmail.com wrote: org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace content allowed before start tag and not \u9518 (position: START_DOCUMENT \u9518 looks like international character sets. Not sure why it isn't whitespace. Same thing, try to make small test case and raise a JIRA. If you can compare the output from 2.5.1 and 2.6 that might help as well. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- 漠洋(苏琳冲) SuLinchong Phone 13656669328 Qq387973308 Msn sulinch...@hotmail.com
Re: [ANN] Maven Eclipse Plugin 2.6 Released
oh, all right, but i think ,i should inspect the cmd -Declipse.addVersionToProjectName=true more carefully.what's more, when i comes to use version 2.6, my eclipse's workspace does not run as well as before. The follow is the log: [WARNING] could not read workspace project:D:\taobao.workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\wangwang-plugin org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace content allowed before start tag and not \u9518 (position: START_DOCUMENT se 8... @1:1) at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1519) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1395) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:187) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:83) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:48) at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readArtefact(ReadWorkspaceLocations.java:341) at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readWorkspace(ReadWorkspaceLocations.java:533) at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(ReadWorkspaceLocations.java:94) at org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfiguration(EclipsePlugin.java:1784) at org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathContainers(EclipsePlugin.java:1350) at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(EclipsePlugin.java:807) at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:498) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) The project wangwang-plugin is also in my workspace,but i have not modified the project's file. when i run the cmd mvn clean eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true for the bellow project projectDescription name**-connect-1.12-SNAPSHOT/name comment**/comment projects project**-json/project project**-string/project project**-xml/project project**-server/project project**-config/project project**-core/project project**-dal/project project**-sm/project project**-engine/project project**-tim/project project**-client/project /projects buildSpec buildCommand nameorg.eclipse.jdt.core.javabuilder/name /buildCommand /buildSpec natures natureorg.eclipse.jdt.core.javanature/nature /natures /projectDescription the maven throws the exception, and also the maven eclipse(2.6) plugin didn't generate the eclipse project definite succssfully ,although the console tell me generate succssfully. On Thu, Apr 2, 2009 at 2:24 PM, Barrie Treloar baerr...@gmail.com wrote: On Thu, Apr 2, 2009 at 4:03 PM, linchongsu sulinchong1...@gmail.com wrote: hi,dear i found i can't run mvn clean eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true all right with version 2.6 If you can provide a small repeatable test case then raise a JIRA and we can look into it. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Eclipse Plugin 2.6 Released
hi,dear i found i can't run mvn clean eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true all right with version 2.6 the plugin generate the project with version,however ,it has not generate the dependency project with version? such as: projectDescription name**-connect-1.12-SNAPSHOT/name comment**/comment projects project**-json/project project**-string/project project**-xml/project project**-server/project project**-config/project project**-core/project project**-dal/project project**-sm/project project**-engine/project project**-tim/project project**-client/project /projects buildSpec buildCommand nameorg.eclipse.jdt.core.javabuilder/name /buildCommand /buildSpec natures natureorg.eclipse.jdt.core.javanature/nature /natures /projectDescription is it a bug? or how can i add version to the denepency project name Thanks for everyone's help! su On Thu, Apr 2, 2009 at 4:57 AM, Barrie Treloar baerr...@apache.org wrote: The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.6 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.6/version /plugin Known Issues: * [MECLIPSE-443] - Only include **/*.java in Java source directories may affect you if you use ajdt or have non-java sources in your directories that you expect to be compiled Release 2.6.1 (which may get renamed to 2.7) has fixed this issue and will be released shortly. See http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11133fixfor=15130 Release Notes - Maven 2.x Eclipse Plugin - Version 2.6 ** Sub-task * [MECLIPSE-479] - More contaigner entries ** Bug * [MECLIPSE-111] - Additional webResources are not added to the component list when using WTP projects generation * [MECLIPSE-150] - [with PATCH] Plugin generates invalid Eclipse project files when multiproject contains two references to the same artifact * [MECLIPSE-206] - IdeUtils.toRelativeAndFixSeparator broken on Windows * [MECLIPSE-261] - IdeUtils.toRelativeAndFixSeparator returns incomplete path * [MECLIPSE-326] - m2eclipse goal does not respect additionalBuildcommands and additionalProjectnatures defined in pom * [MECLIPSE-337] - test failure needed to be commented out * [MECLIPSE-364] - incorrect dependencies with different projectNameTemplates in submodules * [MECLIPSE-377] - eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than once in a multi-project * [MECLIPSE-397] - Eclipse project set as dependency + test-jar dependency is included twice in .classpath * [MECLIPSE-414] - Not beeing @aggregator, eclipse plugin does not require executedProject * [MECLIPSE-415] - settings stored in wrong project directory * [MECLIPSE-418] - OSGi 4 support for Bundle-SymbolicName * [MECLIPSE-419] - Classpath generated by eclipse:myeclipse skip provided dependencies * [MECLIPSE-423] - NullPointerException when existing Manifest.MF file has no Class-Path element * [MECLIPSE-427] - .springBeans definition throws NullPointer if BaseDir does not exist * [MECLIPSE-445] - myeclipse target doesn't generate spring bean files for hierarchical projects. * [MECLIPSE-475] - Container mispelling * [MECLIPSE-486] - ITs dont compare expected files if the IT is a multi-module project * [MECLIPSE-488] - InstallPluginsMojo throws NPE if a jar has no manifest * [MECLIPSE-508] - If base artifact does not exist then the unavailable cache was incorrectly updated * [MECLIPSE-509] - Unavailable cache is incorrectly updated to mark sources/javadoc as not available when downloads option is not specified ** Improvement * [MECLIPSE-318] - test classes and resources need to be first in .classpath file * [MECLIPSE-437] - Ordering of .classpath entries when using a newer version of JARs already included in the JDK. * [MECLIPSE-442] - Classpath container entries should come last in .classpath * [MECLIPSE-443] - Only include **/*.java in Java source directories * [MECLIPSE-493] - Automatically locate workspace ** New Feature * [MECLIPSE-200] - Please add support for the AJDT plugin * [MECLIPSE-270] - Add support for classpathentry attributes * [MECLIPSE-313] - AJDT feature * [MECLIPSE-387] - download source should accept exclusion of artifact * [MECLIPSE-504] - Add a new mojo eclipse:remove-cache ** Task * [MECLIPSE-345] - Split unit tests and integration tests * [MECLIPSE-349] - Move integration tests in the integration-tests profile ** Test * [MECLIPSE-502] -
Re: example for settings.xml
you can get reference from http://maven.apache.org/settings.html Best Regards! On Sun, Mar 1, 2009 at 3:21 PM, nani2ratna nani2ra...@gmail.com wrote: Hi, Thank you very much for your replies. Actually i didnt understand properly about settings.xml. I didnt put anything in that file. Thats why it was not working. I went through some forums then i put the default values. Now its working fine. Thank you very much for giving these replies. Thanks and Regards Ratna Sekhar Ian Petzer wrote: Hi Ratna, To be honest you don't really need much of anything in a settings.xml file. The defaults are enough to get Maven working. I actually run with a settings.xml file that looks much like the snippet below You could create your own settings.xml file like this but I doubt it would solve your problem. Maybe you should paste your error message that you get: - settings xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; mirrors /mirrors servers /servers /settings --- On Sat, Feb 28, 2009 at 10:35 PM, nani2ratna nani2ra...@gmail.com wrote: Hi, I am new user to maven. I installed maven perfectly. I did first hello world perfectly. Now i want to create a project for struts and hibernate. Then i gave command to generate folder for web application. It also worked fine, now i put struts in dependency. But its giving error that settings.xml is not working. I want to start developing with struts very new version 2.1.6 GA. So can please send me the proper settings.xml. Thanks and Regards Ratna - View this message in context: http://www.nabble.com/example-for-settings.xml-tp22267685p22267685.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/example-for-settings.xml-tp22267685p22270551.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- 漠洋(苏琳冲) SuLinchong Phone 13656669328 Qq387973308 Msn sulinch...@hotmail.com
Re: Does the pluginGroup in the setting.xml work?
does the pluginGroups in the setting.xml work? anybody comes to this problem? On Mon, Nov 24, 2008 at 3:21 PM, 苏林冲 sulinchong1...@gmail.com wrote: Anybody konw this? 2008/11/21 苏林冲 sulinchong1...@gmail.com Hi, all I have set below in setting.xml pluginGroups pluginGroupcom.mycompany.maven.plugins/pluginGroup /pluginGroups when i run myplugin:exec , maven print these in the console [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'myplugin'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-myplugin-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Nov 21 13:05:34 CST 2008 [INFO] Final Memory: 1M/2M [INFO] why does maven define the groupId org.apache.maven.plugins rather than com.mycompany.maven.plugins? And below is also the log infomation with -X + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\sulinchong.pt\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\Program Files\apache-maven-2.0.9\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'myplugin'. [DEBUG] Loading plugin prefixes from group: com.taobao.maven.plugins - does it work? [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] maven-myplugin-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-myplugin-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-myplugin-plugin:pom:LATEST [DEBUG] maven-myplugin-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-myplugin-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-myplugin-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-myplugin-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-myplugin-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-myplugin-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91) at
