stevedlawrence commented on issue #133:
URL: https://github.com/apache/daffodil-sbt/issues/133#issuecomment-3427515467
I think we could do that. A similar option is to have some sort of range
using semantic versions, which could also let you exclude things and doesn't
rely on choosing a defaults to exclude, for example:
```scala
daffodilSemanticCrossVersions = Some(">=3.7.0 <3.9.0 || >=4.0.0")
```
That said, I kind of don't like the idea of automatically changing cross
versions. Otherwise it means a project could publish different versions
depending on what version of sbt-daffodil is available at the time of building.
I think the recommend usage wants to use pinned daffodilVersion and pinned
crossDaffodilVersions for production level schema projects. And only for
schemas that are examples, proof of concepts, etc, then its fine to have
versions change to whatever the latest is. And I would suggest in those cases
cross versions is probably less important.
So it's either just test with the latest version that's available (and no
cross versions), or explicitly pin the versions you care about and supporting
new versions requires a change + version bump.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
