m2eclipse 0.9.3 released

[Eugene Kuleshov]

  We glad to announce 0.9.3 release. You can see list of resolved issues
in the project issue tracking system http://tinyurl.com/6h4mzt

  The most notable new feature is cofiguration for Maven Archetype
catalogs that allow to configure custom catalogs or contribute then
using new extension point.

  Please also note that Maven launch configurations had been moved from
"External Tools" into "Run/Debug" category. Because of this change, you
may have to delete old Maven launch configurations from "External Tools"
dialog and recreate them in "Run" dialog. Sorry for the inconvenience,
but now you can explicitly select if you want to run Maven under
debugger by calling "Debug As... / Maven..." from the project popup
menu, or by creating Maven launch configuration from "Debug" drop down
on the main toolbar.

  See more details for this and previous releases on the New and
Noteworthy page at
http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy

  You can install new version from the project update site at
http://m2eclipse.sonatype.org/update/

  As before, we would like to thank everyone who tested previous
versions, submitted ideas, bug reports, test projects and patches.

  m2eclipse team



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

  m2eclipse team would like your feedback and help us test new project
configuration framework [1] implemented for version 0.9.4. Also, if you
are working on your own tools based on Eclipse, we would like to hear
from you if configuration framework is sufficient for integrating your
tools.

  If you are using m2eclipse with WTP and/or AJDT, please install this
stable development build from the dev update site [2], try it with your
projects and give us your feedback. See mini howto for WTP integration
on the wiki [3].

  In addition to project configuration we added shortcuts for opening
project page, issue tracker, source control and ci systems based on
information from pom.xml and also packaged "Maven: The Definitive Guide"
book as an Eclipse help. More details for new features added in this and
previous releases available on the New and Noteworthy page at
http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy

  Known issues in this dev build:
  - web modules configuration is not always immediately reflect
dependency changes, so you may have to call "Update Project
Configuration" action from Maven popup menu (note that this action
replaces old "Update Source Folders" action)
  - support for ear, rar and other j2ee module types is not implemented
yet. Please let us know if you are interested working on this

  As before, we would like to thank everyone who tested previous
versions, submitted ideas, bug reports, test projects and patches.

  m2eclipse team

[1]
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configuration+framework
[2] http://m2eclipse.sonatype.org/update-dev/
[3] http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[matthew.lieder]

Thanks! For those who haven't figured it out yet, this new build can be
found at http://m2eclipse.sonatype.org/update-dev/ (doesn't seem to be
linked to from anywhere ATM)

I've actually already found one potential bug, though it's definitely an
edge case: http://jira.codehaus.org/browse/MNGECLIPSE-597 (Workspace
resolution fails if dependency project has Dynamic Web Project facet).

-Matthew

-----Original Message-----
From: Eugene Kuleshov [mailto:eu@...]
Sent: Monday, May 12, 2008 1:56 PM
To: user@...
Cc: dev@...
Subject: [m2eclipse-user] m2eclipse 0.9.4 dev build


  m2eclipse team would like your feedback and help us test new project
configuration framework [1] implemented for version 0.9.4. Also, if you
are working on your own tools based on Eclipse, we would like to hear
from you if configuration framework is sufficient for integrating your
tools.

  If you are using m2eclipse with WTP and/or AJDT, please install this
stable development build from the dev update site [2], try it with your
projects and give us your feedback. See mini howto for WTP integration
on the wiki [3].

  In addition to project configuration we added shortcuts for opening
project page, issue tracker, source control and ci systems based on
information from pom.xml and also packaged "Maven: The Definitive Guide"

book as an Eclipse help. More details for new features added in this and

previous releases available on the New and Noteworthy page at
http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy

  Known issues in this dev build:
  - web modules configuration is not always immediately reflect
dependency changes, so you may have to call "Update Project
Configuration" action from Maven popup menu (note that this action
replaces old "Update Source Folders" action)
  - support for ear, rar and other j2ee module types is not implemented
