2.1 released

[Hiram Chirino]

FYI:

I just cut a 2.1 release of the xbean modules.  The only one that did  
not make it is the jmx module since it had a SNAPSHOT dependency and  
the m2 release plugin does not allow doing a release of a module with  
a SNAPSHOT dependency.

Regards,
Hiram

[Jason van Zyl-2]

Hiram Chirino wrote:
> FYI:
>
> I just cut a 2.1 release of the xbean modules.  The only one that did
> not make it is the jmx module since it had a SNAPSHOT dependency and the
> m2 release plugin does not allow doing a release of a module with a
> SNAPSHOT dependency.

Right, it won't let you because that makes a release unstable. Was it a
dependency that you couldn't use a release version of?

> Regards,
> Hiram
>
>


--

jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

   -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks

[Alan.Cabrera]

Probably a SNAPSHOT of LiveTribe.  I can fix that.


Regards,
Alan
-----Original Message-----
From: Jason van Zyl <jason@...>
Date: Wed, 04 Jan 2006 12:15:37
To:dev@...
Subject: Re: [xbean-dev] 2.1 released

Hiram Chirino wrote:
> FYI:
>
> I just cut a 2.1 release of the xbean modules.  The only one that did
> not make it is the jmx module since it had a SNAPSHOT dependency and the
> m2 release plugin does not allow doing a release of a module with a
> SNAPSHOT dependency.

Right, it won't let you because that makes a release unstable. Was it a
dependency that you couldn't use a release version of?

> Regards,
> Hiram
>
>


--

jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

   -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks

Sent from my Verizon Wireless BlackBerry

[Hiram Chirino]

I just did not have time to figure it out.  If figure once the jmx  
module moves off a SNAPSHOT, then we can release it.

BTW: it would be nice if the release plugin basically lets you do  
what I did manually (exclude a sub module from the release process  
due to SNAPSHOT dependencies)

Regards,
Hiram


On Jan 4, 2006, at 12:15 PM, Jason van Zyl wrote:

> Hiram Chirino wrote:
>> FYI:
>> I just cut a 2.1 release of the xbean modules.  The only one that  
>> did not make it is the jmx module since it had a SNAPSHOT  
>> dependency and the m2 release plugin does not allow doing a  
>> release of a module with a SNAPSHOT dependency.
>
> Right, it won't let you because that makes a release unstable. Was  
> it a dependency that you couldn't use a release version of?
>
>> Regards,
>> Hiram
>
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more  
> examples
> you look at, the more general your framework will be.
>
>   -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks