cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: svn commit: r367382 - in /cocoon/trunk/lib: core/jetty-jmx-5.1.8.jar core/mx4j-3.0.1.jar core/mx4j-jmx-3.0.1.jar jars.xml
Date Tue, 10 Jan 2006 18:17:37 GMT
Jorg Heymans wrote:
> Leszek Gawron wrote:
> 
> 
> 
>>1. developers/more advanced users often use trunk snapshots even for
>>production (I have probably never used a released version :)). If so
>>there has to be a support in our build system to deploy artifacts not
>>only to apache repository but also to company's/individual's repository.
>> I am not talking here about simple 'mvn install' which only copies the
>>file on the same computer to local repo.
> 
> 
> If you want to deploy your own project artifacts (say a custom block)
> then you would just mvn release this to your repo. Why would you need to
> modify cocoon's pom.xml ?
Maybe I'm missing something but how can you do that without modifying pom?

-- 
Leszek Gawron                                      lgawron@mobilebox.pl
IT Manager                                         MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65

Mime
View raw message