[
https://jira.codehaus.org/browse/MNBMODULE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290437#comment-290437
]
Jesse Glick commented on MNBMODULE-155:
---------------------------------------
Committed revision 15853 to add the new mojo to the platform app archetype.
Committed revision 15852 for your latest patch. I can no longer reproduce the
earlier NPE; running the goal produces a working Linux installer on my test app.
Regarding verbosity level: no specific hints for implementation, just an
observation that as a user I would expect verbosity to be controlled by the
Maven session flags, not a particular plugin's configuration.
I would like to patch {{apisupport.installer.maven}} to work with the new mojo
(once 3.7 is released) but may need some help mapping the existing
{{nb-configuration.xml}} entries produced by the "Installer" panel to new mojo
configuration in {{pom.xml}}. Most parameters seem obvious but
{{...license-type=cddl}} (or whatever plain name) does not obviously match
{{installerLicenseFile}}.
> Build installers goal
> ---------------------
>
> Key: MNBMODULE-155
> URL: https://jira.codehaus.org/browse/MNBMODULE-155
> Project: Maven NetBeans Module Plugin
> Issue Type: New Feature
> Affects Versions: 3.6
> Reporter: Frantisek Mantlik
> Assignee: Jesse Glick
> Attachments: build-installers-2.patch, build-installers-3.patch,
> build-installers.patch, nbm-installers-plugin.zip
>
>
> The proposal is to add a new goal which will provide similar functionality to
> "Build installers" action in IDE for mavenized RCP projects as a maven goal.
> I have developed a standalone plugin based on Ant-maven-plugin functionality
> which wrapped installer provided with Netbeans 6.9.1 and with minimum
> tweaking (mainly allowing some basic branding of generated installer) run an
> Ant task compiling and generating installers in the project application
> artifact. It is working for me on several mavenized RCP projects without any
> changes needed up to 7.1 RC1.
> I was trying to offer my plugin to Codehaus, but there was no interest -
> maybe because my advertisement was not good. I guess, that it should not be
> difficult to extract the goal from my plugin and integrate it to the
> nbm-maven-plugin as a new goal.
> Maybe, there would exist even easier way how to implement the same
> functionality to the nbm-maven-plugin?
> If there is interest in such a new feature, I could promise to do my best
> helping with development of the new goal. I am about to put one of my RCP
> projects to open-source domain and such a publicly available function would
> be helpful to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
