Looks fine
to me.
-----Original Message-----
From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Thursday, July 13, 2006 4:51
PM
To: 'Higgins (Trust Framework)
Project developer discussions'
Subject: RE: [higgins-dev]
Project/package for IdAS
Ok, I've done the commit. Can you take a look to see if
I've done anything obviously wrong?
Jim
>>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 7/13/06
1:25 PM >>>
Jim,
The
org.eclipse.higgins.idas project is now empty no longer used. It can now
be the new location for the new IdAS plug-in/project.
-Paul
-----Original Message-----
From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Tuesday, July 11, 2006 7:57
PM
To: 'Higgins (Trust Framework)
Project developer discussions'
Subject: RE: [higgins-dev]
Project/package for IdAS
Also, If it's standalone, and ultimately a replacement, I
assume it doesn't need to co-exist with the old idas. This means that within
the project, we could go ahead and use the package name
"org.eclipse.higgins.idas" (even though the plugin folder name is
org.eclipse.higgins.idas2). Or are there issues I'm not aware of that would
prevent this?
>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 7/11/06 5:50
PM >>>
So you mean you recommend #1
>>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 7/11/06
3:00 PM >>>
Jim wrote:
We discussed the best place to start adding the new IdAS
interfaces, but I have a question about that. I see two potential places:
1) A project below plugins called
org.eclipse.higgins.idas2 (because there's already the original
org.eclipse.higgins.idas project there.
2) Use the existing project below plugins called
org.eclipse.higgins, and just add a new package under src
(org/eclipse/higgins/idas). I think the most current IdAS-like interfaces are
there in org/eclipse/higgins/core.
I assume you had a reason for not doing #2, but I'm not
sure what it was (other than the notion of starting with a clean slate). Let me
know if #1 is still the better option.
I recommend
#2 because it will allow easier parallel development work (continued building
on proto-IdAS) and new work on the "real" IdAS. Once the new IdAS is
mature enough we can create new Context Providers, one by one, from our
existing providers. That way we can continue development work that relies on
the old/existing proto-IdAS, (e.g. the i-card broker app, etc.) without
introducing any new ripple effects that come from the rapidly maturing new
IdAS. Another reason is that the new IdAS is intended to be used standalone. So
starting it off as its own idas2 plug-in project will make this easier to keep
in focus.
|