January 2013 - jbosstools-dev - Jboss List Archives

FYI: New JBT/JBDS Target Platforms for Kepler M4, Juno R and Juno SR0 (M5 and SR2 coming next month)

by Nick Boldt

On 01/23/2013 01:49 AM, Nick Boldt wrote: > After much refactoring, renaming, reorganizing, and (hopefully soon) > publishing to a github repo, we have 3 new target platforms for use with > builds. > > These have as yet NOT been coupled up into the parent poms for the > 40x/60x and 41x/70x streams so that you can have some time to try them > out. How do you use them? Via a standard maven build, but passing in > this additional flag: > > > mvn clean install ... -DTARGET_PLATFORM_VERSION=4.20.5.Final-SNAPSHOT > > Changes to the previous target platforms (other than refactoring [5] and > migration to a new github repo [6]) include the removal of source and > sdk features [7], so these are slimmer and trimmer than their > predecessors, previously referred to as JunoSR0c and JunoSR1a. > > The new TPs, rather than being named for an Eclipse release train, will > now be named for the version of Eclipse included therein. > > Thus: > > * JunoSR0c (the 4th iteration) would be called 4.20.4.Final-SNAPSHOT > * JunoSR1a (the 2nd iteration) would be called 4.21.2.Final-SNAPSHOT > > Therefore the new target platforms are: > > * 4.20.5.Final-SNAPSHOT > * 4.21.3.Final-SNAPSHOT > * 4.30.0.Alpha1-SNAPSHOT > > These are available here for JBT [1] and JBDS [2]: > > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ > [2] > http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ > > They are also mirrored for use with Jenkins - see settings.xml [3] for > details. > > [3] > https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/settings/hudson-s... > > > All the TPs are being built with a single job [9], which next month will > grow to include target platforms for Juno SR2 (4.22.0.Final-SNAPSHOT) > and Kepler M5 (4.30.1.Alpha1-SNAPSHOT). > > [9] > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... > > > Publishing to the JBoss Nexus snapshots repo is now done to this path > [4], under which you'll now see jbdevstudio-multiple, > jbdevstudio-unified, jbosstools-multiple, & jbosstools-unified. We are > still making a distinction between multiple.target, which includes > multiple URLs, and unified.target, which points to the single unified > URL to which the TP is published ([1] or [2] above). > > [4] > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > > > If you have any questions or comments, please post them here [5], [6], > [7], [8], or reply to this thread. > > [5] https://issues.jboss.org/browse/JBIDE-13232 (refactor/rename/reorg) > [6] https://issues.jboss.org/browse/JBIDE-13386 (create new github repo) > [7] https://issues.jboss.org/browse/JBIDE-13329 (remove sources) > [8] https://issues.jboss.org/browse/JBIDE-13408 (remove SNAPSHOT suffix) > -------- Original Message -------- Subject: Re: New JBT/JBDS Target Platforms for Kepler M4, Juno R and Juno SR0 (M5 and SR2 coming next month) Date: Wed, 23 Jan 2013 14:01:27 -0500 From: Nick Boldt <nboldt(a)redhat.com> Due to the GAV refactoring you may run into a problem using the new TPs in their current form w/o patching [1] & rebuilding the parent pom. "Failed to resolve target definition /home/nboldt/.m2/repository/org/jboss/tools/target-platforms/jbdevstudio/unified/4.30.0.Alpha1-SNAPSHOT/unified-4.30.0.Alpha1-SNAPSHOT-unified.target" "Failed to load metadata repository from location http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4..." [1] https://issues.jboss.org/secure/attachment/12360088/12360088_JBIDE13232.p... --- HOWEVER, you can use @mistria's version of the bits (older GAV & URLs, same content) w/o hacking the parent pom like this: > mvn clean install ... -DTARGET_PLATFORM_VERSION=4.2.0.c-SNAPSHOT -U > mvn clean install ... -DTARGET_PLATFORM_VERSION=4.2.1.a-SNAPSHOT -U > mvn clean install ... -DTARGET_PLATFORM_VERSION=4.3.0.M4-SNAPSHOT -U Soon, I'll be switching the parent pom in 40x and master branches to use the new GAV path /org/jboss/tools/targetplatforms/jbdevstudio-unified/ instead of /org/jboss/tools/target-platforms/jbdevstudio/unified/, which will make the old TPs unusable. Stay tuned! -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 10 months

