Re: [equinox-dev] [prov] manifest changes

[Timothy Webb]

My thought too.  Unfortunately PDE Update Classpath didn't seem to help.

On Feb 21, 2008, at 7:15 PM, Jeff McAffer wrote:

Feels like a missing "Update classpath" or some such.  This all  
works fine

for me though I do have foundation 1.1 installed.

Jeff


-Original Message-
From: [EMAIL PROTECTED] [mailto:equinox-dev-
[EMAIL PROTECTED] On Behalf Of Timothy Webb
Sent: Thursday, February 21, 2008 6:07 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] [prov] manifest changes

The errors I receive are all due to "is not accessible due to
restriction on required library jre..\lib\rt.jar".  It appears
that PDE is still attempting to include those values from my JRE.  My
guess would be that since I don't have a foundation 1.1 compatible  
JVM

installed, it is continuing to try and resolve the classes from the
1.6 JRE that I have configured for this workspace instead of using  
the

org.apache.xerces project that is available.  I do indeed see
org.apache.xerces listed in the Plug-in Dependencies for this  
project.


As a complete guess, I modified by hand the .classpath file.  I moved
the Plug-in Dependencies library prior to the JRE one.  Doing this
fixed the compile errors for me.  I'm guessing we probably shouldn't
be dependent on the ordering of the build path for something like
this...?

On Feb 21, 2008, at 4:44 PM, DJ Houghton wrote:


This is strange... I'm not sure why you would get errors. What type

of

errors do you see? Are they to the effect of "...can't see due to
access
restriction on org.apache.xerces"?

Either way, the code has been checked out for the test build so I

have

reverted the change in HEAD so if you reload you should be ok. But
we still
need to figure out why you are getting these errors.



[EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM:


When I picked up this change on two different systems, I receive
build
errors on the artifact repository about not being able to find the
various XML files.  I do have xerces in my workspace and doing the
normal tricks to get the project building seem to be failing.  Any
suggestions on why this change would break compilation?

Thanks,
Tim

On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote:


I have released a change to the manifest file for the
org.eclipse.equinox.p2.artifact.repository project so Kim can test
the
Foundation EE in the build. If you have this project (and this
change)
loaded into your workspace and a Foundation 1.1 VM set up, it will
also
require that you have a project like Xerces also in your  
workspace.

Xerces
is already in the project set file so you should be good, but I

just

wanted
to give you a heads up in case you see strange errors about not
finding XML
classes.


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

RE: [equinox-dev] [prov] manifest changes

[Jeff McAffer]

Feels like a missing "Update classpath" or some such.  This all works fine
for me though I do have foundation 1.1 installed.

Jeff

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:equinox-dev-
> [EMAIL PROTECTED] On Behalf Of Timothy Webb
> Sent: Thursday, February 21, 2008 6:07 PM
> To: Equinox development mailing list
> Subject: Re: [equinox-dev] [prov] manifest changes
> 
> The errors I receive are all due to "is not accessible due to
> restriction on required library jre..\lib\rt.jar".  It appears
> that PDE is still attempting to include those values from my JRE.  My
> guess would be that since I don't have a foundation 1.1 compatible JVM
> installed, it is continuing to try and resolve the classes from the
> 1.6 JRE that I have configured for this workspace instead of using the
> org.apache.xerces project that is available.  I do indeed see
> org.apache.xerces listed in the Plug-in Dependencies for this project.
> 
> As a complete guess, I modified by hand the .classpath file.  I moved
> the Plug-in Dependencies library prior to the JRE one.  Doing this
> fixed the compile errors for me.  I'm guessing we probably shouldn't
> be dependent on the ordering of the build path for something like
> this...?
> 
> On Feb 21, 2008, at 4:44 PM, DJ Houghton wrote:
> 
> > This is strange... I'm not sure why you would get errors. What type
> of
> > errors do you see? Are they to the effect of "...can't see due to
> > access
> > restriction on org.apache.xerces"?
> >
> > Either way, the code has been checked out for the test build so I
> have
> > reverted the change in HEAD so if you reload you should be ok. But
> > we still
> > need to figure out why you are getting these errors.
> >
> >
> >
> > [EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM:
> >
> >> When I picked up this change on two different systems, I receive
> >> build
> >> errors on the artifact repository about not being able to find the
> >> various XML files.  I do have xerces in my workspace and doing the
> >> normal tricks to get the project building seem to be failing.  Any
> >> suggestions on why this change would break compilation?
> >>
> >> Thanks,
> >> Tim
> >>
> >> On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote:
> >>
> >>> I have released a change to the manifest file for the
> >>> org.eclipse.equinox.p2.artifact.repository project so Kim can test
> >>> the
> >>> Foundation EE in the build. If you have this project (and this
> >>> change)
> >>> loaded into your workspace and a Foundation 1.1 VM set up, it will
> >>> also
> >>> require that you have a project like Xerces also in your workspace.
> >>> Xerces
> >>> is already in the project set file so you should be good, but I
> just
> >>> wanted
> >>> to give you a heads up in case you see strange errors about not
> >>> finding XML
> >>> classes.
> >>
> >> ___
> >> equinox-dev mailing list
> >> equinox-dev@eclipse.org
> >> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> >
> > ___
> > equinox-dev mailing list
> > equinox-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> ___
> equinox-dev mailing list
> equinox-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] [prov] manifest changes

[Timothy Webb]

The errors I receive are all due to "is not accessible due to  
restriction on required library jre..\lib\rt.jar".  It appears  
that PDE is still attempting to include those values from my JRE.  My  
guess would be that since I don't have a foundation 1.1 compatible JVM  
installed, it is continuing to try and resolve the classes from the  
1.6 JRE that I have configured for this workspace instead of using the  
org.apache.xerces project that is available.  I do indeed see  
org.apache.xerces listed in the Plug-in Dependencies for this project.


As a complete guess, I modified by hand the .classpath file.  I moved  
the Plug-in Dependencies library prior to the JRE one.  Doing this  
fixed the compile errors for me.  I'm guessing we probably shouldn't  
be dependent on the ordering of the build path for something like  
this...?


On Feb 21, 2008, at 4:44 PM, DJ Houghton wrote:


This is strange... I'm not sure why you would get errors. What type of
errors do you see? Are they to the effect of "...can't see due to  
access

restriction on org.apache.xerces"?

Either way, the code has been checked out for the test build so I have
reverted the change in HEAD so if you reload you should be ok. But  
we still

need to figure out why you are getting these errors.



[EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM:

When I picked up this change on two different systems, I receive  
build

errors on the artifact repository about not being able to find the
various XML files.  I do have xerces in my workspace and doing the
normal tricks to get the project building seem to be failing.  Any
suggestions on why this change would break compilation?

Thanks,
Tim

On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote:


I have released a change to the manifest file for the
org.eclipse.equinox.p2.artifact.repository project so Kim can test  
the
Foundation EE in the build. If you have this project (and this  
change)

loaded into your workspace and a Foundation 1.1 VM set up, it will
also
require that you have a project like Xerces also in your workspace.
Xerces
is already in the project set file so you should be good, but I just
wanted
to give you a heads up in case you see strange errors about not
finding XML
classes.


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] [prov] manifest changes

[DJ Houghton]

This is strange... I'm not sure why you would get errors. What type of
errors do you see? Are they to the effect of "...can't see due to access
restriction on org.apache.xerces"?

Either way, the code has been checked out for the test build so I have
reverted the change in HEAD so if you reload you should be ok. But we still
need to figure out why you are getting these errors.



[EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM:

> When I picked up this change on two different systems, I receive build
> errors on the artifact repository about not being able to find the
> various XML files.  I do have xerces in my workspace and doing the
> normal tricks to get the project building seem to be failing.  Any
> suggestions on why this change would break compilation?
>
> Thanks,
> Tim
>
> On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote:
>
> > I have released a change to the manifest file for the
> > org.eclipse.equinox.p2.artifact.repository project so Kim can test the
> > Foundation EE in the build. If you have this project (and this change)
> > loaded into your workspace and a Foundation 1.1 VM set up, it will
> > also
> > require that you have a project like Xerces also in your workspace.
> > Xerces
> > is already in the project set file so you should be good, but I just
> > wanted
> > to give you a heads up in case you see strange errors about not
> > finding XML
> > classes.
>
> ___
> equinox-dev mailing list
> equinox-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] [prov] manifest changes

[Timothy Webb]

When I picked up this change on two different systems, I receive build  
errors on the artifact repository about not being able to find the  
various XML files.  I do have xerces in my workspace and doing the  
normal tricks to get the project building seem to be failing.  Any  
suggestions on why this change would break compilation?


Thanks,
Tim

On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote:


I have released a change to the manifest file for the
org.eclipse.equinox.p2.artifact.repository project so Kim can test the
Foundation EE in the build. If you have this project (and this change)
loaded into your workspace and a Foundation 1.1 VM set up, it will  
also
require that you have a project like Xerces also in your workspace.  
Xerces
is already in the project set file so you should be good, but I just  
wanted
to give you a heads up in case you see strange errors about not  
finding XML

classes.


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

[equinox-dev] [prov] manifest changes

[DJ Houghton]

I have released a change to the manifest file for the
org.eclipse.equinox.p2.artifact.repository project so Kim can test the
Foundation EE in the build. If you have this project (and this change)
loaded into your workspace and a Foundation 1.1 VM set up, it will also
require that you have a project like Xerces also in your workspace. Xerces
is already in the project set file so you should be good, but I just wanted
to give you a heads up in case you see strange errors about not finding XML
classes.



___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide

[Pascal Rapicault]

I have released a change to the launch configuration that should fix the
problem. Please try after having synchronized with CVS the
org.eclipse.equinox.p2.ui.admin.rcp




|>
| From:  |
|>
  
>--|
  |Jeff Hamm <[EMAIL PROTECTED]>
 |
  
>--|
|>
| To:|
|>
  
>--|
  |"equinox-dev@eclipse.org"   
 |
  
>--|
|>
| Date:  |
|>
  
>--|
  |02/21/2008 12:57 PM  
 |
  
>--|
|>
| Subject:   |
|>
  
>--|
  |[equinox-dev] Equinox p2 -Problem running director app from the Getting 
Started for Developers Guide  |
  
>--|





All --

I have been trying to work through the Getting Started for Developers
Guide( http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers<
http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers%20>) and
I'm having a problem running the  director app part of the setup.

I have downloaded the src code for p2 and built the project based on the
steps listed in the guide.
I have successfully run the Metadata Generator SDK and had it do its work
against a 3.3 eclipse instance that I had previously installed.

When running the director app in the next step of the guide, I get the
following exception.


osgi> !SESSION 2008-02-21 12:35:51.494
---
eclipse.buildId=unknown
java.version=1.5.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -application
org.eclipse.equinox.p2.director.app.application -metadataRepository
file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\
-installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling
-profile foo
Command-line arguments:  -dev
file:C:/jehamm/dev/open_source/.metadata/.plugins/org.eclipse.pde.core/director
 app/dev.properties -console -consolelog -application
org.eclipse.equinox.p2.director.app.application -metadataRepository
file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\
-installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling
-profile foo

!ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service.
Ensure that the org.eclipse.core.runtime bundle is resolved and started
(see config.ini).
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:72)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:362)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:564)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1251)
at org.eclipse.equinox.launcher.Main.main(Main.java:1227)


