- This topic has 19 replies, 8 voices, and was last updated 16 years, 10 months ago by
.
-
Posts
-
* I have an ant script that fully specifies my J2EE build (WAR inside EAR).
* I’d like to deploy this to WebSphere 6.0, using the same tasty MyEclipse automagic that works when the build is internally/IDE-managed.
Is this possible? If so, where do I begin.
—–
PS I RTFM’d, or rather STFF’d, and didn’t find the answer to this question. If you know a link, please hook me up.
It depends. If you are trying to move your projects into MyEclipse, the first step is understanding how to model your project as MyEclipse projects. It looks like you will need two projects, an EAR, with 1 module, which is a Web Project.
In that case, you can just deploy the EAR to your app server (like WS 6) and MyEclipse will package up the web module in it, and cough it out to WS.
jhm,
Thanks for pointing that out, I read his comment “using the same tasty MyEclipse automagic that works when the build is internally/IDE-managed.” exclusively and didn’t address the first bullet.bono,
MyEclipse doesn’t make use of Ant, so if you want to use MyEclipse you will need to model your projects accordingly inside of MyEclipse. After that is done and working you can certainly write an additional Ant script that models that all, but MyEclipse won’t make use of that and you are effectively circumventing (or duplicating, depending on how you use it) the work MyEclipse does for you. So it’s not an issue of “A and B” it’s more an issue of “A of B”.I think I probably did a poor job describing my problem, probably by not providing enough context.
Just FYI, I’ve been down the, er, sanctioned road for building and deploying an ear/web-app within MyEclipse and to WebSphere (Express, 6.0…). With success! I know how to do that. Yay.
Our team’s goal is build processes that can be run either independently of our IDE, or within the IDE. That way we can start using CruiseControl, and start obtaining all the goodness that imbues from continuous integration. We can also have one-button builds = more goodness.
However, MyEclipse has done lots of great work on integrating app deployment with WebSphere, and we’d still like to leverage that within the IDE. So, given that we’ve got an EAR (with embedded WAR(s)) that’s (presumably) good to go, is there a still a way to hand this off — or set up the plumbing –to the MyEclipse deployer somehow?
Or, put another way, for the ear project, can I replace the all the other builders with Ant, but still use the DeploymentBuilder? Or is there a way to use the MyEclipse “Manage Deployments” dialog and/or “Servers” window in that kind of Scenario?
Does that make sense?
Just FYI, I’ve been down the, er, sanctioned road for building and deploying an ear/web-app within MyEclipse and to WebSphere (Express, 6.0…). With success! I know how to do that. Yay.
So far so good
Our team’s goal is build processes that can be run either independently of our IDE, or within the IDE. That way we can start using CruiseControl, and start obtaining all the goodness that imbues from continuous integration. We can also have one-button builds = more goodness.
Gotcha
owever, MyEclipse has done lots of great work on integrating app deployment with WebSphere, and we’d still like to leverage that within the IDE. So, given that we’ve got an EAR (with embedded WAR(s)) that’s (presumably) good to go, is there a still a way to hand this off — or set up the plumbing –to the MyEclipse deployer somehow?
Ahhh. I think what you want here is just a custom Ant script. We don’t provide facilities for external hooks into the deployer at this time, and if you want to be using cruise control or the like, just write up an Ant script that basically duplicates what ME is doing, but in a script that you can deploy to each puter.
Or, put another way, for the ear project, can I replace the all the other builders with Ant, but still use the DeploymentBuilder? Or is there a way to use the MyEclipse “Manage Deployments” dialog and/or “Servers” window in that kind of Scenario?
Hmm… well if the issue is being able to control *where* the builds go, you can always do a Custom Location deployment to any location on your computer (included mounted shares). But you cannot automate this process in a task or running like a cron job.
Thanks. Just to clarify something further, if I have an arbitrary ear or war, can this be deployed from within MyEclipse using the MyEclipse deployer?
Thanks. Just to clarify something further, if I have an arbitrary ear or war, can this be deployed from within MyEclipse using the MyEclipse deployer?
Well it needs to be dropped into the respective project types as outlined in some of the posts above, but if you can do that, you should be OK.
Completely arbitrary layouts and so on cannot be managed/deployed by MyEclipse.
Thanks for your patience with me, Riyad. I’m just trying to make absolutely sure that I’m not missing some way to hack around this to get ME to work. I’m also pursuing doing this through raw WTP, which might be the better way to do it.
I understand that ME does not support arbitrary directory structures.
Well it needs to be dropped into the respective project types as outlined in some of the posts above, but if you can do that, you should be OK.
I read over the thread twice looking for this. Was there something I missed about wrapping done-deal ears/wars into ear/war project types to use ME deploying?
cb
I read over the thread twice looking for this. Was there something I missed about wrapping done-deal ears/wars into ear/war project types to use ME deploying?
I’ll clarify what I meant:
If you want MyEclipse to handle deployment of your project, you need to be able to model your project using MyEclipse projects (EAR, EJB, WAR, Java Project). There is no automated way to do this, you need to do this step manually. If you cannot model your project as 1 or more deployable MyEclipse projects, then MyEclipse cannot handle the deployment step for you.Did that help or make things worse?
@bonobonewton wrote:
Our team’s goal is build processes that can be run either independently of our IDE, or within the IDE. That way we can start using CruiseControl, and start obtaining all the goodness that imbues from continuous integration. We can also have one-button builds = more goodness.
This is the same thing my team is struggling with at this time: having an easy, consistent deployment process, both from outside the IDE and from within the IDE.
@support-rkalla wrote:
We don’t provide facilities for external hooks into the deployer at this time, and if you want to be using cruise control or the like, just write up an Ant script that basically duplicates what ME is doing, but in a script that you can deploy to each puter.
This is unacceptable to me. For as long as MyEclipse has been around, they seem to be spending more time incorporating bells and whistles and the latest and greatest and neglecting some of the more fundamental features. One of which is just what you mention: providing the ability to call MyEclipse’s deployer from an ant script. Such a feature would take our deployment process soooo far forward it would be awesome. We’ve already automated the checkout and initial prepping of the codebase (depending on which server we’re deploying to). If we could call the deployer after that step, we would then have an EAR which we could then have ant send to our deployment team. This would make our lives soooooooo much easier and give us so much more peace of mind it’s not funny.
Because of the seeming lack of interest in adding this feature to MyEclipse, my team is seriously considering moving away from MyEclipse altogether, to WTP.
P.S. Another feature that would be great would be the ability to utilize a shared installation of MyEclipse. Right now, each of the developers on our team has to install MyEclipse separately. Having a single version of MyEclipse that we all used would be another thing that would give us much more peace of mind about producing consistent builds/deployments.
This would make our lives soooooooo much easier and give us so much more peace of mind it’s not funny.
I *think* you might be able to do this now with our included Maven support in 6.5… I haven’t thoroughly tested it, but if you created your projects in Maven-ized fashion, you should be able to run the package maven goal from the command line to accomplish the deployable unit… that might require some testing on your end and re-creating some projects as Maven-ized projects, but I think it’s doable now. I haven’t tested hugely complex scenarios but in simpler ones, it worked.
my team is seriously considering moving away from MyEclipse altogether, to WTP.
We understand that you and your team need to use whatever tools make you the most effective. We work our assess off to try and strike a balance in functionality/requests with each release to address our 500,000+ users that all have their own features that are “must haves”, it’s tricky. And if we have missed the target on something that your team absolutely needs, the only thing we can offer is that we hope we win your business back with a future release.
P.S. Another feature that would be great would be the ability to utilize a shared installation of MyEclipse. Right now, each of the developers on our team has to install MyEclipse separately. Having a single version of MyEclipse that we all used would be another thing that would give us much more peace of mind about producing consistent builds/deployments.
Ok the cool part here is that you *just* described Pulse Freelance (www.poweredbypulse.com). I could go on and on about how cool it is, but I think if you watch this short screencast (3mins?) you’ll be able to see how powerful this is when you can provision an entire software stack, workspace, projects and repositories, and then share that with an entire team (with full admin read/write controls, etc.)
http://www.poweredbypulse.com/pulse-demo/demos/Pulse-Workspace-Provisioning/Pulse-Workspace-Provisioning.htmPulse is not a MyEclipse-specific technology, it’s a general provisioning technology so if you do decide to go with WTP, you can provision anything you want using it. MyEclipse… WTP, Spring, JBoss, custom update sites, 3rd party tools, locally installed custom plugins… whatever you want.
I was just searching through the forum for anything on continuous automated builds and ran across this thread. The postings by “support-rkalla” and “bonobonewton” stood out to me. Especially the goal of (build processes that can be run either independently of our IDE, or within the IDE). I am primarily interested in the build and packaging aspects, the actual deployment is not a primary concern. However, we have many MyEclispe Web and Application projects so being able to run a build of these from the command line on an automated schedule is the best description of what we are striving to do.
I have been playing with the Maven4MyEclipse stuff for about a day and not making much progress. First, I would like to know if I can build MyEclipse Web and Ear projects from the command line?
Secondly, I followed the tutorial for Maven4MyEclipse and I run into a problem where the two jar files for JSF are not downloaded automatically and it is instructing me to download them manually and then run the command “mvn ….”. My question is where do I find that file in the embedded Maven instance that comes with MyEclispe?
-Dave
Dave,
Maven4MyEclipse is a UI on top of Maven (maven.apache.org).You can use the Maven4MyEclipse to get everything all set up and peachy-keen, as it’s much easier to do than going to maven.apache.org and learning how to do it all using the command line tool.
Nonetheless, once you have it all set up (easy or otherwise), you still need to use the command line tool if you are going to run it command line such as with a continuous integration system. This is all documented on maven.apache.org and many many other online places.
