On 2011-08-27 19:11, Hervé BOUTEMY wrote:
> Le samedi 27 août 2011, Benson Margulies a écrit :
>> The doxia 1.2 POM has some rather surprising things in it. Notably,
>> the dependencyManagement picks up the version of the current project,
>> so they all tend to turn into 1.0-SNAPSHOT.
> yes, I saw it even if I don't understand how/why it does that
> AFAIK, the problem is on Doxia Tools only, isn't it?
>
>>
>> There's also the build.directory reference which leads to warnings.
> I didn't notice this one: what is it?
>
>>
>> Mayhap it would be possible to make a release just to fix this?
> Did you understand why it is causing such problems? is it fixed in actual
> trunk?
>
> In fact, a new version of Doxia Converter should be done independently from
> these problems, as the actual 1.2 uses Doxia 1.1.2, and even more: it not
> only
> *uses* but *contains* the dependencies in its jar-with-dependencies
> classifier.
> Then we need a Doxia Converter version with Doxia 1.2.
>
> But what version number should we give?
> We had already this question, but now it seems to me we made the wrong
> decision.
> We have 3 parts:
> - Doxia (core), with its modules for document and output formats
> - Doxia Sitetools, to make sites or plain documents
> - Doxia Tools, with CLI tools (converter and linkcheck)
Note that we also have maven-doxia-tools in shared components. I was
planning to move that over to the doxia project after the last Doxia
release, but I have unfortunately run out of OSS time. My plan was to
change the versioning when the move would happen, because
maven-doxia-tools is currently at 1.4.
> For the moment, Doxia and Doxia Sitetools have the same versions.
> Doxia Tools has a different version (1.2) than the Doxia version included
> (1.1.2)
>
> IMHO, Doxia Sitetools version should be decoupled from Doxia version, since
> the code does not really depends from Doxia version, and they are simply
> components for different features than Doxia (used by m-site-p and m-pdf-p
> mainly).
This is already done. It's just that they have been released
simultaneously for the past releases.
> But Doxia Tools version should stick with Doxia version, or add a suffix when
> multiple Doxia Tools versions are done for only one Doxia version, since
> these
> are CLI tools for end-users to use Doxia: without this, end-users can't
> understand (even us...).
Why? It is a separate project that is just a consumer of Doxia (core).
We don't version other projects that consume Doxia with numbers that in
some way match the Doxia version they use. This should simply be
documented on the start page of the Doxia Tools project using an
injected property ${doxiaVersion}.
> So IMHO we should release Doxia Tools 1.1.2, which is a fixed version of
> actual
> 1.2 regarding the problems we actually found.
> Then release Doxia Tools 1.2.0.1 with Doxia 1.2 dependency.
I see no reason to re-release the current version with another version
number. That is something that will confuse the users for sure.
> WDYT?
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
