On 2/26/06, Ersin Er <[EMAIL PROTECTED]> wrote:
Right. running mvn install first before runing mvn eclipse:eclipse makes our life much easier. It's because we're lazy enough to skip deploying artifacts after we bump up version numbers. Yes, it takes too long to deploy the whole artifacts for now, so the deployment isn't often executed by everyone. For the time being until this problem (deployment speed) is resolved by the Maven team, let's just run mvn install first.
The biggest problem is actually that the permission is not set properly when we deploy the artifacts. This is really annoying and should be fixed very very soon.
TrustinHi,
Have you tried a mvn install in trunks first ?
Right. running mvn install first before runing mvn eclipse:eclipse makes our life much easier. It's because we're lazy enough to skip deploying artifacts after we bump up version numbers. Yes, it takes too long to deploy the whole artifacts for now, so the deployment isn't often executed by everyone. For the time being until this problem (deployment speed) is resolved by the Maven team, let's just run mvn install first.
The biggest problem is actually that the permission is not set properly when we deploy the artifacts. This is really annoying and should be fixed very very soon.
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
