Re: [imaging] release 1.0 state?

Hi, Am 22.08.2013 22:01, schrieb Gary Gregory: Hi all (Damjan), What state is the code in WRT a 1.0 release? I'm also interested to get the release done. I had a quick look at JIRA and couldn't find any big blockers. Are there any issues with the build? Any other unsolved TODOs? I'm with the

[imaging] release 1.0 state?

Hi all (Damjan), What state is the code in WRT a 1.0 release? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action

Re: Need for an alternatives to the main line of code.

Le 22/08/2013 06:27, James Ring a écrit : > Seems to me that a more distributed change control system like git would > allow would-be contributors to put their code up for scrutiny without > having to create sandbox projects and the like. You can already do it this way if you want. Look at http://

Re: svn commit: r1516533 - /commons/cms-site/trunk/content/resources/.htaccess

Thanks for the tip, Seb! Matt On Thu, Aug 22, 2013 at 1:25 PM, wrote: > Author: mbenson > Date: Thu Aug 22 18:25:28 2013 > New Revision: 1516533 > > URL: http://svn.apache.org/r1516533 > Log: > CMS commit to commons by mbenson > > Modified: > commons/cms-site/trunk/content/resources/.htacc

Re: Multimodule site publish

Followup: site:stage gets the directory under "staging" from the distributionManagement URL. Matt On Thu, Aug 22, 2013 at 1:17 PM, Matt Benson wrote: > The commons-parent POM configures the maven-scm-publish-plugin to take > content from ${project.reporting.outputDirectory}, typically set to

Re: Multimodule site publish

The commons-parent POM configures the maven-scm-publish-plugin to take content from ${project.reporting.outputDirectory}, typically set to target/site. At least for the MM components, this needs to be something like ${project.build.directory}/staging/${commons.componentid}--I'm admittedly not sure

Re: Need for an alternatives to the main line of code.

I agree with James that this is a problem that git has already solved. For the changes I'm working on I have already cloned from the git mirror and plan to upload the patch as a fork + pull request on github. I think the "branchyness" of distributed version control makes it easy to have several

Re: Multimodule site publish

Was going to mention that functor's website had the same problem. Building the website locally works fine too. https://issues.apache.org/jira/browse/FUNCTOR-25 > > From: Matt Benson >To: James Carman >Cc: Commons Developers List >Sent: Thursday, August 22, 2

Re: Multimodule site publish

When published. Everything's fine locally. I note the same problem with the published functor site, though not with JCI. I haven't yet determined what the difference is, however. Matt On Aug 21, 2013 10:16 PM, "James Carman" wrote: > Didn't come through when published or locally? > > On Wednesda

Re: svn commit: r1516350 - /commons/cms-site/trunk/content/resources/.htaccess

On 22 August 2013 02:09, wrote: > Author: mbenson > Date: Thu Aug 22 01:09:46 2013 > New Revision: 1516350 > > URL: http://svn.apache.org/r1516350 > Log: > CMS commit to commons by mbenson > > Modified: > commons/cms-site/trunk/content/resources/.htaccess > > Modified: commons/cms-site/trunk/

Re: svn commit: r1516326 - /commons/sandbox/weaver/trunk/pom.xml

AFAIK the can be the original simpler URL; it's just the scmPubUrl must of course be where the files are uploaded. On 22 August 2013 02:00, Olivier Lamy wrote: > Maybe have a look at all redirect in .htaccess file :-) > > http://svn.apache.org/repos/asf/commons/cms-site/trunk/content/resources/.

Re: Need for an alternatives to the main line of code.

On 22 August 2013 05:27, James Ring wrote: > Seems to me that a more distributed change control system like git would > allow would-be contributors to put their code up for scrutiny without > having to create sandbox projects and the like. > > If enough people get behind some patches, they could i