The sticky wicket of .NET Framework and native builds I just talked someone in GB out of using .NET Framework and GAC for the reason when you load an assembly into GAC you will have to hook that assembly to a native binary There are so many variations of native builds for each OS and with .NET you would need to permutate that array with every conceivable .NET assembly version(e.g. 1.x,2.x,3x)
the plugin that would manage this NativeBuild-DotNetFramework matrix (maven-nar-plugin) would be stressed to the limit finally who would store all these binaries (and assemblies) thoughts? Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > From: mar...@headcrashing.eu > To: users@maven.apache.org > Subject: RE: Maven for Software Installation > Date: Fri, 22 Jun 2012 22:40:53 +0200 > > Ideally for this, Maven (and such, the JVM) would be contained as an itegral > part of the popular operating systems like Windows, MacOS and Linux. What a > perfect world. ;-) > > > -----Original Message----- > > From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] > > Sent: Donnerstag, 21. Juni 2012 21:54 > > To: Maven Users List > > Subject: Maven for Software Installation > > > > I have brought this notion up before, but I have been thinking about it > > a bit more. > > > > Would it make sense to use Maven technology for software deployment and > > installation as opposed to just builds? > > > > What I envision is something akin to the Global Assembly Cache in .NET, > > but for Maven artifacts. In particular, the local repository would act > > like a GAC, but you might want to separate a system local repository > > from the user local repositories. > > > > The basic idea is that when deploying/installing software you would not > > bundle all your dependent artifact into your installer, rather you > > would just bundle their coordinates. At installation time you would > > install the Maven Installer if it was not already there, then your > > installer would work in conjunction with the Maven Installer. Basically > > the Maven Installer subsystem would simply download the dependent > > artifacts from Maven Central or elsewhere, and put them in the System > > Repository (similar to the GAC). > > > > One benefit of this is that if you have a lot of software that all > > reference the same artifacts, they can share copies. Other benefits > > would be similar to those for the .NET GAC, although hopefully we could > > avoid some of the problems the GAC has created. > > > > Another benefit is that installers could be smaller by not bundling in > > dependent artifacts. Installation could be faster in that if dependent > > artifacts are already in the System Repository downloading and > > installing them is unnecessary. > > > > So am I just thinking crazy, or is there any potential benefit to this > > idea? > > > > Cheers, Eric > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
