You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Brekke, Jeff" <Je...@qg.com> on 2002/01/30 22:57:48 UTC

RE: cvs commit: jakarta-turbine-2 build-torque.xml build.properti es build.xml build-turbine-sql.xml

The update-jars target would bring down the dependant jars into your
${lib.repo} ( co jakarta-turbine-3 and try it ).
The old build files in jakarta-turbine-2/build use the jakarta-turbine-2/lib
directory.  I guess that build stuff could be considered deprecated after
the other is working.  Going into jakarta-turbine-2/build and building there
should have always worked and I'll leave that alone.

-----------------------------------------------------------------
Jeffrey D. Brekke                                   Quad/Graphics
Jeff.Brekke@qg.com                              http://www.qg.com
-----------------------------------------------------------------



> -----Original Message-----
> From: Paul Spencer [mailto:paulsp@apache.org]
> Sent: Wednesday, January 30, 2002 3:49 PM
> To: Turbine Developers List
> Subject: Re: cvs commit: jakarta-turbine-2 build-torque.xml
> build.properti es build.xml build-turbine-sql.xml
> 
> 
> Jeff,
> As a test, I recommend you do a fresh "cvs checkout" and then 
> a build. 
> Make sure only the jars downloaded by the "cvs checkout" are 
> used in the 
>   build.
> 
> Brekke, Jeff wrote:
> 
> > With the recent Global Cache patch and test case which was 
> written to use
> > cactus, I'm working on integrating some testing build xml's 
> with t2 and will
> > add in Jason's update-jars target also.  This should 
> alleviate some of the
> > pain temporarily with building t2 from the build*.xml's in 
> the root.  I'll
> > leave the build/* stuff alone for now except to remove the 
> compiling and
> > running of the test cases.
> > 
> > -----------------------------------------------------------------
> > Jeffrey D. Brekke                                   Quad/Graphics
> > Jeff.Brekke@qg.com                              http://www.qg.com
> > -----------------------------------------------------------------
> > 
> 
> Paul Spencer
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <ma...@jakarta.apache.org>
> For additional commands, e-mail: 
<ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: cvs commit: jakarta-turbine-2 build-torque.xml build.properti es build.xml build-turbine-sql.xml

Posted by Paul Spencer <pa...@apache.org>.
Jeff,
I have :
1) checked out turbine-3
2) defined my library repository
3) set lib.repo
4) load the library repository with "ant update_jars"
5) Build turbine-3 without errors :)

I am sure this has been discussed. IMHO the lib directory contained the 
jars the are known to work with turbine, and reflect the "supported" 
versions.  I understand the value of building with the latest version of 
a jar, i.e. velocity, while in a development mode, but a release should 
contain all of the required jars in the distribution.  Thus the lib 
directory should NOT be considered deprecated.

I did get error when building turbine-2 after doing an "ant clean".  The 
  errors involved a failure to import/"resolve symbols" (Not all error 
are listed, but I this should be a representative sample):
     [javac] import javax.servlet.http.Cookie;
     [javac] import javax.servlet.ServletConfig;
     [javac] import javax.servlet.ServletContext;
     [javac] import javax.servlet.http.HttpServletRequest;
     [javac] import javax.servlet.http.HttpServletResponse;
     [javac] import javax.servlet.http.HttpSession;
     [javac] import javax.servlet.http.HttpSessionBindingListener;
     [javac] import org.apache.ecs.Document;
     [javac] import org.apache.ecs.Element;
     [javac] import org.apache.ecs.StringElement;
     [javac] import org.apache.ecs.filter.CharacterFilter;
     [javac] import org.webmacro.servlet.WebContext;
     [javac] import javax.sql.ConnectionEventListener;
     [javac] import javax.sql.ConnectionEvent;

Paul Spencer


Brekke, Jeff wrote:

> The update-jars target would bring down the dependant jars into your
> ${lib.repo} ( co jakarta-turbine-3 and try it ).
> The old build files in jakarta-turbine-2/build use the jakarta-turbine-2/lib
> directory.  I guess that build stuff could be considered deprecated after
> the other is working.  Going into jakarta-turbine-2/build and building there
> should have always worked and I'll leave that alone.
> 
> -----------------------------------------------------------------
> Jeffrey D. Brekke                                   Quad/Graphics
> Jeff.Brekke@qg.com                              http://www.qg.com
> -----------------------------------------------------------------
> 
> 
> 
> 
>>-----Original Message-----
>>From: Paul Spencer [mailto:paulsp@apache.org]
>>Sent: Wednesday, January 30, 2002 3:49 PM
>>To: Turbine Developers List
>>Subject: Re: cvs commit: jakarta-turbine-2 build-torque.xml
>>build.properti es build.xml build-turbine-sql.xml
>>
>>
>>Jeff,
>>As a test, I recommend you do a fresh "cvs checkout" and then 
>>a build. 
>>Make sure only the jars downloaded by the "cvs checkout" are 
>>used in the 
>>  build.
>>
>>Brekke, Jeff wrote:
>>
>>
>>>With the recent Global Cache patch and test case which was 
>>>
>>written to use
>>
>>>cactus, I'm working on integrating some testing build xml's 
>>>
>>with t2 and will
>>
>>>add in Jason's update-jars target also.  This should 
>>>
>>alleviate some of the
>>
>>>pain temporarily with building t2 from the build*.xml's in 
>>>
>>the root.  I'll
>>
>>>leave the build/* stuff alone for now except to remove the 
>>>
>>compiling and
>>
>>>running of the test cases.
>>>
>>>-----------------------------------------------------------------
>>>Jeffrey D. Brekke                                   Quad/Graphics
>>>Jeff.Brekke@qg.com                              http://www.qg.com
>>>-----------------------------------------------------------------
>>>
>>>
>>Paul Spencer
>>
>>
>>
>>--
>>To unsubscribe, e-mail:   
>><ma...@jakarta.apache.org>
>>For additional commands, e-mail: 
>>
> <ma...@jakarta.apache.org>
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 
> 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>