Return-Path: Delivered-To: apmail-ws-kandula-dev-archive@www.apache.org Received: (qmail 59143 invoked from network); 27 May 2010 12:55:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 May 2010 12:55:47 -0000 Received: (qmail 63160 invoked by uid 500); 27 May 2010 12:55:47 -0000 Delivered-To: apmail-ws-kandula-dev-archive@ws.apache.org Received: (qmail 62791 invoked by uid 500); 27 May 2010 12:55:46 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 62783 invoked by uid 99); 27 May 2010 12:55:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 12:55:46 +0000 X-ASF-Spam-Status: No, hits=3.9 required=10.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rickmcg@gmail.com designates 209.85.212.45 as permitted sender) Received: from [209.85.212.45] (HELO mail-vw0-f45.google.com) (209.85.212.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 12:55:38 +0000 Received: by vws6 with SMTP id 6so1780504vws.32 for ; Thu, 27 May 2010 05:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type; bh=gUGdtWIn2NjpySOS+9aFkTtqOc5IRjgEL3bH/H9XWVs=; b=xx4zPXkVDt50lukawi3gCELTuoaM0br+R8rhsrARtpP9SCcMwpd7GSHg/Q5jdvDeek UV4yBqC9CU7ZNIJxH9wTnkyHR6GAWsctJ9cnX6H42VwF+HGOauZ34+0AQw9igf9aGF3O jje7Cxfpq8NtDVV7KEmhizjskbnJqk6Fb9E0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type; b=fQjHWsRyG1pdjBucLucY3SZW90mmKcof2uxe2RAoYLpocpGzqupy6shfDbQnVQTpsX e5D4Lj1vbF4lHPsXfLqCB6j+6t5/nz2O2+dNQs/2hee6MW/mhv7HFAFXlnS69k4+hO+z NtcTBKh1tdkMh8l2hbhSEaKIM/uOg9MSUL35Y= Received: by 10.220.44.20 with SMTP id y20mr7442144vce.237.1274964916282; Thu, 27 May 2010 05:55:16 -0700 (PDT) Received: from [192.168.1.100] (24-151-82-15.dhcp.nwtn.ct.charter.com [24.151.82.15]) by mx.google.com with ESMTPS id b22sm4948724vcp.20.2010.05.27.05.55.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 May 2010 05:55:15 -0700 (PDT) Message-ID: <4BFE6BB0.7070909@gmail.com> Date: Thu, 27 May 2010 08:55:12 -0400 From: Rick McGuire Reply-To: rickmcg@gmail.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: java-dev@axis.apache.org Subject: Re: Split packages issue (AXIS2-4311) References: ,<4BFE4E0D.8080607@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050706090108000406000004" X-Virus-Checked: Checked by ClamAV on apache.org --------------050706090108000406000004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit On 5/27/2010 8:29 AM, Martin Gainty wrote: > devs: to accomodate a delta on a specific style a point release makes > far more sense e.g. Axis2.1.5.1.1 > > when a new base library (Axiom) becomes available a new 'full release' > (with all the patches and previous point releases) is more than > justified..(provided TC's are factored in!) > e.g. Axis2-1.6 > > Re:split packages: maven shaded-plugin can handle most 'split > package' issues or is there another *unknown* interaction at play? > > McGuire: > what gating issues are you seeing with current build of Axis Geronimo 3.0 is restructuring to be an OSGi-based kernel. This means all of the jars that make up the core server runtime need to be OSGi bundles. The Axis2 jars include OSGi imports/exports, but because of the split package issue, they cannot be used together in the same runtime, which makes the OSGi information essentially useless. The only fix we have is to repackage all of the axis2 jars into a single uber bundle to sidestep the problem. The Geronimo build structure is such that any jars that we repackage as bundles get released as separate packages. This means every time we need to update the axis2 version, we first have to spin a new version of the Geronimo repackaged bundle, have a vote on that release, then update Geronimo itself to pick up the new version and have a second vote. This is doable, but fixing the problem at the source makes life a lot easier for us. We have many dependencies we have to worry about, so eliminating as many special considerations as possible helps streamline the entire release process. Rick > ? > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de d�ni et de confidentialit� > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede > unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. > Diese Nachricht dient lediglich dem Austausch von Informationen und > entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten > Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den > Inhalt uebernehmen. > > Ce message est confidentiel et peut �tre privil�gi�. Si vous n'�tes pas le destinataire pr�vu, nous te demandons avec bont� que pour satisfaire informez l'exp�diteur. N'importe quelle diffusion non autoris�e ou la copie de ceci est interdite. Ce message sert � l'information seulement et n'aura pas n'importe quel effet l�galement obligatoire. �tant donn� que les email peuvent facilement �tre sujets � la manipulation, nous ne pouvons accepter aucune responsabilit� pour le contenu fourni. > > > > > > > Date: Thu, 27 May 2010 06:48:45 -0400 > > From: rickmcg@gmail.com > > To: java-dev@axis.apache.org > > Subject: Re: Split packages issue (AXIS2-4311) > > > > On 5/26/2010 3:51 PM, Andreas Veithen wrote: > > > In order to successfully build, they currently have to do that, but I > > > doubt that they consider that as a viable option. Note that they also > > > have the "option" to drop Axis2 support in favor of CXF [1]... > > > > > This is an option we really prefer not to use, since it complicates our > > release process because repackaged jar files get released separately > > from the main server. We'd really prefer to consume the dependency > > directly without requiring this extra step. > > > > Rick > > > > > [1] https://cwiki.apache.org/GMOxDOC20/configure-jax-ws-engine.html > > > > > > On Tue, May 25, 2010 at 13:52, Amila Suriarachchi > > > wrote: > > > > > >> > > >> On Sun, May 23, 2010 at 5:21 PM, Andreas > Veithen > > >> wrote: > > >> > > >>> On Sat, May 22, 2010 at 06:41, Amila Suriarachchi > > >>> wrote: > > >>> > > >>>> > > >>>> On Fri, May 21, 2010 at 12:43 AM, Andreas Veithen > > >>>> wrote: > > >>>> > > >>>>> Hi devs, > > >>>>> > > >>>>> I think we should have a look at AXIS2-4311 and see if and how > we can > > >>>>> fix that for the 1.6 release. > > >>>>> > > >>>>> I had a quick lock at the different packages and here are my > > >>>>> preliminary conclusions: > > >>>>> > > >>>>> * org.apache.axis2.util in axis2-adb only contains a single > utility > > >>>>> class --> should not cause much trouble to move it elsewhere > > >>>>> * org.apache.axis2.transport.jms is no longer in axis2-kernel. > > >>>>> * org.apache.axis2.transport.http in axis2-kernel mainly > contains the > > >>>>> standard MessageFormatter implementations. Obviously the > package name > > >>>>> is no longer appropriate for this and it would make sense to move > > >>>>> these classes. However, this means that users need to change their > > >>>>> axis2.xml file. Note that cleaning this up would also be a good > > >>>>> opportunity to move the non standard message > builders/formatters from > > >>>>> the transports project to the core Axis2 project, as discussed > back in > > >>>>> december 2008 [1] [2]. > > >>>>> > > >>>>> Thoughts? > > >>>>> > > >>>> I agree with you that there are some areas we need to re factor and > > >>>> find > > >>>> the proper way of doing it. > > >>>> > > >>>> We did the Axis2 1.5 release last year May but actually cut the > branch > > >>>> on > > >>>> December as I remember. So my idea was to do an Axis2 1.6 > release with > > >>>> whatever the fixes we have done after cut the 1.5 branch. Otherwise > > >>>> people > > >>>> tend to think Axis2 has died. > > >>>> > > >>>> The split package problem is actually part of the whole Axis2 > OSGI work. > > >>>> Saminda started this discussion some time ago and there was no > progress > > >>>> after that. > > >>>> > > >>>> So my suggestion is to just wait until Axiom and woden releases > (which I > > >>>> believe happen shortly) and cut the Axis2 1.6 branch. Then we > can take > > >>>> the > > >>>> topics like "Axis2 OSGI" , "Axis2 Spring integration" and do > subsequent > > >>>> releases with them. > > >>>> > > >>>> And also I think synapse people wait on Axis2 1.6 release. So > lets do > > >>>> Axis2 > > >>>> 1.6 with whatever fixes we can do with and target major changes > to Axis2 > > >>>> 1.7. > > >>>> > > >>> I tend to agree with that from a purely Axis2 point of view. Not > sure > > >>> though what the Geronimo folks think about that, considering > that 1.7 > > >>> will not be release before a long time. Don't forget that they > are one > > >>> of our important "customers"... > > >>> > > >> I haven't looked into the jira, when I send the reply. As I saw > they have > > >> the option of using it as a one bundle isn't it? > > >> > > >> thanks, > > >> Amila. > > >> > > >> > > >>> > > >>>> thanks, > > >>>> Amila. > > >>>> > > >>>> > > >>>> > > >>>>> Andreas > > >>>>> > > >>>>> [1] http://markmail.org/message/fgtbr6tzpfemlery > > >>>>> [2] http://markmail.org/thread/i6cq72unknnnvjy5 > > >>>>> > > >>>>> > --------------------------------------------------------------------- > > >>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > > >>>>> For additional commands, e-mail: java-dev-help@axis.apache.org > > >>>>> > > >>>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Amila Suriarachchi > > >>>> WSO2 Inc. > > >>>> blog: http://amilachinthaka.blogspot.com/ > > >>>> > > >>>> > > >>> > --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > > >>> For additional commands, e-mail: java-dev-help@axis.apache.org > > >>> > > >>> > > >> > > >> > > >> -- > > >> Amila Suriarachchi > > >> WSO2 Inc. > > >> blog: http://amilachinthaka.blogspot.com/ > > >> > > >> > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > > > For additional commands, e-mail: java-dev-help@axis.apache.org > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > > For additional commands, e-mail: java-dev-help@axis.apache.org > > > > ------------------------------------------------------------------------ > The New Busy think 9 to 5 is a cute idea. Combine multiple calendars > with Hotmail. Get busy. > --------------050706090108000406000004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 5/27/2010 8:29 AM, Martin Gainty wrote:
devs: to accomodate a delta on a specific style a point release makes far more sense e.g. Axis2.1.5.1.1
 
when a new base library (Axiom) becomes available a new 'full release' (with all the patches and previous point releases) is more than justified..(provided TC's are factored in!)
e.g. Axis2-1.6
 
Re:split packages: maven shaded-plugin can handle most 'split package' issues or is there another *unknown* interaction at play?
 
McGuire:
what gating issues are you seeing with current build of Axis

Geronimo 3.0 is restructuring to be an OSGi-based kernel.  This means all of the jars that make up the core server runtime need to be OSGi bundles.  The Axis2 jars include OSGi imports/exports, but because of the split package issue, they cannot be used together in the same runtime, which makes the OSGi information essentially useless.  The only fix we have is to repackage all of the axis2 jars into a single uber bundle to sidestep the problem.

The Geronimo build structure is such that any jars that we repackage as bundles get released as separate packages.  This means every time we need to update the axis2 version, we first have to spin a new version of the Geronimo repackaged bundle, have a vote on that release, then update Geronimo itself to pick up the new version and have a second vote.  This is doable, but fixing the problem at the source makes life a lot easier for us.  We have many dependencies we have to worry about, so eliminating as many special considerations as possible helps streamline the entire release process.

Rick


?
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.




 
> Date: Thu, 27 May 2010 06:48:45 -0400
> From: rickmcg@gmail.com
> To: java-dev@axis.apache.org
> Subject: Re: Split packages issue (AXIS2-4311)
>
> On 5/26/2010 3:51 PM, Andreas Veithen wrote:
> > In order to successfully build, they currently have to do that, but I
> > doubt that they consider that as a viable option. Note that they also
> > have the "option" to drop Axis2 support in favor of CXF [1]...
> >
> This is an option we really prefer not to use, since it complicates our
> release process because repackaged jar files get released separately
> from the main server. We'd really prefer to consume the dependency
> directly without requiring this extra step.
>
> Rick
>
> > [1] https://cwiki.apache.org/GMOxDOC20/configure-jax-ws-engine.html
> >
> > On Tue, May 25, 2010 at 13:52, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com> wrote:
> >
> >>
> >> On Sun, May 23, 2010 at 5:21 PM, Andreas Veithen<andreas.veithen@gmail.com>
> >> wrote:
> >>
> >>> On Sat, May 22, 2010 at 06:41, Amila Suriarachchi
> >>> <amilasuriarachchi@gmail.com> wrote:
> >>>
> >>>>
> >>>> On Fri, May 21, 2010 at 12:43 AM, Andreas Veithen
> >>>> <andreas.veithen@gmail.com> wrote:
> >>>>
> >>>>> Hi devs,
> >>>>>
> >>>>> I think we should have a look at AXIS2-4311 and see if and how we can
> >>>>> fix that for the 1.6 release.
> >>>>>
> >>>>> I had a quick lock at the different packages and here are my
> >>>>> preliminary conclusions:
> >>>>>
> >>>>> * org.apache.axis2.util in axis2-adb only contains a single utility
> >>>>> class --> should not cause much trouble to move it elsewhere
> >>>>> * org.apache.axis2.transport.jms is no longer in axis2-kernel.
> >>>>> * org.apache.axis2.transport.http in axis2-kernel mainly contains the
> >>>>> standard MessageFormatter implementations. Obviously the package name
> >>>>> is no longer appropriate for this and it would make sense to move
> >>>>> these classes. However, this means that users need to change their
> >>>>> axis2.xml file. Note that cleaning this up would also be a good
> >>>>> opportunity to move the non standard message builders/formatters from
> >>>>> the transports project to the core Axis2 project, as discussed back in
> >>>>> december 2008 [1] [2].
> >>>>>
> >>>>> Thoughts?
> >>>>>
> >>>> I agree with you that there are some areas we need to re factor and
> >>>> find
> >>>> the proper way of doing it.
> >>>>
> >>>> We did the Axis2 1.5 release last year May but actually cut the branch
> >>>> on
> >>>> December as I remember. So my idea was to do an Axis2 1.6 release with
> >>>> whatever the fixes we have done after cut the 1.5 branch. Otherwise
> >>>> people
> >>>> tend to think Axis2 has died.
> >>>>
> >>>> The split package problem is actually part of the whole Axis2 OSGI work.
> >>>> Saminda started this discussion some time ago and there was no progress
> >>>> after that.
> >>>>
> >>>> So my suggestion is to just wait until Axiom and woden releases (which I
> >>>> believe happen shortly) and cut the Axis2 1.6 branch. Then we can take
> >>>> the
> >>>> topics like "Axis2 OSGI" , "Axis2 Spring integration" and do subsequent
> >>>> releases with them.
> >>>>
> >>>> And also I think synapse people wait on Axis2 1.6 release. So lets do
> >>>> Axis2
> >>>> 1.6 with whatever fixes we can do with and target major changes to Axis2
> >>>> 1.7.
> >>>>
> >>> I tend to agree with that from a purely Axis2 point of view. Not sure
> >>> though what the Geronimo folks think about that, considering that 1.7
> >>> will not be release before a long time. Don't forget that they are one
> >>> of our important "customers"...
> >>>
> >> I haven't looked into the jira, when I send the reply. As I saw they have
> >> the option of using it as a one bundle isn't it?
> >>
> >> thanks,
> >> Amila.
> >>
> >>
> >>>
> >>>> thanks,
> >>>> Amila.
> >>>>
> >>>>
> >>>>
> >>>>> Andreas
> >>>>>
> >>>>> [1] http://markmail.org/message/fgtbr6tzpfemlery
> >>>>> [2] http://markmail.org/thread/i6cq72unknnnvjy5
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Amila Suriarachchi
> >>>> WSO2 Inc.
> >>>> blog: http://amilachinthaka.blogspot.com/
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >>
> >>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>

The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. Get busy.

--------------050706090108000406000004--