I found this link
http://permalink.gmane.org/gmane.comp.ide.eclipse.equinox.devel/2644
which describes what may be the problem and followed the bugzilla defect.
It appears to have been fixed in 3.4M4 timeframe.

I have subsequently downloade

RE: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide

[Jeff Hamm]

Thanks -- will do

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Kaegi
Sent: Thursday, February 21, 2008 3:36 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Equinox p2 -Problem running director app from the 
Getting Started for Developers Guide

Jeff,

I'm running into a similar problems when launching the dev-time ProvAdmin
UI. I've opened up a bug to take a look --
https://bugs.eclipse.org/bugs/show_bug.cgi?id=219862
You might want to add yourself to the CC list.

-Simon

[EMAIL PROTECTED] wrote on 02/21/2008 12:56:59 PM:

> All --
>
> I have been trying to work through the Getting Started for
> Developers Guide( http://wiki.eclipse.
> org/Equinox_p2_Getting_Started_for_Developers org/Equinox_p2_Getting_Started_for_Developers%20>) and I'm having a
> problem running the  director app part of the setup.
>
> I have downloaded the src code for p2 and built the project based on
> the steps listed in the guide.
> I have successfully run the Metadata Generator SDK and had it do its
> work against a 3.3 eclipse instance that I had previously installed.
>
> When running the director app in the next step of the guide, I get
> the following exception.
>
>
> osgi> !SESSION 2008-02-21 12:35:51.494
> ---
> eclipse.buildId=unknown
> java.version=1.5.0_12
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments:  -application org.eclipse.equinox.p2.director.
> app.application -metadataRepository file:C:\equinox.p2\servers\ -
> artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -
> destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo
> Command-line arguments:  -dev file:C:/jehamm/dev/open_source/.
> metadata/.plugins/org.eclipse.pde.core/director app/dev.properties -
> console -consolelog -application org.eclipse.equinox.p2.director.
> app.application -metadataRepository file:C:\equinox.p2\servers\ -
> artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -
> destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo
>
> !ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalStateException: Unable to acquire application
> service. Ensure that the org.eclipse.core.runtime bundle is resolved
> and started (see config.ini).
> at org.eclipse.core.runtime.internal.adaptor.
> EclipseAppLauncher.start(EclipseAppLauncher.java:72)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.
> run(EclipseStarter.java:362)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.
> run(EclipseStarter.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:564)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1251)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1227)
>
>
> I found this link
> http://permalink.gmane.org/gmane.comp.ide.eclipse.equinox.devel/2644
> which describes what may be the problem and followed the bugzilla
> defect. It appears to have been fixed in 3.4M4 timeframe.
>
> I have subsequently downloaded the eclipse source and examined the
> files that the bugzilla referenced and do not see the changes in the
> source I downloaded.
> I assume that I have the wrong 3.4M5 downloaded? This is the link I
> got the 3.4M5 src from.
> http://mirror.calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/index.php
> Source Build (Source in .zip) (instructions calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/srcIncludedBuildInstructions.html>)   (http) //mirror.calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/download.php?dropFile=eclipse-sourceBuild-
> srcIncluded-3.4M5.zip>   93 MB   eclipse-sourceBuild-srcIncluded-3.
> 4M5.zip   (md5) org/eclipse/downloads/drops/S-3.4M5-200802071530/checksum/eclipse-
> sourceBuild-srcIncluded-3.4M5.zip.md5> (sha1) eclipse.org/eclipse/downloads/drops/S-3.
> 4M5-200802071530/checksum/eclipse-sourceBuild-srcIncluded-3.4M5.zip.sha1>
>
> and here is how I got the p2 code .
>
> 1.
>
> Create a CVS repository location for ":pserver:[EMAIL PROTECTED]
> eclipse.org:/cvsroot/eclipse".
> 2.  Expand HEAD > equinox-incubator > provisioning
> 3.  Checkout "org.eclipse.equinox.p2.releng"
> 4.  Import the "projectSet.psf" project set using File > Import
> > Team Project Set in the releng project you just checked out.
>
> Is this correct, or can anyone provide the correct links to work fr

Re: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide

[Simon Kaegi]

Jeff,

I'm running into a similar problems when launching the dev-time ProvAdmin
UI. I've opened up a bug to take a look --
https://bugs.eclipse.org/bugs/show_bug.cgi?id=219862
You might want to add yourself to the CC list.

-Simon

[EMAIL PROTECTED] wrote on 02/21/2008 12:56:59 PM:

> All --
>
> I have been trying to work through the Getting Started for
> Developers Guide( http://wiki.eclipse.
> org/Equinox_p2_Getting_Started_for_Developers org/Equinox_p2_Getting_Started_for_Developers%20>) and I'm having a
> problem running the  director app part of the setup.
>
> I have downloaded the src code for p2 and built the project based on
> the steps listed in the guide.
> I have successfully run the Metadata Generator SDK and had it do its
> work against a 3.3 eclipse instance that I had previously installed.
>
> When running the director app in the next step of the guide, I get
> the following exception.
>
>
> osgi> !SESSION 2008-02-21 12:35:51.494
> ---
> eclipse.buildId=unknown
> java.version=1.5.0_12
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments:  -application org.eclipse.equinox.p2.director.
> app.application -metadataRepository file:C:\equinox.p2\servers\ -
> artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -
> destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo
> Command-line arguments:  -dev file:C:/jehamm/dev/open_source/.
> metadata/.plugins/org.eclipse.pde.core/director app/dev.properties -
> console -consolelog -application org.eclipse.equinox.p2.director.
> app.application -metadataRepository file:C:\equinox.p2\servers\ -
> artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -
> destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo
>
> !ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalStateException: Unable to acquire application
> service. Ensure that the org.eclipse.core.runtime bundle is resolved
> and started (see config.ini).
> at org.eclipse.core.runtime.internal.adaptor.
> EclipseAppLauncher.start(EclipseAppLauncher.java:72)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.
> run(EclipseStarter.java:362)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.
> run(EclipseStarter.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:564)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1251)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1227)
>
>
> I found this link
> http://permalink.gmane.org/gmane.comp.ide.eclipse.equinox.devel/2644
> which describes what may be the problem and followed the bugzilla
> defect. It appears to have been fixed in 3.4M4 timeframe.
>
> I have subsequently downloaded the eclipse source and examined the
> files that the bugzilla referenced and do not see the changes in the
> source I downloaded.
> I assume that I have the wrong 3.4M5 downloaded? This is the link I
> got the 3.4M5 src from.
> http://mirror.calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/index.php
> Source Build (Source in .zip) (instructions calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/srcIncludedBuildInstructions.html>)   (http) //mirror.calvin.edu/eclipse/downloads/drops/S-3.
> 4M5-200802071530/download.php?dropFile=eclipse-sourceBuild-
> srcIncluded-3.4M5.zip>   93 MB   eclipse-sourceBuild-srcIncluded-3.
> 4M5.zip   (md5) org/eclipse/downloads/drops/S-3.4M5-200802071530/checksum/eclipse-
> sourceBuild-srcIncluded-3.4M5.zip.md5> (sha1) eclipse.org/eclipse/downloads/drops/S-3.
> 4M5-200802071530/checksum/eclipse-sourceBuild-srcIncluded-3.4M5.zip.sha1>
>
> and here is how I got the p2 code .
>
> 1.
>
> Create a CVS repository location for ":pserver:[EMAIL PROTECTED]
> eclipse.org:/cvsroot/eclipse".
> 2.  Expand HEAD > equinox-incubator > provisioning
> 3.  Checkout "org.eclipse.equinox.p2.releng"
> 4.  Import the "projectSet.psf" project set using File > Import
> > Team Project Set in the releng project you just checked out.
>
> Is this correct, or can anyone provide the correct links to work from?
>
> Thanks --
> Jeff
>
> Here is the information in the Help->About Eclipse SDK that I am
> invoking the director app from.
>
> Eclipse SDK
>
> Version: 3.4.0
> Build id: I20080207-1530
>
>
>
> ___
> equinox-dev mailing list
> equinox-dev@eclipse.org
> https://dev.ecl