3
2
0 / 0

jbosstools-integration-stack repo

by Max Rydahl Andersen

> ps. Just an FYI - I've got the Jenkins/hudson composite promote job functioning (to .../integration/...). If at some point I can get > > https://github.com/jbosstools/jbosstools-integration-stack > > repo created that I could push to I could move my proto over and have more people play with it. Hey Paul, https://github.com/jbosstools/jbosstools-integration-stack is now created. Lets review soon where things should go when publishing and what names to use so we got that down and avoid too much confusion ;) Too all others: https://github.com/jbosstools/jbosstools-integration-stack will contain the work done for jbosstools integration stack to composite/aggregate what previously been known as the SOA tools. Once we got something more stable/sanitized we'll post more info. Thanks, /max

10 years, 10 months

1
0
0 / 0

JBossEAP5ExtendedProperties is missing in jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core

by Denis Golovin

Rob, jbosstools-server/master branch has compilation problems because of missing class (see subject). Could you fix that? Thanks Denis

10 years, 10 months

1
0
0 / 0

Cheatsheets in JBT

by Brian Fitzpatrick

Hey folks, I'm investigating potentially adding some cheatsheets to the SwitchYard Editor. Do we have any good examples of Cheatsheets currently in JBT or are there any extensions in JBT that I can take advantage of? And how do we hook these quickstarts or cheatsheets then into JBoss Central? I'm guessing that some of it is documented already, so if you have links I'd love to see them! Thanks in advance! --Fitz _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat

10 years, 10 months

4
7
0 / 0

New JBoss Tools Target Platforms for Kepler M4, Juno R and Juno SR0 (M5 and SR2 coming next month)

by Nick Boldt

