November 2012 - jdf-dev - Jboss List Archives

[JBoss JIRA] (JDF-152) Modify existing helloworld-mdb quickstart to demonstrate JMS Topics in addition to JMS Queues

by Sande Gilda (JIRA)

Sande Gilda created JDF-152: ------------------------------- Summary: Modify existing helloworld-mdb quickstart to demonstrate JMS Topics in addition to JMS Queues Key: JDF-152 URL: https://issues.jboss.org/browse/JDF-152 Project: JBoss Developer Framework Issue Type: Enhancement Components: quickstarts Reporter: Sande Gilda The helloworld-mdg quickstart currently demonstrates JMS Queues. It would be nice to add code to demonstrate JMS Topics as well. -- 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

11 years, 5 months

2
8
0 / 0

Re: [jdf-dev] 20 minute JBDS Demo with OpenShift Enterprise/OnPremise

by Fred Bricon

Damn, the project still fails to build when you choose an enterprise server. The archetype is really borked :-( For your demo, either : - you stick with the community bits, it builds normally - the JDF team rollbacks the archetype to version M5, so you can play with both community & enterprise versions - the Aerogear team releases a working M7 version *now* and the JDF team updates the stacks.yml Regards, Fred Bricon Le mardi 13 novembre 2012 22:28:57, Burr Sutter a écrit : > Thank you - I will be able to test late tonight or tomorrow morning. > > JBDS6 does not run on my mac so I have to get back to my Windows machine to test. > > > On Nov 13, 2012, at 3:36 PM, Fred Bricon wrote: > >> As a temporary workaround, I disabled the arq-jbossas-remote profile on project creation . Created html5 project now builds OOTB... until you manually activate that profile. >> Please refresh the project examples section in JBoss Central or restart your workspace. >> >> Le mardi 13 novembre 2012 18:41:32, Burr Sutter a écrit : >>> Thanks! >>> >>> On Nov 13, 2012, at 12:35 PM, Fred Bricon wrote: >>> >>>> I'm stuck with the kids for the next 3hrs. After that, it'll take me 10 min to get it fixed. >>>> >>>> Le mardi 13 novembre 2012 16:05:57, Burr Sutter a écrit : >>>>> How quickly could this get fixed for me? I have a demo this Thursday but currently unable to use JBDS6 due to this one bug. >>>>> >>>>> There may be other bugs behind this one - JBDS6 is not the most "stable" but the HTML5 archetype is a show-stopper for me right now. >>>>> >>>>> It fails for AS7 and EAP6 - and I won't be able to "stop the recording", fix the problem and restart the recording. >>>>> >>>>> >>>>> On Nov 13, 2012, at 9:53 AM, Fred Bricon wrote: >>>>> >>>>>> Le mardi 13 novembre 2012 15:22:02, Burr Sutter a écrit : >>>>>>> Is that a server-side fix? Or something that requires a new build/update? >>>>>> Server side :-) >>>>>> >>>>>>> >>>>>>> On Nov 13, 2012, at 6:37 AM, Fred Bricon wrote: >>>>>>> >>>>>>>> Le lundi 12 novembre 2012 17:38:38, Max Rydahl Andersen a écrit : >>>>>>>>> Hey Fred/Snjezana, >>>>>>>>> >>>>>>>>> Burr pointed me to JBIDE-12987 which indicates the html5 archetype currently deployed in JBDS is broken. >>>>>>>>> >>>>>>>>> Shit happens - but I Would like to be sure to understand where the culprit is. >>>>>>>>> >>>>>>>>> Did this issue happen because: >>>>>>>>> >>>>>>>>> A) we added an archetype without testing it to projectexamples.xml >>>>>>>>> >>>>>>>>> B) the jdf-stack side is referring to a broken html5 archetype ? >>>>>>>>> >>>>>>>> Yes. Actually the archetype referenced in stacks.yml is broken when you activate the arq-jbossas-remote profile and you're in enterprise mode. >>>>>>>> The profile activation is done in projectexample.xm, which means we can decide to, temporarily, not activate that profile when creating the project. All we need is updating that example descriptor. >>>>>>>> We'd turn the profile back on once a fixed archetype is referenced in stacks >>>>>>>> >>>>>>>>> >>>>>>>>> ...in both cases we need to improve our reaction/QA work on this (we as in jboss wide - not just us from tools) >>>>>>>>> >>>>>>>>> Before I hunt down the rightful owner could you enlighten me on wether its A or B from above ? (and if you got other info why it stopped working and suggestion to avoid it would be great) >>>>>>>>> >>>>>>>>> /max >>>>>>>>> >>>>>>>>> ----- Original Message ----- >>>>>>>>>> unfortunately I am too busy multi-tasking to really nail this done. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The HTML5 archetype on JBoss Central in JBDS6 is broken which is >>>>>>>>>> pretty critical to my demos as well. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> https://issues.jboss.org/browse/JBIDE-12987 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Nov 12, 2012, at 11:21 AM, André Dietisheim wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 11/12/2012 04:24 PM, Burr Sutter wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I seem to get a number of "would you like to wait" messages. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> so you get these when the wizard reports it's waiting for the app to >>>>>>>>>> become ready? if yes, then this is utterly weird. Applications >>>>>>>>>> should follow the naming scheme: >>>>>>>>>> >>>>>>>>>> http://<application-name>-<domainname>.rhcloud.com >>>>>>>>>> >>>>>>>>>> So if you put openshift.redhat.com to your hosts file, then resolving >>>>>>>>>> your apps should not get affected. Can you provide any further >>>>>>>>>> insights/details? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Nov 12, 2012, at 3:33 AM, André Dietisheim wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 11/11/2012 08:17 PM, Burr Sutter wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> This seems to not be working for me >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> what are the symptoms? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> You could alternatively run a liveCD in localhost and have some more >>>>>>>>>> funky hosts entry. The drawback is that the default liveCD does no >>>>>>>>>> dynamic DNS-update so you'd have to add you app-namees into hosts, >>>>>>>>>> too. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> - for now I will simply try to get JBDS6 to work with OpenShift >>>>>>>>>> Hosted. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> And if that acts up, fall back to JBDS5 + OpenShift Hosted - and >>>>>>>>>> hopefully the audience won't "see" it. :-) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> This is a pre-recorded demo/webinar and I am not sure if there is >>>>>>>>>> even a live Q&A after the session. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Nov 8, 2012, at 5:20 AM, André Dietisheim wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 11/06/2012 05:26 PM, Burr Sutter wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I have to script, test and record a 20 minute demo of JBDS (ideally >>>>>>>>>> 6) with OSE next week (around Nov 14 or 15) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 1) My plan is to use one of the hosted versions of OpenShift like >>>>>>>>>> openshift.redhat.com or int.openshift.redhat.com and perhaps play >>>>>>>>>> some games with the hosts file on my Windows machine - do make it >>>>>>>>>> look like " openshift.mycompany.com " or something like that, what >>>>>>>>>> do you think - might that work? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> so yes it works when using some funky hack in hosts: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I added "54.243.111.12 openshift.local" to my hosts file and things >>>>>>>>>> worked fine. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2) Do you have a document that describes how to setup and debug? With >>>>>>>>>> 20 minutes, I will likely have enough time to show off debugging in >>>>>>>>>> the cloud >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 3) What would you say are the most critical things to show? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Here is my list: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> a- Using the HTML5 archetype for JBoss Central >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> b- Displayed in Mobile Browser Sim >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> c- Might even consider making an edit to the screen to so the viewer >>>>>>>>>> sees some "coding" >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> d- Assuming my account is already pre-established, will use the >>>>>>>>>> OpenShift Wizard on JBoss Central to push up my app - I will need >>>>>>>>>> things to talk about while waiting - I will use a pre-establised >>>>>>>>>> account because OSE has not yet figured out how they will enlist new >>>>>>>>>> developers - it won't be like the current self-provisioning model >>>>>>>>>> which creates a RHN account. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> e- Now the app is "up in the cloud" - perhaps hit it with a real >>>>>>>>>> mobile device (I have a special camera for that) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> f- Add a debug break point and step through some things in the HTML5 >>>>>>>>>> kitchensink app...in the cloud >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> g- I would love to show "auto-scaling" but I am not sure how to make >>>>>>>>>> that work - or if anyone has every demo'd that before >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> h- show off remote log access via OpenShift Explorer >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> what else? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >

11 years, 5 months

6
13
0 / 0

[JBoss JIRA] (JDF-115) http://www.jboss.org/jdf/examples/ticket-monster/tutorial/DataPersistence

by Pete Muir (JIRA)

Pete Muir created JDF-115: ----------------------------- Summary: http://www.jboss.org/jdf/examples/ticket-monster/tutorial/DataPersistence Key: JDF-115 URL: https://issues.jboss.org/browse/JDF-115 Project: JBoss Developer Framework Issue Type: Bug Affects Versions: 1.0.5.Final Reporter: Pete Muir Fix For: 2.0.0.Final Tutorial refers to TicketPriceCategory which no longer exists (replaced with TicketCategory) -- 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

11 years, 5 months

3
3
0 / 0

Re: [jdf-dev] Looking for volunteers for new quickstarts

by Sande Gilda

Hi Bernard, That is why I suggested you grab the JIRA describing the quickstart if you are interested in working on one of them. Once the JIRA is assigned to you, it's yours! The only request that did not have a JIRA was the enhancement to the existing helloworld-mdb quickstart. I created JDF-152 for that on to be consistent with the others. If you are not able to grab the JIRA, let me know and I will grab it in your name. The following URL should provide the list currently available quickstarts: https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=p... Thanks, Sande On 11/15/2012 11:44 AM, Bernard Tison wrote: > On 11/14/2012 09:20 PM, Sande Gilda wrote: >> Hi everyone, >> >> As you know, the quickstarts have received a lot of attention and seem >> to be a big hit. If you thought you missed your opportunity to help out, >> you are wrong. We have a growing list of new quickstarts that would be >> extremely useful to our customers. If you choose to contribute, not only >> do you get the satisfaction of knowing you are making JBoss developers' >> lives easier, but you get celebrity status as author of the quickstart! >> >> The following list of JIRAs describe the quickstarts we need. If you see >> one that looks interesting, please feel free to grab the JIRA. If you >> don't have access, send me an email and I will grab it for you. >> >> JDF-37 Provide a JAAS quickstart >> JDF-46 Clustered JMS quickstart >> JDF-131 Provide a MBean quickstart >> JDF-137 Add OSGi war quickstart >> JDF-138 Create a quickstart demonstrating a custom CDI context and >> scope >> JDF-140 Create a quickstart demonstrating CDI alternatives >> JDF-141 Create a quickstart demonstrating CDI Stereotypes >> JDF-142 Create a quickstart demonstrating CDI Decorators >> JDF-143 Create a quickstart demonstrating CDI Interceptors >> JDF-144 Create a quick start using the deltaspike property >> configuration >> JDF-145 Create a quickstart using deltaspike's exception handling >> JDF-146 Add Deltaspike version of kitchensink that shows how to use >> @Transactional >> JDF-147 Upgrade i8ln quickstarts to use DeltaSpike i8ln >> JDF-148 Add a quickstart showing how to create new beans using DS >> utilities >> JDF-149 Add a quickstart that shows how to use DeltaSpike >> BeanManagerProvider to access CDI in a EntityListener >> JDF-150 Add a quickstart that shows how to use @TransactionScoped >> >> If none in the list above appeals to you, we also have an existing >> 'helloword-mdb' example that currently demonstrates JMS Queues. It would >> be great to enhance it to demonstrate JMS Topics as well. >> >> Information about the current quickstarts can be found here: >> http://site-jdf.rhcloud.com/quickstarts/get-started/ >> The source code for the current quickstarts is here: >> https://github.com/jboss-jdf/jboss-as-quickstart/ >> Information about contributing a quickstart is here: >> http://site-jdf.rhcloud.com/about/contributing/ >> >> Please let me know if you need any more information or have any >> questions. >> > Hi Sande, > > Are you coordinating who is working on what? This in order to avoid > you get multiple pull-requests for the same quickstart. > > Bernard >

11 years, 5 months

1
0
0 / 0

New Quickstarts Needed :-)

by Pete Muir

Hi all Jason and I went through and updated the list of quickstarts we want to add to JDF. https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=p... There are a few more to add around OSGi, but I'm waiting for Thomas to get back to me. If you are interested in picking up some of these, then please drop me an email, and I'll assign the issue to you (or, if you can already assign it to yourself, then please do!). Thanks! Pete

11 years, 5 months

3
3
0 / 0

Spring WebsphereMQ quickstart

by Sande Gilda

Hi everyone, Doug submitted a quickstart that demonstrates IBM's WebSphere MQ messaging and Spring JMS. it's a very nice example, but I 'm don't think it is a good candidate for a quickstart. While we ship other quickstarts that are dependent on 3rd party software, currently we only include those where the 3rd party software is freely downloadable and fairly simple to configure. My concern with this quickstart is that even though you can get an evaluation copy for free, it is short term and doesn't allow us to test this quickstart over numerous releases. Also, WebSphere MQ requires setup and configuration and I really don't think we want to support this in a quickstart. I also don't know how we could set up automated tests for it. I would prefer to see this written up on confluence, docspace, or as a support document, although I think it needs more detailed instructions. You can view the pull here: https://github.com/jboss-jdf/jboss-as-quickstart/pull/356 What does everyone else think about this? Thanks, Sande

11 years, 5 months

2
1
0 / 0

QA process of RichFaces Kitchensink archetypes

by Brian Leathem

Hello all, We've released an updated the RichFaces Kitchensink Archetype (version 4.2.3.Final-1), it is currently in a staging repository [1]. RichFaces QE has verified the archetype works as expected, but verification with JBoss tools is still outstanding. To kick off this final piece of QA, I've created a pull-request updating the JDF stack.yaml file [2], referenced that PR from JDF-151 [3], and created the corresponding JBIDE-13059 [4] issue to verify the behavior when the archetype is invoked from JBoss tools. Any thoughts on how we can optimize this process? One possibility is to create the stacks.yaml PR ask the RF QE team to do an initial verification that the archetype/yaml changes aren't visibly breaking, then at that point hand off the issue to the JBIDE QA team for further verification. Any other suggestions for improving this process would be appreciated. Brian Leathem (RichFaces Project Lead) [1] https://repository.jboss.org/nexus/content/groups/staging/org/richfaces/a... [2] https://github.com/jboss-jdf/jdf-stack/pull/3 [ 3] https://issues.jboss.org/browse/JDF-151 [4] https://issues.jboss.org/browse/JBIDE-13059

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-128) Patches for ticket monster app don't apply

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created JDF-128: ------------------------------------- Summary: Patches for ticket monster app don't apply Key: JDF-128 URL: https://issues.jboss.org/browse/JDF-128 Project: JBoss Developer Framework Issue Type: Feature Request Components: ticket-monster Reporter: Hardy Ferentschik Assignee: Marius Bogoevici When running the _admin_layer.fsh_ script, one gets asked to apply a bunch of patched. None of the patches applies cleanly: {noformat} ... ? Apply manual functional changes described in tutorial? [Y/n] Applying manual changes described in tutorial based on admin_layer_functional.patch error: patch failed: demo/src/main/webapp/index.xhtml:1 error: demo/src/main/webapp/index.xhtml: patch does not apply ? Apply manual fixes for FORGE-587,FORGE-589? [Y/n] y Applying manual fixes for FORGE-587,FORGE-589 based on admin_layer_fixes.patch error: patch failed: demo/src/main/webapp/admin/booking/search.xhtml:25 error: demo/src/main/webapp/admin/booking/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/event/search.xhtml:25 error: demo/src/main/webapp/admin/event/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/eventCategory/search.xhtml:25 error: demo/src/main/webapp/admin/eventCategory/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/mediaItem/search.xhtml:25 error: demo/src/main/webapp/admin/mediaItem/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/performance/search.xhtml:25 error: demo/src/main/webapp/admin/performance/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/section/search.xhtml:26 error: demo/src/main/webapp/admin/section/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/show/search.xhtml:25 error: demo/src/main/webapp/admin/show/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/ticketCategory/search.xhtml:25 error: demo/src/main/webapp/admin/ticketCategory/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/ticketPrice/search.xhtml:25 error: demo/src/main/webapp/admin/ticketPrice/search.xhtml: patch does not apply error: patch failed: demo/src/main/webapp/admin/venue/search.xhtml:26 error: demo/src/main/webapp/admin/venue/search.xhtml: patch does not apply ? Apply manual visual changes? [Y/n] Applying manual visual changes based on admin_layer_graphics.patch error: demo/src/main/webapp/admin/index.xhtml: No such file or directory demo/admin_layer_graphics.patch:1124: new blank line at EOF. + error: the patch applies to 'demo/src/main/webapp/resources/forge-logo.png' (021a4735ea8a5cd4e442bcc823d0d18bb424146f), which does not match the current contents. error: demo/src/main/webapp/resources/forge-logo.png: patch does not apply error: patch failed: demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml:7 error: demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml: patch does not apply ? Deploy to JBoss AS 7? [Y/n] n ... {noformat} Why are there even patches required. Should the tip of the repo not always work out of the box? -- 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

