March 2013 - jbosstools-dev - Jboss List Archives

Re: [jbosstools-dev] [jbosstools-base] JBIDE-13797 fix for delay method to handle tests core mode execution (#65)

by Rob Stryker

Hey Denis: Does this fix the issues with AS Test Suite when run headless? - Rob On 03/16/2013 07:20 AM, Denis Golovin wrote: > ------------------------------------------------------------------------ > > > You can merge this Pull Request by running > > git pull https://github.com/dgolovin/jbosstools-base JBIDE-13797 > > Or view, comment on, or merge it at: > > https://github.com/jbosstools/jbosstools-base/pull/65 > > > Commit Summary > > * JobUtils.delay method problem in core tests > > > File Changes > > * *M* > tests/plugins/org.jboss.tools.tests/src/org/jboss/tools/test/util/JobUtils.java > <https://github.com/jbosstools/jbosstools-base/pull/65/files#diff-0> > (11) > > > Patch Links: > > * https://github.com/jbosstools/jbosstools-base/pull/65.patch > * https://github.com/jbosstools/jbosstools-base/pull/65.diff >

11 years, 1 month

1
0
0 / 0

Fwd: [eclipse-dev] Heads up .... a change to Eclipse Platform's traditional milestone composite repository coming for M6

by Max Rydahl Andersen

Thought this was worth sharing - i'm not sure if we will be affected by it but I could imagine our target platform and/or product builds might need a refresh to adjust for the changes coming in M6. /max ----- Forwarded message from David M Williams <david_williams(a)us.ibm.com> ----- >From: David M Williams <david_williams(a)us.ibm.com> >To: eclipse-dev(a)eclipse.org, Eclipse Cross Project Issues <cross-project-issues-dev(a)eclipse.org> >Date: Thu, 14 Mar 2013 00:08:30 -0400 >Subject: [eclipse-dev] Heads up .... a change to Eclipse Platform's traditional milestone composite repository coming for M6 > >This note is primarily for those that build against the Eclipse Platform's >composite repository at .../eclipse/updates/4.3milestones after the >Platform milestone is delivered. While that's not a recommend practice, I >get the impression lots of people do it. For everyone else, you will just >find this information very interesting, I'm sure, but it will not effect >you directly. > >Traditionally, we leave each milestone "connected" to the composite. This >allows rolling back an installation. But, there has been so many changes >since M5, due to the build technology used and other changes since Juno >SR2, that we plan to provide only M6 at that composite site, for M6. This >will help "force" issues to appear, if there are any, rather than waiting >until the end of the release and then everyone being surprised. Many >details are in bug 395030 [1] > >Bug 395030 - Disconnect old milestone repos for M6 > >But, I'll summarize here: > >There are 6 or 12 changes related to things we intentionally removed, that >would be a factor regardless of the build technology used (such as the >"org.junit4" change many of you already discovered). > >There are 6 or 12 known issues related to things missing from the new >build that we plan to correct by M7 (mostly missing *.source bundles). > >But, there are several hundred changes related to the "low level" p2 IUs >(tooling* and *_root IUs) that are involved in building products or RCP >apps for specific platforms or Operating Systems. We are assuming that the >exact names of these IUs don't really matter to anyone, and that >everything needed really is there and working, just named differently ... >but ... that's the reason we plan on forcing the issue by providing only >M6 at that composite repo. More details are in the bug so you can read >ahead of time, but let us know, in that bug or a new one, if there are >issues encountered. We will of course leave the older repos (M1 to M5a) >around in case an "emergency work around" is needed for the milestone, but >we'll cross that bridge if or when we get to it. We expect things to go >smoothly, we just want to make sure. > >Thanks, > >[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=395030 >_______________________________________________ >eclipse-dev mailing list >eclipse-dev(a)eclipse.org >To change your delivery options, retrieve your password, or unsubscribe from this list, visit >https://dev.eclipse.org/mailman/listinfo/eclipse-dev ----- End forwarded message -----

11 years, 1 month

1
0
0 / 0

Bluetooth speaker Supply与您共享了相册。

by Bluetooth speaker Supply

Dear Sir or Madam, Wealth Land Electronics Co.,Ltd here. We specialize in electronic devices field with full experience and we have 100 % confidence in our technology and quality. Now our hot seller is bluetooth speaker . Bluetooth speaker is very morden product which can work with all bluetooth electronic device . Various shapes are available , It can offer you magical sound when you listen music . Make your life more enjoyable . If any interest, feel free to contact me. Best regards, Mr. Buick Sales Manager ELECTRONIC LIMITED https://picasaweb.google.com/lh/sredir?uname=104768384245631762184&target...

11 years, 1 month

1
0
0 / 0

Forge 1 in JBoss Tools/Developer Studio

by Max Rydahl Andersen

Hi, Koen have been working on Forge 1 wizards for JBoss Tools (since Forge 2 is not targeted to be ready before after our next major release). He have had great process but where the original plan was to create a set of Forge 1 based wizards (create project, create entity, scaffold etc.) we thought it was time to readjust what we want to do. Below is what came out from a meetup between Lincoln, Burr, Max, Koen and a few other attendees there to see the show :) 1) Koen will drop the current create project/entity individual wizards - they either duplicate existing functionallity in Eclipse or are not generating recommended project setup (especially for projects targeting enterprise/supported bits) - this saves time that can be used on making Forge 2 better in this area. 2) Koen will focus on making the reverse engineering of entities and scaffolding via Forge 1 be available via Wizards in JBoss Tools. The current wishlist is: * reverse engineer from a database (using hibernate tools forge plugin) * scaffold JSF * scaffold HTML5 * scaffold Rest services 3) Forge 2 should be improved to handle that during creation you might be targeting something else than just one specific version of the spec bom (i.e. EAP 6, EAP 7, AS7, AS8, Glassfish N etc. would need this anyway afaics) This is related to the work Raphael made for updating the used BOM's (http://www.jboss.org/jdf/stack/plugin-jdf/). Hope that clears up the picture for those been involved - if you got any questions or comments do let me or Koen know. Thanks, Max

