Jose Alberto Fernandez wrote:
>> To solve the problem we could add a importable="true"
>> attribute to the
>> project. We can post a message that warns that it's not marked as
>> importable, and if the build fails and a file was imported,
>> we can add
>> to the message a note that tells the user that the file that was
>> imported was not marked as importable.
>>
>
> I like this, but I would be even more strict, the project must be
> "importable" in order to be imported, and this also would make
> ${ant.file.projectname} and ${basedir.projectname} available.
>
> This will force an specific clear pattern for the imports and will
> make users more aware of the suttle diferences on file resolution rules.
I'm not very comfortable with special requirements on the imported files.
Xslt doesn't - and one major use case is using existing build files.
Solving the problem is easy, and it can be made customizable. All we
need is to solve the BuildFile info in the UE and make a small change
in the code that resolves.
Costin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
