Hi Rodney,

Yes, we defintely want to have a working tdk-2.2 no matter what. It will
certainly help a lot of users, new or veteran.

You have done an exceptional job. You are not wasting your time at all.
I appreciate all the great, helpful tips you have posted.

Thank you very much.

Wei

Rodney Schneider wrote:
Hi all,

Apologies for replying to my own email again...

Do you want me to build a working TDK or not?

The reason I am concerned about this is that I feel that Turbine releases should be quality releases. Currently, you can't even build and run newapp without getting errors. I realise that the TDK is disappearing, but that will only happen if and when someone writes a small sample application, which may not happen for a long time. I did give a -1 on releasing the TDK, but Martin released it anyway.

If you don't want to give me commit access to the tdk repo (I know I haven't made any major contributions to Turbine so this is understandable), I could just untar the current TDK release, apply my fixes and tar it up again. Does this sound like the way to go?

If I do this, will you replace the tdk-2.2.tar.gz file in the downloads directory with the new one?

Am I wasting my time trying to help you out?

Thanks,

-- Rodney


On Wed, 11 Dec 2002 10:52, you wrote:

Hi Martin (and other commiters),

It seems you are too busy to maintain the TDK.

People are starting to use the broken TDK 2.2 release.  I am
volunteering to build a working release for you and I'll even
maintain the TDK for the next few months to ensure that any necessary
fixes make it in.

However, in order to do this properly, I'll need CVS commit access to
the jakarta-turbine-tdk repository and I'll need someone to explain
the build process.

What do you think?

-- Rodney

On Mon, 9 Dec 2002 12:47, you wrote:

Hi Martin,

Thanks for all your hard work getting the Turbine and Torque
releases out the door!

I noticed you went ahead and released a broken TDK 2.2 :(

There has already been an email to the turbine-user mailing list
asking about the errors that I described below :(

This is exactly what I was worried about.  Releasing a broken TDK
was a bad idea.  We need to fix this ASAP!!

The fixes I mentioned below would take about 5 minutes to fix and I
would really appreciate it if you could do this soon.  Otherwise,
if you explain how to build the TDK (ie: send me your
build.properties) I will build a working TDK release for you.

I just finished downloading the TDK 2.2 release and applying my
fixes. This is what I did:

------------------------------
# cd $TDK_HOME/tdk/apps/2/src/conf
# rm second-schema.xml third-schema.xml
# vi id-table-schema.xml
   (changed "<database>" to "<database
name="@DATABASE_DEFAULT@">") (see TRQS35 for this patch)
# cp ~/log4j.properties .
   (See TDKS11 for the log4j.properties file)
# cd $TDK_HOME/tdk/apps/2
# vi build.xml
   (added target to copy log4j.properties to WEB-INF/classes after
    compile.  See TDKS11 for this patch)
------------------------------

Please make these changes and release a working TDK!

Sometimes I wish I had CVS commit access...

Regards,

-- Rodney

On Fri, 6 Dec 2002 11:29, you wrote:

On Thu, 5 Dec 2002 18:20, you wrote:

Rodney Schneider wrote:

Hi Martin,

Are you planning on releasing the TDK as well?  The fixes to
make it work are very minor, as mentioned in one of my
previous posts:
http://archives.apache.org/eyebrowse/ReadMsg?listName=turbine
-d ev @ja karta.apache.org&msgNo=12288

If I knew how to build the TDK, I would fix it myself :)
ant test ;-)

i don't think it'S good to release a final tdk as it always
causes problems .. i would prefere to have an example file
structure + some docs
Hi Martin,

I agree that, in the future, we should scrap the TDK.  However,
there are many people out there already using TDK 2.2 beta
versions and release candidate versions, so I think it would be
best to release a final version of TDK 2.2.  I think we should
scrap the TDK after the 2.2 release.

I am happy to build a final working TDK 2.2, however, I just
tried "ant test" and got the following error:

-----------
prepare:
BUILD FAILED
/home/rodney/jakarta/jakarta-turbine-tdk/build.xml:236:
/home/rodney/jakarta/jakarta-turbine-tdk/src/tdk/task not found.
-----------

Here's what the "prepare" target looks like in build.xml:
-----------
<target name="prepare">
 <copy todir="${tdk.build.dir}/src">
   <fileset dir="${tdk.src}/task"/>
 </copy>
</target>
-----------

However, the jakarta-turbine-tdk repository doesn't contain a
"task" directory.

Could you send me the build.properties file you are using to
build the TDK?

Thanks,

-- Rodney

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
Wei He, Ph.D.
Email: [EMAIL PROTECTED]
Voice: (845)359-5621
Fax:   (845)359-1631


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to