[ 
https://jira.codehaus.org/browse/MNBMODULE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291795#comment-291795
 ] 

Frantisek Mantlik commented on MNBMODULE-161:
---------------------------------------------

It should not be necessary to replace the whole harness, I guess. You can 
replace template.xml with the use of templateFile parameter and provide any 
changes/replacements etc. you need in your template.xml. In addition, you can 
pass parameters to the template.xml defined in userSettings map.

A simple example of the above features for simple installer branding can be 
found in [MNBMODULE-161], but I can imagine nearly any intervention to the 
standard NBI this way including replacement of the whole nbi code if needed.

                
> Allow custom harness in build-installers goal
> ---------------------------------------------
>
>                 Key: MNBMODULE-161
>                 URL: https://jira.codehaus.org/browse/MNBMODULE-161
>             Project: Maven NetBeans Module Plugin
>          Issue Type: Wish
>    Affects Versions: 3.7
>            Reporter: Joe Rice
>            Assignee: Jesse Glick
>
> It would be nice to be able to override the harness included in 
> nbm-maven-harness with one customized for a particular project.  Right now 
> this is the easiest (though still pretty crude) way to do finer grained 
> customization of the created installer.
> For my build I added a <harnessLocation> parameter and changed the 
> build-installer target code as follows:
> // Copy Netbeans Installer resources
>         FileUrlUtils fu = new FileUrlUtils();
>         File harnessDir = new File( outputDirectory, "installer" );
>         
>         getLog().debug("Harness Location: " + harnessLocation);
>         if (harnessLocation == null) {            
>             fu.copyResourcesRecursively( 
> getClass().getClassLoader().getResource( "harness" ), harnessDir );
>         }
>         else if (harnessLocation.exists()) {
>             getLog().debug( "Copying harness directory");
>             try {
>                 FileUtils.copyDirectoryStructure(harnessLocation, harnessDir);
>             }
>             catch (IOException e) {
>                 throw new MojoExecutionException("Exception copying harness 
> directory: " + harnessLocation.getAbsolutePath(), e);
>             }
>             getLog().debug( "Finished copying harness directory");
>             
>         }
>         else {
>             throw new MojoExecutionException("The specified harness location 
> does not exist: " + harnessLocation.getAbsolutePath());
>         }

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


Reply via email to