Re: [VOTE] Release taglist-maven-plugin 2.1

+1

2007/9/1, Dennis Lundberg <dennisl <at> apache.org>:
> Anyone?
>
> Dennis Lundberg wrote:
> > Hi
> >
> > I'd like to release taglist-maven-plugin 2.1. The last release was in
> > May 2006.
> >
> > Release notes can be found here:
> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11224&styleName=Html&version=12606
> >
> >
> > All known bugs have been fixed, but there are still a few improvement
> > requests in JIRA. 11 issues have been solved. The site is now
> > docck-compliant.
> >
> > A SNAPSHOT of the current svn code has been deployed.
> >
> > Please vote:
> >
> > [ ] +1, go ahead
> > [ ]  0, whatever
> > [ ] -1, nooooooo
> >
>
>
> --

Re: [VOTE] Release taglist-maven-plugin 2.1

Re: [VOTE] Release taglist-maven-plugin 2.1

+1 from me, obviously

Dennis Lundberg wrote:
> Hi
> 
> I'd like to release taglist-maven-plugin 2.1. The last release was in 
> May 2006.
> 
> Release notes can be found here:
>
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11224&styleName=Html&version=12606 
> 
> 
> All known bugs have been fixed, but there are still a few improvement 
> requests in JIRA. 11 issues have been solved. The site is now 
> docck-compliant.
> 
> A SNAPSHOT of the current svn code has been deployed.
> 
> Please vote:
> 
> [ ] +1, go ahead
> [ ]  0, whatever
> [ ] -1, nooooooo
> 

--

-- 
Dennis Lundberg

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

    http://xircles.codehaus.org/manage_email

[RESULT][VOTE] Release taglist-maven-plugin 2.1

Here are the results of the vote:

+1 from Arnaud Heritier, Marat Radchenko, David Vicente, Dennis Lundberg

I'll proceed with the release.

Dennis Lundberg wrote:
> Hi
> 
> I'd like to release taglist-maven-plugin 2.1. The last release was in 
> May 2006.
> 
> Release notes can be found here:
>
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11224&styleName=Html&version=12606 
> 
> 
> All known bugs have been fixed, but there are still a few improvement 
> requests in JIRA. 11 issues have been solved. The site is now 
> docck-compliant.
> 
> A SNAPSHOT of the current svn code has been deployed.
> 
> Please vote:
> 
> [ ] +1, go ahead
> [ ]  0, whatever
> [ ] -1, nooooooo
> 

--

-- 
Dennis Lundberg

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

    http://xircles.codehaus.org/manage_email

