non-binding +1
On Mon, Oct 21, 2019 at 4:36 AM Colm O hEigeartaigh
wrote:
> +1 to moving Neethi, XML Schema and WSS4J to git.
>
> Colm.
>
> On Fri, Oct 18, 2019 at 5:14 PM Gary Gregory
> wrote:
>
>> FYI, over at Apache Commons, we've migrated most/all of our reposit
FYI, over at Apache Commons, we've migrated most/all of our repositories to
GitBox and it's worked like a charm since, the integration with GitHub is
great.
Gary
On Fri, Oct 18, 2019 at 8:49 AM Daniel Kulp wrote:
>
> I’d like to propose to start the process of moving some (or all) of our
>
[
https://issues.apache.org/jira/browse/XMLSCHEMA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997476#comment-15997476
]
Gary Gregory commented on XMLSCHEMA-44:
---
I'm glad my patch made it in there, I almost had
[
https://issues.apache.org/jira/browse/XMLSCHEMA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated XMLSCHEMA-44:
--
Attachment: ggregory-xmlschema-core-null-safe.diff
> Make XmlSchemaCollection get* APIs n
Gary Gregory created XMLSCHEMA-44:
-
Summary: Make XmlSchemaCollection get* APIs null-safe.
Key: XMLSCHEMA-44
URL: https://issues.apache.org/jira/browse/XMLSCHEMA-44
Project: XmlSchema
Issue
Gary Gregory created WSS-578:
Summary: Binary compatibility breaks between 2.1.5 and
2.1.6-SNAPSHOT
Key: WSS-578
URL: https://issues.apache.org/jira/browse/WSS-578
Project: WSS4J
Issue Type
[
https://issues.apache.org/jira/browse/WSS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262600#comment-15262600
]
Gary Gregory commented on WSS-577:
--
Good idea. I'll be able to do that tomorrow.
> Binary compatibil
[
https://issues.apache.org/jira/browse/WSS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262489#comment-15262489
]
Gary Gregory commented on WSS-577:
--
One less headache, thank you Colm!
Gary
> Binary compatibility bro
Gary Gregory created WSS-577:
Summary: Binary compatibility broken between version <=2.1.3 and
>=2.1.4 with org.apache.wss4j.dom.WSSecurityEngineResult
Key: WSS-577
URL: https://issues.apache.org/jira/browse/W
+1 (non-binding) to drop Java 5 (even drop 6 if you like).
Gary
On Thu, Sep 11, 2014 at 8:16 AM, Alexandr Klimov my-...@yandex.ru wrote:
+1
09.09.2014, 12:04, Colm O hEigeartaigh cohei...@apache.org:
+1 makes sense.
Colm.
On Mon, Sep 8, 2014 at 9:22 PM, Daniel Kulp dk...@apache.org
+1 (non-binding) to drop Java 5 (even drop 6 if you like).
Gary
On Thu, Sep 11, 2014 at 8:16 AM, Alexandr Klimov my-...@yandex.ru wrote:
+1
09.09.2014, 12:04, Colm O hEigeartaigh cohei...@apache.org:
+1 makes sense.
Colm.
On Mon, Sep 8, 2014 at 9:22 PM, Daniel Kulp
It's a bummer the formatting is pretty odd on an iPhone.
Gary
On Apr 29, 2013, at 17:07, Andreas Veithen andreas.veit...@gmail.com wrote:
All,
I've replaced the old Forrest site with a new Maven based site, as
discussed some time ago. Please have a look at the following document
to see how
The FTPS unit test
org.apache.commons.vfs2.provider.ftps.test.FtpsProviderTestCase_Disabled
uses:
protected FileSystemOptions getFileSystemOptions()
{
if (fileSystemOptions == null)
{
fileSystemOptions = new FileSystemOptions();
final
On Thu, May 3, 2012 at 9:26 AM, Colm O hEigeartaigh cohei...@apache.orgwrote:
Hi all,
I propose to drop WSS4J 1.5.x releases after the next release (WSS4J
1.5.13). Most of the major downstream projects that use WSS4J have
already upgraded to use the 1.6.x series of releases. Work will
On Wed, Feb 29, 2012 at 11:13 AM, Colm O hEigeartaigh
cohei...@apache.orgwrote:
Thanks for all the responses. So to address the open questions:
1) Should streaming-xml-security go into Santuario or WSS4J? Should
all of WSS4J move to Santuario?
The consensus seems to be that
Rrrrelease, release often!
Gary
On Thu, Sep 15, 2011 at 1:23 PM, Daniel Kulp dk...@apache.org wrote:
I've fixed a few issues in XMLSchema 2 and was thinking of doing a release
maybe early next week. Are there any changes that others may want in
there?
The only JIRA left open against
16 matches
Mail list logo
