NMaven still supports whatever sourceDirectory you define for it. The issue is what format we will use for the trunk and given that most people will probably be using VS studio (and possibly the Maven addin), the VS defaults make sense. This would not preclude you from using some other structure for your project. Or am I missing something in your requirements? An additional VS addin could also be created specifically for web projects, if needed. Shane
On Wed, Oct 1, 2008 at 9:52 PM, Leopoldo Agdeppa <[EMAIL PROTECTED]> wrote: > Hello > > The problem when having a target in side the web application is that it is > compiled by aspnet_compiler, a simple solution for this is, aspmojo should > delete the target folder before calling aspnet_compiler, > then aspnet_compiler's targetdirectory should be pointed to a temporary > path, then after the execution > the temporary path is then copied in the target folder, > > in this way we can support what is Visual Studio's Default way and still > have the maven-style. > and not forcing users who may have already a very large project to do some > major refactor on there part. > which might cause bad side effects. > > remember Visual studio web projects doesn't have a project file like > (*.csproj/*.vbproj), its dll dependencies are stored in Bin/ directory > and each *.dll has a *.dll.refresh which stores the relative path of the > dependency dll, this means that changing a folder > for the web project could make the relative paths of the *.dll.refresh file > unreachable. > > thanks > bong > > On Wed, Oct 1, 2008 at 4:08 PM, Leopoldo Agdeppa <[EMAIL PROTECTED]> > wrote: > > > +1 with VS defaults > > > > > > On Wed, Oct 1, 2008 at 11:10 AM, Shane Isbell <[EMAIL PROTECTED] > >wrote: > > > >> On Tue, Sep 30, 2008 at 7:59 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > >> > > >> > > >> > What is the convention on trunk exactly? Does it want a directory for > >> > the source code, or is it fine if source is in the same directory as > >> > the pom and .csproj file (the VS default)? > >> > >> I think we should go with VS defaults. After the VS addin, I changed my > >> mind > >> about trying to support two different directory structures for VS, the > >> Maven > >> structure being an unnatural fit. So there may be some archetypes and > ITs > >> of > >> each structure as this transition was going on. > >> > >> Shane > >> > > > > > > > > -- > > Leopoldo L. Agdeppa III > > Software Engineer | Exist Global | +6332 4121155 xtn 103. +639195686024 | > > YM: exst_lagdeppa | www.exist.com | Innovation Delivered > > > > > > -- > Leopoldo L. Agdeppa III > Software Engineer | Exist Global | +6332 4121155 xtn 103. +639195686024 | > YM: exst_lagdeppa | www.exist.com | Innovation Delivered >
