On Mar 16, 2009, at 5:32 PM, sebb wrote:
On 16/03/2009, Ralph Goers <ralph.go...@dslextreme.com> wrote:
On Mar 16, 2009, at 3:31 PM, Jörg Schaible wrote:
Hi Ralph,
Ralph Goers wrote:
I have finished the work to implement webdav versioning support
in VFS
trunk. I would like to take advantage of this in Commons
Configuration
(that code is also complete) but to do so I need a release of VFS
2.0.
What must be done to accomplish this? FWIW I don't yet have a PGP
key
so I kind of get stuck at that spot in the "creating releases"
instructions.
I'd like to fix VFS-169 first. I have a complete different
approach than
Frank. If you don't mind, I'll commit it directly as soon as
possible.
That's fine. Also, while you do this you might want to review the
project
and make sure it has everything for a proper release. I will be
doing the
same?
There seem to be a few java files that don't have AL headers. The
source of these needs to be established and the AL header added if OK.
Thanks, I'll take a look.
Also, which Java version is targettted?
The pom files don't seem to include a definition.
They are inherited from the commons parent pom.
Actually, just found that project.properties species source/
target=1.3.
It would be helpful to include this in the Maven2 POM(s).
project.properties don't apply. They are left over from the maven 1
build. That should really be deleted along with the project.xml
However, there is some Java 1.4+ code in core/ and sandbox/ as several
files use RuntimeException(Throwable).
Hmm. I thought it was targeted at 1.3 but I wonder how that could be.
In fact, a grep on vfs-1-trunk shows it was also doing that. Given
that, I would say that changing it to 1.4 would be the correct thing
to do.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
