Closed dkager closed 8 years ago
Don't like so much your idea of having two counterparts.
Or rather have the checkout and the script in an optional profile. This would also make the Maven build independent of SVN/Mercurial (https://github.com/daisy/pipeline-mod-braille/issues/28).
I second this. I’ll look at it.
In 83c3f20. There are still failing tests mucking things up on Windows, but it's a step forward.
Some comments:
-Pcheckout-tables
. Not sure if that's the case now.Also (detail) the liblouis-mathml doesn't need to be activated because there were no real code changes (except for those warnings you fixed).
Are you saying instead of activating on Unix the profile should be completely manual? In that case just remove the
(There was a code change: I removed an unused variable. Oh ho ho!)
OK, reopening. I will fix this either today or next week. It's a good way to get to know Maven.
I’m still not sure why we don’t just put the tables in main/resources.
Yes that's exactly the plan. I'm going to take care of that. In addition I want to keep the script because it makes moving to a newer version easier.
(There was a code change: I removed an unused variable. Oh ho ho!)
I know... I mean if a module isn't going to be included in the next release it's preferable to have it deactivated so it's not build for no reason. Never mind, not a big deal.
If you keep the script, let's add it in an optional profile as you said, and maybe use this. I tried this locally and while the script obviously doesn't run on Windows the plugin seems to be a lot easier to understand.
Fixed by 4cb07d5dd2a35fc0d0da345ad2617168ae30f6ef
Update pipeline-braille-utils/liblouis-utils/liblouis-mathml/pom.xml: