jwt-dev http://dev.eclipse.org/mhonarc/lists/jwt-dev/maillist.html jwt-dev en-us Tue, 22 May 2012 15:40:07 GMT Tue, 22 May 2012 15:40:07 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) jwt-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/jwt-dev/maillist.html Re: [jwt-dev] Interested in Apache Chemistry, currently in IP process http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01595.html Hi Marc, This is the first that I have heard of these CQs being needed for Juno.  The February 3, 2012 deadline for Projects to let us know what CQs are needed for Juno is a critical part of our planning process.  The last thing we want is for situations s...

Hi Marc,

 

This is the first that I have heard of these CQs being needed for Juno.  The February 3, 2012 deadline for Projects to let us know what CQs are needed for Juno is a critical part of our planning process.  The last thing we want is for situations such as this to arise.   Unfortunately, we won’t be able to complete the review of these CQs for tomorrow.  I would like to understand however, why they weren’t flagged earlier in the year as needed for the simultaneous release.   We’ll use this feedback to improve the process for next year. 

 

With respect to the workflow, if something isn’t working correctly or you think that there is an improvement that can be made, please open a bug in bugzilla.  We’re always open to ideas for improvement, recognizing we are also highly resource constrained.

 

Regards,

Janet

 

---------------------

Janet Campbell

Director, Intellectual Property

Secretary and Legal Counsel

Eclipse Foundation, Inc.

 

From: Marc Dutoo [mailto:marc.dutoo@xxxxxxxxxxx]
Sent: Tuesday, May 22, 2012 10:25 AM
To: emo-ip-team@xxxxxxxxxxx; sharon.corbett@xxxxxxxxxxx
Cc: Campo, Christian; Thierry Delprat; Mos, Adrian; Java Workflow Tooling; Stéphane Drapeau; Thomas Watson; Jochen Krause
Subject: Re: AW: Interested in Apache Chemistry, currently in IP process

 

To the IP-team :
alas I guess it means we won't release our code depending on it in Juno ??
By the way, I've found that sometimes you've had to change "CQ to state "new" in order for workflow to flow accurately", see https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2698 ...

To Christian (and Jochen) :
thanks a lot for the good news & redirection !

Best regards,
Marc Dutoo
Eclipse SOA JWT co-lead

Le 21/05/2012 15:49, Campo, Christian a écrit :

The CQs have been PMC approved from michael keith in the CQ. Not sure why the IP process is not moving forward….

 

IP-Team ?

 

Von: Jochen Krause [mailto:jkrause@xxxxxxxxxxxxxxxxx]
Gesendet: Montag, 21. Mai 2012 15:42
An: Marc Dutoo
Cc: Thierry Delprat; Mos, Adrian; Java Workflow Tooling; gunnar@xxxxxxxxxxxxxxx; jesse.mcconnell@xxxxxxxxx; Stéphane Drapeau; Thomas Watson; Campo, Christian
Betreff: Re: Interested in Apache Chemistry, currently in IP process

 

Hi Marc,

Sorry to hear that the PMC approval is taking longer than usual. I don't have any background information as I have stepped down from the PMC about a year ago.

The new leaders of the Eclipse RT PMC are Thomas Watson and Christian Campo, I copied both of them on this message.

Best Regards,

Jochen Krause

On Wed, May 16, 2012 at 11:44 AM, Marc Dutoo <marc.dutoo@xxxxxxxxxxx> wrote:

Greetings dear RT PMC leaders and members

First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried.

Making it short (*) :

At Eclipse JWT, we've developed a first version of integration with ECM (Entreprise Content Management), that we wanted to put in the Juno yearly release.
However it uses the Apache Chemistry CMIS ECM client library, which is currently in "waiting for PMC approval" phase of the IP process of Eclipse RT Apricot since February :

http://www.eclipse.org/projects/ip_log.php?projectid=rt.apricot
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6170
(and up to 6178)

