RE: [wtp-incubator-dev] JAX-WS standalone build failure

[David M Williams <david_williams@xxxxxxxxxx>]

> Would
it still be possible to produce those downloads as part 
> of the main WTP build if the standalone
build was dropped?

Yes. I've opened bug 304984 to track
the work. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304984

I think I'd prefer this approach, as
opposed to a true stand-alone build.
It would probably be more accurate,
in the sense it would be built with 
all the "right" pre-reqs.
Even though I do still hope to move to more of 
a componentized  build,  it
seems to me the effort to provide a separate 
package would "fit in" to
that long term effort, instead of continuing to 
hack the stand-alone build script. So,
I'll take a look. Might take a week 
or two ... but not long. Please comment
in the bug if you have some 
critical need where its needed sooner.


Thanks,

From:	shane clarke <shane_clarke@xxxxxxxxxxx>
To:	<wtp-incubator-dev@xxxxxxxxxxx>
Date:	03/08/2010 06:39 AM
Subject:	RE: [wtp-incubator-dev] JAX-WS standalone build failure
Sent by:	wtp-incubator-dev-bounces@xxxxxxxxxxx

---

Hi David,

We do use the standalone build output (jaxws runtime, sdk downloads) to
check installs into earlier Eclipse/WTP releases. (3.5.x, 3.1.x)

It is possible to install the milestones into an earlier Eclipse install
using the update site but these downloads are useful for testing installed
integration builds between milestones.

Would it still be possible to produce those downloads as part of the main
WTP build if the standalone build was dropped?

Thanks,
Shane

---

To: wtp-incubator-dev@xxxxxxxxxxx
Subject: Re: [wtp-incubator-dev] JAX-WS standalone build failure
From: david_williams@xxxxxxxxxx
Date: Sun, 7 Mar 2010 20:04:06 -0500


Yes, changing pre-reqs, probably? Perhaps bug 300015 all over again? 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=300015

Do you think we still need this stand alone build? Do you actually use
it for anything other than a quick check? If not, I'd prefer to drop it,
since it requires some special, custom attention. You can do quick checks
in dev. env.,. in my humble opinion and the build machine standalone build
is not really providing that much. Let me know if you need it, otherwise
I'll just remove it and you'll just be part of the wtp build. 

Thanks,

From:	shane clarke <shane_clarke@xxxxxxxxxxx>
To:	<wtp-incubator-dev@xxxxxxxxxxx>
Date:	03/07/2010 06:46 PM
Subject:	[wtp-incubator-dev] JAX-WS standalone build failure
Sent by:	wtp-incubator-dev-bounces@xxxxxxxxxxx

---

Hi David,

There are a lot of compilation errors in the build from the test plug-ins
due to unresolved types. They all look like they have problems finding
the JAX-WS plug-ins they depend on to test.

Can you think of anything that may have changed in the builds that might
be causing this?

Thanks,
Shane

---

Hotmail: Free, trusted and rich email service.
Get
it now._______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev

---

Hotmail: Free, trusted and rich email service.
Get
it now._______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev