Daniel Kulp wrote:
On Monday 12 March 2007 10:45, Dan Diephouse wrote:
I think we should consider making some improvements to our samples.
Mainly, I would like to make them easy to use in Eclipse. It'd be great
IMO if our distribution was simultaneously an Eclipse workspace. Then
people could just do "File->Switch Workspace" in Eclipse and point it at
our distribution. Another option would be to convert our builds to Maven
so we could easily generate eclipse workspace information.
Thoughts?
Honestly, I'd like to convert them all to Maven. The main reason is that
would give us IntelliJ/IDEA support as well. (mvn idea:idea)
I think keep ANT build there will not conflict with adding Maven
support, i prefer keep ant build, i like ANT more than Maven.
There are a few issues though:
1) Building - they wouldn't build unless maven can find the jars.
Normally, we just put them in ${installdir}/lib which wouldn't work too
well. Thus, the samples wouldn't work until we deploy the release. (or
the user builds the source distribution) The OTHER option here is to
create a ${installdir}/maven_repo that is a copy of all the stuff that is
needed. The 2.2-SNAPSHOT version of assembly can create this just fine.
Of course, that would increase the size of the download. (jars in lib
and in maven_repo) I'm not sure if the assembly can grab the sources
jars as well. If so, that would be great. Then the created eclipse
projects could be fully debuggable.
2) Executing the samples: maven is very good for building them. However,
what do we do for exectuting them? Stick with ant? Shell/bat scripts?
Specific profiles in the pom configured to use the exec plugin?
