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.
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.
> >
> > - 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?
> >
> > - We need to do a multi-platform build, this is now possible by
running
> > the build 4 times with different osgi.* arguments, which takes a
long
> > time). It would be nice if this could be done by configuration of
the
> > maven-osgi-packaging-plugin.
>
> Is it the same problem you reported in MNGECLIPSE-941? If this is a
> different problem, can you please open new JIRA and provide sample
> project and expected output.
No, it is not the same problem. Multi-platform build will package a
product for each platform (and ideally zip them). I will create a sample
product and a new jira for this.
>
> Also, it'd be interesting to know how (or if) PDE/Build works for
> multiple target platforms.
In the pde build, you specify the platforms to build for in a property
in the ant build file, look in the eclipse help for "Building an RCP
application from a product configuration file". The property "configs"
can contain all platforms you want to build for and the output is the
zipped contents of the eclipse product export wizzard for multi
platform.
The property "configs" is defined in the
Eclipse3.4\plugins\org.eclipse.pde.build_3.4.0.v20080604\templates\headl
ess-build\build.properties:
# The list of {os, ws, arch} configurations to build. This
# value is a '&' separated list of ',' separate triples. For example,
# configs=win32,win32,x86 & linux,motif,x86
# By default the value is *,*,*
configs = *, *, *
#configs=win32, win32, x86 & \
# linux, gtk, ppc &\
# linux, gtk, x86 & \
# linux, gtk, x86_64 & \
# linux, motif, x86 & \
# solaris, motif, sparc & \
# solaris, gtk, sparc & \
# aix, motif, ppc & \
# hpux, motif, PA_RISC & \
# macosx, carbon, ppc
>
> >
> > - We do have a product configuration that includes splash, about and
> > other branding information. On these properties, the logging
responds
> > with the following warnings:
> >
> > [WARNING] Tycho doesn't handle 'aboutInfo' property.
> > [WARNING] Tycho doesn't handle 'windowImages' property.
> > [WARNING] Tycho doesn't handle 'splash' property.
> > [WARNING] Tycho doesn't handle 'vm' property.
>
> Can you please open JIRA enhancement request for this? Provide sample
> project if you have one handy, but we should be able to figure out
> details from the docs.
ok.
>
> This brings up another question. Are you using P2 repository support
> prototype included in the current DEV build? New target platform
> management code is quite different and only supports local eclipse
> installations and maven repositories at the moment. I was planning to
> defer P2 support for later builds and wonder if this is going to be a
> deal breaker.
No, we are still using the old update mechanism, so no problem there for
now.
Thanks for all the help,
Ida
This e-mail message contains information which is confidential and may be
privileged. It is intended for use by the addressee only. If you are not the
intended addressee, we request that you notify the sender immediately and
delete or destroy this e-mail message and any attachment(s), without copying,
saving, forwarding, disclosing or using its contents in any other way. TomTom
N.V., TomTom International BV or any other company belonging to the TomTom
group of companies will not be liable for damage relating to the communication
by e-mail of data, documents or any other information.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
