[ https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11404 at 3/26/12 10:59 AM: -------------------------------------------------------------- We have several use cases: {code} a) dev wants to build some downstream component w/o building upstream i) resolve against latest milestone site ii) resolve against latest nightly site iii) resolve against latest staging site b) dev wants to build some downstream component including building upstream i) resolve against latest milestone site ii) resolve against latest nightly site iii) resolve against latest staging site c) dev wants to build entire stack In addition, we need to support these use cases, for people in North America (1 or 2) and in Europe (2): 1) resolve against remote target platform (assuming good internet connection to download.jboss.org or www.qa.jboss.com) 2) resolve against local target platform (having previously bootstrapped) {code} So, which of those 14 permutations is "their usual needs" ? Should we conduct a poll? was (Author: nickboldt): We have several use cases: {code} a) dev wants to build some downstream component w/o building upstream i) resolve against latest milestone site ii) resolve against latest nightly site iii) resolve against latest staging site b) dev wants to build some downstream component including building upstream i) resolve against latest milestone site ii) resolve against latest nightly site iii) resolve against latest staging site c) dev wants to build entire stack In addition, we need to support these use cases, for people in North America (1 or 2) and in Europe (2): 1) resolve against remote target platform (assuming good internet connection to download.jboss.org or www.qa.jboss.com) 2) resolve against local target platform (having previously bootstrapped) {code} So, which of those 14 permutations is "their usual needs" ? -- 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-11404?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11404 at 4/4/12 10:29 AM: ------------------------------------------------------------- Ah, but what if you want to build resolving against deps AND build you upstream components too, like if you're working on Archives/JMX/AS at the same time, or you're committing changes to common + vpe/jsf/jst? Just because you use one use case doesn't mean you're the majority. And BTW, you should NOT be building against the composite mirrors (jboss-requirements-composite-mirror,jboss-requirements-composite-extras-mirror). You SHOULD be building against the target platform or target platform site. Using the composite mirrors may result in builds breaking when run against the TP due to missing IUs on the TP. Better to expose that problem and fix the TP than to get into a situation where your local build works but Jenkins fails. Suggest better defaults would be: {code:label= - for JBT Core components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,local.site {code} {code:label= - or, for JBT SOA Tooling Components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site {code} {code:label= - or if you're like Doug, and prefer the nightly aggregate to the composite as it changes less often -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site -Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ {code} See also: http://www.businessballs.com/treeswing.htm was (Author: nickboldt): Ah, but what if you want to build resolving against deps AND build you upstream components too, like if you're working on Archives/JMX/AS at the same time, or you're committing changes to common + vpe/jsf/jst? Just because you use one use case doesn't mean you're the majority. And BTW, you should NOT be building against the composite mirrors (jboss-requirements-composite-mirror,jboss-requirements-composite-extras-mirror). You SHOULD be building against the target platform or target platform site. Using the composite mirrors may result in builds breaking when run against the TP due to missing IUs on the TP. Better to expose that problem and fix the TP than to get into a situation where your local build works but Jenkins fails. Suggest better defaults would be: {code} - for JBT Core components - mvn install -fae -e -P jbosstools-nightly-staging-composite,local.site - or, for JBT SOA Tooling Components - mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site - or if you're like Doug, and prefer the nightly aggregate to the composite as it changes less often - mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site -Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ See also: http://www.businessballs.com/treeswing.htm -- 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-11404?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11404 at 4/4/12 10:30 AM: ------------------------------------------------------------- Ah, but what if you want to build resolving against deps AND build you upstream components too, like if you're working on Archives/JMX/AS at the same time, or you're committing changes to common + vpe/jsf/jst? Just because you use one use case doesn't mean you're the majority. And BTW, you should NOT be building against the composite mirrors (jboss-requirements-composite-mirror,jboss-requirements-composite-extras-mirror). You SHOULD be building against the target platform or target platform site. Using the composite mirrors may result in builds breaking when run against the TP due to missing IUs on the TP. Better to expose that problem and fix the TP than to get into a situation where your local build works but Jenkins fails. Suggest better defaults would be: {code:title= - for JBT Core components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,local.site {code} {code:title= - or, for JBT SOA Tooling Components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site {code} {code:title= - or if you're like Doug, and prefer the nightly aggregate to the composite as it changes less often -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site -Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ {code} See also: http://www.businessballs.com/treeswing.htm was (Author: nickboldt): Ah, but what if you want to build resolving against deps AND build you upstream components too, like if you're working on Archives/JMX/AS at the same time, or you're committing changes to common + vpe/jsf/jst? Just because you use one use case doesn't mean you're the majority. And BTW, you should NOT be building against the composite mirrors (jboss-requirements-composite-mirror,jboss-requirements-composite-extras-mirror). You SHOULD be building against the target platform or target platform site. Using the composite mirrors may result in builds breaking when run against the TP due to missing IUs on the TP. Better to expose that problem and fix the TP than to get into a situation where your local build works but Jenkins fails. Suggest better defaults would be: {code:label= - for JBT Core components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,local.site {code} {code:label= - or, for JBT SOA Tooling Components -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site {code} {code:label= - or if you're like Doug, and prefer the nightly aggregate to the composite as it changes less often -} mvn install -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site -Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ {code} See also: http://www.businessballs.com/treeswing.htm -- 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-11404?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11404: ---------------------------------------- I am not trying to convince what I use is the best for the majority, I am trying to gather the majority's use case to adapt to them; and feedback about them. true. I remove it from my favourite command line. Also I don't use a local.site (I don't like "local" things in Maven, it reduce portability). So I will more likely use unified.target. So the command line I use for my use case is now {code} mvn install -U -fae -e -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,unified.target {code} My question is now, if requirements site should not be used, why are they available in parent pom? -- 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-11404?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11404: ------------------------------------ Lucia: which site? Whether you mean the staging composite or the nightly aggregate, dependencies vanish when they're being replaced by new ones (during the publish phase of a build). We've put stuff in place to mitigate the effect, but if you're lucky enough to ping the site right before a refresh, you will prolly need to restart your build a few mins later. Related: https://twitter.com/#!/nickboldt/status/187266407392747521 -- 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-11404?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11404: ------------------------------------- Having to think hard on this, I would suggest that typically I want to build just my component and have the upstream resolve or skip using latest from a repo. There are times when I would also like to build my deps if I am working on as/jmx/openshift/blahblah, but this is not the usual situation. The usual situation for me is pretty limited to one component at a time. I think the coolest thing ever would be if it could svn diff my upstream components to know whether they have changes and need to be rebuilt or not, but I don't expect you guys to be able to do that. Just saying, it'd be pretty damn cool. Maybe we could have a wrapper shell script that does that for us, and then calls the tycho build with all the proper args, using upstream / repo / local site if there's no change, and rebuilding the plugin if there is a need for it. THAT'd be pretty damn cool. -- 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-11404?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11404: ------------------------------------ @Lucia: Staging site is a composite of all the component sites, and therefore is repopulated every time a component successfully builds + publishes. Note that it has "composite" in the URL and is assembled via this XML file: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... Nightly site is an aggregate, which is built by taking a snapshot of the contents of the above composite and copying that content to another location. Thus where the composite site changes every time a component respins, the aggregate only changes when all the components have stopped changing long enough for the aggregate to be able to run. "Nightly" is a misnomer; this job can run every few hours, or be stuck waiting to run for days. Think of it more like a "weekly snapshot". So, if you're interested in picking up changes that were built in the last few hours, you would pull upstream binary bits from the composite site(s). If on the other hand you're good using last week's more stable bits, you'd pull from the nightly site: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -- 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-11404?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-11404: ----------------------------------------- @Nick Thanks for the explanation. -- 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-11404?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11404: ---------------------------------------- Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta3) not blocking B3 -- 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-11404?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-11404: -------------------------------------- Assignee: Nick Boldt (was: Mickael Istria) I'm thinking about: * renaming "default" profile to to "target-platform-site" * removing activeByDefault from ex-"default", new "target-platform-site" * setting activeByDefault to unified.target WDYT? -- 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-11404?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11404: ------------------------------------ Does running a build w/ the unified.target profile work the same as running a build pointing at the update site referenced by the unified.target file? That is, will devs get the same performance if by default they resolve against a .target instead of an http://path/to/target-platform/latest/ site? -- 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

[ https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11404 at 10/3/12 5:15 PM: ------------------------------------------------------------- [~mickael_istria]: Does running a build w/ the unified.target profile work the same as running a build pointing at the update site referenced by the unified.target file? That is, will devs get the same performance if by default they resolve against a .target instead of an http://path/to/target-platform/latest/ site? was (Author: nickboldt): Does running a build w/ the unified.target profile work the same as running a build pointing at the update site referenced by the unified.target file? That is, will devs get the same performance if by default they resolve against a .target instead of an http://path/to/target-platform/latest/ site? -- 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

[ https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11404 at 10/3/12 5:17 PM: ------------------------------------------------------------- [~mickael_istria]: Does running a build w/ the unified.target profile work the same as running a build pointing at the update site referenced by the unified.target file? That is, will devs get the same performance if by default they resolve against a .target instead of an http://path/to/target-platform/latest/ site? I know that some devs build like this: mvn install -Djbosstools-target-site=file:///path/to/local/repo Would that still work if we moved to default operation being from target file instead of target site? was (Author: nickboldt): [~mickael_istria]: Does running a build w/ the unified.target profile work the same as running a build pointing at the update site referenced by the unified.target file? That is, will devs get the same performance if by default they resolve against a .target instead of an http://path/to/target-platform/latest/ site? -- 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

[ https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11404: ---------------------------------------- Do we agree to set activeByDefault on unified.target and jbosstools-staging-aggregate activeByDefault, and remove the "default" profile? -- 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

[ https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-11404. ------------------------------------ Resolution: Done New default profiles are unified.target + jbosstools-staging-aggregate. direct "mvn verify" should work in most cases. In tricky cases, one case still use other profiles. -- 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