yet. Please let us know if you are interested working on this

  As before, we would like to thank everyone who tested previous
versions, submitted ideas, bug reports, test projects and patches.

  m2eclipse team

[1]
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configurat
ion+framework
[2] http://m2eclipse.sonatype.org/update-dev/
[3] http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

Thanks Matthew,

  Can you please attach test projects that would allow us to reproduce
and debug your JIRA issue, also please specify Eclipse and WTP versions
you are using or version of J2EE package from EPP.

  We have added link to the dev update site to project web sites at
http://m2eclipse.sonatype.org/ and http://m2eclipse.codehaus.org/

  regards,
  Eugene


matthew.lieder@... wrote:

> Thanks! For those who haven't figured it out yet, this new build can be
> found at http://m2eclipse.sonatype.org/update-dev/ (doesn't seem to be
> linked to from anywhere ATM)
>
> I've actually already found one potential bug, though it's definitely an
> edge case: http://jira.codehaus.org/browse/MNGECLIPSE-597 (Workspace
> resolution fails if dependency project has Dynamic Web Project facet).
>
> -Matthew
>  

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[matthew.lieder]

Done.

-----Original Message-----
From: Eugene Kuleshov [mailto:eu@...]
Sent: Monday, May 12, 2008 2:55 PM
To: user@...
Subject: Re: [m2eclipse-user] m2eclipse 0.9.4 dev build (dynamic web
project)

Thanks Matthew,

  Can you please attach test projects that would allow us to reproduce
and debug your JIRA issue, also please specify Eclipse and WTP versions
you are using or version of J2EE package from EPP.

  We have added link to the dev update site to project web sites at
http://m2eclipse.sonatype.org/ and http://m2eclipse.codehaus.org/

  regards,
  Eugene


matthew.lieder@... wrote:
> Thanks! For those who haven't figured it out yet, this new build can
be
> found at http://m2eclipse.sonatype.org/update-dev/ (doesn't seem to be
> linked to from anywhere ATM)
>
> I've actually already found one potential bug, though it's definitely
an
> edge case: http://jira.codehaus.org/browse/MNGECLIPSE-597 (Workspace
> resolution fails if dependency project has Dynamic Web Project facet).
>
> -Matthew
>  


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Langs Gerhard]

Hello Eugene

Tried 0.9.4 on one of our WTP Projects, and it seems to work.
One trap I ran into in my first attempt, was that I forgot to install the "Maven Project Configurators->..WTP" extension in the Eclipse Update Manager.

When you are in that trap, many things seem to work, but the system then installs "provided" Artefacts, which then leads to ugly ClassLoading Problems during startup of Web-apps. Maybe some warning/error during "Update Configuration" could prevent that trap....


Another thing I saw, and I'm not yet sure if it's a problem for us:
In our WTP Project, we use Seam 2.0, and it requires JRE 5. Up to now, we used JRE 6 and had no problem with it, however during "Update Project Configuration", this seems to be checked now, and I get an error dialog, telling me to use JRE 5 for Seam.  Such a verfication I've not seen on 0.9.3.
.. As I said, I'm not *yet* sure if it hurts, or what we can do on it.

Btw, thanx for the new navigation options in the Popupmenu of Artefacts (Home page, Jira etc).


Gerhard.






-----Ursprüngliche Nachricht-----
Von: Eugene Kuleshov [mailto:eu@...]
Gesendet: Montag, 12. Mai 2008 20:56
An: user@...
Cc: dev@...
Betreff: [m2eclipse-user] m2eclipse 0.9.4 dev build


  m2eclipse team would like your feedback and help us test new project configuration framework [1] implemented for version 0.9.4. Also, if you are working on your own tools based on Eclipse, we would like to hear from you if configuration framework is sufficient for integrating your tools.

  If you are using m2eclipse with WTP and/or AJDT, please install this stable development build from the dev update site [2], try it with your projects and give us your feedback. See mini howto for WTP integration on the wiki [3].

  In addition to project configuration we added shortcuts for opening project page, issue tracker, source control and ci systems based on information from pom.xml and also packaged "Maven: The Definitive Guide"
book as an Eclipse help. More details for new features added in this and previous releases available on the New and Noteworthy page at http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy

  Known issues in this dev build:
  - web modules configuration is not always immediately reflect dependency changes, so you may have to call "Update Project Configuration" action from Maven popup menu (note that this action replaces old "Update Source Folders" action)
  - support for ear, rar and other j2ee module types is not implemented yet. Please let us know if you are interested working on this

  As before, we would like to thank everyone who tested previous versions, submitted ideas, bug reports, test projects and patches.

  m2eclipse team

[1]
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configuration+framework
[2] http://m2eclipse.sonatype.org/update-dev/
[3] http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

Langs Gerhard wrote:
> Tried 0.9.4 on one of our WTP Projects, and it seems to work.
> One trap I ran into in my first attempt, was that I forgot to install the "Maven Project Configurators->..WTP" extension in the Eclipse Update Manager.
>
> When you are in that trap, many things seem to work, but the system then installs "provided" Artefacts, which then leads to ugly ClassLoading Problems during startup of Web-apps. Maybe some warning/error during "Update Configuration" could prevent that trap....
>  
  There isn't really any warning we can put there because this feature
provides the actual configuration. From the technical point of view it
is ok to not have it installed and m2eclipse core don't know anything
about WTP.
> Another thing I saw, and I'm not yet sure if it's a problem for us:
> In our WTP Project, we use Seam 2.0, and it requires JRE 5. Up to now, we used JRE 6 and had no problem with it, however during "Update Project Configuration", this seems to be checked now, and I get an error dialog, telling me to use JRE 5 for Seam.  Such a verfication I've not seen on 0.9.3.
> .. As I said, I'm not *yet* sure if it hurts, or what we can do on it.
>  
  I don't recall any dialogs about "JRE 5 for Seam" in our code, but it
is possible, that our configuration triggers some validation in WTP
facets that gives that error. If it bothers you, please open a JIRA
issue and attach test seam project along with info about your Eclipse
from Help / About Eclipse SDK / Configuration Details and any additional
instructions that we would need to reproduce this.

  Thanks

  Eugene



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[sebdotv]

Hi,

I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
integration. Good job!

Aspect Path is correctly configured as jar files for projects not
present in the workspace, but if projects are present in the workspace
(and workspace resolution is active), then M2Eclipse seems to skip
those projects from the aspect path. I'll try to create a minimal set
of test projects to show this issue.

Cheers,

Sebastien

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Igor Fedorenko-4]

Sebastien,

This seems to be AJDT limitation -- it does not allow workspace project
references in inpath/aspectpath. Do you know how to set it up manually?

I tried to get clarification on AJDT developers but no reply yet as of
yet. Maybe I should try dev mailing list instead of the newsgroup...

sebdotv wrote:

> Hi,
>
> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
> integration. Good job!
>
> Aspect Path is correctly configured as jar files for projects not
> present in the workspace, but if projects are present in the workspace
> (and workspace resolution is active), then M2Eclipse seems to skip
> those projects from the aspect path. I'll try to create a minimal set
> of test projects to show this issue.
>
> Cheers,
>
> Sebastien
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[sebdotv]

Before m2eclipse introduced this feature, I used to manually add the
output folders of those projects to the aspect path.

On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...> wrote:

> Sebastien,
>
> This seems to be AJDT limitation -- it does not allow workspace project
> references in inpath/aspectpath. Do you know how to set it up manually?
>
> I tried to get clarification on AJDT developers but no reply yet as of yet.
> Maybe I should try dev mailing list instead of the newsgroup...
>
> sebdotv wrote:
>>
>> Hi,
>>
>> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
>> integration. Good job!
>>
>> Aspect Path is correctly configured as jar files for projects not
>> present in the workspace, but if projects are present in the workspace
>> (and workspace resolution is active), then M2Eclipse seems to skip
>> those projects from the aspect path. I'll try to create a minimal set
>> of test projects to show this issue.
>>
>> Cheers,
>>
>> Sebastien
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[bouiaw]