11 years, 5 months

3
7
0 / 0

[JBoss JIRA] (JDF-139) OSGi in an EAR quickstart

by Pete Muir (JIRA)

Pete Muir created JDF-139: ----------------------------- Summary: OSGi in an EAR quickstart Key: JDF-139 URL: https://issues.jboss.org/browse/JDF-139 Project: JBoss Developer Framework Issue Type: Feature Request Reporter: Pete Muir Add a quickstart that shows how to use OSGi in an EAR -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-123) Rename module folders to match their artifacId

by Fred Bricon (JIRA)

Fred Bricon created JDF-123: ------------------------------- Summary: Rename module folders to match their artifacId Key: JDF-123 URL: https://issues.jboss.org/browse/JDF-123 Project: JBoss Developer Framework Issue Type: Feature Request Components: quickstarts Reporter: Fred Bricon As discussed on the JDF ML, the module folder names need to be renamed to match their artifact id, so that Eclipse WTP based tooling (JBoss Tools/ JBDS) can deploy the webapps using the proper context root. I created the following PR where all the rename as been done https://github.com/jboss-jdf/jboss-as-quickstart/pull/347 The PR contains one [commit|https://github.com/fbricon/jboss-as-quickstart/commit/59ae6033c55e...] fixing a bug preventing building the quickstarts when the EAP repo is not available. It was crucial for me to fix it before testing the rest of my changes. If, for some reason, you'd like to delay the rename, then you should : * cherry-pick https://github.com/fbricon/jboss-as-quickstart/commit/cda4fe8bf434b2e3b22... and : * run "groovy rename" in the root folder (yeah I'm on Windows, groovy is my best shot at scripting stuff, so you need to have [groovy installed|http://groovy.codehaus.org/Download?nc]) -- 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

11 years, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

jdf-dev November 2012