there's something wrong with your install ... this is not from the 3.5
build.xml template. i don't know how you managed to get this
build.xml, but it's not the one that ships in 3.5. We don't have
stdFrameworks and yours isn't evaluated properly because it has a
WOLipsContext.getAntFolderNa
ops! I apologize
On Sep 27, 2009, at 12:06 PM, Paolo Sommaruga wrote:
Hi,
here is woapplication task generated by a new wo application with
eclipse 3.5 + wolips 3.5.5990
The woapplication task is more than this, it extends down to:
Now I solved by copying the build.xml from a new application I jus
Hi,
here is woapplication task generated by a new wo application with
eclipse 3.5 + wolips 3.5.5990
Now I solved by copying the build.xml from a new application I just
created with eclipse-jee-ganimede + wolips 3.4.5950
Not nice, but it seems that this workaround works.
It seems that I
Hello Paolo,
When I do a search on this error, it seems to be created when the new
build.xml is not copied into your application properly. Are you sure
that you have the build.xml for an application in your application or
did you maybe copy the framework build.xml in by mistake? They are
It looks like you have an outdated XML file (yes, I know you just
copied in a new one).
What does the whole woapplication task look like?
Chuck
On Sep 27, 2009, at 11:14 AM, Paolo Sommaruga wrote:
I removed stdFrameworks="false" but I have a lot of errors
build.xml:63: There is no root
I removed stdFrameworks="false" but I have a lot of errors
build.xml:63: There is no root named '/System' in
[[ExternalFolderRoot: name = Project Local Frameworks; folder = null],
[ExternalFolderRoot: name = External Build Root; folder = null],
[ExternalFolderRoot: name = User Frameworks;
On Sep 27, 2009, at 10:37 AM, Paolo Sommaruga wrote:
Hi,
I migrated a wo application from eclipse 3.3.x to eclipse 3.5 +
wolips 3.5.5990 I replaced the build.xml file and the woproject
folder with the one obtained from a new project created on purpose
with eclipse 3.5
All works fine w
Hi,
I migrated a wo application from eclipse 3.3.x to eclipse 3.5 + wolips
3.5.5990 I replaced the build.xml file and the woproject folder with
the one obtained from a new project created on purpose with eclipse 3.5
All works fine when one run the application within eclipse
(incremental
Does anybody have any idea on how to solve this problem? I'm stuck
and would very much like to move onto actually deploying this test
app in tomcat. Any suggestions on how to get the Too many open
files thing resolved?
Seems possible that the error is just telling the truth and you really
a
On Mar 9, 2009, at 3:19 PM, Dom wrote:
Does anybody have any idea on how to solve this problem? I'm stuck
and would very much like to move onto actually deploying this test
app in tomcat. Any suggestions on how to get the Too many open files
thing resolved?
Thanks,
Dom
On Mar 9, 2009,
Does anybody have any idea on how to solve this problem? I'm stuck and
would very much like to move onto actually deploying this test app in
tomcat. Any suggestions on how to get the Too many open files thing
resolved?
Thanks,
Dom
On Mar 9, 2009, at 3:51 PM, Dom wrote:
I think the .class
I think the .classpath is good; it looks just like the one you'd get
from a brand new project and nothing like the old pre hotness
classpath file. Here's a very relevant lines from ant with -verbose;
first output upon hitting the compile target:
ZoneInfo: /usr/lib/jvm/java-1.6.0-sun-1.6.0.7
OK, and now I'm getting this:
Failed to process eclipse frameworks.
when issuing "ant war" or any other target that requires a build.
IIRC that means the .classpath file has not been updated to New
Hotness.
It could also be that a framework can't be found ... You're really
just seeing the
On Mar 9, 2009, at 11:37 AM, Dom wrote:
OK, and now I'm getting this:
Failed to process eclipse frameworks.
when issuing "ant war" or any other target that requires a build.
IIRC that means the .classpath file has not been updated to New Hotness.
Chuck
On Mar 8, 2009, at 11:16 AM, Dom
ant -verbose ... ant is retarded and doesn't show you the root cause
by default, only the top level exception.
On Mar 9, 2009, at 2:37 PM, Dom wrote:
OK, and now I'm getting this:
Failed to process eclipse frameworks.
when issuing "ant war" or any other target that requires a build.
On Mar
OK, and now I'm getting this:
Failed to process eclipse frameworks.
when issuing "ant war" or any other target that requires a build.
On Mar 8, 2009, at 11:16 AM, Dom wrote:
Thank you Mike,
Where should I put the woproject.jar on my local machine assuming
osx? Does it matter? I currently h
On Mar 8, 2009, at 8:16 AM, Dom wrote:
Thank you Mike,
Where should I put the woproject.jar on my local machine assuming
osx? Does it matter? I currently have it in my /Library/WebObjects/
lib directory, and that was more in an effort to resolve this while
messing around yesterday. I'm no
Thank you Mike,
Where should I put the woproject.jar on my local machine assuming osx?
Does it matter? I currently have it in my /Library/WebObjects/lib
directory, and that was more in an effort to resolve this while
messing around yesterday. I'm not really sure how it worked before;-)
Th
build.xml:207: Class org.objectstyle.woproject.ant.FrameworkSet
doesn't support the "eclipse" attribute.
old woproject.jar
I'm seeing this error: java.lang.NoSuchMethodError:
org.objectstyle.woproject.ant.FrameworkSet.getDir()Ljava/io/File;
old ant
upgrade to ant 1.7
ms
__
Hello all, I'm not a regular here, but have been checking out wo for a
while now. Yesterday, I upgraded to eclipse 3.4.x and did a fresh
install of wolips. I ran into the known problem with wolips.properties
initially, but manually creating the file resolved that.
However, I'm not able to b
Hi all:
I've been having a problem with ant builds from the command line in
Eclipse 3.3.1.1 with WOLips 3.3.4574.
To isolate the problem, I created a Dummy project and when I run an
ant build from the command line and then launch the app I still get
the same error:
BUILD SUCCESSFUL
To
22 matches
Mail list logo
