That would only work if one assumes that the HTML generated by the
Maven site only contains relative links. I don't think that's the
case. What we really need to do is to clean up the Maven site and get
Axis2 1.6 out.
Andreas
On Mon, Oct 25, 2010 at 16:03, Sanjiva Weerawarana
On Mon, Oct 25, 2010 at 17:33, Benson Margulies bimargul...@gmail.com wrote:
1. I'm the only person who has touched the ws site. If you want to be
annoyed, be annoyed at me.
BTW, I was wondering why that didn't generate any SVN commit
notifications. At least I didn't see any kind of
On Mon, Oct 25, 2010 at 21:36, Daniel Kulp dk...@apache.org wrote:
On Monday 25 October 2010 3:21:27 pm Andreas Veithen wrote:
I think it's again a perfect example of a discussion that degenerates
because some people don't take the time to first get the facts and try
to think about what
Glen,
Can you try to make that consistent with the discussion in [1], i.e.
either do it as described in that discussion, or if you believe that
this is not the best solution, propose another one?
Andreas
[1] http://markmail.org/thread/xztnna4sfy2tzfq7
On Fri, Oct 29, 2010 at 17:35, Glen
FYI: As required by the mail below, I've requested migration to
svnpubsub for the Axis sites; see INFRA-5152. In practice, there are
only two things that change for release managers:
1. The locations of the generated sites in SVN have changed: they are
now all under
with supporting
java Enum support to POJO and did his GSoc project on improving axis2
json support. Mean time he has been contributing in user list as well.
The PMC voted to invite him/her to join as per the Apache process.
There were 10 +1 votes and no -1 votes.
Welcome aboard!
-- Andreas Veithen, on behalf
. In particular, he
has worked on upgrading Axis2 to HTTPClient 4 and
XmlSchema 2.0.
The PMC voted to invite him/her to join as per the Apache process.
There were 6 +1 votes and no -1 votes.
Welcome aboard!
-- Andreas Veithen, on behalf of the Axis PMC
[1] https://cwiki.apache.org/confluence/display/AXIS
Are you proposing to move them to the Apache Attic or to archive them
inside the Axis TLP?
Andreas
On Sun, Oct 27, 2013 at 1:23 AM, Deepal jayasinghe deep...@gmail.com wrote:
Dear All,
Savan/Java, Savan/C and Sandesha/C projects seem to be inactive for a
long time, and the Apache way is to
The same as moving them to the Attic, except that you don't cross PMC
boundaries. You basically do two things:
- Move the SVN trees of the projects to /axis/archive.
- Add a notice to their sites saying that they are no longer active
(see e.g. http://ws.apache.org/wsif/) or remove/archive their
I'm in favor of _archiving_ Axis1/C++ and Axis2/C. By archiving I mean
doing the same as we did with inactive projects in Apache Web
Services, i.e. moving them to an archive area inside the PMC's SVN
tree. I think that's much easier than moving them to the Attic PMC.
Regarding the Axis(/Java) 1.x
10 matches
Mail list logo
