[jira] Commented: (MNG-1830) add a 'compiled on ' label when maven 2 is invoked with --version option
[ http://jira.codehaus.org/browse/MNG-1830?page=comments#action_60293 ] Rahul Thakur commented on MNG-1830: --- ping! Timestamp still doesn't show up. > add a 'compiled on ' label when maven 2 is invoked with --version > option > > > Key: MNG-1830 > URL: http://jira.codehaus.org/browse/MNG-1830 > Project: Maven 2 > Type: Improvement > Reporter: Rahul Thakur > Priority: Minor > > > It might be a good idea to append > 'compiled on ' > when maven2 is invoked with '--version' swtich/option, just like Ant does. > Can be helpful when compiling m2 locally 'n' times and need to ensure the m2 > installation was infact updated or when was it last updated. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MECLIPSE-71) eclipse:clean delets too much
[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_60044 ] Rahul Thakur commented on MECLIPSE-71: -- I think the eclipse:clean goal should delete any artifacts the maven-eclipse-plugin generates (+1 on Fabrizio's comment above), so stuff under .settings should be cleaned up! Perhaps a better way to re-create the config/prefs under .settings would be to write a small Mojo specific to your dev environment that can take care of re-creating required files consistently rather than having to control and share them via SVN. One another solution could be to have an "ignore" list (comma-separated list of paths to resources under the project) that indicates to the eclipse:clean goal which resources to skip when running a 'clean' goal. What do others think? > eclipse:clean delets too much > - > > Key: MECLIPSE-71 > URL: http://jira.codehaus.org/browse/MECLIPSE-71 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.1 > Reporter: Reinhard Poetz > > > If I call eclipse:clean, the complete ".settings" directory is deleted. In my > projects we share some Eclipse settings in our team by adding the .settings > directory to SVN. > This behaviour is unpractical for us as SVN gets confused by the missing > ./settings/.svn directory. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (ARCHETYPE-21) Unecessary java directory creation
[ http://jira.codehaus.org/browse/ARCHETYPE-21?page=comments#action_54670 ] Rahul Thakur commented on ARCHETYPE-21: --- I had a patch submitted for this a while ago and I see the relevant code is still in there in org.apache.maven.archetype.DefaultArchetype.java (see processTemplates(...) method ) Are you using a custom Archetype? Where are you trying to specify your source directory/directories? > Unecessary java directory creation > -- > > Key: ARCHETYPE-21 > URL: http://jira.codehaus.org/browse/ARCHETYPE-21 > Project: Maven Archetype > Type: Improvement > Components: maven-archetype-plugin > Reporter: Eric Redmond > Assignee: Jason van Zyl > Priority: Trivial > > > Whether specified in the archetype.xml or not, the plugin will generate the > path /src/main/java if tags are used. It would be nice if it only > honored the specified source dirs. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MECLIPSE-47) Planning support for wtp 1.0
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MECLIPSE-50) Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition
[ http://jira.codehaus.org/browse/MECLIPSE-50?page=all ] Rahul Thakur updated MECLIPSE-50: - Attachment: MECLIPSE-50.diff > Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via > composition > > > Key: MECLIPSE-50 > URL: http://jira.codehaus.org/browse/MECLIPSE-50 > Project: Maven 2.x Eclipse Plugin > Type: New Feature > Reporter: Rahul Thakur > Assignee: Jason van Zyl > Attachments: MECLIPSE-50.diff > > > Add getter/setter methods to Mojos under Eclipse Plugin to allow extension > and reuse via composition. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MECLIPSE-50) Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition
Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition Key: MECLIPSE-50 URL: http://jira.codehaus.org/browse/MECLIPSE-50 Project: Maven 2.x Eclipse Plugin Type: New Feature Reporter: Rahul Thakur Assigned to: Jason van Zyl Add getter/setter methods to Mojos under Eclipse Plugin to allow extension and reuse via composition. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1879) Allow dependencies to be defined in external profiles.xml for inclusion at build time when a profile is activated (and allow reuse of profies.xml)
Allow dependencies to be defined in external profiles.xml for inclusion at
build time when a profile is activated (and allow reuse of profies.xml)
--
Key: MNG-1879
URL: http://jira.codehaus.org/browse/MNG-1879
Project: Maven 2
Type: Improvement
Reporter: Rahul Thakur
Here's a use-case where I believe it would make sense to allow
to be defined for profiles in profiles.xml.
Lets says I have a web-project that sets up profiles.xml for target build
environments that it can be deployed on. Target environments can each have
different J2EE containers. Now this is what happens when I setup my project for
builds/deploys.
1) Set up a build control project, a minimal pom.xml that has contains SCM
connection to my web-project above.
2) checks out profiles.xml first so now the build control project has a minimal
pom + profiles.xml.
3) checks out the web-project under ${basedir}/target
4) I can activate a particular profile, based on which some operations can be
done by a custom Plugin before an embedded instance of maven is spawned
and some goals (specific to that profile) are delegated down to the checked out
project.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1830) add a 'compiled on ' label when maven 2 is invoked with --version option
add a 'compiled on ' label when maven 2 is invoked with --version option Key: MNG-1830 URL: http://jira.codehaus.org/browse/MNG-1830 Project: Maven 2 Type: Improvement Reporter: Rahul Thakur Priority: Minor It might be a good idea to append 'compiled on ' when maven2 is invoked with '--version' swtich/option, just like Ant does. Can be helpful when compiling m2 locally 'n' times and need to ensure the m2 installation was infact updated or when was it last updated. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1480) archetype-plugin copies sub-packaged source template files into wrong location
[ http://jira.codehaus.org/browse/MNG-1480?page=all ] Rahul Thakur updated MNG-1480: -- Attachment: MNG-1480.diff Submitted patch to fix this issue. Any extra directories other than the default ones should now get created in correct order, that is - after appropriate package structure has been created. > archetype-plugin copies sub-packaged source template files into wrong location > -- > > Key: MNG-1480 > URL: http://jira.codehaus.org/browse/MNG-1480 > Project: Maven 2 > Type: Bug > Versions: 2.0 > Environment: WindowsXP, Sun JDK1.4.2_08, Maven2.0 > Reporter: YOKOTA Takehiko > Attachments: MNG-1480.diff, Sample-archetype.zip > > > When generating project skelton using archetype-plugin and a custom archetype > which has > sub-packaged source template files, the plugin copies the source template > files into wrong > location. > For example, let a custom archetype have the following source template files: > archetype-resources/src/main/java/App.java > archetype-resources/src/main/java/impl/AppImpl.java > I expect the source files copied as the following: > PROJECTTOP/src/main/java/PACKAGE/App.java > PROJECTTOP/src/main/java/PACKAGE/impl/AppImpl.java > But the actual result is like the following: > PROJECTTOP/src/main/java/PACKAGE/App.java > PROJECTTOP/src/main/java/impl/PACKAGE/AppImpl.java > AFAIK, Maven1.x's genapp plugin behaves like I expect. Can you fix the > behavior If possible? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1480) archetype-plugin copies sub-packaged source template files into wrong location
[ http://jira.codehaus.org/browse/MNG-1480?page=all ] Rahul Thakur updated MNG-1480: -- Attachment: Sample-archetype.zip Sample Test archetype testcase to mimick this scenario. To use : a) extract the zip (should get extracted as an Eclipse Project) b) run 'mvn clean install' from the directory extracted to and from command prompt Patch follows... > archetype-plugin copies sub-packaged source template files into wrong location > -- > > Key: MNG-1480 > URL: http://jira.codehaus.org/browse/MNG-1480 > Project: Maven 2 > Type: Bug > Versions: 2.0 > Environment: WindowsXP, Sun JDK1.4.2_08, Maven2.0 > Reporter: YOKOTA Takehiko > Attachments: Sample-archetype.zip > > > When generating project skelton using archetype-plugin and a custom archetype > which has > sub-packaged source template files, the plugin copies the source template > files into wrong > location. > For example, let a custom archetype have the following source template files: > archetype-resources/src/main/java/App.java > archetype-resources/src/main/java/impl/AppImpl.java > I expect the source files copied as the following: > PROJECTTOP/src/main/java/PACKAGE/App.java > PROJECTTOP/src/main/java/PACKAGE/impl/AppImpl.java > But the actual result is like the following: > PROJECTTOP/src/main/java/PACKAGE/App.java > PROJECTTOP/src/main/java/impl/PACKAGE/AppImpl.java > AFAIK, Maven1.x's genapp plugin behaves like I expect. Can you fix the > behavior If possible? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1629) tag not terminated in archetype creation example
tag not terminated in archetype creation example -- Key: MNG-1629 URL: http://jira.codehaus.org/browse/MNG-1629 Project: Maven 2 Type: Improvement Components: documentation - guides Reporter: Rahul Thakur Priority: Trivial http://maven.apache.org/guides/mini/guide-creating-archetypes.html Section 1 my.groupId Tag not terminated. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-688) m2 archetype:create without -DgroupId and -DartifactId throws exception
[ http://jira.codehaus.org/browse/MNG-688?page=comments#action_47155 ] Rahul Thakur commented on MNG-688: -- Just wondering - could we extract all the [required] parameters/properties for a Mojo in runtime and create and display a usage/help message by default to the user when a plugin (any plugin) encounters org.apache.maven.plugin.PluginParameterException ? > m2 archetype:create without -DgroupId and -DartifactId throws exception > --- > > Key: MNG-688 > URL: http://jira.codehaus.org/browse/MNG-688 > Project: Maven 2 > Type: Bug > Components: maven-archetype-plugin > Versions: 2.0-alpha-3 > Reporter: Niklas Gustavsson > Priority: Minor > Fix For: 2.0-beta-4 > > > When running m2 archetype:create without the system properties -DgroupId and > -DartifactId an exception is thrown (see below). It would be great (and > probably helpful for developers) if these properties were asked for if > missing. > > org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for > exe > cution of 'archetype:create'. > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:169) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:150) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:133) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:103) > at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) > at org.codehaus.classworlds.Launcher.main(Launcher.java:363) > Caused by: org.apache.maven.plugin.PluginParameterException: Invalid or > missing > parameters: [Mojo parameter [name: 'artifactId'; alias: 'null'], Mojo > parameter > [name: 'groupId'; alias: 'null']] for mojo: > org.apache.maven.plugins:maven-arche > type-plugin:1.0-alpha-1:create > at > org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters( > DefaultPluginManager.java:764) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul > tPluginManager.java:527) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:373) > ... 15 more -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-303) property 'plexus.system.path' is being set to empty and results in maven, m2 and ant executables to be unresolved
property 'plexus.system.path' is being set to empty and results in maven, m2 and ant executables to be unresolved - Key: CONTINUUM-303 URL: http://jira.codehaus.org/browse/CONTINUUM-303 Project: Continuum Type: Bug Environment: Windows XP, Continuum SVN snapshot, Maven 2 SVN snapshot Reporter: Rahul Thakur ok, I have been noticing build failures on Integration tests for sometime now. On playing around with the PATH variables and looking at plexus DefaultExecutableResolver source, i noticed the following: a) plexus.system.path was being set to '' (empty string) on my system even though the PATH is set to include all reqd. executables. The PATH variable had values with space (ex: c:\Program Files\...) b) On running integ. tests with -Dplexus.system.path=%PATH% set on command line, the spaces in the path variable were not being handled correctly, seems like the 'path list' used to resolve executables is being set up incorrectly. I am not sure if this is better reported as an issue on Plexus JIRA or here. c) on running integ. tests with -Dplexus.system.path="%PATH%", the path list is being build up properly and executables are getting resolved. Not sure where this property is being set up in first place. In case, this being setup and passed via build script, would it be a good idea to have double quotes around PATH? -- 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
[jira] Created: (MNG-647) Allow Maven 2 to be monitored using JMX.
Allow Maven 2 to be monitored using JMX. Key: MNG-647 URL: http://jira.codehaus.org/browse/MNG-647 Project: Maven 2 Type: New Feature Components: design Reporter: Rahul Thakur Having JMX hooks in M2 to allow monitoring (and possibly runtime configuration) by JMX clients would be nice. This would be a neat feature especially where M2 is being used in embedded mode. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-479) unable to override the default central repository
[ http://jira.codehaus.org/browse/MNG-479?page=all ] Rahul Thakur updated MNG-479: - Attachment: DefaultModelInheritanceAssembler-with-updated-JUnitTest.diff Please use this one. Tested along with updated unit test. > unable to override the default central repository > - > > Key: MNG-479 > URL: http://jira.codehaus.org/browse/MNG-479 > Project: Maven 2 > Type: Bug > Components: maven-core > Versions: 2.0-alpha-2 > Environment: WinXP > Reporter: Edwin Punzalan > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > Attachments: DefaultModelInheritanceAssembler-with-updated-JUnitTest.diff, > DefaultModelInheritanceAssembler.diff > > > Adding to my pom.xml: > > > > central > custom repository > http://maven.company.com/maven2 > > > > did not override the central repository but instead uses the above configured > repository as backup/mirror. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-479) unable to override the default central repository
[ http://jira.codehaus.org/browse/MNG-479?page=all ] Rahul Thakur updated MNG-479: - Attachment: DefaultModelInheritanceAssembler.diff Minor patch. Haven't tested as the latest svn build is broken. > unable to override the default central repository > - > > Key: MNG-479 > URL: http://jira.codehaus.org/browse/MNG-479 > Project: Maven 2 > Type: Bug > Components: maven-core > Versions: 2.0-alpha-2 > Environment: WinXP > Reporter: Edwin Punzalan > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > Attachments: DefaultModelInheritanceAssembler.diff > > > Adding to my pom.xml: > > > > central > custom repository > http://maven.company.com/maven2 > > > > did not override the central repository but instead uses the above configured > repository as backup/mirror. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-202) Add support of .pac file for proxy configuration
[ http://jira.codehaus.org/browse/MNG-202?page=comments#action_42278 ] Rahul Thakur commented on MNG-202: -- another resource: http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/proxie_config.html#automatic > Add support of .pac file for proxy configuration > > > Key: MNG-202 > URL: http://jira.codehaus.org/browse/MNG-202 > Project: Maven 2 > Type: New Feature > Reporter: Emmanuel Venisse > Priority: Minor > Fix For: 2.0-beta-2 > > > Authorize Proxy Auto-Config File (.pac file) for proxy configuration in user > model. > http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html > =>Use rhino for read the pac file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-30) Upload Snowball porter stemmer library
Upload Snowball porter stemmer library --- Key: MEV-30 URL: http://jira.codehaus.org/browse/MEV-30 Project: Maven Evangelism Type: New Feature Components: Dependencies Reporter: Rahul Thakur Snowball is available at: http://snowball.tartarus.org/download.php -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-490) Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated.
[ http://jira.codehaus.org/browse/MNG-490?page=all ] Rahul Thakur updated MNG-490: - Attachment: DefaultArchetype.diff DefaultArchetype now overrides defaults if following are specified in the POM template: - source directory - test source directory - resources director(y/ies) - test resource director(y/ies) - script source directory Re. Overriding the default archetype resource location within the archetype JAR An alternative to do this would be to have a tag, say , in the archetype descriptor that points to the location under which all the archetype resources are sitting. This, however, hasn't been implemented as this would require change in method signature for processTemplate() in DefaultArchetype class. > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated. > -- > > Key: MNG-490 > URL: http://jira.codehaus.org/browse/MNG-490 > Project: Maven 2 > Type: Bug > Environment: Windows XP, JDK 1.5.0, Maven2 SVN > Reporter: Rahul Thakur > Fix For: 2.0-beta-1 > Attachments: DefaultArchetype.diff > > > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated, even > though these are being created empty. > I created an archetype and need to follow a set folder structure (all java > sources to sit under folder "src" and tests under "test" folder respectively) > Also the Archetype plugin makes an assumption that the archetype resources > will always reside under "archetype-resources/". User should be able to > override this and specify a custom name. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-490) Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated.
[ http://jira.codehaus.org/browse/MNG-490?page=comments#action_41763 ] Rahul Thakur commented on MNG-490: -- ok, an update on this one and some notes : 'archetype.xml' or archetype descriptor contains elements that need to be merged and copied over when a new archetype is being created. For projects with a custom archetypes/skeletons, it would be desirable to copy sources, testsources and resources defined in archetype.xml to appropriate directories referred by the POM template. This is how I have gone about implementing it so far: a) create a POM model instance from the generated POM for the archetype resources(skeleton resources). b) check if following definitions are set up in generated POM : b-1) sourceDirectory : if yes, create it and then process sources defined via archetype descriptor's tag and copy them to source directory defined in POM. b-2) testSourceDirectory: same deal as (b-1) b-3) resources/resource: Iterate and create directories for each resource and then copy over the one's defined in archetype.xml ( tag) b-4) testResources/resource: same deal as (b-3) Now, the problem I am hitting (assuming I am on right track!) is that if there is a directory defined as a resource in case of (b-3) and (b-4) I am not sure of a way to copy them over to the target archetype that is being setup. Also, I'd like to be able to specify nested resources via the archetype descriptor, for instance: [snip] bare/readme.txt build/** (this should copy 'build' dir and everything under it) [/snip] Ideally, I think we'd like to have everything defined by the archetype skeleton to be copied over to the target project. Do you think this is a reasonable/rational extension to add to the existing archetype creation mechanism. Look forward to thoughts... > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated. > -- > > Key: MNG-490 > URL: http://jira.codehaus.org/browse/MNG-490 > Project: Maven 2 > Type: Bug > Environment: Windows XP, JDK 1.5.0, Maven2 SVN > Reporter: Rahul Thakur > Fix For: 2.0-beta-1 > > > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated, even > though these are being created empty. > I created an archetype and need to follow a set folder structure (all java > sources to sit under folder "src" and tests under "test" folder respectively) > Also the Archetype plugin makes an assumption that the archetype resources > will always reside under "archetype-resources/". User should be able to > override this and specify a custom name. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-490) Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated.
[ http://jira.codehaus.org/browse/MNG-490?page=comments#action_41674 ] Rahul Thakur commented on MNG-490: -- Yep! This is mine :-) > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated. > -- > > Key: MNG-490 > URL: http://jira.codehaus.org/browse/MNG-490 > Project: Maven 2 > Type: Bug > Environment: Windows XP, JDK 1.5.0, Maven2 SVN > Reporter: Rahul Thakur > Fix For: 2.0-beta-1 > > > Creating an archetype with a different folder structure for java and test > sources still results in default (src/main/java) folder being generated, even > though these are being created empty. > I created an archetype and need to follow a set folder structure (all java > sources to sit under folder "src" and tests under "test" folder respectively) > Also the Archetype plugin makes an assumption that the archetype resources > will always reside under "archetype-resources/". User should be able to > override this and specify a custom name. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-490) Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated.
Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated. -- Key: MNG-490 URL: http://jira.codehaus.org/browse/MNG-490 Project: Maven 2 Type: Bug Environment: Windows XP, JDK 1.5.0, Maven2 SVN Reporter: Rahul Thakur Creating an archetype with a different folder structure for java and test sources still results in default (src/main/java) folder being generated, even though these are being created empty. I created an archetype and need to follow a set folder structure (all java sources to sit under folder "src" and tests under "test" folder respectively) Also the Archetype plugin makes an assumption that the archetype resources will always reside under "archetype-resources/". User should be able to override this and specify a custom name. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-432) install:install-file relies on a project when it shouldn't need to
[ http://jira.codehaus.org/browse/MNG-432?page=comments#action_41319 ] Rahul Thakur commented on MNG-432: -- Where can I gather more info on this one ? I can look into this one if no one's picked this one up yet. Thanks, Rahul > install:install-file relies on a project when it shouldn't need to > -- > > Key: MNG-432 > URL: http://jira.codehaus.org/browse/MNG-432 > Project: Maven 2 > Type: Bug > Reporter: Brett Porter > Fix For: 2.0-alpha-3 > > -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-202) Add support of .pac file for proxy configuration
[ http://jira.codehaus.org/browse/MNG-202?page=comments#action_41318 ] Rahul Thakur commented on MNG-202: -- Hi, Is anyone working on this one ? If not, I can pick this up. Could someone let me know how we intended to go about this, i.e. I am not sure about what the 'user model' in the firs comment pertains to? Thanks, Rahul > Add support of .pac file for proxy configuration > > > Key: MNG-202 > URL: http://jira.codehaus.org/browse/MNG-202 > Project: Maven 2 > Type: New Feature > Reporter: Emmanuel Venisse > Priority: Minor > Fix For: 2.0-beta-1 > > > Authorize Proxy Auto-Config File (.pac file) for proxy configuration in user > model. > http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html > =>Use rhino for read the pac file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-261) don't create parent directories when artifact not downloaded
[ http://jira.codehaus.org/browse/MNG-261?page=all ] Rahul Thakur updated MNG-261: - Attachment: AbstractWagon.diff AbstractWagon now takes care of creating parent directories for file/artifact being downloaded. > don't create parent directories when artifact not downloaded > > > Key: MNG-261 > URL: http://jira.codehaus.org/browse/MNG-261 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Trivial > Fix For: 2.0-alpha-3 > Attachments: AbstractWagon.diff, DefaultWagonManager.diff > > > directories are created first - it should only be done by wagon, at the point > it is actually needed -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-261) don't create parent directories when artifact not downloaded
[ http://jira.codehaus.org/browse/MNG-261?page=all ] Rahul Thakur updated MNG-261: - Attachment: DefaultWagonManager.diff Wagon Manager now lets the Wagon Implementation take care of parent directory creation for an artifact. > don't create parent directories when artifact not downloaded > > > Key: MNG-261 > URL: http://jira.codehaus.org/browse/MNG-261 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Trivial > Fix For: 2.0-alpha-3 > Attachments: DefaultWagonManager.diff > > > directories are created first - it should only be done by wagon, at the point > it is actually needed -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-261) don't create parent directories when artifact not downloaded
[ http://jira.codehaus.org/browse/MNG-261?page=comments#action_41045 ] Rahul Thakur commented on MNG-261: -- If this is to be handled by Wagon, does that means that an issue needs to be opened with Wagon project. I think this fix will impact both projects, i.e., moving creation of directories from Artifact Deployer to Wagon implementations. Is my understanding correct? > don't create parent directories when artifact not downloaded > > > Key: MNG-261 > URL: http://jira.codehaus.org/browse/MNG-261 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Trivial > Fix For: 2.0-alpha-3 > > > directories are created first - it should only be done by wagon, at the point > it is actually needed -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-276) Make out output from archetype more informative
[ http://jira.codehaus.org/browse/MNG-276?page=comments#action_40822 ] Rahul Thakur commented on MNG-276: -- ohh, and the patch is for file: org.apache.maven.archetype.DefaultArchetype.java > Make out output from archetype more informative > --- > > Key: MNG-276 > URL: http://jira.codehaus.org/browse/MNG-276 > Project: Maven 2 > Type: Improvement > Versions: 2.0-alpha-2 > Reporter: Jason van Zyl > Assignee: Brett Porter > Fix For: 2.0-alpha-3 > Attachments: DefaultArchetype.diff > > > Let the user know where the project was generated and display the parameters > used during generation. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-276) Make out output from archetype more informative
[ http://jira.codehaus.org/browse/MNG-276?page=all ] Rahul Thakur updated MNG-276: - Attachment: DefaultArchetype.diff Hi Brett, I have attached a patch for this issue. Since this is my 'first ever open source' patch :-), please let me know if there is anything (code convention, formatting, or anything) I need to revisit or be aware of. Thanks, (Visible to jira-users) > Make out output from archetype more informative > --- > > Key: MNG-276 > URL: http://jira.codehaus.org/browse/MNG-276 > Project: Maven 2 > Type: Improvement > Versions: 2.0-alpha-2 > Reporter: Jason van Zyl > Assignee: Brett Porter > Fix For: 2.0-alpha-3 > Attachments: DefaultArchetype.diff > > > Let the user know where the project was generated and display the parameters > used during generation. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-86) m2-bootstrap-all.bat fails if ${maven.home} contains spaces
[ http://jira.codehaus.org/browse/MNG-86?page=comments#action_40628 ]
Rahul Thakur commented on MNG-86:
-
This looks to be working OK. I tested this with M2_HOME set with spaces, the
batch script (m2-bootstrap-all.bat) ran and installed M2 in target folder.
> m2-bootstrap-all.bat fails if ${maven.home} contains spaces
> ---
>
> Key: MNG-86
> URL: http://jira.codehaus.org/browse/MNG-86
> Project: Maven 2
> Type: Bug
> Environment: Windows XP SP2, JDK 1.4.2_05
> Reporter: Magne Rasmussen
> Priority: Trivial
> Attachments: MNG-86.patch
>
>
> m2-bootstrap-all.bat (CVS rev. 1.4) fails on line 114 if
> M2_HOME=%USERPROFILE%/m2 (expands to 'C:\Documents and Settings\User/m2').
> This can be fixed by replacing line 104 with:
> SET MAVEN_CMD_LINE_ARGS=%MAVEN_CMD_LINE_ARGS% -Dmaven.home="%M2_HOME%"
> The same error manifests itself in maven-core-it/maven-core-it.bat, where
> line 23 can be replaced with:
> %JAVA_HOME%\bin\java.exe %* -Dmaven.home="%M2_HOME%" -cp
> "..\maven-core-it-verifier\target\maven-core-it-verifier-1.0.jar"
> org.apache.maven.it.Verifier
> as a fix.
> There will be a lot of errors if M2_HOME is set like 'SET
> M2_HOME="C:\Documents and Settings\User\m2"' (notice double qoutes around the
> path). These qoutes should probably be stripped before trying to use M2_HOME
> in any script. Or a suitable warning could be put in the docs :-)
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
