I admit to limited practical understanding of this, but it raises a
couple of other concerns (if they are applicable):
- won't this require system admin privileges?
- isn't it possible some people won't want their gac touched?
- can this impact other applications on the system?
Cheers,
Brett
On 22/06/2007, at 2:10 PM, Shane Isbell wrote:
Currently, we have dual support for both GAC and maven repo
installation.
This is to experiment with just using the GAC. There are some
potential
benefits, including: 1) not needing to copy dependent assemblies into
executable addin and netplugin directories (within the repo); 2)
not needing
to copy dependent assemblies into the target directory for unit
testing; 3)
simpilfication and readability of code. The current way (1) is
handled does
not allow the application to use two different versions of the same
assembly
during execution. This may be required for assemblies with strong
names.
Shane
On 6/21/07, Evan Worley <[EMAIL PROTECTED]> wrote:
Brett,
I believe the GAC does allow multiple versions of the same artifact,
http://en.wikipedia.org/wiki/Global_Assembly_Cache#Side-by-
side_versioning
-Evan
On 6/21/07, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> In addition to, or instead of?
>
> Sounds like a contradiction with Maven philosophy of being able to
> use different versions for different applications (IIUC, the GAC
> doesn't permit duplicates of an artifact with different versions).
>
> - Brett
>
> On 21/06/2007, at 3:55 PM, [EMAIL PROTECTED] wrote:
>
> > Author: sisbell
> > Date: Wed Jun 20 22:55:03 2007
> > New Revision: 549393
> >
> > URL: http://svn.apache.org/viewvc?view=rev&rev=549393
> > Log:
> > Copy of trunk. Branch deals with experimental work with using the
> > GAC instead of the maven repo for storing artifacts.
> >
> > Added:
> > incubator/nmaven/branches/SI_GAC/
> > - copied from r549392, incubator/nmaven/trunk/
>
