-website.git;a=commit;h=7671110548ec67fd87e774c6d1af2fd07c17a0b8
> [PATCH] Build documentation omission (maven)
>
>
> Key: FOP-3113
> URL: https://issues.apache.org/jira/browse/FOP-3113
> Project: FO
[
https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3113:
--
Assignee: Simon Steiner
> [PATCH] Build documentation omission (ma
change was already on trunk - that change is replicated in 2.8 by
the attached patch.
[^FOP-3113-patch2.diff]
was (Author: JIRAUSER298677):
The required change was already on trunk - that change is replicated in 2.8 by
the attached patch.[^FOP-3113-patch2.diff]
> Build documentation omiss
[
https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Roxburgh updated FOP-3113:
---
Summary: [PATCH] Build documentation omission (maven) (was: Build
documentation omission (maven
.diff]
> Build documentation omission (maven)
>
>
> Key: FOP-3113
> URL: https://issues.apache.org/jira/browse/FOP-3113
> Project: FOP
> Issue Type: Bug
> Components: documentati
[
https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Roxburgh updated FOP-3113:
---
Attachment: FOP-3113-patch2.diff
> Build documentation omission (ma
is replicated in 2.8 by
the attached patch.[^FOP-3113-patch2.diff]
> Build documentation omission (maven)
>
>
> Key: FOP-3113
> URL: https://issues.apache.org/jira/browse/FOP-3113
> Project: FOP
>
is replicated in 2.8 by
the attached patch.
[^FOP-3113-patch2.diff]
> Build documentation omission (maven)
>
>
> Key: FOP-3113
> URL: https://issues.apache.org/jira/browse/FOP-3113
> Project: FOP
>
[
https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Roxburgh updated FOP-3113:
---
Attachment: FOP-3113-patch.txt
> Build documentation omission (ma
/compiling.mdtext:
### Apache Maven
Parts of the build also use [Apache
Maven](https://maven.apache.org/index.html). You will need your Maven bin
directory on your PATH environment variable.
[^FOP-3113-patch.txt]
> Build documentation omission (ma
to dependency on maven. After installing maven,
the build succeeded.
Update instructions to indicate maven dependency.
> Build documentation omission (maven)
>
>
> Key: FOP-3113
> URL: https://issues.apache.org/
Dave Roxburgh created FOP-3113:
--
Summary: Build documentation omission (maven)
Key: FOP-3113
URL: https://issues.apache.org/jira/browse/FOP-3113
Project: FOP
Issue Type: Bug
/68cc1bd6b3adc6a2a62ea7a36b264be8ac4c4574
> External configuration documentation outdated
> -
>
> Key: FOP-2966
> URL: https://issues.apache.org/jira/browse/FOP-2966
> Project: FOP
>
[
https://issues.apache.org/jira/browse/FOP-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2966:
--
Assignee: Simon Steiner
> External configuration documentation outda
Tim created FOP-2966:
Summary: External configuration documentation outdated
Key: FOP-2966
URL: https://issues.apache.org/jira/browse/FOP-2966
Project: FOP
Issue Type: Task
Components
({color:#008000}"xyx"{color}).build();
and pass into fopfactory
> Embedding: missing migration documentation from FOP 1.x
> ---
>
> Key: FOP-2495
> URL: https://issues.apache
an update, or FOP should
re-introduce the fontBaseUrl.
> Embedding: missing migration documentation from FOP 1.x
> ---
>
> Key: FOP-2495
> URL: https://issues.apache.org/jira/browse/FOP-2495
>
, so you may
need to use custom resource resolver
> Embedding: missing migration documentation from FOP 1.x
> ---
>
> Key: FOP-2495
> URL: https://issues.apache.org/jira/browse/FOP-2495
>
be extended to
show how to set the baseUrl / fontBaseUrl in FOP >= 2.0 when upgrading.
> Embedding: missing migration documentation from FOP 1.x
> ---
>
> Key: FOP-2495
> URL: https:/
[
https://issues.apache.org/jira/browse/FOP-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner resolved FOP-2796.
Resolution: Fixed
Assignee: simon steiner
> Documentation doesnt mention need for pdfbox
[
https://issues.apache.org/jira/browse/FOP-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2796:
---
Summary: Documentation doesnt mention need for pdfbox jar to run tests
(was: Missing pdfbox jar files
2.2 documentation
>
>
> Key: FOP-2791
> URL: https://issues.apache.org/jira/browse/FOP-2791
> Project: FOP
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.2
&g
[
https://issues.apache.org/jira/browse/FOP-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner reassigned FOP-2791:
--
Assignee: simon steiner
> Broken Link in FOP 2.2 documentat
[Changes (2.2)|https://xmlgraphics.apache.org/fop/2.2/changes_2.2.html]
* [Known
Issues|https://xmlgraphics.apache.org/fop/2.2/knownissues_overview.html]
* [Upgrading|https://xmlgraphics.apache.org/fop/2.2/upgrading.html]
The "Known Issues" is the broken link.
> Bro
e.org/fop/2.2/changes_2.2.html]
* [Known
Issues|https://xmlgraphics.apache.org/fop/2.2/knownissues_overview.html]
* [Upgrading|https://xmlgraphics.apache.org/fop/2.2/upgrading.html]
The "Known Issues" is the broken link.
> Broken Link in FOP 2.2 documentation
>
issues_overview.html
> Broken Link in FOP 2.2 documentation
>
>
> Key: FOP-2791
> URL: https://issues.apache.org/jira/browse/FOP-2791
> Project: FOP
> Issue Type: Bug
> Componen
Thomas Schraitle created FOP-2791:
-
Summary: Broken Link in FOP 2.2 documentation
Key: FOP-2791
URL: https://issues.apache.org/jira/browse/FOP-2791
Project: FOP
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2495:
---
Priority: Major (was: Blocker)
> Embedding: missing migration documentation from FOP
? Because of
performance reasons it is not an option in our project to create a new Factory
for each pdf.
> Embedding: missing migration documentation from FOP 1.x
> ---
>
> Key: FOP-2495
>
[
https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2495:
---
Assignee: (was: Robert Meyer)
Embedding: missing migration documentation from FOP 1.x
[
https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2495:
---
Assignee: Robert Meyer
Embedding: missing migration documentation from FOP 1.x
here -- I fully understand the
frustrations -- but can we please distinguish between:
a) the core issue that was reported, which was related to missing migration
documentation: comments related to that belong here
b) other issues: comments should be deleted here, and moved to other, separate
JIRA
that were show stoppers because I had to try out and browse
the internet to get bits of peaces to finally get it to run. So, as the topic
is almost self explainable, the comments just show various examples what APIs
need to be documented.
Embedding: missing migration documentation from FOP 1.x
examples what APIs
need to be documented.
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
)
at org.apache.batik.bridge.GVTBuilder.build(Unknown Source)
at
org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:103)
... 61 more
--
I don't know if this is a Batik bug in FOP...
Embedding: missing migration documentation from FOP 1.x
Source)
at
org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:103)
... 61 more
--
I don't know if this is a Batik bug in FOP...)
Embedding: missing migration documentation from FOP 1.x
//builder.setStrictFOValidation(false);
fopFactory = builder.build();
-
In FOP 1.0, I was able to change the baseURI via
foUserAgent.setBaseURL();
for each document - but FOP 2.0 does nott have such a method anymore. :-(
Embedding: missing migration documentation from FOP 1.x
: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components: documentation
looking at relative urls
{code}
public Resource getResource(URI uri) throws IOException {
return new Resource(new FileInputStream());
}
{code}
Embedding: missing migration documentation from FOP 1.x
is with
Windowsnetwork shares like \\PC1\ I set the correct URI (tested in
Windows Explorer) file:PC1/.. but somehoe, FOP is changing this to an
invalid path.
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP
= FopFactory.newInstance(currentBase);
}
foUserAgent = fopFactory.newFOUserAgent();
}//setupFOP()
--
only to replace FOP 1.0 foUserAgent.setBaseURL() ... :-(
Embedding: missing migration documentation from FOP 1.x
... :-(
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components
() ... :-(
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components: documentation
concatenation!?
We also get thousands of font errors:
Font FrutigerIC,normal,400 not found. Substituting with any,normal,400.
even though I set a fixed (correct) font-base URI in the config.
Embedding: missing migration documentation from FOP 1.x
(correct) font-base URI in the config.
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue
migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components: documentation
Affects
= factory.newTransformer();
Source src = new StreamSource(new ByteArrayInputStream(fo.getBytes()));
Result res = new SAXResult(fop.getDefaultHandler());
transformer.transform(src, res);
fos.close();
}
Embedding: missing migration documentation from FOP 1.x
).
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components: documentation
).
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components
a org.apache.xmlgraphics.io.ResourceResolver that is an interface ...
probably org.apache.fop.apps.io.InternalResourceResolver that has no API to use
a javax.xml.transform.URIResolver
Oh boy ...
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP
has a example where in fop
1.0 it uses setURIResolver and fop 2.0 a ResourceResolver
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP
MH created FOP-2495:
---
Summary: Missing migration documentation from FOP 1.x
Key: FOP-2495
URL: https://issues.apache.org/jira/browse/FOP-2495
Project: FOP
Issue Type: Bug
Components
running with all those undocumented API changes. Can you please state a
migration documentation for all methods (method signatures) that don't exist
anymore? We can't start coding all over again from scratch. Thank you very much!
was:
Because of bug FOP-2177 wie couldn't upgrade form FOP 1.0
code somehow
running with all those undocumented API changes. Can you please state a
migration documentation for all methods (method signatures) that don't exist
anymore? We can't start coding all over again from scratch. Thank you very much!
was:
Because of bug FOP-2177 we couldn't upgrade
[
https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
MH updated FOP-2495:
Summary: Embedding: missing migration documentation from FOP 1.x (was:
Missing migration documentation from FOP 1.x
running with all those undocumented API changes. Can you please state a
migration documentation for all methods (method signatures) that don't exist
anymore? We can't start coding all over again from scratch. Thank you very much!
was:
Because of bug FOP-2177 we couldn't upgrade form FOP 1.0
things to the old
code. I'm sure I missed some test cases and there's no high-level guidance as
to how to safely replace calls to xx.yy() that no longer exists, etc.
Embedding: missing migration documentation from FOP 1.x
org.apache.fop.apps.io.InternalResourceResolver that has no API to use
a javax.xml.transform.URIResolver
Oh boy ...
Embedding: missing migration documentation from FOP 1.x
---
Key: FOP-2495
URL: https://issues.apache.org/jira
Glenn,
I was trying to play with the extension elements added in FOP-2298 and
FOP-2301 and could do with some documentation, but I couldn’t find any.
Is it somewhere I haven’t looked at?
Thanks,
Vincent
[
https://issues.apache.org/jira/browse/FOP-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2209:
-
Summary: Move new CMS documentation back into FOP repository or ... (was:
move new CMS documentation back
. on the
other hand, TTF can be either subset or full embedded.
Documentation is misleading
---
Key: FOP-2169
URL: https://issues.apache.org/jira/browse/FOP-2169
Project: Fop
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FOP-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bernardo closed FOP-2169.
--
the web page was updated to make the fact clear.
Documentation is misleading
, just remove
also, i presume that at some point (but not in this bug), we will create a new
src/documentation directory and appropriate build steps that contain the and
build/deploy the new markdown doc sources
remove obsolete documentation files
also need to do the
same for Batik and XML Graphics Commons, but I thought I'd wait until other
folks had a chance to ensure I didn't munge stuff!
remove obsolete documentation files
---
Key: FOP-2208
URL: https
/documentation/intermediate-format-ng, which includes the schema for the IF,
and is used by junit testing.
remove obsolete documentation files
---
Key: FOP-2208
URL: https://issues.apache.org/jira/browse/FOP-2208
the
documentation portion. Before I nuke the following unnecessary files, could you
run the ant/build process with the attached build.xml file to ensure I'm not
munging something?
Thanks!
Files to be nuked:
- fop/trunk/forrest.properties
- fop/trunk/forrest.properties.xml
- fop/trunk/publish.xml
,
I've gone through the fop/trunk/build.xml and believe I have eradicated the
documentation portion. Before I nuke the following unnecessary files, could you
run the ant/build process with the attached build.xml file to ensure I'm not
munging something?
Thanks!
Files to be nuked:
- fop/trunk
Glenn Adams created FOP-2208:
Summary: remove obsolete documentation files
Key: FOP-2208
URL: https://issues.apache.org/jira/browse/FOP-2208
Project: Fop
Issue Type: Task
Reporter
[
https://issues.apache.org/jira/browse/FOP-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2208:
-
Affects Version/s: trunk
remove obsolete documentation files
[
https://issues.apache.org/jira/browse/FOP-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2208:
-
Component/s: documentation
remove obsolete documentation files
Glenn Adams created FOP-2209:
Summary: move new CMS documentation back into FOP repository or ...
Key: FOP-2209
URL: https://issues.apache.org/jira/browse/FOP-2209
Project: Fop
Issue Type: Task
artifacts that contained
document sources; but now, it doesn't seem like that is possible, or at
least the dist-src build targets do not go out to collect the new
documentation sources and copy them into the generated source artifact;
while you are at it, the old publish.xml ant files seem
On Wed, Feb 6, 2013 at 4:29 AM, Pascal Sancho psancho@gmail.com wrote:
Hi,
Since XCG website repository includes now all XCG sub-projects, there
should be a Jira entry for that.
By include all do you mean includes all documentation for XCG
sub-projects?
I'm personally not comfortable
where do we edit documentation now? is fop/src/documentation now obsolete?
if so, then why is it still in the tree? how will we do releases and still
include documentation if it lives in another tree?
Hi Glenn,
The documentation exists solely in the ASF CMS, and so fop/src/documentation is
obsolete. We purposely did not delete the src/documentation path until we were
completely sure we weren't going back. I suppose we're there…
I'm happy to nuke ye olde documentation Forrest-based 'xdoc
ok; how about the question about future releases? until now, batik,
xgc-commons, and fop could be released with source artifacts that contained
document sources; but now, it doesn't seem like that is possible, or at
least the dist-src build targets do not go out to collect the new
documentation
future releases? until now, batik,
xgc-commons, and fop could be released with source artifacts that contained
document sources; but now, it doesn't seem like that is possible, or at least
the dist-src build targets do not go out to collect the new documentation
sources and copy them
https://issues.apache.org/bugzilla/show_bug.cgi?id=54234
Bug ID: 54234
Summary: Documentation is misleading
Product: Fop
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
:
Author: gadams
Date: Fri May 25 19:10:28 2012
New Revision: 1342781
URL: http://svn.apache.org/viewvc?rev=1342781view=rev
Log:
Update FAQ and New Bug documentation.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml
xmlgraphics/fop/trunk/src/documentation
:10:28 2012
New Revision: 1342781
URL: http://svn.apache.org/viewvc?rev=1342781view=rev
Log:
Update FAQ and New Bug documentation.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml
xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml
xmlgraphics
https://issues.apache.org/bugzilla/show_bug.cgi?id=49097
Chris Bowditch bowditch_ch...@hotmail.com changed:
What|Removed |Added
Status|NEW
(Some notes relating to this work that I thought would be more easily
retrievable if I put them here rather than in the Bugzilla entry.)
I had to forgo the soft hyphen approach due to a hack in XGC that
replaces soft hyphens with normal hyphens when no glyph is available in
the font for soft
Hi Peter,
good job, anyway.
Tests are ok for now (except a 0 run for Testsuite:
org.apache.fop.image.loader.batik.ImageLoaderTestCase -- ;-) I guess
this is not related to rounded corners).
2012/10/30 Peter Hancock peter.hanc...@gmail.com:
Well spotted Pascal and sorry for the late reply.
Hi,
it appears that the change from r687369 is lost (replacing
org.apache.fop.util.UnitConv with
org.apache.xmlgraphics.util.UnitConv).
This regression starts with the branch (r1003017), so I guess it was
branched from a local modified WC.
I think that this merge should be reverted, and the
Hi,
This merge seems introduce 3 deprecated warning.
I'm not sure, but it is possible that UnitConv has migrated to
xmlgraphics.commons
compile-java:
[mkdir] Created dir: D:\bin\java\fop\trunk\build\classes
[javac] Compiling 1441 source files to D:\bin\java\fop\trunk\build\classes
:
Update FAQ and New Bug documentation.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml
xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml
xmlgraphics/fop/trunk/status.xml
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml
://svn.apache.org/viewvc?rev=1342781view=rev
Log:
Update FAQ and New Bug documentation.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml
xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml
xmlgraphics/fop/trunk/status.xml
Modified: xmlgraphics/fop
relevant there.
the source for this file is under
src/documentation/content/xdocs/compliance.ihtml; you can
create a bug attaching a patch, or if it is a simple change,
just send the diff or describe it in an email
Actually the changes you made to update
/documentation/content/**xdocs/compliance.ihtml;
you can create a bug attaching a patch, or if it is a simple change, just
send the diff or describe it in an email
Actually the changes you made to update the documentation for the 1.1
release don't appear to have yet been merged back to trunk
-dev as its now more relevant there.
the source for this file is under
src/documentation/content/**xdocs/compliance.ihtml;
you can create a bug attaching a patch, or if it is a simple change,
just
send the diff or describe it in an email
Actually the changes you made to update
On 14/07/2012 22:14, Glenn Adams wrote:
Hi Glenn,
I've moved this discussion to fop-dev as its now more relevant there.
the source for this file is
under src/documentation/content/xdocs/compliance.ihtml; you can create
a bug attaching a patch, or if it is a simple change, just send the
diff
On Wed, Jul 18, 2012 at 2:35 AM, Chris Bowditch
bowditch_ch...@hotmail.comwrote:
On 14/07/2012 22:14, Glenn Adams wrote:
Hi Glenn,
I've moved this discussion to fop-dev as its now more relevant there.
the source for this file is under
src/documentation/content/**xdocs/compliance.ihtml
Glenn,
On 02/07/12 19:49, gad...@apache.org wrote:
Author: gadams
Date: Mon Jul 2 18:49:00 2012
New Revision: 1356398
URL: http://svn.apache.org/viewvc?rev=1356398view=rev
Log:
Fix broken link to permit documentation deployment.
Please port that change to the branch and revert
On 02/07/12 09:57, cbowdi...@apache.org wrote:
replace tabs with space. Correct use of it's with its as suggested by
Vincent. Sorry for the noise.
I should have done all the changes in a single commit.
Actually not. It’s good to follow the atomicity of commits. That way
it’s easy to revert
Please note that I have published the XGC/FOP site docs from the respective
{1.5,1.1}RC1 tags of these repos. Until this is merged into trunk, please
avoid publishing directly from trunk, lest the new RC1 docs be overwritten.
fixed, which, btw, can be done with:
svn propedit -r *revision* --revprop svn:log new log message
On Thu, May 17, 2012 at 3:02 AM, Vincent Hennebert vhenneb...@gmail.comwrote:
Glenn,
May I remind you to put contributor names in commit messages when you
apply their patches [1].
[1]
Thanks Glenn ( Vincent for your diligence! ;-)
My religion is simple. My religion is kindness.
- HH The Dalai Lama of Tibet
On May 18, 2012, at 6:12 PM, Glenn Adams gl...@skynav.com wrote:
fixed, which, btw, can be done with:
svn propedit -r revision --revprop svn:log new log message
On
/test/java/org/apache/fop/afp/goca/GraphicsSetLineWidthTestCase.java
Modified:
xmlgraphics/fop/trunk/conf/fop.xconf
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
xmlgraphics
https://issues.apache.org/bugzilla/show_bug.cgi?id=53247
Priority: P2
Bug ID: 53247
Assignee: fop-dev@xmlgraphics.apache.org
Summary: incorrect documentation for pcl mime type
Severity: normal
Classification: Unclassified
OS
https://issues.apache.org/bugzilla/show_bug.cgi?id=53247
Glenn Adams gad...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
1 - 100 of 279 matches
Mail list logo
