integrations stack in jboss tools 4.2 early access
by Max Rydahl Andersen
Hey Paul/Nick/Denis,
I'm at eclipsecon so have limited/broken access to check things.
Can you help this user commenting on release blog that he cannot find
integration stack in early access.
/max
http://about.me/maxandersen
Forwarded message:
> From: Disqus <notifications(a)disqus.net>
> To: tools(a)jboss.org
> Subject: Re: New comment posted on JBoss Tools - JBoss Tools and
> Developer Studio for Eclipse Luna
> Date: Tue, 28 Oct 2014 08:40:08 -0000
>
>
>
> Jaén Swart <jaenswart(a)gmail.com> wrote, in response to maxandersen:
>
> Hi Max,
>
> I just installed both devstudio 8 but also the luna SR1 with JBoss
> Tools 4.2.
>
> In the last after enabling early access in JBoss Central, I still
> cannot see the integration stack components.
>
> Thus in short I cannot see them either from devstudio (as you
> explained), but also not from jboss tools
>
> IP address: 209.132.186.30
> Link to comment:
> http://redirect.disqus.com/url?impression=04f039d2-5e7e-11e4-9247-0025908...
>
> maxandersen wrote:
>
> It can but not yet in a easy to install way.
>
> I hope to be able to announce a build of integration stack very soon
> where it becomes available via early access.
>
> -----
> Options: You can moderate through email. Respond in the body with
> "Delete". Reply with "Like" to like this comment, or respond with
> anything else to approve this comment and post your message as a reply
> comment.
>
> Or use the moderate panel:
> https://jbosstools.disqus.com/admin/moderate/#/pending
>
>
> Stop receiving notifications when new comments are posted:
> http://disqus.com/account/#notifications
9 years, 4 months
JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 Luna Integration Stack tooling QE handoff
by Paul Leacu
Greetings,
The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible Integration Stack tooling is
available for QE testing. This capture contains new versions of BPMN2, Fuse Tooling, SwitchYard
and Teiid Designer.
This release is for internal consumption only until after QE has sanctioned it.
JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
1. If installing from Eclipse Luna:
Help > Eclipse Marketplace...
- in the 'Search' tab enter 'jbds' in the 'Find' input widget
- select the 'Go' button
- install 'Red Hat JBoss Developer Studio 8.0.0.GA'
2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
Help > Install New Software...
Add...
- use this for 'Location:'
http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio...
Done!
Note that the integration stack update site is in a QE development area until after it's validated. If you have
trouble accessing the server add these lines to your /etc/hosts or C:\windows\system32\drivers\etc\hosts
file:
10.16.89.17 dev39.mw.lab.eng.bos.redhat.com www.qa.jboss.com
10.16.90.43 hudson.qa.jboss.com
JBoss Central is supported for the production capture as Early Access (JBDSIS): ** Note - Select the 'Enable Early Access' checkbox **
* Specify the integration stack discovery artifact:
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Beta1/devstudio-integration-stack-directory.xml
-Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Beta1
The standard p2 installer is available for the community capture (JBTIS):
* Start jbdevstudio or eclipse-with-jbds, then:
Help > Install New Software...
Add...
- use this for 'Location:' ** Note this is a different URL than before **
http://download.jboss.org/jbosstools/updates/development/luna/integration...
JBoss Central is supported for the community capture as Early Access (JBTIS): ** Note - Select the 'Enable Early Access' checkbox **
* Install JBoss Tools 4.2.0.Final:
Help > Eclipse Marketplace...
- in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
- select the 'Go' button
- install 'JBoss Tools 4.2.0.Final'
* Specify the integration stack discovery artifact:
./eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.2.0.Beta1/jbosstools-integration-stack-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.2.0.Beta1
** New - A standalone p2 installer is now available for the community capture (JBTIS):
* Start eclipse Luna, then:
Help > Install New Software...
Add...
- use this for 'Location:'
http://download.jboss.org/jbosstools/updates/development/luna/integration...
** Extra Credit **
For component and QE test developers - the JBTIS target platform is:
https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
Give it a try!
9 years, 4 months
Re: [jbosstools-dev] FYI: incubator-ripple moved to jbosstools organization
by Ilya Buziuk
I'd like to add some additional info to the #2.
For now all ripple specific code is situated in the
*org.jboss.tools.vpe.cordovasim.ripple *plugin in the *ripple* folder -
https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim/...
If there is a new bug / feature request on the cordovasim side it must be
fixed it in the giant (~2.5 Mb) js file. This approach has 2 main drawbacks:
1) It's utterly complicated to catch up updates from ripple (need to mainly
build ripple and merge 2 giant ripple.js file)
2) It's extremely unhandy to contribute changes back to ripple
That is why we come up with a new approach - fork ripple for jbosstools and
keep all cordovasim changes above the ripple's *master* branch ( <- #1
which is already solved).
How to try it:
- clone https://github.com/jbosstools/incubator-ripple
- checkout *cordovasim *branch
- pre-build step - Build Requirements
<https://github.com/jbosstools/incubator-ripple#build-requirements>
- run (in the project root): *./configure*
- run *(in the project root): jake*
- the result of the build will be in the *pkg/hosted* folder
- assuming that all necessary plugins for running *aerogear *and
*cordovasim* are in the workspace you can remove everything from the
ripple folder (
https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim/...)
and substitute it with a newly build content of the *pkg/hosted* folder
- that's it. If you run new Eclipse application, create HMT project and
run it via Cordovasim it will use brand new ripple build
Basically we want to make one step ahead and automate the process above ^.
Will be glad to hear your ideas / proposals on it. The main purpose of the
letter is to give extra food for thoughts before f-2-f ;-)
> On Tue, Oct 14, 2014 at 12:54 PM, Max Rydahl Andersen <manderse(a)redhat.com
> > wrote:
>
>> Heya,
>>
>> For a while we've had our fork of incubator-ripple under
>> https://github.com/ibuziuk/incubator-ripple which was manually built to
>> then get included into cordovasim.
>>
>> We will be looking at doing two things: 1) move the repo to jbosstools
>> so it is together with all the other work we do 2) setup more automatic
>> builds of this.
>>
>> For today #1 is solved, and
>> https://github.com/jbosstools/incubator-ripple exists.
>>
>> For #2 Ilya will follow up on in the following week(s), intent is we got
>> a plan for this by the face-2-face to execute on.
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Best Regards,
> Ilya Buziuk
>
--
Best Regards,
Ilya Buziuk
9 years, 5 months