[ https://issues.jboss.org/browse/JBIDE-12292?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-12292: -------------------------------- Description: Our maven features should now depend on m2e-wtp @ eclipse. However, there's no stable build available from Eclipse yet. We should use the development update site to point to the latest m2e-wtp 0.16.0 build : http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... [~mickael_istria] suggests to add that repo in the pom.xml's repositories was: Our maven features should now depend on m2e-wtp @ eclipse. However, there's no stable build available from Eclipse yet. We should use the development update site to point to latest m2e-wtp 0.16.0 builds : http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... [~mickael_istria] suggests to add a that repo in the pom.xml's repositories -- 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-12292?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-12292 at 7/6/12 6:44 AM: ---------------------------------------------------------------- Nick, we need your opinion on this <repository> approach. The idea is to temporarily put the m2e-wtp snapshot repo into maven pom.xml, so they can perform development build using it; and when m2e-wtp gets released, we remove this repository and put the stable version of m2e-wtp in the target-platform. !http://icons.iconarchive.com/icons/pixelmixer/basic/16/plus-icon.png! It's transparent and easy for developers !http://icons.iconarchive.com/icons/pixelmixer/basic/16/plus-icon.png! It's no effort in target-platform !http://cdn1.iconfinder.com/data/icons/diagona/icon/16/104.png! Dependency not visible in target platform !http://cdn1.iconfinder.com/data/icons/diagona/icon/16/104.png! We must remember about changing TP when m2e-wtp has a stable version was (Author: mickael_istria): Nick, we need your opinion on this <repository> approach. The idea is to temporarily put the m2e-wtp snapshot repo into maven pom.xml, so they can perform development build using it; and when m2e-wtp gets released, we remove this repository and put the stable version of m2e-wtp in the target-platform. + It's transparent and easy for developers + It's no effort in target-platform - Dependency not visible in target platform - We must remember about changing TP when m2e-wtp has a stable version -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12292: ------------------------------------ Why would this dep be treated any differently than any other? Why not have: a) a timestamped mirror here: http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/ (timestamp folder) b) link to it from the composite requirements mirror: http://download.jboss.org/jbosstools/updates/juno/SR0/ (composite*.xml) c) filter the specific version into the TPs: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ (*.target* files) -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12292: ------------------------------------ Proposed solution - treat m2e-wtp like another JBT component: a) add m2e-wtp nightly build URL [0] to http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... so JBT aggregate site can find it like other components / upstream b) add m2e-wtp nightly build URL [0] to associate.properties [1] so it can me automatically found when installing from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ c) add m2e-wtp nightly build URL [0] as new repository to JBDS product pom [2] d) add m2e-wtp nightly build URL [0] to composite staging site for JBDS 6.0 [3] [0] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... I presume? [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso... (and other aggregates like coretests, soa, etc.) [2] https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml [3] https://devstudio.jboss.com/updates/6.0/staging/ (forthcoming, does not exist yet) -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12292: ------------------------------- Summary: Use m2e-wtp dev builds in composite sits and aggregate builds (rather than in Juno target platform) (was: Use m2e-wtp dev builds in our own Juno target platform) -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12292 at 7/6/12 10:55 AM: ------------------------------------------------------------- Proposed solution - treat m2e-wtp like another JBT component: a) add m2e-wtp nightly build URL [0] to http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... so JBT aggregate site can find it like other components / upstream b) add m2e-wtp nightly build URL [0] to associate.properties [1] so it can me automatically found when installing from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ c) add m2e-wtp nightly build URL [0] as new repository to JBDS product pom [2] d) add m2e-wtp nightly build URL [0] to composite staging site for JBDS 6.0 [3] [0] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... I presume? [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso... (and other aggregates like coretests, soa, etc.) [2] https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml [3] https://devstudio.jboss.com/updates/6.0/staging/ (forthcoming, does not exist yet) We should also unlink m2e-apt site from parent pom and other places and use this similar approach instead (JBIDE-12294). was (Author: nickboldt): Proposed solution - treat m2e-wtp like another JBT component: a) add m2e-wtp nightly build URL [0] to http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... so JBT aggregate site can find it like other components / upstream b) add m2e-wtp nightly build URL [0] to associate.properties [1] so it can me automatically found when installing from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ c) add m2e-wtp nightly build URL [0] as new repository to JBDS product pom [2] d) add m2e-wtp nightly build URL [0] to composite staging site for JBDS 6.0 [3] [0] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... I presume? [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso... (and other aggregates like coretests, soa, etc.) [2] https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml [3] https://devstudio.jboss.com/updates/6.0/staging/ (forthcoming, does not exist yet) We should also unlink m2e-apt site from parent pom and other places and use this similar approach instead (JBIDE-11700). -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12292: ------------------------------- Description: Our maven features should now depend on m2e-wtp @ eclipse. However, there's no stable build available from Eclipse yet. We should use the development update site to point to the latest m2e-wtp 0.16.0 build : http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... [~mickael_istria] suggests to add that repo in the pom.xml's repositories was: Our maven features should now depend on m2e-wtp @ eclipse. However, there's no stable build available from Eclipse yet. We should use the development update site to point to the latest m2e-wtp 0.16.0 build : http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... [~mickael_istria] suggests to add that repo in the pom.xml's repositories -- 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-12292?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12292: ---------------------------------------- Nick, I see target-platforms use static versions for dependencies, including m2e-wtp. If we use the procedure you describe, then we'll also need to modify version for m2e-wtp in target-platforms every time a new build and new qualifier is produced for m2e-wtp. Am I right? Shouldn't we in such case put 0.0.0 as version for m2e-wtp in target-platforms? -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-12292. -------------------------------- Resolution: Done http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... is now part of http://download.jboss.org/jbosstools/updates/juno/SR0/, and as such can be used to resolve the latest when building TP, using TP, or installing. -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-12292: ---------------------------------- Assignee: Fred Bricon (was: Nick Boldt) Builds are blue, please test and verify that building, installation, and running m2e-wtp 0.16 works as you expect, then close this when satisfied. Merci d'avance. -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12292: ------------------------------------ Yes, the reason multiple.target is called "multiple" is that when first launched it contained multiple URLs. But that doesn't solve the need to have a non-versioned reference to wtp-m2e in order for the target file to pull in the latest version available. Or have you found a workaround for including xulrunner and m2e-wtp in the TP? -- 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-12292?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-12292. ------------------------------ Done. See also JBIDE-12294, JBIDE-12516, JBIDE-12517 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira