Is there going to be a groovy-eclipse-batch:2.2.1-RELEASE?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Is there going to be a groovy-eclipse-batch:2.2.1-RELEASE?

Chris Hamilton
We’re using Groovy 2.2 on a project and not quite ready to jump to 2.3.

My problem is we are still using the groovy-eclipse-batch:2.2.1-01-SNAPSHOT with Maven and I would prefer to use a RELEASE version.

Since there is a groovy-eclipse-batch:2.3.4-01-RELEASE in Maven Central I was just wondering if you could publish a RELEASE version of groovy-eclipse-batch:2.2.1?

Chris Hamilton
C & T Consulting, Inc.
Currently on assignment at Verizon Wireless
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Is there going to be a groovy-eclipse-batch:2.2.1-RELEASE?

Kris De Volder
We usually only publish the latest version of the compiler as a 'release'.

It is certainly possible to put out a 'release' for latest on 2.2.x.
We just don't do it by default because its extra work for us.

I'll see what I can do. I also need to put out a 2.3.6 so can look at it at the same time.

Please keep an eye on that ticket.

Usually when I build the maven artefacts and stage them on codehaus someone from
the community volunteers to test them out before I release them to maven central.

So it would be nice if you could test the 2.2.1 artefact :-)

Cheers,

Kris



On Wed, Jul 30, 2014 at 8:43 AM, Chris Hamilton <[hidden email]> wrote:
We’re using Groovy 2.2 on a project and not quite ready to jump to 2.3.

My problem is we are still using the groovy-eclipse-batch:2.2.1-01-SNAPSHOT with Maven and I would prefer to use a RELEASE version.

Since there is a groovy-eclipse-batch:2.3.4-01-RELEASE in Maven Central I was just wondering if you could publish a RELEASE version of groovy-eclipse-batch:2.2.1?

Chris Hamilton
C & T Consulting, Inc.
Currently on assignment at Verizon Wireless
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|

Re: Is there going to be a groovy-eclipse-batch:2.2.1-RELEASE?

Chris Hamilton
Kris,

I’d be happy to test the release. I set up our Nexus to proxy the Staging repository but it appears to require authentication and I do not have credentials for the codehaus.org nexus staging repository.

If you want me to test this in staging, I guess we’ll need to get credentials set up. Is there an alternative that I am not aware of, if so let me know and I can work on that.

Thanks,
Chris Hamilton
C & T Consulting, Inc. 
Currently on assignment at Verizon Wireless

On Aug 5, 2014, at 11:42 AM, Kris De Volder <[hidden email]> wrote:

We usually only publish the latest version of the compiler as a 'release'.

It is certainly possible to put out a 'release' for latest on 2.2.x.
We just don't do it by default because its extra work for us.

I'll see what I can do. I also need to put out a 2.3.6 so can look at it at the same time.

Please keep an eye on that ticket.

Usually when I build the maven artefacts and stage them on codehaus someone from
the community volunteers to test them out before I release them to maven central.

So it would be nice if you could test the 2.2.1 artefact :-)

Cheers,

Kris



On Wed, Jul 30, 2014 at 8:43 AM, Chris Hamilton <[hidden email]> wrote:
We’re using Groovy 2.2 on a project and not quite ready to jump to 2.3.

My problem is we are still using the groovy-eclipse-batch:2.2.1-01-SNAPSHOT with Maven and I would prefer to use a RELEASE version.

Since there is a groovy-eclipse-batch:2.3.4-01-RELEASE in Maven Central I was just wondering if you could publish a RELEASE version of groovy-eclipse-batch:2.2.1?

Chris Hamilton
C & T Consulting, Inc.
Currently on assignment at Verizon Wireless
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




Reply | Threaded
Open this post in threaded view
|

Re: Is there going to be a groovy-eclipse-batch:2.2.1-RELEASE?

Kris De Volder
I wasn't aware you need credentials. I don't think you do. All you need is to add the staging repos to your pom or settings.xml

I.e. something like this:

                <pluginRepository>
                   <id>codehaus-staging</id>
                   <name>codehaus-staging</name>
                   <url>https://nexus.codehaus.org/content/groups/staging/</url>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>always</updatePolicy>
                        <checksumPolicy>warn</checksumPolicy>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                        <updatePolicy>always</updatePolicy>
                        <checksumPolicy>warn</checksumPolicy>
                    </snapshots>
                    <layout>default</layout>
                </pluginRepository>
...

                <repository>
                   <id>codehaus-staging</id>
                   <name>codehaus-staging</name>
                   <url>https://nexus.codehaus.org/content/groups/staging/</url>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>always</updatePolicy>
                        <checksumPolicy>warn</checksumPolicy>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                        <updatePolicy>always</updatePolicy>
                        <checksumPolicy>warn</checksumPolicy>
                    </snapshots>
                    <layout>default</layout>
                </repository>

Maybe credentials are needed to mirror the staging repo, or to publish to tthem,, but don't think they are needed
to simply use them directly in your pom or settings.xml to resolved dependencies.


Kris


On Wed, Aug 6, 2014 at 5:12 AM, Chris Hamilton <[hidden email]> wrote:
Kris,

I’d be happy to test the release. I set up our Nexus to proxy the Staging repository but it appears to require authentication and I do not have credentials for the codehaus.org nexus staging repository.

If you want me to test this in staging, I guess we’ll need to get credentials set up. Is there an alternative that I am not aware of, if so let me know and I can work on that.

Thanks,
Chris Hamilton
C & T Consulting, Inc. 
Currently on assignment at Verizon Wireless

On Aug 5, 2014, at 11:42 AM, Kris De Volder <[hidden email]> wrote:

We usually only publish the latest version of the compiler as a 'release'.

It is certainly possible to put out a 'release' for latest on 2.2.x.
We just don't do it by default because its extra work for us.

I'll see what I can do. I also need to put out a 2.3.6 so can look at it at the same time.

Please keep an eye on that ticket.

Usually when I build the maven artefacts and stage them on codehaus someone from
the community volunteers to test them out before I release them to maven central.

So it would be nice if you could test the 2.2.1 artefact :-)

Cheers,

Kris



On Wed, Jul 30, 2014 at 8:43 AM, Chris Hamilton <[hidden email]> wrote:
We’re using Groovy 2.2 on a project and not quite ready to jump to 2.3.

My problem is we are still using the groovy-eclipse-batch:2.2.1-01-SNAPSHOT with Maven and I would prefer to use a RELEASE version.

Since there is a groovy-eclipse-batch:2.3.4-01-RELEASE in Maven Central I was just wondering if you could publish a RELEASE version of groovy-eclipse-batch:2.2.1?

Chris Hamilton
C & T Consulting, Inc.
Currently on assignment at Verizon Wireless
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email