have this straight?
On Tue, Apr 12, 2016 at 9:25 AM, Benson Margulies <bimargul...@gmail.com> wrote:
> Folks, I need some help. The doc says to run release:prepare.
>
> Running mvn release:prepare with a version of 2.5 will make a tag
> commons-io-2.5, not 2.5-RCx. Running it (as
Folks, I need some help. The doc says to run release:prepare.
Running mvn release:prepare with a version of 2.5 will make a tag
commons-io-2.5, not 2.5-RCx. Running it (as I did) with a tag of -RCx
will make a release package with a pom in it that says RCx.
Did I miss a step here, like manually
Folks,
I feel like my only contribution to this PMC at this point is vestigial
supervision and the occasional vote. I don't have any technological issues
to scratch.
However, I don't want to abruptly leave people high and dry.
Do we have enough active participants that the PMC would remain
Who will join me in being on an AdminGroup for the wiki so we can disable
new pages by default?
No one uses the wiki except spammers. Shall we turn off writes altogether?
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
Thank you, Dan, you remember the code I wrote better than I do.
On Sat, Jan 5, 2013 at 9:31 PM, Daniel Kulp dk...@apache.org wrote:
On Jan 5, 2013, at 2:24 AM, Kishanthan Thangarajah kshanth2...@gmail.com
wrote:
Hi Devs,
We are now in the process of moving to xmlschema2 in axis2 [1].
+1
On Wed, Jan 2, 2013 at 9:15 AM, Daniel Kulp dk...@apache.org wrote:
+1
Dan
On Jan 1, 2013, at 6:53 AM, Colm O hEigeartaigh cohei...@apache.org wrote:
This is a vote to release Apache WSS4J 1.6.9. This release fixes a single
(critical) issue which prevents WSS4J from working
On Sun, Nov 18, 2012 at 9:48 AM, Martin Gainty mgai...@hotmail.com wrote:
This is what Im referring to:
http://servicemix.apache.org/docs/4.4.x/jbi/components/servicemix-cxf-bc.html
A JBI compliant HTTP/SOAP or JMS/SOAP binding component named
servicemix-cxf-bc which use apache cxf
Martin,
I find myself feeling that I'm having two different conversations with
one man named Martin.
In one of those conversations, there's a JIRA from long ago, never
fixed, which caused the SM project to copy and hack some CXF code
instead just having a dependency. Whether or not fixing that
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned WSCOMMONS-559:
--
Assignee: (was: Benson Margulies)
Utils to ease use of XmlSchema
+1
On Wed, Jul 25, 2012 at 7:13 PM, Freeman Fang freeman.f...@gmail.com wrote:
+1 (non-binding)
－
Freeman Fang
FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo:
wrote:
On Sunday, April 08, 2012 04:48:27 PM Benson Margulies wrote:
but ... we have no KEYS file in the xmlschema tree.
Not in neethi or axiom or others either
That is not correct. Axiom always had its own KEYS file which was located
here:
http://www.apache.org/dist/ws/commons/axiom
will
help with this.
Andreas
On Mon, Apr 9, 2012 at 16:22, Benson Margulies bimargul...@gmail.com wrote:
Yes, SVN. One of the validation mechanisms is to get KEYS from svn, to
detect tampered-with packages.
On Mon, Apr 9, 2012 at 10:21 AM, Daniel Kulp dk...@apache.org wrote:
On Monday, April
Sorry, there's nothing we can do about than ancient version.
On Tue, Mar 13, 2012 at 6:22 AM, Stephan Götter keepal...@gmail.com wrote:
Hello,
the file
http://search.maven.org/remotecontent?filepath=org/apache/ws/commons/XmlSchema/1.1/XmlSchema-1.1.pom
contains SNAPSHOT as version instead
+1 binding
On Mon, Jan 30, 2012 at 5:02 AM, Colm O hEigeartaigh
cohei...@apache.org wrote:
+1.
Colm.
On Mon, Jan 30, 2012 at 6:03 AM, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
There were number of discussion on above subject but I couldn't locate any
vote thread on this. Shall
+1
On Mon, Dec 5, 2011 at 7:14 AM, Daniel Kulp dk...@apache.org wrote:
+1
Dan
On Friday, December 02, 2011 5:06:56 PM Colm O hEigeartaigh wrote:
All,
This is a vote to release Apache WSS4J 1.6.4.
Issues Fixed:
https://issues.apache.org/jira/browse/WSS/fixforversion/12318343
Svn tag:
That's two positives. @dkulp, you listening? Got an opinion?
On Sun, Aug 21, 2011 at 2:09 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
On Wed, Aug 17, 2011 at 03:36, Benson Margulies bimargul...@gmail.com wrote:
Oh, a few hours.
Considering the poorer development standards, for Axis2
Based on email since we released 2.0, I've become convinced that it
was a mistake to leave the package names alone and change all the
APIs. There are a few outstanding JIRA. I propose to make a branch for
'urgent' fixes atop 2.0, and then aim the trunk at 2.1, and rename the
packages. This would
Wasn't there one of the 'w' projects related to wsdl? Or am I just
imagining the non-Axis2 case? Axis2 would probably be enough of a
reason.
On Tue, Aug 16, 2011 at 1:20 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
On Tue, Aug 16, 2011 at 17:44, Benson Margulies bimargul...@gmail.com
to XmlSchema 2.0?
Andreas
On Tue, Aug 16, 2011 at 19:27, Benson Margulies bimargul...@gmail.com wrote:
Wasn't there one of the 'w' projects related to wsdl? Or am I just
imagining the non-Axis2 case? Axis2 would probably be enough of a
reason.
On Tue, Aug 16, 2011 at 1:20 PM, Andreas
[
https://issues.apache.org/jira/browse/XMLSCHEMA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved XMLSCHEMA-15.
---
Resolution: Not A Problem
Assignee: Benson Margulies
2.0 is documented
[
https://issues.apache.org/jira/browse/XMLSCHEMA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13071222#comment-13071222
]
Benson Margulies commented on XMLSCHEMA-15:
---
There is no tutorial for 2.0
Right now, XMLSchema gets work done to it when someone at either Axis
or CXF sees a need. I know of no credible thread to move any web
service standard to 1.1. Not WS-I, not JAX-B, not nothing.
Of course, code contributions are encouraged.
On Wed, Jun 1, 2011 at 11:24 AM, Dmitry redmi...@list.ru
[
https://issues.apache.org/jira/browse/XMLSCHEMA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030771#comment-13030771
]
Benson Margulies commented on XMLSCHEMA-11:
---
I fear that there's less
[
https://issues.apache.org/jira/browse/XMLSCHEMA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030526#comment-13030526
]
Benson Margulies commented on XMLSCHEMA-11:
---
True, I missed it altogether
[
https://issues.apache.org/jira/browse/XMLSCHEMA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved XMLSCHEMA-12.
---
Resolution: Fixed
Fix Version/s: XmlSchema 2.1
Assignee: Benson
[
https://issues.apache.org/jira/browse/XMLSCHEMA-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved XMLSCHEMA-13.
---
Resolution: Fixed
Fix Version/s: XmlSchema 2.0.1
Assignee: Benson
https://issues.apache.org/jira/browse/XMLSCHEMA-12
Proposes that we model the basic type hierarchy of the built-in types.
My first reaction was negative, but the idea is growing on me. After
all, you can't usefully serialize the built-in schema to xml, so what
harm could be done here?
Has
[
https://issues.apache.org/jira/browse/XMLSCHEMA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved XMLSCHEMA-4.
--
Resolution: Fixed
Fix Version/s: XmlSchema 2.0
java.lang.RuntimeException
[
https://issues.apache.org/jira/browse/XMLSCHEMA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed XMLSCHEMA-2.
Resolution: Invalid
Null pointer processing schema file
+1
On Wed, Apr 6, 2011 at 1:30 PM, Colm O hEigeartaigh cohei...@apache.org wrote:
All,
This is a vote to release Apache WSS4J 1.6.0. WSS4J 1.6.0 has been
under development for over two years now, and it's high time it was
released. It features support for SAML2 assertions, JSR-105 support,
+1
On Mon, Apr 4, 2011 at 9:09 AM, Daniel Kulp dk...@apache.org wrote:
+1
On Sunday 03 April 2011 2:40:30 PM Andreas Veithen wrote:
This is a vote to release Neethi 2.0.5.
I'll assume this was for 3.0.0 since the subject and the tag and everything is
for 3.0.0. :-)
Dan
I fixed
Done.
I pushed ws.apache.org/neethi/3.0.1-SNAPSHOT.
It works with either m2 or m3.
The next step would be to put a plain html page as
ws.apache.org/neethi/index.html that we would add to for every release
to point to the per-release maven site.
--benson
On Sun, Apr 3, 2011 at 5:27 AM,
We should not use 'commons' any longer. In my opinion, the 2.5 site
should go to ws.apache.org/neethi/2.5 and the 3.0 should go to
neethi/3.0. In other words, use ${project.version} in the url/ in
the pom.
On Sat, Apr 2, 2011 at 4:51 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
I did
andreas.veit...@gmail.com wrote:
On Sat, Apr 2, 2011 at 22:56, Benson Margulies bimargul...@gmail.com wrote:
We should not use 'commons' any longer.
That's what I was thinking. So we need to fix that as well.
In my opinion, the 2.5 site
should go to ws.apache.org/neethi/2.5 and the 3.0 should
Um, why not set the site URLs so that they can co-exist?
On Fri, Apr 1, 2011 at 1:28 PM, Daniel Kulp dk...@apache.org wrote:
This is a vote to release Neethi 2.0.5
I fixed the release notes. I also did a minor update to the site stuff, but
it really shouldn't matter. 3.0.0 is also being
+1
On Fri, Apr 1, 2011 at 1:28 PM, Daniel Kulp dk...@apache.org wrote:
This is a vote to release Neethi 2.0.5
I fixed the release notes. I also did a minor update to the site stuff, but
it really shouldn't matter. 3.0.0 is also being released at the same time
and I expect the site to be
[
https://issues.apache.org/jira/browse/XMLSCHEMA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012673#comment-13012673
]
Benson Margulies commented on XMLSCHEMA-10:
---
I don't suppose I could interest
Yes, 2.0 is released. What have I neglected to update to make that clearer?
On Tue, Mar 29, 2011 at 5:25 PM, William Eliot Kimber (JIRA)
j...@apache.org wrote:
[
[
https://issues.apache.org/jira/browse/XMLSCHEMA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012752#comment-13012752
]
Benson Margulies commented on XMLSCHEMA-10:
---
Yes, 2.0 is released
Please file a JIRA to ask for the behavior you'd like. I haven't though
carefully this morning about this.
On Thu, Mar 10, 2011 at 9:00 AM, Dmitry Repchevsky dmitry.repchev...@bsc.es
wrote:
Hello,
I noticed that the method doesn't initialize inheritance model as specified
in
We have 4 +1 votes and no others.
And I apologize if I veered into grumpiness on the discussion about
compatibility.
--benson
On Tue, Feb 15, 2011 at 1:30 PM, Tom Jordahl tjord...@adobe.com wrote:
I further want to point out that the maintainers of the code consist
of me and some small
Folks,
Due to a misunderstanding between me and the ASF common parent POM,
the XmlSchema 2.0 release is a more spartan device than I anticipated.
It has a full set of source, binary, and javadoc for the actual jar
file of xmlschema-core. It does not have the traditional items aimed
at non-Maven
dist directory. (Note that
the vote is about the source distribution, which is the primarily
important thing.)
And nothing prevents you to add code to the Maven POM that automates
the same thing for the next release.
On Wed, Feb 16, 2011 at 3:04 PM, Benson Margulies bimargul...@gmail.com
Dear recipients,
I prepared a 2.0 release of Apache XML schema, and neither I nor
anyone else managed to notice that I somehow messed up the use of the
ASF shared POM so as to produce no MD5 or SHA1 files at all. The asc
files from my signature are there, but not checksums.
So, I suppose that I
explicitly tell it to do so). It
only does that when deploying to a remote repository. If Maven had not
generated appropriate checksums during the deployment, then Nexus
would not have allowed you to promote the release.
Andreas
On Wed, Feb 16, 2011 at 15:13, Benson Margulies bimargul
https://repository.apache.org/content/repositories/orgapachews-001/
The above URL is a staging repository for the proposed 2.0 release of
XML schema.
This release is a significant housecleaning of XmlSchema: updated to
use Java 1.5 collections, rationalize the data model, and generally
try to
of an application and in different versions.
Jochen
On Mon, Feb 14, 2011 at 1:28 PM, Benson Margulies bimargul...@gmail.com
wrote:
https://repository.apache.org/content/repositories/orgapachews-001/
The above URL is a staging repository for the proposed 2.0 release of
XML schema
Sadly, eclipse has this very stupid policy of warning all suppressions
that it doesn't know. My favorite is
@SuppressWarmings(PMD)
Complain to the eclipse team, is my advice.
On Mon, Feb 14, 2011 at 3:18 PM, Tom Jordahl tjord...@adobe.com wrote:
Hey Dan,
This is a suppression added by
the user side (since I work on
stuff that basically integrates as or into Java web applications), anything
we can do to make coexistence easier is a big +1. On the flip side, changing
package names is pretty ugly.
Tom Jordahl
-Original Message-
From: Benson Margulies
at 13:15, Benson Margulies bimargul...@gmail.com
wrote:
Currently, the deployed site is a 'forrest' antique.
We have some pretty reasonable content sitting in Confluence. As you
may know, in general, intrastructure@apache is pushing projects from
Confluence to their new Markdown+svn CMS
At https://repository.apache.org/content/repositories/orgapachews-052/,
you will find a staging repository for a very dull release. This is
the build support modules for XmlSchema. Due to a maven restriction,
this has to be released first before XML Schema itself can be
released.
I think that
Last night I finally got the XmlSchema hudson builds fully under
control. I've kept the maven3 requirement so that the reports work.
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail:
://axis.apache.org/;axis.apache.org/a.
Please put this in the project list - where it should stay for a while
(say thru 2011).
Thanks,
Sanjiva.
On Wed, Dec 29, 2010 at 11:09 PM, Benson Margulies bimargul...@gmail.com
wrote:
I am waiting for someone to provide the content in the form
Do we really have to credit patches?
On Mon, Nov 29, 2010 at 10:31 AM, Tom Jordahl tjord...@adobe.com wrote:
Conditional +1 (binding)
I noticed that the NOTICE file has the following:
This product includes software Copyright University of Southampton IT
Innovation Centre, 2006
+1 (binding)
Some build warmings for some day:
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.apache.ws.security:wss4j:bundle:1.5.10
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead.
[WARNING] The
.
On Fri, Nov 5, 2010 at 3:13 AM, Andreas Veithen andreas.veit...@gmail.com
wrote:
The question remains (also to Sanjiva): did you have a closer look at it?
Andreas
On Thu, Nov 4, 2010 at 20:03, Benson Margulies bimargul...@gmail.com
wrote:
Because INFRA will force us all to use it some time
Same error with chmod.
On Wed, Nov 3, 2010 at 5:20 PM, Benson Margulies bimargul...@gmail.com wrote:
Oddly, I can't.
chgrp g+w *
On Wed, Nov 3, 2010 at 5:03 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Benson,
Can you please login to people.apache.org and fix the permissions
1. I'm the only person who has touched the ws site. If you want to be
annoyed, be annoyed at me.
2. It never occurred to me, when I started, that Axis would, at this late
date, have a 'web site' consisting of a raw HTML link to the old content on
the WS site. I didn't set out to disturb anyone or
and into the custody of the Attic PMC.
However, these 'WS' components are not TLPs. So we have yet to
determine whether they go to the Official Foundation Attic with the
mad uncles and aunts, or whether we do some similar things under our
own control here.
On 10/25/2010 1:48 PM, Benson Margulies wrote
On Sun, Oct 17, 2010 at 10:37 PM, Glen Daniels g...@thoughtcraft.com wrote:
Hi Benson,
On 10/17/2010 4:54 PM, Benson Margulies wrote:
I hope no one will be offended by offering this as a vote right off
the bat, but it seems sort of self-evidently a good idea to me.
I want to move
I'll mod. I don't think we need commit lists at this point, we can
always change that later.
On Fri, Oct 15, 2010 at 10:35 AM, Daniel Kulp dk...@apache.org wrote:
I've filed:
https://issues.apache.org/jira/browse/INFRA-3073
Couple things I think still need discussing:
1) Do we want
No one has updated this since Axis moved out. I am trying to get a
working version of forrest for Java 1.6, and then I plan to make some
adjustments. I'll also deal with the new mailing lists.
Various APIs in the XmlSchema object return collections which the
caller should not modify. What do you think of returning read-only
wrappers from the Collections class?
After a long period of hibernation, I am now pushing toward a
releasable version of XmlSchema 2.0. I have plugged it into CXF and am
working out the kinks.
Xml Schema 2.0 will be materially different than the current branch.
Superficially, it uses standard Java 1.5 generic collections and
enums.
Three binding +1 votes, one nonbinding +1, and nothing else. I'll be
pushing this evening. (I'll push nexus sooner)
Dan,
I think that I would claim that the trunk has all the functionality of
the 1.4 branch. Which is to say, it does not have any more support for
the redefine element than before, and there are probably a few other
ugly cases that never worked.
I think that, when I left off, I thought that the
Apologies to general; I constantly forget about the 'cc' implications
of the subproject structure.
The vote to release 1.4.7 passed with 3 binding +1's, one non-binding
+1, and the John Cage chorus of other voices.
I've pushed the new release, it will of course take some time to
replicate
...
Please vote for the XmlSchema release.
I have prepared a proposed release of Apache XmlSchema 1.4.7.
https://repository.apache.org/content/repositories/orgapachews-008/
This is a formal vote for a release. Andreas has verified that all the
downstreams on the Axis/WS side are OK.
Here is my +1.
The vote will close in 72 hours.
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912664#action_12912664
]
Benson Margulies commented on WSCOMMONS-559:
Oh, yuck. Indeed. My bad
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912664#action_12912664
]
Benson Margulies edited comment on WSCOMMONS-559 at 9/20/10 3:33 PM
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated WSCOMMONS-559:
---
Comment: was deleted
(was: Not according to the source. The constructor
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated WSCOMMONS-559:
---
Fix Version/s: (was: XmlSchema 1.4.7)
This is an incompatible API change
Hello out there,
Barring objections, I am going to prepare a release candidate for
1.4.7 in the next few days and offer up a vote.
--benson
[
https://issues.apache.org/jira/browse/WSCOMMONS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912225#action_12912225
]
Benson Margulies commented on WSCOMMONS-504:
I'm not prepared to take
/orgapachews-042/
As usual, even the 'non-maven' files are in there.
This vote will remain open for 72 hours.
Here is my initial +1.
Thanks,
Benson Margulies
Here are the release notes:
Changes since 1.4.6:
** Bug
* [WSCOMMONS-484] - Performance enhancement for build from DOM
. Can we postpone the 1.4.7 release until this is
sorted out?
Fixed.
Dan
Andreas
On Sun, Sep 19, 2010 at 17:27, Benson Margulies bimargul...@gmail.com
wrote:
The XmlSchema tree turned to be in a relatively clean state w/r/t a
release. So, I've staged one.
This email formally offers
:28 pm Andreas Veithen wrote:
The change in r993403 causes build failures in at least one downstream
project, namely Woden. Can we postpone the 1.4.7 release until this is
sorted out?
Fixed.
Dan
Andreas
On Sun, Sep 19, 2010 at 17:27, Benson Margulies bimargul...@gmail.com
wrote
Well, some people might like it if you addressed the problem addressed
by the performance work before we move on, but some people might be
disappointed .
On Tue, Sep 7, 2010 at 12:15 PM, Daniel Kulp dk...@apache.org wrote:
On Sunday 05 September 2010 8:45:30 am Benson Margulies wrote:
I see
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906482#action_12906482
]
Benson Margulies commented on WSCOMMONS-559:
Chris,
Really, I'm trying
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reopened WSCOMMONS-559:
Assignee: Benson Margulies
Chris added another patch.
Utils to ease use
[
https://issues.apache.org/jira/browse/WSCOMMONS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved WSCOMMONS-520.
Fix Version/s: XmlSchema 1.4.7
Resolution: Fixed
patch applied.
Add
[
https://issues.apache.org/jira/browse/WSCOMMONS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved WSCOMMONS-539.
Fix Version/s: XmlSchema 1.4.6
Resolution: Fixed
992758
Infinite loop
The downloads don't work. I tried to fix them, and apparently failed. Can
someone else have a look?
[
https://issues.apache.org/jira/browse/WSCOMMONS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated WSCOMMONS-539:
---
Fix Version/s: XmlSchema 1.4.7
(was: XmlSchema 1.4.6
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved WSCOMMONS-559.
Fix Version/s: XmlSchema 1.4.7
Resolution: Fixed
992760
Utils to ease
[
https://issues.apache.org/jira/browse/WSCOMMONS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906337#action_12906337
]
Benson Margulies commented on WSCOMMONS-520:
Brian,
Could you post
I see some recent bug reports and even a couple of patches on XmlSchema.
There's the 1.4 branch where we're maintaining the classic code line: Java
1.4, lots of unfinished hanging apis, etc.
There's the trunk, where I produced a first pass at a 2.0. I think it could
be a reasonable forward
that the download.cgi based mechanism is the
preferred way to build download pages.
Andreas
On Sun, Sep 5, 2010 at 15:48, Benson Margulies bimargul...@gmail.com
wrote:
I see what I have to do to fix this once and for all.
that it
used Confluence and that the available options to build a download
page are more limited than in the case of a Maven site.
Andreas
On Sun, Sep 5, 2010 at 16:40, Benson Margulies bimargul...@gmail.com
wrote:
Andreas,
Well, I decided to follow the pattern at CXF instead, since Dan
[
https://issues.apache.org/jira/browse/WSCOMMONS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906399#action_12906399
]
Benson Margulies commented on WSCOMMONS-520:
I hate to be a pill
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906400#action_12906400
]
Benson Margulies commented on WSCOMMONS-559:
Chris,
Please join the dev
[
https://issues.apache.org/jira/browse/WSCOMMONS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906410#action_12906410
]
Benson Margulies commented on WSCOMMONS-559:
Chris,
My remark
[
https://issues.apache.org/jira/browse/WSCOMMONS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906243#action_12906243
]
Benson Margulies commented on WSCOMMONS-560:
Andreas,
I just reached
[
https://issues.apache.org/jira/browse/WSCOMMONS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed WSCOMMONS-560.
--
Resolution: Invalid
Wrong analysis of the problem I started with.
XDomUtil uses
Versions: XmlSchema 1.4.5
Reporter: Benson Margulies
All the functions in here are badly broken. They call getNamespaceURI as it it
returned the computed namespace of the element, not just the local declared
namespace. It's fairly susprising that this seems to cause as little trouble
I think you need to open an infra ticket.
On Jun 13, 2010, at 3:14 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Hi,
I'm preparing a release of Apache Axiom and we have a release of Axis2
in the pipeline. Can somebody please create corresponding staging
profiles in Nexus? The group
I don't see how it could be a bug. Any XML parser is permitted to
split these things for it's own convenience, it doesn't change the
infoset.
On Fri, Apr 30, 2010 at 8:48 AM, Hiranya Jayathilaka
hiranya...@gmail.com wrote:
On Fri, Apr 30, 2010 at 3:21 PM, Kasun Indrasiri kasun...@gmail.com
1 - 100 of 282 matches
Mail list logo
