Okay thanks. I think moving the pom generator for 0.14 to trunk will the easiest place to start with getting VS support back in.
Shane On Wed, Apr 16, 2008 at 1:32 AM, Jan Ancajas <[EMAIL PROTECTED]> wrote: > I only tried with 05 though, I'll install 08 and try to see the > difference. > > > Shane Isbell wrote: > > > Okay, let's look into what the deltas are between the project files and > > APIs > > between VS 2005 and VS 2008 and see how easy it would be to support > > both. If > > there is a lot of difference, we need initially to peg it to one > > version. I > > saw a couple of patches: NMAVEN-110 and NMAVEN-119 dealing with the pom > > generation. Maria, Jan any idea on what the difference is between the > > project file formats 05/08? > > > > Shane > > > > On Tue, Apr 15, 2008 at 9:02 AM, Dusty R. Burwell < > > [EMAIL PROTECTED]> wrote: > > > > > > > > > +1 to both 2005 & 2008 > > > > > > We're in the process of making the switch here. > > > > > > > > > -----Original Message----- > > > From: Shane Isbell [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, April 15, 2008 10:45 AM > > > To: [email protected] > > > Subject: Re: NMaven 0.14 Feedback > > > > > > Thanks Wendy. I'm going to start reviewing the patches this week. If > > > there > > > is interest in the VS studio, we should definitely look into getting > > > something into the trunk. At the Microsoft interoperability conference > > > back > > > in February, Sam said they had loosened up licensing on their package > > > integration, which allows tighter integration into VS. We considered > > > this > > > before, but couldn't pull off with the existing license. This is > > > something > > > we should be looking at as well. > > > > > > Also Microsoft has released VS 2008 so I'd like to do new work > > > targeting > > > that version. How many people on the list are using VS 2008 vs 2005? > > > > > > Thanks, > > > Shane > > > > > > On Tue, Apr 15, 2008 at 8:28 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > I've been working with 0.14 + the patches in JIRA (and possibly some > > > > patches that haven't been submitted yet). I want to hold off > > > > opening > > > > more issues until the current set gets reviewed, but here are some > > > > comments so far: > > > > > > > > * All of the right-click menu items say "Maven" except the project > > > > importer which says NMaven: Import Project. Looks like NMAVEN-119 > > > > is > > > > only for the command-line pom generator, can we get an issue open > > > > for > > > > the companion VS integration, so I have somewhere to comment? > > > > > > > > * The right-click menu lists Maven Phase -> Build, but 'build' is > > > > not > > > > a phase in the Maven lifecycle. Should it be compile? > > > > > > > > * On the "Stop Maven Build..." menu item, the ellipsis indicates > > > > that > > > > there will be another dialog, but there isn't one. > > > > > > > > * Can "Stop Maven Build" be greyed out when a build is not running? > > > > > > > > * Now that I've clicked Tools -> NMaven Build System, it disappeared > > > > from the Tools menu. How do I turn off/shut down the NMaven Build > > > > System? > > > > > > > > * The 'Output' window does not appear automatically when I click > > > > Tools > > > > -> NMaven Build System, and I think it used to. If it's not already > > > > open, there is no feedback that anything happened. > > > > > > > > * For the VS integration, the new once-off invocation of mvn (rather > > > > than the long-running Jetty process) seems to be working fine. It > > > > takes us back to Maven 2.0.x, which makes it more consistent with > > > > the > > > > Java builds. > > > > > > > > I'm looking forward to seeing the functionality from 0.14 re-appear > > > > on > > > > trunk, so we can move up soon. :) > > > > > > > > Thanks, > > > > -- > > > > Wendy > > > > > > > > > > > > > > > > > > > >
