| 'Cloud' PDE style on our product in 3.5RC2 [message #63597] |
Thu, 28 May 2009 19:10  |
 michael.sacarny
Messages: 103
Registered: July 2009
Location: USA |
Senior Member |
|
|
I am trying to apply the 'Cloud' PDE approach demonstrated here by Niefer:
http://aniefer.blogspot.com/2009/03/building-p2-rcp-products -in-eclipse.html
to our RCP Product on SDK 3.5RC2.
* Our Product is Feature-based.
* I've removed all our plugins from the feature save our branding plugin.
* I use Niefers build.properties and buildProduct.xml.
* The Product Dependencies are as follows:
[our feature]
org.eclipse.rcp
org.eclipse.equinox.p2.user.ui
org.eclipse.platform
org.eclipse.cdt.platform
org.eclipse.cvs
org.eclipse.help
org.eclipse.equinox.executable
* I've stripped out all Start level items and VM arguments from the
Product Configuration panels.
The console shows the following runDirector error during build:
runDirector:
[echo] !SESSION 2009-05-28 14:08:29.161
-----------------------------------------------
[echo] eclipse.buildId=I20090522-1710
[echo] java.version=1.6.0_07
[echo] java.vendor=Sun Microsystems Inc.
[echo] BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
[echo] Framework arguments: -application
org.eclipse.equinox.p2.director.app.application --launcher.suppressErrors
-flavor ${p2.flavor} -installIU com.analog.visualdsp.product -version
1.0.0.200905281407 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
-profile profile -profileProperties
org.eclipse.update.install.features=true -metadataRepository
file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
-artifactRepository
file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
-destination
C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
-bundlepool
C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
[echo] Command-line arguments: -application
org.eclipse.equinox.p2.director.app.application --launcher.suppressErrors
-consoleLog -flavor ${p2.flavor} -installIU com.analog.visualdsp.product
-version 1.0.0.200905281407 -p2.os win32 -p2.ws win32 -p2.arch x86
-roaming -profile profile -profileProperties
org.eclipse.update.install.features=true -metadataRepository
file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
-artifactRepository
file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
-destination
C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
-bundlepool
C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
[echo]
[echo] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0
2009-05-28 14:08:51.464
[echo] !MESSAGE The installable unit
org.eclipse.ui.win32.translated_host_properties is missing the filename
property.
[echo] This application is deprecated. Please use the
org.eclipse.equinox.p2.director application.
[echo] Installing com.analog.visualdsp.product 1.0.0.200905281407.
[echo] Operation completed in 31293 ms.
1) The runDirector error "missing filename property" looks like Bugzilla
275274. Is it harmless? Workaround?
2) The product contains the expected files [our product].exe and [our
product].ini, but also an extra file 'launcher.exe'. How do we avoid that?
3) Help, About, Installation, Features, shows two entries for each
Feature. This seems like Bugzilla 275523. Harmless? Workaround?
Thanks for any insight into these issues,
MSacarny
|
|
|
| Re: 'Cloud' PDE style on our product in 3.5RC2 [message #63824 is a reply to message #63597] |
Mon, 01 June 2009 19:18  |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
> 2) The product contains the expected files [our product].exe and [our
> product].ini, but also an extra file 'launcher.exe'. How do we avoid
that?
launcher.exe is coming from org.eclipse.equinox.executable, you don't
need to add this to your .product file. This feature contains unbranded
executables, due to a change in how rootfiles from features are
contributed to product, you shouldn't include this feature directly.
PDE/Build will automatically brand the executables for your product and
include them for you, which is how you got the product.exe.
I'm not sure about (1) and (3).
-Andrew
MSacarny wrote:
> I am trying to apply the 'Cloud' PDE approach demonstrated here by Niefer:
> http://aniefer.blogspot.com/2009/03/building-p2-rcp-products -in-eclipse.html
> to our RCP Product on SDK 3.5RC2.
> * Our Product is Feature-based. * I've removed all our plugins from the
> feature save our branding plugin.
> * I use Niefers build.properties and buildProduct.xml. * The Product
> Dependencies are as follows:
> [our feature]
> org.eclipse.rcp
> org.eclipse.equinox.p2.user.ui
> org.eclipse.platform
> org.eclipse.cdt.platform
> org.eclipse.cvs
> org.eclipse.help
> org.eclipse.equinox.executable
> * I've stripped out all Start level items and VM arguments from the
> Product Configuration panels.
>
> The console shows the following runDirector error during build:
>
> runDirector:
> [echo] !SESSION 2009-05-28 14:08:29.161
> -----------------------------------------------
> [echo] eclipse.buildId=I20090522-1710
> [echo] java.version=1.6.0_07
> [echo] java.vendor=Sun Microsystems Inc.
> [echo] BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> [echo] Framework arguments: -application
> org.eclipse.equinox.p2.director.app.application
> --launcher.suppressErrors -flavor ${p2.flavor} -installIU
> com.analog.visualdsp.product -version 1.0.0.200905281407 -p2.os win32
> -p2.ws win32 -p2.arch x86 -roaming -profile profile -profileProperties
> org.eclipse.update.install.features=true -metadataRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -artifactRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -destination
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
> -bundlepool
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
>
> [echo] Command-line arguments: -application
> org.eclipse.equinox.p2.director.app.application
> --launcher.suppressErrors -consoleLog -flavor ${p2.flavor} -installIU
> com.analog.visualdsp.product -version 1.0.0.200905281407 -p2.os win32
> -p2.ws win32 -p2.arch x86 -roaming -profile profile -profileProperties
> org.eclipse.update.install.features=true -metadataRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -artifactRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -destination
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
> -bundlepool
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
>
> [echo] [echo] !ENTRY
> org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-28 14:08:51.464
> [echo] !MESSAGE The installable unit
> org.eclipse.ui.win32.translated_host_properties is missing the filename
> property.
> [echo] This application is deprecated. Please use the
> org.eclipse.equinox.p2.director application.
> [echo] Installing com.analog.visualdsp.product 1.0.0.200905281407.
> [echo] Operation completed in 31293 ms.
>
> 1) The runDirector error "missing filename property" looks like Bugzilla
> 275274. Is it harmless? Workaround?
> 2) The product contains the expected files [our product].exe and [our
> product].ini, but also an extra file 'launcher.exe'. How do we avoid that?
> 3) Help, About, Installation, Features, shows two entries for each
> Feature. This seems like Bugzilla 275523. Harmless? Workaround?
>
> Thanks for any insight into these issues,
> MSacarny
>
|
|
|
| Re: 'Cloud' PDE style on our product in 3.5RC2 [message #598019 is a reply to message #63597] |
Mon, 01 June 2009 19:18 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
> 2) The product contains the expected files [our product].exe and [our
> product].ini, but also an extra file 'launcher.exe'. How do we avoid
that?
launcher.exe is coming from org.eclipse.equinox.executable, you don't
need to add this to your .product file. This feature contains unbranded
executables, due to a change in how rootfiles from features are
contributed to product, you shouldn't include this feature directly.
PDE/Build will automatically brand the executables for your product and
include them for you, which is how you got the product.exe.
I'm not sure about (1) and (3).
-Andrew
MSacarny wrote:
> I am trying to apply the 'Cloud' PDE approach demonstrated here by Niefer:
> http://aniefer.blogspot.com/2009/03/building-p2-rcp-products -in-eclipse.html
> to our RCP Product on SDK 3.5RC2.
> * Our Product is Feature-based. * I've removed all our plugins from the
> feature save our branding plugin.
> * I use Niefers build.properties and buildProduct.xml. * The Product
> Dependencies are as follows:
> [our feature]
> org.eclipse.rcp
> org.eclipse.equinox.p2.user.ui
> org.eclipse.platform
> org.eclipse.cdt.platform
> org.eclipse.cvs
> org.eclipse.help
> org.eclipse.equinox.executable
> * I've stripped out all Start level items and VM arguments from the
> Product Configuration panels.
>
> The console shows the following runDirector error during build:
>
> runDirector:
> [echo] !SESSION 2009-05-28 14:08:29.161
> -----------------------------------------------
> [echo] eclipse.buildId=I20090522-1710
> [echo] java.version=1.6.0_07
> [echo] java.vendor=Sun Microsystems Inc.
> [echo] BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> [echo] Framework arguments: -application
> org.eclipse.equinox.p2.director.app.application
> --launcher.suppressErrors -flavor ${p2.flavor} -installIU
> com.analog.visualdsp.product -version 1.0.0.200905281407 -p2.os win32
> -p2.ws win32 -p2.arch x86 -roaming -profile profile -profileProperties
> org.eclipse.update.install.features=true -metadataRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -artifactRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -destination
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
> -bundlepool
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
>
> [echo] Command-line arguments: -application
> org.eclipse.equinox.p2.director.app.application
> --launcher.suppressErrors -consoleLog -flavor ${p2.flavor} -installIU
> com.analog.visualdsp.product -version 1.0.0.200905281407 -p2.os win32
> -p2.ws win32 -p2.arch x86 -roaming -profile profile -profileProperties
> org.eclipse.update.install.features=true -metadataRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -artifactRepository
> file:C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/bu ildDirectory/buildRepo
> -destination
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
> -bundlepool
> C:\eclipse\VisualDSP_3.5_3_feature\workspace\builder/buildDi rectory/tmp/eclipse
>
> [echo] [echo] !ENTRY
> org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-28 14:08:51.464
> [echo] !MESSAGE The installable unit
> org.eclipse.ui.win32.translated_host_properties is missing the filename
> property.
> [echo] This application is deprecated. Please use the
> org.eclipse.equinox.p2.director application.
> [echo] Installing com.analog.visualdsp.product 1.0.0.200905281407.
> [echo] Operation completed in 31293 ms.
>
> 1) The runDirector error "missing filename property" looks like Bugzilla
> 275274. Is it harmless? Workaround?
> 2) The product contains the expected files [our product].exe and [our
> product].ini, but also an extra file 'launcher.exe'. How do we avoid that?
> 3) Help, About, Installation, Features, shows two entries for each
> Feature. This seems like Bugzilla 275523. Harmless? Workaround?
>
> Thanks for any insight into these issues,
> MSacarny
>
|
|
|
Powered by
FUDForum. Page generated in 0.02604 seconds
] 
Search
Help
Register
Login
Home
