UFaceKit@Eclipse - Update

1 view
Skip to first unread message

Tom

unread,
Dec 17, 2008, 5:48:59 AM12/17/08
to uface
Hi,

Just an update for all people listen to this google-group and what is
happening in the next week(s).

a) The proposal was accepted (I already posted about this)

b) The project and it's homepage are up (http://www.eclipse.org/
ufacekit/) there's not much there yet and we need to
fill it with content in the next weeks. A first step would be if
all committer send me a picture so I could make a
Team-Page.

c) Yesterday our Mentor Chris requested Parallel IP for us and it was
granted a few hours later.
This means that we can take advantage of Parallel-IP and check in
our sources with wait for the initial CQ.

The process is like the following:
- Package up everything we have in our repo and we want to move
over to Eclipse (besides external libs) and
file a CQ
- Lock down Google-Code-SVN
- Move SVN-Repo to Eclipse
- Restart working against the Eclipse-SVN-Repo and Bugzilla

d) Request IP-Review for our external libs - some of them (LGPL, GPL)
can't be moved to Eclipse.org and we
need to host them at another location but as far as I can see
currently only the QT-Stuff can't be moved and
has to stay here. Thanks to maven all other external dependencies
are assembled by maven. How we can
release code and provide installable units with this external
dependencies is another question we need to
clarify later on. I'm also going to contact the AIM and m2m people
who are working on maven integration at
Eclipse and ask if they have consumeable artifacts for Eclipse-
Bundles.

The code move is going to be a bit of a though thing because I need to
adjust all our package, bundle names but I don't want to loose the
file history (if this is possible).

Tom

Tom

unread,
Dec 17, 2008, 10:56:12 AM12/17/08
to uface
> c) Yesterday our Mentor Chris requested Parallel IP for us and it was
> granted a few hours later.
>     This means that we can take advantage of Parallel-IP and check in
> our sources with wait for the initial CQ.
>
>     The process is like the following:
>     - Package up everything we have in our repo and we want to move
> over to Eclipse (besides external libs) and
>       file a CQ
>     - Lock down Google-Code-SVN
>     - Move SVN-Repo to Eclipse
>     - Restart working against the Eclipse-SVN-Repo and Bugzilla
>

Because I want to get this move to Eclipse done before the holidays,
I'll lock down the repo today in about 2 hours and file the
Contribution Request. Please don't check-in code after I send out a
mail - it won't get transfered to Eclipse!

I must afterwards wait for Parallel IP approval which can take between
24 and week! You can still work against the repo but keep everything
local to your workspace. Once the intial import is done one can
produce a patch against the SVN-State and apply it to the Eclipse-
Codebase.

Tom

Tom

unread,
Dec 17, 2008, 1:59:33 PM12/17/08
to uface
If I don't here anything from you I'll declare the state of trunk from
20:30 CET (=in 30 minutes from now the state we send to Eclipse.org).

Tom

Tom

unread,
Dec 17, 2008, 2:47:08 PM12/17/08
to uface
Source is tagged and I'll commit this state to Eclipse. Ideally no
changes go into Google-SVN any more. I created a tag of the code!

Tom

Tom

unread,
Dec 23, 2008, 4:34:14 AM12/23/08
to uface
Hi,

The initial contribution of the google code is available in Eclipse-
SVN and we qualified for Parallel IP [1]. Angelo if you have any thing
you have not
committed yet to the google-repo please:
a) If you have commit-rights to Eclipse checkin your changes there
b) If you are not comfortable with this then create a patch / open a
bugzilla [2] and I'll apply the patch
c) Please give me feedback when done because

I want to switch the package-names, .... today in the evening which
would mean that merging in patches is a lot of
work for you. I have myself to do this because I modified some sources
after having submitted the CQ but this is not a big
problem either.

I'm out now for x-mas shopping but you can find me on IRC in the
afternoon / evening / night.

Tom

[1]https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2910
[2]https://bugs.eclipse.org/bugs/enter_bug.cgi?
product=Incubator&component=ufacekit

Angelo zerr

unread,
Dec 23, 2008, 5:47:35 AM12/23/08
to uf...@googlegroups.com
Hi Tom,

I have start to develop Swing UIDialog and JXPath feature with EMF in
my workspace.
But I'm waiting for having UFace stable code to commit my work.
So don't worry for me, I will adapt my code and commit my work as soon
as UFace will become stable.

Angelo

2008/12/23, Tom <toms...@gmail.com>:

Tom

unread,
Jan 3, 2009, 10:50:11 AM1/3/09
to uface
Hi,

The code is available from this point on in the Eclipse-Repository and
I'd suggest we move all discussions to the Eclipse-Infrastructure.

a) Mailing-List: ufk...@eclipse.org
Subscription via https://dev.eclipse.org/mailman/listinfo/ufk-dev
For developer discussions, ....

b) Newsgroup:
Host: news.eclipse.org
Group: eclipse.ufacekit

The initially contributed code is move to Eclipse-Repositories and
packagenames and maven build is adjusted.
- None-Committers have anonymous access using
http://dev.eclipse.org/svnroot/eclipse/org.eclipse.ufacekit/
- Committers have access using https://dev.eclipse.org/svnroot/eclipse/org.eclipse.ufacekit/
and their committer name and password (Please don't use the svn+ssh://
because it looks like
its not very stable)

I'm going to fill our project page (http://www.eclipse.org/ufacekit/)
with content in the next days. Only one note before you start
committing. I'd like to see that every check-in is associated with a
bug-id so if you start working on a topic file a bug (e.g. using
Mylyn) and make your committs with this bug-id.

Tom

On 23 Dez. 2008, 11:47, "Angelo zerr" <angelo.z...@gmail.com> wrote:
> Hi Tom,
>
> I have start to develop Swing UIDialog and JXPath feature with EMF in
> my workspace.
> But I'm waiting for having UFace stable code to commit my work.
> So don't worry for me, I will adapt my code and commit my work as soon
> as UFace will become stable.
>
> Angelo
>
> 2008/12/23, Tom <tomson...@gmail.com>:
Reply all
Reply to author
Forward
0 new messages