incubator-nmaven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leopoldo Agdeppa III (JIRA)" <>
Subject [jira] Created: (NMAVEN-157) Can't add a dependency w/Add NMaven Artifact
Date Wed, 02 Jul 2008 07:49:26 GMT
Can't add a dependency w/Add NMaven Artifact

                 Key: NMAVEN-157
             Project: NMaven
          Issue Type: Bug
            Reporter: Leopoldo Agdeppa III
         Attachments: Fix.patch

Directory structure for this project is

|                  |------------ Logging.vbproj
|                                    {Source Files}
                                    {Unit Test Files}

>From a discussion, I thought I understood that .NET unit tests are placed in a separate

If that is the case, shouldn't there be pom.xml files in the "Logging" and "Logging.Tests"

I'm also unable to use Add Maven Artifact on a normal multi-module project, so I'm changing
the summary on this issue to be more generic.

To reproduce:
1. Check out the MyVBSolution example project
2. Import the project to generate poms
3. right-click on MyVBProject -> Add Maven Artifact
4. Switch to the Remote tab
5. Navigate to a .dll file and click Add

It should both add the dependency to the pom and add a reference in the solution.

Instead, I get a dialog: Could not add reference. Missing pom file: File = c:\svn\aedc-build-pilot\pom.xml

The pom it should be adding to is the one for the project I right-clicked on, which is located

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message