We are testing wildfly snapshot with our latest jbossws-cxf. It requires us to pull
wildfly and build locally each time before we run the jbossws test suite. If there
is wildfly snapshot binary zip can be deployed to maven repo, we can unpack the binary
in our maven build.
----- Original Message -----
From: "Tomaž Cerar" <tomaz.cerar(a)gmail.com>
To: "Jim Ma" <ema(a)redhat.com>
Cc: "Claudio Miranda" <claudio(a)claudius.com.br>,
Sent: Thursday, December 18, 2014 9:20:33 PM
Subject: Re: [wildfly-dev] Wildfly binary snapshot
I see no real need for that as this wouldn't provide any good usage pattern
If your code builds upon wildfly snapshot that is fine, but you should
build wildfly locally for that.
As having (public) code depend on snapshot is not really a good practice as
it can result in non reproducible build.
You do have 9.0.0.Alpha1 published, and soon there will be Beta1 out which
are preview versions that you should build upon.
On Thu, Dec 18, 2014 at 12:41 PM, Jim Ma <ema(a)redhat.com> wrote:
So we need a separated storage and nexus server to place snapshot
artifacts ? Is there a plan to setup one?
This is required if other project wants to catch up with wildfly latest
change and depends on snapshot artifact.
On 12/18/2014 06:53 PM, Tomaž Cerar wrote:
No we do not publish nightly snapshots to maven repo.
As this would be a big burden on storage & nexus performance.
On Thu, Dec 18, 2014 at 3:23 AM, Jim Ma <ema(a)redhat.com> wrote:
> Thanks, Claudio and Brian. Do we have maven snapshot artifacts deployed ?
> On 12/18/2014 09:51 AM, Claudio Miranda wrote:
> > https://ci.jboss.org/hudson/job/WildFly-latest-master/
> > On Wed, Dec 17, 2014 at 10:58 PM, Jim Ma <ema(a)redhat.com> wrote:
> >> Hi,
> >> When our community user wants to try the latest wildfly9 snapshot, does
> >> he or she have to git clone our code and build locally ? Can we set up
> >> job to deploy snapshot binary/artifacts every day or every other day ?
> >> Cheers,
> >> Jim
> >> _______________________________________________
> >> wildfly-dev mailing list
> >> wildfly-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> wildfly-dev mailing list