Re: [equinox-dev] Tom Watson: Equinox co-lead

2008-01-24 Thread Richard S. Hall

You da' man, Tom!

- richard

Jeff McAffer wrote:


Recently I was reviewing the Equinox project, the direction and the 
community around it.  One of the things that stood out for me is that 
Tom Watson has been quietly leading vast swaths of the activity in 
Equinox from the framework and service implementations to the OSGi 
spec work and areas in between.  Not only does Tom produce great code 
and designs but he has a great sense of the community and repeatedly 
performs heroic feats to meet their needs.  

It is with great pleasure that the Eclipse PMC invited Tom to co-lead 
the Equinox project and he accepted.  Congratulations Tom and thanks 
for all the great work!



___
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] Tom Watson: Equinox co-lead

2008-01-24 Thread Simon Kaegi
Congrats Tom.

[EMAIL PROTECTED] wrote on 01/23/2008 11:36:40 PM:


 Recently I was reviewing the Equinox project, the direction and the
 community around it.  One of the things that stood out for me is
 that Tom Watson has been quietly leading vast swaths of the activity
 in Equinox from the framework and service implementations to the
 OSGi spec work and areas in between.  Not only does Tom produce
 great code and designs but he has a great sense of the community and
 repeatedly performs heroic feats to meet their needs.

 It is with great pleasure that the Eclipse PMC invited Tom to co-
 lead the Equinox project and he accepted.  Congratulations Tom and
 thanks for all the great
work!___
 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] Tom Watson: Equinox co-lead

2008-01-24 Thread Chris Aniszczyk
This is like the greatest day ever. Tom is now a co-lead and idles on IRC.

Congrats!

Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | 
http://mea-bloga.blogspot.com | +1.860.839.2465



From:
Simon Kaegi [EMAIL PROTECTED]
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
01/24/2008 09:03 AM
Subject:
Re: [equinox-dev] Tom Watson:  Equinox co-lead



Congrats Tom.

[EMAIL PROTECTED] wrote on 01/23/2008 11:36:40 PM:


 Recently I was reviewing the Equinox project, the direction and the
 community around it.  One of the things that stood out for me is
 that Tom Watson has been quietly leading vast swaths of the activity
 in Equinox from the framework and service implementations to the
 OSGi spec work and areas in between.  Not only does Tom produce
 great code and designs but he has a great sense of the community and
 repeatedly performs heroic feats to meet their needs.

 It is with great pleasure that the Eclipse PMC invited Tom to co-
 lead the Equinox project and he accepted.  Congratulations Tom and
 thanks for all the great
work!___
 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] [prov] Updated to new ECF

2008-01-24 Thread DJ Houghton

I have made the changes in the p2 build to move to the latest version of
ECF.

Details are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=213381

The project set files have been updated and should be reloaded.


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


[equinox-dev] Equinox with OSGi security?

2008-01-24 Thread Marcel Offermans
I would like to run Equinox with OSGi security (PermissionAdmin,  
ConditionalPermissionAdmin) enabled.


I read the quickstart guide here:

http://www.eclipse.org/equinox/documents/quickstart.php

I even found some reference to a property to set that should enable  
security:


- 
Declipse 
.security 
=org.eclipse.osgi.framework.internal.core.FrameworkSecurityManager


However, if I just run the Equinox framework like described in the  
quickstart guide with that property, I still do not get any security  
related service. Am I missing some piece of documentation here? It  
should not be too hard to run with security, right?


Greetings, Marcel

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


[equinox-dev] [prov] Creating Eclipse Packages

2008-01-24 Thread Jeff McAffer



From Ian in the committer list. There might be some input needed here 
from p2 if we are going to produce installers etc.


Jeff

Dear Eclipse Committers

We would like to encourage more participation in the creation of the 
packages created by the Eclipse Packaging Project. The goal is to 1) 
encourage more cross-project testing of the existing four packages, and 
2) encourage the creation of packages in addition to the existing four 
that were created last year. A framework for doing this was discussed at 
a recent Planning Council meeting 
http://wiki.eclipse.org/Planning_Council_Minutes_2007.11.06#Packages 
and this document is to provide addition details.


  1. Creation of a Package

To create a package a project leader or committer must agree to be a 
package maintainer. The package maintainer is responsible for defining 
the contents of the package and arrange for testing of the package.


To define a package the package maintainer will need to specify the 
package contents based on the EPP package configuration file format 
http://wiki.eclipse.org/EPP/Configuration_File_Format. The package 
maintainer will need to store this file in their cvs repository and then 
inform the EPP team, via a bugzilla entry, the location of the file. The 
EPP team will then begin to automatically build the package based on the 
config file.


  2. What can be included in a Package?

· Packages must only contain code from Eclipse projects

· Packages should usually only contain code from projects that have 
passed their 1.0 creation review, and if exceptions are found, the code 
must still have passed an Eclipse Release Review.


· Packages should attempt to include code from a variety of projects, 
while maintaining a coherent theme to the package, balanced with 
download and install size, fitting with the desires and suggestions of 
the community.


  3. Testing of a Package

The package maintainer is responsible for testing the package. The 
package maintainer should arrange for a number of committers and 
community members to act as testers. The type and degree of testing may 
vary but is expected to at least confirm that all the projects basically 
work together with no immediate problems introduced by being packaged 
together. In all cases the type of testing and test cases should be 
documented. EPP will define a process for each package maintainer to 
identify that the package has been tested, the type of testing and that 
the package is ready for download.


  4. Publishing of Packages

A new web site will be created to publish the different packages. This 
new web site will be directly accessible from the download page. The 
packaging page will show all the available packages and use social 
networking techniques to influence the order and display of the 
packages. For instance, the number of time a package is download will be 
visible, the names of the project maintainers and testers will be 
associated with the project or maybe individuals can vote/recommend a 
package. The Eclipse Foundation will also continue to list 4-5 packages 
directly on the download page.


How to Get Started?

If you would like to create a package, we ask that you open a bugzilla 
request for EPP, using the ‘package content’ component. In the bugzilla 
bug, please specify a description of the package you would like to 
create, including the intended targeted user and the feature set of the 
package. You will then need to create a package configuration file 
together with the EPP team and then specify the location of the file. 
You will then need to create an package configuration file and then 
specify the location of the file. Please add this location to the 
bugzilla request. EPP builds the packages on a nightly basis, so once 
your package is defined, we will start building it.


EPP is also releasing packages for each milestone and release candidate 
for Ganymede. If you would like your package to be built for M5, we ask 
that you please have it defined before February 11.


We are just starting this process so your feedback and support is 
welcome. It will take sometime to make it perfect but the intention is 
to have a number of packages available in time for the Ganymede release.


Thanks for your support,

Ian Skerrett

Director of Marketing

Eclipse Foundation

613-224-9461 ext. 227

blog: ianskerrett.wordpress.com .wordpress

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


[equinox-dev] Movin' on

2008-01-24 Thread Jeff McAffer

In case you do not read my blog or PlanetEclipse...
   http://dev.eclipse.org/blogs/jeff/2008/01/24/movin-on-well-sorta/

One thing to add the message is my new coordinates.  My new email 
address is first name at code9.com (the source of this message).


Note also that my bugzilla id will change as well.  Though not finalized 
yet, it will likely be [EMAIL PROTECTED]


See ya around.

Jeff

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


Re: [equinox-dev] [prov] Download manager support for pack200

2008-01-24 Thread Jim Colson
how would that work on J2ME (CDC/Foundatoin)?



Jim Colson, Chief Architect - IBM Client Software
Distinguished Engineer
IBM Academy of Technology
Board Member - IT Architect Certification

11501 Burnet Rd. Austin, TX 78758
Ph 512-823-7357, Fax 512-838-0962
email: [EMAIL PROTECTED]

Admin:  Sandra Wallis 512-838-3241
email:  [EMAIL PROTECTED]




   
  From:   Pascal Rapicault [EMAIL PROTECTED]  
 

   
  To: Equinox development mailing list equinox-dev@eclipse.org
   

   
  Date:   01/24/2008 08:11 PM   
   

   
  Subject:[equinox-dev] [prov] Download manager support for pack200 
   

   






I seem to remember that someone was working on adding to support to our
download manager to favor downloading pack200'ed artifacts over canonical
ones.
Did that ever made it into the code?

Thx

PaScaL

___
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] Creating Eclipse Packages

2008-01-24 Thread Pascal Rapicault
From the discussion we have had with Markus from the EPP project
(http://wiki.eclipse.org/Equinox_p2_Meeting_Week_Jan_14-18_2008#Ganymede.2C_EPP),
 it seems that the package configuration file EPP takes as input contains
almost everything p2 needs to generate the product IU.
We will quickly see if everything needed is there since we are hoping to be
able to produce an installer for one or two packages for the M5 build of
Ganymede.

PaScaL



|
| From:  |
|
  
|
  |Jeff McAffer [EMAIL PROTECTED] 
  |
  
|
|
| To:|
|
  
|
  |equinox-dev@eclipse.org  
   |
  
|
|
| Date:  |
|
  
|
  |01/24/2008 12:20 PM  
   |
  
|
|
| Subject:   |
|
  
|
  |[equinox-dev] [prov] Creating Eclipse Packages   
   |
  
|







 From Ian in the committer list. There might be some input needed here
from p2 if we are going to produce installers etc.

Jeff

Dear Eclipse Committers

We would like to encourage more participation in the creation of the
packages created by the Eclipse Packaging Project. The goal is to 1)
encourage more cross-project testing of the existing four packages, and
2) encourage the creation of packages in addition to the existing four
that were created last year. A framework for doing this was discussed at
a recent Planning Council meeting
http://wiki.eclipse.org/Planning_Council_Minutes_2007.11.06#Packages
and this document is to provide addition details.

   1. Creation of a Package

