On Wed, May 28, 2008 at 8:48 AM, Shane Isbell <[EMAIL PROTECTED]> wrote:
>> We need to be able to use the 'Add Maven Artifact' feature of the VS >> Addin, and see the framework dlls so they can be added to the project. >> Currently it looks like it's only going to display things from the >> local and remote repositories. > > 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'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. With Java, you don't have to add pom dependencies for things like java.util.LinkedHashSet, just an import statement. How does that compare to .NET? Is everything in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory supposed to automatically be available when compiling with 'mvn install'? How about when compiling within VS? Thanks, -- Wendy
