Hi Carlos,
I have no objections to that ... however then I would also add some more
explanation to the exclusion in the pom files rat-exclusion.
Chris
Am 05.05.20, 10:33 schrieb "Carlos Rovira" <carlosrov...@apache.org>:
Hi Chris,
I'd like to have it "at hand" in the project. What about to move to some
location. I think you suggested /src/assets or something like that
Moving to other separate repo or CMS make it very cumbersome. I think that
way we get both: not add it to a final output and as well get closer to
manage in the project so we can modify and put the output in the resources
folder
El mar., 5 may. 2020 a las 10:18, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:
> Hi folks,
>
> the discussion on the release brought up the existence of the afdesign
> files in one of the examples.
>
> These file seem to be the source project files Carlos used to create some
> vector-graphics, so I think it’s good that they are available in the
> project.
>
> However the current location is not ideal.
>
> First off all as it’s in the src/main/resources, they will be included in
> any library of application, which is probably not what we want.
>
> On the other side it’s sort of a binary file as you need some third party
> tool to edit it.
>
> The other thing is, that If someone uses the SVG and edits that … as soon
> as someone then edits the original project file again to generate a new
> SVG, the direct SVG changes get overwritten. Perhaps it’s a good idea to
> put the project files somewhere else and to add a comment to the generated
> SVGs to where to find the sources for the original file.
>
> How about adding the afdesign files to either confluence or some separate
> repo? Otherwise I bet this will come up every now and then.
>
> Chris
>
--
Carlos Rovira
http://about.me/carlosrovira
