On Sep 1, 2009, at 4:42 AM, Adam Lally wrote:
On Sat, Aug 29, 2009 at 1:00 PM, Jörn Kottmannkottm...@gmail.com
wrote:
On Aug 28, 2009, at 3:14 PM, Marshall Schor wrote:
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
Hi,
On Fri, Aug 28, 2009 at 3:14 PM, Marshall Schorm...@schor.com wrote:
Should we adopt this approach?
+1 Source jars in the Maven repository are very convenient.
This practice is quickly becoming more common within Apache. See the
latest org.apache:apache parent POM [1] that by default
Adam Lally wrote:
On Sat, Aug 29, 2009 at 1:00 PM, Jörn Kottmannkottm...@gmail.com wrote:
On Aug 28, 2009, at 3:14 PM, Marshall Schor wrote:
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
On Sat, Aug 29, 2009 at 1:00 PM, Jörn Kottmannkottm...@gmail.com wrote:
On Aug 28, 2009, at 3:14 PM, Marshall Schor wrote:
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
On Aug 28, 2009, at 3:14 PM, Marshall Schor wrote:
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
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
Marshall Schor wrote:
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
