Re: source files packaging
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 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. +1 Yes I would really appreciate having the source code in eclipse linked to the uiima jars automatically with mvn eclipse:eclipse. I'm not sure I completely understand - does this mean our binary distributions contain source, or not? If so, I am uneasy about that. We had this discussion prior to the last release without a real consensus being reached: http://markmail.org/thread/oqredcsn3camvyy7. To have source code linked in eclipse a binary (the one we have now) and separate source jars must be published via maven. Jörn
Re: source files packaging
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 attaches source and javadoc jars to a release build. [1] http://repo2.maven.org/maven2/org/apache/apache/6/apache-6.pom BR, Jukka Zitting
Re: source files packaging
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 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. +1 Yes I would really appreciate having the source code in eclipse linked to the uiima jars automatically with mvn eclipse:eclipse. I'm not sure I completely understand - does this mean our binary distributions contain source, or not? If so, I am uneasy about that. We had this discussion prior to the last release without a real consensus being reached: http://markmail.org/thread/oqredcsn3camvyy7. No, the binary assemblies produced by our builds would not have the sources. What would change is that the maven artificat distribution servers would have, in addition to our Jars, the Sources that go with those Jars. We still have the approach for people not using Maven, of having separate sources, which can be downloaded (or not), and if downloaded, can be added to the Jars directly. -Marshall -Adam
Re: source files packaging
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 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. +1 Yes I would really appreciate having the source code in eclipse linked to the uiima jars automatically with mvn eclipse:eclipse. I'm not sure I completely understand - does this mean our binary distributions contain source, or not? If so, I am uneasy about that. We had this discussion prior to the last release without a real consensus being reached: http://markmail.org/thread/oqredcsn3camvyy7. -Adam
Re: source files packaging
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 than get maven warning messages that no sources were found, and the m2eclipse plugin would easily be able to get the sources. +1 Yes I would really appreciate having the source code in eclipse linked to the uiima jars automatically with mvn eclipse:eclipse. Jörn
source files packaging
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
Re: source files packaging
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 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 +1 We must still ship a source distribution as it is considered the primary distribution by Apache. Everything else is convenience. --Thilo
