RE: [p2-dev] publishing a product from source, headlessly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [p2-dev] publishing a product from source, headlessly

From: "Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
Date: Wed, 8 Apr 2009 16:06:54 +0200
Delivered-to: p2-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/p2-dev>
List-help: <mailto:p2-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/p2-dev>, <mailto:p2-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/p2-dev>, <mailto:p2-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: Acm3BrdC0iAPDoVYRXCoKCuXjLCwpAATU5ewAD8DWgA=
Thread-topic: [p2-dev] publishing a product from source, headlessly

Ciao @ll :)
My 3.5-based build and tests are working now, thought I'd share some
experiences:

1.) pdebuilder now does metadata generation as well.
This new feature is awesome. No more do I need to call the director by
hand after pdebuild was finished.
Using "p2.gathering=true" did not work for a long time, took me some
hours to realize that the implicit director call was not inheriting the
pdebuilders -configuration option and thus failed with a disappointing
"Java exited with error code 13" message. I was able to work around this
problem by using the p2.director.extraArgs java property with my
"-configuration <my config>" 

2.) product build creates usable roaming installation zips, well, nearly
usable
These zips generated by "p2.gathering" are great, one issue I'm having
is that my launcher exe on unix is not getting proper execute
permissions, it gets dumped with 644 with renders the RCP unusable at
first...

3.) 3.5-based installer
Firing up my brand new 35based installer on linux I'm running into
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268321 

Also, on all hosts I'm getting these messages, note that I'm M6-based:
!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.324
!MESSAGE NLS unused message: ecf_configuration_error in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.324
!MESSAGE NLS unused message: io_invalidLocation in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.324
!MESSAGE NLS unused message: mirror_alreadyExists in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.324
!MESSAGE NLS unused message: message_mirroringStatus in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.324
!MESSAGE NLS unused message: message_childrenRepos in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: exception_comparatorNotFound in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: exception_noComparators in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: exception_destinationNotModifiable in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: exception_needSourceDestination in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: exception_malformedRepoURI in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.325
!MESSAGE NLS unused message: Mirroring_NO_MATCHING_DESCRIPTOR in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS unused message: exception_unsupportedAddToComposite in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS unused message: exception_unsupportedGetOutputStream in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS unused message: exception_unsupportedRemoveFromComposite
in: org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS missing message: FileDownloadError in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS missing message: repoMan_exists in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.326
!MESSAGE NLS missing message: repoMan_failedRead in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.327
!MESSAGE NLS missing message: repoMan_notExists in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:14.327
!MESSAGE NLS missing message: repoMan_unknownType in:
org.eclipse.equinox.internal.p2.artifact.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:15.546
!MESSAGE NLS unused message: ecf_configuration_error in:
org.eclipse.equinox.internal.p2.metadata.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:15.546
!MESSAGE NLS missing message: repoMan_adding in:
org.eclipse.equinox.internal.p2.metadata.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:15.546
!MESSAGE NLS missing message: repoMan_exists in:
org.eclipse.equinox.internal.p2.metadata.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:15.546
!MESSAGE NLS missing message: repoMan_failedRead in:
org.eclipse.equinox.internal.p2.metadata.repository.messages

!ENTRY org.eclipse.osgi 2 1 2009-04-08 14:54:15.546
!MESSAGE NLS missing message: repoMan_unknownType in:
org.eclipse.equinox.internal.p2.metadata.repository.messages

So far, so good, thanks for all your help, special thanks to Andrew for
his build support !:)
Helmut

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Haigermoser, Helmut
Sent: Tuesday, April 07, 2009 9:40 AM
To: P2 developer discussions
Subject: RE: [p2-dev] publishing a product from source, headlessly

Thanks Andrew! :) 

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Andrew Niefer
Sent: Tuesday, April 07, 2009 12:26 AM
To: P2 developer discussions
Subject: RE: [p2-dev] publishing a product from source, headlessly


The director output should come out on the console with the rest of the
ant output.  If you are calling ant programmatically, you may need to
set up a build listener. 
I did raise https://bugs.eclipse.org/bugs/show_bug.cgi?id=271386 to look
at adding support to log this separately to a file. 

