Re: Eclipse 3.4.1
Re: Eclipse 3.4.1
- Subject: Re: Eclipse 3.4.1
- From: Chuck Hill <email@hidden>
- Date: Wed, 29 Oct 2008 13:13:35 -0700
In the interests of brevity...
[property] Loading /Users/james/Documents/workspace/PWDA/Sources/
build.properties
Something in the build.xml is making it think that the project root is
/Users/james/Documents/workspace/PWDA/Sources'
instead of
/Users/james/Documents/workspace/PWDA
I think that all of your other problems stem from that.
Look at the top of the build.xml:
<project name="PWDA" default="build" basedir=".">
does basedir say Sources there?
Chuck
On Oct 29, 2008, at 12:56 PM, james o'loughlin wrote:
On Oct 28, 2008, at 7:45 PM, Chuck Hill wrote:
On Oct 28, 2008, at 3:48 PM, james o'loughlin wrote:
On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote:
Here is the rough checklist for upgrading ... (in my case I have
Wonder source linked into my workspace ... and I use WO 5.3.3)
- Every project's build.properties needs to have project.name and
project.name.lowercase defined
where is this defined? i don't see project.name and
project.name.lowercase in the build.properties file... maybe this
is my problem?
I don't think it is the problem below, but it will be a problem
eventually. If you create a new project after upgrading to
hotness, you can look at its build.properties to see what is used.
actually found this in the "build.xml" file and not
"build.properties".
- Check Build Path Order and put ERExtensions at the top of the
build order (that is important!)
- Do a pre-upgrade commit of everything to svn
- Turn off autobuild
- Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New
Hotness) and close Eclipse without building
new Hotness... check :)
- Download and install latest Wonder
check
- Reopen your 3.4 workspace
- Create a new temporary WonderApplication project
- Replace your old application build.xml files with new one from
temp project
- Replace your old application woproject/*.patternsets with new
ones from temp project
- Create a new temporary WonderFramework project
- Replace your old framework build.xml files with new one from
temp project
- Replace your old framework woproject/*.patternsets with new
ones from temp project
- Delete your old woproject/ant path whatever files in all projects
check
- Right-click application projects -> Properties -> Turn on
embedding (the more embed checkboxes you turn on, the less fire
Future You will be playing with ;-) )
- Clean/Rebuild all
- Test app(s)
- Commit to svn
apps build.
If you have build issues, open Build Path and check the Order of
Frameworks and push ERExtensions to the top (Mike, possibly the
automatic upgrade should do this anyway if ERExtensions is in the
classpath?)
HTH, Kieran
thank you so much for the checklist kieran!
unfortunately, i'm still running into an issue on my ant build
------------------------------
Buildfile: /Users/james/Documents/workspace/PWDA/build.xml
init.properties:
init.build:
compile:
BUILD FAILED
/Users/james/Documents/workspace/PWDA/build.xml:207: Failed to
process eclipse frameworks.
I wonder if you really have updated to new hotness. Or if that
project's .classpath has been updated to the hotness form. Maybe
try it with ant -verbose as well and see if anything looks
suspicious.
-verbose, bingo!
i get the following error when using -verbose:
BUILD FAILED
/Users/james/Documents/workspace/PWDA/build.xml:207: srcdir "/Users/
james/Documents/workspace/PWDA/Sources/Sources" does not exist
not sure why it's trying to build with /Sources/Sources? shouldn't
my build path be:
/Users/james/Documents/workspace/PWDA/Sources
-------------------------------
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: /Users/james/Documents/workspace/PWDA/build.xml
parsing buildfile /Users/james/Documents/workspace/PWDA/build.xml
with URI = file:/Users/james/Documents/workspace/PWDA/build.xml
Project base dir set to: /Users/james/Documents/workspace/PWDA/Sources
Build sequence for target(s) `build' is [init.properties,
init.build, compile, build.woapp, javaclient, ssdd, war, split,
package, build]
Complete build sequence is [init.properties, init.build, compile,
build.woapp, javaclient, ssdd, war, split, package, build,
init.install, install, clean, ]
init.properties:
[antlib:org.apache.tools.ant] Could not load definitions from
resource org/apache/tools/ant/antlib.xml. It could not be found.
[property] Loading /Users/james/Documents/workspace/PWDA/Sources/
build.properties
[property] Unable to find property file: /Users/james/Documents/
workspace/PWDA/Sources/build.properties
[property] Loading /Users/james/Library/Application Support/WOLips/
wolips.properties
Property "project.name" has not been set
Property "project.name.lowercase" has not been set
init.build:
compile:
[mkdir] Skipping /Users/james/Documents/workspace/PWDA/Sources/
bin because it already exists.
BUILD FAILED
/Users/james/Documents/workspace/PWDA/build.xml:207: srcdir "/Users/
james/Documents/workspace/PWDA/Sources/Sources" does not exist!
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:809)
at org.objectstyle.woproject.ant.WOCompile.execute(Unknown Source)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect
.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun
.reflect
.DelegatingMethodAccessorImpl
.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org
.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:
1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at
org
.apache
.tools
.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at
org
.eclipse
.ant
.internal
.ui
.antsupport
.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at
org
.eclipse
.ant
.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:
423)
at
org
.eclipse
.ant
.internal
.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
Total time: 8 seconds
-------------------------------
Total time: 1 second
------------------------------
build.xml line 207:
<wocompile srcdir="Sources" destdir="bin">
Can you post the whole wocompile clause?
<taskdef name="wocompile"
classname="org.objectstyle.woproject.ant.WOCompile" />
<mkdir dir="bin" />
<wocompile srcdir="Sources" destdir="bin">
<frameworks root="ProjectLocal" embed="false" eclipse="true" />
<frameworks root="External" embed="false" eclipse="true" />
<frameworks root="Local" embed="false" eclipse="true" />
<frameworks root="User" embed="false" eclipse="true" />
<frameworks root="System" embed="false" eclipse="true" />
<frameworks root="Network" embed="false" eclipse="true" />
<classpath>
<fileset dir="Libraries">
<include name="*.jar" />
</fileset>
<fileset dir="${wo.extensions}">
<include name="*.jar" />
</fileset>
</classpath>
</wocompile>
the temporary Wonder app i got this build.xml file from is able to
do an ANT build, NewBuildPathHotness split install dist directory
<Picture 6.png>
not sure why my build.xml is trying to use eclipse frameworks?!
That is what new hotness does.
so i looked at the SVN source and realized the eclipse frameworks
are the frameworks i've added to my eclipse project and not
"eclipse.frameworks"
https://svn.objectstyle.org/repos/woproject/branches/NewBuildPathHotness/woproject/woproject-ant-tasks/src/java/org/objectstyle/woproject/ant/FrameworkSet.java
i just went back through and removed my frameworks from my project
and added them back in. not sure why the new hotness can't find 'em?
on a side note, where is this fancy, "Add Library" window located?
http://2.bp.blogspot.com/_gRYgZfzU1BE/SL9erDHwi9I/AAAAAAAAAJo/gUxbOge02BM/s1600-h/Picture+4.png
Project - Properties - Java Build Path ... after you update to New
Hotness.
gotcha. i thought this window would appear when viewing my
frameworks. it actually appears when i add a new WO Framework.
not sure where to go from here.
Chuck
On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote:
On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote:
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips
nightly build and downloaded and installed the lastest Wonder-
latest-frameworks-5.4. Now, when I open my workspace I don't
see my WOFrameworks folder, and neither does eclipse since
nothing in the ERX framework compiles. What can I do to get
my frameworks back into my project? I tried looking at the
filters, but there are only two listed, *.class and .*
Even when I try to open Eclipse 3.3 my frameworks can no
longer be seen. Why would upgrading have blasted my
project's framework setup? And why was I dumb enough to try
this in the first place :-(
WOLips 3.4 has an entirely new classpath system. Touching a
WOLips 3.3 project with WOLips 3.4 will cause the .classpath
file to be upgraded, and it is not backwards compatible. WO
Frameworks are no longer handled as a single classpath
container, rather each framework is now managed independently
as its own classpath container (which more closely matches
reality), and they each appear as Libraries in your build
path. As far as ERX not compiling, I'm not sure what version
of the source you have, but given that the trunk of Wonder has
been upgraded to WOLips 3.4, and I check it out all the time, I
can assure you that it compiles without any errors under WOLips
3.4 straight out of SVN. If you're using WO 5.4, you will need
to change the build path of WOOGNL to remove Sources_53 and add
Sources_54, but other than that, things should work fine.
That said, nightly is not "stable" for a reason. If you're
using nightly, you should really either be on the wolips
mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html
), so you know what you're getting yourself into. There are
SUBSTANTIAL changes to the way things work in the new WOLips
that you need to be aware of.
ms
You make it sound so scary! :-)
I take it that it's stable enough though...? The only reason I'm
updating is because the new .classpath files were pushed into
the repository. I took that as an 'all clear' :-) Everything
looks fine so far (knock on wood). Any gotcha's that we should
be aware of??
Ramsey _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden