Hello Jakub, [EMAIL PROTECTED] wrote: > On 4/25/07, Ryan Lee <[EMAIL PROTECTED]> wrote: >> Why is it that Longwell 2.4.2 doesn't build for you? > > Longwell 2.4.2 build stops with the following message (it is not a proxy > problem): > > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] The plugin 'org.apache.maven.plugins:maven-source-plugin' does not > exist or no valid version could be found
Odd. Perhaps this thread might be of some use (unlikely since the error doesn't appear to affect Longwell 2.4): http://www.mail-archive.com/[EMAIL PROTECTED]/msg66536.html >> I am curious about your use of Longwell that requires frequent updates >> to existing data. > > I thought about using Longwell to browse a bunch of projects described in > DOAP files. The files won't change that frequently I guess but still, it > would be nicer to avoid having to stop longwell and create a new repository > each time some of the files changes (or each cycle in which I would check > for changes). There was a proposal on the list some time ago to use Sesame contexts and switch out an old context for an updated one while keeping Longwell running. I don't know what happened with that idea. I should note that using two different applications to work with the raw files of a triple store simultaneously seems iffy (I'd take down Longwell before running a separate update)... >> I wouldn't recommend it, per se. There are layers in Longwell on top of >> Sesame that may (or may not, I don't recall specifics for the 2.4.2 >> release at the moment) get out of sync with the triple store if you >> modify it at that lower level. > > Ok, I'll try and see I guess :) ...but I don't suppose that will stop you ;) -- Ryan Lee [EMAIL PROTECTED] MIT CSAIL Research Staff http://simile.mit.edu/ http://people.csail.mit.edu/ryanlee/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
