Argh... I can't believe I got disillusioned.  I have to take back what I said in my last few mails.

I have verified that the latest version of the jar is selected when no version is mentioned in the dependency both in G 2.0 and WAS-CE 1.1.0.2.  I have tested it with a web app and a lib jar.  The application will not pickup the new jar unless it is stopped and started.  Redeployment is not necessary.  If you have a specific test case to recreate the problem, please post it.

Thanks and best regards,
Vamsi

On 8/7/07, Vamsavardhana Reddy <c1vamsi1c@gmail.com> wrote:
You can still go ahead and create a JIRA.  Further investigation showed that this problem is applicable to only library dependencies but not configuration depedencies.


Vamsi

On 8/7/07, Xh <xhsaymyname@yahoo.co.uk> wrote:
Hi!

I'm using IBM WAS-CE based on Apache Geronimo 1.1

If You think I should still create a JIRA tell me

best regards
Lukasz


----- Original Message ----
From: Vamsavardhana Reddy <c1vamsi1c@gmail.com>
To: user@geronimo.apache.org
Sent: Tuesday, 7 August, 2007 3:40:08 PM
Subject: Re: the newest available dependencies - <dependency><version> question

Oops... that bombs.  If I have 1.2 and 1.15, 1.15 gets selected.  Can you create a JIRA.  https://issues.apache.org/jira/browse/GERONIMO

Thanks and regards,
Vamsi

On 8/7/07, Vamsavardhana Reddy < c1vamsi1c@gmail.com> wrote:
Which version of Geronimo are you using?  Can you post a testcase?  With Geronimo 2.0, I am noticing that if I don't specify the version in dependency, it is selecting the latest version from repository.  I have used versions 1.0 and 1.1 in my verification.

Thanks and regards,
Vamsi


On 8/7/07, Xh < xhsaymyname@yahoo.co.uk > wrote:
Hi All!

I was wondering if there is a way I can point to Apache Geronimo that I want the newest version of given dependency?

I have few versions of my "commons" libraries and I thought it would be very nice feature if I wouldn't have to change my <dependency><version> and redeploy whole application each time I change something in my commons libraries.

I've deployed successfully my app with:

<dependency>
                <groupId>dataweaver</groupId>
                <artifactId>dataweaver-commons</artifactId>
                <type>jar</type>
</dependency>

(so I guess that <version> element is not required)

added new method (getVersion) to the one of my classes.

when running the result:

java.lang.NoSuchMethodError: org.xh.dataweaver.common.utils.StringUtils.getVersion()

when I add the <version> element:

<dependency>
                <groupId>dataweaver</groupId>
                <artifactId>dataweaver-commons</artifactId>
                <version>1.15</version>
                <type>jar</type>
</dependency>

StringUtils.getVersion () works fine.

So, is there any way I can point to AG that I want the newest available dependencies?

thanks and regards
Lukasz


Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today.





Yahoo! Answers - Get better answers from someone who knows. Try it now.