[jira] Commented: (MECLIPSE-156) Plugin should support setting file encoding
[ http://jira.codehaus.org/browse/MECLIPSE-156?page=comments#action_76895 ] Ralph Poellath commented on MECLIPSE-156: - All my files under version conrol need to be UTF-8 encoded. Whenever I create a new Eclipse workspace, I have to manually switch the encoding from platform default to UTF-8. Since I generate all Eclipse project files using the Maven Eclipse plugin already, I could use this functionality to work around the real problem (that Eclipse won't let me override the default for new workspaces). For me, this would not create additional complexity in the POM, because I have to configure the Maven Eclipse plugin anyway. > Plugin should support setting file encoding > --- > > Key: MECLIPSE-156 > URL: http://jira.codehaus.org/browse/MECLIPSE-156 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Ralph Poellath > > The plugin should support setting Eclipse's text file encoding on a > per-project basis. -- 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] Commented: (MWAR-79) copy fails in a multi-project build
[ http://jira.codehaus.org/browse/MWAR-79?page=comments#action_76896 ] Milos Kleint commented on MWAR-79: -- MWAR-77 might be a duplicate of this one. MRESOURCES-32 also related > copy fails in a multi-project build > -- > > Key: MWAR-79 > URL: http://jira.codehaus.org/browse/MWAR-79 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Maven 2.0.4, maven-war-plugin trunk r453448, Sun Java > 1.5, Ubuntu Linux >Reporter: Elliot Metsger > Attachments: MWAR-79.patch, test-project.tar.gz > > > In this example project (attached as test-project.tar.gz) > |-- foo-bar-webapp > | |-- pom.xml > | `-- src > | `-- main > | |-- resources > | | `-- foo.properties > | `-- webapp > | |-- WEB-INF > | | `-- web.xml > | `-- index.jsp > `-- pom.xml > Executing 'mvn package' from the foo-bar-webapp directory succeeds, but > executing 'mvn package' from the parent project directory fails with: > java.lang.IllegalStateException: basedir src/main/resources does not exist > at > org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542) > at > org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles(AbstractWarMojo.java:821) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:405) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:515) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:344) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:161) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:127) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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 foo-bar-webapp/pom.xml contains: > > foo-bar-webapp > > > maven-war-plugin > > > > src/main/resources > true > > > > > > -- 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: (DOXIA-76) Doxia misses line breaks in apt when \ is not followed by \n
Doxia misses line breaks in apt when \ is not followed by \n Key: DOXIA-76 URL: http://jira.codehaus.org/browse/DOXIA-76 Project: doxia Issue Type: Bug Components: Core Affects Versions: 1.0-alpha-8 Environment: Windows XP Reporter: Mathieu Champlon Trying to force a line break in an apt file using \ as explained in [1] does not work on the windows platform. A test case is provided as a very simple maven project using the minimal pom from [2] and only an index.apt file in src/main/site/apt Simply run 'mvn site' on a windows box to reproduce the issue. The resulting page fom target/site/index.html displays : Line\ break. instead of : Line break. [1] http://maven.apache.org/guides/mini/guide-apt-format.html [2] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html -- 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] Updated: (DOXIA-76) Doxia misses line breaks in apt when \ is not followed by \n
[ http://jira.codehaus.org/browse/DOXIA-76?page=all ] Mathieu Champlon updated DOXIA-76: -- Attachment: DOXIA-76.patch DOXIA-76_testcase.zip > Doxia misses line breaks in apt when \ is not followed by \n > > > Key: DOXIA-76 > URL: http://jira.codehaus.org/browse/DOXIA-76 > Project: doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.0-alpha-8 > Environment: Windows XP >Reporter: Mathieu Champlon > Attachments: DOXIA-76.patch, DOXIA-76_testcase.zip > > > Trying to force a line break in an apt file using \ as explained in [1] does > not work on the windows platform. > A test case is provided as a very simple maven project using the minimal pom > from [2] and only an index.apt file in src/main/site/apt > Simply run 'mvn site' on a windows box to reproduce the issue. > The resulting page fom target/site/index.html displays : > Line\ break. > instead of : > Line > break. > [1] http://maven.apache.org/guides/mini/guide-apt-format.html > [2] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html -- 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: (MIDEA-70) Idea Plugin does not handle any kind of Version ranges
Idea Plugin does not handle any kind of Version ranges -- Key: MIDEA-70 URL: http://jira.codehaus.org/browse/MIDEA-70 Project: Maven 2.x Idea Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Jan Thomae Priority: Blocker I am using version ranges in my project. For example, i have specified a range for hibernate: org.hibernate hibernate [3.1.3,) Now idea:idea tries to download http://repo1.maven.org/maven2/org/hibernate/hibernate/[3.1.3,)/hibernate-[3.1.3,).pom instead of recognizing that i have given a range and looking for an appropriate version. Since it cannot resolve the dependency, it does not create any dependencies for the module at all. Even worse, it crashes if any dependency uses version ranges. I could live with the issue and stick to fixed versions for the time being, however i have no control about the poms of the dependencies i am linking, so if a pom of a dependency is containing a version range, i am totally out of luck. E.g one of my modules references to jasperreports: jasperreports jasperreports 1.2.7 which itself contains a ranged dependency. When i try to do idea:idea on that one i get: INFO] Building TTT 2006 Reporting Plugin [INFO]task-segment: [idea:idea] [INFO] [INFO] Preparing idea:idea [INFO] No goals needed for project - skipping [INFO] [idea:idea] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Unable to build project dependencies. -- 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: (MIDEA-71) Sources are not consistently attached to dependencies
Sources are not consistently attached to dependencies - Key: MIDEA-71 URL: http://jira.codehaus.org/browse/MIDEA-71 Project: Maven 2.x Idea Plugin Issue Type: Bug Reporter: Jan Thomae Attachments: module1.jpg, module2.jpg, root-pom.xml I have a multimodule project, where all submodules depend on commons-logging (and other modules). When i run idea:idea with downloadSources enabled, the sources for commons logging are correctly downloaded, and commons logging is added to the dependency list of all modules. However, the sources are only added to some of the modules, not all of them. I wasnt able yet, to find out some reason for this. I have attached two shots of one module with attached source and one without, plus the root pom and the module poms -- 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] Updated: (MIDEA-71) Sources are not consistently attached to dependencies
[ http://jira.codehaus.org/browse/MIDEA-71?page=all ] Jan Thomae updated MIDEA-71: Attachment: server-pom.xml admin-pom.xml > Sources are not consistently attached to dependencies > - > > Key: MIDEA-71 > URL: http://jira.codehaus.org/browse/MIDEA-71 > Project: Maven 2.x Idea Plugin > Issue Type: Bug >Reporter: Jan Thomae > Attachments: admin-pom.xml, module1.jpg, module2.jpg, root-pom.xml, > server-pom.xml > > > I have a multimodule project, where all submodules depend on commons-logging > (and other modules). When i run idea:idea with downloadSources enabled, the > sources for commons logging are correctly downloaded, and commons logging is > added to the dependency list of all modules. However, the sources are only > added to some of the modules, not all of them. I wasnt able yet, to find out > some reason for this. I have attached two shots of one module with attached > source and one without, plus the root pom and the module poms -- 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] Commented: (MNGECLIPSE-201) IllegalArgumentException on Fedora Eclipse 3.1.2
[ http://jira.codehaus.org/browse/MNGECLIPSE-201?page=comments#action_76900 ] Henning Schmiedehausen commented on MNGECLIPSE-201: --- Yep, same error here. Platform is Windows XP, Eclipse 3.2.1, Java-1.5.0. > IllegalArgumentException on Fedora Eclipse 3.1.2 > > > Key: MNGECLIPSE-201 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-201 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug >Affects Versions: 0.0.9 > Environment: Fedora Core 5, Fedora Eclipse 3.1.2, > java-1.4.2-gcj-compat-1.4.2.0, libgcj-4.1.1-1 >Reporter: Ricardo Gladwell >Priority: Critical > Attachments: stacktrace.txt > > > I get the attached IllegalArgumentException after install of plugin when > trying to access Maven 2 Eclipse Plugin features (right clicking Maven -> > Enable, Preferences -> Maven, etc). Plugin does not work at all. -- 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] Commented: (MNGECLIPSE-201) IllegalArgumentException on Fedora Eclipse 3.1.2
[ http://jira.codehaus.org/browse/MNGECLIPSE-201?page=comments#action_76901 ] Henning Schmiedehausen commented on MNGECLIPSE-201: --- Same behaviour with 0.0.8. Not even the preferences window can be opened. Quite disappointing. > IllegalArgumentException on Fedora Eclipse 3.1.2 > > > Key: MNGECLIPSE-201 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-201 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug >Affects Versions: 0.0.9 > Environment: Fedora Core 5, Fedora Eclipse 3.1.2, > java-1.4.2-gcj-compat-1.4.2.0, libgcj-4.1.1-1 >Reporter: Ricardo Gladwell >Priority: Critical > Attachments: stacktrace.txt > > > I get the attached IllegalArgumentException after install of plugin when > trying to access Maven 2 Eclipse Plugin features (right clicking Maven -> > Enable, Preferences -> Maven, etc). Plugin does not work at all. -- 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] Commented: (MECLIPSE-120) Force inter-project dependencies
[ http://jira.codehaus.org/browse/MECLIPSE-120?page=comments#action_76908 ]
Kenney Westerhof commented on MECLIPSE-120:
---
Hi Joerg,
Your first problem is another issue (MECLIPSE-152), that I'd like to see solved
there. Forcing snapshot versions only fixes
that problem in certain situations.
But you actually mean -forceProjectReference here, right?
Second issue: I see that as a good thing - you'll find out soon enough which
artifacts are affected by a change since you can't change them
because they reference jar files, not projects.
Also, when you do a lot of refactoring etc, I get the impression you don't have
multiple release cycles, but just 1, for the entire project tree.
If that's the case, you could use a dependencyManagement section in the root
pom, specifying ${version} for all modules. That way they're always
referring to reactor/workspace projects. This should fix your issue, no?
Third issue: this is fixing it afterwards, and hoping that the developer will
indeed update the poms. As I mentioned above, if you still have
jar references and not project references, you're forced to update the pom at
that time, or decide not to since it's an unwanted change.
Isn't that safer? Developers are confronted with making a good decision on what
to upgrade and what for.
What I meant with my third comment is that you see stuff working in eclipse,
but it won't compile on the commandline. That gives the developer
another responsibility - mvn install before a commit, and update the poms. It's
an iterative process and requires more time on big projects. Just
updating a pom and mvn eclipse:eclipse, then refresh in eclipse gives you much
faster feedback on wheter it still works.
On the EAR thing: shouldn't that be solved in the dependencyManagement section?
That way it'll work both for eclipse and on the commandline.
Let me know what you think. I feel this change will probably make things worse
because it requires a lot of extra attention from developers,
and makes it much easier for them to commit breaking builds.
> Force inter-project dependencies
>
>
> Key: MECLIPSE-120
> URL: http://jira.codehaus.org/browse/MECLIPSE-120
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: multiproject
>Affects Versions: 2.2
>Reporter: Joerg Schaible
>
> In a multi-module setup, the dependencies between the projects are only
> created, if the project's version match the one of the referenced artfiact.
> After a release this is normally no longer the case if you have modules with
> independent release cycles. Therefore it would be good, if the plugin could
> be forced with an option (e.g. -forceSnapshot) to use a dependency to a
> module's project with a snapshot version instead of a dependency to the
> released artifact in the local repository. The plugin detects this situation
> already, but logs just a warning. Without this feature, refactorings are
> getting really tedious.
--
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] Commented: (MECLIPSE-156) Plugin should support setting file encoding
[ http://jira.codehaus.org/browse/MECLIPSE-156?page=comments#action_76910 ] Kenney Westerhof commented on MECLIPSE-156: --- Ah okay. Why won't eclipse let you override the workspac default? Window->Preferences-> General -> Workspace contains the file encoding and line ending setting. Actually, allowing different settings on a per project basis is only needed if the settings really differ per project. Nevertheless, if that's the case, it's pretty easy to support in the eclipse plugin and probably a desired feature. > Plugin should support setting file encoding > --- > > Key: MECLIPSE-156 > URL: http://jira.codehaus.org/browse/MECLIPSE-156 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Ralph Poellath > > The plugin should support setting Eclipse's text file encoding on a > per-project basis. -- 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] Commented: (MECLIPSE-152) Write .classpath with ordered dependencies [incl. Patch]
[ http://jira.codehaus.org/browse/MECLIPSE-152?page=comments#action_76917 ] Kenney Westerhof commented on MECLIPSE-152: --- Hm, actually, when I just disable the 'exported' flag on dependencies, the problem above goes away. I tested reordering the dependencies but this doesn't work in eclipse 3.2. Even though the correct dep is listed first, it still resolves to the second one. Weird. > Write .classpath with ordered dependencies [incl. Patch] > > > Key: MECLIPSE-152 > URL: http://jira.codehaus.org/browse/MECLIPSE-152 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.2 > Environment: Windowz XP, eclipse 3.2 >Reporter: Holger Hoffstätte > Attachments: orderDependencies.patch, orderDependencies.patch > > > Related to my comment in MNG-1412 - I decided to take a quick stab at the > eclipse plugin and voilá! Ordered dependencies in the written .classpath. > This is only a prototype (my first attempt at maven development) and could > serve as basis for other orderings like groupId, transitive nearness etc. > Initially I wanted to make IdeDependency comparable (similar to MECLIPSE-150 > which added proper equals) but having multiple Comparators seemed better for > extensibility. > It worked right away, does exactly what I want (ordering by artifactId) and > has minimal impact. I am not familiar with the maven codebase so I hope this > is the right place to do the actual ordering before writing; obviously it > should observe a property like -DorderDependencies=artifactId or something > similar. The patch is against svn r425750 (2006-08-30). Currently no testcase > but if someone tells me how to add/read an orderDependencies property I might > add one. > Comments welcome. -- 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] Commented: (MECLIPSE-34) Goals to build eclipse plugin/feature and site
[ http://jira.codehaus.org/browse/MECLIPSE-34?page=comments#action_76925 ] Eugene Kuleshov commented on MECLIPSE-34: - Kenney, I just don't see how can you do that. Build still require Eclipse install to get dependencies and I don't think it would be a good idea to move these tependencies into Maven repo, unless you use Eclipse istall as a repository and also read Eclipse's manifests and plugin.xml's for dependency resolution... Sounds like more complicated task to me. > Goals to build eclipse plugin/feature and site > -- > > Key: MECLIPSE-34 > URL: http://jira.codehaus.org/browse/MECLIPSE-34 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: PDE support >Affects Versions: 2.0 >Reporter: Eugene Kuleshov > > Please provide new goals to build eclipse plugin/feature and site using > Eclipse's builder. > See following articles on the topic: > Build and Test Automation for plug-ins and features > http://eclipse.org/articles/Article-PDE-Automation/automation.html > Followup article - Building features and plugins with Ant > http://eclipse.techforge.com/index.php/articles/188 > So, plugin can issue command like this: > set ECLIPSE_HOME=D:\eclipse\eclipse-3.0.2 > java -cp %ECLIPSE_HOME%\startup.jar org.eclipse.core.launcher.Main > -application org.eclipse.ant.core.antRunner -buildfile build.xml > -Dcomponent=sdk.examples -Dconfigs="*,*,*" -Dbaseos=win32 -Dbasews=win32 > -Dbasearch=x86 -Djavacfailonerror=true > -Dpde.build.scripts=%ECLIPSE_HOME%/plugins/org.eclipse.pde.build_3.0.1/scripts > -DbaseLocation=%ECLIPSE_HOME% > It will sort of run ant under the hood, but nobody will see it... -- 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] Updated: (MNGECLIPSE-200) Maven Enabled Projects should have target directory marked as derived
[ http://jira.codehaus.org/browse/MNGECLIPSE-200?page=all ] Eugene Kuleshov updated MNGECLIPSE-200: --- Priority: Minor (was: Major) No plans to work on this any time soon, but patch would be appreciated. > Maven Enabled Projects should have target directory marked as derived > - > > Key: MNGECLIPSE-200 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-200 > Project: Maven 2.x Extension for Eclipse > Issue Type: Improvement >Affects Versions: 0.0.9 >Reporter: Yuri Schimke >Priority: Minor > > I currently have to manually mark the target directory as derived. Otherwise > I get multiple copies of resource files etc. once in src and once in target. > On an incremental build, the Maven Plugin could check this directory is > marked as derived. -- 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] Closed: (MNGECLIPSE-201) IllegalArgumentException on Fedora Eclipse 3.1.2
[ http://jira.codehaus.org/browse/MNGECLIPSE-201?page=all ] Eugene Kuleshov closed MNGECLIPSE-201. -- Resolution: Duplicate > IllegalArgumentException on Fedora Eclipse 3.1.2 > > > Key: MNGECLIPSE-201 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-201 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug >Affects Versions: 0.0.9 > Environment: Fedora Core 5, Fedora Eclipse 3.1.2, > java-1.4.2-gcj-compat-1.4.2.0, libgcj-4.1.1-1 >Reporter: Ricardo Gladwell >Priority: Critical > Attachments: stacktrace.txt > > > I get the attached IllegalArgumentException after install of plugin when > trying to access Maven 2 Eclipse Plugin features (right clicking Maven -> > Enable, Preferences -> Maven, etc). Plugin does not work at all. -- 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: (SUREFIRE-55) Incorrect splitting of command line arguments in ForkConfiguration
Incorrect splitting of command line arguments in ForkConfiguration -- Key: SUREFIRE-55 URL: http://jira.codehaus.org/browse/SUREFIRE-55 Project: surefire Issue Type: Bug Affects Versions: 2.1, 2.2 Environment: any Reporter: Walco van Loon Attachments: argline.patch ForkConfiguration.createCommandLine splits argLine on spaces, where it should use org.codehaus.plexus.util.cli.Commandline.setLine to create an argLine which splits quoted arguments containing spaces correctly. -- 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: (MSUREFIRE-171) Add support for specifying and configuring java instrumentation agents for tests being launched in a new jvm
Add support for specifying and configuring java instrumentation agents for tests being launched in a new jvm Key: MSUREFIRE-171 URL: http://jira.codehaus.org/browse/MSUREFIRE-171 Project: Maven 2.x Surefire Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Walco van Loon Attachments: javaagent-support.patch JDK 1.5 added a new feature for instrumenting byte code in Java (See java.lang.Instrument for more information). The attached patch adds support for configuration of java agents and agent dependencies on the surefire command line, when forking is enabled. The code used to configure the jvm argLine does not use any JDK 1.5 features. Test cases are included. The java.lang.Instrument approach has a few advantages: 1) no stale instrumented classes 2) no need for forked lifecycles and hacks to get the instrumented classes on the classpath 3) any class that is loaded into the jvm can be instrumented -- 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
