[ https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13014: ------------------------------------ From: https://github.com/mickaelistria/jbosstools-build/commit/2c0c793336752336... {quote} Currently, a job like the JBT SOA aggregate uses these profiles: -P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite So with this change we'll have to redo all the jobs to set -DjbossToolsDepsProfile=jbosstools-staging-aggregate -DthirdPartyDepsProfile=jenkins.target.maximum (for aggregate builds) or -DjbossToolsDepsProfile=jbosstools-nightly-staging-composite -DthirdPartyDepsProfile=jenkins.target (component builds), but no longer have the ability to fall back to an alternate URL should the local NFS mount fails. Not sure I'm 100% happy with this implementation. Do we only ever want just ONE upstream site w/ JBT bits and ONE upstream site w/ 3rd party bits (TP) ? {quote} -- 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-13014?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13014 at 11/8/12 1:39 PM: ------------------------------------------------------------- From: https://github.com/mickaelistria/jbosstools-build/commit/2c0c793336752336... {quote} Currently, a job like the JBT SOA aggregate uses these profiles: {code} -P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite {code} So with this change we'll have to redo all the jobs to set {code} -P hudson -DjbossToolsDepsProfile=jbosstools-staging-aggregate -DthirdPartyDepsProfile=jenkins.target.maximum (for aggregate builds){code} or{code} -P hudson -DjbossToolsDepsProfile=jbosstools-nightly-staging-composite -DthirdPartyDepsProfile=jenkins.target (component builds),{code} but no longer have the ability to fall back to an alternate URL should the local NFS mount fails. Not sure I'm 100% happy with this implementation. Do we only ever want just ONE upstream site w/ JBT bits and ONE upstream site w/ 3rd party bits (TP) ? {quote} was (Author: nickboldt): From: https://github.com/mickaelistria/jbosstools-build/commit/2c0c793336752336... {quote} Currently, a job like the JBT SOA aggregate uses these profiles: {code} -P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite {code} So with this change we'll have to redo all the jobs to set {code} -DjbossToolsDepsProfile=jbosstools-staging-aggregate -DthirdPartyDepsProfile=jenkins.target.maximum (for aggregate builds){code} or{code} -DjbossToolsDepsProfile=jbosstools-nightly-staging-composite -DthirdPartyDepsProfile=jenkins.target (component builds),{code} but no longer have the ability to fall back to an alternate URL should the local NFS mount fails. Not sure I'm 100% happy with this implementation. Do we only ever want just ONE upstream site w/ JBT bits and ONE upstream site w/ 3rd party bits (TP) ? {quote} -- 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-13014?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13014: --------------------------------------------- guys - why do you keep opening new issues about this when we have this issue: https://issues.jboss.org/browse/jbide-12836 ? please take a look at that issue which fixes this issue and more. -- 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-13014?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13014: ---------------------------------------- We can enable the local.site and local.composite profiles. Also, note that using several providers for TP or jbosstools deps does not mean we have a fall-back, it means that we don't know exactly which one is used. Alternate URL are to be controlled by Maven mirrors. I think that's what we want, and what we use. -- 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-13014?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13014: ---------------------------------------- {quote} Bear in mind too that the simple syntax used by local users to quickly build against the latest max TP: mvn clean install -Pmaximum becomes mvn clean install -DthirdPartyDepsProfile=maximum -DjbossToolsDepsProfile=jbosstools-staging-aggregate {quote} jbosstools-staging-aggregate is the default value for jbossToolsDepsProfile, so it becomes mvn clean install -DthirdPartyDepsProfile=maximum It's a few characters more, but it's way more explicit and help end-users to understand that they are choosing a profile, which is not clear with current approach where people don't understand how profile can be mixed. -- 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-13014?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13014: ---------------------------------------- After a quick call, Max suggestion looks ok to me. I'm working on some improvements to its branch, as described in http://ether-man.rhcloud.com/p/parentnext We'll hopefully come with all the flexibility we want, without changing how end-users have to use flags, and with dozens of line saved in the pom.xml. The general idea is to replace plugin configuration in profile by simple properties settings, and use these properties later. The default value of these properties constitutes the "default". Profiles only override the default. -- 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