machine and in other place (without proxy) I could build
sucessfully Cocoon!!!
Thank you for all to all!
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19367471.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
Hi Yosauron,
finally, in other machine and in other place (without proxy) I could build
sucessfully Cocoon!!!
Glad to hear you now have a way to build it. Proxies can be very useful
for lots of reasons... but they can also be infuriating too!
Actually, I did pick up on this list that
machine whith non-proxied internet
connection... I'll tell you the result!! :).
PS: I hope my health returns whith that :-P.
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19305017.html
Sent from the Cocoon - Users mailing list archive
: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19284820.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
2.0.9
svn 1.4.6
I can't determine which is my problem... I've tried all the solutions of
this thread and the tests errors are still there :'(. I'm crazy...
Thank you for all
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19285413.html
Sent from
yosauron wrote:
I can't determine which is my problem... I've tried all the solutions of
this thread and the tests errors are still there :'(. I'm crazy..
Sorry I can't think of anything else... except maybe try the machine
from another (non-proxied) internet connection if you have access to
CEST 2008
[INFO] Final Memory: 99M/178M
[INFO]
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19265410.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
Hi Yosauron,
I've updated to rev. 690861 and I've still gotten the same tests errors.
Could anyone help me?
Which revision do i have to download to compile cocoon successfully?
I can confirm that on my windows XP system I updated my copy of the
Cocoontrunk to revision 691183 (the latest
in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19268977.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
I'm behind a proxy, could be this the source of the problem
Is this new info that you omitted to tell us?!!! ;-)
I'm not a subversion expert and I'm not personally behind a proxy here
but I did notice that you have to make some adjustments if you are
behind a proxy. See here [1] for more
Hi!
David Legg schrieb:
I'm behind a proxy, could be this the source of the problem
Is this new info that you omitted to tell us?!!! ;-)
I'm not a subversion expert and I'm not personally behind a proxy here
but I did notice that you have to make some adjustments if you are
behind a
Hi Martin,
I think that the subversion checkout works well, but maven is the problem.
I think your right. Tak, probably avoided problems with svn because he
was using https protocol which might have been allowed by the proxy.
Maybe you should try the following:
Correctly configure maven
Could we have tags in subvision? The company I work for still use CVS as
version control. We put tags in CVS during development. Cocoon is a big
project. Not all people need all features. For the newbies, we can always
go back to the old tag that we know, and use that version. Could that be
Tak,
Cocoon is a big project. Not all people need all features. For the
newbies, we can always go back to the old tag that we know, and
use that version. Could that be a solution?
That's not the issue. One of the reasons for making Cocoon 2.2 the way
it is is to allow people to only add
Yosauron,
I can confirm that on my windows XP system I updated my copy of the
Cocoontrunk to revision 691183 (the latest version) and then ran:
mvn install -P allblocks
23 minutes and 21 seconds later it had built everything with no failures.
I've followed these step:
% rm -R
I've tried to compile without using tests. I've used this sentence:
%./build.sh -Dmave.test.skip=true install
And I got a Failed to resolve artifact
(org.apache.cocoon:cocoon-core:test-jar:tests:2.2.1-SNAPSHOT).
How do I build cocoon correctly? :confused:
Thanks a lot.
[INFO] Scanning for
minutes 30 seconds
[INFO] Finished at: Fri Aug 08 12:11:06 CEST 2008
[INFO] Final Memory: 98M/175M
[INFO]
---
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p19257682.html
yosauron schrieb:
I've tried to compile without using tests. I've used this sentence:
%./build.sh -Dmave.test.skip=true install
There's a typo in your command:
It should be:
mvn -Dmaven.test.skip=true install
See
minutes 30 seconds
[INFO] Finished at: Fri Aug 08 12:11:06 CEST 2008
[INFO] Final Memory: 98M/175M
[INFO]
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p18887735.html
Sent from
me what are i doing wrong?
Thanks a lot!
I'm desperate!!
--
View this message in context:
http://www.nabble.com/C22---Maven-artifact-missing-tp17780552p18868468.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
yosauron pisze:
I have tried to build C2.2 several times but the process always fails me.
If you have done it within last two days the reason might be that we were releasing some stuff and
in some intermediate states the build can be broken.
I follow this steps (under Ubuntu 8.04, java 1.6
: Re: C22 - Maven artifact missing
yosauron pisze:
I have tried to build C2.2 several times but the process always fails me.
If you have done it within last two days the reason might be that we were
releasing some stuff and
in some intermediate states the build can be broken.
I follow
://www.nabble.com/C22---Maven-artifact-missing-tp17780552p18873697.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Grzegorz Kossakowski wrote:
yosauron pisze:
I have tried to build C2.2 several times but the process always fails me.
If you have done it within last two days the reason might be that we
were releasing some stuff and in some intermediate states the build can
be broken.
I follow this
-Oorspronkelijk bericht-
Van: Reinhard Pötz [mailto:[EMAIL PROTECTED]
Verzonden: do 7-8-2008 21:56
Aan: users@cocoon.apache.org
Onderwerp: Re: C22 - Maven artifact missing
I've just fixed the build, which was indeed broken because of my recent
release activities. Could you please
I Just tried building Cocoon from svn by following these instructions
[1] and got the build error listed below.
I've tried deleting my local repository and tried building all the
blocks with:
mvn install -Dmaven.test.skip=true -P allblocks
All with the same result. Should I just try again
David Legg pisze:
I Just tried building Cocoon from svn by following these instructions
[1] and got the build error listed below.
I've tried deleting my local repository and tried building all the
blocks with:
mvn install -Dmaven.test.skip=true -P allblocks
Skipping test phase is not a
Grzegorz Kossakowski wrote:
David, you are the second person reporting this issue, the first one
was Alexander[1] so there must be an issue with Cocoon dependencies here.
I noticed that thread already thanks, but as it didn't conclude I
wondered if it had been resolved.
Since I'm now sure
Grzegorz Kossakowski wrote:
Skipping test phase is not a good idea anymore and docs need an update
(I've done it already). Anyway, this flag shouldn't make the build fail.
Would you believe it! I tried it without the -Dmaven.test.skip=true
flag and it passed all the tests and completed the
David Legg pisze:
Grzegorz Kossakowski wrote:
Skipping test phase is not a good idea anymore and docs need an update
(I've done it already). Anyway, this flag shouldn't make the build fail.
Would you believe it! I tried it without the -Dmaven.test.skip=true
flag and it passed all the tests
Grzegorz Kossakowski wrote:
I don't have an idea why it behaves differently. Maybe it's another
bug in Maven that we have found here?
I think it's a conspiracy to always make us run regression tests ;-)
Thanks for updating the web site.
David.
31 matches
Mail list logo
