[
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
Get basic "mvn clean install" to work with everything
developers want
---------------------------------------------------------------------
Key: JBIDE-11404
URL:
https://issues.jboss.org/browse/JBIDE-11404
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.Beta3
We should set up the default profiles so that developers can use simply "mvn clean
install" to build their project.
That will require to see what they usually want to build, and to change default profiles
to match 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