Re: [jboss-dev] Can't perform a vfs release without updating the JBVFS releases

Also, I don't see svn commits for closed vfs issues like the following: http://jira.jboss.com/jira/browse/JBVFS-35?page=com.atlassian.jira.plugin... You need to be including the jira issue in the svn commits that apply to the issue. JBVFS-35 is marked as resolved for 2.0.0.CR1, but it must be in some previously release. I can guess its 2.0.0.Beta18 based on the date, but I don't know. Scott Stark wrote: > We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the http://jira.jboss.com/jira/browse/JBVFS > project only has releases defined up to 2.0.0.Beta12. All changes > in 2.0.0.Beta13-18 are in the 2.0.0.CR1 or no version. We need to > have a jira release for every maven release we do. > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development