On Mon, Jul 4, 2011 at 11:24 AM, Saminda Wijeratne <samin...@wso2.com>wrote:
> > > On Mon, Jul 4, 2011 at 10:55 AM, Hasitha Aravinda <hasi...@wso2.com>wrote: > >> Hi, >> >> Last year, Keheliya and Ishan had applied following patches to the [0] . >> >> [1] - Gives a warning when attempting to create a BPEL file with the same >> name >> [2] - Properties view of each object in a BPEL diagram does not appear by >> default >> [3] - Process clean-up configuration support for deployment descriptor >> editor >> >> Patch [1] and [2] were accepted and already added to the Eclipse's BPEL >> Designer project source. But the patch [3] has a bug and not applied to the >> bpel designer source. >> >> The patch [3] causes problem when there are more than one bpel projects in >> the workspace. When editor is cleaning one deply.xml in a one project, the >> clean operation will apply to the all other depoy.xml s in other projects. >> >> Since it is a not critical issue for now, I have applied [3] to the new >> Source code at [4]. But we will have to fix it in future. >> >> Then I added new E4X feature to the [4] and all Pom.xml are updated to the >> maven3. >> >> Another thing I observed is BPEL project structure has been changed. In >> new BPEL project, it uses nested folder called “BpelContent” (The name can >> be changed) to store project files. (.bpel , .wsdl , deploy.xml etc ). But >> in current CS *BPELArtifactWizard*, it links to the BPLE project’s >> folder. So we need to fix this linking problem in carbon studio side. >> Otherwise Carbon Application project and BPEL project will not work >> together. >> > Noted. We will fix this for up coming trunk releases. In the meanwhile can > you check if this is a mandatory change or not and any other associated > structural changes? > > Ok, I will check and let you know about changes. > Saminda > >> >> I will keep update the progress of the Branching work. >> >> Now I am working on implementing bpel4peopel activity to the BPEL >> Designer. >> >> >> [0] - https://wso2.org/svn/browse/wso2/trunk/tools/ide/eclipse/bps/ >> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=312401 >> [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=318151 >> [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=318153 >> [4] - https://svn.wso2.com/wso2/sites/intern/hasitha/bps/ >> >> >> >> >> On Fri, Jun 24, 2011 at 12:05 PM, Denis Weerasiri <de...@wso2.com> wrote: >> >>> >>> >>> On Fri, May 27, 2011 at 11:50 PM, Saminda Wijeratne >>> <samin...@wso2.com>wrote: >>> >>>> +1. >>>> >>>> AFAIK not all patches contributed to the eclipse bpel editor project >>>> were applied. Please contact Keheliya or Ishan to obtain the patch list or >>>> use the svn to track down commited patches to our forked bpel-editor >>>> source. >>>> >>>> Hasitha, make sure eclipse bpel-editor trunk revision you are going to >>>> migrate to CS is stable enough. >>>> >>> Hi, >>> Based on bpel-dev folks, current trunk is in stable mode. So Hasitha has >>> started merging the changes on carbon studio to a forked current trunk of >>> bpel-editor. He is in the process of merging the changes what Ishan and >>> Keheliya did some times back. Hasitha will update the thread with progress >>> status. >>> >>>> >>>> Saminda >>>> >>>> >>>> On Fri, May 27, 2011 at 7:26 PM, Denis Weerasiri <de...@wso2.com>wrote: >>>> >>>>> Hi, >>>>> Hasitha is working on some improvements to bpel editor trunk at >>>>> http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.bpel/?root=Technology_Project >>>>> . >>>>> >>>>> But Carbon Studio team maintain a forked older revision >>>>> http://svn.wso2.org/repos/wso2/branches/tools/eclipse/carbon-studio/1.0.0/bps/ >>>>> (which >>>>> include some patches applied by Keheliya et. al + Modifications done by CS >>>>> team), >>>>> >>>>> I think Hasitha can work on this migration. WDYT? >>>>> >>>>> -- >>>>> Thanks, >>>>> Denis >>>>> ---------------------------------------------------------- >>>>> *Denis Weerasiri* >>>>> Software Engineer; WSO2 Inc.; http://wso2.com, >>>>> *email: denis <http://goog_277208233/>** [AT] wso2.com*<http://wso2.com/> >>>>> * >>>>> blog: **http://ddweerasiri.blogspot.com*<http://ddweerasiri.blogspot.com/> >>>>> * >>>>> twitter: **http://twitter.com/ddweerasiri*<http://twitter.com/ddweerasiri> >>>>> * >>>>> linked-in: >>>>> **http://lk.linkedin.com/in/ddweerasiri*<http://lk.linkedin.com/in/ddweerasiri> >>>>> >>>>> >>>> >>> >>> >>> -- >>> Thanks, >>> Denis >>> ---------------------------------------------------------- >>> *Denis Weerasiri* >>> Software Engineer; WSO2 Inc.; http://wso2.com, >>> *email: denis <http://goog_277208233/>** [AT] wso2.com*<http://wso2.com/> >>> * >>> blog: **http://ddweerasiri.blogspot.com*<http://ddweerasiri.blogspot.com/> >>> * >>> twitter: **http://twitter.com/ddweerasiri*<http://twitter.com/ddweerasiri> >>> * >>> linked-in: >>> **http://lk.linkedin.com/in/ddweerasiri*<http://lk.linkedin.com/in/ddweerasiri> >>> >>> >> >> >> Thanks >> -- >> >> Hasitha Aravinda >> >> >> >> > Thanks, -- Hasitha Aravinda
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
