Re: how to change the jetty port from 80 to other

Hello Simon,

Thanks very much for your help and remind.

2007/10/31, Simon Kaegi <Simon_Kaegi@...>:
> Hi Bob,
>
> These sorts of question should normally be asked in the user newsgroup
> instead of the dev list.
>
> You can configure the Jetty Server in a number of different ways:
> 1)  System properties (prefix the properties you found with the bundle name
> -- e.g. -Dorg.eclipse.equinox.http.jetty.http.port=8080)
> 2)  JettyConfigurator (see
> http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/equinox/http/jetty/JettyConfigurator.html)
> 3)  ConfigurationAdmin (The config.xml file you found is actually for use
> with the metatype service in conjunction with ConfigAdmin.)
>
> HTH
> -Simon
>
>
> equinox-dev-bounces@... wrote on 10/31/2007 02:01:36 AM:
>
> > Hello everybody,
> >
> > I am new to the Equinox, I am coding a sample application by following
> > the article " Embedding an HTTP server in Equinox".
> >
> > I coded a servlet and want to start a jetty server in Equinox. The

[prov] M3 Testing status on Linux

Here's what I've found so far while running the tests.  I'll finish the
rest tomorrow.

1. Basic install, run and update

- do not exit admin UI in between

✓ new profile creation
✓ installing 3.4M2 sdk
✓ running provisioned install
✓ update using admin UI
✓ run and verify updates applied
✓ verify updates in admin ui

- exit admin UI in between

✓ new profile creation
✓ installing 3.4M2 sdk
✓ running provisioned install
✓ update using admin UI
✓ run and verify updates applied
✓ verify updates in admin ui

2. Basic install, and update

✓ new profile creation
✓ installing 3.4M2 sdk
✓ Using the Admin UI:
✓ - look for updates, install eclipse SDK 3.4 M3 
✓ Run and verify that the plugins have been changed

Re: [sec] questions about EE for security

Re: [api tooling] Re: Using component.xml as a starting point

Re: [sec] questions about EE for security

[prov] p2 M3 wrap up call

Hello p2'ers,

The spooky night brought us a few good treats (a.k.a builds) that seem to
be working relatively well.
Let's quickly meet today at 11AM EDT to decide if we are ready to declare
M3.
The call info:
      International:  613 287 8000
      Toll free:  866 362 7064
      Participant passcode:  892048#

PaScaL

Re: [prov] M3 Testing status on Linux

Here's my latest status.  I still have to finish the manual updates test
and the installation from a remote repo and automatic updates tests to
complete.  See questions and errors below.

5. Reverting

✓ Using the Admin UI:
✓ - Create a new profile
✓ - Install an SDK
✓ - Install the releng tools 
✓ Start the provisioned install
✓ - verify the presence of the releng tools 
✓ Using the Admin UI:
✓ - Revert to the state where releng tools was not installed 
✗ - does this mean just use the admin UI's uninstall operation?
✓ Start the provisioned install
✓ - verify the absence of the releng tools 

7. Bundle pool

✓ Using the Admin UI:
✓  - Create a new profile
✓  - Install the SDK.
✓ Create a second profile
✓ Install the SDK in it
✓ - During the installation notice the dialog saying that only around
    50K should be "installed".
✓ - Notice that the download phase goes much faster. 

8. Bundle pool in the eclipse install

✓ Using the Admin UI:
✓ - Create a new profile: in the dialog set the install folder and the bundle
    pool to the same location. It will be the root of your eclipse install. 
✓ Install the SDK
✓ Verify that the plugins folder is located at a subfolder of the install
  location
✓ Verify that the path in the bundles.txt are relative.
✗ Verify that the path in the osgi.bundles property of the config.ini are
  relative 
  - is this correct?
  osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_0.1.0.200711011014.jar <at> 1\:start

  in the same config.ini as:

  osgi.framework=file\:plugins/org.eclipse.osgi_3.4.0.v20071031.jar

  - it starts up fine

9. Manual updates

✓ From the Admin UI
✓ - Create a profile
✓ - Install the SDK 3.4 M2 (or any version for which you will have an update in
✓the repository)
✓ - Install the User UI 
✓ Start the provisioned SDK
✗ - need to add a step in here for adding the testUpdates repository or
    information on how to use a local repo
✓ - Go to the end user UI (Help>Software Updates (Incubation)
✗ - need to add a step in here for selecting the sdk (or whatever we
    want to update)
✓ - On the installed features page, push the "Check for Updates" button
✗ - I get the same version I installed as an option (20071031).  I
    assume this is because the randomly-generated qualifiers don't match?
✓ - You should get a dialog showing the newer version

----- Still to be completed -----

✓ - Accept the update, restart
  - still downloading
? - Verify that the end user UI now shows the new version in the installed
?   features list 

6. Install from a remote repository

? Using the Admin UI:
? - Create a new profile
? - Point your repos to the repositories produced during the build
? - Install the SDK 
? Start the provisioned install 

10. Automatic updates

? From the Admin UI
? - Create a profile
? - Install the SDK 3.4 M2 (or any version for which you will have an update in
?   the repository)
? - Install the User UI 
? Start the provisioned SDK
? - Go to the update preference and enable the auto update
? - Wait for a notification to show up
? - Accept the install, restart 

Re: [prov] M3 Testing status on Linux

9. Manual updates

✓ From the Admin UI
✓ - Create a profile
✓ - Install the SDK 3.4 M2 (or any version for which you will have an update in
✓the repository)
✓ - Install the User UI 
✓ Start the provisioned SDK
✗ - need to add a step in here for adding the testUpdates repository or
    information on how to use a local repo
✓ - Go to the end user UI (Help>Software Updates (Incubation)
✗ - need to add a step in here for selecting the sdk (or whatever we
    want to update)
✓ - On the installed features page, push the "Check for Updates" button
✗ - I get the same version I installed as an option (20071031).  I
    assume this is because the randomly-generated qualifiers don't match?
✓ - You should get a dialog showing the newer version
✓ - Accept the update, restart
✗ - Verify that the end user UI now shows the new version in the installed
    features list 
  -- can't restart due to many errors like this:

  org.osgi.framework.BundleException: State change in progress for bundle
  "initial <at> reference:file:plugins/org.eclipse.equinox.simpleconfigurator_0.1.0.200710301724.jar/"
  by thread "main".

  - maybe I just happened to pick two bad versions?

Re: [sec] questions about EE for security

[prov] M3 docs and screen snaps