Ida de Groot wrote:
Hi Igor,
I'll do the comments inline too.
This is really good news, thanks. It works for me and it also seems
to
have solved MNGECLIPSE-941 (build broke on platform specific
fragments)
and MNGECLIPSE-949 (eclipse-update-site breaks on "directory based
bundle"), so I will close those issues.
I was a bit too optimistic about the MNGECLIPSE-949, directory based
bundles still breaks the update-site build. I will leave the issue in
jira and hope it gets solved.
We'll try to fix this week.
Another problem I noticed is that the "unpack" attribute for plugins in
the feature.xml does not have any effect. If the plugins that should be
unpacked (like the launcher for an rcp) are not unpacked, the
application will not work. Plugins containing (nested) jars have to be
unpacked in a product (not for an update site!). This is an attribute
for the plugin in the feature. If you have the platform specific
launcher in the feature, the checkbox for "unpack" will be checked
automatically and these plugins should be unpacked at product build.
Created MNGECLIPSE-974, we'll try to fix this week.
- The .qualifier version extension is not replaced in filenames in
the
product.
Right now .qualifier version expansion needs to be configured/enabled
explicitly, see [1] for relatively detailed explanation, but in
nutshells, you need to define buildNumber property either externally
or
using one of existing plugins.
I have the timestamp execution in my parent pom. This does work for the
update site, but not for the product build. Any other configuration
needed?
Sorry, I missed "in product" part. Created MNGECLIPSE-973, we'll try to
fix this week.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