[equinox-dev] [prov] p2 UI prios for EclipseCon, M6, and beyond...

[Susan Franklin McCourt]

In the p2 call on Tuesday, Scott was asking if I had bandwidth for some
service discovery UI (in particular discovering p2 repos) before
EclipseCon.
I promised to make a prio list of UI work items so that I could answer that
question.

Please take a look at:
http://wiki.eclipse.org/Equinox_p2_UI_Plan

I've made a pass over the UI items planned for 1.0
P0 = must have for SDK integration
P1 = must have for 1.0 (functionality)
P2 = should have for 1.0 (usability)
P3 = nice to have for 1.0 (wow factor)

- if we are forgetting any P0 items you know of, please let me know ASAP as
I think we are ready (apart from responding to underlying changes that are
P0)
- if you see anything missing, please add to the wiki page and report here,
especially P1 items
- if you think that the priorities need to be changed, let's have that
discussion on this list, or if it gets too difficult, in a p2 call.  (I may
not notice if you simply edit my prio list!)

An interesting scheduling thing is that EclipseCon is coming up, so working
through the P1 list as our M6 plan may not be exactly what we want to do.
As you can imagine, feature completeness is not nearly as great for
presentations as "wow" items.  I don't want to work on too many P2 and P3
features before having confidence we can finish P1, but if we all think
that the posted P1 list is complete, it looks like I could promote one or
two lower prio items...

Thanks everyone,
Susan___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Building against specific EEs

[DJ Houghton]

> Ok, I have a few ... I'm not familiar with the background, so I'm
> not sure if I need to know or not. :)
>
> > eRCP XML bundles
>
> What are these?
> Can the ones in Orbit work? Such as javax.xml_1.3.4
>

Yes, I believe we could use this bundle as well. (or Xerces, etc) We just
need the XML APIs to compile against.

> > Note that this will require people to have the XML APIs available in
their
> > workspace if they are set up with exact match VMs.
>
> What's exact match mean? You mean lower than 1.4 or Java 5 VMs?
>
> > We will adjust the project set files to load
> > Xerces or the bundles from eRCP, accordingly.
>
> According to what? And, are you saying never from the VM?
>

If you add a Foundation VM to your list of installed JREs and it is
correctly identified as an exact match to that profile, then you will not
get (for instance) the XML APIs for free (from the VM) so you need you have
another bundle in your workspace which can provide them.

If you don't have a lower profile (like Foundation) VM installed, then you
will not be effected because 1.4/1.5/1.6 VMs are considered to be
compatible and your bundles will still resolve and function correctly.

Here is a (probably a little out-dated) wiki page that we put together with
a bit more info on EEs and setting things up.

http://wiki.eclipse.org/Execution_Environments


>
> From:
>
> DJ Houghton <[EMAIL PROTECTED]>
>
> To:
>
> equinox-dev@eclipse.org
>
> Date:
>
> 02/20/2008 05:30 PM
>
> Subject:
>
> [equinox-dev] Building against specific EEs
>
>
>
>
>
>
> As mentioned in the Equinox call earlier this week, I am investigating
the
> EE situation with our bundles and how it relates to the build. Kim and I
> discussed this today and we will move forward by:
>
> - Kim ensuring that VMs for the appropriate profiles are available in the
> build (in the process of aquiring Foundation 1.1)
> - downloading the eRCP XML bundles and put them in a spot so PDE/Build
> knows to take them into account when compiling
> - running a test build with one of our "requires XML" bundles changed to
> have the correct order for the EE
>
> If everything is ok, then we will recommend that the order of EEs in the
> bundle manifests be changed to reflect the true order.
>
> Note that this will require people to have the XML APIs available in
their
> workspace if they are set up with exact match VMs. We will adjust the
> project set files to load Xerces or the bundles from eRCP, accordingly.
>
> Please direct question or comments to this list.
>
> Thanks.
>
>
> ___
> equinox-dev mailing list
> equinox-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> ___
> equinox-dev mailing list
> equinox-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

[equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide

[Jeff Hamm]

All --

I have been trying to work through the Getting Started for Developers Guide( 
http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers)
 and I'm having a problem running the  director app part of the setup.

I have downloaded the src code for p2 and built the project based on the steps 
listed in the guide.
I have successfully run the Metadata Generator SDK and had it do its work 
against a 3.3 eclipse instance that I had previously installed.

When running the director app in the next step of the guide, I get the 
following exception.


osgi> !SESSION 2008-02-21 12:35:51.494 
---
eclipse.buildId=unknown
java.version=1.5.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -application 
org.eclipse.equinox.p2.director.app.application -metadataRepository 
file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ 
-installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile 
foo
Command-line arguments:  -dev 
file:C:/jehamm/dev/open_source/.metadata/.plugins/org.eclipse.pde.core/director 
app/dev.properties -console -consolelog -application 
org.eclipse.equinox.p2.director.app.application -metadataRepository 
file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ 
-installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile 
foo

!ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure 
that the org.eclipse.core.runtime bundle is resolved and started (see 
config.ini).
at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:72)
at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:362)
at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:564)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1251)
at org.eclipse.equinox.launcher.Main.main(Main.java:1227)


I found this link
http://permalink.gmane.org/gmane.comp.ide.eclipse.equinox.devel/2644
which describes what may be the problem and followed the bugzilla defect. It 
appears to have been fixed in 3.4M4 timeframe.

I have subsequently downloaded the eclipse source and examined the files that 
the bugzilla referenced and do not see the changes in the source I downloaded.
I assume that I have the wrong 3.4M5 downloaded? This is the link I got the 
3.4M5 src from.
http://mirror.calvin.edu/eclipse/downloads/drops/S-3.4M5-200802071530/index.php
Source Build (Source in .zip) 
(instructions)
   
(http)
   93 MB   eclipse-sourceBuild-srcIncluded-3.4M5.zip   
(md5)
 
(sha1)

and here is how I got the p2 code .

1.

Create a CVS repository location for ":pserver:[EMAIL 
PROTECTED]:/cvsroot/eclipse".
2.  Expand HEAD > equinox-incubator > provisioning
3.  Checkout "org.eclipse.equinox.p2.releng"
4.  Import the "projectSet.psf" project set using File > Import > Team 
Project Set in the releng project you just checked out.

Is this correct, or can anyone provide the correct links to work from?

Thanks --
Jeff

Here is the information in the Help->About Eclipse SDK that I am invoking the 
director app from.

Eclipse SDK

Version: 3.4.0
Build id: I20080207-1530



___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

[equinox-dev] [prov] Build, p2 and consumption

[Pascal Rapicault]

Hi,

I just posted on the wiki a document [1] reviewing the implication of p2 on
what/how people build and how the consumption of the build output is
affected.
If I have missed any use-case or have remarks  / suggestions, etc. please
respond to this email
Thx

PaScaL

[1] http://wiki.eclipse.org/Equinox_p2_build_and_consumption

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Building against specific EEs

[Mark Rogalski]

eRCP XML bundles, also known as "microXML" are in the Eclipse embedded 
Rich Client Platform project (www.eclipse.org/ercp).
The two bundles provide full DOM Level 2, SAX 2.0 and JAXP 1.0 support in 
about 100k. Part of the reason for the small size is that the parser is 
non-validating.
You can check out the two projects from CVS or get pre-built bundles from 
an eRCP runtime.

Mark




David M Williams/Raleigh/[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
02/20/2008 05:19 PM
Please respond to
Equinox development mailing list 


To
Equinox development mailing list 
cc

Subject
Re: [equinox-dev] Building against specific EEs







> Please direct question or comments to this list.

Ok, I have a few ... I'm not familiar with the background, so I'm not sure 
if I need to know or not. :) 

> eRCP XML bundles 

What are these? 
Can the ones in Orbit work? Such as javax.xml_1.3.4 


> Note that this will require people to have the XML APIs available in 
their
> workspace if they are set up with exact match VMs. 

What's exact match mean? You mean lower than 1.4 or Java 5 VMs? 

> We will adjust the project set files to load 
> Xerces or the bundles from eRCP, accordingly. 

According to what? And, are you saying never from the VM? 





From: 
DJ Houghton <[EMAIL PROTECTED]> 
To: 
equinox-dev@eclipse.org 
Date: 
02/20/2008 05:30 PM 
Subject: 
[equinox-dev] Building against specific EEs





As mentioned in the Equinox call earlier this week, I am investigating the
EE situation with our bundles and how it relates to the build. Kim and I
discussed this today and we will move forward by:

- Kim ensuring that VMs for the appropriate profiles are available in the
build (in the process of aquiring Foundation 1.1)
- downloading the eRCP XML bundles and put them in a spot so PDE/Build
knows to take them into account when compiling
- running a test build with one of our "requires XML" bundles changed to
have the correct order for the EE

If everything is ok, then we will recommend that the order of EEs in the
bundle manifests be changed to reflect the true order.

Note that this will require people to have the XML APIs available in their
workspace if they are set up with exact match VMs. We will adjust the
project set files to load Xerces or the bundles from eRCP, accordingly.

Please direct question or comments to this list.

Thanks.


___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

RE: [equinox-dev] How do I write an Application Container

[Srijith Kochunni]

 Hi Dennis,

I tried searching the mail archives but could not find much 
discussion on the same. Had gone through the wiki earlier (Sorry about not 
mentioning earlier) Problem with that is that it is much too specific to 
'Eclipse'. I was looking for a simple application where the container 
Implementation is also provided. In the case of the wiki, the application 
container implementation is again abstracted and seems to be 
'org.eclipse.core.runtime.applications'. 

   Anyway thanks for your quick help. Shall post any developments.

Thanks,
Srijith.
 
