[jira] Resolved: (CONNECTORS-51) Reduce the number of required -D defines by using System.setProperty() in the appropriate places
[ https://issues.apache.org/jira/browse/CONNECTORS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-51. --- Assignee: Karl Wright Resolution: Fixed r959748. > Reduce the number of required -D defines by using System.setProperty() in the > appropriate places > > > Key: CONNECTORS-51 > URL: https://issues.apache.org/jira/browse/CONNECTORS-51 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JCIFS connector >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > > The JCIFS connector requires a fair number of -D switches in the java startup > in order to do the right things. This is largely because jcifs.jar is > constructed this way. It may be possible, however, to eliminate these -D's > by judicious static use of System.setProperty() within the appropriate > connector class, provided we presume that jcifs classes will never be loaded > prior to the jcifs connector classes being loaded. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-40) Classloader-based plug-in architecture would permit LCF to be prebuilt
[ https://issues.apache.org/jira/browse/CONNECTORS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-40. --- Resolution: Fixed All code committed. Related tickets (such as removing the need for connector-specific -D switches) still in progress. > Classloader-based plug-in architecture would permit LCF to be prebuilt > -- > > Key: CONNECTORS-40 > URL: https://issues.apache.org/jira/browse/CONNECTORS-40 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > > The LCF architecture at this point requires interaction with the build script > in order to add connectors. This is because the connector JSPs and jars need > to be added to the appropriate war files. However, there is another > architectural option that would eliminate this need, which is to use a custom > classloader to pull components from jars that are placed in a specific > directory or directories. > In order for this to work, however, the UI components of every connector must > become part of a jar. That implies that they will need to cease being JSPs, > and become instead methods of each connector class. (There is no > proscription against using something like Velocity for assembling the > necessary output for a connector, however.) Limiting the > backwards-compatibility impact of this change will be difficult, especially > after a first release is made, so it seems clear that any change along these > lines should be attempted before version 1.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-40) Classloader-based plug-in architecture would permit LCF to be prebuilt
[ https://issues.apache.org/jira/browse/CONNECTORS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884285#action_12884285 ] Karl Wright commented on CONNECTORS-40: --- Classloader has bee added, and the configuration file format is now XML. The wiki connector description pages have been updated. Next: - Change the build process and connector delivery model to take advantage of the classloader - Change the build process wiki document to reflect all changes > Classloader-based plug-in architecture would permit LCF to be prebuilt > -- > > Key: CONNECTORS-40 > URL: https://issues.apache.org/jira/browse/CONNECTORS-40 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > > The LCF architecture at this point requires interaction with the build script > in order to add connectors. This is because the connector JSPs and jars need > to be added to the appropriate war files. However, there is another > architectural option that would eliminate this need, which is to use a custom > classloader to pull components from jars that are placed in a specific > directory or directories. > In order for this to work, however, the UI components of every connector must > become part of a jar. That implies that they will need to cease being JSPs, > and become instead methods of each connector class. (There is no > proscription against using something like Velocity for assembling the > necessary output for a connector, however.) Limiting the > backwards-compatibility impact of this change will be difficult, especially > after a first release is made, so it seems clear that any change along these > lines should be attempted before version 1.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-37) LCF should use an XML configuration file, not the simple name/value config file it currently has
[ https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-37. --- Assignee: Karl Wright Resolution: Fixed r959660. properties.xml is now the default, rather than properties.ini. The basic format of the file is: ... ... > LCF should use an XML configuration file, not the simple name/value config > file it currently has > > > Key: CONNECTORS-37 > URL: https://issues.apache.org/jira/browse/CONNECTORS-37 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > > LCF's configuration file is limited in what it can specify, and XML > configuration files seem to offer more flexibility and are the modern norm. > Before backwards compatibility becomes an issue, it may therefore be worth > converting the property file reader to use XML rather than name/value format. > It would also be nice to be able to fold the logging configuration into the > same file, if this seems possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-52) Update documentation to reflect changes to Solr Connector
Update documentation to reflect changes to Solr Connector - Key: CONNECTORS-52 URL: https://issues.apache.org/jira/browse/CONNECTORS-52 Project: Lucene Connector Framework Issue Type: Bug Components: Documentation Reporter: Karl Wright The Solr Connector has sprouted various new tabs and features lately. The end-user documentation for it should be revamped to match the software. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
