On Jan 26, 2009, at 2:46 PM, Michael Hast wrote:
> I am sorry about my vague question. The build fails when using
> WOLips' woproject.jar file:
>
> /Users/mhast/Developer/eclipse_workspaces_3_4_1/dss/DSSAntTools/
> generic.xml:38: java.lang.NullPointerException
> at
> org
> .apache
> .tools
> .ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
> at
> org
> .apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:
> 394)
> at
> net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:
> 259)
> at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268)
> at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:299)
> at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
> 288)
> at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 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)
>
> generic.xml: line 38 (is the wocompile call)
> <target name="generic.project.compile"
> depends="generic.project.environment,generic.project.prepare">
> <wocompile srcdir="${project.dir}/${sources.dir}" destdir="$
> {build.classes}" debug="on" optimize="off" deprecation="on" source="$
> {compiler.source}" target="${compiler.target}">
> <classpath>
> <fileset dir="${project.dir}/Libraries">
> <include name="**/*.jar" />
> </fileset>
> </classpath>
> <frameworks dir="${wo.frameworks}" includesfile="$
> {project.deployment.dir}/woframeworklist">
> </frameworks>
> <frameworks dir="${project.build.root.dstroot}" includesfile="$
> {project.dir}/frameworklist">
> </frameworks>
May I suggest some more modern Ant?
<wopath id="project.classpath">
<frameworks root="User" eclipse="true" />
<frameworks root="Library" eclipse="true" />
<frameworks root="System" eclipse="true" />
</wopath>
wopath is like classpath, but it understands WO frameworks.
Chuck
>
> </wocompile>
> </target>
>
> WOnder's WOCompile class in woproject.jar:
> 1606 Thu Jan 11 18:49:34 MST 2007 org/objectstyle/woproject/ant/
> WOCompile.class
>
> WOLips' WOCompile class in woproject.jar:
> 1626 Thu Jan 22 03:21:12 MST 2009 org/objectstyle/woproject/ant/
> WOCompile.class
>
> Why are the 2 WOCompile classes different? Where did Project WOnder
> gets its woproject.jar from?
>
> Michael.
>
> Mike Schrag wrote:
>>>> :-) I found out. Use WOnder's woproject.jar. WOOOHOOO !!! But why?
>>> Isn't that a question for you? Why did the version in WOLips not
>>> work?
>> "not working" is just too vague to be able to diagnose ...
>>>> Is it because WOLips does not use the ant-based incremental
>>>> builder? Why shouldn't the taskdef's like WOCompile match up?
>>> What does not match up?
>> DEFINITELY the implementation of these ant tasks is different, so
>> I'm not terribly surprised. Wonder also manages dependencies in
>> sort of its own way. I despise build systems, though, so I leave
>> these problems for other people.
>> ms
>
> --
> Tel: (520) 572-9410
> Desert Sky Software: www.desertsky.com
> Specializing in the Development and Hosting of
> e-Business Applications.
>
-- Chuck Hill Senior Consultant / VP DevelopmentPractical 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
This archive was generated by hypermail 2.0.0 : Mon Jan 26 2009 - 18:23:17 EST