[jira] Closed: (MOJO-430) Support locating configuration in classpath

     [
http://jira.codehaus.org/browse/MOJO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed MOJO-430.
--------------------------------

      Assignee: Dennis Lundberg
    Resolution: Fixed

This functionality has been added to svn by someone. I have tried it out and it working. It is also documented.

> Support locating configuration in classpath
> -------------------------------------------
>
>                 Key: MOJO-430
>                 URL: http://jira.codehaus.org/browse/MOJO-430
>             Project: Mojo
>          Issue Type: Improvement
>          Components: jalopy
>            Reporter: Andrea Aime
>            Assignee: Dennis Lundberg
>         Attachments: jalopy-1.path, jalopy-2.patch, pom.xml
>
>
> In multi-module projects the ability to locate the configuration from the classpath is quite important.
> I believe I have added this capability with the attached patch, which is unit tested but still no
real-world tested.
> In the meantime can someone have a look at it? I tried to replicate the checkstyle behaviour, shamelessly
copying a few classes too
> since I did not want to add a dependency on checkstyle.

--

-- 
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

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

    http://xircles.codehaus.org/manage_email

[VOTE] Release jalopy-maven-plugin 1.0-alpha-1

Hi

I'd like to release jalopy-maven-plugin 1.0-alpha-1, as requested in 
MOJO-895. This will be the first ever release of this plugin.

All known bugs have been fixed, and no other issues remain in JIRA.

The site is docck-compliant and has been published. A link on the 
plugins page is still to come, but will have to wait until the release 
is done.

http://mojo.codehaus.org/jalopy-maven-plugin/

A SNAPSHOT of the current svn code has been deployed.

Please vote:

[ ] +1, go ahead
[ ]  0, whatever
[ ] -1, nooooooo

--

-- 
Dennis Lundberg

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

    http://xircles.codehaus.org/manage_email

Re: [VOTE] Release jalopy-maven-plugin 1.0-alpha-1

+1

Arnaud

On 02/09/07, Dennis Lundberg <dennisl <at> apache.org> wrote:
> Hi
>
> I'd like to release jalopy-maven-plugin 1.0-alpha-1, as requested in
> MOJO-895. This will be the first ever release of this plugin.
>
> All known bugs have been fixed, and no other issues remain in JIRA.
>
> The site is docck-compliant and has been published. A link on the
> plugins page is still to come, but will have to wait until the release
> is done.
>
> http://mojo.codehaus.org/jalopy-maven-plugin/
>
> A SNAPSHOT of the current svn code has been deployed.
>
> Please vote:
>
> [ ] +1, go ahead
> [ ]  0, whatever
> [ ] -1, nooooooo
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--

-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

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

    http://xircles.codehaus.org/manage_email

[jira] Created: (MGROOVY-82) Allow to compile against groovy-1.0

Allow to compile against groovy-1.0
-----------------------------------

                 Key: MGROOVY-82
                 URL: http://jira.codehaus.org/browse/MGROOVY-82
             Project: Maven 2.x Groovy Integration
          Issue Type: Improvement
          Components: compile
    Affects Versions: 1.0-beta-3
            Reporter: Aaron Digulla
            Assignee: Jason Dillon

I've tried to compile my code with the latest version of the plugin but when I run the code, I get:
java.lang.NoClassDefFoundError: org/codehaus/groovy/runtime/GStringImpl.

This is probably due to the fact that you use the 1.1 compiler in the plugin, now, but I have to run my code with
1.0 until 1.1 is officially released and I find the time to test my code with 1.1.

Please either allow to compile against a specific version of Groovy in your plugin or mention somewhere in
your documentation which version of the plugin depends on which version of Groovy.

--

-- 
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

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

    http://xircles.codehaus.org/manage_email

[jira] Commented: (MWEBSTART-47) Generator and JarResourcesGenerator should have common superclass.

    [
http://jira.codehaus.org/browse/MWEBSTART-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106223
] 

Jerome Lacoste commented on MWEBSTART-47:
-----------------------------------------

patch is OK as it just conveys the ugliness of the initial Generator :)

Question: if we switch the webstart mojo to reuse your generator, then this merging has no meaning, right ?

> Generator and JarResourcesGenerator should have common superclass.
> ------------------------------------------------------------------
>
>                 Key: MWEBSTART-47
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-47
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.0-alpha-2
>            Reporter: Kevin Stembridge
>            Priority: Minor
>         Attachments: MWEBSTART-47-1.diff
>
>
> A new class, JarResourcesGenerator, was created as part of the work done for MWEBSTART-38. It was created
by copying the existing Generator class and modifying it for JarResources. These classes should have a
common superclass so that they can both make use of new features such as the introduction of an
explicitTimestamp placeholder. See MWEBSTART-40.
> Jerome, I'll get a patch under way. Let me know if there is anything in particular you'd like me to watch out for.

--

-- 
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

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

    http://xircles.codehaus.org/manage_email

[jira] Commented: (MGROOVY-81) Repository pom containing dependencies with ${pom.version}

    [
http://jira.codehaus.org/browse/MGROOVY-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106265
] 

Pablo commented on MGROOVY-81:
------------------------------

Yes, I had problems.
Maven tried to download an inexisting version of *groovy-mojo-common*.
(And I discovered that *groovy-mojo-support-1.0-beta-2.pom* contains a non-static dependency.)

It was by using Selenium and Cargo jetty5x.
Anyway, by twiking a bit my POM file, I managed to have something working (don't know exactly why, but working).

> Repository pom containing dependencies with ${pom.version}
> ----------------------------------------------------------
>
>                 Key: MGROOVY-81
>                 URL: http://jira.codehaus.org/browse/MGROOVY-81
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Bug
>          Components: build
>            Reporter: Pablo
>            Assignee: Jason Dillon
>

--

-- 
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

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

    http://xircles.codehaus.org/manage_email