[jimisola]

Hi!

Before I start whining I want to let you guys know that I’ve been using MyEclipse since the very start. Put, it simple it is a great tool! 🙂

Of course I use a database gui tool. Currently, SquirrelSQL (squirrel-sql.sf.net) and there is Squirrel Eclipse Plguin JFaceDBc (www.pratocity.com/index.jsp?mod=/jface/jfacedbc.jsp) as well.

But is your Database Explorer really needed? I mean there are several other good, even very good, gui database tools. I just feel that there are other features I rather see you guys spend your time with, e.g. JSP2.0 support, refactoring etc and most importantly project structures and their flexibility. I remembering bringing up the need for flexibility early, since it keeps me (and the project that I am in) to use all of MyEclipse features fully. Actually, I haven’t checked lately, but isn’t it still so that MyEclipse expects an exploded JAR file?

Just my five cents.

Regards,
Jimisola

[Riyad Kalla]

But is your Database Explorer really needed?

Good question… its not *just* the DB tool… the DB tool ties into currently our Hibernate tool and future OR mapping strategy… its a small piece of a big puzzle if you will. Also we want to provide as much of the J2EE tooling picture as we can… its tough for our customers when we have 90% of what they want, but the 10% we are missing costs them $50 when they have to go buy another plugin.

Actually, I haven’t checked lately, but isn’t it still so that MyEclipse expects an exploded JAR file?

Its getting there piece by piece. Major additions to deployment of dependent resources (JARs, Projects, etc.) was included, and now in 3.8 GA we are going to include the extremely popular “I want my WebRoot directory to be my Project Root” request that will free up a lot of people from project structure requirements.

We will continue to enhance our project structure support just as we have done, each release getting a little more flexible, and a little more powerful.

[jimisola]

Just to let you know what me/you/we are up against when it comes to project structure I’ve provided my project below.

We create our taglibs and classes dynamically using Ant/XDoclet when we create the final WAR file. The easist way for this to work would be to still have Ant to the create taglibs etc and then be able to point out different files (taglibs, classes etc) in the MyEclipse Web Project (a little like the Java Build Path for Java Projects).

Regards,
Jimisola

 + build \  
  |        + classes  -- Compiled classes from src         
  |        |
  |        + test \
  |                + classes -- Compiled unit test classes
  |                | 
  |                + data    -- Results from unit test runs
  |                |
  |                + reports -- HTML reports from unit test runs 
  | 
  + db         -- Database SQL definitions
  |
  + dtds       -- Global XML DTDs
  | 
  + javadoc    -- JavaDoc generated documentation
  |
  + lib        -- Global Java jar files
  |
  + prototypes -- Prototype code
  |
  + src  \      -- Source code (yippeee) 
  |       + se \
  |             + org\
  |                          + product \
  |                                            + component1-- component1 source code
  |                                            | 
  |                                            + component2   -- component2 source code
  |                                            | 
  |                                            + common  -- common (shared) source code
  |       + webroot \   -- Server web application 
  |                 
  |
  + test \       -- JUnit test code
  |       + se \
  |             + org \
  |                          + product \
  |                                            + component1-- component1  unit tests
  |                                            | 
  |                                            + component2-- component2  unit tests 
  |                                            | 
  |                                            + common  -- common unit tests 
  + tools \
           + apache-ant-1.5.2
           |
           + jakarta-tomcat-4.1.18

[Scott Anderson]

Jimi,

Thanks for providing this layout. We’re actually writing up the requirements for fully flexible projects next week.

[jimisola]

No problem. Keep us updated 🙂

Jimisola

[Robert Varga]

@support-scott wrote:

Jimi,

Thanks for providing this layout. We’re actually writing up the requirements for fully flexible projects next week.

Hi Scott,

I hope you don’t forget to take my old specification draft into account, which I posted in one of your forums 🙂 If you’d like, I can try to find it… 🙂

I don’t think you need anything more flexible than that… 🙂

Regards,

Robert

[Riyad Kalla]

Robert,
Is this it? http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-1841-highlight-project.html

[Robert Varga]

@support-rkalla wrote:

Robert,
Is this it? http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-1841-highlight-project.html

Yes, the post on Mar 09, 2004 – 12:34 PM in that topic.

Regards,

Robert

[Robert Varga]

@support-scott wrote:

Jimi,

Thanks for providing this layout. We’re actually writing up the requirements for fully flexible projects next week.

Scott,

could you post a heads up after the meeting regarding the agreed upon functionality specs to be implemented and the target version? 🙂

Thanks in advance,

Robert

[Author]

Posts