[
https://issues.apache.org/jira/browse/NPANDAY-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042367#comment-13042367
]
Spencer Van Hoose commented on NPANDAY-439:
-------------------------------------------
A good workaround, as Wendy suggested, is to change the preparationGoals for
the release plugin to "clean install". I accomplished that with:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<preparationGoals>clean install</preparationGoals>
</configuration>
</plugin>
{code}
> Unable to release multi-module project with library
> ---------------------------------------------------
>
> Key: NPANDAY-439
> URL: https://issues.apache.org/jira/browse/NPANDAY-439
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.4-incubating
> Environment: Windows 7 x64
> Maven 2.2.1
> Reporter: Spencer Van Hoose
>
> I have a multi-module C# project containing 1 library project and 2 winexe
> projects. Both of the winexe projects depend on the library.
> Building these project works correctly but I cannot run a release:prepare
> because it attempts to copy the release version of the dll from my repository
> where it doesn't exist yet.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
