If there are better examples than the current ones, please nominate them!

On Oct 9, 2012, at 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...) > <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 <http://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 >

Le 09/10/2012 17:39, Burr Sutter a écrit : > If there are better examples than the current ones, please nominate them! > The "old" examples from previous JBT versions and still available until now use old/incomplete descriptors. There are literally dozens of them that need to be tested against JBT4, which represents a significant effort. Many examples relate to ESB (or other technologies) and I don't think they should be included in JBT anymore, but rather contributed by some SOA plugins. Likewise, identifying the JDF examples deserving to appear in JBT is no small feat, so I hoped this thread would help me gather some informations on what exactly we want to show the end-users. > > On Oct 9, 2012, at 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 >> > _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

Pete, have you decided a strategy to handle the directory/project rename? I started scripting a folder rename as it seems easier to me. @Rafael, you broke the quickstarts with https://github.com/jboss-jdf/jboss-as-quickstart/commit/a4f9bbba5218b71d1... : projects don't compile anymore $ mvn clean [INFO] Scanning for projects... Downloading: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... with-tools-${version.org.jboss.bom}.pom Downloading: http://repo.maven.apache.org/maven2/org/jboss/bom/jboss-javaee-6.0-with-t... oss.bom}.pom Downloading: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... -javaee-web-6.0-${version.org.jboss.spec.jboss.javaee.6.0}.pom Downloading: http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-web-6.0/$... rg.jboss.spec.jboss.javaee.6.0}.pom [ERROR] The build could not read 2 projects -> [Help 1] [ERROR] [ERROR] The project org.jboss.as.quickstarts:jboss-as-helloworld-html5:7.1.2-SNAPSHOT (D:\Dev\GitHub\jboss-as-quickstart\helloworld-html5\pom.xml) has 8 error s [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:${version.org.jboss.bom} from/to jboss-public-r epository (https://repository.jboss.org/nexus/content/groups/public-jboss/): IllegalArgumentException @ line 53, column 25: Illegal character in path at index 1 06: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... s-${version.org.jboss.bom}.pom -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 67, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 75, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 83, column 21 [ERROR] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-war-plugin must be a valid version but is '${version.war.plugin}'. @ line 97, colu mn 26 [ERROR] 'build.plugins.plugin.version' for org.jboss.as.plugins:jboss-as-maven-plugin must be a valid version but is '${version.org.jboss.as.plugins.maven.p lugin}'. @ line 108, column 26 [ERROR] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin must be a valid version but is '${version.compiler.plugin}'. @ lin e 114, column 26 [ERROR] 'build.plugins.plugin.version' for com.mycila.maven-license-plugin:maven-license-plugin must be a valid version but is '${version.license.plugin}'. @ line 124, column 26 [ERROR] [ERROR] The project org.jboss.as.quickstarts:jboss-as-kitchensink-html5-mobile:7.1.2-SNAPSHOT (D:\Dev\GitHub\jboss-as-quickstart\kitchensink-html5-mobile\pom. xml) has 8 errors [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-web-6.0:pom:${version.org.jboss.spec.jboss.javaee.6.0} from/to jb oss-public-repository (https://repository.jboss.org/nexus/content/groups/public-jboss/): IllegalArgumentException @ line 80, column 25: Illegal character in pat h at index 100: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... oss-javaee-web-6.0-${version.org.jboss.spec.jboss.javaee.6.0}.pom -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 94, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 101, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 108, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 115, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 122, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar is missing. @ line 129, column 21 [ERROR] 'build.plugins.plugin.version' for org.jboss.as.plugins:jboss-as-maven-plugin must be a valid version but is '${version.org.jboss.as.plugins.maven.p lugin}'. @ line 214, column 26 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Le 10/10/2012 13:54, Pete Muir a écrit : > Fred, > > I think the way to do this is: > > 1) define some quickstarts as "promoted" - those that are relevant to a developer, today. Relevance could be based on a large existing userbase, or the fact that the technology is new and upcoming. How about we aim for 15 promoted quickstarts? > 2) display only the promoted quickstarts in JBDS > 3) revisit what is promoted regularly, eg. every 6 months > > At some point, we should actually encode this into the quickstart metadata. > > For now, let's do it manually. > > 1) helloworld > 2) greeter > 3) numberguess > 4) kitchensink > 5) kitchensink-html5-mobile > 6) helloworld-errai > 7) helloworld-jsf (renaming to helloworld-richfaces sometime soon > 8) tasks-rs > 9) tasks-jsf > 10) helloworld-rs > 11) kitchensink-cordova > 12) carmart > 13) carmart-transactional > 14) forge-from-scratch > 15) helloworld-jms > > WDYT? > > On 9 Oct 2012, at 17:08, Fred Bricon wrote: > >> Le 09/10/2012 17:39, Burr Sutter a écrit : >>> If there are better examples than the current ones, please nominate them! >>> >> The "old" examples from previous JBT versions and still available until now use old/incomplete descriptors. There are literally dozens of them that need to be tested against JBT4, which represents a significant effort. Many examples relate to ESB (or other technologies) and I don't think they should be included in JBT anymore, but rather contributed by some SOA plugins. >> >> Likewise, identifying the JDF examples deserving to appear in JBT is no small feat, so I hoped this thread would help me gather some informations on what exactly we want to show the end-users. >> >>> On Oct 9, 2012, at 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 >>>> >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev

Pete, have you decided a strategy to handle the directory/project rename? I started scripting a folder rename as it seems easier to me. @Rafael, you broke the quickstarts with https://github.com/jboss-jdf/jboss-as-quickstart/commit/a4f9bbba5218b71d1... : projects don't compile anymore $ mvn clean [INFO] Scanning for projects... Downloading: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... with-tools-${version.org.jboss.bom}.pom Downloading: http://repo.maven.apache.org/maven2/org/jboss/bom/jboss-javaee-6.0-with-t... oss.bom}.pom Downloading: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... -javaee-web-6.0-${version.org.jboss.spec.jboss.javaee.6.0}.pom Downloading: http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-web-6.0/$... rg.jboss.spec.jboss.javaee.6.0}.pom [ERROR] The build could not read 2 projects -> [Help 1] [ERROR] [ERROR] The project org.jboss.as.quickstarts:jboss-as-helloworld-html5:7.1.2-SNAPSHOT (D:\Dev\GitHub\jboss-as-quickstart\helloworld-html5\pom.xml) has 8 error s [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:${version.org.jboss.bom} from/to jboss-public-r epository (https://repository.jboss.org/nexus/content/groups/public-jboss/): IllegalArgumentException @ line 53, column 25: Illegal character in path at index 1 06: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... s-${version.org.jboss.bom}.pom -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 67, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 75, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 83, column 21 [ERROR] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-war-plugin must be a valid version but is '${version.war.plugin}'. @ line 97, colu mn 26 [ERROR] 'build.plugins.plugin.version' for org.jboss.as.plugins:jboss-as-maven-plugin must be a valid version but is '${version.org.jboss.as.plugins.maven.p lugin}'. @ line 108, column 26 [ERROR] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin must be a valid version but is '${version.compiler.plugin}'. @ lin e 114, column 26 [ERROR] 'build.plugins.plugin.version' for com.mycila.maven-license-plugin:maven-license-plugin must be a valid version but is '${version.license.plugin}'. @ line 124, column 26 [ERROR] [ERROR] The project org.jboss.as.quickstarts:jboss-as-kitchensink-html5-mobile:7.1.2-SNAPSHOT (D:\Dev\GitHub\jboss-as-quickstart\kitchensink-html5-mobile\pom. xml) has 8 errors [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-web-6.0:pom:${version.org.jboss.spec.jboss.javaee.6.0} from/to jb oss-public-repository (https://repository.jboss.org/nexus/content/groups/public-jboss/): IllegalArgumentException @ line 80, column 25: Illegal character in pat h at index 100: https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/... oss-javaee-web-6.0-${version.org.jboss.spec.jboss.javaee.6.0}.pom -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 94, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 101, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 108, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 115, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 122, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar is missing. @ line 129, column 21 [ERROR] 'build.plugins.plugin.version' for org.jboss.as.plugins:jboss-as-maven-plugin must be a valid version but is '${version.org.jboss.as.plugins.maven.p lugin}'. @ line 214, column 26 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Le 10/10/2012 13:54, Pete Muir a écrit : > Fred, > > I think the way to do this is: > > 1) define some quickstarts as "promoted" - those that are relevant to > a developer, today. Relevance could be based on a large existing > userbase, or the fact that the technology is new and upcoming. How > about we aim for 15 promoted quickstarts? > 2) display only the promoted quickstarts in JBDS > 3) revisit what is promoted regularly, eg. every 6 months > > At some point, we should actually encode this into the quickstart > metadata. > > For now, let's do it manually. > > 1) helloworld > 2) greeter > 3) numberguess > 4) kitchensink > 5) kitchensink-html5-mobile > 6) helloworld-errai > 7) helloworld-jsf (renaming to helloworld-richfaces sometime soon > 8) tasks-rs > 9) tasks-jsf > 10) helloworld-rs > 11) kitchensink-cordova > 12) carmart > 13) carmart-transactional > 14) forge-from-scratch > 15) helloworld-jms > > WDYT? > > On 9 Oct 2012, at 17:08, Fred Bricon wrote: > >> Le 09/10/2012 17:39, Burr Sutter a écrit : >>> If there are better examples than the current ones, please nominate >>> them! >>> >> The "old" examples from previous JBT versions and still available >> until now use old/incomplete descriptors. There are literally dozens >> of them that need to be tested against JBT4, which represents a >> significant effort. Many examples relate to ESB (or other >> technologies) and I don't think they should be included in JBT >> anymore, but rather contributed by some SOA plugins. >> >> Likewise, identifying the JDF examples deserving to appear in JBT is >> no small feat, so I hoped this thread would help me gather some >> informations on what exactly we want to show the end-users. >> >>> On Oct 9, 2012, at 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 >>>> >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev

Fred, this looks really cool!

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?

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.

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...) > <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 >

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.

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

On 9.10.2012 18:34, Max Rydahl Andersen wrote: > On 09 Oct 2012, at 18:25, Snjezana Peco <snjezana.peco(a)redhat.com&gt; 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...

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

Le 09/10/2012 19:04, Max Rydahl Andersen a écrit : > On 09 Oct 2012, at 18:46, Snjezana Peco <snjeza.peco(a)gmail.com&gt; 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&gt; 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 ? I still believe this needs to be implemented upstream, as I said in JBIDE-8452.

Anyway, that wouldn't guarantee the problem'd be solved : When checked out under the workspace, projects can't be renamed.

>> 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. Yes > 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 > _______________________________________________ > 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

>> 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.

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

On 9.10.2012 19:37, Max Rydahl Andersen wrote: >>>> 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 ? Currently, the JBoss Git Integration clones the git repo and imports only a declared project example to the workspace. For instance, the jboss-as quickstart repo is about 35MB and needs to be cloned only once. If it is possible to clone/import a partial repository (maybe using the github API), we can add such a feature. Anyway, the project examples of the git type would be an additional feature within the project examples that would be, in my opinion, very useful.

Snjeza >> 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 > > _______________________________________________ > 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

moving this of jdf list since not really related to their problem right now. >> Currently, the JBoss Git Integration clones the git repo and >> imports >> only a declared project example to the workspace. >> For instance, the jboss-as quickstart repo is about 35MB and needs >> to >> be >> cloned only once. >> If it is possible to clone/import a partial repository (maybe >> using >> the >> github API), we can add such a feature. >> Anyway, the project examples of the git type would be an >> additional >> feature within the project examples that would be, in my opinion, >> very >> useful. > > I wonder about that. Typically, you'd want a quickstart that is > compatible with the runtime version you are working with. In > order to do something like this with git, you'd need to specify > the tag that corresponds to each release version. thats not really different from wether you use a zip, maven artifact or something else. > Also, when you clone, you're creating a local repo on the user's > machine. Not sure I'd want that if I simply wanted to look at a > quickstart. Wouldn't it be better to download a blob (i.e. the > zip associated with the tag) instead of cloning the repo? The nice thing about the above git integration is that you actually get a git repo directly you can work on, commit into etc. with history if you want to.

/max > >> >> Snjeza >> >>>> 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 >>> >>> _______________________________________________ >>> 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 >>

>> >> The nice thing about the above git integration is that you actually >> get a git repo directly you can work on, commit into etc. with >> history if you want to. > > I think if you were going that route, you'd clone the repo and import. If I just wanted to look at a quickstart, I'd be a little upset if importing one also stashed a whole git repo on my hard drive. If that is an option, that's fine, but if that's the default behavior, I think you're going to end up pissing people off. well sure - default could be it just git clones and then deletes the non-relevant parts afterwards.

/max _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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...

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&gt; > 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

> 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&gt; >> 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 >

>> 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 I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;)

>> 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. > Yes, it would. That, or losing the jboss-as prefix. >> >> 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 >>> >> > _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

On 10/09/2012 12:32 PM, Max Rydahl Andersen wrote: >>>> 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 >> I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;) > not really - problem is that jboss-web.xml is not a reliable source to get it from since it depends on how/where its deployed. > > But the quickstarts could for now add: > > <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> > > and m2e would be able to adjust it afaik. Is this added to the jboss-web.xml file? Very few of the quickstarts have a jboss-web.xml file. > I'm surprised they ever were renamed with jboss-web.xml since that would break its usage instantly from tools...or the "test from jboss tools" was missed when doing that fix ;( Pete, correct me if I'm wrong, but I believe this tag <finalName>jboss-as-QUICKSTART_NAME></finalName> in the pom.xml file is how the context is set.

> /max > >>>> 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. >>> >> Yes, it would. That, or losing the jboss-as prefix. >>>> 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 >>>>> >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

>>> >>> But the quickstarts could for now add: >>> >>> <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> >>> >>> and m2e would be able to adjust it afaik. >> Is this added to the jboss-web.xml file? Very few of the >> quickstarts >> have a jboss-web.xml file. >> >>> I'm surprised they ever were renamed with jboss-web.xml since >>> that would break its usage instantly from tools...or the "test >>> from jboss tools" was missed when doing that fix ;( >> Pete, correct me if I'm wrong, but I believe this tag >> <finalName>jboss-as-QUICKSTART_NAME></finalName> in the pom.xml >> file is >> how the context is set. > > Right. > > There is generally no convention that the maven artifact id must be > the same as the directory name of the project must be the same as > the context root. This is something that Eclipse/JBoss Tools/m2e > adds as a requirement. problem is there isn't a good place to get the "right" info from.

