[ 
http://jira.codehaus.org/browse/MOJO-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226645#action_226645
 ] 

Marco Rocci commented on MOJO-1541:
-----------------------------------

Thanks Evgeny for the quick answer.

It's that I'm no so confident with maven and all these plugins I'm having to 
use (buildnumber, scm, exec, assembly, dependency, launch4j, etc...). And I 
suppose that internal releases defy, at least partially, the reason for having 
maven on the project. :D

This is the only plugin I'm using that has this problem. Its code doesn't seem 
to be moving much. Maybe it would be a good time to release it, at least in 
beta, like other codehaus mojos.

But ok... I'll work out the internal release, so the rest of the workgroup 
doesn't need to worry about it.

Marco

> Release NSIS Maven Plugin
> -------------------------
>
>                 Key: MOJO-1541
>                 URL: http://jira.codehaus.org/browse/MOJO-1541
>             Project: Mojo
>          Issue Type: Wish
>          Components: nsis
>            Reporter: Marco Rocci
>            Priority: Minor
>
> Having only a SNAPSHOT version of this plugin is a problem if you use the 
> maven release plugin, which requests the project does not depend on any 
> snapshot artifact.
> Would it be possible to have a release of the nsis-maven-plugin? A beta 
> release or a release candidate would do fine, I suppose.
> I think the easiest workaround for now is to release it myself to our own 
> internal nexus repository.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to