To create a package a project leader or committer must agree to be a
package maintainer. The package maintainer is responsible for defining
the contents of the package and arrange for testing of the package.

To define a package the package maintainer will need to specify the
package contents based on the EPP package configuration file format
http://wiki.eclipse.org/EPP/Configuration_File_Format. The package
maintainer will need to store this file in their cvs repository and then
inform the EPP team, via a bugzilla entry, the location of the file. The
EPP team will then begin to automatically build the package based on the
config file.

   2. What can be included in a Package?

· Packages must only contain code from Eclipse projects

· Packages should usually only contain code from projects that have
passed their 1.0 creation review, and if exceptions are found, the code
must still have passed an Eclipse Release Review.

· Packages should attempt to include code from a variety of projects,
while maintaining a coherent theme to the package, balanced with
download and install size, fitting with the desires and suggestions of
the community.

   3. Testing of a Package

The package maintainer is responsible for testing the package. The
package maintainer should arrange for a number of committers and
community members to act as testers. The type and degree of testing may
vary but is expected to at least confirm that all the projects basically
work together with no immediate problems introduced by being packaged
together. In all cases the type of testing and test cases should be
documented. EPP will define a process for each package maintainer to
identify that the package has been tested, the type of testing and that
the package is ready for download.

   4. Publishing of Packages

A new web site will be created to publish the different packages. This
new web 

Re: [equinox-dev] [prov] Download manager support for pack200

2008-01-24 Thread John Arthorne
The only support I know is in MirrorRequest#perform, but it is quite 
rudimentary. Essentially if the repository is local, it prefers a 
descriptor in canonical form (not packed/zipped), and if the repository is 
remote it prefers a descriptor in non-canonical form. It doesn't have any 
further smarts about which non-canonical form is available. Also, the 
pack200 processing step does a check for the unpack200 executable so it 
will quickly abort if unpacking is not available on the client.





Pascal Rapicault/Ottawa/[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
01/24/2008 09:14 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org


To
Equinox development mailing list equinox-dev@eclipse.org
cc

Subject
[equinox-dev] [prov] Download manager support for pack200







I seem to remember that someone was working on adding to support to our
download manager to favor downloading pack200'ed artifacts over canonical
ones.
Did that ever made it into the code?

Thx

PaScaL

___
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] Download manager support for pack200

2008-01-24 Thread Jeff McAffer
right but there is the practical detail that the exe you need comes with 
Java 5 or later and the licensing does not likely allow you to ship just 
the unpack200 exe.  But that is a matter for someone's legal team.  As 
John says, the unpack support simply cares whether or not the exe is 
there. 

What we really need is an open source implementation of unpack that runs 
on/with Foundation...


Jeff


John Arthorne wrote:


Just to clarify, the JRE level doesn't matter here. Unpack is 
performed by a standalone unpack200 executable that doesn't require 
presence of a JVM.  You can run with a Foundation class library, plus 
a standalone unpack200 executable from Java 5 or Java 6.




*Jim Colson [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]

01/24/2008 09:18 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org



To
Equinox development mailing list equinox-dev@eclipse.org
cc
	Equinox development mailing list equinox-dev@eclipse.org, 
[EMAIL PROTECTED]

Subject
Re: [equinox-dev] [prov] Download manager support for pack200









how would that work on J2ME (CDC/Foundatoin)?



Jim Colson, Chief Architect - IBM Client Software
Distinguished Engineer
IBM Academy of Technology
Board Member - IT Architect Certification

11501 Burnet Rd. Austin, TX 78758
Ph 512-823-7357, Fax 512-838-0962
email: [EMAIL PROTECTED]

Admin:  Sandra Wallis 512-838-3241
email:  [EMAIL PROTECTED]



  
   
 From:   Pascal Rapicault [EMAIL PROTECTED]   
   
  
   
 To: Equinox development mailing list 
equinox-dev@eclipse.org 
 
  
   
 Date:   01/24/2008 08:11 PM   
   
  
   
 Subject:[equinox-dev] [prov] Download manager support for pack200 
   
  
   







I seem to remember that someone was working on adding to support to our
download manager to favor downloading pack200'ed artifacts over canonical
ones.
Did that ever made it into the code?

Thx

PaScaL

___
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