October 2012 - jdf-dev - Jboss List Archives

[JBoss JIRA] (JDF-122) Kitchensink Archetype: can't insert a new member with name containg diacritics

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JDF-122?page=com.atlassian.jira.plugin.sy... ] Brian Leathem moved RF-12515 to JDF-122: ---------------------------------------- Project: JBoss Developer Framework (was: RichFaces) Key: JDF-122 (was: RF-12515) Affects Version/s: (was: 4.2.3.CR1) Component/s: (was: archetype) Security: (was: Public) > Kitchensink Archetype: can't insert a new member with name containg diacritics > ------------------------------------------------------------------------------ > > Key: JDF-122 > URL: https://issues.jboss.org/browse/JDF-122 > Project: JBoss Developer Framework > Issue Type: Bug > Reporter: Jan Papousek > > The bug is caused by [this regexp|https://github.com/richfaces/archetypes/blob/develop/kitchensink/s...]. -- 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, 5 months

1
0
0 / 0

Re: [jdf-dev] [jbosstools-dev] jboss

by Max Rydahl Andersen

> >> I don't quite understand why selective install can't be: >> >> 1) clone repo >> 2) offer user choice / have choice specified by JBDS >> 3) create project for just that directory >> >> ? >> >> Note that github allows you you to grab a zip of a tag, which means >> you can avoid the git clone... > > A great idea. It's been suggested twice now. Max? A zip of a tag is what you can already do, right ? Just point to a zip on an url as a straight up projectexample. Doesn't need anything specific git integration. I was considering the github integration one where you could actually get an example with history, branches,tags, option to do pull requests etc. afterwards. /max > >> >> On 9 Oct 2012, at 09:34, Max Rydahl Andersen wrote: >> >>> >>> On 09 Oct 2012, at 18:25, Snjezana Peco <snjezana.peco(a)redhat.com> >>> wrote: >>> >>>> It would be better to fix >>>> https://issues.jboss.org/browse/JBIDE-8452 >>>> That way, we would be able to create project examples from git as >>>> well as other project examples, select a branch, tag, add >>>> requirements/fixes... >>>> There are already a prototype for this issue >>>> (https://github.com/snjeza/jbossm2egit) that is necessary to >>>> upgrade to newer versions of m2e and EGit. >>> >>> Yes, but that wouldn't allow selective install either would it ? >>> and the issues below with the run-as would still be there. >>> >>> note: I still think JBIDE-8452 should happen but not sure it solves >>> the problem on its own ? >>> >>> /max >>> >>>> >>>> Snjeza >>>> >>>> On 9.10.2012 18:11, Fred Bricon wrote: >>>>> Le 09/10/2012 17:43, Sande Gilda a écrit : >>>>>> Fred, this looks really cool! >>>>> Yeah I know :-) >>>>>> I do have one question. You say "However our own JBoss AS server >>>>>> adapter ignores the WTP project context root and bases its >>>>>> deployment on the project name, leading to 404s as seen in the >>>>>> video below." Is this a bug with JBoss or something else? Is >>>>>> there a JIRA or Bugzilla for this? >>>>>> >>>>> See https://issues.jboss.org/browse/JBIDE-473 >>>>>> Pete, correct me if I'm wrong, but I believe the context root >>>>>> for the quickstarts was prefixed by jboss-as to make them >>>>>> unique and prevent them from overwriting existing deployments. >>>>>> for example "helloworld". It would be nice if the quickstarts >>>>>> worked the same way in JDBS as they do deployed in command >>>>>> line. >>>>>> >>>>> renaming the module directories to include the jboss-as prefix >>>>> would actually fix the problem. >>>>> >>>>>> >>>>>> On 10/09/2012 11:14 AM, Fred Bricon wrote: >>>>>>> Hi, >>>>>>> >>>>>>> we need to clean up the project examples in JBoss Tools >>>>>>> 4.0/JBDS 6.0 (as part of >>>>>>> https://issues.jboss.org/browse/JBIDE-12554). >>>>>>> So, my idea was to replace all the old examples with the >>>>>>> quickstarts from >>>>>>> https://github.com/jboss-jdf/jboss-as-quickstart >>>>>>> >>>>>>> Since the quickstarts are not available as standalone zips, for >>>>>>> consumption in JBT/JBDS, I created a script >>>>>>> (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) >>>>>>> that does that, and it also generates a project example stub >>>>>>> we can use almost directly in JBT. >>>>>>> >>>>>>> D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N >>>>>>> -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts >>>>>>> [INFO] Scanning for projects... >>>>>>> [INFO] >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] >>>>>>> [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ >>>>>>> jboss-as-quickstarts-parent --- >>>>>>> Starting zipping JBoss AS Quickstarts Parent modules >>>>>>> Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips >>>>>>> Zipped 51 quickstart modules >>>>>>> Generating project examples descriptor for JBoss Tools >>>>>>> [WARNING] module 'bmt' has a non matching artifactId >>>>>>> 'jboss-as-bmt' >>>>>>> [WARNING] module 'cdi-injection' has a non matching artifactId >>>>>>> 'jboss-as-cdi-injection' >>>>>>> [WARNING] module 'cdi-portable-extension' has a non matching >>>>>>> artifactId 'jboss-as-cdi-portable-extension' >>>>>>> [WARNING] module 'ejb-in-ear' has a non matching artifactId >>>>>>> 'jboss-as-ejb-in-ear' >>>>>>> [WARNING] module 'ejb-in-war' has a non matching artifactId >>>>>>> 'jboss-as-ejb-in-war' >>>>>>> [WARNING] module 'ejb-remote' has a non matching artifactId >>>>>>> 'jboss-as-ejb-remote-parent' >>>>>>> [WARNING] module 'ejb-security' has a non matching artifactId >>>>>>> 'jboss-as-ejb-security' >>>>>>> [WARNING] module 'greeter' has a non matching artifactId >>>>>>> 'jboss-as-greeter' >>>>>>> [WARNING] module 'helloworld' has a non matching artifactId >>>>>>> 'jboss-as-helloworld' >>>>>>> [WARNING] module 'helloworld-errai' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-errai' >>>>>>> [WARNING] module 'helloworld-gwt' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-gwt' >>>>>>> [WARNING] module 'helloworld-html5' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-html5' >>>>>>> [WARNING] module 'helloworld-jms' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-jms' >>>>>>> [WARNING] module 'helloworld-osgi' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-osgi' >>>>>>> [WARNING] module 'helloworld-rs' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-rs' >>>>>>> [WARNING] module 'helloworld-singleton' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-singleton' >>>>>>> [WARNING] module 'hibernate3' has a non matching artifactId >>>>>>> 'jboss-as-hibernate3' >>>>>>> [WARNING] module 'hibernate4' has a non matching artifactId >>>>>>> 'jboss-as-hibernate4' >>>>>>> [WARNING] module 'kitchensink' has a non matching artifactId >>>>>>> 'jboss-as-kitchensink' >>>>>>> [WARNING] module 'kitchensink-ear' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-ear' >>>>>>> [WARNING] module 'kitchensink-html5-mobile' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-html5-mobile' >>>>>>> [WARNING] module 'kitchensink-jsp' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-jsp' >>>>>>> [WARNING] module 'kitchensink-ml' has a non matching artifactId >>>>>>> 'jboss-as-kitchensink-ml' >>>>>>> [WARNING] module 'kitchensink-ml-ear' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-ml-ear' >>>>>>> [WARNING] module 'log4j' has a non matching artifactId >>>>>>> 'jboss-as-log4j' >>>>>>> [WARNING] module 'logging-tools' has a non matching artifactId >>>>>>> 'jboss-as-logging-tools' >>>>>>> [WARNING] module 'mail' has a non matching artifactId >>>>>>> 'jboss-as-mail' >>>>>>> [WARNING] module 'numberguess' has a non matching artifactId >>>>>>> 'jboss-as-numberguess' >>>>>>> [WARNING] module 'payment-cdi-event' has a non matching >>>>>>> artifactId 'jboss-as-payment-cdi-event' >>>>>>> [WARNING] module 'richfaces-validation' has a non matching >>>>>>> artifactId 'jboss-as-richfaces-validation' >>>>>>> [WARNING] module 'servlet-async' has a non matching artifactId >>>>>>> 'jboss-as-servlet-async' >>>>>>> [WARNING] module 'servlet-filterlistener' has a non matching >>>>>>> artifactId 'jboss-as-servlet-filterlistener' >>>>>>> [WARNING] module 'servlet-security' has a non matching >>>>>>> artifactId 'jboss-as-servlet-security' >>>>>>> [WARNING] module 'tasks' has a non matching artifactId >>>>>>> 'jboss-as-tasks' >>>>>>> [WARNING] module 'tasks-jsf' has a non matching artifactId >>>>>>> 'jboss-as-tasks-jsf' >>>>>>> [WARNING] module 'temperature-converter' has a non matching >>>>>>> artifactId 'jboss-as-temperature-converter' >>>>>>> [WARNING] module 'tasks-rs' has a non matching artifactId >>>>>>> 'jboss-as-tasks-rs' >>>>>>> [WARNING] module 'wicket-ear' has a non matching artifactId >>>>>>> 'jboss-as-wicket-ear-parent' >>>>>>> [WARNING] module 'wicket-war' has a non matching artifactId >>>>>>> 'jboss-as-wicket-war' >>>>>>> [WARNING] module 'xml-jaxp' has a non matching artifactId >>>>>>> 'jboss-as-xml-jaxp' >>>>>>> [WARNING] module 'xml-dom4j' has a non matching artifactId >>>>>>> 'jboss-as-xml-dom4j' >>>>>>> [WARNING] module 'cmt' has a non matching artifactId >>>>>>> 'jboss-as-cmt' >>>>>>> [WARNING] module 'jts' has a non matching artifactId >>>>>>> 'jboss-as-jts-parent' >>>>>>> [WARNING] module 'jax-rs-client' has a non matching artifactId >>>>>>> 'jboss-as-jax-rs-client' >>>>>>> [WARNING] module 'inter-app' has a non matching artifactId >>>>>>> 'jboss-as-inter-app-parent' >>>>>>> [WARNING] module 'helloworld-mdb' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-mdb' >>>>>>> [WARNING] module 'jta-crash-rec' has a non matching artifactId >>>>>>> 'jboss-as-jta-crash-rec' >>>>>>> [WARNING] module 'wsat-simple' has a non matching artifactId >>>>>>> 'jboss-as-wsat-simple' >>>>>>> [WARNING] module 'wsba-coordinator-completion-simple' has a non >>>>>>> matching artifactId >>>>>>> 'jboss-as-wsba-coordinator-completion-simple' >>>>>>> [WARNING] module 'wsba-participant-completion-simple' has a non >>>>>>> matching artifactId >>>>>>> 'jboss-as-wsba-participant-completion-simple' >>>>>>> D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml >>>>>>> generated >>>>>>> >>>>>>> >>>>>>> [WARNING] 50 quickstart artifactIds mismatch with their folder >>>>>>> name. >>>>>>> This will prevent WTP from opening the proper url when running >>>>>>> on a server. >>>>>>> >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] BUILD SUCCESS >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Total time: 5.506s >>>>>>> [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 >>>>>>> [INFO] Final Memory: 11M/490M >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> >>>>>>> As hinted in the log, the examples wouldn't quite work >>>>>>> perfectly OOTB. >>>>>>> http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... >>>>>>> explains how the context root is inferred from the pom.xml by >>>>>>> m2e-wtp. However our own JBoss AS server adapter ignores the >>>>>>> WTP project context root and bases its deployment on the >>>>>>> project name, leading to 404s as seen in the video below. >>>>>>> >>>>>>> End result in JBT / Central : >>>>>>> http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... >>>>>>> >>>>>>> Now. >>>>>>> * are you guys ok to actually remove and replace the old >>>>>>> examples with the JDF quickstarts >>>>>>> * if you're ok, I'll setup a CI job to deploy the quickstarts >>>>>>> to download.jboss.org >>>>>>> * who's willing to give me a hand in validating the quickstarts >>>>>>> properly work in JBT/JBDS. That includes : >>>>>>> - checking the project belongs (or not) to JBT/JBDS >>>>>>> - checking there's a proper project description >>>>>>> - checking the projects are properly configured (I noticed >>>>>>> some EARs are seen as 1.3 instead of 6.0) and compile >>>>>>> without errors >>>>>>> - checking the projects deploy OOTB on AS7/EAP6 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Fred Bricon >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> _______________________________________________ >>> jdf-dev mailing list >>> jdf-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-116) wsat jboss-web.xml with contextroot

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JDF-116: --------------------------------------- Summary: wsat jboss-web.xml with contextroot Key: JDF-116 URL: https://issues.jboss.org/browse/JDF-116 Project: JBoss Developer Framework Issue Type: Bug Reporter: Max Rydahl Andersen ./wsat-simple/src/main/webapp/WEB-INF/jboss-web.xml: <context-root>/</context-root> A root context root will not work without changing the welcome screen. -- 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, 5 months

1
0
0 / 0

Slipping JDG from this release of JDF

by Pete Muir

All As you've seen from emails, we haven't got the JDG portion of TicketMonster ready for JDF 2.0, and we are already late, so we think it's best to slip it to the 2.1 release in January. Please respond by midday tomorrow (GMT) if you object to this. If we do this, then we need to: * back the -with-infinispan BOM out of stacks * back the jdf quickstarts out of jboss-as-quickstarts Rafael, can you take care of the above, tomorrow, assuming there are no objections? Pete

12 years, 5 months

2
2
0 / 0

Re: [jdf-dev] [jbosstools-dev] jboss

by Pete Muir

The current zip of quickstarts is 13.8MB. If this is too large, then we can try to reduce it down again - stuff crept in ;-) On 11 Oct 2012, at 15:40, Rob Cernich wrote: > > > ----- Original Message ----- >> I don't quite understand why selective install can't be: >> >> 1) clone repo >> 2) offer user choice / have choice specified by JBDS >> 3) create project for just that directory >> >> ? >> >> Note that github allows you you to grab a zip of a tag, which means >> you can avoid the git clone... > > A great idea. It's been suggested twice now. Max? > >> >> On 9 Oct 2012, at 09:34, Max Rydahl Andersen wrote: >> >>> >>> On 09 Oct 2012, at 18:25, Snjezana Peco <snjezana.peco(a)redhat.com> >>> wrote: >>> >>>> It would be better to fix >>>> https://issues.jboss.org/browse/JBIDE-8452 >>>> That way, we would be able to create project examples from git as >>>> well as other project examples, select a branch, tag, add >>>> requirements/fixes... >>>> There are already a prototype for this issue >>>> (https://github.com/snjeza/jbossm2egit) that is necessary to >>>> upgrade to newer versions of m2e and EGit. >>> >>> Yes, but that wouldn't allow selective install either would it ? >>> and the issues below with the run-as would still be there. >>> >>> note: I still think JBIDE-8452 should happen but not sure it solves >>> the problem on its own ? >>> >>> /max >>> >>>> >>>> Snjeza >>>> >>>> On 9.10.2012 18:11, Fred Bricon wrote: >>>>> Le 09/10/2012 17:43, Sande Gilda a écrit : >>>>>> Fred, this looks really cool! >>>>> Yeah I know :-) >>>>>> I do have one question. You say "However our own JBoss AS server >>>>>> adapter ignores the WTP project context root and bases its >>>>>> deployment on the project name, leading to 404s as seen in the >>>>>> video below." Is this a bug with JBoss or something else? Is >>>>>> there a JIRA or Bugzilla for this? >>>>>> >>>>> See https://issues.jboss.org/browse/JBIDE-473 >>>>>> Pete, correct me if I'm wrong, but I believe the context root >>>>>> for the quickstarts was prefixed by jboss-as to make them >>>>>> unique and prevent them from overwriting existing deployments. >>>>>> for example "helloworld". It would be nice if the quickstarts >>>>>> worked the same way in JDBS as they do deployed in command >>>>>> line. >>>>>> >>>>> renaming the module directories to include the jboss-as prefix >>>>> would actually fix the problem. >>>>> >>>>>> >>>>>> On 10/09/2012 11:14 AM, Fred Bricon wrote: >>>>>>> Hi, >>>>>>> >>>>>>> we need to clean up the project examples in JBoss Tools >>>>>>> 4.0/JBDS 6.0 (as part of >>>>>>> https://issues.jboss.org/browse/JBIDE-12554). >>>>>>> So, my idea was to replace all the old examples with the >>>>>>> quickstarts from >>>>>>> https://github.com/jboss-jdf/jboss-as-quickstart >>>>>>> >>>>>>> Since the quickstarts are not available as standalone zips, for >>>>>>> consumption in JBT/JBDS, I created a script >>>>>>> (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) >>>>>>> that does that, and it also generates a project example stub >>>>>>> we can use almost directly in JBT. >>>>>>> >>>>>>> D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N >>>>>>> -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts >>>>>>> [INFO] Scanning for projects... >>>>>>> [INFO] >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] >>>>>>> [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ >>>>>>> jboss-as-quickstarts-parent --- >>>>>>> Starting zipping JBoss AS Quickstarts Parent modules >>>>>>> Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips >>>>>>> Zipped 51 quickstart modules >>>>>>> Generating project examples descriptor for JBoss Tools >>>>>>> [WARNING] module 'bmt' has a non matching artifactId >>>>>>> 'jboss-as-bmt' >>>>>>> [WARNING] module 'cdi-injection' has a non matching artifactId >>>>>>> 'jboss-as-cdi-injection' >>>>>>> [WARNING] module 'cdi-portable-extension' has a non matching >>>>>>> artifactId 'jboss-as-cdi-portable-extension' >>>>>>> [WARNING] module 'ejb-in-ear' has a non matching artifactId >>>>>>> 'jboss-as-ejb-in-ear' >>>>>>> [WARNING] module 'ejb-in-war' has a non matching artifactId >>>>>>> 'jboss-as-ejb-in-war' >>>>>>> [WARNING] module 'ejb-remote' has a non matching artifactId >>>>>>> 'jboss-as-ejb-remote-parent' >>>>>>> [WARNING] module 'ejb-security' has a non matching artifactId >>>>>>> 'jboss-as-ejb-security' >>>>>>> [WARNING] module 'greeter' has a non matching artifactId >>>>>>> 'jboss-as-greeter' >>>>>>> [WARNING] module 'helloworld' has a non matching artifactId >>>>>>> 'jboss-as-helloworld' >>>>>>> [WARNING] module 'helloworld-errai' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-errai' >>>>>>> [WARNING] module 'helloworld-gwt' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-gwt' >>>>>>> [WARNING] module 'helloworld-html5' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-html5' >>>>>>> [WARNING] module 'helloworld-jms' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-jms' >>>>>>> [WARNING] module 'helloworld-osgi' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-osgi' >>>>>>> [WARNING] module 'helloworld-rs' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-rs' >>>>>>> [WARNING] module 'helloworld-singleton' has a non matching >>>>>>> artifactId 'jboss-as-helloworld-singleton' >>>>>>> [WARNING] module 'hibernate3' has a non matching artifactId >>>>>>> 'jboss-as-hibernate3' >>>>>>> [WARNING] module 'hibernate4' has a non matching artifactId >>>>>>> 'jboss-as-hibernate4' >>>>>>> [WARNING] module 'kitchensink' has a non matching artifactId >>>>>>> 'jboss-as-kitchensink' >>>>>>> [WARNING] module 'kitchensink-ear' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-ear' >>>>>>> [WARNING] module 'kitchensink-html5-mobile' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-html5-mobile' >>>>>>> [WARNING] module 'kitchensink-jsp' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-jsp' >>>>>>> [WARNING] module 'kitchensink-ml' has a non matching artifactId >>>>>>> 'jboss-as-kitchensink-ml' >>>>>>> [WARNING] module 'kitchensink-ml-ear' has a non matching >>>>>>> artifactId 'jboss-as-kitchensink-ml-ear' >>>>>>> [WARNING] module 'log4j' has a non matching artifactId >>>>>>> 'jboss-as-log4j' >>>>>>> [WARNING] module 'logging-tools' has a non matching artifactId >>>>>>> 'jboss-as-logging-tools' >>>>>>> [WARNING] module 'mail' has a non matching artifactId >>>>>>> 'jboss-as-mail' >>>>>>> [WARNING] module 'numberguess' has a non matching artifactId >>>>>>> 'jboss-as-numberguess' >>>>>>> [WARNING] module 'payment-cdi-event' has a non matching >>>>>>> artifactId 'jboss-as-payment-cdi-event' >>>>>>> [WARNING] module 'richfaces-validation' has a non matching >>>>>>> artifactId 'jboss-as-richfaces-validation' >>>>>>> [WARNING] module 'servlet-async' has a non matching artifactId >>>>>>> 'jboss-as-servlet-async' >>>>>>> [WARNING] module 'servlet-filterlistener' has a non matching >>>>>>> artifactId 'jboss-as-servlet-filterlistener' >>>>>>> [WARNING] module 'servlet-security' has a non matching >>>>>>> artifactId 'jboss-as-servlet-security' >>>>>>> [WARNING] module 'tasks' has a non matching artifactId >>>>>>> 'jboss-as-tasks' >>>>>>> [WARNING] module 'tasks-jsf' has a non matching artifactId >>>>>>> 'jboss-as-tasks-jsf' >>>>>>> [WARNING] module 'temperature-converter' has a non matching >>>>>>> artifactId 'jboss-as-temperature-converter' >>>>>>> [WARNING] module 'tasks-rs' has a non matching artifactId >>>>>>> 'jboss-as-tasks-rs' >>>>>>> [WARNING] module 'wicket-ear' has a non matching artifactId >>>>>>> 'jboss-as-wicket-ear-parent' >>>>>>> [WARNING] module 'wicket-war' has a non matching artifactId >>>>>>> 'jboss-as-wicket-war' >>>>>>> [WARNING] module 'xml-jaxp' has a non matching artifactId >>>>>>> 'jboss-as-xml-jaxp' >>>>>>> [WARNING] module 'xml-dom4j' has a non matching artifactId >>>>>>> 'jboss-as-xml-dom4j' >>>>>>> [WARNING] module 'cmt' has a non matching artifactId >>>>>>> 'jboss-as-cmt' >>>>>>> [WARNING] module 'jts' has a non matching artifactId >>>>>>> 'jboss-as-jts-parent' >>>>>>> [WARNING] module 'jax-rs-client' has a non matching artifactId >>>>>>> 'jboss-as-jax-rs-client' >>>>>>> [WARNING] module 'inter-app' has a non matching artifactId >>>>>>> 'jboss-as-inter-app-parent' >>>>>>> [WARNING] module 'helloworld-mdb' has a non matching artifactId >>>>>>> 'jboss-as-helloworld-mdb' >>>>>>> [WARNING] module 'jta-crash-rec' has a non matching artifactId >>>>>>> 'jboss-as-jta-crash-rec' >>>>>>> [WARNING] module 'wsat-simple' has a non matching artifactId >>>>>>> 'jboss-as-wsat-simple' >>>>>>> [WARNING] module 'wsba-coordinator-completion-simple' has a non >>>>>>> matching artifactId >>>>>>> 'jboss-as-wsba-coordinator-completion-simple' >>>>>>> [WARNING] module 'wsba-participant-completion-simple' has a non >>>>>>> matching artifactId >>>>>>> 'jboss-as-wsba-participant-completion-simple' >>>>>>> D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml >>>>>>> generated >>>>>>> >>>>>>> >>>>>>> [WARNING] 50 quickstart artifactIds mismatch with their folder >>>>>>> name. >>>>>>> This will prevent WTP from opening the proper url when running >>>>>>> on a server. >>>>>>> >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] BUILD SUCCESS >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Total time: 5.506s >>>>>>> [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 >>>>>>> [INFO] Final Memory: 11M/490M >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> >>>>>>> As hinted in the log, the examples wouldn't quite work >>>>>>> perfectly OOTB. >>>>>>> http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... >>>>>>> explains how the context root is inferred from the pom.xml by >>>>>>> m2e-wtp. However our own JBoss AS server adapter ignores the >>>>>>> WTP project context root and bases its deployment on the >>>>>>> project name, leading to 404s as seen in the video below. >>>>>>> >>>>>>> End result in JBT / Central : >>>>>>> http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... >>>>>>> >>>>>>> Now. >>>>>>> * are you guys ok to actually remove and replace the old >>>>>>> examples with the JDF quickstarts >>>>>>> * if you're ok, I'll setup a CI job to deploy the quickstarts >>>>>>> to download.jboss.org >>>>>>> * who's willing to give me a hand in validating the quickstarts >>>>>>> properly work in JBT/JBDS. That includes : >>>>>>> - checking the project belongs (or not) to JBT/JBDS >>>>>>> - checking there's a proper project description >>>>>>> - checking the projects are properly configured (I noticed >>>>>>> some EARs are seen as 1.3 instead of 6.0) and compile >>>>>>> without errors >>>>>>> - checking the projects deploy OOTB on AS7/EAP6 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Fred Bricon >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> _______________________________________________ >>> jdf-dev mailing list >>> jdf-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>

12 years, 5 months

1
0
0 / 0

Re: [jdf-dev] [jbosstools-dev] jboss

by Max Rydahl Andersen

On 09 Oct 2012, at 18:25, Snjezana Peco <snjezana.peco(a)redhat.com> wrote: > It would be better to fix https://issues.jboss.org/browse/JBIDE-8452 > That way, we would be able to create project examples from git as well as other project examples, select a branch, tag, add requirements/fixes... > There are already a prototype for this issue (https://github.com/snjeza/jbossm2egit) that is necessary to upgrade to newer versions of m2e and EGit. Yes, but that wouldn't allow selective install either would it ? and the issues below with the run-as would still be there. note: I still think JBIDE-8452 should happen but not sure it solves the problem on its own ? /max > > Snjeza > > On 9.10.2012 18:11, Fred Bricon wrote: >> Le 09/10/2012 17:43, Sande Gilda a écrit : >>> Fred, this looks really cool! >> Yeah I know :-) >>> I do have one question. You say "However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below." Is this a bug with JBoss or something else? Is there a JIRA or Bugzilla for this? >>> >> See https://issues.jboss.org/browse/JBIDE-473 >>> Pete, correct me if I'm wrong, but I believe the context root for the quickstarts was prefixed by jboss-as to make them unique and prevent them from overwriting existing deployments. for example "helloworld". It would be nice if the quickstarts worked the same way in JDBS as they do deployed in command line. >>> >> renaming the module directories to include the jboss-as prefix would actually fix the problem. >> >>> >>> On 10/09/2012 11:14 AM, Fred Bricon wrote: >>>> Hi, >>>> >>>> we need to clean up the project examples in JBoss Tools 4.0/JBDS 6.0 (as part of https://issues.jboss.org/browse/JBIDE-12554). >>>> So, my idea was to replace all the old examples with the quickstarts from https://github.com/jboss-jdf/jboss-as-quickstart >>>> >>>> Since the quickstarts are not available as standalone zips, for consumption in JBT/JBDS, I created a script (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) that does that, and it also generates a project example stub we can use almost directly in JBT. >>>> >>>> D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts >>>> [INFO] Scanning for projects... >>>> [INFO] >>>> [INFO] ------------------------------------------------------------------------ >>>> [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT >>>> [INFO] ------------------------------------------------------------------------ >>>> [INFO] >>>> [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ jboss-as-quickstarts-parent --- >>>> Starting zipping JBoss AS Quickstarts Parent modules >>>> Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips >>>> Zipped 51 quickstart modules >>>> Generating project examples descriptor for JBoss Tools >>>> [WARNING] module 'bmt' has a non matching artifactId 'jboss-as-bmt' >>>> [WARNING] module 'cdi-injection' has a non matching artifactId 'jboss-as-cdi-injection' >>>> [WARNING] module 'cdi-portable-extension' has a non matching artifactId 'jboss-as-cdi-portable-extension' >>>> [WARNING] module 'ejb-in-ear' has a non matching artifactId 'jboss-as-ejb-in-ear' >>>> [WARNING] module 'ejb-in-war' has a non matching artifactId 'jboss-as-ejb-in-war' >>>> [WARNING] module 'ejb-remote' has a non matching artifactId 'jboss-as-ejb-remote-parent' >>>> [WARNING] module 'ejb-security' has a non matching artifactId 'jboss-as-ejb-security' >>>> [WARNING] module 'greeter' has a non matching artifactId 'jboss-as-greeter' >>>> [WARNING] module 'helloworld' has a non matching artifactId 'jboss-as-helloworld' >>>> [WARNING] module 'helloworld-errai' has a non matching artifactId 'jboss-as-helloworld-errai' >>>> [WARNING] module 'helloworld-gwt' has a non matching artifactId 'jboss-as-helloworld-gwt' >>>> [WARNING] module 'helloworld-html5' has a non matching artifactId 'jboss-as-helloworld-html5' >>>> [WARNING] module 'helloworld-jms' has a non matching artifactId 'jboss-as-helloworld-jms' >>>> [WARNING] module 'helloworld-osgi' has a non matching artifactId 'jboss-as-helloworld-osgi' >>>> [WARNING] module 'helloworld-rs' has a non matching artifactId 'jboss-as-helloworld-rs' >>>> [WARNING] module 'helloworld-singleton' has a non matching artifactId 'jboss-as-helloworld-singleton' >>>> [WARNING] module 'hibernate3' has a non matching artifactId 'jboss-as-hibernate3' >>>> [WARNING] module 'hibernate4' has a non matching artifactId 'jboss-as-hibernate4' >>>> [WARNING] module 'kitchensink' has a non matching artifactId 'jboss-as-kitchensink' >>>> [WARNING] module 'kitchensink-ear' has a non matching artifactId 'jboss-as-kitchensink-ear' >>>> [WARNING] module 'kitchensink-html5-mobile' has a non matching artifactId 'jboss-as-kitchensink-html5-mobile' >>>> [WARNING] module 'kitchensink-jsp' has a non matching artifactId 'jboss-as-kitchensink-jsp' >>>> [WARNING] module 'kitchensink-ml' has a non matching artifactId 'jboss-as-kitchensink-ml' >>>> [WARNING] module 'kitchensink-ml-ear' has a non matching artifactId 'jboss-as-kitchensink-ml-ear' >>>> [WARNING] module 'log4j' has a non matching artifactId 'jboss-as-log4j' >>>> [WARNING] module 'logging-tools' has a non matching artifactId 'jboss-as-logging-tools' >>>> [WARNING] module 'mail' has a non matching artifactId 'jboss-as-mail' >>>> [WARNING] module 'numberguess' has a non matching artifactId 'jboss-as-numberguess' >>>> [WARNING] module 'payment-cdi-event' has a non matching artifactId 'jboss-as-payment-cdi-event' >>>> [WARNING] module 'richfaces-validation' has a non matching artifactId 'jboss-as-richfaces-validation' >>>> [WARNING] module 'servlet-async' has a non matching artifactId 'jboss-as-servlet-async' >>>> [WARNING] module 'servlet-filterlistener' has a non matching artifactId 'jboss-as-servlet-filterlistener' >>>> [WARNING] module 'servlet-security' has a non matching artifactId 'jboss-as-servlet-security' >>>> [WARNING] module 'tasks' has a non matching artifactId 'jboss-as-tasks' >>>> [WARNING] module 'tasks-jsf' has a non matching artifactId 'jboss-as-tasks-jsf' >>>> [WARNING] module 'temperature-converter' has a non matching artifactId 'jboss-as-temperature-converter' >>>> [WARNING] module 'tasks-rs' has a non matching artifactId 'jboss-as-tasks-rs' >>>> [WARNING] module 'wicket-ear' has a non matching artifactId 'jboss-as-wicket-ear-parent' >>>> [WARNING] module 'wicket-war' has a non matching artifactId 'jboss-as-wicket-war' >>>> [WARNING] module 'xml-jaxp' has a non matching artifactId 'jboss-as-xml-jaxp' >>>> [WARNING] module 'xml-dom4j' has a non matching artifactId 'jboss-as-xml-dom4j' >>>> [WARNING] module 'cmt' has a non matching artifactId 'jboss-as-cmt' >>>> [WARNING] module 'jts' has a non matching artifactId 'jboss-as-jts-parent' >>>> [WARNING] module 'jax-rs-client' has a non matching artifactId 'jboss-as-jax-rs-client' >>>> [WARNING] module 'inter-app' has a non matching artifactId 'jboss-as-inter-app-parent' >>>> [WARNING] module 'helloworld-mdb' has a non matching artifactId 'jboss-as-helloworld-mdb' >>>> [WARNING] module 'jta-crash-rec' has a non matching artifactId 'jboss-as-jta-crash-rec' >>>> [WARNING] module 'wsat-simple' has a non matching artifactId 'jboss-as-wsat-simple' >>>> [WARNING] module 'wsba-coordinator-completion-simple' has a non matching artifactId 'jboss-as-wsba-coordinator-completion-simple' >>>> [WARNING] module 'wsba-participant-completion-simple' has a non matching artifactId 'jboss-as-wsba-participant-completion-simple' >>>> D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml generated >>>> >>>> >>>> [WARNING] 50 quickstart artifactIds mismatch with their folder name. >>>> This will prevent WTP from opening the proper url when running on a server. >>>> >>>> [INFO] ------------------------------------------------------------------------ >>>> [INFO] BUILD SUCCESS >>>> [INFO] ------------------------------------------------------------------------ >>>> [INFO] Total time: 5.506s >>>> [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 >>>> [INFO] Final Memory: 11M/490M >>>> [INFO] ------------------------------------------------------------------------ >>>> >>>> As hinted in the log, the examples wouldn't quite work perfectly OOTB. http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... explains how the context root is inferred from the pom.xml by m2e-wtp. However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below. >>>> >>>> End result in JBT / Central : http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... >>>> >>>> Now. >>>> * are you guys ok to actually remove and replace the old examples with the JDF quickstarts >>>> * if you're ok, I'll setup a CI job to deploy the quickstarts to download.jboss.org >>>> * who's willing to give me a hand in validating the quickstarts properly work in JBT/JBDS. That includes : >>>> - checking the project belongs (or not) to JBT/JBDS >>>> - checking there's a proper project description >>>> - checking the projects are properly configured (I noticed some EARs are seen as 1.3 instead of 6.0) and compile without errors >>>> - checking the projects deploy OOTB on AS7/EAP6 >>>> >>>> Regards, >>>> >>>> Fred Bricon >>>> >>> >> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

12 years, 5 months

2
1
0 / 0

Re: [jdf-dev] JBoss Stacks Echosystem 1.0.0.Final released!

by Rafael Benevides

Cool!!! :D Em 09-10-2012 05:40, Fred Bricon escreveu: > FYI, I've updated JBT 4.0.0.Beta1 to use stacks-client 1.0.0.Final > (https://issues.jboss.org/browse/JBIDE-12816) > > Fred > > Le 08/10/2012 23:44, Rafael Benevides a écrit : >> JBoss Stacks (stacks.yaml format / stacks-client / jdg-forge-plugin ) >> 1.0.0.Final released >> >> Em 02-10-2012 12:13, Rafael Benevides escreveu: >>> Hi all, >>> >>> I want a feedback from JBoss Stacks Echosystem (stacks.yaml format / >>> stacks-client / jdf-forge-plugin). >>> >>> We are on 1.0.0.CR2 format to stacks.yaml and I want to know if do you >>> have any other issue on this? So I can move all of them to .Final >>> and we >>> can release JDF 2.0.0.Final next week. >>> >>> >>> Thanks >>> >

12 years, 5 months

1
0
0 / 0

Re: [jdf-dev] [jbosstools-dev] JDF Quickstarts in JBoss Central?

by Max Rydahl Andersen

