| RE: [higgins-dev] Code Changes |
|
I think removing
everything and leaving a readme is a good idea for now. From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim This is an
example of why I need to tie up these loose ends. There should not be an
"org.eclipse.higgins.idas" project. No one should be using it
anymore. Even though I sent the mail to the dev list announcing this, I
need to do something to cause it to not work at all anymore -- maybe removing
everything and leaving a readme which explains where the new projects are. Note that the
instructions at http://wiki.eclipse.org/index.php/Components#Identity_Attribute_Service_and_Context_Providers are
current. CVS repositories are listed at: Jim I strongly
request we wait to freeze until there we have a consistent set of sources that
build. I've been keeping up to date with the sources and there seem to be
inconistencies. For example the current issue I'm looking into is: there
are references to "org.eclipse.higgins.idas.spi"
from files in the "org.eclipse.higgins.idas"
project, but I don't see where the "...spi"
package is defined. Brian From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim So, I do have one
question regarding this. Some time back I
finished refactoring the package names / projects for IdAS. I still have
some outstanding tasks in that area: 1) Remove the
code / project files from the old IdAS repository location. 2) Make new
projects work with the nightly build. Should I also
perform these project/build related tasks in a fork and merge back to the
regular dev head after the 25th? I
would like to propose that all non-bug related changes be held or forked until
after June 25, thus putting a freeze on current code before the Burton Interop,
as we don't want to spend resources chasing bugs that changes might cause, and
we would resume normal processes after June 25th ********************************************************************** This
email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. Any
unauthorized review, use, disclosure or distribution is prohibited. If you are
not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. ********************************************************************** |