Op 14-01-13 18:27, André Fróes schreef:
I'm trying by maven, but still can't do it

<modelVersion>4.0.0</modelVersion>
    <artifactId>ai</artifactId>
    <name>Proj</name>
    <packaging>jar</packaging>

<parent>
<groupId>my.new.project</groupId>
<artifactId>parent-pom</artifactId>
<version>1.0.0</version>
</parent>
<properties>
<org.drools.version>5.5.0.Final</org.drools.version>
<org.codehaus.janino.version>2.5.16</org.codehaus.janino.version>
</properties>

    <!-- Dependencies -->
    <dependencies>

        <!-- Projects -->
        <dependency>
            <groupId>my.new.project</groupId>
            <artifactId>commons</artifactId>
            <version>1.0.0</version>
        </dependency>

        <!-- API -->
        <dependency>
            <groupId>org.drools</groupId>
            <artifactId>drools-core</artifactId>
            <version>${org.drools.version}</version>
            <scope>provided</scope>
Why go scope provided?
        </dependency>
        <dependency>
            <groupId>org.drools</groupId>
            <artifactId>drools-compiler</artifactId>
            <version>${org.drools.version}</version>
            <scope>provided</scope>
Why go scope provided?
        </dependency>
        <dependency>
            <groupId>org.codehaus.janino</groupId>
            <artifactId>janino</artifactId>
By default drools-compiler transitively depends on a java compiler (I forgot if it's janino or eclipse jdt),
so you don't need to specify that dependency.
If you want to use the other one, you might want to exclude the default.
Either way, you might want to try first with the default one, by not declaring any janino/jdt dependency and let maven drag in the transitive dependency automatically.
            <version>${org.codehaus.janino.version}</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

is this right?


2013/1/14 Geoffrey De Smet <ge0ffrey.spam@gmail.com>
If you're using maven/gradle/ivy/buildr, just update the version and let
it figure out the transitive dependencies.
Although you might want to use the enforcer plugin to check if you
haven't overwritten any transitive dependency to a lower version:
http://maven.apache.org/enforcer/enforcer-rules/requireUpperBoundDeps.html

If you're using ant, basically replace all of them with those from the
5.5 lib zip.
If you want to get rid of dead deps, compare the 5.4 lib zip with the
5.5 lib zip afterwards (= painful).
If you just want the subset of deps that you need (like with maven, for
example if you only use drools-core, you don't need most of the deps in
the lib zip), don't use ant.

Op 14-01-13 12:44, Andre Froes schreef:
> Hello everyone,
>
> in order to update from drools 5.4 to 5.5 which lib should I update? Or must
> I replace them all?
>
> Thanks
>
>
>
> --
> View this message in context: http://drools.46999.n3.nabble.com/Which-libs-should-I-update-after-update-tp4021500.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users