After much refactoring, renaming, reorganizing, and (hopefully soon) publishing to a github repo, we have 3 new target platforms for use with builds. These have as yet NOT been coupled up into the parent poms for the 40x/60x and 41x/70x streams so that you can have some time to try them out. How do you use them? Via a standard maven build, but passing in this additional flag: > mvn clean install ... -DTARGET_PLATFORM_VERSION=4.20.5.Final-SNAPSHOT Changes to the previous target platforms (other than refactoring [5] and migration to a new github repo [6]) include the removal of source and sdk features [7], so these are slimmer and trimmer than their predecessors, previously referred to as JunoSR0c and JunoSR1a. The new TPs, rather than being named for an Eclipse release train, will now be named for the version of Eclipse included therein. Thus: * JunoSR0c (the 4th iteration) would be called 4.20.4.Final-SNAPSHOT * JunoSR1a (the 2nd iteration) would be called 4.21.2.Final-SNAPSHOT Therefore the new target platforms are: * 4.20.5.Final-SNAPSHOT * 4.21.3.Final-SNAPSHOT * 4.30.0.Alpha1-SNAPSHOT These are available here [1]: [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ All the TPs are being built with a single job, which next month will grow to include target platforms for Juno SR2 (4.22.0.Final-SNAPSHOT) and Kepler M5 (4.30.1.Alpha1-SNAPSHOT). Publishing to the JBoss Nexus snapshots repo is now done to this path [4], under which you'll now see jbosstools-multiple, jbosstools-unified. We are still making a distinction between multiple.target, which includes multiple URLs, and unified.target, which points to the single unified URL to which the TP is published ([1] above). [4] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... If you have any questions or comments, please post them here [5], [6], [7], [8], or reply to this thread. [5] https://issues.jboss.org/browse/JBIDE-13232 (refactor/rename/reorg) [6] https://issues.jboss.org/browse/JBIDE-13386 (create new github repo) [7] https://issues.jboss.org/browse/JBIDE-13329 (remove sources) [8] https://issues.jboss.org/browse/JBIDE-13408 (remove SNAPSHOT suffix) -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 10 months

1
0
0 / 0

ORDER NOW

by Shirley＠rugsource.localdomain

Dear Supplier, We are interested in buying your products. Kindly get back to us with your quotation which should include price, MOQ, payment terms and the time of delivery. Your prompt response will be highly appreciated. Best Regards, Shirley

10 years, 10 months

1
0
0 / 0

Re: [jbosstools-dev] Building coretests for 4.0.juno

by Nick Boldt

I've kicked off the job (which was disabled around Dec 5 when we finished JBT 4.0.0 / JBDS 6.0.0). Did you push changes into that stream which will be picked up by the job? On 01/11/2013 03:02 AM, Andrej Podhradsky wrote: > Hi Nick, > > could you do this also for 4.0.juno, please? > Because http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/p... doesn't contain org.jboss.tools.ui.bot.ext > which we need for running bot tests. > > Andrej. > > ----- Original Message ----- > From: "Nick Boldt" <nboldt(a)redhat.com> > To: "Andrej Podhradsky" <apodhrad(a)redhat.com> > Sent: Wednesday, January 2, 2013 4:33:48 PM > Subject: Re: Commiting into jbosstools-3.3.x > > http://download.jboss.org/jbosstools/updates/nightly/coretests/3.3.indigo/ > was updated Dec 20 and will respin via this job [1] shortly after you > commit anything for which it sees it needs to respin, or if you kick it > yourself [2]. > > [1] > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... > [2] > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... > > On 01/02/2013 04:56 AM, Andrej Podhradsky wrote: >> Hi Nick, >> >> I'm wondering if it is possible to commit some changes into http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x >> The reason is that I want to create some bot tests based on Eclipse Indigo (Fuse IDE [1]) but there is a problem which is described at >> >> https://issues.jboss.org/browse/JBIDE-13334 >> >> If yes, could you also update org.jboss.tools.test.feature at http://download.jboss.org/jbosstools/updates/nightly/coretests/3.3.indigo please? >> >> [1] http://fusesource.com/products/fuse-ide/ >> >> Best Regards >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 10 months

2
5
0 / 0

Re: [jbosstools-dev] Deltaspike

by Viacheslav Kabanovich

Hi Jaroslav > Note, I am using deltaspike 0.4 incubation version. May this be a problem? Yes, our tool supports 0.3 incubation version. In version 0.4, class implementing Extension interface is moved from org.apache.deltaspike.security.impl.authorization.SecurityExtension to org.apache.deltaspike.security.impl.extension.SecurityExtension. That name is registered in META-INF/javax.enterprise.inject.spi.Extension. Best regards Slava Kabanovich On 01/21/2013 12:27 AM, Jaroslav Jankovic wrote: > Hi Slava, > > what triggers CDI Validator to work? I have performed all steps you've > provided but still no errors nor warnings. > > I have CDI enabled project with 4 deltaspike jars on its classpath > (core-api/impl, secure model-api/impl). What am I missing? > > Note, I am using deltaspike 0.4 incubation version. May this be a problem? > > J.J. > > On 01/15/2013 06:40 PM, Viacheslav Kabanovich wrote: >> >> >> >> -------- Original Message -------- >> Subject: Re: Deltaspike >> Date: Tue, 15 Jan 2013 09:32:03 -0800 >> From: Viacheslav Kabanovich <scabanovich(a)exadel.com> >> To: Jaroslav Jankovic <jjankovi(a)redhat.com> >> >> >> >> Hi Jaroslav >> >> Please look at test DeltaspikeValidationTest in plugin >> org.jboss.tools.cdi.deltaspike.core.test >> Method testSecurityValidation() tests all situations that our >> validation supports. It works with test project located at >> org.jboss.tools.cdi.deltaspike.core.test/projects/DeltaspikeCoreTest >> >> For example, in the last assert, it checks that error is added at >> method SecuredBean1.doSomething3() "No matching authorizer found for >> security binding type deltaspike.security.CustomSecurityBinding on >> method doSomething3" because there is no authorized method with >> binding CustomSecurityBinding(1). Class CustomAuthorizer declares >> five authorizer methods, but they do not match this binding. On the >> other hand two authorizer methods match SecuredBean1.doSomething2() >> so that another assert checks that there is error on that method >> "Ambiguous authorizers found for security binding type >> deltaspike.security.CustomSecurityBinding on method doSomething2" >> >> So, steps: >> 1. Annotation type for security binding >> @SecurityBindingType >> public @interface CustomSecurityBinding { >> int value() default 0; >> } >> >> 2. Class providing authorizing methods >> public class CustomAuthorizer { >> >> @Secures >> @CustomSecurityBinding(4) >> public boolean check() { >> return true; >> } >> >> @Secures >> @CustomSecurityBinding(4) >> public boolean check1() { >> return true; >> } >> >> @Secures // error - authorizer method should return boolean >> @CustomSecurityBinding2 >> public void check3() { >> } >> >> @Secures //error - authorizer method should have a binding annotation >> public boolean check4() { >> return true; >> } >> >> } >> >> 3. Class with security methods >> public class SecuredBean1 { >> >> @CustomSecurityBinding(4) // error - two authorizer methods match >> public SecuredBean1 doSomething2() { >> return null; >> } >> >> @CustomSecurityBinding(1) // error - no matching authorizer method >> public SecuredBean1 doSomething3() { >> return null; >> } >> } >> >> Best regards >> Slava Kabanovich >> >> On 01/15/2013 03:34 AM, Jaroslav Jankovic wrote: >>> Hi Slava, >>> >>> I am implementing integration tests for deltaspike. I have only one >>> problem - it is security model. >>> I cannot figure out circumstances under which specific validation >>> problems appear. I mean I have read all documentation about security >>> model in deltaspike I had found, but with no success. I have also >>> read your comment in https://issues.jboss.org/browse/JBIDE-11552, >>> but also no progress. >>> >>> Can you please provide me exact steps to simulate all security >>> validations situations supported for deltaspike? >>> >>> I would really appreciate it. >>> Thanks >>> >>> Best regards >>> Jaroslav Jankovic >> >> >> >

10 years, 10 months

1
0
0 / 0

How to import switchyard tools?

by Rob Stryker

Hi all: I've cloned the repo git://github.com/jboss-switchyard/tools.git but for some reason I can't import the projects. They contain no .project file, so I assume I must import them as a maven project? In a clean workspace, trying to import them as a maven project, the maven project importer wizard simply freezes. ANy ideas? If anyone's curious why I'm trying to import this, it's because the project structure was forked / cloned / adapted from the esb project, which, as we've all seen lately, has tons of problems associated with it. So I'd like to get the jump on cleaning up the switchyard project structure before it reaches 1.0, to help avoid a lot of these issues, and to make use of all of the recent additions to API available in webtools which the esb project has NOT been using at all. Anyway, any advice is definitely appreciated.

10 years, 10 months

5
5
0 / 0

JBoss Tools Core 3.3.2.CR4 bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR4.core/ http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR3.webtools/ (unchanged from last week) Builds: http://download.jboss.org/jbosstools/builds/development/3.3.2.CR4.core/20... http://download.jboss.org/jbosstools/builds/development/3.3.2.CR3.webtool... (unchanged from last week) JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR4.core/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 10 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev January 2013