[
https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11404:
------------------------------------
If upstream has changed and you're building against that upstream (either composite
nightly staging or aggregate nightly) then you'll immediately see the upstream binary
dep changes.
The only place where this script would be useful is if SVN for upstream *has changed* but
the related builds have *not yet spun* (due to blocked slaves or further-upstream jobs
spinning).
If you use git-svn you can type `git log` to see which components have changed since the
last time you checked, and can then run an "as-bootstrap" build instead of just
the usual component build:
{code}
cd ~/trunk/build; mvn clean install -Pas-bootstrap # builds as, archives, jmx, tests,
common, usage
vs.
cd ~/trunk/as; mvn clean install # builds just as
{code}
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