+1 to renaming the package - nows the time.
- Mark
http://www.lucidimagination.com (mobile)
On Aug 22, 2010, at 8:01 PM, "Jack Krupansky"
wrote:
> +1
>
> -- Jack Krupansky
>
> --
> From: "Karl Wright"
> Sent: Sunday, August 22, 2010 1:49 PM
+1
-- Jack Krupansky
--
From: "Karl Wright"
Sent: Sunday, August 22, 2010 1:49 PM
To: "connectors-dev"
Subject: Need an opinion, on whether to change package or not
Consider this an official request for a vote.
+1 indicates you think we should
Karl, is the Fully-Qualified classname in the DB the only problem? I
mean you would break all kinds of BW compat if you change the package
names. All imports must be fixed etc.
One thing I don't get is that LCF has not yet been released, right?!
We can fix the DB issues in the code very easily but
Consider this an official request for a vote.
+1 indicates you think we should change the following in the source code, as
soon as is practical:
org.apache.lcf.xxx -> org.apache.acf.xxx
All classes LCF.java and LCFException.java should change to ACF.java and
ACFException.java
Bear in mind that u
[
https://issues.apache.org/jira/browse/CONNECTORS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901193#action_12901193
]
Karl Wright commented on CONNECTORS-91:
---
Yes, your trunk version is too out of dat
[
https://issues.apache.org/jira/browse/CONNECTORS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901186#action_12901186
]
Karl Wright commented on CONNECTORS-91:
---
The patch failed to apply, fairly catastr
Are any of these classes generally usable outside of LCF/ACF, such as by an
integrator or administrator who wants some scriptable control over crawl
jobs, as opposed to internal product testing? If so, maybe there should be
third category, say "public" or "utility".
-- Jack Krupansky
