On Wed, May 28, 2008 at 9:31 AM, Shane Isbell <[EMAIL PROTECTED]> wrote: > On Wed, May 28, 2008 at 9:00 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>> > This is intentional because you can use the standard VS add artifacts >> form >> > for adding of references from the GAC. >> >> But then the pom does not stay in sync with the solution file. >> IM(limited)E, the only way both of them get updated is with 'Add Maven >> Artifact'. > > I checked the code. It handles removing of dependencies from the pom using > the standard VS controls; adding functionality still needs to be coded. Interesting. If you use the standard VS "Add Reference," would it be a system scoped dependency, given that you're not picking something from a Maven repository? (And how will that affect portability?) >> I'm still confused about when you *need* to add a dependency to the >> pom (and/or reference to the solution) though, which drives the "what >> things need to be in the remote repository" question. > There is a bootstrap file: > C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\csc.rsp that contains all the > included references in a standard csc/mvn compile. VS doesn't use the > csc.rsp file for its compiles and you will need to explicitly add the > references yourself. So... that sounds like it would be appropriate to add a reference in Visual Studio that does *not* need to be in the pom, because the command-line csc compiler would already know about it. Correct? Thanks for your patience. :) -- Wendy
