2

I recently asked about a maven like tool for other languages but there hasn't been any responses (except for a few upvotes :). Given that, I've decided that maybe using Maven is good, but I'd have to write my own plugins to do simple things

This gives rise to a number of issues, and I'd like to hear about solutions that people are using in their daily process:

  • running other build/release systems and mostly use Maven for packaging/dependency management? (msbuild, vcbuild, cmake, setuptools)
  • working directly with other languages:
    • The native-archive-plugin supports C/C++, but does it integrate with visual studio?
    • Are there other plugins for more langugages, that I've missed?
  • how hard is it to write your own plugin for this?

Question:

What is your recommended approach for managing non-Java languages and artefacts with Maven?

Cœur
  • 37,241
  • 25
  • 195
  • 267
Macke
  • 24,812
  • 7
  • 82
  • 118

1 Answers1

1

I'm currenctly using maven-scala-plugin and it work just great. I only put my sources to src/main/scala instead of java and bind scala:compile goal to compile phase and that's it. But scala is very close to java, so the issues with c++ might arise.

ryskajakub
  • 6,351
  • 8
  • 45
  • 75
  • Scala is not only close to Java, it runs on the same infrastructure (the JVM), so it's mostly "just another Java". Jython and Groovy would be similar it that sense. Nevertheless, I'll take a look at the plugin. Thanks! – Macke Dec 10 '10 at 08:10