We have a very similar setup for one of our projects: 3 Frameworks, 1
framework depends on another, app depends on all 3. These are legacy
projects and many have subprojects. I got ours running with the incremental
builder with this setup:
WinXP Pro
Eclipse 3.0
WOLips 1.1.0.77
1. First, I did not bring over the old projects. The project structure is
different enough, I chose to recreate all of the projects using the new
WOLips without any baggage, so I got brand new builds of Eclipse and
WOLips, and a new workspace.
2. Created the 3 Frameworks using the wizard. For <FrameworkB>, I check the
box for <FrameworkA> in the Referenced projects section. Added any needed
subprojects with wizard.
3. Created the Application with the wizard, and checked all 3 projects on
the Referenced projects section. Added subprojects with wizard.
4. Copied all of my source files and resources from my old projects into
the appropriate places in the new workspace. In the past I have done this
in the file-system, but this time I dragged and dropped from the file
system into the Eclipse navigator and let Eclipse copy them for me.
Re-adjusted individual project properties in Eclipse for the source paths
and needed jar files. This took several iterations as I often forgot a jar
file or installed framework (JavaJDBCFramework frequently :-/ ). I didn't
bring over any of the files that WOLips manages (ant.*, PB.project, etc.).
5. Manually edited the woproject/*.patternset files to get our needed
resources in the right places (we have several *.xml, *.jasper etc files
that we need on the classpath). The contextual menu for this is currently
broken (see WOLips bug list).
Something to remember with the incremental builder is that editing
resources or source files does not trigger a full build. With the ant
builder, we'd just edit a .java file (add space, delete space, save) which
would trigger a new full build. With the incremental builder, only modified
files are rebuilt, so we often had to use Project->Clean or manually delete
the build folder in the filesystem or Eclipse and do a refresh in Eclipse
to trigger full builds until we got the project structure stabilized. I've
not needed to do a full rebuild for a while now. Because of this, we
weren't as rigorous in our project structure with the ant builder. The
incremental builder needs your project set up in Eclipse just right.
For this project at least, everything is building, running, and debugging
smoothly (once we figured out a few quirks of the *.patternset files). Next
item to tackle is our big project with several apps and 13 frameworks. We
never got that one fully working in any previous version of Eclipse/WOLips,
but I feel confident enough to at least attempt it again now.
I'll be glad to provide any details I can if it helps someone get set up.
Logan Allred
"Shelli D. Orton"
<shelli.orto..mo To: <woproject-dev@objectstyle.org>
de.com> cc:
Subject: Build/Run Configuration Woes
08/13/2004 11:42
AM
I'm trying to understand how best to set up my builds so that things run
smoothly. Which build style should I use? Incremental or Ant? What are
the pros/cons of each?
Here's what I have:
FrameworkA
FrameworkB - which uses FrameworkA
Application1 - which uses FrameworkA and FrameworkB
<snip>
This archive was generated by hypermail 2.0.0 : Fri Aug 13 2004 - 19:16:55 EDT