>>> "O'Flynn, Dennis" <[EMAIL PROTECTED]> 02/21/08 6:22 PM >>> 
Have you searched the following resources?  I found some very help
postings here that may answer your questions.
* Eclipse RCP/PDE online help (re: ext point
org.eclipse.core.runtime.applications)
* Eclipse Wiki (see
http://wiki.eclipse.org/Equinox_Application_Model_Demo)
* Newsgroup (eclipse.technology.equinox)



The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it.

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Srijith Kochunni
Sent: Thursday, February 21, 2008 7:46 AM
To: equinox-dev@eclipse.org
Subject: [equinox-dev] How do I write an Application Container


Hi,

I am interested in knowing how an Application container is written.
Went through the specification, but am not really able to get a good
picture of how they are built and how they interact with each other. I
was therefore interested in knowing if there is any examples or
documentation relevant to this either on the internet / elsewhere, which
could help me.

I am looking at writing a small application instance, a descriptor for
it, and an Application Manager implementation to manage it. How is an
Application Handle retrieved and also knowing how to schedule my
application would be an added bonus..! The code snippets and details
provided in the spec, don`t seem complete.

Please excuse me for the avalanche of questions. Any help or leads would
be greatly appreciated.

Thanks,
Srijith.




___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

RE: [equinox-dev] How do I write an Application Container

[O'Flynn, Dennis]

Have you searched the following resources?  I found some very help
postings here that may answer your questions.
* Eclipse RCP/PDE online help (re: ext point
org.eclipse.core.runtime.applications)
* Eclipse Wiki (see
http://wiki.eclipse.org/Equinox_Application_Model_Demo)
* Newsgroup (eclipse.technology.equinox)



The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it.

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Srijith Kochunni
Sent: Thursday, February 21, 2008 7:46 AM
To: equinox-dev@eclipse.org
Subject: [equinox-dev] How do I write an Application Container


Hi,

I am interested in knowing how an Application container is written.
Went through the specification, but am not really able to get a good
picture of how they are built and how they interact with each other. I
was therefore interested in knowing if there is any examples or
documentation relevant to this either on the internet / elsewhere, which
could help me.

I am looking at writing a small application instance, a descriptor for
it, and an Application Manager implementation to manage it. How is an
Application Handle retrieved and also knowing how to schedule my
application would be an added bonus..! The code snippets and details
provided in the spec, don`t seem complete.

Please excuse me for the avalanche of questions. Any help or leads would
be greatly appreciated.

Thanks,
Srijith.




___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

[equinox-dev] How do I write an Application Container

[Srijith Kochunni]

Hi,

I am interested in knowing how an Application container is written. Went 
through the specification, but am not really able to get a good picture of how 
they are built and how they interact with each other. I was therefore 
interested in knowing if there is any examples or documentation relevant to 
this either on the internet / elsewhere, which could help me.

I am looking at writing a small application instance, a descriptor for it, and 
an Application Manager implementation to manage it. How is an Application 
Handle retrieved and also knowing how to schedule my application would be an 
added bonus..! The code snippets and details provided in the spec, don`t seem 
complete.

Please excuse me for the avalanche of questions. Any help or leads would be 
greatly appreciated.

Thanks,
Srijith.




___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

RE: [equinox-dev] [prov] ID consistency in the metadata

[Jeff McAffer]

> Installable Units
> - "org.eclipse.equinox.p2.iunamespace" is the namespace in which the
> identifier of every IU is made available. It can be used in
> capabilities
> and requirements.
> - Installable units have a type which is used to differentiate between
> IUs.
> The name of this property is "org.eclipse.equinox.p2.type" and can
> currently take 2 values ("iu.fragment," "group"). Similarly to this
> type we
> have the "categoryIU" property whose value can be set to "true". I'm

Must avoid Boolean valued anything.

> really
> wondering why categories and group / fragments are not handled the
> same?
> Also "iu.fragment" is a weird name.

Consistency here would be good and I agree that iu.fragment is strange

> - IUs also have a lot of properties carrying information such as:
> description (equinox.p2.description), name (equinox.p2.name), etc...
> See
> the IInstallableUnit interface.
> - The IUs carrying configuration information usually have a capability
> whose namespace is "flavor". Why is this not qualified like any other
> name?
> - IUs have an applicability filter. Most of our filters are expressed
> in
> terms of "osgi.ws", "osgi.os", "osgi.arch". The presence of osgi in the
> name of these filter does not seem appropriate since they are used to
> filter arbitraty things. What don't we simply call those "os", "ws",
> "arch"?

Agreed that having "osgi" there is strange.  Not sure that just ws, os, ...
is appropriate.  This should be subject to the same qualification terms we
define elsewhere

> Type for the things delivered by the IU
> In 1.0 our main focus is on eclipse things: bundles, source bundles,
> features, packages. To represent all those we have defined the
> following
> namespaces:
> - "osgi.bundles", who describe the symbolic id of the bundle delivered
> by
> the IU. Should that be more qualified like "org.osgi.bundles"? Should
> we
> talk to the OSGi Alliance?

Don't think we want to use an org.osgi namespace here.  We don't qualify
"osgi" with "org." anywhere else in Equinox.  Perhaps we just remove the
"osgi" part?  Dunno, there might be other kinds of bundles being delivered
in the future.

> - "osgi.packages", who describe the packages delivered in the IU. I
> think
> this should likely be renamed into "java.packages".

Yup

> - "osgi.source.bundles", this provides a capability with the name of
> the
> source bundle itself. It is not used in any requirement expression. Do
> we
> want to keep it? Would not it be smarter / more useful to have a
> capability
> saying which bundle it is the source of?

Not sure here but it needs to be easy to find source bundles and to find the
source bundle for a particular bundle.

> Also in order to distinguish between a bundle, a feature and a source
> bundle we have the "org.eclipse.equinox.p2.eclipsetouchpoint.types"
> namespace which can take "bundle", "feature", "source" as value.
> 
> Touchpoint types
> We currently have 2 touchpoints: eclipse and native. Should the name of
> these be more general? Should the eclipse one be renamed to "osgi" (or
> something like that) and have the eclipse specific things in another
> touchpoint?

The Eclipse touchpoint talks a lot about bundle pooling and other things
that are specific to Eclipse right?  I could see it being Equinox but am not
so sure we are general enough to call it osgi.

> Artifacts:
> The namespace of artifact keys are just used as an indexing mechanism
> in
> the repository. We currently define "eclipse", "native" and for each
> one of
> them we have "plugins". Should we change the "eclipse" one to be more
> specific?

Not sure what you mean here.  As I recall, the type and classifier were
there to help with auto-indexing of the repo.  Not sure that is still needed
because of the mapping rules.  Personally I would use equinox and bundles.
Not sure if/why the native guy has "bundles" associated with it.


> Other things
> Outside of the metadata we have system properties (e.g.
> "eclipse.p2.data.area") that are in the eclipse.p2 namespace and also
> profile properties (e.g. "eclipse.p2.install.features") ,
> 
> 
> Changes
> For IUs:
> - having every namespace id who contains p2 be prefixed with
> "org.eclipse.p2.", have flavors also be prefixed
> - have IU properties be either just their short name (e.g. description
> instead of equinox,p2.description) or be prefixed with iu (e.g.
> iu.description)

Why don't properties need to be qualified?  Not sure putting iu on the front
of things helps.  Is there another kind of description that is relevant
here?

> - remove osgi of the filters

+1 but not sure they should then be unqualified.

> For bundles, features etc.
> - Ask the opinion of BJ and Peter about the name we should use for
> bundles.

Don't see the need for this.  They will say no because it is not something
that OSGi wants to define at this point.  Not sure what it gets us.

> - Use "java.packages" for packages. Is there any trademark issue with
> that?

+1 unlikely TM issues

Je