Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: 
 <6688334.1182127317498.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Sun, 17 Jun 2007 19:41:57 -0500 (CDT)
From: "Brett Porter (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Moved: (MSANDBOX-20) maven-it-plugin doesn't work with
 plugins leveraging CSharp dependencies
In-Reply-To: 
 <132188436.1150316321600.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ http://jira.codehaus.org/browse/MSANDBOX-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-2370 to MSANDBOX-20:
-------------------------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
      Component/s:     (was: Sandbox)
              Key: MSANDBOX-20  (was: MNG-2370)
          Project: Maven 2.x Sandbox  (was: Maven 2)

> maven-it-plugin doesn't work with plugins leveraging CSharp dependencies
> ------------------------------------------------------------------------
>
>                 Key: MSANDBOX-20
>                 URL: http://jira.codehaus.org/browse/MSANDBOX-20
>             Project: Maven 2.x Sandbox
>          Issue Type: Bug
>         Environment: Windows XP
>            Reporter: James Carpenter
>            Priority: Minor
>         Attachments: dotnet-dummy-plugin.zip
>
>
> The maven-it-plugin doesn't work correctly when the integration test project is a csharp build.  I'm not sure why this is the case.
> The attachment below demonstrates the problematic behavior.  As there is no release version for the csharp plugins, I have created my own in-house versions simply to keep them from unknowingly moving under my feet.  I'm strongly suspect the in-house csharp plugin versions are still identical to that in the maven plugin sandbox, but I havn't actually checked.  My in-house copies were built from maven SVN copies only a few weeks ago.  You will need to change the version numbers of the plugins in the attached example project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira