[
http://jira.codehaus.org/browse/MNBMODULE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint updated MNBMODULE-72:
----------------------------------
Fix Version/s: 3.2
http://fisheye.codehaus.org/changelog/mojo/?cs=11498 should be a good start.
Still need to do the same in CreateClusterMojo.
It's not that easy, the hard part is figuring what jar within the nbm is the
module jar. Additionally the whole process is suboptimal. We need to create the
update tracking file twice. Once before generating the nbm and then again when
assembling the complete application. I'm wondering if we could somehow drop the
tracking file into the nbm file and reuse it later.
Another optimization is to calculate the crc of the nbm content while copying
it, not afterwards.
The AutoUpdate class is not public, just package private.
> missing update-tracking files in the created nbm-application
> ------------------------------------------------------------
>
> Key: MNBMODULE-72
> URL: http://jira.codehaus.org/browse/MNBMODULE-72
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Bug
> Affects Versions: 3.1
> Reporter: Milos Kleint
> Assignee: Milos Kleint
> Fix For: 3.2
>
>
> jglick suggests to add this update tracking file as they are important for
> updates. They are supposed to be reconstructable from the nbm content.
--
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
