You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Ralph Goers <ra...@dslextreme.com> on 2009/03/16 06:56:19 UTC
[VFS] 2.0 release
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.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
It's not necessary to get the key signed by others before using it to
sign a release.
Just create a key and add it to KEYS and upload it to a key server.
On 16/03/2009, Ralph Goers <ra...@dslextreme.com> wrote:
> I'd be happy to do all that. But my understanding is that I can't do the
> release until all those steps are completed. I'd really like VFS 2.0
> released asap. Since I'm also not on the PMC I can't even vote for the
> release. As far as I can tell I'm the only one committing code but I know
> I'm not the only one using VFS.
>
> Ralph
>
>
> On Mar 16, 2009, at 10:05 AM, Siegfried Goeschl wrote:
>
>
> > Hi Ralph,
> >
> > +) see http://www.apache.org/dev/release-signing.html
> > +) you can upload your key to a public key server even if it is not
> > trusted yet
> > +) afterwards you add it to the KEYS file and commit it
> > +) you have to join a key signing party at some point in time
> >
> > Cheers,
> >
> > Siegfried Goeschl
> >
> >
> > 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.
> > >
> > > Ralph
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
I'd be happy to do all that. But my understanding is that I can't do
the release until all those steps are completed. I'd really like VFS
2.0 released asap. Since I'm also not on the PMC I can't even vote for
the release. As far as I can tell I'm the only one committing code
but I know I'm not the only one using VFS.
Ralph
On Mar 16, 2009, at 10:05 AM, Siegfried Goeschl wrote:
> Hi Ralph,
>
> +) see http://www.apache.org/dev/release-signing.html
> +) you can upload your key to a public key server even if it is not
> trusted yet
> +) afterwards you add it to the KEYS file and commit it
> +) you have to join a key signing party at some point in time
>
> Cheers,
>
> Siegfried Goeschl
>
>
> 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.
>>
>> Ralph
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Ralph,
+) see http://www.apache.org/dev/release-signing.html
+) you can upload your key to a public key server even if it is not
trusted yet
+) afterwards you add it to the KEYS file and commit it
+) you have to join a key signing party at some point in time
Cheers,
Siegfried Goeschl
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.
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Henri Yandell <fl...@gmail.com>.
Stick one in the m2 snapshot repository on p.o.a and point
Configuration to that.
There's no release process for those, they're akin to nightly builds.
Hen
On Sun, Mar 22, 2009 at 6:19 AM, Ralph Goers <ra...@dslextreme.com> wrote:
> If we aren't going to release real soon is there any process for publishing
> a SNAPSHOT? I have a bunch of stuff for Configuration I'd really like to
> commit but I can't because Commons Configuration will now have a dependency
> on Commons VFS 2.0-SNAPSHOT.
>
> Ralph
>
> On Mar 21, 2009, at 4:55 PM, Jörg Schaible wrote:
>
>> Sergey Vladimirov wrote:
>>
>>> Personally, I would like to see some issues to be resolved before 2.0
>>> release, because they can create incompatibility with previous releases
>>> in
>>> some way.
>>> - VFS-169 is the example of such issue (changing default behavior of
>>> toString() to use friendly URI)
>>
>> this is already on my plate for 2.0 ...
>>
>>> - VFS-203 (if it's going to be fixed at all, it should be done in mayor
>>> release)
>>>
>>> Some JIRA issues do have patches and they just need to be
>>> tested/committed/closed. Before release.
>>>
>>> Anyway, +1 for 2.0 release soon - it's been too long since last release.
>>
>>
>> - Jörg
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
If we aren't going to release real soon is there any process for
publishing a SNAPSHOT? I have a bunch of stuff for Configuration I'd
really like to commit but I can't because Commons Configuration will
now have a dependency on Commons VFS 2.0-SNAPSHOT.
Ralph
On Mar 21, 2009, at 4:55 PM, Jörg Schaible wrote:
> Sergey Vladimirov wrote:
>
>> Personally, I would like to see some issues to be resolved before 2.0
>> release, because they can create incompatibility with previous
>> releases in
>> some way.
>> - VFS-169 is the example of such issue (changing default behavior of
>> toString() to use friendly URI)
>
> this is already on my plate for 2.0 ...
>
>> - VFS-203 (if it's going to be fixed at all, it should be done in
>> mayor
>> release)
>>
>> Some JIRA issues do have patches and they just need to be
>> tested/committed/closed. Before release.
>>
>> Anyway, +1 for 2.0 release soon - it's been too long since last
>> release.
>
>
> - Jörg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Jörg Schaible <jo...@gmx.de>.
Jörg Schaible wrote:
> Sergey Vladimirov wrote:
>
>> Personally, I would like to see some issues to be resolved before 2.0
>> release, because they can create incompatibility with previous releases
>> in some way.
>> - VFS-169 is the example of such issue (changing default behavior of
>> toString() to use friendly URI)
>
> this is already on my plate for 2.0 ...
Fixed, however please read the comments in the issue and add yours, we might
use a different approach instead.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Jörg Schaible <jo...@gmx.de>.
Sergey Vladimirov wrote:
> Personally, I would like to see some issues to be resolved before 2.0
> release, because they can create incompatibility with previous releases in
> some way.
> - VFS-169 is the example of such issue (changing default behavior of
> toString() to use friendly URI)
this is already on my plate for 2.0 ...
> - VFS-203 (if it's going to be fixed at all, it should be done in mayor
> release)
>
> Some JIRA issues do have patches and they just need to be
> tested/committed/closed. Before release.
>
> Anyway, +1 for 2.0 release soon - it's been too long since last release.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Sergey Vladimirov <vl...@gmail.com>.
Personally, I would like to see some issues to be resolved before 2.0
release, because they can create incompatibility with previous releases in
some way.
- VFS-169 is the example of such issue (changing default behavior of
toString() to use friendly URI)
- VFS-203 (if it's going to be fixed at all, it should be done in mayor
release)
Some JIRA issues do have patches and they just need to be
tested/committed/closed. Before release.
Anyway, +1 for 2.0 release soon - it's been too long since last release.
--
Sergey.
On Mon, Mar 16, 2009 at 8:56 AM, Ralph Goers <ra...@dslextreme.com>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.
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Sergey Vladimirov
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 17/03/2009, Ralph Goers <ra...@dslextreme.com> wrote:
>
> On Mar 16, 2009, at 5:32 PM, sebb wrote:
>
>
> > On 16/03/2009, Ralph Goers <ra...@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.
<soapbox>
IMO, that's a bad idea, as it it quite hard to find out the setting
without running Maven.
It's also not clear whether someone forgot to specify the Java version.
Unfortunately M2 needs Java 1.4+ and the compile stage uses 1.4+ libraries.
So it does not detect the problem.
I think the parent pom should have forced projects to specify the version.
</soapbox>
>
> >
> >
> > 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
Agreed, but at least it gave a clue as to the intended Java version.
>
> >
> >
> > 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.
Agreed.
Also makes it possible to test correctly using M2.
The Ant build can also be dropped.
>
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
On Mar 16, 2009, at 5:32 PM, sebb wrote:
> On 16/03/2009, Ralph Goers <ra...@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 16/03/2009, Ralph Goers <ra...@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.
Also, which Java version is targettted?
The pom files don't seem to include a definition.
Actually, just found that project.properties species source/target=1.3.
It would be helpful to include this in the Maven2 POM(s).
However, there is some Java 1.4+ code in core/ and sandbox/ as several
files use RuntimeException(Throwable).
> Also, is there a way to release a SNAPSHOT so that I can commit my Commons
> Configuration enhancements?
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 17/03/2009, sebb <se...@gmail.com> wrote:
> On 17/03/2009, Ralph Goers <ra...@dslextreme.com> wrote:
>
> > Actually, the tests are (correctly) run many times. VFS uses an interesting
> > mechanism to run the tests once for each provider type. It took me quite a
> > while to figure out what it was doing. Some providers, such as webdav, http
> > and ftp have to be run manually. I've put instructions in the doc on how to
> > do that, but you can only read it if you build the site.
>
>
> I think there is a problem with the implementation, as it looks like
> the same names are used for the surefire-reports files for different
> providers.
>
> If a test for one provider fails, the failure details will be lost
> when another provider runs the same test.
Duh - ignore that - the provider name is in the file.
>
> > As for the test jar, yes Sandbox has a dependency on it. It has to be built
> > and available for the Sandbox build to run. Maven won't do that with just
> > mvn test.
> >
> > Ralph
> >
> >
> > On Mar 17, 2009, at 5:55 AM, sebb wrote:
> >
> >
> > > On 17/03/2009, sebb <se...@gmail.com> wrote:
> > >
> > > > On 17/03/2009, Siegfried Goeschl <si...@it20one.at> wrote:
> > > >
> > > > > Hi Ralph,
> > > > >
> > > > > +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
> > > > > +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
> > > > >
> > > >
> > > >
> > > > Surely you just have to run
> > > >
> > > > mvn install
> > > >
> > > > to deploy it to your local repo?
> > > >
> > > >
> > >
> > > That worked for me.
> > >
> > > However, the test takes quite a long time, and produces lots of output.
> > > It looks as though some (most) of the tests are being run twice.
> > >
> > > The Surefire settings perhaps need to be tweaked.
> > > And/or remove any package suites.
> > >
> > >
> > >
> > > >
> > > > > Cheers,
> > > > >
> > > > > Siegfried Goeschl
> > > > >
> > > > > === START ===
> > > > >
> > > > > Downloading:
> > > > >
> > http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
> > > > > Downloading:
> > > > >
> > http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
> > > > > [INFO]
> > > > >
> > ------------------------------------------------------------------------
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO]
> > > > >
> > ------------------------------------------------------------------------
> > > > > [INFO] Failed to resolve artifact.
> > > > >
> > > > > Missing:
> > > > > ----------
> > > > > 1)
> > org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> > > > >
> > > > > Try downloading the file manually from the project website.
> > > > >
> > > > > Then, install it using the command:
> > > > > mvn install:install-file -DgroupId=org.apache.commons
> > > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > > > > -Dpackaging=test-jar -Dfile=/path/to/file
> > > > >
> > > > > Alternatively, if you host your own repository you can deploy the
> > file
> > > > > there:
> > > > > mvn deploy:deploy-file -DgroupId=org.apache.commons
> > > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > > > > -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url]
> > -DrepositoryId=[id]
> > > > >
> > > > > Path to dependency:
> > > > > 1)
> > org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> > > > > 2)
> > org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> > > > >
> > > > > ----------
> > > > > 1 required artifact is missing.
> > > > >
> > > > > for artifact:
> > > > >
> > org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> > > > >
> > > > > from the specified remote repositories:
> > > > > central (http://repo1.maven.org/maven2),
> > > > > apache.m1
> > (http://people.apache.org/repo/m1-snapshot-repository/),
> > > > > apache.snapshots
> > (http://people.apache.org/repo/m2-snapshot-repository/)
> > > > >
> > > > > === END ===
> > > > >
> > > > >
> > > > > Ralph Goers 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?
> > > > > >
> > > > > > Also, is there a way to release a SNAPSHOT so that I can commit my
> > > > > > Commons Configuration enhancements?
> > > > > >
> > > > > > Ralph
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > dev-unsubscribe@commons.apache.org
> > > > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > dev-unsubscribe@commons.apache.org
> > > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 17/03/2009, Ralph Goers <ra...@dslextreme.com> wrote:
> Actually, the tests are (correctly) run many times. VFS uses an interesting
> mechanism to run the tests once for each provider type. It took me quite a
> while to figure out what it was doing. Some providers, such as webdav, http
> and ftp have to be run manually. I've put instructions in the doc on how to
> do that, but you can only read it if you build the site.
I think there is a problem with the implementation, as it looks like
the same names are used for the surefire-reports files for different
providers.
If a test for one provider fails, the failure details will be lost
when another provider runs the same test.
> As for the test jar, yes Sandbox has a dependency on it. It has to be built
> and available for the Sandbox build to run. Maven won't do that with just
> mvn test.
>
> Ralph
>
>
> On Mar 17, 2009, at 5:55 AM, sebb wrote:
>
>
> > On 17/03/2009, sebb <se...@gmail.com> wrote:
> >
> > > On 17/03/2009, Siegfried Goeschl <si...@it20one.at> wrote:
> > >
> > > > Hi Ralph,
> > > >
> > > > +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
> > > > +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
> > > >
> > >
> > >
> > > Surely you just have to run
> > >
> > > mvn install
> > >
> > > to deploy it to your local repo?
> > >
> > >
> >
> > That worked for me.
> >
> > However, the test takes quite a long time, and produces lots of output.
> > It looks as though some (most) of the tests are being run twice.
> >
> > The Surefire settings perhaps need to be tweaked.
> > And/or remove any package suites.
> >
> >
> >
> > >
> > > > Cheers,
> > > >
> > > > Siegfried Goeschl
> > > >
> > > > === START ===
> > > >
> > > > Downloading:
> > > >
> http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
> > > > Downloading:
> > > >
> http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
> > > > [INFO]
> > > >
> ------------------------------------------------------------------------
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> ------------------------------------------------------------------------
> > > > [INFO] Failed to resolve artifact.
> > > >
> > > > Missing:
> > > > ----------
> > > > 1)
> org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> > > >
> > > > Try downloading the file manually from the project website.
> > > >
> > > > Then, install it using the command:
> > > > mvn install:install-file -DgroupId=org.apache.commons
> > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > > > -Dpackaging=test-jar -Dfile=/path/to/file
> > > >
> > > > Alternatively, if you host your own repository you can deploy the
> file
> > > > there:
> > > > mvn deploy:deploy-file -DgroupId=org.apache.commons
> > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > > > -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> > > >
> > > > Path to dependency:
> > > > 1)
> org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> > > > 2)
> org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> > > >
> > > > ----------
> > > > 1 required artifact is missing.
> > > >
> > > > for artifact:
> > > >
> org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> > > >
> > > > from the specified remote repositories:
> > > > central (http://repo1.maven.org/maven2),
> > > > apache.m1
> (http://people.apache.org/repo/m1-snapshot-repository/),
> > > > apache.snapshots
> (http://people.apache.org/repo/m2-snapshot-repository/)
> > > >
> > > > === END ===
> > > >
> > > >
> > > > Ralph Goers 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?
> > > > >
> > > > > Also, is there a way to release a SNAPSHOT so that I can commit my
> > > > > Commons Configuration enhancements?
> > > > >
> > > > > Ralph
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
Actually, the tests are (correctly) run many times. VFS uses an
interesting mechanism to run the tests once for each provider type. It
took me quite a while to figure out what it was doing. Some providers,
such as webdav, http and ftp have to be run manually. I've put
instructions in the doc on how to do that, but you can only read it if
you build the site.
As for the test jar, yes Sandbox has a dependency on it. It has to be
built and available for the Sandbox build to run. Maven won't do that
with just mvn test.
Ralph
On Mar 17, 2009, at 5:55 AM, sebb wrote:
> On 17/03/2009, sebb <se...@gmail.com> wrote:
>> On 17/03/2009, Siegfried Goeschl <si...@it20one.at>
>> wrote:
>>> Hi Ralph,
>>>
>>> +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
>>> +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
>>
>>
>> Surely you just have to run
>>
>> mvn install
>>
>> to deploy it to your local repo?
>>
>
> That worked for me.
>
> However, the test takes quite a long time, and produces lots of
> output.
> It looks as though some (most) of the tests are being run twice.
>
> The Surefire settings perhaps need to be tweaked.
> And/or remove any package suites.
>
>
>>> Cheers,
>>>
>>> Siegfried Goeschl
>>>
>>> === START ===
>>>
>>> Downloading:
>>> http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
>>> Downloading:
>>> http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Failed to resolve artifact.
>>>
>>> Missing:
>>> ----------
>>> 1) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>>>
>>> Try downloading the file manually from the project website.
>>>
>>> Then, install it using the command:
>>> mvn install:install-file -DgroupId=org.apache.commons
>>> -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
>>> -Dpackaging=test-jar -Dfile=/path/to/file
>>>
>>> Alternatively, if you host your own repository you can deploy the
>>> file
>>> there:
>>> mvn deploy:deploy-file -DgroupId=org.apache.commons
>>> -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
>>> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -
>>> DrepositoryId=[id]
>>>
>>> Path to dependency:
>>> 1) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
>>> 2) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>>>
>>> ----------
>>> 1 required artifact is missing.
>>>
>>> for artifact:
>>> org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
>>>
>>> from the specified remote repositories:
>>> central (http://repo1.maven.org/maven2),
>>> apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/),
>>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository/
>>> )
>>>
>>> === END ===
>>>
>>>
>>> Ralph Goers 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?
>>>>
>>>> Also, is there a way to release a SNAPSHOT so that I can commit my
>>>> Commons Configuration enhancements?
>>>>
>>>> Ralph
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 17/03/2009, sebb <se...@gmail.com> wrote:
> On 17/03/2009, Siegfried Goeschl <si...@it20one.at> wrote:
> > Hi Ralph,
> >
> > +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
> > +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
>
>
> Surely you just have to run
>
> mvn install
>
> to deploy it to your local repo?
>
That worked for me.
However, the test takes quite a long time, and produces lots of output.
It looks as though some (most) of the tests are being run twice.
The Surefire settings perhaps need to be tweaked.
And/or remove any package suites.
> > Cheers,
> >
> > Siegfried Goeschl
> >
> > === START ===
> >
> > Downloading:
> > http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
> > Downloading:
> > http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > Missing:
> > ----------
> > 1) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file -DgroupId=org.apache.commons
> > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > -Dpackaging=test-jar -Dfile=/path/to/file
> >
> > Alternatively, if you host your own repository you can deploy the file
> > there:
> > mvn deploy:deploy-file -DgroupId=org.apache.commons
> > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> > -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >
> > Path to dependency:
> > 1) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> > 2) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
> >
> > ----------
> > 1 required artifact is missing.
> >
> > for artifact:
> > org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2),
> > apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/),
> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository/)
> >
> > === END ===
> >
> >
> > Ralph Goers 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?
> > >
> > > Also, is there a way to release a SNAPSHOT so that I can commit my
> > > Commons Configuration enhancements?
> > >
> > > Ralph
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by sebb <se...@gmail.com>.
On 17/03/2009, Siegfried Goeschl <si...@it20one.at> wrote:
> Hi Ralph,
>
> +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
> +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
Surely you just have to run
mvn install
to deploy it to your local repo?
> Cheers,
>
> Siegfried Goeschl
>
> === START ===
>
> Downloading:
> http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
> Downloading:
> http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.commons
> -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> -Dpackaging=test-jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.commons
> -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
> 2) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository/)
>
> === END ===
>
>
> Ralph Goers 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?
> >
> > Also, is there a way to release a SNAPSHOT so that I can commit my
> > Commons Configuration enhancements?
> >
> > Ralph
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Ralph,
+) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
+) you can deploy a SNAPSHOT using "mvn -Pci deploy"
Cheers,
Siegfried Goeschl
=== START ===
Downloading:
http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
Downloading:
http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.commons
-DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.commons
-DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
2) org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository/)
=== END ===
Ralph Goers 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?
>
> Also, is there a way to release a SNAPSHOT so that I can commit my
> Commons Configuration enhancements?
>
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
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?
Also, is there a way to release a SNAPSHOT so that I can commit my
Commons Configuration enhancements?
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VFS] 2.0 release
Posted by Jörg Schaible <jo...@gmx.de>.
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.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org