[opencms-dev] Module Package format (manifest.xml)

[Bruce Norman]

Thanks -

Funny I had already started doing exactly what you described - importing the
new stuff on top of earlier import.  The lib jars in cvs did not download
properly for me (like they weren't binary) so I had to get these elsewhere
and the jakarta-poi jar file was not used at all - anyone else see this
behaviour?

-----Original Message-----
From: opencms-dev-admin at opencms.org [mailto:opencms-dev-admin at opencms.org]
On Behalf Of M Butcher
Sent: Thursday, January 22, 2004 11:25 AM
To: opencms-dev at opencms.org
Subject: Re: [opencms-dev] Module Package format (manifest.xml)


LOL... I'm working on the same thing right now (working on a 1.5 release 
of the Lucene module). How I've done it up to now is import the older 
version of the module, then import the new stuff, then export the module 
again. Very ugly.

Alternatively, you can unzip the earlier module and copy the old 
manifest to the new and then edit it by hand.

If you (or anyone else, for that matter) can find a better way, please 
tell me!

Matt

Bruce Norman wrote:
> I have successfully compiled the Lucene 1.4 code and would like to 
> install & test the module.  How do I create the manifest.xml file that I 
> assume is used by opencms to import the module?  I could hack an older 
> one but assume there is a more elegant / safer method.
> 
>  
> 
> Thx
> 
>  
> 
> Bruce Norman
> 

_______________________________________________
This mail is send to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://mail.opencms.org/mailman/listinfo/opencms-dev