[djm007]

I assume this is doable, but I’d like to see the ability to call MyEclipse features from Ant. Something along the lines of:

<taskdef name=”build” classname=”com.myeclipseide.BuildProjectTask”/>
<taskdef name=”deploy” classname=”com.myeclipseide.DeployProjectTask”/>

<target name=”junit”>
<junit>
<test name=”my.test.TestCase”/>
…
</junit>
…
</target>

<target name=”all” depends=”build,junit,deploy”/>

so the build and deploy features can be integrated with Ant.

[djm007]

… of course, with “build” and “deploy” targets that call the build and deploy tasks…

[Robert Varga]

I second this… 🙂

[Scott Anderson]

Interesting idea. Of course, building the project is really an Eclipse functionality, even though we add custom builders to the cycle. The deployer is certainly doable though. Anyone else like this?

–Scott
MyEclipse Support

[Riyad Kalla]

I’m fine with whats there now, I like buttons.

[Ronald R DiFrango]

I would love to see this as well. The way it is structured today, I have to have Eclipse [and MyEclipse] up and running on the machine where I am deploying to which can be a real pain if have seperate machines for development, testing and production.

Additionally, there is no safe way for me to put my own custom code into the ANT build scripts.

[djm007]

The buttons and all work just fine.

What I’d like is a button that does this:
build, shutdown app server, deploy, startup app server, run junit tests, run junitreport, rinse and repeat.

[Riyad Kalla]

Ahh, so like a customizable button that you can assign actions to? Kind of like the Build Tools setup for each project? (defines tasks to execute when “building”)? That’s not a bad idea…

[Author]

Posts