Our main approach to packaging source files is to use Maven's assembly plugin.
The Lucas project includes in its build section of its POM the maven-source-plugin execution. This results in generating 2 additional Jars - for the sources and the test-sources, and "attaching" them to the generated artifact. We could do this for all of our Jars, and I'm thinking this would be a good idea. One reason would be it would align us slightly better with the "maven way" of doing things. When users download jars from maven they would find the sources rather than get maven warning messages that no sources were found, and the m2eclipse plugin would easily be able to get the sources. If we did this, I think we would still ship the sources distribution, but building it might be easier. Should we adopt this approach? -Marshall
