When VFS went from 1.0 to 2.0 the API was not compatible. This meant the
package names had to change and the groupId/artifactId in the pom had to be
different. If the new release is compatible with the prior release I would
keep the naming conventions the same. Otherwise you run the risk of peo
I'm not sure I can help with tagging and deploying as I don't have the
permissions. However, I'm happy to help test the RC's, confirm MD5s, and
provide non-binding votes.
- Original Message -
From: "Bernd Eckenfels"
To: "Commons Developers List"
Sent: Wednesday, December 3, 2014 3:
Hello.
On Wed, 03 Dec 2014 10:13:08 +0100, Thorsten Kiefer wrote:
Hi,
the port is now finished.
The code may still contain bugs.
Maybe alpha-state.
But if you like it, you can add it.
Thank you for offering code to enhance the scope of Commons Math.
Yet I must emphasize that one of the goals o
Hi,
the port is now finished.
The code may still contain bugs.
Maybe alpha-state.
But if you like it, you can add it.
Best Regards
Thorsten Kiefer
Am 17.11.2014 um 23:57 schrieb Thorsten Kiefer:
Hi,
I decided to port it to java, and if you should like it, you can extend
[Math] with RL algorith
Gary,
Thank you very much!
On Mon, Dec 1, 2014 at 2:52 PM, Gary Gregory wrote:
> Israel,
>
>
> The sandbox is not released as a jar for licensing reasons IIRC. You have
> to check it out of SVN and build it yourself.
>
> Gary
>
> On Mon, Dec 1, 2014 at 2:53 AM, Israel Malachi
> wrote:
>
> > He
Hello,
I checked the release-plugin documentation and I cannot find a way to
specify different tags for the usage inside the prepared POM and the
Tag which should be used for actually tagging.
I also think this is pretty uncommon, and I would go with using the
final release version tag (commons-v
