[
https://issues.jboss.org/browse/JBIDE-11524?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11524:
---------------------------------------------
note, I agree I don't think we should change these things blindly without actually
considering what options it actually make sense to expose - right now I feel there are too
many options or wrong options.
What I would expect is that each branch (trunk, stable, 3.3.x, 3.4.x etc going forward)
has the same commands to use.
i.e.
Default for dev should just be:
mvn clean install
Doing a release build:
mvn clean install -Prelease
Doing a build with some different sites:
add -Pnightly or -Psnapshot for adding the latest built repo to the list of repos.
The content of nightly/snapshot is then committed proper versioned parent pom's in the
branches/trunk.
Rename jobs, sites, profiles, variables... to clearer names (remove
reference to nightly)
-----------------------------------------------------------------------------------------
Key: JBIDE-11524
URL:
https://issues.jboss.org/browse/JBIDE-11524
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Minor
nightly is a very confusing name, that does not reflect at all what really happens.
We should prefer using "staging" in variable, profiles, jobs, url... to make it
clearer
For instance,
* jbosstools-nightly-staging-composite -> jbosstools-staging-composite
* jboostools-nightly -> jbosstools-staging-aggregate
--
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