I know that it's pretty unreasonable of me to expect anything at this point, being this late in the game, but still could there be any chance for it to be approved before May the 23rd (for Juno) ??

Best regards,
Marc Dutoo
Open Wide
Eclipse SOA Java Workflow Tooling co-lead

(*) The long version :

We're actually Nuxeo partners, which is why I knew that Nuxeo had contributed Apricot, and somehow believed (wrongly) that its dependencies would be OK in Eclipse.

So I've talked it up with Thierry Delprat, Nuxeo CTO. Then I've tried to send an email to the RT PMC mailing list 2 weeks ago, but I didn't see until now that it had bounced (being on holidays).

Finally I had a word with Adrian Mos, SOA PMC rep to the Architecture Council, about sending such a mail to a few of RT PMC leaders and members.

And even if you can't do it for Juno, rest assured that there is a rising level of interest in Eclipse SOA for it, according to those recent discussions with Adrian but also Stephane Drapeau of Eclipse SCA !




-- 


EclipseSource Group
Lammstr 21, 76133 Karlsruhe Germany 
Telefon: +49 721 664733-0
Telefax: +49 721 66473329
 
http://eclipsesource.com
 
 

 

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main

fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de


Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------

 

]]> Tue, 22 May 2012 15:34:34 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01595.html janet.campbell@xxxxxxx (Janet Campbell) Re: [jwt-dev] Interested in Apache Chemistry, currently in IP process http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01594.html Hi Christian, I&#8217;ve had a quick look at the CQ for you.&#xA0; &#xA0;In reviewing the history, it appears that an automated request for PMC approval was requested February 1, 2012, and that Michael Keith responded by setting the PMC approval flag the same day.&#xA0; Furthe...

Hi Christian,

 

I’ve had a quick look at the CQ for you.   In reviewing the history, it appears that an automated request for PMC approval was requested February 1, 2012, and that Michael Keith responded by setting the PMC approval flag the same day.  Further action has not yet been taken by the IP Team (currently Sharon Corbett and myself) as we are focused on requirements that have been identified as needed for the Juno release. 

 

The good news is that the bulk of this work is now done, with a few remaining requirements left to be completed.   We will then be in a position to look requirements for Projects that are not participating in the Juno release.   The bad news is that we will not be able to complete this CQ for tomorrow in light of current work on our plate.   We ask for your patience as we try to work through the backlog of requirements that have accumulated while we focused on Juno.   Also, in order to better meet the needs of the community and increase our turnaround time, we expect to be hiring an additional person to the IP Team in the coming months.

 

If you have any additional questions, please let me know.

 

Regards,

Janet

 

---------------------

Janet Campbell

Director, Intellectual Property

Secretary and Legal Counsel

Eclipse Foundation, Inc.

 

From: Campo, Christian [mailto:Christian.Campo@xxxxxxxxxxxx]
Sent: Monday, May 21, 2012 9:49 AM
To: emo-ip-team@xxxxxxxxxxx; sharon.corbett@xxxxxxxxxxx
Cc: Thierry Delprat; Mos, Adrian; Java Workflow Tooling; gunnar@xxxxxxxxxxxxxxx; jesse.mcconnell@xxxxxxxxx; Stéphane Drapeau; Thomas Watson; Marc Dutoo; Jochen Krause
Subject: AW: Interested in Apache Chemistry, currently in IP process
Importance: High

 

The CQs have been PMC approved from michael keith in the CQ. Not sure why the IP process is not moving forward….

 

IP-Team ?

 

Von: Jochen Krause [mailto:jkrause@xxxxxxxxxxxxxxxxx]
Gesendet: Montag, 21. Mai 2012 15:42
An: Marc Dutoo
Cc: Thierry Delprat; Mos, Adrian; Java Workflow Tooling; gunnar@xxxxxxxxxxxxxxx; jesse.mcconnell@xxxxxxxxx; Stéphane Drapeau; Thomas Watson; Campo, Christian
Betreff: Re: Interested in Apache Chemistry, currently in IP process

 

