On 24/08/2016 09:41, Jacques Le Roux wrote:
Le 24/08/2016 à 09:23, Julien NICOLAS a écrit :
Hi Jacques,
I don't understand what to do if we had a new file type. I understand
that something is wrong with the svn config but I don't know what.
Simple, just add it, like I did for *.less at
ht
Thanks Pierre for the explanation, I never used it so thought it also provided
storage.
Jacques
Le 24/08/2016 à 09:32, Pierre Smits a écrit :
Please keep in mind that the OEM (https://oem.ofbizci.net/oci-2) is just a
place to promote the components. That is why it lists both OFBiz controlled
Le 24/08/2016 à 09:23, Julien NICOLAS a écrit :
Hi Jacques,
I don't understand what to do if we had a new file type. I understand that
something is wrong with the svn config but I don't know what.
Simple, just add it, like I did for *.less at
http://svn.apache.org/viewvc?rev=1757468&view=rev
Please keep in mind that the OEM (https://oem.ofbizci.net/oci-2) is just a
place to promote the components. That is why it lists both OFBiz controlled
components and themes (in ASF SVN) and products that are controlled by
others (and elsewhere, e.g. GitHub).
It links through to the actual locati
Hi Jacques,
I don't understand what to do if we had a new file type. I understand
that something is wrong with the svn config but I don't know what.
For the 4 colors, it is only because my customer order included 4 theme
colors and when I push the theme in trunk, I keep them.
I like the 4 c
OK, the *.less type is not in the svn config. I'll revert, add it, and commit
again.
So again, please committers remember to do so when you commit a new file type.
While at it I really wonder if we need to have 4 colored versions of the same
theme in trunk?
I suggest to have only one and prop