WTP integration works for me except for one thing : my war overlay dependency is not taken in account. Is it a known limitation ?

On Wed, May 14, 2008 at 4:30 PM, sebdotv <sebdotv@...> wrote:

Before m2eclipse introduced this feature, I used to manually add the
output folders of those projects to the aspect path.

On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...> wrote:
> Sebastien,
>
> This seems to be AJDT limitation -- it does not allow workspace project
> references in inpath/aspectpath. Do you know how to set it up manually?
>
> I tried to get clarification on AJDT developers but no reply yet as of yet.
> Maybe I should try dev mailing list instead of the newsgroup...
>
> sebdotv wrote:
>>
>> Hi,
>>
>> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
>> integration. Good job!
>>
>> Aspect Path is correctly configured as jar files for projects not
>> present in the workspace, but if projects are present in the workspace
>> (and workspace resolution is active), then M2Eclipse seems to skip
>> those projects from the aspect path. I'll try to create a minimal set
>> of test projects to show this issue.
>>
>> Cheers,
>>
>> Sebastien
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Igor Fedorenko-4]

Overlays are not supported at the moment. Can you open enhancement
request in JIRA http://jira.codehaus.org/browse/MNGECLIPSE? Sample
project would be very helpful to scope this work properly.

Bouiaw wrote:

> WTP integration works for me except for one thing : my war overlay
> dependency is not taken in account. Is it a known limitation ?
>
> On Wed, May 14, 2008 at 4:30 PM, sebdotv <sebdotv@...
> <mailto:sebdotv@...>> wrote:
>
>     Before m2eclipse introduced this feature, I used to manually add the
>     output folders of those projects to the aspect path.
>
>     On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...
>     <mailto:igor@...>> wrote:
>      > Sebastien,
>      >
>      > This seems to be AJDT limitation -- it does not allow workspace
>     project
>      > references in inpath/aspectpath. Do you know how to set it up
>     manually?
>      >
>      > I tried to get clarification on AJDT developers but no reply yet
>     as of yet.
>      > Maybe I should try dev mailing list instead of the newsgroup...
>      >
>      > sebdotv wrote:
>      >>
>      >> Hi,
>      >>
>      >> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
>      >> integration. Good job!
>      >>
>      >> Aspect Path is correctly configured as jar files for projects not
>      >> present in the workspace, but if projects are present in the
>     workspace
>      >> (and workspace resolution is active), then M2Eclipse seems to skip
>      >> those projects from the aspect path. I'll try to create a
>     minimal set
>      >> of test projects to show this issue.
>      >>
>      >> Cheers,
>      >>
>      >> Sebastien
>      >>
>      >>
>     ---------------------------------------------------------------------
>      >> To unsubscribe from this list, please visit:
>      >>
>      >>    http://xircles.codehaus.org/manage_email
>      >>
>      >>
>      >
>      >
>      > ---------------------------------------------------------------------
>      > To unsubscribe from this list, please visit:
>      >
>      >   http://xircles.codehaus.org/manage_email
>      >
>      >
>      >
>
>     ---------------------------------------------------------------------
>     To unsubscribe from this list, please visit:
>
>        http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Igor Fedorenko-4]

Can you please open an enhancement request for m2e to do this?

sebdotv wrote:

> Before m2eclipse introduced this feature, I used to manually add the
> output folders of those projects to the aspect path.
>
> On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...> wrote:
>> Sebastien,
>>
>> This seems to be AJDT limitation -- it does not allow workspace project
>> references in inpath/aspectpath. Do you know how to set it up manually?
>>
>> I tried to get clarification on AJDT developers but no reply yet as of yet.
>> Maybe I should try dev mailing list instead of the newsgroup...
>>
>> sebdotv wrote:
>>> Hi,
>>>
>>> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
>>> integration. Good job!
>>>
>>> Aspect Path is correctly configured as jar files for projects not
>>> present in the workspace, but if projects are present in the workspace
>>> (and workspace resolution is active), then M2Eclipse seems to skip
>>> those projects from the aspect path. I'll try to create a minimal set
>>> of test projects to show this issue.
>>>
>>> Cheers,
>>>
>>> Sebastien
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[bouiaw]

