[jira] Created: (MECLIPSE-204) Support to set the test output directory with property
Support to set the test output directory with property
--
Key: MECLIPSE-204
URL: http://jira.codehaus.org/browse/MECLIPSE-204
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Affects Versions: 2.2
Environment: -
Reporter: Martin Heitz
Priority: Minor
Problem still exists in version $Id: EclipsePlugin.java 479356 2006-11-26
13:24:31Z fgiust $
While it is possible to set a different output directory for compiled classes
using -DoutputDirectory= it is not possible to specify an output directory
for test classes. This is strange, because the plugin already creates a special
output directory when not called with -DoutputDirectory=. e.g.
classpathentry kind=src path=src/test/java output=target/test-classes/
classpathentry kind=src path=src/test/resources
output=target/test-classes/
classpathentry kind=output path=target/classes/
So it would also be easy, to add an option -DtestOutputDirectory=
Code to be changed is in the class EclipsePlugin:
String testOutput = null;
boolean useStandardOutputDir = buildOutputDirectory.equals( new File(
project.getBuild().getOutputDirectory() ) );
if ( useStandardOutputDir )
{
testOutput = IdeUtils.toRelativeAndFixSeparator( projectBaseDir,
new File( project.getBuild()
.getTestOutputDirectory() ), false );
}
Instead of doing the test for the standard dir, just check, if the option was
set instead.
REASON for the request:
We have tests, which check if some special interface is implemented by the
classes in the source and then execute tests for the classes found. But test
implementations of the interface shall not be tested.
Best regards from sunny Black Forrest, Germany,
Martin Heitz
--
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: (MANTRUN-37) Antrun breaks on multi-module builds
[ http://jira.codehaus.org/browse/MANTRUN-37?page=comments#action_73296 ] Martin Heitz commented on MANTRUN-37: - Having the same problem. Seems to be related to the use of xdoclet, which is loading antrun 1.0... Extract from pom: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.1/version executions ... Stack trace (which shows, that 1.0 is used, although 1.1 is configured) follows: INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run': Unable to find the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the plugin 'org.apache.maven.plugins:maven-antrun-plugin' Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-antrun-plugin:1.0:run. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run': Unable to find the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the plugin 'org.apache.maven.plugins:maven-antrun-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:538) 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:324) 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.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the plugin 'org.apache.maven.plugins:maven-antrun-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:533) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-antrun-plugin:1.0:run. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:524) ... 18 more Antrun breaks on multi-module builds Key: MANTRUN-37 URL: http://jira.codehaus.org/browse/MANTRUN-37 Project: Maven 2.x Antrun Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Maven 2.0.1 Reporter: Mike Perham Priority: Critical I just updated to antrun v1.1 (which needs to be marked as released in jira BTW) and find that my multimodule build is now breaking. Running the build in the child module itself works fine but if I build the parent, it fails when it gets
[jira] Created: (MECLIPSE-129) dependent .war files should be resolved and added to classpath
dependent .war files should be resolved and added to classpath -- Key: MECLIPSE-129 URL: http://jira.codehaus.org/browse/MECLIPSE-129 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: dependency resolution Reporter: Martin Heitz To set up an integration test eclipse project, I have a dependency to a WAR file containing a web service implementation. But the classes from the war file are not visible in the generated Eclipse project. In other words: the web service project is contained in the .project, but not in the generated .classpath file. Wish: .war files, where a project depends upon, should become part of the generated .classpath; dependencies which arise by the .war file should be added also to the generated .classpath. Best regards from sunny Black Forrest, Germany, Mattin -- 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-129) dependent .war files should be resolved and added to classpath
[ http://jira.codehaus.org/browse/MECLIPSE-129?page=comments#action_70175 ] Martin Heitz commented on MECLIPSE-129: --- Additionally to my use case this is necessary if having two .war projects: The first one contains standard web stuff (e.g. a basic MVC-Framework), the second one contains project-specific stuff (e.g. extensions of the MVC-Framework classes). dependent .war files should be resolved and added to classpath -- Key: MECLIPSE-129 URL: http://jira.codehaus.org/browse/MECLIPSE-129 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: dependency resolution Reporter: Martin Heitz To set up an integration test eclipse project, I have a dependency to a WAR file containing a web service implementation. But the classes from the war file are not visible in the generated Eclipse project. In other words: the web service project is contained in the .project, but not in the generated .classpath file. Wish: .war files, where a project depends upon, should become part of the generated .classpath; dependencies which arise by the .war file should be added also to the generated .classpath. Best regards from sunny Black Forrest, Germany, Mattin -- 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
