Hi Colin,
Replies below.
On 07/05/2012 7:06 PM, Colin McCabe wrote:
> Hi,
>
> When I examined the Maven central repository (
search.mvn.org), I found
> only these three versions of cmake-maven: 2.8.8-b1, 2.8.7-b4, and 0.3.
>
> It seems like 0.3 only supported Visual Studio, and 2.8.8-b1 and 2.8.7-
> b4 require Java 7.
>
> First of all, why are you requiring Java 7? Are you really using the
> features of Java 7, or did you just forget to set the version when
> compiling the jar? For the project I was considering using this
> plugin for, Java 7 is a non-starter. I know that many other projects
> have the same constraint. In fact, we even have to support Java 5...
> yes, really.
There were some Java7-specific features I've used in the past. I'm
not sure whether this is still the case. Before I investigate further,
please help me understand why your requirements. Please differentiate
between having to use Java5 at build-time versus having to use it at
runtime. You can still use Java5 at runtime. The plugin only forces you
to have Java7 at build in. Is this still a problem? If so, please
explain why.
> Secondly, why only 3 versions? Are you deleting the old versions from
> the central repository? This is a very bad practice. Or did you jump
> from version 0.3 to 2.8.7-b4? I am so confused. If you are deleting
> the old versions, then I don't see how anyone can realistically hope
> to use this. We certainly don't want old versions of our software to
> become unbuildable.
I jumped from version 0.3 to 2.8.7. Prior to version 2.8.7 users
had to install CMake externally. From version 2.8.7 onward the plugin
will actually download cmake on the user's behalf, hence the version
number is now in sync with the cmake version it bundles. Don't worry, I
don't plan on removing old versions.
Gili