-Andrew 




"Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx 

04/06/2009 12:15 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To
"P2 developer discussions" <p2-dev@xxxxxxxxxxx> cc Subject
RE: [p2-dev] publishing a product from source, headlessly

	




Ciao Andrew :)
Ah, thanks !:)
I'm trying things with April 1st' I-build now! :) Using
p2.gathering=true I'm getting past the generation into the director
phase! :) The implicit director calls are still failing as I write this
(java returned exit 13). This gets me to todays question, is there any
place I can look for director output in such a case? (Took me some time
running the director by hand on the p2.gathering-generated repos so that
I could see my product had failed dependencies...)

Anyway, keep up the great work and improvements! :) Helmut 

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Andrew Niefer
Sent: Friday, April 03, 2009 4:24 PM
To: P2 developer discussions
Subject: Re: [p2-dev] publishing a product from source, headlessly


Helmut,
You are hitting https://bugs.eclipse.org/bugs/show_bug.cgi?id=269540
(which causes 269322).  This was fixed in the IBuild after M6. 

-Andrew 



"Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx 

04/01/2009 12:47 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To
"P2 developer discussions" <p2-dev@xxxxxxxxxxx> cc Subject [p2-dev]
publishing a product from source, headlessly

                




Hi @ll :)
Just tried using 3.5 M6 to create an RCP but got stuck somehow. 
Thought I'd ask before spending too much time trying to find the right
way,
so here is what I did in 3.4                 

1.) Build the product (modify build.properties with all the
generate.p2.metadata properties) based on my .product
2.) Install from the generated repo to get a roaming, usable profile for
my RCP

>From eclipseCon I seem to remember some changes:
- pde now builds all at once (combining my two steps)
- have only a single property (can't remember which one)

Looks like my 3.4 setup succeeds in building my 3.5 code just fine (i.e.
without any changes), but does not finish the assembly phase
successfully:
.
.
.
BUILD FAILED
plugins/org.eclipse.pde.build/scripts/productBuild/productBuild.xml:32:
The following error occurred while executing this line:
plugins/org.eclipse.pde.build/scripts/build.xml:115: The following error
occurred while executing this line:
plugins/org.eclipse.pde.build/templates/headless-build/customTargets.xml
:12: The following error occurred while executing this line:
plugins/org.eclipse.pde.build/scripts/productBuild/allElements.xml:10:
The following error occurred while executing this line:
plugins/org.eclipse.pde.build/scripts/genericTargets.xml:182: The
following error occurred while executing this line:
/tmp/release_010409_18_39_35/build/package.org.eclipse.pde.build.contain
er.feature.all.xml:23: The following error occurred while executing this
line:
/tmp/release_010409_18_39_35/build/package.org.eclipse.pde.build.contain
er.feature.all.xml:15: The following error occurred while executing this
line:
plugins/org.eclipse.pde.build/scripts/productBuild/allElements.xml:44:
The following error occurred while executing this line:
/tmp/release_010409_18_39_35/build/package.org.eclipse.pde.build.contain
er.feature.win32.win32.x86.xml:96: java.io.EOFException

Removing my custom launcher name from the product helps a bit here but I
thought I'd stop experimenting at this point and ask for directions,
maybe the whole process changed and I need not try to fix these
issues...

Tried searching the docs but there is not much there yet, any help is
appreciated! :) Helmut _______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

References:
- RE: [p2-dev] publishing a product from source, headlessly
  - From: Haigermoser, Helmut
- RE: [p2-dev] publishing a product from source, headlessly
  - From: Andrew Niefer
- RE: [p2-dev] publishing a product from source, headlessly
  - From: Haigermoser, Helmut

Prev by Date: Re: [p2-dev] Feature patch and GC
Next by Date: Re: [p2-dev] installing bundle fragments
Previous by thread: RE: [p2-dev] publishing a product from source, headlessly
Next by thread: [p2-dev] error occurred while collecting items to be installed
Index(es):
- Date
- Thread

Breadcrumbs