Hi Marc,

Sorry to hear that the PMC approval is taking longer than usual. I don't have any background information as I have stepped down from the PMC about a year ago.

The new leaders of the Eclipse RT PMC are Thomas Watson and Christian Campo, I copied both of them on this message.

Best Regards,

Jochen Krause

On Wed, May 16, 2012 at 11:44 AM, Marc Dutoo <marc.dutoo@xxxxxxxxxxx> wrote:

Greetings dear RT PMC leaders and members

First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried.

Making it short (*) :

At Eclipse JWT, we've developed a first version of integration with ECM (Entreprise Content Management), that we wanted to put in the Juno yearly release.
However it uses the Apache Chemistry CMIS ECM client library, which is currently in "waiting for PMC approval" phase of the IP process of Eclipse RT Apricot since February :

http://www.eclipse.org/projects/ip_log.php?projectid=rt.apricot
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6170
(and up to 6178)

I know that it's pretty unreasonable of me to expect anything at this point, being this late in the game, but still could there be any chance for it to be approved before May the 23rd (for Juno) ??

Best regards,
Marc Dutoo
Open Wide
Eclipse SOA Java Workflow Tooling co-lead

(*) The long version :

We're actually Nuxeo partners, which is why I knew that Nuxeo had contributed Apricot, and somehow believed (wrongly) that its dependencies would be OK in Eclipse.

So I've talked it up with Thierry Delprat, Nuxeo CTO. Then I've tried to send an email to the RT PMC mailing list 2 weeks ago, but I didn't see until now that it had bounced (being on holidays).

Finally I had a word with Adrian Mos, SOA PMC rep to the Architecture Council, about sending such a mail to a few of RT PMC leaders and members.

And even if you can't do it for Juno, rest assured that there is a rising level of interest in Eclipse SOA for it, according to those recent discussions with Adrian but also Stephane Drapeau of Eclipse SCA !




-- 

EclipseSource Group
Lammstr 21, 76133 Karlsruhe Germany 
Telefon: +49 721 664733-0
Telefax: +49 721 66473329

http://eclipsesource.com
 

 

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main

fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de


Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------

]]> Tue, 22 May 2012 14:35:02 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01594.html janet.campbell@xxxxxxx (Janet Campbell) Re: [jwt-dev] Interested in Apache Chemistry, currently in IP process http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01593.html To the IP-team : alas I guess it means we won't release our code depending on it in Juno ?? By the way, I've found that sometimes you've had to change "CQ to state "new" in order for workflow to flow accurately", see https://dev.eclipse.org/ipzilla/show_b... To the IP-team :
alas I guess it means we won't release our code depending on it in Juno ??
By the way, I've found that sometimes you've had to change "CQ to state "new" in order for workflow to flow accurately", see https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2698 ...

To Christian (and Jochen) :
thanks a lot for the good news & redirection !

Best regards,
Marc Dutoo
Eclipse SOA JWT co-lead

Le 21/05/2012 15:49, Campo, Christian a écrit :

The CQs have been PMC approved from michael keith in the CQ. Not sure why the IP process is not moving forward….

 

IP-Team ?

 

Von: Jochen Krause [mailto:jkrause@xxxxxxxxxxxxxxxxx]
Gesendet: Montag, 21. Mai 2012 15:42
An: Marc Dutoo
Cc: Thierry Delprat; Mos, Adrian; Java Workflow Tooling; gunnar@xxxxxxxxxxxxxxx; jesse.mcconnell@xxxxxxxxx; Stéphane Drapeau; Thomas Watson; Campo, Christian
Betreff: Re: Interested in Apache Chemistry, currently in IP process

 

Hi Marc,

Sorry to hear that the PMC approval is taking longer than usual. I don't have any background information as I have stepped down from the PMC about a year ago.

The new leaders of the Eclipse RT PMC are Thomas Watson and Christian Campo, I copied both of them on this message.

Best Regards,

Jochen Krause

