unsuscribe

[Tobias Marx <to...@fivecast.com>]

-----Ursprüngliche Nachricht-----
Von: Andrus Adamchik [mailto:andrus@objectstyle.org] 
Gesendet: Dienstag, 31. Juli 2007 11:10
An: user@cayenne.apache.org
Betreff: Re: MVN again - now on Dataviews :( !

All code dependencies do have explicit versions in the parent pom  
(and maven actually requires version to be present). But Maven  
plugins are considered different beasts and versions are not  
required. If omitted, Maven will fetch the latest version. This  
caused us grief in the past already, so explicitly setting plugin  
versions as well is a good idea.

Andrus


On Jul 31, 2007, at 11:59 AM, Ahmed Mohombe wrote:

>> I hardcoded version of japplication plugin to 2.0.5 - this is the  
>> last version that I personally tested. Try it now.
> Thank you. Now it works :).
>
> If the trick of hardcoding versions does it, wouldn't it make more  
> sense to
> add version for other dependencies as well? I mean generally with  
> mvn, not just for dataviews (in order to prevent future problems -  
> since one can't always test all the latest versions of dependent  
> libs) ?
>
> Thanks in advance,
>
> Ahmed.
>
>

Re: unsuscribe

[Andrus Adamchik <an...@objectstyle.org>]

I just manually unsubscribed Tobias, but for the future reference -  
users can unsubscribe themselves without bothering the list or the  
admins. Per http://cayenne.apache.org/mailing-lists.html

"To unsubscribe send empty email to user-unsubscribe@cayenne.apache.org"

Cheers,
Andrus




On Jul 31, 2007, at 12:12 PM, Tobias Marx wrote:

>
>
> -----Ursprüngliche Nachricht-----
> Von: Andrus Adamchik [mailto:andrus@objectstyle.org]
> Gesendet: Dienstag, 31. Juli 2007 11:10
> An: user@cayenne.apache.org
> Betreff: Re: MVN again - now on Dataviews :( !
>
> All code dependencies do have explicit versions in the parent pom
> (and maven actually requires version to be present). But Maven
> plugins are considered different beasts and versions are not
> required. If omitted, Maven will fetch the latest version. This
> caused us grief in the past already, so explicitly setting plugin
> versions as well is a good idea.
>
> Andrus
>
>
> On Jul 31, 2007, at 11:59 AM, Ahmed Mohombe wrote:
>
>>> I hardcoded version of japplication plugin to 2.0.5 - this is the
>>> last version that I personally tested. Try it now.
>> Thank you. Now it works :).
>>
>> If the trick of hardcoding versions does it, wouldn't it make more
>> sense to
>> add version for other dependencies as well? I mean generally with
>> mvn, not just for dataviews (in order to prevent future problems -
>> since one can't always test all the latest versions of dependent
>> libs) ?
>>
>> Thanks in advance,
>>
>> Ahmed.
>>
>>
>
>
>
>