11 years, 1 month

1
0
0 / 0

Settlement report 12 March 2013

by Western Union Holdings, Inc.

Dear AgentRef. 13 March 2013Please find enclosed your settlement report for the date indicated above. Please pay the amount due today.If you have any query, please contact your local Settlement Executive.Thank you for your co-operation.RegardsPlease do not reply to this unnatended e-mail address---------------Cher AgentVeuillez trouver ci-joint votre rapport de règlement pour la date indiquée ci-dessus. Veuillez nous remettre le montant du aujourdhui.Si vous avez besoin de renseignements supplémentaires, appelez votre Administrateur local.Merci de votre co-opération.Bien à vous--------------------------------------------Apreciable Agente,Ref. 13 March 2013Sírvase encontrar adjunto su reporte de cierre de la fecha arriba indicada.Favor de contactar a su representante de cuentas para cualquier pregunta adicional.Saludos) 2001-2013 Western Union Holdings, Inc.

11 years, 1 month

1
0
0 / 0

ACTION REQUIRED: 4.0.1 release delayed - please fix the tests!

by Max Rydahl Andersen

Hi guys, Nick posted below earlier - please take a look at these issues ASAP and open PR/jiras for them to get them fixed. These issues covers maven/central/as/hibernate/vpe/seam/javaee so its the full stack that needs a checkup. Please make this your priority to get fixed so we can get this release airborne. Thank you, Max On Mon, Mar 11, 2013 at 03:21:22AM -0400, Nick Boldt wrote: >The 401/601 builds are not happy w/ the updated 4.22.2 target platform [1]. > >Over the weekend numerous builds failed [2], so I'm not comfortable >releasing a CR1a build today. > >We need to decide if these tests can be fixed, or if the TP needs to >be rolled back to 1.2 / 0.16 [3]. > >Failing builds include: > >* central-maven-examples: test crash (SIGSEV, error code 134) in >org.jboss.tools.maven.configurators.tests, >org.jboss.tools.project.examples.test, org.jboss.tools.central.test > >* javaee: test failure, >org.jboss.tools.seam.core.test.SeamEARTest.testEarProject (from >org.jboss.tools.seam.core.test.SeamCoreAllTests) > >--- > >Additionally, these builds have been failing for several days: > >* hibernate: test timeout, org.hibernate.eclipse.console.test (last 5 >builds, since Mar 6) > >* server: test failure, org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[12] >(from org.jboss.tools.as.test.core.ASToolsTestSuite) (last 10 builds, >since Mar 1) > >* vpe: test timeout, org.jboss.tools.vpe.jsp.test (last 5 builds, >failing since Mar 5) > >--- > >[1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... > >[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > >[3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... > >-- >Nick Boldt :: JBoss by Red Hat >Productization Lead :: JBoss Tools & Dev Studio >http://nick.divbyzero.com >

