James Moody wrote:
Michal,
Oracle was originally on tap to own
the runtime framework milestone items (see the milestone plan), so you
guys should take care of this.
Will you be able to deliver on this
soon?
I'll take a look at the code "soon".
-michal
james
Michal Chmielewski
<michal.chmielewski@xxxxxxxxxx>
wrote on 08/25/2006 02:35:37 PM:
> Who does the review, James ? I am little swamped here right now
with
> out of band things that have landed on me ....
>
> -m
>
> Bruno Wassermann wrote:
> Hi All,
>
> The source code for org.eclipse.bpel.runtimes
is now in Bugzilla.
>
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=155197
>
> Happy reviewing J
>
> -- Bruno
>
>
> From: James Moody [mailto:James_Moody@xxxxxxxxxx]
> Sent: 21 August 2006 12:57
> To: B.Wassermann; BPEL Designer project developer discussions.
> Subject: Re: [bpel-dev] org.eclipse.bpel.runtimes
>
>
> Hey Bruno,
>
> This sounds great.
>
> As a bit of background, here is how we should proceed.
>
> 1. All commits to the CVS repository have to be made by a
committer.
> The current committers are myself, Michal, Wylie and Rodrigo.
> 2. The easiest way for this to happen is for you to open a bug in
> bugzilla, and then create a zip file with all the code and attach
it
> to the bug as an attachment.
> 3. One of the committers can then take the code into their
> workspace, review, and commit.
>
> The bugzilla step is important for traceability as well as for
legal
> reasons - please don't send code in a direct email to one of the
committers.
>
> Going forward, the procedure for becoming a committer is for an
> existing committer to nominate you on the mailing list, followed
by
> a vote of all existing committers. If the vote succeeds, the new
> committer process begins and after some legal stuff a new
committer
is born.
>
> james
>
> bpel-dev-bounces@xxxxxxxxxxx wrote on 08/21/2006 06:55:23 AM:
>
> > Hi,
> >
> > I think it would be worthwhile to get the runtimes plug-in
into
cvs now. It
> > is not complete yet, but should provide enough to allow
third-party
runtime
> > providers to get started and provide feedback.
> >
> > I have started working on exercising the plug-in by
integrating
ActiveBPEL,
> > but will have to delay this to work on yet another interim
release.
> >
> > Once the plug-in is in cvs, I will make the ActiveBPEL
integrationcode
that
> > exists so far available on our (OMII-BPEL) web site to show
how
the runtimes
> > plug-in could be used.
> >
> > How do we get the runtimes plug-in into cvs? Are there any
instructions
> > somewhere?
> >
> >
> > Thanks,
> >
> > -- Bruno
> >
> >
> > What it does:
> > - BPEL project creation wizard (minus suitable icons)
> > - recognise bpel files as server framework modules
> > - deployable adapters to add bpel modules to 'add/remove'
wizard
for
> > publishing to suitable runtime
> >
> > What it doesn't yet do:
> > - recognise BPEL projects as modules
> > - GenericBPELPublisher does not yet provide any utility
methods
(store
> > deployment archive locally, add validation status to problems
view, etc.)
> >
> > ______________________________________________
> > Bruno Wassermann
> >
> > Research Fellow
> >
> > University College London Tel: +44 (0)20
7679 0369 (Direct Dial)
> > Dept. of Computer Science Fax: +44 (0)20
7387 1397
> > Gower Street
> > London WC1E 6BT
http://www.cs.ucl.ac.uk/staff/B.Wassermann
> > United Kingdom
> > ______________________________________________
> >
> >
> > _______________________________________________
> > bpel-dev mailing list
> > bpel-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/bpel-dev
>
>
> _______________________________________________
> bpel-dev mailing list
> bpel-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/bpel-dev
>
>
> --
> Michal Chmielewski, CMST, Oracle Corp,
> W:650-506-5952 / M:408-209-9321
>
> "Manuals ?! What manuals ? Son, it's Unix, you just gotta know."
--
Michal Chmielewski, CMST, Oracle Corp,
W:650-506-5952 / M:408-209-9321
"Manuals ?! What manuals ? Son, it's Unix, you just gotta know."
|