[
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.
Could not resolve target platform
---------------------------------
Key: JBIDE-12834
URL:
https://issues.jboss.org/browse/JBIDE-12834
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 4.0.0.Beta1
Reporter: Andrej Podhradsky
Assignee: Mickael Istria
Attachments: debug.log, setting.xml
After running
$ cd jbosstools/tests
$ mvn clean verify
I get the following error
java.lang.RuntimeException: Could not resolve target platform specification artifact
org.jboss.tools.target-platforms.jbosstools-JunoSR0c:unified:target:unified:4.0.0.Beta1-SNAPSHOT
-> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
--
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