>>> JBIDE-8542 would enable creating a project example from git repository directly. >>> It would be possible to define a project example for any maven or eclipse project on some git repository. >>> it would be enough to declare a project example of the git type in the project example xml file, specify a branch or tag and add other standard project examples properties: fixes, tags... >> >> yes, but that doesn't apply for the quickstarts since their repo contain multiple projects. >> >> Or am I missing something ? > > We can define a project example of the git type that contains one or more projects. eh? your feature clones the git repo - how will you clone a partial repository ? > > Snjeza > >> >> /max >> >>> Snjeza >>>> /max >>>> >>>>> Snjeza >>>>> >>>>> On 9.10.2012 18:11, Fred Bricon wrote: >>>>>> Le 09/10/2012 17:43, Sande Gilda a écrit : >>>>>>> Fred, this looks really cool! >>>>>> Yeah I know :-) >>>>>>> I do have one question. You say "However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below." Is this a bug with JBoss or something else? Is there a JIRA or Bugzilla for this? >>>>>>> >>>>>> See https://issues.jboss.org/browse/JBIDE-473 >>>>>>> Pete, correct me if I'm wrong, but I believe the context root for the quickstarts was prefixed by jboss-as to make them unique and prevent them from overwriting existing deployments. for example "helloworld". It would be nice if the quickstarts worked the same way in JDBS as they do deployed in command line. >>>>>>> >>>>>> renaming the module directories to include the jboss-as prefix would actually fix the problem. >>>>>> >>>>>>> On 10/09/2012 11:14 AM, Fred Bricon wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> we need to clean up the project examples in JBoss Tools 4.0/JBDS 6.0 (as part of https://issues.jboss.org/browse/JBIDE-12554). >>>>>>>> So, my idea was to replace all the old examples with the quickstarts from https://github.com/jboss-jdf/jboss-as-quickstart >>>>>>>> >>>>>>>> Since the quickstarts are not available as standalone zips, for consumption in JBT/JBDS, I created a script (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) that does that, and it also generates a project example stub we can use almost directly in JBT. >>>>>>>> >>>>>>>> D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts >>>>>>>> [INFO] Scanning for projects... >>>>>>>> [INFO] >>>>>>>> [INFO] ------------------------------------------------------------------------ >>>>>>>> [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT >>>>>>>> [INFO] ------------------------------------------------------------------------ >>>>>>>> [INFO] >>>>>>>> [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ jboss-as-quickstarts-parent --- >>>>>>>> Starting zipping JBoss AS Quickstarts Parent modules >>>>>>>> Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips >>>>>>>> Zipped 51 quickstart modules >>>>>>>> Generating project examples descriptor for JBoss Tools >>>>>>>> [WARNING] module 'bmt' has a non matching artifactId 'jboss-as-bmt' >>>>>>>> [WARNING] module 'cdi-injection' has a non matching artifactId 'jboss-as-cdi-injection' >>>>>>>> [WARNING] module 'cdi-portable-extension' has a non matching artifactId 'jboss-as-cdi-portable-extension' >>>>>>>> [WARNING] module 'ejb-in-ear' has a non matching artifactId 'jboss-as-ejb-in-ear' >>>>>>>> [WARNING] module 'ejb-in-war' has a non matching artifactId 'jboss-as-ejb-in-war' >>>>>>>> [WARNING] module 'ejb-remote' has a non matching artifactId 'jboss-as-ejb-remote-parent' >>>>>>>> [WARNING] module 'ejb-security' has a non matching artifactId 'jboss-as-ejb-security' >>>>>>>> [WARNING] module 'greeter' has a non matching artifactId 'jboss-as-greeter' >>>>>>>> [WARNING] module 'helloworld' has a non matching artifactId 'jboss-as-helloworld' >>>>>>>> [WARNING] module 'helloworld-errai' has a non matching artifactId 'jboss-as-helloworld-errai' >>>>>>>> [WARNING] module 'helloworld-gwt' has a non matching artifactId 'jboss-as-helloworld-gwt' >>>>>>>> [WARNING] module 'helloworld-html5' has a non matching artifactId 'jboss-as-helloworld-html5' >>>>>>>> [WARNING] module 'helloworld-jms' has a non matching artifactId 'jboss-as-helloworld-jms' >>>>>>>> [WARNING] module 'helloworld-osgi' has a non matching artifactId 'jboss-as-helloworld-osgi' >>>>>>>> [WARNING] module 'helloworld-rs' has a non matching artifactId 'jboss-as-helloworld-rs' >>>>>>>> [WARNING] module 'helloworld-singleton' has a non matching artifactId 'jboss-as-helloworld-singleton' >>>>>>>> [WARNING] module 'hibernate3' has a non matching artifactId 'jboss-as-hibernate3' >>>>>>>> [WARNING] module 'hibernate4' has a non matching artifactId 'jboss-as-hibernate4' >>>>>>>> [WARNING] module 'kitchensink' has a non matching artifactId 'jboss-as-kitchensink' >>>>>>>> [WARNING] module 'kitchensink-ear' has a non matching artifactId 'jboss-as-kitchensink-ear' >>>>>>>> [WARNING] module 'kitchensink-html5-mobile' has a non matching artifactId 'jboss-as-kitchensink-html5-mobile' >>>>>>>> [WARNING] module 'kitchensink-jsp' has a non matching artifactId 'jboss-as-kitchensink-jsp' >>>>>>>> [WARNING] module 'kitchensink-ml' has a non matching artifactId 'jboss-as-kitchensink-ml' >>>>>>>> [WARNING] module 'kitchensink-ml-ear' has a non matching artifactId 'jboss-as-kitchensink-ml-ear' >>>>>>>> [WARNING] module 'log4j' has a non matching artifactId 'jboss-as-log4j' >>>>>>>> [WARNING] module 'logging-tools' has a non matching artifactId 'jboss-as-logging-tools' >>>>>>>> [WARNING] module 'mail' has a non matching artifactId 'jboss-as-mail' >>>>>>>> [WARNING] module 'numberguess' has a non matching artifactId 'jboss-as-numberguess' >>>>>>>> [WARNING] module 'payment-cdi-event' has a non matching artifactId 'jboss-as-payment-cdi-event' >>>>>>>> [WARNING] module 'richfaces-validation' has a non matching artifactId 'jboss-as-richfaces-validation' >>>>>>>> [WARNING] module 'servlet-async' has a non matching artifactId 'jboss-as-servlet-async' >>>>>>>> [WARNING] module 'servlet-filterlistener' has a non matching artifactId 'jboss-as-servlet-filterlistener' >>>>>>>> [WARNING] module 'servlet-security' has a non matching artifactId 'jboss-as-servlet-security' >>>>>>>> [WARNING] module 'tasks' has a non matching artifactId 'jboss-as-tasks' >>>>>>>> [WARNING] module 'tasks-jsf' has a non matching artifactId 'jboss-as-tasks-jsf' >>>>>>>> [WARNING] module 'temperature-converter' has a non matching artifactId 'jboss-as-temperature-converter' >>>>>>>> [WARNING] module 'tasks-rs' has a non matching artifactId 'jboss-as-tasks-rs' >>>>>>>> [WARNING] module 'wicket-ear' has a non matching artifactId 'jboss-as-wicket-ear-parent' >>>>>>>> [WARNING] module 'wicket-war' has a non matching artifactId 'jboss-as-wicket-war' >>>>>>>> [WARNING] module 'xml-jaxp' has a non matching artifactId 'jboss-as-xml-jaxp' >>>>>>>> [WARNING] module 'xml-dom4j' has a non matching artifactId 'jboss-as-xml-dom4j' >>>>>>>> [WARNING] module 'cmt' has a non matching artifactId 'jboss-as-cmt' >>>>>>>> [WARNING] module 'jts' has a non matching artifactId 'jboss-as-jts-parent' >>>>>>>> [WARNING] module 'jax-rs-client' has a non matching artifactId 'jboss-as-jax-rs-client' >>>>>>>> [WARNING] module 'inter-app' has a non matching artifactId 'jboss-as-inter-app-parent' >>>>>>>> [WARNING] module 'helloworld-mdb' has a non matching artifactId 'jboss-as-helloworld-mdb' >>>>>>>> [WARNING] module 'jta-crash-rec' has a non matching artifactId 'jboss-as-jta-crash-rec' >>>>>>>> [WARNING] module 'wsat-simple' has a non matching artifactId 'jboss-as-wsat-simple' >>>>>>>> [WARNING] module 'wsba-coordinator-completion-simple' has a non matching artifactId 'jboss-as-wsba-coordinator-completion-simple' >>>>>>>> [WARNING] module 'wsba-participant-completion-simple' has a non matching artifactId 'jboss-as-wsba-participant-completion-simple' >>>>>>>> D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml generated >>>>>>>> >>>>>>>> >>>>>>>> [WARNING] 50 quickstart artifactIds mismatch with their folder name. >>>>>>>> This will prevent WTP from opening the proper url when running on a server. >>>>>>>> >>>>>>>> [INFO] ------------------------------------------------------------------------ >>>>>>>> [INFO] BUILD SUCCESS >>>>>>>> [INFO] ------------------------------------------------------------------------ >>>>>>>> [INFO] Total time: 5.506s >>>>>>>> [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 >>>>>>>> [INFO] Final Memory: 11M/490M >>>>>>>> [INFO] ------------------------------------------------------------------------ >>>>>>>> >>>>>>>> As hinted in the log, the examples wouldn't quite work perfectly OOTB. http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... explains how the context root is inferred from the pom.xml by m2e-wtp. However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below. >>>>>>>> >>>>>>>> End result in JBT / Central : http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... >>>>>>>> >>>>>>>> Now. >>>>>>>> * are you guys ok to actually remove and replace the old examples with the JDF quickstarts >>>>>>>> * if you're ok, I'll setup a CI job to deploy the quickstarts to download.jboss.org >>>>>>>> * who's willing to give me a hand in validating the quickstarts properly work in JBT/JBDS. That includes : >>>>>>>> - checking the project belongs (or not) to JBT/JBDS >>>>>>>> - checking there's a proper project description >>>>>>>> - checking the projects are properly configured (I noticed some EARs are seen as 1.3 instead of 6.0) and compile without errors >>>>>>>> - checking the projects deploy OOTB on AS7/EAP6 >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Fred Bricon >>>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> >>>>>> jbosstools-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

12 years, 5 months

1
0
0 / 0

Re: [jdf-dev] [jbosstools-dev] JDF Quickstarts in JBoss Central?

by Max Rydahl Andersen

> Have you thought about modifying the project-examples functionality to work directly with the quickstarts zips in Maven? I was looking at something like this a while back, as SwitchYard bundles all their quickstarts in a zip for packaging with the runtime. If you could simply download the projects from Maven, I think that would greatly simplify things. > > That said, I never got a chance to finish this work for SwitchYard (other priorities). > > Here is some history: https://issues.jboss.org/browse/JBIDE-10616 this issue is marked as resolved but no comments on what was fixed ....snjezana ? /max > > Best, > Rob > > Hi, > > we need to clean up the project examples in JBoss Tools 4.0/JBDS 6.0 (as part of https://issues.jboss.org/browse/JBIDE-12554). > So, my idea was to replace all the old examples with the quickstarts from https://github.com/jboss-jdf/jboss-as-quickstart > > Since the quickstarts are not available as standalone zips, for consumption in JBT/JBDS, I created a script (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) that does that, and it also generates a project example stub we can use almost directly in JBT. > > D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ jboss-as-quickstarts-parent --- > Starting zipping JBoss AS Quickstarts Parent modules > Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips > Zipped 51 quickstart modules > Generating project examples descriptor for JBoss Tools > [WARNING] module 'bmt' has a non matching artifactId 'jboss-as-bmt' > [WARNING] module 'cdi-injection' has a non matching artifactId 'jboss-as-cdi-injection' > [WARNING] module 'cdi-portable-extension' has a non matching artifactId 'jboss-as-cdi-portable-extension' > [WARNING] module 'ejb-in-ear' has a non matching artifactId 'jboss-as-ejb-in-ear' > [WARNING] module 'ejb-in-war' has a non matching artifactId 'jboss-as-ejb-in-war' > [WARNING] module 'ejb-remote' has a non matching artifactId 'jboss-as-ejb-remote-parent' > [WARNING] module 'ejb-security' has a non matching artifactId 'jboss-as-ejb-security' > [WARNING] module 'greeter' has a non matching artifactId 'jboss-as-greeter' > [WARNING] module 'helloworld' has a non matching artifactId 'jboss-as-helloworld' > [WARNING] module 'helloworld-errai' has a non matching artifactId 'jboss-as-helloworld-errai' > [WARNING] module 'helloworld-gwt' has a non matching artifactId 'jboss-as-helloworld-gwt' > [WARNING] module 'helloworld-html5' has a non matching artifactId 'jboss-as-helloworld-html5' > [WARNING] module 'helloworld-jms' has a non matching artifactId 'jboss-as-helloworld-jms' > [WARNING] module 'helloworld-osgi' has a non matching artifactId 'jboss-as-helloworld-osgi' > [WARNING] module 'helloworld-rs' has a non matching artifactId 'jboss-as-helloworld-rs' > [WARNING] module 'helloworld-singleton' has a non matching artifactId 'jboss-as-helloworld-singleton' > [WARNING] module 'hibernate3' has a non matching artifactId 'jboss-as-hibernate3' > [WARNING] module 'hibernate4' has a non matching artifactId 'jboss-as-hibernate4' > [WARNING] module 'kitchensink' has a non matching artifactId 'jboss-as-kitchensink' > [WARNING] module 'kitchensink-ear' has a non matching artifactId 'jboss-as-kitchensink-ear' > [WARNING] module 'kitchensink-html5-mobile' has a non matching artifactId 'jboss-as-kitchensink-html5-mobile' > [WARNING] module 'kitchensink-jsp' has a non matching artifactId 'jboss-as-kitchensink-jsp' > [WARNING] module 'kitchensink-ml' has a non matching artifactId 'jboss-as-kitchensink-ml' > [WARNING] module 'kitchensink-ml-ear' has a non matching artifactId 'jboss-as-kitchensink-ml-ear' > [WARNING] module 'log4j' has a non matching artifactId 'jboss-as-log4j' > [WARNING] module 'logging-tools' has a non matching artifactId 'jboss-as-logging-tools' > [WARNING] module 'mail' has a non matching artifactId 'jboss-as-mail' > [WARNING] module 'numberguess' has a non matching artifactId 'jboss-as-numberguess' > [WARNING] module 'payment-cdi-event' has a non matching artifactId 'jboss-as-payment-cdi-event' > [WARNING] module 'richfaces-validation' has a non matching artifactId 'jboss-as-richfaces-validation' > [WARNING] module 'servlet-async' has a non matching artifactId 'jboss-as-servlet-async' > [WARNING] module 'servlet-filterlistener' has a non matching artifactId 'jboss-as-servlet-filterlistener' > [WARNING] module 'servlet-security' has a non matching artifactId 'jboss-as-servlet-security' > [WARNING] module 'tasks' has a non matching artifactId 'jboss-as-tasks' > [WARNING] module 'tasks-jsf' has a non matching artifactId 'jboss-as-tasks-jsf' > [WARNING] module 'temperature-converter' has a non matching artifactId 'jboss-as-temperature-converter' > [WARNING] module 'tasks-rs' has a non matching artifactId 'jboss-as-tasks-rs' > [WARNING] module 'wicket-ear' has a non matching artifactId 'jboss-as-wicket-ear-parent' > [WARNING] module 'wicket-war' has a non matching artifactId 'jboss-as-wicket-war' > [WARNING] module 'xml-jaxp' has a non matching artifactId 'jboss-as-xml-jaxp' > [WARNING] module 'xml-dom4j' has a non matching artifactId 'jboss-as-xml-dom4j' > [WARNING] module 'cmt' has a non matching artifactId 'jboss-as-cmt' > [WARNING] module 'jts' has a non matching artifactId 'jboss-as-jts-parent' > [WARNING] module 'jax-rs-client' has a non matching artifactId 'jboss-as-jax-rs-client' > [WARNING] module 'inter-app' has a non matching artifactId 'jboss-as-inter-app-parent' > [WARNING] module 'helloworld-mdb' has a non matching artifactId 'jboss-as-helloworld-mdb' > [WARNING] module 'jta-crash-rec' has a non matching artifactId 'jboss-as-jta-crash-rec' > [WARNING] module 'wsat-simple' has a non matching artifactId 'jboss-as-wsat-simple' > [WARNING] module 'wsba-coordinator-completion-simple' has a non matching artifactId 'jboss-as-wsba-coordinator-completion-simple' > [WARNING] module 'wsba-participant-completion-simple' has a non matching artifactId 'jboss-as-wsba-participant-completion-simple' > D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml generated > > > [WARNING] 50 quickstart artifactIds mismatch with their folder name. > This will prevent WTP from opening the proper url when running on a server. > > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 5.506s > [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 > [INFO] Final Memory: 11M/490M > [INFO] ------------------------------------------------------------------------ > > As hinted in the log, the examples wouldn't quite work perfectly OOTB. http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... explains how the context root is inferred from the pom.xml by m2e-wtp. However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below. > > End result in JBT / Central : http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... > > Now. > * are you guys ok to actually remove and replace the old examples with the JDF quickstarts > * if you're ok, I'll setup a CI job to deploy the quickstarts to download.jboss.org > * who's willing to give me a hand in validating the quickstarts properly work in JBT/JBDS. That includes : > - checking the project belongs (or not) to JBT/JBDS > - checking there's a proper project description > - checking the projects are properly configured (I noticed some EARs are seen as 1.3 instead of 6.0) and compile without errors > - checking the projects deploy OOTB on AS7/EAP6 > > Regards, > > Fred Bricon > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

12 years, 5 months

1
0
0 / 0

Re: [jdf-dev] [jbosstools-dev] JDF Quickstarts in JBoss Central?

by Max Rydahl Andersen

On 09 Oct 2012, at 18:46, Snjezana Peco <snjeza.peco(a)gmail.com> wrote: > On 9.10.2012 18:34, Max Rydahl Andersen wrote: >> On 09 Oct 2012, at 18:25, Snjezana Peco <snjezana.peco(a)redhat.com> wrote: >> >>> It would be better to fix https://issues.jboss.org/browse/JBIDE-8452 >>> That way, we would be able to create project examples from git as well as other project examples, select a branch, tag, add requirements/fixes... >>> There are already a prototype for this issue (https://github.com/snjeza/jbossm2egit) that is necessary to upgrade to newer versions of m2e and EGit. >> Yes, but that wouldn't allow selective install either would it ? and the issues below with the run-as would still be there. >> >> note: I still think JBIDE-8452 should happen but not sure it solves the problem on its own ? > > JBIDE-8542 would enable creating a project example from git repository directly. > It would be possible to define a project example for any maven or eclipse project on some git repository. > it would be enough to declare a project example of the git type in the project example xml file, specify a branch or tag and add other standard project examples properties: fixes, tags... yes, but that doesn't apply for the quickstarts since their repo contain multiple projects. Or am I missing something ? /max > Snjeza >> /max >> >>> Snjeza >>> >>> On 9.10.2012 18:11, Fred Bricon wrote: >>>> Le 09/10/2012 17:43, Sande Gilda a écrit : >>>>> Fred, this looks really cool! >>>> Yeah I know :-) >>>>> I do have one question. You say "However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below." Is this a bug with JBoss or something else? Is there a JIRA or Bugzilla for this? >>>>> >>>> See https://issues.jboss.org/browse/JBIDE-473 >>>>> Pete, correct me if I'm wrong, but I believe the context root for the quickstarts was prefixed by jboss-as to make them unique and prevent them from overwriting existing deployments. for example "helloworld". It would be nice if the quickstarts worked the same way in JDBS as they do deployed in command line. >>>>> >>>> renaming the module directories to include the jboss-as prefix would actually fix the problem. >>>> >>>>> On 10/09/2012 11:14 AM, Fred Bricon wrote: >>>>>> Hi, >>>>>> >>>>>> we need to clean up the project examples in JBoss Tools 4.0/JBDS 6.0 (as part of https://issues.jboss.org/browse/JBIDE-12554). >>>>>> So, my idea was to replace all the old examples with the quickstarts from https://github.com/jboss-jdf/jboss-as-quickstart >>>>>> >>>>>> Since the quickstarts are not available as standalone zips, for consumption in JBT/JBDS, I created a script (https://github.com/fbricon/jboss-as-quickstart/commit/cb1a0638b352434c48c...) that does that, and it also generates a project example stub we can use almost directly in JBT. >>>>>> >>>>>> D:\Dev\GitHub\jboss-as-quickstart>mvn groovy:execute -N -Pzip-modules,requires-postgres,complex-dependencies,requires-full,requires-xts >>>>>> [INFO] Scanning for projects... >>>>>> [INFO] >>>>>> [INFO] ------------------------------------------------------------------------ >>>>>> [INFO] Building JBoss AS Quickstarts Parent 7.1.2-SNAPSHOT >>>>>> [INFO] ------------------------------------------------------------------------ >>>>>> [INFO] >>>>>> [INFO] --- gmaven-plugin:1.4:execute (default-cli) @ jboss-as-quickstarts-parent --- >>>>>> Starting zipping JBoss AS Quickstarts Parent modules >>>>>> Deleting D:\Dev\GitHub\jboss-as-quickstart\target\zips >>>>>> Zipped 51 quickstart modules >>>>>> Generating project examples descriptor for JBoss Tools >>>>>> [WARNING] module 'bmt' has a non matching artifactId 'jboss-as-bmt' >>>>>> [WARNING] module 'cdi-injection' has a non matching artifactId 'jboss-as-cdi-injection' >>>>>> [WARNING] module 'cdi-portable-extension' has a non matching artifactId 'jboss-as-cdi-portable-extension' >>>>>> [WARNING] module 'ejb-in-ear' has a non matching artifactId 'jboss-as-ejb-in-ear' >>>>>> [WARNING] module 'ejb-in-war' has a non matching artifactId 'jboss-as-ejb-in-war' >>>>>> [WARNING] module 'ejb-remote' has a non matching artifactId 'jboss-as-ejb-remote-parent' >>>>>> [WARNING] module 'ejb-security' has a non matching artifactId 'jboss-as-ejb-security' >>>>>> [WARNING] module 'greeter' has a non matching artifactId 'jboss-as-greeter' >>>>>> [WARNING] module 'helloworld' has a non matching artifactId 'jboss-as-helloworld' >>>>>> [WARNING] module 'helloworld-errai' has a non matching artifactId 'jboss-as-helloworld-errai' >>>>>> [WARNING] module 'helloworld-gwt' has a non matching artifactId 'jboss-as-helloworld-gwt' >>>>>> [WARNING] module 'helloworld-html5' has a non matching artifactId 'jboss-as-helloworld-html5' >>>>>> [WARNING] module 'helloworld-jms' has a non matching artifactId 'jboss-as-helloworld-jms' >>>>>> [WARNING] module 'helloworld-osgi' has a non matching artifactId 'jboss-as-helloworld-osgi' >>>>>> [WARNING] module 'helloworld-rs' has a non matching artifactId 'jboss-as-helloworld-rs' >>>>>> [WARNING] module 'helloworld-singleton' has a non matching artifactId 'jboss-as-helloworld-singleton' >>>>>> [WARNING] module 'hibernate3' has a non matching artifactId 'jboss-as-hibernate3' >>>>>> [WARNING] module 'hibernate4' has a non matching artifactId 'jboss-as-hibernate4' >>>>>> [WARNING] module 'kitchensink' has a non matching artifactId 'jboss-as-kitchensink' >>>>>> [WARNING] module 'kitchensink-ear' has a non matching artifactId 'jboss-as-kitchensink-ear' >>>>>> [WARNING] module 'kitchensink-html5-mobile' has a non matching artifactId 'jboss-as-kitchensink-html5-mobile' >>>>>> [WARNING] module 'kitchensink-jsp' has a non matching artifactId 'jboss-as-kitchensink-jsp' >>>>>> [WARNING] module 'kitchensink-ml' has a non matching artifactId 'jboss-as-kitchensink-ml' >>>>>> [WARNING] module 'kitchensink-ml-ear' has a non matching artifactId 'jboss-as-kitchensink-ml-ear' >>>>>> [WARNING] module 'log4j' has a non matching artifactId 'jboss-as-log4j' >>>>>> [WARNING] module 'logging-tools' has a non matching artifactId 'jboss-as-logging-tools' >>>>>> [WARNING] module 'mail' has a non matching artifactId 'jboss-as-mail' >>>>>> [WARNING] module 'numberguess' has a non matching artifactId 'jboss-as-numberguess' >>>>>> [WARNING] module 'payment-cdi-event' has a non matching artifactId 'jboss-as-payment-cdi-event' >>>>>> [WARNING] module 'richfaces-validation' has a non matching artifactId 'jboss-as-richfaces-validation' >>>>>> [WARNING] module 'servlet-async' has a non matching artifactId 'jboss-as-servlet-async' >>>>>> [WARNING] module 'servlet-filterlistener' has a non matching artifactId 'jboss-as-servlet-filterlistener' >>>>>> [WARNING] module 'servlet-security' has a non matching artifactId 'jboss-as-servlet-security' >>>>>> [WARNING] module 'tasks' has a non matching artifactId 'jboss-as-tasks' >>>>>> [WARNING] module 'tasks-jsf' has a non matching artifactId 'jboss-as-tasks-jsf' >>>>>> [WARNING] module 'temperature-converter' has a non matching artifactId 'jboss-as-temperature-converter' >>>>>> [WARNING] module 'tasks-rs' has a non matching artifactId 'jboss-as-tasks-rs' >>>>>> [WARNING] module 'wicket-ear' has a non matching artifactId 'jboss-as-wicket-ear-parent' >>>>>> [WARNING] module 'wicket-war' has a non matching artifactId 'jboss-as-wicket-war' >>>>>> [WARNING] module 'xml-jaxp' has a non matching artifactId 'jboss-as-xml-jaxp' >>>>>> [WARNING] module 'xml-dom4j' has a non matching artifactId 'jboss-as-xml-dom4j' >>>>>> [WARNING] module 'cmt' has a non matching artifactId 'jboss-as-cmt' >>>>>> [WARNING] module 'jts' has a non matching artifactId 'jboss-as-jts-parent' >>>>>> [WARNING] module 'jax-rs-client' has a non matching artifactId 'jboss-as-jax-rs-client' >>>>>> [WARNING] module 'inter-app' has a non matching artifactId 'jboss-as-inter-app-parent' >>>>>> [WARNING] module 'helloworld-mdb' has a non matching artifactId 'jboss-as-helloworld-mdb' >>>>>> [WARNING] module 'jta-crash-rec' has a non matching artifactId 'jboss-as-jta-crash-rec' >>>>>> [WARNING] module 'wsat-simple' has a non matching artifactId 'jboss-as-wsat-simple' >>>>>> [WARNING] module 'wsba-coordinator-completion-simple' has a non matching artifactId 'jboss-as-wsba-coordinator-completion-simple' >>>>>> [WARNING] module 'wsba-participant-completion-simple' has a non matching artifactId 'jboss-as-wsba-participant-completion-simple' >>>>>> D:\Dev\GitHub\jboss-as-quickstart\target\zips\quickstarts.xml generated >>>>>> >>>>>> >>>>>> [WARNING] 50 quickstart artifactIds mismatch with their folder name. >>>>>> This will prevent WTP from opening the proper url when running on a server. >>>>>> >>>>>> [INFO] ------------------------------------------------------------------------ >>>>>> [INFO] BUILD SUCCESS >>>>>> [INFO] ------------------------------------------------------------------------ >>>>>> [INFO] Total time: 5.506s >>>>>> [INFO] Finished at: Tue Oct 09 15:02:44 CEST 2012 >>>>>> [INFO] Final Memory: 11M/490M >>>>>> [INFO] ------------------------------------------------------------------------ >>>>>> >>>>>> As hinted in the log, the examples wouldn't quite work perfectly OOTB. http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_change_the_context_root_of_m... explains how the context root is inferred from the pom.xml by m2e-wtp. However our own JBoss AS server adapter ignores the WTP project context root and bases its deployment on the project name, leading to 404s as seen in the video below. >>>>>> >>>>>> End result in JBT / Central : http://www.screencast.com/users/fbricon/folders/Jing/media/464f8246-84bc-... >>>>>> >>>>>> Now. >>>>>> * are you guys ok to actually remove and replace the old examples with the JDF quickstarts >>>>>> * if you're ok, I'll setup a CI job to deploy the quickstarts to download.jboss.org >>>>>> * who's willing to give me a hand in validating the quickstarts properly work in JBT/JBDS. That includes : >>>>>> - checking the project belongs (or not) to JBT/JBDS >>>>>> - checking there's a proper project description >>>>>> - checking the projects are properly configured (I noticed some EARs are seen as 1.3 instead of 6.0) and compile without errors >>>>>> - checking the projects deploy OOTB on AS7/EAP6 >>>>>> >>>>>> Regards, >>>>>> >>>>>> Fred Bricon >>>>>> >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

12 years, 5 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

jdf-dev October 2012