Jeremy, for building silk we had developed a small build tool loosely resembling the DPML Magic approach. We didn't drive it as long as to create Eclipse project files though.
Since we now have PaxConstruct, I will go over it and convert it to build with Maven, which lets us reference all artifacts in OBR repos, and build the Eclipse projects etc, and run silk out of the box. Will try to get that running ASAP, maybe Niclas can chip in when he is not busy in Sweden ;) So, for now just do your own stuff, will see to getting things into a buildable state again. /peter On 5/4/07, Jeremy Volkman <[EMAIL PROTECTED]> wrote: > OPS4Jers, > > I checked out the Silk project and I'd like to mess around with it in > my Eclipse environment. I noticed that many of the modules include > "project" and "classpath" files under a src/eclipse subdirectory. Was > there some convention in place for using these files where they > reside, or were they simply reference files for developers to use in > setting up their own workspace? Currently, I've got each file > symlinked as ".project" and ".classpath" in the correct location, > however the project files reference a "SILK_ROOT" keyword (not a valid > Eclipse variable, I don't think), which obviously doesn't resolve: > e.g., > > <link> > <name>build.xml</name> > <type>1</type> > <locationURI>SILK_ROOT/core/jena/build.xml</locationURI> > </link> > > For now I'll just tailor the files to my local environment. > > Thanks, > Jeremy > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
