Jira component for cordovasim
by Gorkem Ercan
Should we create a new Jira component for cordovasim? I think cordovasim
issues are different from browsersim and this is what we use for them right
now.
--
Gorkem
9 years, 5 months
integration stack component installation
by Paul Leacu
Greetings,
At the JBoss f2f last week in Brno there was a meeting to discuss the ease of installation
issue (or lack thereof) of integration stack components. Presented here is a summary of the
issue and a proposed solution as drafted by the team. Although members of platform architecture,
engineering, PM and QE were present - the solution is simply proposed at this time. We also
plan to evolve the solution over time - so that the issue will be addressed more fully.
Your comments are welcome!
Thanks,
--paull
------
Issue: Finding integration stack components to install is too difficult. This was made
clear by Fuse Tooling usability reviews and is discussed in detail here:
https://mojo.redhat.com/docs/DOC-977658
Proposed Solution:
- Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product groupings and establish
JBTIS/ JBDSIS installers based on JBT/ JBDS.
Discussion:
As it exists today, users who search within the standard Eclipse Marketplace for keywords
such as "Camel Editor" or "Fuse" are directed to the JBDS or JBT Kepler installers. Users
must select the "more info" link on the Marketplace installer page and then page down to
find this text:
"Also available is the JBoss Developer Studio Integration Stack, which includes support for SwitchYard, Camel, Fuse, Fabric8, Drools, jBPM, ModeShape, Teiid and more. It is available from within JBoss Central, via the Software/update tab."
This is the first mention of Fuse and directs the user to install JBDS (or JBT) and then,
after installing/ restarting and as a separate action, use the Software/Update tab within
JBoss Central to find the Fuse tooling. In this case Fuse is part of:
"JBoss Integration and SOA Development" - (The category description does mention Fuse.)
Solution Details:
The extended IS-aware Eclipse Marketplace entries will reference the existing update site
and when selecting "Install" you will get a yet-to-be-defined subset of the Eclipse features that
will match what you would get when using the install from JBoss Central today - but without having
to install Developer Studio plugins separately first.
The installer option is to be based on the JBDS installer and will be made available from the CSP/jboss.org
download next to the existing installer.
JBDS 7.1.1.GA/JBDSIS 7.1.0.GA (Kepler) - What can we do today?
- https://issues.jboss.org/browse/JBTIS-354
The least required changes would leave the user with a single JBDSIS installer and a single
JBTIS installer when searching for "Fuse" or "Data Virtualization" for example. Upon selecting
one of these installers the user would see all available installation-units (features) available
in the combined integration stack. Users could then select all or just the fuse tooling IUs.
This is the "laundry list" approach.
JBDS 8.1.0.GA/JBDSIS 8.0.x.GA (Luna) - Short term for upcoming tooling releases.
- https://issues.jboss.org/browse/JBTIS-355
* Add a new com.jboss.devstudio.core.central.feature that packages up the com.jboss.devstudio.core.central
plugin and include this in com.jboss.devstudio.core.feature (this is missing today).
* Enable usage tracking in JBTIS components' MANIFEST.MF files (this is under way now)
- https://issues.jboss.org/browse/JBTIS-290
* create three connectors, each based on the content in JBDSIS discovery plugin.xml's top three
connector categories
- https://issues.jboss.org/browse/JBTIS-357
1. Fuse ServiceWorks - ref: JBoss Integration and SOA Development
2. BRMS/BPMS - ref: JBoss Business Process and Rules Development
3. JBoss Data Virtualization - ref: JBoss Data Virtualization Development
** A1: PMs (hey Alan) must come up with appropriate names for 1-3 above. The naming convention should be
"compatible" with a Mobile tools install that have been requested too.
The user searches for "Fuse" from Marketplace and immediately finds JBDSIS. The installer allows
the user to select from 1-3 above. The user selects "Fuse ServiceWorks" (if that's the name) by
selecting the radio button (or selects all easily).
JBDS 9.0.0.GA/JBDSIS 9.0.x.GA (Mars) - Make it better - continue to evolve the solution
- https://issues.jboss.org/browse/JBTIS-356/ https://issues.jboss.org/browse/JBIDE-18734
Refactor project examples in Central to remove dependencies on portal & seam (size reduction - avoid
installing unnecessary plugins).
Similar experience to Luna except the installer is much leaner.
No default perspective change - potential stretch goal.
This subject went back and forth. The user has an established perspective when they began the installation
process and may be installing multiple features which may very well have different default perspectives.
Once users manually set their perspective it will be remembered the next time they start the tool.
Alternatively, the installer option definitely should be able to do this. When installing into an existing
Eclipse that is not that trivial, which is one of the reasons why JBoss Central exists. Central shows
up across perspectives and when the user selects Fuse the Fuse project can declare it and would ask users
if they want to move to the Fuse perspective.
We could also look into adding "roles" to Central to make it adopt better depending on what interest you
have as a user.
--paull
9 years, 5 months
PLEASE READ: Proposal for new approach to managing transient upstream deps like Tern, AngularJS and Thym
by Nick Boldt
If you're a dev or QE for projects which use Tern, AngularJS, or Thym,
or any other upstream incubating / frequently-changing dependency,
please *read and reply* if this approach seems reasonable to you.
---
For dependencies like Tern, AngularJS and Thym, instead of iteratively
updating them every few weeks in the target platform, we could instead
treat them like jbosstools-* components, and simply refer to them as
<dependencies> within dependent projects' root poms.
We used to do this for "moving target" upstream dependencies like m2e-*
extensions, but for JBDS 8 we put EVERYTHING into the target platform
and it was a bit of a pain to manage.
We could go a step further, too, and do automated weekly pulls of new
upstream deps.
---
The process would look like this:
* every Friday, a Jenkins job pings eclipse.org looking for the latest
available Tern, AngularJS, and Thym builds.
* if a newer one is found, a mirror is pulled and added to the pile on
http://download.jboss.org/jbosstools/updates/requirements/
* the latest one is then symlinked from
http://download.jboss.org/jbosstools/updates/requirements/{tern,angularjs...
* new entries are added to the parent pom for these 3 URLs:
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
* projects which wish to build against these newer deps can do so by
choice (local experiments) or automatically by updating their root poms
to include new <repository> entries:
https://github.com/jbosstools/jbosstools-jst/blob/master/pom.xml#L23-L27
* projects will then need to monitor their manifests/feature.xml files
to ensure they depend on the correct versions of upstream deps:
https://github.com/jbosstools/jbosstools-jst/blob/master/plugins/org.jbos...
* should they forget, their build will break w/ an obvious error message
* they can then apply a fix & rebuild, or rollback to an earlier
upstream dep in their root pom's <repository> reference, if they're not
able to move up to the newer Tern. Angular, or Thym dependency.
* if the upstream component stabilizes, it can then later be added to
the target platform; this is an approach suited for incubating upstream
dependencies.
WDYT?
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 5 months
dockerization of jbosstools-website
by Max Rydahl Andersen
Hi,
To experiment with docker and actually make it useful I today pushed a
Dockerfile + .dockerignore to
https://github.com/jbosstools/jbosstools-website
I have not yet updated the docs so the info on how to use it is
currently in the commit:
https://github.com/jbosstools/jbosstools-website/commit/c9b9224a89f73f7bb...
But basically now instead of following the somewhat complicated full
setup of ruby/awestruct you do this:
Install Docker (or boot2docker if on windows/osx)
Build docker image:
$ cd jbosstools-website
$ docker build -t jbosstools-website .
(this takes a while: 10-40 min dependent on network speed/cpu you got)
From that time on you can now do this to run local website build:
$ docker run -it --rm -p 4242:4242 -v `pwd`:/jbosstools-website -t
jbosstools-website
(if on windows replace `pwd` with full path to your jbosstools-website
checkout)
Content will then be available at http://${DOCKER_HOST}:4242
So why is this interesting ?
Well, look at the Dockerfile - its simple steps to setup a ruby
environment.
Now imagine doing the same for a java environment. with maven and p2
mirrors for target platforms prepopulated/preconfigured (maybe even
jenkins - but it might not be needed anymore in the same degree as
before).
Suddenly you got a reproducible and isolated build system for any number
of eclipse plugins.
...and it can run anywhere and we can start testing and building in full
isolation.
This could become really useful!
/max
http://about.me/maxandersen
9 years, 5 months
dockerization of jbosstools-website
by Max Rydahl Andersen
Hi,
To experiment with docker and actually make it useful I today pushed a
Dockerfile + .dockerignore to
https://github.com/jbosstools/jbosstools-website
I have not yet updated the docs so the info on how to use it is
currently in the commit:
https://github.com/jbosstools/jbosstools-website/commit/c9b9224a89f73f7bb...
But basically now instead of following the somewhat complicated full
setup of ruby/awestruct you do this:
Install Docker (or boot2docker if on windows/osx)
Build docker image:
$ cd jbosstools-website
$ docker build -t jbosstools-website .
(this takes a while: 10-40 min dependent on network speed/cpu you got)
From that time on you can now do this to run local website build:
$ docker run -it --rm -p 4242:4242 -v `pwd`:/jbosstools-website -t
jbosstools-website
(if on windows replace `pwd` with full path to your jbosstools-website
checkout)
Content will then be available at http://${DOCKER_HOST}:4242
So why is this interesting ?
Well, look at the Dockerfile - its simple steps to setup a ruby
environment.
Now imagine doing the same for a java environment. with maven and p2
mirrors for target platforms prepopulated/preconfigured (maybe even
jenkins - but it might not be needed anymore in the same degree as
before).
Suddenly you got a reproducible and isolated build system for any number
of eclipse plugins.
...and it can run anywhere and we can start testing and building in full
isolation.
This could become really useful!
/max
http://about.me/maxandersen
9 years, 5 months
Re: [jbosstools-dev] Confusing name - time for a change?
by Burr Sutter
trying to add that list
> On Nov 14, 2014, at 5:46 AM, Max Rydahl Andersen <max.andersen(a)redhat.com> wrote:
>
> *please* move this to jbosstools-dev if you want anything changed.
>
> noone from aerogear/hybrid mobile dev is in the cc.
>
> /max
>
>> Hi all,
>>
>> the name "Aerogear" appears on JBoss Tools website (http://tools.jboss.org/features/aerogear.html) and on internal Mojo pages talking about it.
>>
>> I believe that the name should be only "Hybrid Mobile (Cordova) Tools" or similar. It doesn't have any special tooling just for Aerogear libraries.
>>
>> --Petr
>>
>> ----- Original Message -----
>> From: "Burr Sutter" <bsutter(a)redhat.com>
>> To: "Len DiMaggio" <ldimaggi(a)redhat.com>
>> Cc: "Paul Leacu" <pleacu(a)redhat.com>, "Jiri Pallich" <jpallich(a)redhat.com>, "Max Rydahl Andersen" <max.andersen(a)redhat.com>, "Petr Stribny" <pstribny(a)redhat.com>
>> Sent: Friday, 14 November, 2014 12:45:57 AM
>> Subject: Re: Confusing name - time for a change?
>>
>> Where is the name seen?
>>
>>
>>> On Nov 13, 2014, at 10:59 AM, Len DiMaggio <ldimaggi(a)redhat.com> wrote:
>>>
>>> Hey Paul, Jiri, Max, and Burr,
>>>
>>> I had a question about the Mobile tooling - the name for this is still Areogear - will we be able to change this to "mobile" any time soon?
>>>
>>>
>>> Thanks!,
>>> Len
>>>
>>>
>>>
>>> --
>>>
>>> Len DiMaggio (ldimaggi(a)redhat.com)
>>> JBoss by Red Hat
>>> 314 Littleton Road
>>> Westford, MA 01886 USA
>>> tel: 978.392.3179
>>> cell: 781.472.9912
>>> http://www.redhat.com
>>> http://community.jboss.org/people/ldimaggio
>>>
>>> <RHxJBpngthumb.png> <http://www.redhat.com/>
>>>
>
>
> /max
> http://about.me/maxandersen
9 years, 5 months
JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
by Paul Leacu
Greetings,
The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible Integration Stack Beta tooling is
released. This capture contains new versions of BPMN2, Fuse Tooling, SwitchYard and Teiid Designer.
This beta release is available as "development" or as "early access".
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)
3. Select the Software/Update tab in the JBoss Central view. Check the "Enable Early Access" check box.
The production Early Access tooling appears in the 'Features Available' window.
done!
The standard p2 installer is also available for JBDSIS:
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:'
https://devstudio.redhat.com/updates/8.0-development/integration-stack/
The standard p2 installer is available for the community capture (JBTIS):
1. 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'
2. Start eclipse-with-jbt from step 1, then:
Help > Install New Software...
Add...
- use this for 'Location:'
http://download.jboss.org/jbosstools/updates/development/luna/integration...
JBoss Central is supported for the community capture as Early Access (JBTIS):
1. Start eclipse-with-jbt from step 1
2. Select the Software/Update tab in the JBoss Central view. Check the "Enable Early Access" check box.
The Early Access tooling appears in the 'Features Available' window.
----
** 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, 5 months