11 years, 1 month

5
5
0 / 0

JBDS 7.0.0.Alpha1 on Early Access

by Nick Boldt

JBDS 7.0.0.Alpha1 Early Access installers are now available! https://devstudio.jboss.com/earlyaccess/ Note that bits may take a while to replicate from our staging server to publication. Please allow at least an hour before attempting to download them - if the page does not work, try again later before reporting a JIRA. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

JBoss Tools 4.1.0.Alpha1 is available

by Nick Boldt

JBoss Tools 4.1.0.Alpha1 is now available. This is a development release aimed at Eclipse Kepler (4.3 M5a) users. Update Sites: http://download.jboss.org/jbosstools/updates/development/kepler/ Installation + Download Pages: http://www.jboss.org/tools/download http://www.jboss.org/tools/download/dev/4_1 http://www.jboss.org/tools/download/installation/update_4_1 Requirement Sites: (These are loaded automatically into Eclipse when installing JBoss Tools from the URLs above. Provided here simply for reference.) http://download.jboss.org/jbosstools/updates/kepler/ http://download.jboss.org/jbosstools/updates/kepler/extras/ New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ --------- Project leads, please tag your projects! co jbosstools-4.1.0.Alpha1x git tag jbosstools-4.1.0.Alpha1 git push origin jbosstools-4.1.0.Alpha1 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
2
0 / 0

Location of esb / drools handler; which is 'live'?

by Rob Stryker

Hi: I'm trying to locate the repository used currently for esb / drools / etc. I've received links to two different github repositories, but they seem to contain overlapping non-subset lists of plugins. https://github.com/jbosstools/jbosstools-esb https://github.com/jbosstools/jbosstools-runtime-soa What I'm basically looking to do is get a dev-env up where I can test esb / drools usage of 'runtimes' in base. I am looking into refactoring small portions of it, specifically how nested runtimes are discovered and created, and I obviously want to make sure I don't break anything in the process. So I'm wondering what list of repos and source code I need to have and import into my workspace to test this stuff and ensure I don't break anything. It was my understanding that a move was underway between the two repositories, however Max has indicated he doesn't know the status, and so I'm left unsure what repos to test ;) - Rob Stryker breaker of all things.

11 years, 1 month

2
1
0 / 0

Enabled jboss.org new approach to jira/github integration

by Max Rydahl Andersen

I've enabled the tab integration that is described at https://community.jboss.org/en/website/blog/2013/03/11/new-way-to-show-gi... on all repos in @jbosstools github organization. I've enabled the "magic" jira management from git commits on jbosstools-documentation repo and will give it a go and if it works well enable it on any other repo where the maintainer is ok with having this enabled. (i'm just using the jbosstools-documentation as a test since i'm going to push a few to that later today) The magic is described at https://confluence.atlassian.com/display/AOD/Processing+JIRA+issues+with+... and allows you to do this: $ git checkout -b JBIDE-1233 $ <do changes> $ git commit -m "JBIDE-1233 #resolve fix that issue by sprinkling magic dust on the bug" $ <do the proper git rebase/pull as needed> $ git checkout master $ git merge JBIDE-1233 $ git push origin Now JBIDE-1233 will get resolved with the commend "fix that issue by sprinkling magic dust on the bug"" I'll let you know how it goes - but do let me know if this git magic is something you would want enabled for the repos or not (you can read about limitations etc. in the docs above) p.s. it might be a while before you will see the tabs/issues show up since jira needs to index the full history first. /max

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev March 2013