ect setups), then it should work.
>>
>> yes, it would make sense to have an optional configuration property in the
>> maven-sling-plugin to support this use case.
>>
>> stefan
>>
>>>-Original Message-
>>>From: Julian Sedding [mailto:jsedd...
have an optional configuration property in the
> maven-sling-plugin to support this use case.
>
> stefan
>
>>-Original Message-
>>From: Julian Sedding [mailto:jsedd...@gmail.com]
>>Sent: Thursday, December 14, 2017 9:35 AM
>>To: Sling Developers List
>>Subject
Julian Sedding [mailto:jsedd...@gmail.com]
>Sent: Thursday, December 14, 2017 9:35 AM
>To: Sling Developers List
>Subject: Re: Maven Sling Plugin - fsmount
>
>Hi Stefan
>
>Thanks again for your reply. However, I still don't understand why you
>think I need to use "
gt; stefan
>
>
>>-Original Message-
>>From: Julian Sedding [mailto:jsedd...@gmail.com]
>>Sent: Wednesday, December 13, 2017 2:32 PM
>>To: Sling Developers List
>>Subject: Re: Maven Sling Plugin - fsmount
>>
>>Hi Stefan
>>
>>Thanks
fsresource implementation; i'm not
sure if it makes sense to integrate this special usecase also in the logic of
the sling:fsmount goal.
stefan
>-Original Message-
>From: Julian Sedding [mailto:jsedd...@gmail.com]
>Sent: Wednesday, December 13, 2017 2:32 PM
>To: Sling Develo
Hi Stefan
Thanks for your reply.
I was hoping that we could avoid generating build artifacts inside the
"src" folder. It just doesn't feel quite right. Also, I would like to
locate the respective "*.ts" and "*.scss" files in the location where
the compiled "*.js" and "*.css" files end up. I
hello julian.
yes, i think your assumptions are right. in case of filevault project there is
currently no way to add some "custom additional mappings" (although you could
of course add an additional mapping with only "files and folders" only for your
target dir, when there are no content