On Wed, May 16, 2012 at 11:44 AM, Marc Dutoo <marc.dutoo@xxxxxxxxxxx> wrote:

Greetings dear RT PMC leaders and members

First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried.

Making it short (*) :

At Eclipse JWT, we've developed a first version of integration with ECM (Entreprise Content Management), that we wanted to put in the Juno yearly release.
However it uses the Apache Chemistry CMIS ECM client library, which is currently in "waiting for PMC approval" phase of the IP process of Eclipse RT Apricot since February :

http://www.eclipse.org/projects/ip_log.php?projectid=rt.apricot
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6170
(and up to 6178)

I know that it's pretty unreasonable of me to expect anything at this point, being this late in the game, but still could there be any chance for it to be approved before May the 23rd (for Juno) ??

Best regards,
Marc Dutoo
Open Wide
Eclipse SOA Java Workflow Tooling co-lead

(*) The long version :

We're actually Nuxeo partners, which is why I knew that Nuxeo had contributed Apricot, and somehow believed (wrongly) that its dependencies would be OK in Eclipse.

So I've talked it up with Thierry Delprat, Nuxeo CTO. Then I've tried to send an email to the RT PMC mailing list 2 weeks ago, but I didn't see until now that it had bounced (being on holidays).

Finally I had a word with Adrian Mos, SOA PMC rep to the Architecture Council, about sending such a mail to a few of RT PMC leaders and members.

And even if you can't do it for Juno, rest assured that there is a rising level of interest in Eclipse SOA for it, according to those recent discussions with Adrian but also Stephane Drapeau of Eclipse SCA !




-- 

EclipseSource Group
Lammstr 21, 76133 Karlsruhe Germany 
Telefon: +49 721 664733-0
Telefax: +49 721 66473329

http://eclipsesource.com


 

 

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------

]]> Tue, 22 May 2012 14:25:28 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01593.html marc.dutoo@xxxxxxx (Marc Dutoo) Re: [jwt-dev] Interested in Apache Chemistry, currently in IP process http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01592.html - just to say that, if it doesn't work for the 23rd, we'd still be hoping for July (for Eclipse Con Europe). Best regards, Marc Le 16/05/2012 11:44, Marc Dutoo a &#xE9;crit : - just to say that, if it doesn't work for the 23rd, we'd still be hoping for July (for Eclipse Con Europe).

Best regards,
Marc

Le 16/05/2012 11:44, Marc Dutoo a écrit : 
Greetings dear RT PMC leaders and members

First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried.

Making it short (*) :

At Eclipse JWT, we've developed a first version of integration with ECM (Entreprise Content Management), that we wanted to put in the Juno yearly release.
However it uses the Apache Chemistry CMIS ECM client library, which is currently in "waiting for PMC approval" phase of the IP process of Eclipse RT Apricot since February :

http://www.eclipse.org/projects/ip_log.php?projectid=rt.apricot
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6170
(and up to 6178)

I know that it's pretty unreasonable of me to expect anything at this point, being this late in the game, but still could there be any chance for it to be approved before May the 23rd (for Juno) ??

Best regards,
Marc Dutoo
Open Wide
Eclipse SOA Java Workflow Tooling co-lead

(*) The long version :

We're actually Nuxeo partners, which is why I knew that Nuxeo had contributed Apricot, and somehow believed (wrongly) that its dependencies would be OK in Eclipse.

So I've talked it up with Thierry Delprat, Nuxeo CTO. Then I've tried to send an email to the RT PMC mailing list 2 weeks ago, but I didn't see until now that it had bounced (being on holidays).

Finally I had a word with Adrian Mos, SOA PMC rep to the Architecture Council, about sending such a mail to a few of RT PMC leaders and members.

