[ https://issues.jboss.org/browse/JBIDE-12834?page=com.atlassian.jira.plugi... ] Andrej Podhradsky edited comment on JBIDE-12834 at 10/12/12 4:36 AM: --------------------------------------------------------------------- added log file from command 'mvn clean verify -X' was (Author: apodhrad): log file from command 'mvn clean verify -X' -- 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-12834?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-12834: -------------------------------------- Priority: Major (was: Blocker) -- 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-12834?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12834: ---------------------------------------- In such case, try with "-U", it will force update and force Maven repo to check for availability of new artifacts it couldn't find earlier. -- 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-12834?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12834: ---------------------------------------- Looks like your Maven only looks at the JBoss releases repository. However, the target platform are published as snapshots. Please verify your Maven settings allow to pull snapshots too: https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#Maven_set... -- 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-12834?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-12834: ------------------------------------------- I have already set the file you mentioned. -- 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-12834?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-12834: ------------------------------------------- Oh... now I see what's the problem... I named the file setting.xml instead of settings.xml :( Thank you Mickael! Now it is working. -- 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-12834?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12834: --------------------------------------- Nick added the jboss snapshots nexus repo to parent pom and so now the builds should work again even if you don't add this repo in your settings.xml. -- 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-12834?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12834: --------------------------------------- Yes, it is now working. But I have one more comment. I wrongly assumed that the unified.target profile is really on by default. So I didn't specify it. But that doesn't work. Now I saw the pom for myself and saw there is just "<activeByDefault>true</activeByDefault>" which of course doesn't work if you have another profile active. So something like this works: -P unified.target,jbosstools-staging-aggregate I guess I cannot avoid using jbosstools-staging-aggregate or jbosstools-nightly-staging-composite. Speaking of which, what is the difference between those two? I know they point to one site of all features and a site that contains all the components' sites respectively. But they should be equal content-wise, right? So it doesn't really matter which one we use. Please correct me if I'm wrong. Anyway, I can confirm that our builds pass again as long as you specify either unified.target or maximum. -- 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-12834?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12834: ---------------------------------------- [~mmalina] All you need to know should be documented here https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#Building_... Composite and aggregate are exactly equals. Contents of aggregate is a subset of content of composite. Aggregate is categorized. But in general, you can use one or the other, your build will behave the same way. -- 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-12834?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12834: ---------------------------------- Fix Version/s: 4.0.0.Beta1 -- 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