Any plans to publish a new release on central?

[fifteen...@gmail.com]

Hi there,

I just tried cmake-maven-plugin, but maven central still has revision 2.8.10.2-b2. Are there any plans to publish a newer one?

And please could you compile it for Java 1.6?
I always get a
java.lang.UnsupportedClassVersionError: com/googlecode/cmakemavenproject/GenerateMojo : Unsupported major.minor version 51.0
here.

TIA,
 Martin

[Kevin S. Clarke]

Hi Martin,

I plan to do a new release this week.  While I'm at it, I'll take a look at adding support for Java 1.6.

Kevin

[15 knots]

Hi Kevin,

that's good news!

Thanks,

 Martin

2013/12/17 Kevin S. Clarke <kscl...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "cmake-maven-project-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cmake-maven-projec...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Kevin S. Clarke]

Hi,

Just a note that I pushed a new version to the central repo today: 2.8.11-b4

I made some changes to make it compatible with JDK 1.6, now, too.

Kevin

On Tuesday, December 17, 2013 11:16:43 AM UTC-5, fifteen...@gmail.com wrote:

[fifteen...@gmail.com]

Hi,

I can confirm that with version 2.8.11-b4 the

UnsupportedClassVersionError

no longer is thrown when running on a Java 1.6 VM.

Too sad, the plugin still seems to be incompatible with Java 1.6. It depends on class java.nio.file.Paths, which is not part of the 1.6 runtime:
Caused by: java.lang.NoClassDefFoundError: java/nio/file/Paths
    at com.googlecode.cmakemavenproject.GenerateMojo.execute(GenerateMojo.java:129)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    ... 20 more

Martin

[Kevin S. Clarke]

Ah, thanks.  I must have missed that one (not sure why it didn't give me an exception while the other changes did).  I'll take a look.

Kevin

--

[Kevin S. Clarke]

Yes, so it seems just changing the maven compiler to 1.6 compatibility
wasn't enough to surface all the changes that would need to be made.
I've actually installed JDK 6 now and configured my build to use it.
There are some substantial changes that would need to be made. I'll
continue to look into it.

Kevin

[cowwoc]

Ehm... with Java 8 due out in 3 months (March 18), and with Java 6
having been discontinued in April 16 2013, does it really make sense to
backport to Java 6?

Martin, doesn't your organization plan to upgrade to Java 7 now that
Java 6 has been discontinued?

Gili

[Kevin S. Clarke]

Yes, good points... and, considering backporting would require
removing lots of nice concise code and replacing it with much more
verbose code, perhaps it's just time to look forward.

I'll need to update the pom to configure the maven-compiler-plugin to
use the 1.7 compliance level again.

Kevin

[15 knots]

@cowwoc: No, we do not plan to upgrade to Java 7. But I#m sure we will be forced to do so, one day:-)

Considering backporting the plugin to Java 6, I agree: It does not make sense.

Thanks,
 Martin

2014/1/7 Kevin S. Clarke <kscl...@gmail.com>

[cowwoc]

Kevin,

I'll leave it up to you to decide how you want to proceed (is it worth the work?). If you want to go ahead, please use a separate a Java6 branch, and java6 classifier, and release that. That way the main codebase would remain on Java7.

Gili

[Kevin S. Clarke]

I was leaning towards no, but putting it in a separate branch with a
java6 classifier is a good idea. I might take a stab at that.

Thanks,
Kevin