You should be able to upgrade any AppFuse dependencies w/o issues.
Downgrading them might be a different story. The best thing to do is
try upgrading and report back if you see any issues.

Matt

On Tue, Sep 29, 2009 at 3:26 PM, jackalista <j...@twaxx.com> wrote:
>
> Hi kids,
>
> I'm starting to integrate mule into appfuse and was wondering if anyone has
> any experience with this?  My first question concerns dependencies and maven
> (and yes, I did read the maven for newbies page -- Nathan, public
> humiliation is the best perk of all -- no treading on thin ice == no cold
> water wake up, right?).
>
> First thing I noticed a couple of differences between the versions of things
> mule likes and those appfuse likes.  Here's the stuff I found:
>
> stuff                           mule version      appfuse version
> -----------------------------------------------
> jetty                           6.1.11              6.1.9
> servlet-api                    2.5 (?)*             2.4
> xalan                          2.7.1                 ??? - I'd thought xalan
> was in appfuse but I don't see a jar...?
> maven-compiler-plugin   ? v listed**       2.0.2 -
> cxf                             2.1.2                2.2.3 - ?!?!?  prolly
> mule lore but anyone know about this?
>
>
> I'm going to take the tack of using the latest version either dist wants and
> hope for the best but if anybody has details on these I'd like to hear about
> it if you can spit it out... Also, do I care about things like this:
> "<encoding>ISO-8859-1</encoding>" in one maven compiler plugin and not the
> other?   Also, is there any reason appfuse shouldn't upgrade to servlet api
> 2.5 (vs. 2.4 in use now)?  Also, what's the deal with xalan, wasn't it in
> appfuse or am I confused?  TIA... See notes for "*" and "**" below...
> thanks!
>
> -=j=-
>
>
> * = The servlet-api isn't called out in the mule pom.xml as it is in appfuse
> but this jetty dependecy makes it look like it's 2.5:
>
>        <dependency>
>            <groupId>org.mortbay.jetty</groupId>
>            <artifactId>servlet-api-2.5</artifactId>
>            <version>${jettyVersion}</version>
>            <scope>test</scope>
>        </dependency>
>
> ** = the mule maven-compiler-plugin lists an encoding value inside the
> <configuration> with a value of ISO-8859-1 while the appfuse plugin doesn't,
> do I care?  Here's the mule version:
>
>            <plugin>
>                <groupId>org.apache.maven.plugins</groupId>
>                <artifactId>maven-compiler-plugin</artifactId>
>                <configuration>
>                    <source>1.5</source>
>                    <target>1.5</target>
>                    <encoding>ISO-8859-1</encoding>
>                </configuration>
>            </plugin>
>
> Here's the appfuse version:
>
>            <plugin>
>                <artifactId>maven-compiler-plugin</artifactId>
>                <version>2.0.2</version>
>                <configuration>
>                    <source>1.5</source>
>                    <target>1.5</target>
>                </configuration>
>            </plugin>
>
>
> --
> View this message in context: 
> http://www.nabble.com/integrating-enterprise-mule---appfuse-2.02-tp25672004s2369p25672004.html
> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
> For additional commands, e-mail: users-h...@appfuse.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net

Reply via email to