New Kepler M5 target platform in progress
by Nick Boldt
I've started work on the new Kepler M5 target platform, which includes
newer versions of m2e (1.3), m2e-wtp (0.17), GPE (3.1.3), and GWT SDK
(2.5.0), as well as the usual Eclipse.org stuff like Kepler (M5),
Eclipse (4.3.0.M5), WTP (3.5.0.M5), and BIRT 4.2.2.
It may have to be rebuilt again in a day or two if the Kepler staging
site I used changes to pull in newer WTP bits, or if the final WTP build
for M5 is different from the I build I used.
Speaking of WTP... it appears that the *org.eclipse.persistence.jpa*
feature no longer exists. The *org.eclipse.persistence.jpa* PLUGIN is
still part of WTP (and therefore Kepler), but it's now only wrapped by
the org.eclipse.jpt.jpa.feature. If you currently depend on the old
org.eclipse.persistence.jpa feature, you should now depend on either
just the plugin(s) you actually need, or the new feature.
---
The new TP bits will be located here, but are subject to change as noted
above:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
(REPO/ folder or zip file)
(A significant change in content, rather than just a fix, will result in
creation of a .3 version instead of simply rebuilding the .2 version.)
---
When the TP is ready, I'll switch the parent pom to use it by default.
For now, you can test it using this:
mvn verify -DTARGET_PLATFORM_VERSION=4.30.2.Alpha1-SNAPSHOT
---
Aside: if you're wondering how we got from 4.30.0 to 4.30.2, there was
an TP built in between which removed uml2, graphiti, and zest. See
https://issues.jboss.org/browse/JBIDE-13435.
Comments or issues w/ the new TP in progress, report them on
https://issues.jboss.org/browse/JBIDE-13336.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years
Plugin versions
by Alexey Kazakov
Hi guys,
I have a question regarding updating plugin/feature version for JBT
4.1.0.Alpha.
Should we just increment N in x.N.y for all the plugins/features
versions which we changed even if it was just a minor bug fixing?
Should we change Eclipse (wtp, etc.) dependencies in plugin.xml too even
if we don't use any new API from Kepler?
We don't test our plugins against Juno any more afaik so should we do it?
Max, Denis, ...?
13 years
Alpha1 branch/code freeze readiness: 10 projects have not yet branched! :: ACTION REQUIRED!
by Nick Boldt
The following projects are branched for Alpha1, using a
"jbosstools-4.1.0.Alpha1" branch:
base
hibernate
javaee
jst
build
build-ci
build-sites
download.jboss.org
maven-plugins
This project has branched using a "1.5.0.Alpha1" branch:
webservices
The following projects have not yet created "jbosstools-4.1.0.Alpha1"
branches (if following JBT release convention), or "x.y.0.Alpha1"
branches (if following their own versioning convention):
birt
central
forge
freemarker
gwt
integration-tests
openshift
portlet
server
vpe
Project Leads, please branch your projects! Or, Denis/Max, can you
branch them?
Wondering how to branch? Try this gist:
https://gist.github.com/nickboldt/4740072
export GITUSER=nickboldt
cd ~/trunk/jbosstools-birt
~/bin/git-new-branch.sh jbosstools-4.1.0.Alpha1
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years
Re: [jbosstools-dev] Status for VPE/BrowserSim - 4 Feb 2013
by Mickael Istria
On 02/05/2013 11:51 AM, Yahor Radtsevich wrote:
> On Tue, Feb 5, 2013 at 1:25 PM, Mickael Istria <mistria(a)redhat.com> wrote:
>> On 02/05/2013 11:07 AM, Yahor Radtsevich wrote:
>>
>> On Tue, Feb 5, 2013 at 10:44 AM, Mickael Istria <mistria(a)redhat.com> wrote:
>>
>> Hi Yahor et al.
>>
>> I have some ideas/questions regarding integration of those tools in
>> BrowserSim and JBT/JBDS.
>> * Since most of them at actually HTML code, could the pop-up open in a
>> dedicated view inside JBT/JBDS? Would it make sense in term of usability?
>>
>> Now BrowserSim opens as a separate process.
>>
>> I understand that, and I think it's good to have it in a separate process.
>> What I had in mind is that the tab that contain the "debugger"
>> (Firefox-Lite, Weinre, Ripple..) probably has an URL and opens in a browser.
>> So if it's an URL, this could be opened inside an Eclipse view or editor
>> when launching BrowserSim. Don't you think it will improve usability and
>> consistency of the tools we provide?
>>
>>
>> * I remember a presentation at EclipseCon which highlighted usage of
>> BrowserFunction to make a nice interaction between web content -displayed in
>> SWT Browser- and Eclipse. See
>> http://eclipsecon.org/2010/sessions/?page=sessions&id=1418 and
>> http://www.slideshare.net/bokowski/embedding-web-uis-in-your-eclipse-appl...
>> . Do you have any plan to leverage this for a better integration of Ripple
>> and co in JBT/JBDS ?
>>
>> Actually BrowserSim is an SWT-based application. SWT Browser widget
>> and BrowserFunction are already widely used in it.
>> We can integrate BrowserSim/Ripple windows in any Eclipse view, but
>> unfortunately it will lead to lots of Eclipse crashes and poor user
>> experience.
>>
>> Indeed, it would be a complex and risky integration. I'm not trying to push
>> a feature here ;) That was just an idea I wanted to share in order to make
>> HTML debugging possible from inside Eclipse rather that in
>> yet-another-window.
> Now I get your idea. Yes, this would be great!
>
> Sadly, there are some limitations:
> * Firebug Lite and Ripple require to be in the same process with
> BrowserSim, because they communicate with BrowserSim as child/parent
> browser windows.
Ok, I did not know about the linkage of those 2 windows through
child/parent browser window. It makes sense. What would be very fun then
would be to have browsers allowing to have child/parent windows in
different process with a protocol to communicate between them.
But I guess I'm going to far ;)
> * Weinre requires to be run in WebKit-based browser, which means the
> same JVM crashes are possible.
Ok.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
13 years, 1 month
New git repository for soa tests
by Andrej Podhradsky
Hi folks,
what do you think about having new git repository for SOA related bot tests?
SOA tests include bpel, jbpm, modeshape, teiid designer etc. And these components are independently released.
Now, the soa tests are in jbosstools-integration-tests together with jbt core tests.
The problem is that the next soa release will be for juno, so I'm developing tests under Juno.
It means committing to jbosstools-4.0.x branch while people for JBT core commit to the master branch (Kepler).
But what happens when I start developing soa tests for Kepler? Possibly commit my juno changes to kepler branch.
What happens when there is another eclipse release? It seams that I will be still behind the master branch :(
Another reason is that soa tests have nothing in common with core tests. Everyone is still dividing the tools into core and soa.
So, lets start discussing about pros and cons ;-)
Have a nice day!
--
Andrej Podhradsky
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
13 years, 1 month
Who's Who in JBTIS (JBoss Tools Integration Stack) ?
by Nick Boldt
Have started a spreadsheet [0] which lists projects, owners, job names,
and some useful URLs (github/sourceforge repo, update sites):
[0]
https://docs.google.com/spreadsheet/ccc?key=0AmGcQy-AtllqdEo4M25tdDhyNEFj...
If you'd like to be an editor/maintainer, send me your usual Google
Drive login and I'll add you.
I expect that we will want to link to this from the JBoss Wiki
somewhere, and perhaps even from jboss.org/tools/ ? Discuss.
We could also list JBoss Tools core projects here, too, if we want to
start treating some (or all) of those projects as independent content
producers too.
(For the curious, this documentation effort grew out of a discussion
Paul, Rob, Max, & I had on Thursday. Goal is to centralize the pertinent
information related to what's in JBTIS, who to contact, and where to
find sources & binaries when it's
aggregation/integration/coordination/productization time. It's a bit
like what's done here [1, 2, 3], but on a smaller scale.)
[1] http://wiki.eclipse.org/Ganymede/Signoffs
[2] http://wiki.eclipse.org/Helios/Participating_Projects
[3] http://www.eclipse.org/projects/releases/releases.php?release=kepler
Cheers,
Nick
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 1 month