And even if you can't do it for Juno, rest assured that there is a rising level of interest in Eclipse SOA for it, according to those recent discussions with Adrian but also Stephane Drapeau of Eclipse SCA !


]]> Mon, 21 May 2012 13:27:20 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01592.html marc.dutoo@xxxxxxx (Marc Dutoo) [jwt-dev] Interested in Apache Chemistry, currently in IP process http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01591.html Greetings dear RT PMC leaders and members First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried. Making it short (*) : At Eclipse JWT, we've develope... Greetings dear RT PMC leaders and members
First, sorry for coming out of the blue with this email. I'm not sure I shouldn't be doing it otherwise, but I haven't found a better channel, though I've tried.

Making it short (*) :

At Eclipse JWT, we've developed a first version of integration with ECM (Entreprise Content Management), that we wanted to put in the Juno yearly release.
However it uses the Apache Chemistry CMIS ECM client library, which is currently in "waiting for PMC approval" phase of the IP process of Eclipse RT Apricot since February :

http://www.eclipse.org/projects/ip_log.php?projectid=rt.apricot
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6170
(and up to 6178)

I know that it's pretty unreasonable of me to expect anything at this point, being this late in the game, but still could there be any chance for it to be approved before May the 23rd (for Juno) ??

Best regards,
Marc Dutoo
Open Wide
Eclipse SOA Java Workflow Tooling co-lead

(*) The long version :

We're actually Nuxeo partners, which is why I knew that Nuxeo had contributed Apricot, and somehow believed (wrongly) that its dependencies would be OK in Eclipse.

So I've talked it up with Thierry Delprat, Nuxeo CTO. Then I've tried to send an email to the RT PMC mailing list 2 weeks ago, but I didn't see until now that it had bounced (being on holidays).

Finally I had a word with Adrian Mos, SOA PMC rep to the Architecture Council, about sending such a mail to a few of RT PMC leaders and members.

And even if you can't do it for Juno, rest assured that there is a rising level of interest in Eclipse SOA for it, according to those recent discussions with Adrian but also Stephane Drapeau of Eclipse SCA !

]]> Wed, 16 May 2012 09:44:22 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01591.html marc.dutoo@xxxxxxx (Marc Dutoo) Re: [jwt-dev] makeing dependencies optional http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01590.html Hi, you are right, just making them optional would probably introduce some problems. It therefore should be checked whether certain dependencies are available and functions accordingly disabled. This should also be clearly indicated to the user. I've creat... Hi,
you are right, just making them optional would probably introduce some problems. It therefore should be checked whether certain dependencies are available and functions accordingly disabled. This should also be clearly indicated to the user.

I've created a bug for this (1.3.0:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=379526

Regards,
Chris

Am 09.05.2012 11:06, schrieb Yoann Rodière: 
Hi,

I agree this would be great for those users who want a light-weight
platform, but it may require more attention than just modifying the
manifest file, I guess. I'm assuming you were talking about adding the
"optional" keyword to dependencies in the manifest file. With the
current code, I think JWT would simply blow up if we tried to use SVG
export with, say, batik not installed. Two solutions:

 1. Assume that users who have these dependencies not installed know
    what they do.
 2. Make sure to (programatically) disable the features related to these
    dependencies if they're not installed.

I wonder what form this "optional OSGi dependency" will take, especially
regarding the Eclipse Update Manager.

 1. Will it install all dependencies by default, and allow users to
    remove thoses they don't want?
 2. Will it NOT install the optional dependencies and therefore require
    active actions from the user in order to install them?

In the second case, we definitely should disable SVG export when the
required dependencies are not available. It seems a common way doing
this is by using OSGi services (I only searched quickly and found this
<http://www.developer.com/java/ent/article.php/3655231/Eclipse-Tip-Use-Optional-Plug-in-Dependencies-to-Support-Diverse-Runtime-Environments.htm>)

Of course, we could also avoid using the OSGi "optional dependency"
mechanism, and simply relocate the diagram export features in a new
bundle, which would use extension points. Users could choose explicitly
to install it when installing JWT in the Update manager. This would
involve a bit more work, though.

Let me know if I'm missing something :)

Regards,
Yoann

Le mar. 08 mai 2012 18:09:57 CEST, Christian Saad a écrit :
 > Hi Marc, Yoann,
 >
 > playing around a lot with Eclipse and JWT (and several other
 > Eclipse-based products) recently I've discovered that it might not in
 > all cases be desirable to force users to install very heavyweight
 > components such as GMF that themselves drag along many dependencies,
 > especially since we emphasize the customisability aspect of our
 > platform. Therefore, I would propose to mark the GMF dependencies (and
 > in the future maybe other components such as ATL/JDT?) in jwt-we
 > (shown below) as optional, so that the user can choose whether to
 > install the product and enjoy a fully featured solution or to work
 > with a restricted feature set but have a more light-weight platform.
 > What do you think?
 >
 > Regards,
 > Chris
 >
 > org.apache.batik.util;bundle-version="1.6.0",
 > org.apache.batik.dom;bundle-version="1.6.0",
 > org.apache.batik.dom.svg;bundle-version="1.6.0",
 > org.apache.batik.svggen;bundle-version="1.6.0",
 > org.apache.batik.ext.awt;bundle-version="1.6.0",
 > org.eclipse.gmf.runtime.common.ui;bundle-version="1.5.0",
 > org.eclipse.gmf.runtime.draw2d.ui;bundle-version="1.5.0",
 > org.eclipse.gmf.runtime.draw2d.ui.render;bundle-version="1.4.1",
 > org.w3c.dom.svg;bundle-version="1.1.0"

]]> Tue, 15 May 2012 10:34:59 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01590.html christian.saad@xxxxxxx (Christian Saad) Re: [jwt-dev] Welcome Yoann RodiÃÂre as a new soa.jwt Committer http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01589.html Thanks everyone! I'll make sure to give the best to this project ;) I am going to release my current work on a new branch on JWT's SVN by the end of next week. It's mainly about synchronizing JWT's model with an ECM. It's really only prototype, partially f... Thanks everyone! I'll make sure to give the best to this project ;)
I am going to release my current work on a new branch on JWT's SVN by the end of next week. It's mainly about synchronizing JWT's model with an ECM. It's really only prototype, partially functional, and the architecture is very likely to change radically, but you'll be able to take a look if you want to :)

Best regards,
Yoann

Le jeu. 10 mai 2012 16:15:02 CEST, portal on behalf of Marc Dutoo a Ãcrit : 
soa.jwt Committers,
This automatically generated message marks the completion of all the legal
paperwork and webmaster provisioning for Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re=2E?= Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re?= is
a new full Committer on the soa.jwt project.

Welcome!
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

]]> Fri, 11 May 2012 08:26:05 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01589.html yoann.rodiere@xxxxxxx (Yoann RodiÃre) [jwt-dev] Welcome Yoann RodiÃÂre as a new soa.jwt Committer http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01588.html soa.jwt Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re=2E?= Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re?= is a new full Committer on the soa.jwt proj... soa.jwt Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re=2E?= Yoann =?UTF-8?Q?Rodi=C3=83=C2=A8re?= is a new full Committer on the soa.jwt project. Welcome! ]]> Thu, 10 May 2012 14:15:02 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01588.html marc.dutoo@xxxxxxx (portal on behalf of Marc Dutoo) Re: [jwt-dev] makeing dependencies optional http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01587.html Hi, I agree this would be great for those users who want a light-weight platform, but it may require more attention than just modifying the manifest file, I guess. I'm assuming you were talking about adding the "optional" keyword to dependencies in the ma... Hi,

I agree this would be great for those users who want a light-weight platform, but it may require more attention than just modifying the manifest file, I guess. I'm assuming you were talking about adding the "optional" keyword to dependencies in the manifest file. With the current code, I think JWT would simply blow up if we tried to use SVG export with, say, batik not installed. Two solutions:
  1. Assume that users who have these dependencies not installed know what they do.
  2. Make sure to (programatically) disable the features related to these dependencies if they're not installed. 
