[Frank Weber]

I am working with other developers using eclipse / ant i.e. not (yet 🙂 ME . .. and I would like to utilize ME deployer and features like hot deploy, debug …

I browsed through the forum archive and found an older comment from Scott:
http://www.myeclipseide.com/modules.php?op=modload&name=PNphpBB2&file=viewtopic&t=352

If you must use Ant, you need to either configure it to compile your code with full debugging information included (default is off) or don’t compile at all and just repackage the class files that Eclipse has compiled.

Is there possible a thread that covers this issue perhaps in more detail or could you give me some advice ?

Thanks in advance,

Frank

[Riyad Kalla]

Frank,
There isn’t another thread covering this, but as long as all your projects can be setup under MyEclipse, and build correctly and all that, you can just ignore their Ant script and use MyEclipse to do everything.

Are you having a problem getting the project into MyEclipse as project(s) or is it alredy in there as a web project, and you just weren’t sure what to do next?

[Frank Weber]

Riyad,

Well let’s consider a project with possibly multiple JARs WARs that are checked out from the CVS in one go, see Directory Structure section below…

Whereby one build.xml defines subproject filesets (WAR, JAR, EAR) and imports main build.xml.
The main build.xml defines the tasks for init, compile, packaging and deploy.

How would you handled this by ME?
Or how would you recommend to organize a directory structure so that ant build or ME build can be used together with the CVS?

Thanks in advance,

Frank

Directory Structure:

main-project:
build.xml
build.properties
lib/
output/
build/
doc/
<sub project web>/
build.xml (defines subproject filesets (WAR, JAR, EAR) and imports main build.xml)
build/
view/
resources/
META-INF/
WEB-INF/

<sub project ejb>/src/
<package of subproject>*.java

…

<sub project web>/
build.xml (defines subproject filesets (WAR, JAR, EAR) and imports main build.xml)
build/
view/
resources/
META-INF/
WEB-INF/

<sub project ejb>/src/
<package of subproject>*.java

[Frank Weber]

Sorry the indentation on the Directory Structure got lost. Please refer to this outline instead, thanks.

main-project

build.xml
build.properties
lib/
output/
build/
doc/

<subproject web>/
    build.xml (defines subproject filesets (WAR, JAR, EAR) and imports main build.xml)
    build/
    view/
    resources/
        META-INF/
        WEB-INF/

<subproject ejb>/src/
    <package of subproject>*.java

...

<subproject web>/
    build.xml (defines subproject filesets (WAR, JAR, EAR) and imports main build.xml)
    build/
    view/
    resources/
        META-INF/
        WEB-INF/

<subproject ejb>/src/
    <package of subproject>*.java

[Riyad Kalla]

Each “sub project” will have to be modelled as an individual project in MyEclipse. Web Projects can rely on Java Projects for common code, but cannot rely on other web projects or EJB projects.

Web, EJB, Java and 3rd party JARs can be added to an EAR as modules for deployment to an app server as a single EAR if you need that.

Our project flexibility is going to increase greatly in MyEclipse 5.0, I would almost encourage you to keep using Ant if you can until we release MyEclipse 5.0 and then give it a try and see if you can set this up without pulling all these apart. I’m not guarunteeing that it will work, just that the chances are much higher it will.

Each project is different, I would suggest to start with something easy, say converting one of the web projects to a MyEclipse Web Project, then an EJB project and so on.

[Author]

Posts