You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Greg Luck (JIRA)" <ji...@codehaus.org> on 2007/03/06 04:24:00 UTC
[jira] Created: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks for
Ant and Maven 2.0.5 Embedder for everything to remain sane
Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
--------------------------------------------------------------------------------------------------
Key: MNG-2859
URL: http://jira.codehaus.org/browse/MNG-2859
Project: Maven 2
Issue Type: Bug
Components: Ant tasks, Embedding
Affects Versions: 2.0.5
Reporter: Greg Luck
I am moving my project from Maven plus Antlib to pure Maven, maybe.
Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
Re: Ant Maven Tasks
Jason van Zyl
Wed, 21 Feb 2007 06:40:26 -0800
On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
Hi,
I couldn't find any info regarding the status of the ant maven tasks
wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
Jason.
Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MANTTASKS-62) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-2859 to MANTTASKS-62:
--------------------------------------------
Affects Version/s: (was: 2.0.5)
Component/s: (was: Embedding)
(was: Ant tasks)
Complexity: (was: Intermediate)
Key: MANTTASKS-62 (was: MNG-2859)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MANTTASKS-62
> URL: http://jira.codehaus.org/browse/MANTTASKS-62
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Reporter: Greg Luck
> Assignee: Jason van Zyl
> Fix For: 2.0.6
>
> Attachments: maven-ant-tasks.patch, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar
>
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Ben Speakmon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89873 ]
Ben Speakmon commented on MNG-2859:
-----------------------------------
My company is preparing a release, and our build system is already 2.0.5. Some bits of it are older and still use ant and getting rid of them isn't an option. Is this a priority for anyone right now?
If not, well, I'm going to have to get the ant tasks working with 2.0.5 for our builds anyway, probably sooner rather than later. My company is willing to let me contribute my fixes upstream as well, assuming the time investment isn't too large. Can someone point me in the right direction?
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2859
> URL: http://jira.codehaus.org/browse/MNG-2859
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Embedding
> Affects Versions: 2.0.5
> Reporter: Greg Luck
> Assigned To: Jason van Zyl
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MANTTASKS-62) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MANTTASKS-62:
----------------------------------
Fix Version/s: 2.0.6
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MANTTASKS-62
> URL: http://jira.codehaus.org/browse/MANTTASKS-62
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Reporter: Greg Luck
> Assignee: Jason van Zyl
> Fix For: 2.0.6
>
> Attachments: maven-ant-tasks.patch, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar
>
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks for
Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2859.
------------------------------
Resolution: Fixed
Patch applied and this will go out with 2.0.6.
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2859
> URL: http://jira.codehaus.org/browse/MNG-2859
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Embedding
> Affects Versions: 2.0.5
> Reporter: Greg Luck
> Assigned To: Jason van Zyl
> Attachments: maven-ant-tasks.patch, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar
>
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Ben Speakmon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89874 ]
Ben Speakmon commented on MNG-2859:
-----------------------------------
Took a whirl at this, and after running mvn assembly:assembly in the maven-artifact-ant directory, I got my jar. Seems to work fine.
Are there any code changes required for this, or is it just a question of someone finding the time to run the release?
For us devs, I just wanted to point out that building it yourself is trivial.
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2859
> URL: http://jira.codehaus.org/browse/MNG-2859
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Embedding
> Affects Versions: 2.0.5
> Reporter: Greg Luck
> Assigned To: Jason van Zyl
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91052 ]
Jason van Zyl commented on MNG-2859:
------------------------------------
I have updated the tasks to match what is in 2.0.6. Created an uber jar and deployed here:
http://idisk.maven.org/jvanzyl/Public/maven/
Give them a whirl, they appear to be working.
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2859
> URL: http://jira.codehaus.org/browse/MNG-2859
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Embedding
> Affects Versions: 2.0.5
> Reporter: Greg Luck
> Assigned To: Jason van Zyl
> Attachments: maven-ant-tasks.patch, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar
>
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2859) Maven 2.0.5 needs Maven 2.0.5 Tasks
for Ant and Maven 2.0.5 Embedder for everything to remain sane
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90957 ]
Jason van Zyl commented on MNG-2859:
------------------------------------
These don't live in maven-artifact-ant anymore. I would love some help cleaning them up. But they are here now:
http://svn.apache.org/repos/asf/maven/ant-tasks/trunk/
> Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2859
> URL: http://jira.codehaus.org/browse/MNG-2859
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Embedding
> Affects Versions: 2.0.5
> Reporter: Greg Luck
> Assigned To: Jason van Zyl
> Attachments: maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar
>
>
> I am moving my project from Maven plus Antlib to pure Maven, maybe.
> Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.
> Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.
> But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.
> I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.
> The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.
> Re: Ant Maven Tasks
> Jason van Zyl
> Wed, 21 Feb 2007 06:40:26 -0800
> On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:
> Hi,
> I couldn't find any info regarding the status of the ant maven tasks
> wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
> As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.
> Jason.
> Cheers, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira