Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » p2 director issue - "binary" and "ini" are missing
p2 director issue - "binary" and "ini" are missing [message #587140] Sat, 13 December 2008 08:32
Michael Spector is currently offline Michael SpectorFriend
Messages: 110
Registered: July 2009
Senior Member

Hi All,

I think that I've created a good repository using p2 generator:

1. I've extracted non-p2 application using the following layout (I've looked
how PDE builder does this):

/tmp/App_source/
plugins/
features/
App/
App <-- executable
App.ini
configuration
....

2. My product file is looks like this:

<product name="%productName" id="com.my.app"
application="org.eclipse.ui.ide.workbench" version="1.0.0"
useFeatures="true">
<configIni use="default">
</configIni>
.... branding skipped ...
<features>
.... all features my product includes
</features>
</product>


3. Then I've run the following two commands:

~/devenv.michael/build/eclipse/eclipse -vm
/opt/jdk1.5.0_12/bin/java -application
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
-consoleLog --launcher.suppressErrors \
-source /tmp/App_source -p2.os linux -p2.ws gtk -p2.arch
x86_64 -metadataRepository file:/tmp/repo -metadataRepositoryName "My
Repository" -artifactRepository file:/tmp/repo \
-artifactRepositoryName "My
Repository" -noDefaultIUs -append -compress -publishArtifacts -publishArtifactRepository
-vmargs -Xmx256m

~/devenv.michael/build/eclipse/eclipse -vm
/opt/jdk1.5.0_12/bin/java -application
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -nosplash -debug
-consoleLog --launcher.suppressErrors \
-config /tmp/App_source/App -exe /tmp/App_source/App/App -productFile
~/devenv.michael/build/plugins/com.my.app/App.product -launcherConfig
linux_gtk_x86_64 \
-p2.os linux -p2.ws gtk -p2.arch x86_64 -metadataRepository
file:/tmp/repo -metadataRepositoryName "My Repository" -artifactRepository
file:/tmp/repo \
-artifactRepositoryName "My
Repository" -append -compress -publishArtifacts -publishArtifactRepository -vmargs
-Xmx256m

4. The repository was created successfully (no errors reported), as follows:

/tmp/repo
plugins/ <--- all my plugins including dependencies
features/ <--- all my features including dependencies
binary/
com.my.app.launcher.gtk.linux.x86_64_6.1.0 <--- Zip containing my App
executable, ini file, configuration, etc...
content.jar
artifacts.jar


Now, I'm running p2 director in order to extract my application from the
repository:

1. Run the following command:

~/devenv.michael/build/eclipse/eclipse -vm
/opt/jdk1.5.0_12/bin/java -application
org.eclipse.equinox.p2.director.app.application -nosplash --launcher.suppressErrors
-consoleLog -debug \
-metadataRepository file:/tmp/repo -artifactRepository
file:/tmp/repo -installIU com.my.app -version 1.0.0 -roaming -profile
AppProfile -profileProperties org.eclipse.update.install.features=true \
-destination /tmp/App -bundlepool /tmp/App -p2.os linux -p2.ws
gtk -p2.arch x86_64 -vmargs -Declipse.p2.data.area=/tmp/App/p2 -Xmx256m

2. The output from the command was:

Installing com.my.app 1.0.0.
Operation completed in 76519 ms.

3. When looking at the destination directory /tmp/App, I find the following:

/tmp/App/
artifacts.xml
configuration
dropins
eclipse.ini
features
p2
plugins

First of all, there's no App executable and icons. Furthermore eclipse.ini
is not named like "App.ini"

Do you see any issues in the procedure presented above?

Thanks in advance!

--
Best regards,
Michael
Previous Topic:[Announce] Model Driven PDE Builds - a fresh perspective
Next Topic:Request help checking out PDE source
Goto Forum:
  


Current Time: Tue Aug 03 05:23:34 GMT 2021

Powered by FUDForum. Page generated in 0.01489 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top