[
https://issues.jboss.org/browse/JBIDE-11404?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11404:
----------------------------------------
Just because you use one use case doesn't mean you're the
majority.
I am not trying to convince what I use is the best for the majority, I am trying to gather
the majority's use case to adapt to them; and feedback about them.
And BTW, you should NOT be building against the composite mirrors
true. I remove it from my favourite command line. Also I don't use a local.site (I
don't like "local" things in Maven, it reduce portability). So I will more
likely use unified.target.
So the command line I use for my use case is now
{code}
mvn install -U -fae -e -P
jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,unified.target
{code}
My question is now, if requirements site should not be used, why are they available in
parent pom?
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