December 2012 - jdf-dev - Jboss List Archives

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on JDF-172: ------------------------------- IMO we should always use binary deployment with TicketMonster due to the resources required for the GWT build (it's pretty slow to build on OpenShift even with a large gear). > Update TicketMonster tutorial to use JBDS for OpenShift deployment > ------------------------------------------------------------------ > > Key: JDF-172 > URL: https://issues.jboss.org/browse/JDF-172 > Project: JBoss Developer Framework > Issue Type: Task > Components: ticket-monster > Affects Versions: 2.0.0.Final > Reporter: Stefan Bunciak > Assignee: Marius Bogoevici > > We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way: > * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295 > * Binary deployment works, but there's no way to deploy it to application root: JBIDE-13296 > Once above jira issues are resolved, the TicketMonster tutorial should be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Stefan Bunciak updated JDF-172: ------------------------------- Description: We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way: * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295 * Binary deployment works, but there's no way to deploy it to application root: JBIDE-13296 Once above jira issues are resolved, the TicketMonster tutorial should be updated. was: We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way: * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295 * Binary deployment works, but there's no way to deploy it to application root: https://issues.jboss.org/browse/JBIDE-13296 Once above jira issues are resolved, the TicketMonster tutorial should be updated. > Update TicketMonster tutorial to use JBDS for OpenShift deployment > ------------------------------------------------------------------ > > Key: JDF-172 > URL: https://issues.jboss.org/browse/JDF-172 > Project: JBoss Developer Framework > Issue Type: Task > Components: ticket-monster > Affects Versions: 2.0.0.Final > Reporter: Stefan Bunciak > Assignee: Marius Bogoevici > > We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way: > * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295 > * Binary deployment works, but there's no way to deploy it to application root: JBIDE-13296 > Once above jira issues are resolved, the TicketMonster tutorial should be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Stefan Bunciak (JIRA)

Stefan Bunciak created JDF-172: ---------------------------------- Summary: Update TicketMonster tutorial to use JBDS for OpenShift deployment Key: JDF-172 URL: https://issues.jboss.org/browse/JDF-172 Project: JBoss Developer Framework Issue Type: Task Components: ticket-monster Affects Versions: 2.0.0.Final Reporter: Stefan Bunciak Assignee: Marius Bogoevici We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way: * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295 * Binary deployment works, but there's no way to deploy it to application root: https://issues.jboss.org/browse/JBIDE-13296 Once above jira issues are resolved, the TicketMonster tutorial should be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-171) Design errors on What Is Ticket WhatIsTicketMonsterMonster page

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JDF-171?page=com.atlassian.jira.plugin.sy... ] Vlado Pakan updated JDF-171: ---------------------------- Attachment: wrongLink.png tooLongLineNotWrapped.png mistypeError.png tooLongLineNnotWrapped.png screenshot is showing line which is very long and is not wrapped so looks ugly in web browser. Also it has two times character ` on places where it doesn't make sense probably it should be somehow interpreted by web browser but it's not working. > Design errors on What Is Ticket WhatIsTicketMonsterMonster page > --------------------------------------------------------------- > > Key: JDF-171 > URL: https://issues.jboss.org/browse/JDF-171 > Project: JBoss Developer Framework > Issue Type: Bug > Components: ticket-monster > Environment: Google Chrome > Reporter: Vlado Pakan > Assignee: Marius Bogoevici > Attachments: mistypeError.png, tooLongLineNotWrapped.png, wrongLink.png > > > There are design errors on page http://www.jboss.org/jdf/examples/ticket-monster/tutorial/WhatIsTicketMon... > See attached screenshots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-158) Add custom authorization example using @SecurityBindingType from DeltaSpike

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JDF-158?page=com.atlassian.jira.plugin.sy... ] Work on JDF-158 started by Rafael Benevides. > Add custom authorization example using @SecurityBindingType from DeltaSpike > --------------------------------------------------------------------------- > > Key: JDF-158 > URL: https://issues.jboss.org/browse/JDF-158 > Project: JBoss Developer Framework > Issue Type: Feature Request > Components: quickstarts > Reporter: Pete Muir > Assignee: Rafael Benevides > Labels: deltaspike > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-171) Design errors on What Is Ticket WhatIsTicketMonsterMonster page

by Vlado Pakan (JIRA)

Vlado Pakan created JDF-171: ------------------------------- Summary: Design errors on What Is Ticket WhatIsTicketMonsterMonster page Key: JDF-171 URL: https://issues.jboss.org/browse/JDF-171 Project: JBoss Developer Framework Issue Type: Bug Components: ticket-monster Environment: Google Chrome Reporter: Vlado Pakan Assignee: Marius Bogoevici There are design errors on page http://www.jboss.org/jdf/examples/ticket-monster/tutorial/WhatIsTicketMon... See attached screenshots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

Fwd: Re: Design of maven plugin to verify supported versions

by Rafael Benevides

Hi all, For the maven-dependency-checker plugin (more details bellow or at https://github.com/jboss/maven-dependency-checker ) we have 3 major features: 1. Detect unsupported dependency versions. 2. Detect api dependencies that should be relocated to corresponding jboss-spec artifacts 3. Provide an excludes configuration to tell the plugin to ignore things that the user is intentionally not using a supported version of - especially for cases where there is no supported version For feature #1 I basically check if the GAV version has the -redhat-N prefix but this is not working for all cases since there are many libraries that is supported and it's not rebuilt by Red Hat. One example is the Spring Sports Club in WFK. I would like suggestions how can this plugin check if GAV is a supported version. We can start thinking about having a properties file with this information, but the management cost of that seems too high. Maybe we can find an alternative way. I'm opened to suggestion. Thank you -------- Mensagem original -------- Assunto: Re: Design of maven plugin to verify supported versions Data: Wed, 14 Nov 2012 18:27:09 -0200 De: Rafael Benevides <benevides(a)redhat.com> Empresa: Red Hat Para: John Casey <jcasey(a)redhat.com> CC: Enterprise Maven Repo (Project Wolf) <enterprise-maven-list(a)redhat.com>, Pete Muir <pmuir(a)redhat.com> Hi all, Today, I pushed a new version of the maven-dependency-checker plugin with the following changes: 1 - The relocated dependencies is checked on groupId and artifactId of the declared dependency. So it's now possible to detect uses of example: org.glassfish.main:javax.ejb and propose the right relocate dependency 2 - Pete gave an excelent suggestion to check if a dependency has a BOM for it. So it uses the JBoss Stacks project (http://www.jboss.org/jdf/stack/stacks/) to discover all BOMs and them it looks for matches on the managed BOM dependencies and project dependencies. 3 - The Readme instructions was updated with instructions on how to use the plugin on command line without needing to add it on the project pom.xml. I believe that it's now ready to start using it. Thank you. Em 12-11-2012 11:44, Rafael Benevides escreveu: > The first functional version is available here: > https://github.com/rafabene/maven-dependency-checker > > Please, > > Feel free to provide any feedback. > > Cheers > > Em 08-11-2012 12:53, John Casey escreveu: >> I've started working with rbenevides on the Maven plugin we discussed >> yesterday. He's jumping into coding the first version, but I wanted >> to reflect the requirements we discussed on IRC so we can get feedback. >> >> Basically, it does three things: >> >> 1. Detect unsupported dependency versions. >> >> 2. Detect api dependencies that should be relocated to corresponding >> jboss-spec artifacts >> >> 3. Provide an excludes configuration to tell the plugin to ignore >> things that the user is intentionally not using a supported version >> of - especially for cases where there is no supported version >> >> >> For #1, it's not clear whether we need to be verifying that the >> dependencies used are from the same product release. If so, this will >> be a fair bit more complicated, as we'll need to download a product >> definition in terms of artifacts. >> >> Additionally, we would probably want to provide a flag to switch >> between WARN vs FAIL modes. >> >> For relocations, we're currently thinking of loading the list either >> from a maven artifact (type == properties, perhaps), or else from >> some Git repository. >> >> This is a fairly lightweight sketch, but are there any >> questions/concerns so far?

12 years

3
4
0 / 0

[JBoss JIRA] (JDF-148) Add a quickstart showing how to create new beans using DeltaSpike utilities

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/JDF-148?page=com.atlassian.jira.plugin.sy... ] Jason Porter commented on JDF-148: ---------------------------------- These are new types being shown in the aforementioned pull, not Beans. I think what Pete was originally thinking about was something along the lines as what Mark Procter is doing in Drools: https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main... > Add a quickstart showing how to create new beans using DeltaSpike utilities > --------------------------------------------------------------------------- > > Key: JDF-148 > URL: https://issues.jboss.org/browse/JDF-148 > Project: JBoss Developer Framework > Issue Type: Feature Request > Components: quickstarts > Reporter: Pete Muir > Assignee: Rafael Benevides > Labels: deltaspike > > This should show both BeanBuilder, AnnotatedTypeBuilder, AnnotationInstanceProvider (with member values) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JDF-148) Add a quickstart showing how to create new beans using DeltaSpike utilities

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JDF-148?page=com.atlassian.jira.plugin.sy... ] Rafael Benevides commented on JDF-148: -------------------------------------- I think that the pull request https://github.com/jboss-jdf/jboss-as-quickstart/pull/360 satisfies this issue. I'm not sure with we have a good, clear and didactical use case for BeanBuilder > Add a quickstart showing how to create new beans using DeltaSpike utilities > --------------------------------------------------------------------------- > > Key: JDF-148 > URL: https://issues.jboss.org/browse/JDF-148 > Project: JBoss Developer Framework > Issue Type: Feature Request > Components: quickstarts > Reporter: Pete Muir > Assignee: Rafael Benevides > Labels: deltaspike > > This should show both BeanBuilder, AnnotatedTypeBuilder, AnnotationInstanceProvider (with member values) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

developer environment ideas

by Jason Porter

Here are some ideas about the development environment we discussed on the hangout: IDE: Eclipse works, it's not my choice, but it works and JBDS has some great extensions Issue-tracker: Honestly not sure. JIRA works alright, YourKit is very good. Unfortunately there isn't a good OSS issue tracker that I'm aware of Static analysis: sonar and co work very well, however, findbugs and PMD have issues with EE especially around serialization Testing: Certainly the Arquillian universe. I think instead of plain unit tests we should push BDD ala spock. For support I believe Arquillian and Byteman make a great duo. I'll have to think about some others, but those are the initial thoughts

12 years

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

jdf-dev December 2012