That is why I 'polled' the masses: to find out if anyone is attached to our current packaging. Fortunately the @dev subscribers aren't attached to the current packaging, so we can move to the default assemblies.
Martijn On 1/24/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
but there is no longer the pain of sf.net releases! since all our future (save 1.2.5) will be asf where you just drop files into an ftp server. so if we use default maven packaging it will remove that burden from you. -igor On 1/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > Because I like our current assembly: source and binary in one package > per project. > > Splitting things up into src/bin is really a pain with the sf.net file > release system. Doubling the number of artifacts would increase the > release manager's workload considerably (twice the number of files to > upload, twice the agony of attaching files to a release package, twice > the agony of updating the file information). > > The reason for this thread is to see what can be done to make it more > easy in the future. Not for our current sf.net releases (they will > remain the same). > > Martijn > > On 1/23/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > On 1/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > > > If/when we are going to use the standard/default maven supplied > > > templates, then we will have the following distributions readily > > > available: > > > > http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html > > > > > > why arent we already? > > > > -igor > > > > > > > -- > Vote for Wicket at the > http://www.thebeststuffintheworld.com/vote_for/wicket > Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! > http://wicketframework.org >
-- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org