Re: Eclipse projects are nice but...

[JacobFeldman]

Agree. We will (probably) mavenize JSR-331 as soon as time allows. At the same time being aware that CP community is not extremely friendly even to the basic Java we are trying to stay away from discussions about Ant, Maven, or Gradle.

Meanwhile, there is nothing that prevents you to incorporate JSR-331 into your own Maven-based project. If you want to contribute an example, you are very welcome.

On Wednesday, February 13, 2013 5:28:06 PM UTC-5, Bryan Absher wrote:

Wouldn't it be better to create maven artifacts?

I think that Choco is the only project supported now that uses maven, however since maven is becoming more and more popular shouldn't these adapters and the JSR-331 classes be in maven as well?

Thanks,

Bryan

[Werner Keil]

How about posting at least the public JSR API to MavenCentral that way, too?;-)

Werner

[JacobFeldman]

Julien,

I simply haven't had time to mavenize the JSR331 yet. I will create a prototype project for Concrete and send you access attributes to the SVN in a personal email.

Jacob

On Wednesday, May 22, 2013 11:49:49 AM UTC-4, Julien Vion wrote:

I compiled and published the artifacts on my Concrete/CSP4J solver repository at http://cspfj.sourceforge.net/repository using SBT (should be compatible with Maven).

Organization is "org.jcp", artifact name is "jsr331", and version is "1.1.1".

I encountered a few encoding issues during compilation, i.e., " ” " symbols in some JavaDoc comments that did not conform to either UTF-8, UTF-16 nor Latin-1 (could not figure the correct encoding, btw my version of Eclipse does not cover any other encodings). Also got a few other warnings during JavaDoc compilation with @link keywords. The jar will probably be useable anyway.

[fmj...@gmail.com]

I also would like the jsr331 jars to be available through maven, it would make its usage much easier.

Has there been progress on this?