[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11714: --------------------------------------------- I don't even think we need anything special. http://maven.apache.org/plugins/maven-dependency-plugin/get-mojo.html might be enough if we can make it only download if needed and not at every invocation of mvn. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11714: ------------------------------------ Bear in mind we have a job that fetches and unpacks everything so it can be ref'd outside Jenkins for reuse and disk speed. https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... Would a fully maven solution also be able to achieve NFS-mounted outside-Jenkins bootstrapping? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11714: --------------------------------------------- yes - the location where you get it from would be just a directory/url which you can point to anywhere.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-11714: ------------------------------------- Location of unpacked requirement is /requirements/target. Examples: - for job jsf.bot.tests on Hudson it's /home/hudson/workspace/jsf.bot.tests/requirements/target - for locally run maven build run from ../trunk/requirements/target it's ../trunk/requirements/target -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11714: ---------------------------------------- Found it: a swtbot.properties file is generated at each build and contains info about runtime configurations to use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11714: --------------------------------------------- how about we actually put the internal runtimes we need into to a maven structure on a server somewhere so we could use those for download? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11714: --------------------------------------------- i.e. I really don't want to have us maintain multiple copies of boilerplate ant code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11714: ------------------------------------ Many of these runtime requirement builders use a shared script, only passing in different properties: http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbeap/ http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas-4.2.... http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas-7.1.... etc. Deviations from the "use generic/common downloader" approach are for the cases where a single req fetcher/builder is made to handle more than one download: http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/soap/ http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas/ Or where the fetching process requires some special steps: http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.0.1.GA/ http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.3.0/ Because of differences, I question the benefit to porting all this to maven simply so that a single component can bootstrap itself. This already happens via the test harness. If a requirements.properties file is found, those requirement builders fire locally, fetch what's needed, and the tests proceed. In Jenkins, however, they can benefit from a pre-bootstrapped cache of these files so the download's faster/easier. Simply switching to maven to fetch zips (and unpack them)... what would the gain be? Sounds a bit like "I don't like American, let's speak English instead": same conversation, but with slightly different words. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11714: ----------------------------------- Attachment: JBIDE-11714-ws-sample.patch This is a sample patch on "ws" tests that shows the described alternative approach for runtime. What it cost: * ~10 lines in pom.xml What it brings; * Caching (in Maven repo) -> download once * No more requirements.properties, all conf in pom.xml * Tests work without requirements/ folder In general, less constraints, less magic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11714 at 5/15/12 10:37 AM: ------------------------------------------------------------------ Lost of files to replace by get-mojo or unpack-mojo in their pom: ./maven/tests/org.jboss.tools.maven.ui.bot.test/requirements.properties ./smooks/tests/org.jboss.tools.smooks.ui.bot.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.ui.test/requirements.properties ./runtime-soa/tests/org.jboss.tools.runtime.soa.test/requirements.properties ./vpe/tests/org.jboss.tools.vpe.ui.bot.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.ui.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.test/requirements.properties ./runtime/tests/org.jboss.tools.runtime.test/requirements.properties ./examples/tests/org.jboss.tools.project.examples.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.ui.bot.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.core.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.bot.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.seam3.bot.test/requirements.properties ./jsf/tests/org.jboss.tools.jsf.ui.bot.test/requirements.properties -./central/tests/org.jboss.tools.central.test.ui.bot/requirements.properties- DONE ./jbpm/tests/org.jboss.tools.jbpm.ui.bot.test/requirements.properties -./ws/tests/org.jboss.tools.ws.creation.core.test/requirements.properties- DONE -./ws/tests/org.jboss.tools.ws.ui.bot.test/requirements.properties- DONE ./esb/tests/org.jboss.tools.esb.ui.bot.test/requirements.properties ./esb/tests/org.jboss.tools.esb.project.core.test/requirements.properties was (Author: mickael_istria): Lost of files to replace by get-mojo or unpack-mojo in their pom: ./maven/tests/org.jboss.tools.maven.ui.bot.test/requirements.properties ./smooks/tests/org.jboss.tools.smooks.ui.bot.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.ui.test/requirements.properties ./runtime-soa/tests/org.jboss.tools.runtime.soa.test/requirements.properties ./vpe/tests/org.jboss.tools.vpe.ui.bot.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.ui.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.test/requirements.properties ./runtime/tests/org.jboss.tools.runtime.test/requirements.properties ./examples/tests/org.jboss.tools.project.examples.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.ui.bot.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.core.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.bot.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.seam3.bot.test/requirements.properties ./jsf/tests/org.jboss.tools.jsf.ui.bot.test/requirements.properties ./central/tests/org.jboss.tools.central.test.ui.bot/requirements.properties ./jbpm/tests/org.jboss.tools.jbpm.ui.bot.test/requirements.properties -./ws/tests/org.jboss.tools.ws.creation.core.test/requirements.properties- DONE -./ws/tests/org.jboss.tools.ws.ui.bot.test/requirements.properties- DONE ./esb/tests/org.jboss.tools.esb.ui.bot.test/requirements.properties ./esb/tests/org.jboss.tools.esb.project.core.test/requirements.properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11714: ---------------------------------------- You end by multiple GAV <artifactItem> in the <artifactItems> element. In the specific case of this test, it's in the swtbot.properties file. Some other tests directly use systemProperties in pom. The "managed by Ant and requirements.properties" approach downloads and unzips in [root]/requirements/target. However, since there is one copy of requirements/ for each job, it is not shared on Hudson. Locally, if you use the same requirements/ folder, unzipped version are shared (I guess). With Maven, you share only zipped version, in the M2_REPO. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11714 at 5/16/12 7:06 AM: ----------------------------------------------------------------- Very good questions! I just gave a try and here are some good answers. That's true. We could then think about using another location for the output, and make it configurable through a property (as it is with the former approach). Are there cases where we run all SWTBot tests? About concrete/technical points: # maven-dependency-plugin uses markers to not perform on a place where is just performed: if no change happened in M2_REPO between 2 invocations of this plugin, it keeps what it did in first run. Then the second execution does nothing except telling the dependency is already here # You download only once, whether you are offline or not: Maven repo acts as a cache. If you run "mvn clean install" they you get a new "unpack". If we unpack in another folder (not in target/) then "clean" won't remove it, and we keep it forever. Currently "mvn clean install" ensures you have a clean server, "mvn install" keeps the previous one. It should be OK for everybody # So I tried a "mvn -o install", here is what I got: {code} NFO] --- maven-dependency-plugin:2.4:unpack (unpack) @ org.jboss.tools.jsf.ui.bot.test --- [INFO] Configured Artifact: org.jboss.as:jboss-as-dist:7.0.2.Final:zip artifact1 = /home/mistria/.m2/repository/org/jboss/as/jboss-as-dist/7.0.2.Final/jboss-as-dist-7.0.2.Final.zip marker = /home/mistria/workspaceJBossTools/jboss-tools-eclipse-repository/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/dependency-maven-plugin-markers/org.jboss.as-jboss-as-dist-zip-7.0.2.Final.marker artifact1 lastModified: 1337159586000 marker lastModified: 1337159586000 < false = marker older than artifact? [INFO] Configured Artifact: org.richfaces:richfaces-distribution:4.2.1.Final:zip artifact1 = /home/mistria/.m2/repository/org/richfaces/richfaces-distribution/4.2.1.Final/richfaces-distribution-4.2.1.Final.zip marker = /home/mistria/workspaceJBossTools/jboss-tools-eclipse-repository/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/dependency-maven-plugin-markers/org.richfaces-richfaces-distribution-zip-4.2.1.Final.marker artifact1 lastModified: 1337159780000 marker lastModified: 1337159780000 < false = marker older than artifact? [INFO] jboss-as-dist-7.0.2.Final.zip already unpacked. [INFO] richfaces-distribution-4.2.1.Final.zip already unpacked. {code} As you can see: # When you have the dependency in your M2_REPO, you can work offline and maven-dependency-plugin behaves well # When you do not clean, you keep the previous install I admit I did not expected the plugin to behave so well! was (Author: mickael_istria): Very good questions! I just gave a try and here are some good answers. That's true. We could then think about using another location for the output, and make it configurable through a property (as it is with the former approach). Are there cases where we run all SWTBot tests? # maven-dependency-plugin uses markers to not perform on a place where is just performed: if no change happened in M2_REPO between 2 invocations of this plugin, it keeps what it did in first run. Then the second execution does nothing except telling the dependency is already here # You download only once, whether you are offline or not: Maven repo acts as a cache. If you run "mvn clean install" they you get a new "unpack". If we unpack in another folder (not in target/) then "clean" won't remove it, and we keep it forever. Currently "mvn clean install" ensures you have a clean server, "mvn install" keeps the previous one. It should be OK for everybody # So I tried a "mvn -o install", here is what I got: {code} NFO] --- maven-dependency-plugin:2.4:unpack (unpack) @ org.jboss.tools.jsf.ui.bot.test --- [INFO] Configured Artifact: org.jboss.as:jboss-as-dist:7.0.2.Final:zip artifact1 = /home/mistria/.m2/repository/org/jboss/as/jboss-as-dist/7.0.2.Final/jboss-as-dist-7.0.2.Final.zip marker = /home/mistria/workspaceJBossTools/jboss-tools-eclipse-repository/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/dependency-maven-plugin-markers/org.jboss.as-jboss-as-dist-zip-7.0.2.Final.marker artifact1 lastModified: 1337159586000 marker lastModified: 1337159586000 < false = marker older than artifact? [INFO] Configured Artifact: org.richfaces:richfaces-distribution:4.2.1.Final:zip artifact1 = /home/mistria/.m2/repository/org/richfaces/richfaces-distribution/4.2.1.Final/richfaces-distribution-4.2.1.Final.zip marker = /home/mistria/workspaceJBossTools/jboss-tools-eclipse-repository/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/dependency-maven-plugin-markers/org.richfaces-richfaces-distribution-zip-4.2.1.Final.marker artifact1 lastModified: 1337159780000 marker lastModified: 1337159780000 < false = marker older than artifact? [INFO] jboss-as-dist-7.0.2.Final.zip already unpacked. [INFO] richfaces-distribution-4.2.1.Final.zip already unpacked. {code} As you can see: # When you have the dependency in your M2_REPO, you can work offline and maven-dependency-plugin behaves well # When you do not clean, you keep the previous install I admit I did not expected the plugin to behave so well! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11714 at 5/16/12 9:25 AM: ----------------------------------------------------------------- Lost of files to replace by get-mojo or unpack-mojo in their pom: Simple Maven dependencies: -./vpe/tests/org.jboss.tools.vpe.ui.bot.test/requirements.properties- DONE -./central/tests/org.jboss.tools.central.test.ui.bot/requirements.properties- DONE -./cdi/tests/org.jboss.tools.cdi.bot.test/requirements.properties- DONE -./cdi/tests/org.jboss.tools.cdi.seam3.bot.test/requirements.properties- DONE -./jsf/tests/org.jboss.tools.jsf.ui.bot.test/requirements.properties- DONE -./ws/tests/org.jboss.tools.ws.creation.core.test/requirements.properties- DONE -./ws/tests/org.jboss.tools.ws.ui.bot.test/requirements.properties- DONE Involve Seam (need more effort - filtering, install...): ./maven/tests/org.jboss.tools.maven.ui.bot.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.ui.test/requirements.properties ./examples/tests/org.jboss.tools.project.examples.test/requirements.properties Runtme not found as Maven artifact (need either Maven artifact, or is still stuck w/ Ant): ./smooks/tests/org.jboss.tools.smooks.ui.bot.test/requirements.properties ./runtime/tests/org.jboss.tools.runtime.test/requirements.properties (EAP) ./runtime-soa/tests/org.jboss.tools.runtime.soa.test/requirements.properties (EAP) ./as/tests/org.jboss.ide.eclipse.as.ui.test/requirements.properties (old AS) ./as/tests/org.jboss.ide.eclipse.as.test/requirements.properties (old AS) ./portlet/tests/org.jboss.tools.portlet.core.test/requirements.properties (jbossesb) ./portlet/tests/org.jboss.tools.portlet.ui.bot.test/requirements.properties (JBossPortletBridge) ./jbpm/tests/org.jboss.tools.jbpm.ui.bot.test/requirements.properties (old jbpm) ./esb/tests/org.jboss.tools.esb.ui.bot.test/requirements.properties ./esb/tests/org.jboss.tools.esb.project.core.test/requirements.properties was (Author: mickael_istria): Lost of files to replace by get-mojo or unpack-mojo in their pom: ./maven/tests/org.jboss.tools.maven.ui.bot.test/requirements.properties ./smooks/tests/org.jboss.tools.smooks.ui.bot.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam221GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam202SP1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam211GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seamfp.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.core.test/requirements.properties ./seam/tests/org.jboss.tools.seam201GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam230.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam220CR1.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam121EAP.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam212GA.ui.test/requirements.properties ./seam/tests/org.jboss.tools.seam203CR1.ui.test/requirements.properties ./runtime-soa/tests/org.jboss.tools.runtime.soa.test/requirements.properties ./vpe/tests/org.jboss.tools.vpe.ui.bot.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.ui.test/requirements.properties ./as/tests/org.jboss.ide.eclipse.as.test/requirements.properties ./runtime/tests/org.jboss.tools.runtime.test/requirements.properties ./examples/tests/org.jboss.tools.project.examples.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.ui.bot.test/requirements.properties ./portlet/tests/org.jboss.tools.portlet.core.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.bot.test/requirements.properties ./cdi/tests/org.jboss.tools.cdi.seam3.bot.test/requirements.properties ./jsf/tests/org.jboss.tools.jsf.ui.bot.test/requirements.properties -./central/tests/org.jboss.tools.central.test.ui.bot/requirements.properties- DONE ./jbpm/tests/org.jboss.tools.jbpm.ui.bot.test/requirements.properties -./ws/tests/org.jboss.tools.ws.creation.core.test/requirements.properties- DONE -./ws/tests/org.jboss.tools.ws.ui.bot.test/requirements.properties- DONE ./esb/tests/org.jboss.tools.esb.ui.bot.test/requirements.properties ./esb/tests/org.jboss.tools.esb.project.core.test/requirements.properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11714: --------------------------------------------- and swtbot is the least of my problems - the main concern is for the unit tests that require runtimes for their testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11714: ----------------------------------- Fix Version/s: 3.4.x (was: 3.3.0.CR1) Further efforts necessary to get other dependencies installed in a more independent and Maven-friendly way. Target to 3.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11714: ---------------------------------------- Looks like this move makes build users happy (got good feedback from ModeShape guys). The gain is really to be able to configure the runtime to use in the pom.xml, which is their singe entry point when they want to change their build. The current mechanism using Ant, Get and MD5 should/will be replaced by a maven-wget-plugin of ours. I couldn't find anything similar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11714 at 6/12/12 9:25 AM: ----------------------------------------------------------------- I found a project related to this use-case and succeeded to contribute to it. I updated a Mojo that we can use instead of our scripts. Will give a try soon. https://code.google.com/p/maven-download-plugin/ was (Author: mickael_istria): I found a project related to this use-case and succeeded to contribute to it. I updated a Mojo that we can use instead of our scripts. Will give a try soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11714 at 7/4/12 8:24 AM: ---------------------------------------------------------------- This job tests installation of latest JBT 3.3.0 and update trunk on Eclipse 3.7.2. http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.install-tests-... was (Author: mickael_istria): This job tests installation of latest JBT 3.3.0 and update trunk on Eclipse 3.7.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11714?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-11714. ------------------------------ Thanks for doing this. Great work! Closing JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira