+1

--
Keith.

> On 30 Apr 2014, at 16:59, Robbie Gemmell <[email protected]> wrote:
> 
> HI all,
> 
> It is a bit overdue that we actually publish a release version of the new
> qpid-parent pom for the upcoming maven build, such that we can stop
> installing it locally and actually later release the things that now
> inherit from it (such as the preview maven build available on the 0.28
> branch). I have prepared an initial 1.0 release, which is now staged
> awaiting vote/release.
> 
> Given the very basic nature of this artifact this will be a faster than
> normal vote, so please register your votes early. I will close the vote
> after 12pm UTC on Friday 2nd May.
> 
> 
> The staged pom is available here:
> http://repository.apache.org/content/repositories/orgapacheqpid-1005/org/apache/qpid/qpid-parent/1.0/qpid-parent-1.0.pom
> 
> The associated release archive is available here:
> http://repository.apache.org/content/repositories/orgapacheqpid-1005/org/apache/qpid/qpid-parent/1.0/qpid-parent-1.0-source-release.zip
> 
> Add .asc to the URLs for the signatures.
> 
> 
> You can test the artifact via the maven build itself by using it after
> applying the following diff:
> 
> diff --git qpid/java/pom.xml qpid/java/pom.xml
> index 17c8f23..25cfde4 100644
> --- qpid/java/pom.xml
> +++ qpid/java/pom.xml
> @@ -21,7 +21,7 @@
>   <parent>
>     <groupId>org.apache.qpid</groupId>
>     <artifactId>qpid-parent</artifactId>
> -    <version>1.0-SNAPSHOT</version>
> +    <version>1.0</version>
>   </parent>
> 
>   <groupId>org.apache.qpid</groupId>
> @@ -314,6 +314,12 @@
>         <enabled>false</enabled>
>       </snapshots>
>     </repository>
> +
> +    <repository>
> +      <id>qpid.staging</id>
> +      <url>
> https://repository.apache.org/content/repositories/orgapacheqpid-1005</url>
> +      <layout>default</layout>
> +    </repository>
>   </repositories>
> 
>   <reporting>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to