J�rg Schaible wrote:
Hi Dalibor,
Well, but even for this purpose a system like Maven (or Maven-wagon) does meet the need of Java developers and users. See, I fully understand your point (writing Gentoo ebuilds for Java apps myself), but this is not a specific problem with Maven or its technology. We also have Avalon-Merlin around (a kind of Enterprise Application Framework) already using the same idea with compatible repo to Maven (although not sharing it for some reason). We have Eclipse downloading plugins and their updates on the fly and the new 3.0M6 uses for this functionality an OSCI-based platform. Meanwhile I have seen other people stating to use this technology for their own applications too. So, it seems this automated mangement and distributions of applications has a lot of interest within the (Java) community and solves a basic problem and will be eventually become commodity. I bet, that you'll not able to change this movement.
I'm neither trying nor would I want to change a movement. I've stated in a couple of posts in this thread that I can imagine contexts in which using Maven for software distribution is adequate. I'm arguing it's not an all-encompasing solution it;s made out to be, though.
I'm trying to find ways to produce a best-of-both-worlds approach for Linux alone, as that's what I'm working with. In order to be able to do that, I'm asking questions and the answers I've been getting seem to indicate that everyone could profit from a little more education on the issues involved. I'm educating people on the portability of Java code, they are educating me on Maven's internals, and I appreciate the discussion very much.
So you better hope that there will be not more of this kind of technology developed and something like Maven-wagon gets standard. At least for Maven you are able to set the repository to a local directory, that you can stuff with symlinks to the native libs at various locations. I don't see any other working solution. Maybe you can enhance the download technology with a platform-specific mechanism, that will automatically use the native build system, but that's clearly out of the focus of this community as Jason already stated.
Java WebStart is already 'standard', i.e. included with Sun's JDK. I'm still waiting for the flood of WebStart enabled applications, though ;)
Maven is a nice build tool, and all that. As Jason said, he doesn't want to care about platform specific aspects. That's fine. Other people do, though, in order to deliver audited, tested and integrated applications on those platforms. I'd like to figure out a way to make their job easier. That's all.
cheers, dalibor topic
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
