Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails when pom is a parent. #137

Closed
s17t opened this issue Aug 21, 2013 · 9 comments
Closed

Build fails when pom is a parent. #137

s17t opened this issue Aug 21, 2013 · 9 comments

Comments

@s17t
Copy link

s17t commented Aug 21, 2013

I have a parent pom in which the plugin is configured. When I install the parent pom with:

mvn install

The build fails:

[ERROR] NotDirectoryException -> [Help 1]
Path([OMISSIS]/target/test-classes) is not a directory so descendants can not be called on itis not a directory
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NotDirectoryException

To get the build work I have to specify -DskipTests option.

@davidB
Copy link
Owner

davidB commented Aug 21, 2013

Hi,

Can you provide the pom.xml (where do you configure the plugin) and the exception stacktrace (run mvn with '-e' ) ?

@s17t
Copy link
Author

s17t commented Aug 21, 2013

Hi,
the previous message comes from mvn -e already. Here you can find the plugin configuration.

Thank you.

@davidB
Copy link
Owner

davidB commented Aug 21, 2013

the pom fragment doesn't show where the plugin is configured : in pluginConfiguration, in build/plugins, in a profile,....
You don't have stackstrace with -e ?
You don't have issue with target/classes ? (strange)

@davidB
Copy link
Owner

davidB commented Aug 21, 2013

A side note about your pom :

  • you don't need to use build-helper-maven-plugin, the 'add-source' goal of the scala-maven-plugin do the job
  • you can remove the maven-eclipse-plugin configuration, it's better to use m2e (less issue) and the configuration you provide is for an old version of the eclipse plugin (IIRC for scala-2.7 and less)

@s17t
Copy link
Author

s17t commented Aug 26, 2013

I updated my parent pom plugins configuration here. I bumped up to latest version of maven-eclipse-plugin (eclipse is fine with Scala from mvn eclipse:eclipse) and I removed maven-helper-plugin.

The original problem still there. For completeness, I run mvn with -X but there is no there is no stack-trace neither.

Thank for your support.

@holograph
Copy link

The Scala plugin bit looks just fine, so there's likely something else
going on. If you can't just post your entire POMs on Gist or something, can
you please include the section defining the source/test
directories, and the section for Surefire?

On Mon, Aug 26, 2013 at 10:08 PM, s17t.net notifications@github.com wrote:

I updated my parent pom plugins configuration herehttp://nopaste.info/7f3479b999.html.
I bumped up to latest version of maven-eclipse-plugin (eclipse is fine with
Scala from mvn eclipse:eclipse) and I removed maven-helper-plugin.

The original problem still there. For completeness, I run mvn with -X but
there is no there is no stack-trace neither.

Thank for your support.


Reply to this email directly or view it on GitHubhttps://github.com//issues/137#issuecomment-23287054
.

@s17t
Copy link
Author

s17t commented Aug 27, 2013

Here the part (Scala bit omitted for brevity).

I also tried

mkdir -p src/main/{java,scala}

in the project folder but the error is the same.

Thank for your support.

@davidB
Copy link
Owner

davidB commented Aug 27, 2013

In your pom.xml fragment scala-maven-plugin seems to be define under the , in this case the plugin will not run except if you call it explicitly from command line or also under .

So can you provide the FULL pom.xml and the FULL output of 'mvn install -e' (send me a private email if you like) ?

Internaly of the plugin management of src/main and src/test are simular, so if the issue come from scala-maven-plugin it should failed before (IMHO). May be the issue comme from an other plugin like the specs2 one (you can try to comment it).

@slandelle
Copy link
Collaborator

Very old issue, not enough information from the user and links are now broken.
Closing for now.
Feel free to provide more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants