Use case: As it allows any url I can just have links to build files via file: protocol and then when I want to update a file I just do a "touch".Plus, imagine the "power" of installing pax urls together with file install. I can have .lnk file doing war transformation, automatic wrapping, mvn references. And the change is so trivial and small... ;)
On Wed, Jun 24, 2009 at 8:30 PM, Filippo Diotalevi < [email protected]> wrote: > On Wed, Jun 24, 2009 at 5:39 PM, Alin Dreghiciu<[email protected]> > wrote: > > Well, we are talking about pretty much a small change as it only adds the > > code to read the content of the link file and instead of a file input > stream > > it uses url.openStream. So, it does not introduce any new dependency and > the > > changes are relative small in > > size. I can out up a patch quickly. It may look like a lot of changes > > but is just moving code around. > > I see. Having used Pax-Url I thought you wanted to add support for > custom protocol like mvn: or wrap:, which would require additional > code or dependencies. > > Anyway, what would be the expected use case for .lnk files? > I mean, fileinstall usually update a bundle/file when it finds a new > version of it in the watched directory. What do you expect with .lnk > files? > In other words, is the (linked) bundle updated when > a) the .lnk file is modified > b) when the resource pointed by the .lnk file is modified > ? > -- > Filippo Diotalevi > -- Alin Dreghiciu Software Developer - Looking for new projects! My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.blogspot.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development.