Done : http://jira.codehaus.org/browse/MNGECLIPSE-599

On Wed, May 14, 2008 at 7:12 PM, Igor Fedorenko <igor@...> wrote:

Overlays are not supported at the moment. Can you open enhancement request in JIRA http://jira.codehaus.org/browse/MNGECLIPSE? Sample project would be very helpful to scope this work properly.

Bouiaw wrote:

WTP integration works for me except for one thing : my war overlay dependency is not taken in account. Is it a known limitation ?

On Wed, May 14, 2008 at 4:30 PM, sebdotv <sebdotv@... <mailto:sebdotv@...>> wrote:

   Before m2eclipse introduced this feature, I used to manually add the
   output folders of those projects to the aspect path.

   On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...

   <mailto:igor@...>> wrote:
    > Sebastien,
    >
    > This seems to be AJDT limitation -- it does not allow workspace
   project
    > references in inpath/aspectpath. Do you know how to set it up
   manually?
    >
    > I tried to get clarification on AJDT developers but no reply yet
   as of yet.
    > Maybe I should try dev mailing list instead of the newsgroup...
    >
    > sebdotv wrote:
    >>
    >> Hi,
    >>
    >> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
    >> integration. Good job!
    >>
    >> Aspect Path is correctly configured as jar files for projects not
    >> present in the workspace, but if projects are present in the
   workspace
    >> (and workspace resolution is active), then M2Eclipse seems to skip
    >> those projects from the aspect path. I'll try to create a
   minimal set
    >> of test projects to show this issue.
    >>
    >> Cheers,
    >>
    >> Sebastien
    >>
    >>
   ---------------------------------------------------------------------
    >> To unsubscribe from this list, please visit:
    >>
    >>    http://xircles.codehaus.org/manage_email
    >>
    >>
    >
    >
    > ---------------------------------------------------------------------
    > To unsubscribe from this list, please visit:
    >
    >   http://xircles.codehaus.org/manage_email
    >
    >
    >

   ---------------------------------------------------------------------
   To unsubscribe from this list, please visit:

      http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email

[sebdotv]

Sure, done: http://jira.codehaus.org/browse/MNGECLIPSE-601

On Wed, May 14, 2008 at 7:24 PM, Igor Fedorenko <igor@...> wrote:

> Can you please open an enhancement request for m2e to do this?
>
> sebdotv wrote:
>>
>> Before m2eclipse introduced this feature, I used to manually add the
>> output folders of those projects to the aspect path.
>>
>> On Wed, May 14, 2008 at 4:16 PM, Igor Fedorenko <igor@...>
>> wrote:
>>>
>>> Sebastien,
>>>
>>> This seems to be AJDT limitation -- it does not allow workspace project
>>> references in inpath/aspectpath. Do you know how to set it up manually?
>>>
>>> I tried to get clarification on AJDT developers but no reply yet as of
>>> yet.
>>> Maybe I should try dev mailing list instead of the newsgroup...
>>>
>>> sebdotv wrote:
>>>>
>>>> Hi,
>>>>
>>>> I tried 0.9.4 dev and I must say I'm very impressed by the AJDT
>>>> integration. Good job!
>>>>
>>>> Aspect Path is correctly configured as jar files for projects not
>>>> present in the workspace, but if projects are present in the workspace
>>>> (and workspace resolution is active), then M2Eclipse seems to skip
>>>> those projects from the aspect path. I'll try to create a minimal set
>>>> of test projects to show this issue.
>>>>
>>>> Cheers,
>>>>
>>>> Sebastien
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>   http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>  http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email