- This topic has 32 replies, 5 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
Riyad,
I see the button, but it does nothing and gives a null pointer exception in the shell from which I launched. I did some peeking and noticed that I have no browsers listed in the MyEclipse preferences. Does this button launch an external browser that would be defined there? If so, and there is no preview and/or integrated web browser on Linux, does the debugging still work the same?
Oh, and as for the preview view in M2 on Linux, there is absolutely no preview tab next to the source tab.
Brian,
The Web Browser view is an Eclipse component that is quiet picky about the version of Mozilla installed (what it is bound to on Linux), if you check this doc here:
http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/htmleditor/index.htmland scroll to the FAQ section, those tips were written for Eclipse 3.0 but they may still apply to 3.1. I am not sure of the state of the mozilla binding at this point (Searching bugs.eclipse.org may turn up more info).
If you only have firefox installed or neither mozilla or firefox installed (for example if you are using Konqueror as your browser) that would explain why the view is failing to load.
Riyad,
OK, that explains that. On to a couple of more issues. Please don’t hate me, my whole group just bought memberships… ;^)
1. The deployment mechanism blows away everything in the target and exports the project contents to the target. In my situation, we have one large web application on the server in which there are multiple people working on various parts. If I create a project, import my portion in, and then deploy my portion, it’ll blow away everyone else’s portions and stick only mine back in. You guys warned me about this, so I didn’t screw up. However, what I’m having to do is deploy to a bogus location, then manually rsync the files to the server so I don’t affect anyone but me. What are the chances of you guys adding an option (like a checkbox) to the deployment mechanism that allows you to keep everything that is in the target, but overwrite what has changed (or at a minimum, overwrite whatever is in the active MyEclipse web project regardless if has changed or not)?
2. I got debugging working with my remote server! :^) I take it that for custom classes that are in my project, I have to compile them with debugging enabled or something to get the debugger to dive into them?
Brain,
With respect to #1, are you deploying a simple web project? When you sayd that each of you is working on a part, do you mean that each of you are working on a portion of the same web project OR that you are deploying an enterprise app and each of you is working on a module (web module, ejb module, etc.)If it’s the later, an exploded deployment should fix that, if it’s the first (multiple people working on same webapp) I’m afraid there isn’t much you can do except try and make sure everyone is using exploded deployments, in which case ONLY the changed parts are synced out to the server as soon as you save them (no more needing to open the deploy window and hit deploy each time).
Riyad,
We’re all working in separate directories of the same webapp/context, and share responsibilities in the “webapps” directory, which I now know I shouldn’t have named that:
etiweb (webapp/context)
..eds (me)
..css (me)
..include (me)
..ssds (fred)
..cde (chad)
..vis (alan)
..eti (nancy)
..webapps (all)The “etiweb” webapp/context is so large that it would be unfeasible for each of us to have the whole thing in our local project. So, my project only includes the stuff I work on (eds, css, include, and webapps). I made a dummy copy of the entire etiweb tree and tried to deploy just my portion there exploded. It removed everything that’s not in my project. If the answer is to put the whole webapp in my project, I can do so, but the build times would be horrible, and I’d always be in conflict with my teammates.
To further explain, the reason we decided to keep everything all in one context is because we needed to share a top-level configurable menu and share the same styles. Our main requirement was to have a common look and feel across all department groups that was low maintenance. The only way I could do this in Tomcat at the time was to put everything in one context because I couldn’t get the cross-context thing to work. I ran up against the deadline and had to implement this way instead.
Brian,
I understand your basic requirment (tell the deployer to “leave things alone”). I’ll see if we can get this enhancement added, I don’t know in what release it would be in if management thought it was needed.Brian,
Would a new feature that is discussed here work for you?
https://www.genuitec.com/forums/topic/deployment-option-overwrite-resource/#post-212926If so, this new feature has been implemented in 4.0GA as the new “overwrite” deployment option.
Greg,
I tried to make sense of that post. It appears that Dorothy started out by requesting a total “overwrite” deployment feature, then switched gears to request that the deployment only overwrite a portion of the EAR. What I’m seeing is that when I initially setup my deployment, if the directory already exists, it won’t continue to let me choose that directory. Then, after setting it up, the auto-deploy always cleans and deploys. What I’m looking for is what I think Dorothy was looking for at the bottom of the thread. I need to be able to choose my live development server location to deploy to which already exists. Being that I work on specific portions of this EAR, I need to be able to tell the deployment mechanism to push my stuff and overwrite what is in my project, but not the entire EAR. What would be even better is to have the deployment mechansim only push what has changed since the last deploy, not the entire project. Does this makes sense?
I need to be able to choose my live development server location to deploy to which already exists.
Can’t you do that by configuring one of the “Custom Location” options in the deployer? You can set those to whatever directory you wish.
Actually, no. MyEclipse won’t allow you to choose a location that already exists. Even if so, from the behavior I’ve seen from the deployment mechanism in the past, if I were able to choose my already existing location, the deployment mechanism would wipe out it’s contents and replace it with what’s in my current project. This is where the problem lies because my project doesn’t contain the entire web application, only my portion. If I do this, I’ll blow away about 10 other areas that aren’t under my control.