> To date, we've followed the rule that the artifact id (which > translates to project name in eclipse) must be the same as the > context root, but that the directory name can be different. > > This seems to work for me in Eclipse/m2e/JBoss Tools, and I don't > really want to change all quickstart directory names, it's going > to make them harder to explore. > > Can we check what the actual problem is here? Yes, thinking about it i'm not grokking if the problem Fred sees is related to just the groovy/project examples or also a problem for when importing the quickstarts ? if also a problem for quickstarts my suggestion is to put in <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> if only for the groovy/projectexamples then yeah...why ? :) /max _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Le 10/10/2012 04:35, Pete Muir a écrit : > On 9 Oct 2012, at 09:45, Sande Gilda wrote: > >> On 10/09/2012 12:32 PM, Max Rydahl Andersen wrote: >>>>>> 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 >>>> I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;) >>> not really - problem is that jboss-web.xml is not a reliable source to get it from since it depends on how/where its deployed. >>> >>> But the quickstarts could for now add: >>> >>> <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> >>> >>> and m2e would be able to adjust it afaik. >> Is this added to the jboss-web.xml file? Very few of the quickstarts >> have a jboss-web.xml file. >> >>> I'm surprised they ever were renamed with jboss-web.xml since that would break its usage instantly from tools...or the "test from jboss tools" was missed when doing that fix ;( >> Pete, correct me if I'm wrong, but I believe this tag >> <finalName>jboss-as-QUICKSTART_NAME></finalName> in the pom.xml file is >> how the context is set. > Right. > > There is generally no convention that the maven artifact id must be the same as the directory name of the project must be the same as the context root. This is something that Eclipse/JBoss Tools/m2e adds as a requirement. > > To date, we've followed the rule that the artifact id (which translates to project name in eclipse) must be the same as the context root, but that the directory name can be different. > > This seems to work for me in Eclipse/m2e/JBoss Tools, and I don't really want to change all quickstart directory names, it's going to make them harder to explore. > > Can we check what the actual problem is here? When the project you import is directly located in your workspace folder, the project name in eclipse must match the folder name. This is a limitation in Eclipse. So when we import quickstarts in the workspace (the default behaviour), eclipse uses the folder name, not the artifact id The context root is set by m2e-wtp according to the maven rules. WTP uses it to open a browser when it receives the signal the app deployment is complete. However, the AS server adapter in JBT does not respect the context root as declared in the project, deploys it using the project name in the workspace instead. This mismatch between war file and context root leads to a 404. Easiest/cheapest solution here (by far) is to add a <finalName> in the pom.xmls that matches the folder name. Leads to shorter context name, leads to less typing, leads to developer happiness.

>>> /max >>> >>>>>> 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. >>>>> >>>> Yes, it would. That, or losing the jboss-as prefix. >>>>>> 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 >>>>>>> >>>> _______________________________________________ >>>> jdf-dev mailing list >>>> jdf-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev > > _______________________________________________ > jdf-dev mailing list > jdf-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jdf-dev

Le 11/10/2012 17:54, Pete Muir a écrit : > On 11 Oct 2012, at 16:48, Fred Bricon wrote: > >> Le 10/10/2012 04:35, Pete Muir a écrit : >>> On 9 Oct 2012, at 09:45, Sande Gilda wrote: >>> >>>> On 10/09/2012 12:32 PM, Max Rydahl Andersen wrote: >>>>>>>> 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 >>>>>> I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;) >>>>> not really - problem is that jboss-web.xml is not a reliable source to get it from since it depends on how/where its deployed. >>>>> >>>>> But the quickstarts could for now add: >>>>> >>>>> <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> >>>>> >>>>> and m2e would be able to adjust it afaik. >>>> Is this added to the jboss-web.xml file? Very few of the quickstarts >>>> have a jboss-web.xml file. >>>> >>>>> I'm surprised they ever were renamed with jboss-web.xml since that would break its usage instantly from tools...or the "test from jboss tools" was missed when doing that fix ;( >>>> Pete, correct me if I'm wrong, but I believe this tag >>>> <finalName>jboss-as-QUICKSTART_NAME></finalName> in the pom.xml file is >>>> how the context is set. >>> Right. >>> >>> There is generally no convention that the maven artifact id must be the same as the directory name of the project must be the same as the context root. This is something that Eclipse/JBoss Tools/m2e adds as a requirement. >>> >>> To date, we've followed the rule that the artifact id (which translates to project name in eclipse) must be the same as the context root, but that the directory name can be different. >>> >>> This seems to work for me in Eclipse/m2e/JBoss Tools, and I don't really want to change all quickstart directory names, it's going to make them harder to explore. >>> >>> Can we check what the actual problem is here? >> When the project you import is directly located in your workspace folder, the project name in eclipse must match the folder name. This is a limitation in Eclipse. So when we import quickstarts in the workspace (the default behaviour), eclipse uses the folder name, not the artifact id >> >> The context root is set by m2e-wtp according to the maven rules. WTP uses it to open a browser when it receives the signal the app deployment is complete. However, the AS server adapter in JBT does not respect the context root as declared in the project, deploys it using the project name in the workspace instead. This mismatch between war file and context root leads to a 404. >> >> Easiest/cheapest solution here (by far) is to add a <finalName> in the pom.xmls that matches the folder name. Leads to shorter context name, leads to less typing, leads to developer happiness. > Except that this will break the maven import. Why?

From experience, here the artifact id must be the same as the context root.

> >>>>> /max >>>>> >>>>>>>> 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. >>>>>>> >>>>>> Yes, it would. That, or losing the jboss-as prefix. >>>>>>>> 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 >>>>>>>>> >>>>>> _______________________________________________ >>>>>> jdf-dev mailing list >>>>>> jdf-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>> _______________________________________________ >>>> jdf-dev mailing list >>>> jdf-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>> _______________________________________________ >>> jdf-dev mailing list >>> jdf-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jdf-dev

On jeudi 11 octobre 2012 18:02:57, Pete Muir wrote: > > On 11 Oct 2012, at 16:59, Fred Bricon wrote: > >> Le 11/10/2012 17:54, Pete Muir a écrit : >>> On 11 Oct 2012, at 16:48, Fred Bricon wrote: >>> >>>> Le 10/10/2012 04:35, Pete Muir a écrit : >>>>> On 9 Oct 2012, at 09:45, Sande Gilda wrote: >>>>> >>>>>> On 10/09/2012 12:32 PM, Max Rydahl Andersen wrote: >>>>>>>>>> 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 >>>>>>>> I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;) >>>>>>> not really - problem is that jboss-web.xml is not a reliable source to get it from since it depends on how/where its deployed. >>>>>>> >>>>>>> But the quickstarts could for now add: >>>>>>> >>>>>>> <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> >>>>>>> >>>>>>> and m2e would be able to adjust it afaik. >>>>>> Is this added to the jboss-web.xml file? Very few of the quickstarts >>>>>> have a jboss-web.xml file. >>>>>> >>>>>>> I'm surprised they ever were renamed with jboss-web.xml since that would break its usage instantly from tools...or the "test from jboss tools" was missed when doing that fix ;( >>>>>> Pete, correct me if I'm wrong, but I believe this tag >>>>>> <finalName>jboss-as-QUICKSTART_NAME></finalName> in the pom.xml file is >>>>>> how the context is set. >>>>> Right. >>>>> >>>>> There is generally no convention that the maven artifact id must be the same as the directory name of the project must be the same as the context root. This is something that Eclipse/JBoss Tools/m2e adds as a requirement. >>>>> >>>>> To date, we've followed the rule that the artifact id (which translates to project name in eclipse) must be the same as the context root, but that the directory name can be different. >>>>> >>>>> This seems to work for me in Eclipse/m2e/JBoss Tools, and I don't really want to change all quickstart directory names, it's going to make them harder to explore. >>>>> >>>>> Can we check what the actual problem is here? >>>> When the project you import is directly located in your workspace folder, the project name in eclipse must match the folder name. This is a limitation in Eclipse. So when we import quickstarts in the workspace (the default behaviour), eclipse uses the folder name, not the artifact id >>>> >>>> The context root is set by m2e-wtp according to the maven rules. WTP uses it to open a browser when it receives the signal the app deployment is complete. However, the AS server adapter in JBT does not respect the context root as declared in the project, deploys it using the project name in the workspace instead. This mismatch between war file and context root leads to a 404. >>>> >>>> Easiest/cheapest solution here (by far) is to add a <finalName> in the pom.xmls that matches the folder name. Leads to shorter context name, leads to less typing, leads to developer happiness. >>> Except that this will break the maven import. >> Why? > > From experience, here the artifact id must be the same as the context root. You should try again then :-) Only what you code in your app might lead to such constraint. And that would be a baaad thing

>>> >>>>>>> /max >>>>>>> >>>>>>>>>> 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. >>>>>>>>> >>>>>>>> Yes, it would. That, or losing the jboss-as prefix. >>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> jdf-dev mailing list >>>>>>>> jdf-dev(a)lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>>>> _______________________________________________ >>>>>> jdf-dev mailing list >>>>>> jdf-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>>> _______________________________________________ >>>>> jdf-dev mailing list >>>>> jdf-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> >

The context root is set by m2e-wtp according to the maven rules. WTP uses it to open a browser when it receives the signal the app deployment is complete. However, the AS server adapter in JBT does not respect the context root as declared in the project, deploys it using the project name in the workspace instead.

This mismatch between war file and context root leads to a 404.

>>>> 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 >> >> I interpret this to mean there is no intent to fix the issue. Am I reading it correctly? ;) > > not really - problem is that jboss-web.xml is not a reliable source to get it from since it depends on how/where its deployed. > > But the quickstarts could for now add: > > <m2eclipse.wtp.contextRoot>jboss-as-whatever</m2eclipse.wtp.contextRoot> > > and m2e would be able to adjust it afaik. > > I'm surprised they ever were renamed with jboss-web.xml since that would break its usage instantly from tools...or the "test from jboss tools" was missed when doing that fix ;( Quickstarts don't use jboss-web.xml to get a context name, they use the artifact id/war name.

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

> 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 _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

I didn't know about that one. I see you're point but I'd still prefer using one zip / example, it'd be more efficient, I think. JBIDE-12554 is marked as closed. You should probably open a new one.

On mardi 9 octobre 2012 17:14:29, 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...) > <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 > > > > _______________________________________________ > jdf-dev mailing list > jdf-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

Could we leave the git-backed examples discussion aside for a moment, as this is really an orthogonal issue that deserves another thread. My main concern is : what examples do we want to ship in JBT 4 / JBDS 6 - are you guys ok to add the JDF ones? If so which ones? should they appear in central? if so which ones? - If you guys want to keep (some of) the old examples, which ones? Fred Le 09/10/2012 19:18, Max Rydahl Andersen a écrit : >> I didn't know about that one. I see you're point but I'd still prefer >> using one zip / example, it'd be more efficient, I think. >> JBIDE-12554 is marked as closed. You should probably open a new one. > his point is that since its downloaded via maven the zip only needs to be fetched once. > >> On mardi 9 octobre 2012 17:14:29, 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...) >>> <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 >>> >>> >>> >>> _______________________________________________ >>> jdf-dev mailing list >>> jdf-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

> file:/D:/Dev/GitHub/jboss-as-quickstart/target/zips/quickstarts.xml - JBoss Developer Framework My biggest problem with including the full long list from JDF is that its app version specific aren't they? these have dependencies to just AS7, not to the EAP6 boms, right ? So would need one set for JBT in community examples, and another one in JBDS ?

On 10 Oct 2012, at 11:44, Max Rydahl Andersen wrote: >> file:/D:/Dev/GitHub/jboss-as-quickstart/target/zips/quickstarts.xml - JBoss Developer Framework > My biggest problem with including the full long list from JDF is that its app version specific aren't they? these have dependencies to just AS7, not to the EAP6 boms, right ? > > So would need one set for JBT in community examples, and another one in JBDS ? The only difference should be the BOM version, which is overridable via a property. So you could use the same version, and set the flag on the project?