[
https://issues.apache.org/jira/browse/XERCESC-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898407#comment-17898407
]
Scott Cantor commented on XERCESC-2257:
---------------------------------------
There is no official statement about it, every time it comes up, the PMC
decides to leave the project in limbo and the board hasn't stepped in. It is
what it is, and I just don't think it's responsible to portray the situation
externally as other than it is when an issue arises such as the port status. I
didn't intend to open a can of worms, but none of this is new information or
anything that wasn't true 5 years ago, and if deprecating the port starts a
conversation outside of the ASF, then that's a clear positive in my mind.
All of this applies equally to xml-security-c except that that PMC didn't fight
the move to retire the code base, so there's no ambiguity there.
If the PMC agrees to change the public status of the project, then I will post
whatever is agreed to, but as it stands, I have no license to do that. I
probably had no claim to say what I did about the port, but the facts and the
public position aren't really in alignment here.
I don't happen to agree that it's the project's job to explicitly reach out to
dependent projects. It's the responsbility of any project that depends on
anything to be actively monitoring and aware of the state of its dependencies,
not the other way around. I have been very public on the lists about all this,
so the only people who don't know the situation didn't pay any attention.
To your questions, I don't know anything about xml-commons at all. I assumed
Xerces-P died years ago but I don't know that for a fact, I don't really know
much about it either.
Xerces-J was even more moribund than this version was but was revived a bit
recently (unwisely IMHO) so it's in a slightly better state I suppose but that
was after years of neglect. As a personal opinion, I do think one would be
ill-advised to be using it at this point also, particularly given that the fork
in the JDK exists.
> symbol not found in flat namespace (_xercesc_messages_3_2_dat)
> --------------------------------------------------------------
>
> Key: XERCESC-2257
> URL: https://issues.apache.org/jira/browse/XERCESC-2257
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Ryan Carsten Schmidt
> Priority: Major
>
> Software linking with libxerces-c-3.3.dylib fails to work:
>
> {noformat}
> dyld[5155]: symbol not found in flat namespace (_xercesc_messages_3_2_dat)
> {noformat}
>
> This was reported to MacPorts here: [https://trac.macports.org/ticket/71304]
> This is a regression; 3.2.4 didn't have this problem.
> Surely for version 3.3.x on these lines {{3_2}} should be changed to
> {{{}3_3{}}}?
> [https://github.com/apache/xerces-c/blob/v3.3.0/src/xercesc/util/MsgLoaders/ICU/ICUMsgLoader.cpp#L54-L55]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
