Due to end of scala-tools.org (and end of maven 2 support), the next
version 2.16.0 will move from
groupId : org.scala-tools
artifactId : maven-scala-plugin
to
groupId : net.alchim31.maven
artifactId : scala-maven-plugin (follow maven 3 rules)
You can access a snapshot from
repository : https://oss.sonatype.org/content/repositories/snapshots/
<groupId>net.alchim31.maven</groupId>
<artifactId>scala-maven-plugin</artifactId>
<version>2.16.0-SNAPSHOT</version>
Also, I would :
* rename as "scala-maven-plugin" the git repository (github) to mirror
the change.
* move the license from "Apache Software License 2.0" to UNLICENSE
(see http://unlicense.org/)
WDYT ?
+1 from me.
Would it also make sense to bump up the major version number?
- Indrajit
On Tuesday 6 March 2012 at 4:41 AM, Josh Suereth wrote:
> +1 from me.
> On Mar 5, 2012 7:53 AM, "David Bernard" <david.be...@gmail.com (mailto:david.be...@gmail.com)> wrote:
> > Hi,
> >
> > Due to end of scala-tools.org (http://scala-tools.org) (and end of maven 2 support), the next
development is minimal (try to fix bug, and react to environment
changes, issues, merge pull request)
I'll probably remove goal scala:cs in the next version (in this case
the version number will bump).
> Why was the Apache License no good? Did it not have a waranty section or
> something?
I prefer UNLICENSE because i thing it matches more the project/code
life : no copyright, no owner (anyone can fork, release).
The code/project can live out of "our jurisdiction".
>
> Regards,
>
> Bryan Hunt