Greg Monroe wrote:
> If I understand this right, the "Pros and Cons" of this are:
>
> Pros -
> Fewer Jenkins build failures (and related e-mails)
> Snapshot artifacts only available if people specifically request them
> "Brave souls" could access newer snapshots with fixes after 4.0
released
>
> Cons -
> We would have unstable snapshots available to the public.
> Support requests might be a bit confusing if folks are using snapshots
>
> Anything missing here?
There are probably other ways to address the jenkins issue.
Only if we decided that we want to have snapshots anyway there would be no
need to look for other ways.
> Am I right in thinking the snapshots are "dated" and not just -snapshot?
I am not sure but my hope would be that we could go for just -SNAPSHOT
Thomas
> -----Original Message-----
> From: Thomas Fox [mailto:[email protected]]
> Sent: Thursday, July 12, 2012 4:43 PM
> To: [email protected]
> Subject: Should we publish snapshots from the jenkins maven builds ?
>
>
> Currently, the jenkins build is problematic because somehow the
> artifacts installed by the mvn:install tasks are not found by the
> test project builds (at least not the newest version), leading to
> failures in the test projects.
>
> We could try to solve that by publishing the torque snapshot
> artifacts to the snapshots repository on repository.apache.org.
> This has the side effect that snapshots are available to the general
public.
> Do we want to do this ?
>
> If yes, I believe we must have the PMC approval for this.
>
> Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> DukeCE Privacy Statement:
> Please be advised that this e-mail and any files transmitted with
> it are confidential communication or may otherwise be privileged or
> confidential and are intended solely for the individual or entity
> to whom they are addressed. If you are not the intended recipient
> you may not rely on the contents of this email or any attachments,
> and we ask that you please not read, copy or retransmit this
> communication, but reply to the sender and destroy the email, its
> contents, and all copies thereof immediately. Any unauthorized
> dissemination, distribution or copying of this communication is
> strictly prohibited.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
