[Erik Reuter]

I’m deploying to a JBoss 3.2.2 server running locally and would like to put my EARs into a non-default location, so that they’re easier to manage than when deploying into the default deploy dir in JBoss along with the other stuff in there.

I thought the Browse button in Manage Deployments would be the ticket, but it does…. Absolutely nothing… as far as i Can tell…

Is the Browse button for picking an alternate deploy location of the EAR, or just some fancy file-browsing feature? Wee! I can see my files ; )

I’m running MyEclipse v3.6.2 on Linux, so if this is fixed in v3.6.3 I’ll quickly apologize in advance for this posting.

Regards
Erik Reuter

[Scott Anderson]

Erik,

Is the Browse button for picking an alternate deploy location of the EAR, or just some fancy file-browsing feature? Wee! I can see my files ; )

It’s the latter, to an extent. It’s really intended as a fast way to look at your exploded deployment directory in case you are concerned that certain files aren’t going out properly or mod times are wrong or something.

At present, we only support deployment to the default locations. This is the case for a couple of reasons. First, you have to start somewhere to get something working. 🙂 Second, as soon as we let user’s specify different locations it means they have to know enough to modify their server configuration files manually. This would give a large rise in the number of support cases almost immediately as users assumed they could specify any random directory and MyEclipse would make it work somehow. Since we really target development efficiency, rather than production-like deployment, support for only the default configurations seemed like a good trade-off/starting point at the time.

If you have some ideas on how we can improve this, without killing us with the extra support burden or massive development effort to support random configurations on 20 different server connectors, please post your ideas to the Feature Requests forum. We really want to provide what’s needed to our users.

–Scott
MyEclipse Support

[Ceki Gulcu]

Here a couple of suggestions.

– Include a warning label stating that MyEclipse currently supports deployment to the default location on linux. This could save some grief to new MyEclipse users.

– Otherwise, allowing to user to set the deployment location would be a step forward. Many users do not expect MyEclipse to modify the server config files.

As a side note, it would be very helpful if the user could redeploy the last deployed project by pressing a single button, instead of “Deploy J2EE project to server”+select project+click redeploy+click OK. These 4 steps are repeated very frequently exactly in the same oder.

Many thanks in advance,

—
Ceki

[support-michael]

– Otherwise, allowing to user to set the deployment location would be a step forward. Many users do not expect MyEclipse to modify the server config files

Internally the codebase supports user-specified deployment to a non-default location. The functionality has not been surfaced because of concerns that users will expect that deployment to any folder will include configuring the respective appserver to use the non-default folder. Presently we plan to surface this functionality once we have appropriate user warning/notice system in place.

it would be very helpful if the user could redeploy the last deployed project by pressing a single button

I have added your feedback to the current internal thread for this feature. Look for it in 2.8 since the 2.7 feature set is set.

Michael
MyEclipse Support

[Author]

Posts