-
1. Re: JBoss under configuration management
starksm64 Feb 21, 2005 2:27 PM (in response to tquas)You would have to provide a custom DeploymentFilter implementation to filter out:
<!-- The Filter specifies a java.io.FileFilter for scanned directories. Any file not accepted by this filter will not be deployed. The org.jboss.deployment.scanner.DeploymentFilter rejects the following patterns: "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK", "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state", ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS", "TAGS", "core", "tags" --> <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>
It would be as simple as:import org.jboss.deployment.scanner.DeploymentFilter; public class MyDeploymentFilter extends DeploymentFilter { public DeploymentFilter() { super(); addSuffix(".svn"); } }
We need to externalize the suffixes of the default DeploymentFilter so that this is simple to configure. There is a feature request for this:
http://jira.jboss.com/jira/browse/JBAS-1494 -
2. Re: JBoss under configuration management
tquas Feb 22, 2005 3:52 AM (in response to tquas)Thanks, Scott, for the quick response. I appreciate you putting a feature request in Jira. Could you please give a rough estimate when this will be available? I'm asking because we don't have any JBoss customization code yet, and integration-wise I'd prefer not to open that can at the moment.
Would it be an option to add '.svn' to the current implementation of org.jboss.deployment.scanner.DeploymentFilter and roll this feature out with the next release of JBoss before going for the freely configurable solution? I guess this would save us both some time.
Thanks again,
-tom -
3. Re: JBoss under configuration management
tquas Feb 23, 2005 3:25 AM (in response to tquas)Ok, I was a little too quick with my judgement. It wasn't JBoss' fault. The DeploymentFilter implementation already has support for filtering out files starting with a '.'--obviously, '.svn' is a match here.
I forwarded the problem to the Subversion group. At the current stage, I can say that there seems to be a difference between importing/adding large binaries over svn+ssh:// and file://. The latter worked for me, whereas the former caused the trouble.
Sorry for the inconvenience.