[
https://issues.jboss.org/browse/JBIDE-12756?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12756:
----------------------------------------
{quote}
But... a default profile that's supposed to always be on shouldn't be disabled
based on a property like -Dmaven.test.skip, should it?
{quote}
Actually, a default profile is activeByDefault. Whenever another non-activeByDefault
profile is enabled (via -P or via <activation> expression -property, os...-), the
activeByDefault profile gets disabled.
That's the same reason why the macosx profile (activated by os test) had to repeat
some properties from default.
{quote}
At least for now there's a workaround... use -DskipTests instead, or explicitly enable
-Pdefault.
{quote}
If you use -DskipTests, it will probably not set the skipPrivateTests property correctly.
I recommend using "-P default".
-Dmaven.skip.tests disables default profile when building locally
-----------------------------------------------------------------
Key: JBIDE-12756
URL:
https://issues.jboss.org/browse/JBIDE-12756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform, UpStream
Affects Versions: 4.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Mickael Istria
Riddle me this...
1. This works:
{code}
mvn clean install -DskipTests=true
[INFO] Scanning for projects...
[INFO] Computing target platform for MavenProject:
org.jboss.tools.common.plugins:org.jboss.tools.common.core:3.4.0-SNAPSHOT @
/home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/common/plugins/org.jboss.tools.common.core/pom.xml
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0...
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0...
{code}
2. And this works:
{code}
mvn clean install -Dmaven.test.skip -Pdefault
[INFO] Scanning for projects...
[INFO] Computing target platform for MavenProject:
org.jboss.tools.common.plugins:org.jboss.tools.common.core:3.4.0-SNAPSHOT @
/home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/common/plugins/org.jboss.tools.common.core/pom.xml
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0...
[INFO] Adding repository
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0...
{code}
3. But this does not:
{code}
mvn clean install -Dmaven.test.skip
[INFO] Scanning for projects...
[INFO] Computing target platform for MavenProject:
org.jboss.tools.common.plugins:org.jboss.tools.common.core:3.4.0-SNAPSHOT @
/home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/common/plugins/org.jboss.tools.common.core/pom.xml
[INFO] Resolving dependencies of MavenProject:
org.jboss.tools.common.plugins:org.jboss.tools.common.core:3.4.0-SNAPSHOT @
/home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/common/plugins/org.jboss.tools.common.core/pom.xml
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86,
org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.common.core 3.4.0.qualifier
[ERROR] Missing requirement: org.jboss.tools.common.core 3.4.0.qualifier requires
'bundle org.eclipse.core.runtime 3.7.0' but it could not be found
{code}
So... why does -Dmaven.test.skip cause the default profile in the parent pom, *default*,
to be disabled when you turn off the tests, but DOES keep it enabled w/ -DskipTests?
--
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