I wonder what form this "optional OSGi dependency" will take, especially regarding the Eclipse Update Manager.
  1. Will it install all dependencies by default, and allow users to remove thoses they don't want?
  2. Will it NOT install the optional dependencies and therefore require active actions from the user in order to install them?
In the second case, we definitely should disable SVG export when the required dependencies are not available. It seems a common way doing this is by using OSGi services (I only searched quickly and found this)

Of course, we could also avoid using the OSGi "optional dependency" mechanism, and simply relocate the diagram export features in a new bundle, which would use extension points. Users could choose explicitly to install it when installing JWT in the Update manager. This would involve a bit more work, though.

Let me know if I'm missing something :)

Regards,
Yoann

Le mar. 08 mai 2012 18:09:57 CEST, Christian Saad a écrit :
> Hi Marc, Yoann,
>
> playing around a lot with Eclipse and JWT (and several other
> Eclipse-based products) recently I've discovered that it might not in
> all cases be desirable to force users to install very heavyweight
> components such as GMF that themselves drag along many dependencies,
> especially since we emphasize the customisability aspect of our
> platform. Therefore, I would propose to mark the GMF dependencies (and
> in the future maybe other components such as ATL/JDT?) in jwt-we
> (shown below) as optional, so that the user can choose whether to
> install the product and enjoy a fully featured solution or to work
> with a restricted feature set but have a more light-weight platform.
> What do you think?
>
> Regards,
> Chris
>
> org.apache.batik.util;bundle-version="1.6.0",
> org.apache.batik.dom;bundle-version="1.6.0",
> org.apache.batik.dom.svg;bundle-version="1.6.0",
> org.apache.batik.svggen;bundle-version="1.6.0",
> org.apache.batik.ext.awt;bundle-version="1.6.0",
> org.eclipse.gmf.runtime.common.ui;bundle-version="1.5.0",
> org.eclipse.gmf.runtime.draw2d.ui;bundle-version="1.5.0",
> org.eclipse.gmf.runtime.draw2d.ui.render;bundle-version="1.4.1",
> org.w3c.dom.svg;bundle-version="1.1.0" ]]> Wed, 09 May 2012 09:06:11 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01587.html yoann.rodiere@xxxxxxx (Yoann Rodière) [jwt-dev] makeing dependencies optional http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01586.html Hi Marc, Yoann, playing around a lot with Eclipse and JWT (and several other Eclipse-based products) recently I've discovered that it might not in all cases be desirable to force users to install very heavyweight components such as GMF that themselves drag... Hi Marc, Yoann,
playing around a lot with Eclipse and JWT (and several other Eclipse-based products) recently I've discovered that it might not in all cases be desirable to force users to install very heavyweight components such as GMF that themselves drag along many dependencies, especially since we emphasize the customisability aspect of our platform. Therefore, I would propose to mark the GMF dependencies (and in the future maybe other components such as ATL/JDT?) in jwt-we (shown below) as optional, so that the user can choose whether to install the product and enjoy a fully featured solution or to work with a restricted feature set but have a more light-weight platform. What do you think?

Regards,
Chris

 org.apache.batik.util;bundle-version="1.6.0",
 org.apache.batik.dom;bundle-version="1.6.0",
 org.apache.batik.dom.svg;bundle-version="1.6.0",
 org.apache.batik.svggen;bundle-version="1.6.0",
 org.apache.batik.ext.awt;bundle-version="1.6.0",
 org.eclipse.gmf.runtime.common.ui;bundle-version="1.5.0",
 org.eclipse.gmf.runtime.draw2d.ui;bundle-version="1.5.0",
 org.eclipse.gmf.runtime.draw2d.ui.render;bundle-version="1.4.1",
 org.w3c.dom.svg;bundle-version="1.1.0"

]]> Tue, 08 May 2012 16:08:37 GMT http://dev.eclipse.org/mhonarc/lists/jwt-dev/msg01586.html christian.saad@xxxxxxx (Christian Saad)