[ 
https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632257#action_12632257
 ] 

Gunnar Wagenknecht commented on LUCENE-1344:
--------------------------------------------

Michael, I solved the issue with {{${src.dir}}}. 

The property is initially set the following way:
{{{
<property name="src.dir" location="src/java"/>
}}}

This resolves the path and sets the property to the actually path. It is then 
inherited to all sub ant calls. Thus, whenever you refer to {{${src.dir}}} it 
actually was already set to the outer most. Thus, when {{compile-core}} is 
invoked it actually compiles highlight instead of memory.

If the property is defined the following way, it will resolve at reference time 
and not at definition time.
{{{
<property name="src.dir" value="src/java"/>
}}}

> Make the Lucene jar an OSGi bundle
> ----------------------------------
>
>                 Key: LUCENE-1344
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1344
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Nicolas Lalevée
>            Assignee: Michael McCandless
>         Attachments: LUCENE-1344-r679133.patch, LUCENE-1344-r690675.patch, 
> LUCENE-1344-r690691.patch, LUCENE-1344.patch, LUCENE-1344.patch, 
> LUCENE-1344.patch, LUCENE-1344.patch, MANIFEST.MF.diff
>
>
> In order to use Lucene in an OSGi environment, some additional headers are 
> needed in the manifest of the jar. As Lucene has no dependency, it is pretty 
> straight forward and it ill be easy to maintain I think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to