You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera" <as...@wso2.com> on 2008/05/07 06:11:36 UTC
Fixing the dependencies and cutting the 1.2 Branch..
Hi Devs
Right now we are dependent on the SNAPSHOT versions of Apache Rampart
and WSS4J for Synapse. It would be good to get the next QA build, with
the RC's of these two, instead of the SNAPSHOTS, as we can then verify
all dependencies etc, and really make it close to a RC.
Thus I was thinking of branching, and temporarily adding a private Maven
repo (to the branch) to get the RC's of the above from there. We can
continue any fixes and/or development on the branch for what goes into
1.2 (we can easily svn switch), and merge back changes to the trunk
after the release.
I know Andreas is working on some fixes right now, so I will wait for
his confirmation on this,.. if any others have any work in progress do
let me know
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Fixing the dependencies and cutting the 1.2 Branch..
Posted by Paul Fremantle <pz...@gmail.com>.
+1
Paul
On Wed, May 7, 2008 at 7:02 AM, Ruwan Linton <ru...@gmail.com> wrote:
> +1 for cutting the branch and adding the RCs of Rampart and WSS4J by adding
> a private repo to the branch.
>
> BTW: If we can complete changes on this branch by Friday (the next and the
> last QA build will be done on Friday), and fix only the blockers afterwards,
> I think it will be better since we are planing to release on the 16th
> (provided that rampart and wss4j will be official out by then)
>
> Thanks,
> Ruwan
>
>
>
> On Wed, May 7, 2008 at 9:41 AM, Asankha C. Perera <as...@wso2.com> wrote:
> > Hi Devs
> >
> > Right now we are dependent on the SNAPSHOT versions of Apache Rampart and
> WSS4J for Synapse. It would be good to get the next QA build, with the RC's
> of these two, instead of the SNAPSHOTS, as we can then verify all
> dependencies etc, and really make it close to a RC.
> >
> > Thus I was thinking of branching, and temporarily adding a private Maven
> repo (to the branch) to get the RC's of the above from there. We can
> continue any fixes and/or development on the branch for what goes into 1.2
> (we can easily svn switch), and merge back changes to the trunk after the
> release.
> >
> > I know Andreas is working on some fixes right now, so I will wait for his
> confirmation on this,.. if any others have any work in progress do let me
> know
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Fixing the dependencies and cutting the 1.2 Branch..
Posted by Ruwan Linton <ru...@gmail.com>.
+1 for cutting the branch and adding the RCs of Rampart and WSS4J by adding
a private repo to the branch.
BTW: If we can complete changes on this branch by Friday (the next and the
last QA build will be done on Friday), and fix only the blockers afterwards,
I think it will be better since we are planing to release on the 16th
(provided that rampart and wss4j will be official out by then)
Thanks,
Ruwan
On Wed, May 7, 2008 at 9:41 AM, Asankha C. Perera <as...@wso2.com> wrote:
> Hi Devs
>
> Right now we are dependent on the SNAPSHOT versions of Apache Rampart and
> WSS4J for Synapse. It would be good to get the next QA build, with the RC's
> of these two, instead of the SNAPSHOTS, as we can then verify all
> dependencies etc, and really make it close to a RC.
>
> Thus I was thinking of branching, and temporarily adding a private Maven
> repo (to the branch) to get the RC's of the above from there. We can
> continue any fixes and/or development on the branch for what goes into 1.2
> (we can easily svn switch), and merge back changes to the trunk after the
> release.
>
> I know Andreas is working on some fixes right now, so I will wait for his
> confirmation on this,.. if any others have any work in progress do let me
> know
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Cleaning up dependencies
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Asankha and all,
Since we did not receive any other view on this I have removed the quickfix
transport jars as well as qpid jars.
Please see below for more details of the dependencies.
> New additions for Synapse 1.2
> ---------------------------------------------------
> tribes-6.0.14.jar (axis2-clustering)
> juli-6.0.14.jar (axis2-clustering)
> mex-1.4-impl.jar (rampart-policy)
>
> xmlParserAPIs-2.6.0.jar (axis2-kernel)
> geronimo-stax-api_1.0_spec-1.0.1.jar (axis2-kernel)
> woden-impl-dom-1.0M8.jar (axis2-kernel)
>
> mercury-core-0.9.jar (new RM implementation)
>
> spring-xml-1.0.3.jar (Synapse transformations)
> commons-io-1.4.jar (Synapse transports)
>
commons-lang-2.1.jar (Synapse transports)
>
> To be removed from binary distribution
> ------------------------------------------------------------------
> mina-core-1.1.0.jar (QuickFix)
> quickfixj-core-1.3.1.jar (QuickFix)
> quickfixj-msg-fix40-1.3.1.jar (QuickFix)
> quickfixj-msg-fix41-1.3.1.jar (QuickFix)
> quickfixj-msg-fix42-1.3.1.jar (QuickFix)
> quickfixj-msg-fix43-1.3.1.jar (QuickFix)
> quickfixj-msg-fix44-1.3.1.jar (QuickFix)
> slf4j-api-1.3.0.jar (QuickFix)
> slf4j-jdk14-1.3.0.jar (QuickFix)
all the above quickfixj deps have been removed
>
>
> mina-filter-ssl-1.0.0.jar (QPid)
> qpid-client-1.0-incubating-M3-615355.jar (QPid)
> qpid-common-1.0-incubating-M3-615355.jar (QPid)
> commons-cli-1.0.jar (QPid)
> geronimo-jms_1.1_spec-1.0.jar (QPid)
> geronimo-jms_1.1_spec-1.1.jar (QPid)
also the above qpid related deps have been removed.
>
>
> Already removed from 1.2 build as we do not depend on these
>
> ---------------------------------------------------------------------------------------------------------
> xmlbeans-2.3.0.jar (rampart-policy)
> geronimo-activation_1.1_spec-1.0.1.jar (axis2-kernel)
> geronimo-javamail_1.4_spec-1.2.jar (axis2-kernel)
>
>
Thanks,
Ruwan
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Cleaning up dependencies
Posted by "Asankha C. Perera" <as...@wso2.com>.
> my feeling is that we should not ship QuickFixJ and Qpid jars and we
> can keep those two transports commented on the axis2.xml, and we must
> add sections on this to the Sample Setup Guide. So when people need to
> run these samples we can ask them to put these jars.
>
> Otherwise simple mediation case also carries all these jar files which
> increases the synapse distribution size.
+1.. unless there are any other views, lets remove these from the core
build of Synapse
Synapse 1.2 no longer needs
-------------------------------------------------
sandesha2-core-1.3.jar (previous RM implementation)
sandesha2-policy-1.3.jar (previous RM implementation)
New additions for Synapse 1.2
---------------------------------------------------
tribes-6.0.14.jar (axis2-clustering)
juli-6.0.14.jar (axis2-clustering)
mex-1.4-impl.jar (rampart-policy)
xmlParserAPIs-2.6.0.jar (axis2-kernel)
geronimo-stax-api_1.0_spec-1.0.1.jar (axis2-kernel)
woden-impl-dom-1.0M8.jar (axis2-kernel)
mercury-core-0.9.jar (new RM implementation)
spring-xml-1.0.3.jar (Synapse transformations)
commons-io-1.4.jar (Synapse transports)
To be removed from binary distribution
------------------------------------------------------------------
mina-core-1.1.0.jar (QuickFix)
quickfixj-core-1.3.1.jar (QuickFix)
quickfixj-msg-fix40-1.3.1.jar (QuickFix)
quickfixj-msg-fix41-1.3.1.jar (QuickFix)
quickfixj-msg-fix42-1.3.1.jar (QuickFix)
quickfixj-msg-fix43-1.3.1.jar (QuickFix)
quickfixj-msg-fix44-1.3.1.jar (QuickFix)
slf4j-api-1.3.0.jar (QuickFix)
slf4j-jdk14-1.3.0.jar (QuickFix)
mina-filter-ssl-1.0.0.jar (QPid)
qpid-client-1.0-incubating-M3-615355.jar (QPid)
qpid-common-1.0-incubating-M3-615355.jar (QPid)
commons-cli-1.0.jar (QPid)
geronimo-jms_1.1_spec-1.0.jar (QPid)
geronimo-jms_1.1_spec-1.1.jar (QPid)
Already removed from 1.2 build as we do not depend on these
---------------------------------------------------------------------------------------------------------
xmlbeans-2.3.0.jar (rampart-policy)
geronimo-activation_1.1_spec-1.0.1.jar (axis2-kernel)
geronimo-javamail_1.4_spec-1.2.jar (axis2-kernel)
--- TODO : Verify if this addition is really needed---
commons-lang-2.1.jar (Maven site plugin?!)
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Cleaning up dependencies
Posted by Ruwan Linton <ru...@gmail.com>.
BTW: we need commons-io due to fix that has been done by andreas to use
CountingOutputStream class from that.
Thanks,
Ruwan
On Thu, May 8, 2008 at 1:52 PM, Ruwan Linton <ru...@gmail.com> wrote:
> Asankha,
>
> my feeling is that we should not ship QuickFixJ and Qpid jars and we can
> keep those two transports commented on the axis2.xml, and we must add
> sections on this to the Sample Setup Guide. So when people need to run these
> samples we can ask them to put these jars.
>
> Otherwise simple mediation case also carries all these jar files which
> increases the synapse distribution size.
>
> WDYT?
>
> Thanks,
> Ruwan
>
>
> On Thu, May 8, 2008 at 12:13 PM, Asankha C. Perera <as...@wso2.com>
> wrote:
>
> > Hi All
> >
> > Currently I'm seeing the following differences between the last 1.1.1
> > release and the upcoming 1.2 SNAPSHOT and reviewing these additions..
> >
> > Do you think we should ship the QuickFix and AMQP JARs with the binary
> > distribution?
> >
> > asankha
> >
> >
> > Removed
> > ---------------
> > sandesha2-core-1.3.jar (previous RM implementation)
> > sandesha2-policy-1.3.jar (previous RM implementation)
> >
> > Changed
> > ---------------
> > geronimo-jms_1.1_spec-1.1.jar ** to ** geronimo-jms_1.1_spec-1.0.jar
> > (Need to check why the version changed and if this is correct)
> >
> > Additions to 1.2
> > ---------------------------
> > tribes-6.0.14.jar - (for clustering on throttle, cache mediators?)
> > mercury-core-0.9.jar - (new RM implementation)
> >
> > -- should we ship the QuickFix and AMQP JAR's by default? --
> > mina-core-1.1.0.jar
> > mina-filter-ssl-1.0.0.jar
> > quickfixj-core-1.3.1.jar
> > quickfixj-msg-fix40-1.3.1.jar
> > quickfixj-msg-fix41-1.3.1.jar
> > quickfixj-msg-fix42-1.3.1.jar
> > quickfixj-msg-fix43-1.3.1.jar
> > quickfixj-msg-fix44-1.3.1.jar
> > slf4j-api-1.3.0.jar
> > slf4j-jdk14-1.3.0.jar
> > qpid-client-1.0-incubating-M3-615355.jar
> > qpid-common-1.0-incubating-M3-615355.jar
> >
> >
> > --- Verify if these additions are really needed---
> > xmlbeans-2.3.0.jar
> > xmlParserAPIs-2.6.0.jar
> > spring-xml-1.0.3.jar
> > commons-cli-1.0.jar
> > commons-io-1.4.jar
> > commons-lang-2.1.jar
> > geronimo-stax-api_1.0_spec-1.0.1.jar
> > juli-6.0.14.jar woden-impl-dom-1.0M8.jar
> > mex-1.4-impl.jar
> > geronimo-activation_1.1_spec-1.0.1.jar
> > geronimo-javamail_1.4_spec-1.2.jar
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Cleaning up dependencies
Posted by Ruwan Linton <ru...@gmail.com>.
Asankha,
my feeling is that we should not ship QuickFixJ and Qpid jars and we can
keep those two transports commented on the axis2.xml, and we must add
sections on this to the Sample Setup Guide. So when people need to run these
samples we can ask them to put these jars.
Otherwise simple mediation case also carries all these jar files which
increases the synapse distribution size.
WDYT?
Thanks,
Ruwan
On Thu, May 8, 2008 at 12:13 PM, Asankha C. Perera <as...@wso2.com> wrote:
> Hi All
>
> Currently I'm seeing the following differences between the last 1.1.1
> release and the upcoming 1.2 SNAPSHOT and reviewing these additions..
>
> Do you think we should ship the QuickFix and AMQP JARs with the binary
> distribution?
>
> asankha
>
>
> Removed
> ---------------
> sandesha2-core-1.3.jar (previous RM implementation)
> sandesha2-policy-1.3.jar (previous RM implementation)
>
> Changed
> ---------------
> geronimo-jms_1.1_spec-1.1.jar ** to ** geronimo-jms_1.1_spec-1.0.jar (Need
> to check why the version changed and if this is correct)
>
> Additions to 1.2
> ---------------------------
> tribes-6.0.14.jar - (for clustering on throttle, cache mediators?)
> mercury-core-0.9.jar - (new RM implementation)
>
> -- should we ship the QuickFix and AMQP JAR's by default? --
> mina-core-1.1.0.jar
> mina-filter-ssl-1.0.0.jar
> quickfixj-core-1.3.1.jar
> quickfixj-msg-fix40-1.3.1.jar
> quickfixj-msg-fix41-1.3.1.jar
> quickfixj-msg-fix42-1.3.1.jar
> quickfixj-msg-fix43-1.3.1.jar
> quickfixj-msg-fix44-1.3.1.jar
> slf4j-api-1.3.0.jar
> slf4j-jdk14-1.3.0.jar
> qpid-client-1.0-incubating-M3-615355.jar
> qpid-common-1.0-incubating-M3-615355.jar
>
>
> --- Verify if these additions are really needed---
> xmlbeans-2.3.0.jar
> xmlParserAPIs-2.6.0.jar
> spring-xml-1.0.3.jar
> commons-cli-1.0.jar
> commons-io-1.4.jar
> commons-lang-2.1.jar
> geronimo-stax-api_1.0_spec-1.0.1.jar
> juli-6.0.14.jar woden-impl-dom-1.0M8.jar
> mex-1.4-impl.jar
> geronimo-activation_1.1_spec-1.0.1.jar
> geronimo-javamail_1.4_spec-1.2.jar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Cleaning up dependencies
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi All
Currently I'm seeing the following differences between the last 1.1.1
release and the upcoming 1.2 SNAPSHOT and reviewing these additions..
Do you think we should ship the QuickFix and AMQP JARs with the binary
distribution?
asankha
Removed
---------------
sandesha2-core-1.3.jar (previous RM implementation)
sandesha2-policy-1.3.jar (previous RM implementation)
Changed
---------------
geronimo-jms_1.1_spec-1.1.jar ** to ** geronimo-jms_1.1_spec-1.0.jar
(Need to check why the version changed and if this is correct)
Additions to 1.2
---------------------------
tribes-6.0.14.jar - (for clustering on throttle, cache mediators?)
mercury-core-0.9.jar - (new RM implementation)
-- should we ship the QuickFix and AMQP JAR's by default? --
mina-core-1.1.0.jar
mina-filter-ssl-1.0.0.jar
quickfixj-core-1.3.1.jar
quickfixj-msg-fix40-1.3.1.jar
quickfixj-msg-fix41-1.3.1.jar
quickfixj-msg-fix42-1.3.1.jar
quickfixj-msg-fix43-1.3.1.jar
quickfixj-msg-fix44-1.3.1.jar
slf4j-api-1.3.0.jar
slf4j-jdk14-1.3.0.jar
qpid-client-1.0-incubating-M3-615355.jar
qpid-common-1.0-incubating-M3-615355.jar
--- Verify if these additions are really needed---
xmlbeans-2.3.0.jar
xmlParserAPIs-2.6.0.jar
spring-xml-1.0.3.jar
commons-cli-1.0.jar
commons-io-1.4.jar
commons-lang-2.1.jar
geronimo-stax-api_1.0_spec-1.0.1.jar
juli-6.0.14.jar
woden-impl-dom-1.0M8.jar
mex-1.4-impl.jar
geronimo-activation_1.1_spec-1.0.1.jar
geronimo-javamail_1.4_spec-1.2.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Cleaning up dependencies
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi All
Currently I'm seeing the following differences between the last 1.1.1
release and the upcoming 1.2 SNAPSHOT and reviewing these additions..
Do you think we should ship the QuickFix and AMQP JARs with the binary
distribution?
asankha
Removed
---------------
sandesha2-core-1.3.jar (previous RM implementation)
sandesha2-policy-1.3.jar (previous RM implementation)
Changed
---------------
geronimo-jms_1.1_spec-1.1.jar ** to ** geronimo-jms_1.1_spec-1.0.jar
(Need to check why the version changed and if this is correct)
Additions to 1.2
---------------------------
tribes-6.0.14.jar - (for clustering on throttle, cache mediators?)
mercury-core-0.9.jar - (new RM implementation)
-- should we ship the QuickFix and AMQP JAR's by default? --
mina-core-1.1.0.jar
mina-filter-ssl-1.0.0.jar
quickfixj-core-1.3.1.jar
quickfixj-msg-fix40-1.3.1.jar
quickfixj-msg-fix41-1.3.1.jar
quickfixj-msg-fix42-1.3.1.jar
quickfixj-msg-fix43-1.3.1.jar
quickfixj-msg-fix44-1.3.1.jar
slf4j-api-1.3.0.jar
slf4j-jdk14-1.3.0.jar
qpid-client-1.0-incubating-M3-615355.jar
qpid-common-1.0-incubating-M3-615355.jar
--- Verify if these additions are really needed---
xmlbeans-2.3.0.jar
xmlParserAPIs-2.6.0.jar
spring-xml-1.0.3.jar
commons-cli-1.0.jar
commons-io-1.4.jar
commons-lang-2.1.jar
geronimo-stax-api_1.0_spec-1.0.1.jar
juli-6.0.14.jar
woden-impl-dom-1.0M8.jar
mex-1.4-impl.jar
geronimo-activation_1.1_spec-1.0.1.jar
geronimo-javamail_1.4_spec-1.2.jar
Re: Fixing the dependencies and cutting the 1.2 Branch..
Posted by "Asankha C. Perera" <as...@wso2.com>.
Thanks all.. I created the branch
Please svn switch to the new branch:
svn switch *https://svn.apache.org/repos/asf/synapse/branches/1.2*
thanks
asankha
Andreas Veithen wrote:
>> I know Andreas is working on some fixes right now, so I will wait for
>> his confirmation on this,.. if any others have any work in progress do
>> let me know
>
> I don't have any local changes for the moment. I'm currently working
> on SYNAPSE-282 and since the code I'm developing is not essential for
> the 1.2 release I will add it directly to the trunk when it's ready.
> So you can go ahead and create a branch.
>
> Andreas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
Re: Fixing the dependencies and cutting the 1.2 Branch..
Posted by Andreas Veithen <an...@skynet.be>.
> I know Andreas is working on some fixes right now, so I will wait for
> his confirmation on this,.. if any others have any work in progress do
> let me know
I don't have any local changes for the moment. I'm currently working
on SYNAPSE-282 and since the code I'm developing is not essential for
the 1.2 release I will add it directly to the trunk when it's ready.
So you can go ahead and create a branch.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org