[
http://jira.codehaus.org/browse/MIDEA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171613#action_171613
]
Rama Notowidigdo commented on MIDEA-119:
----------------------------------------
It's interesting you mentioned that but it's recommended on maven website,
specially when you're migrating from ant that has been used for years to maven,
radical changes is hard to do at one time and should be in phases. This would
accomodate that.
http://maven.apache.org/guides/mini/guide-using-one-source-directory.html
> sourceDirectory that's not direct children of the current directory doesn't
> get pick up when issuing maven idea:idea
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-119
> URL: http://jira.codehaus.org/browse/MIDEA-119
> Project: Maven 2.x IDEA Plugin
> Issue Type: Bug
> Reporter: Rama Notowidigdo
>
> When issuing mvn idea:idea with the following pom:
> <modelVersion>4.0.0</modelVersion>
> <artifactId>xxxxx</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> <packaging>jar</packaging>
> <build>
> <sourceDirectory>../../build/java</sourceDirectory>
> </build>
> The module created doesn't pickup the source directory.
> But it works fine if I"m pointing a directory that's a child directory from
> the current dir:
> When issuing mvn idea:idea with the following pom:
> <modelVersion>4.0.0</modelVersion>
> <artifactId>xxxxx</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> <packaging>jar</packaging>
> <build>
> <sourceDirectory>build/java</sourceDirectory>
> </build>
> build directory is the child of the current dir.
--
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
