The ArtifactContext constructs the dependency list. To support multiple dependency types within the pom is a simple matter of having the ArtifactContext filter out non-java dependencies for jars and filter out non-.NET dependencies for a .NET build. These technical issues can be addressed. The question is: does anyone have a need for it?
Shane On 8/3/07, Evan Worley <[EMAIL PROTECTED]> wrote: > > The biggest drawback to using one pom is the fact that parent poms can no > longer have dependency declarations for their child poms. Some users > might > also want independent control of deployment repos and version management. > > Thoughts? > > On 8/3/07, Shane Isbell <[EMAIL PROTECTED]> wrote: > > > > Coming back to the problem that Brian raised some time ago concerning > > having > > dual poms for dotnet and java: I can easily add in a java compiler that > > uses > > the CompilerContext within NMaven. This would a single build (and pom) > for > > both Java and .NET. It would also allow Java builds to leverage the > > profile > > and capability matching within NMaven, allowing things like MIDP, CDC > > build > > support. Is there any interest from the community in this support? > > > > Shane > > >
