- This topic has 16 replies, 5 voices, and was last updated 16 years, 4 months ago by
SrinivasVemula.
-
AuthorPosts
-
Paul_PMemberThis message has not been recovered.
November 29, 2007 at 10:52 am #279142
Loyal WaterMemberThis message has not been recovered.
December 14, 2007 at 3:50 am #279673
Paul_PMemberNipun,
thanks for your message. As we heard, the first release of MyEclipse Blue Edition is scheduled for Mid March. We bought a number of MyEclipse 6.0.1 licenses and are using it in our everyday development. After MyEclipse Blue will come out, we will try it and probably upgrade our subscriptions.
It would though be important for us that this bug be fixed as soon as possible. I suppose, that will take place in the next release of MyEclipse, so before the Blue Edition. Is that right? When will the next MyEclipse Version come out?
Thanks & Regards,
Paul P.
December 14, 2007 at 10:00 am #279684
Riyad KallaMemberPaul,
We are working to get this WAS-specific behavior into Blue Edition, but the good news is that we are targeting a mid-Jan release for Blue. Our 6.1 release we are shooting for March/April.I believe should have a milestone for Blue out before the final release, so any feedback you could give us during testing would be appreciated if possible when that happens.
January 8, 2008 at 11:49 am #280407
rkathlerMemberAdding to issue above that Paul has listed, I have a problem that is related.
App Server that I have – Websphere 61 on Windows XP Professional and Intel hardware.
I followed the directions on the below url http://www.myeclipseide.com/documentation/quickstarts/websphere6/ to configure my Websphere 61 (not 60) server
I wanted to do the Enterprise Sync-on-Demand Development as explained in the above URL. For some reason the MyEclipse 61 connector links to 2 different directories for Package and Exploded views.
For Packaged View it points to – C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installableApps
For Exploded View it points to – C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installedApps
One is “installableApps” and one is “installedApps”.
So with this I am not able to do the following instruction as documented in the MyEclipse documentation listed on the above URL.
“So, in order to be able to install to WebSphere (and other application servers that require installation of EARs) and still gain the benefit of Exploded deployment, we need to do a little trick to “overlay” an exploded deployment ontop of an existing installed application. ”My question is – How do i configure MyEclipse to change the “Exploded” and the “Packaged” to the same directory to “overlay” or is there another way to do this?
Any help is greatly appreciated.
Thanks
RajJanuary 9, 2008 at 9:00 am #280452
Riyad KallaMemberRaj,
You don’t need to worry about changing the directory. What you do is first deploy the packaged deployment, it will be put in “installableApps”, you then login to WAS Admin Console and *install* the app. Now you remove the packaged deployment and redeploy an exploded deployment, it will automatically overlay ontop of where WAS installed the packaged app: “installedApps”January 9, 2008 at 10:19 am #280461
rkathlerMemberAwesome.
Thanks Riyad.
That did the trick. I was thinking too much and got ahead of me.
Thanks
RajJanuary 9, 2008 at 10:50 am #280466
Riyad KallaMemberNo problem, glad it helped.
September 30, 2008 at 4:13 am #289530
Paul_PMemberHi,
we upgraded to MyEclipse Blue Edition. We are using MyEclipse 6.5.1 Blue-GA-20080715. Now some of my colleagues are working with IBM WebSphere Portal, Version 6.0.1.3. They have the same problem with WebSphere Portal:
Some configuration files, particularly web.xml, portlet.xml und struts-config.xml, are saved upon installation in the following backup directory:
<WebSpherePortalRoot>\profiles\<profileName>\config\cells\<cellname>\applications\<AppName>\deployments\<AppEAR>\As described in my previous messages, MyEclipse Blue use these files in the deployment process from the above directory, instead of the exploded deployment directory. This leads to the fact that when we change these configuration files, the old files are still used and the new ones are ignored.
To solve this problem, the HotDeployment Plugin of MyEclipse Blue should IMHO copy the configuration files to the backup directory as well, not only to the Exploded Deployment Directory.
Can you please deliver a patch that solves this problem?
Many thanks in advance,
Paul P
October 7, 2008 at 11:20 am #289753
Riyad KallaMemberPaul,
I believe a solution to this issue is on our roadmap, I’ll ping the Blue dev team to double check however.
October 8, 2008 at 4:47 am #289786
Paul_PMemberHi rkhalla,
I’m sorry, but this is not what I expected. For one year, you have been writing that you plan to fix this problem in the next release. Unfortunately, this didn’t happen, neither for WAS nor for the WebSphere Portal, neither in MyEclipse nor in the Blue Edition. This problem is costing our company every day time, nerves and money. We need to know when this problem will be solved, in order to be able to calculate reliably the work efficiency on our projects.
Please provide us with an exact release date for this bugfix.
Thanks in advance,
Paul P
October 8, 2008 at 2:49 pm #289809
Riyad KallaMemberPaul,
I’m discussing/evaluating this with management right now. Will need to wait on them for full evaluation.
October 21, 2008 at 3:59 am #290146
Paul_PMemberHi Riyad,
we have been waiting for two weeks now. How long do your management need for the “full evaluation” you are mentioning?
Please give us a quick answer.
Thank you,
Paul
October 21, 2008 at 11:07 am #290161
Riyad KallaMemberPaul,
Management did assess it and will try and address it in November for the 7.0GA release. So I do have a pending commitment out of them now.
November 24, 2008 at 4:41 am #291320
Paul_PMemberHi Riyad,
has the bug been fixed in 7.0GA? When exactly will 7.0GA be (or has been) released?
Thanks,
Paul
-
AuthorPosts