It was probably a jar file mismatch. It seems that the maven proxy I have to use (Artifactory) doesn't give me the good ones. Perhaps a misconfiguration... Not using Artifactory building is a succes.
Sorry for my questions... -----Message d'origine----- De : Ruwan Linton [mailto:[EMAIL PROTECTED] Envoyé : lundi 7 janvier 2008 13:22 À : [email protected] Objet : Re: RE : Synapse 1.1 & Maven Hi Laurent, Both the svn and the source download should work fine... I think there was a jar file mismatch. Can you try to build the source using the -U switch (i.e. : mvn clean install -U) and let me know whether you are running in to that problem again. If so try to get a svn checkout and build the source @ the svn. For me both of these are working. Thanks, Ruwan On Jan 7, 2008 3:33 PM, Laurent CHARTIER <[EMAIL PROTECTED]> wrote: > I follow the steps of the guide but i still have a compilation > error... > - Download the source distribution on the site > - Building (mvn clean install) > > My environnement is: > Maven version: 2.0.8 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > May i try to obtain the sources fron svn? > > Best regards. > > -----Message d'origine----- > De : Paul Fremantle [mailto:[EMAIL PROTECTED] > Envoyé : lundi 7 janvier 2008 10:36 > À : [email protected] > Objet : Re: Synapse 1.1 & Maven > > > Laurent > > Here is the Building guide that is about to go up on the website > (thanks to > Ant) > > Obtaining the code > > You can obtain the code by downloading the source distribution or, > more commonly, checking out the source from Subversion (SVN). To > checkout the code from Subversion, firstly get subversion installed, > then use the following commands: > > svn co http://svn.apache.org/repos/asf/webservices/synapse/trunk/java > [path-where-you-want-the-code]<http://svn.apache.org/repos/asf/webserv > ices/synapse/trunk/java%5Bpath-where-you-want-the-code%5D> > > If you are a committer then you need to use the secure version: > > svn co https://svn.apache.org/repos/asf/webservices/synapse/trunk/java > [path-where-you-want-the-code]<https://svn.apache.org/repos/asf/webser > vices/synapse/trunk/java%5Bpath-where-you-want-the-code%5D> > > Building > > The first thing you need to build the code is JDK1.5 and Maven2. You > need at least version 2.0.7. Synapse is not yet tested on JDK1.6 or > above. > > To build, in the top level Synapse folder do: > > mvn clean install > > To build the distribution archive packages do (the distribution > archives are created in new folder named target): > > mvn assembly:assembly -Drelease > > Offline builds > > The first time you build Maven downloads all the required dependency > jars to your local repository, after there has been a successful build > you can add the "-o" parameter to the above commands to run in offline > mode which avoids > going out to remote Maven repositories. The result - the build runs > faster. > > mvn clean install -o > > or > > mvn assembly:assembly -Drelease -o > > Skipping tests > > If you don't want to have all the Synapse test cases run during the > build you can add the parameter "-Dmaven.test.skip=true", eg: > > mvn clean install -o -Dmaven.test.skip=true > > or > > mvn assembly:assembly -Drelease -o -Dmaven.test.skip=true > > Updating Snapshots > > Sometimes the trunk build uses snapshot versions of some dependency > jars which can go out of date but may not get refreshed in your local > Maven repository even when the "-o" parameter is not used. So if you > get build failures you can try refreshing any snapshot dependencys > with the "-U" parameter, eg: > > mvn clean install -U > > By default the Maven local repository is in your home directory, you > can change this so the build uses use a different local repository > with the parameter "-Dmaven.repo.local=", eg: > > mvn clean install -Dmaven.repo.local=\Synapse\MyRepo > > Eclipse Projects > > You can create Eclipse project definitions for Synapse (that can be > imported directly into Eclipse). At the top level Synapse folder run: > > mvn eclipse:eclipse > > Now within eclipse you can import those Synapse projects into an > Eclipse workspace. From Eclipse do File -> Import, expand the > "General" toggle and choose "Existing Projects into Workspace", click > Next, click Browse and navigate to your Synapse SVN folder, click OK > and it should find the six Synapse projects, click Finish. That should > set up the projects and show them in the Package Explorer. There will > be lots of compile errors about missing classpath entries, to fix this > select Window -> Preferences, expend the Java toggle, then expand the > Build Path toggle and select Classpath Variables. Click New and use > the name "M2_REPO" and then click Folder and navigate to you local > Maven repository (eg C:/Documents and > Settings/Administrator/.m2/repository), click OK and again OK and it > should rebuild everything with all the compile errors gone. > > > > On Jan 7, 2008 9:12 AM, Laurent CHARTIER < > [EMAIL PROTECTED]> > wrote: > > Hi all, > > I'm trying to make synapse jar with Maven. > > So I downloaded sources, install them in a folder and run mvn > > compile. The module Synapse-Core doesn't compile: > > > > [INFO] > > -------------------------------------------------------------------- > > -- > > -- > > [INFO] Building Apache Synapse - Core > > [INFO] task-segment: [compile] > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] [resources:resources] > > [INFO] Using default encoding to copy filtered resources. > > [INFO] [compiler:compile] > > Compiling 94 source files to > > D:\Interops-WKSPC\Interops\Apache-Synapse\modules\core\target\classes > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Compilation failure > > > > D:\Interops-WKSPC\Interops\Apache-Synapse\modules\core\src\main\java > > \o > > rg\apa > > che\synapse\mediators\builtin\CacheMediator.java:[151,25] > > setResponseEnvelope(byte[]) in org.wso2.caching.CachedObject cannot be > > applied to (org.apache.axiom.soap.SOAPEnvelope) > > > > D:\Interops-WKSPC\Interops\Apache-Synapse\modules\core\src\main\java > > \o > > rg\apa > > che\synapse\mediators\builtin\CacheMediator.java:[212,26] > > setEnvelope(org.apache.axiom.soap.SOAPEnvelope) in > > org.apache.synapse.MessageContext cannot be applied to (byte[]) > > > > D:\Interops-WKSPC\Interops\Apache-Synapse\modules\core\src\main\java > > \o > > rg\apa > > che\synapse\mediators\builtin\CacheMediator.java:[283,17] > > setRequestEnvelope(byte[]) in org.wso2.caching.CachedObject cannot be > > applied to (org.apache.axiom.soap.SOAPEnvelope) > > > > D:\Interops-WKSPC\Interops\Apache-Synapse\modules\core\src\main\java > > \o > > rg\apa > > che\synapse\mediators\builtin\CacheMediator.java:[284,17] > > setRequestHash(java.lang.String) in org.wso2.caching.CachedObject cannot > be > > applied to (java.lang.Object) > > > > [INFO] > > -------------------------------------------------------------------- > > -- > > -- > > [INFO] For more information, run Maven with the -e switch > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 8 seconds > > [INFO] Finished at: Mon Jan 07 10:10:15 CET 2008 > > [INFO] Final Memory: 10M/29M > > [INFO] > > ------------------------------------------------------------------------ > > > > Can someone help me? > > > > Thank you. > > > > > > > > Ce message est protégé par les règles relatives au secret des > > correspondances. Il est donc établi à destination exclusive de son > > destinataire. Celui-ci peut donc contenir des informations > > confidentielles. La divulgation de ces informations est à ce titre > > rigoureusement interdite. Si vous avez reçu ce message par erreur, > > merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure > > ci-dessus et de détruire le message ainsi que toute pièce jointe. > > > > This message is protected by the secrecy of correspondence rules. > > Therefore, this message is intended solely for the attention of the > > addressee. This message may contain privileged or confidential > > information, as such the disclosure of these informations is > > strictly forbidden. If, by mistake, you have received this message, > > please return this message to the addressser whose e-mail address is > > written above and destroy this message and all files attached. > > > > > > > > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > Ce message est protégé par les règles relatives au secret des > correspondances. Il est donc établi à destination exclusive de son > destinataire. Celui-ci peut donc contenir des informations > confidentielles. La divulgation de ces informations est à ce titre > rigoureusement interdite. Si vous avez reçu ce message par erreur, > merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure > ci-dessus et de détruire le message ainsi que toute pièce jointe. > > This message is protected by the secrecy of correspondence rules. > Therefore, this message is intended solely for the attention of the > addressee. This message may contain privileged or confidential > information, as such the disclosure of these informations is strictly > forbidden. If, by mistake, you have received this message, please > return this message to the addressser whose e-mail address is written > above and destroy this message and all files attached. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform" Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe. This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
