You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jean-Christophe Kermagoret <jc...@openbluelab.org> on 2007/01/19 06:51:38 UTC
org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
I have the following error with a fresh updated code from cocoon svn
repository :
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.cocoon:cocoon-maven-reports:jar:1.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.cocoon
-DartifactId=cocoon-maven-reports \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.cocoon:cocoon-webapp:war:2.2.0-M2-SNAPSHOT
2) org.apache.cocoon:cocoon-maven-reports:jar:1.0
----------
How to deal with this ?
Cheers,
--
Jean-Christophe
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Giacomo Pati <gi...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 26 Jan 2007, Niclas Hedhman wrote:
> Date: Fri, 26 Jan 2007 14:27:15 +0800
> From: Niclas Hedhman <ni...@hedhman.org>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
>
> On Friday 26 January 2007 00:26, Vadim Gritsenko wrote:
>
>>>> http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
>
>> My guess: he does not like Sun's whitespace policies :-P
>
>
> Code convention written by vi and emacs nerds of the 80s, with 80x24 character
> VT100 terminals, really sux... Saving screen real-estate is not a concern
Exaclty!
> anymore. Readability is.
And that's why I loved the Avalon Coding Conventions. It's much more
readable IMHO than Sun's.
> But change in this field is like mass conversion of religious devotees... ;o)
:-)
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.1 (GNU/Linux)
iD8DBQFFugZbLNdJvZjjVZARAlSDAJ9kMBn95gSr4y0kvWE68JAj8CgdOwCg7LDK
22yNBtrKyxri3010+umZUSk=
=R7W6
-----END PGP SIGNATURE-----
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Friday 26 January 2007 00:26, Vadim Gritsenko wrote:
> >> http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
> My guess: he does not like Sun's whitespace policies :-P
Code convention written by vi and emacs nerds of the 80s, with 80x24 character
VT100 terminals, really sux... Saving screen real-estate is not a concern
anymore. Readability is.
But change in this field is like mass conversion of religious devotees... ;o)
Cheers
Niclas
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Carsten Ziegeler <cz...@apache.org>.
Vadim Gritsenko wrote:
> Reinhard Poetz wrote:
>> Vadim Gritsenko wrote:
>>> Reinhard Poetz wrote:
>>>> If not, we should vote on the rules. It will be a lot of fun to read
>>>> dozens of mails about coding conventions ;-)
>>> Yet again? Give it a rest, follow the book [1].
>> aren't you missing it? We haven't had a coding conventions discussion
>> for months (or even years)! :-p
>
> :)
>
>>> http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
>> Carsten, in a previous mail you said that you used a stripped down
>> version of rules. But of what rules, the Sun rules that Vadim refers to?
>> I assume you did this because the Sun rules caused too many errors and
>> warnings and made the report unreadable, didn't it?
>
> My guess: he does not like Sun's whitespace policies :-P
>
:) I hate whitespaces, all this formatting is imho superfluous. Why not
write the whole code into one single line and forget about the
discussions of using tabs or spaces? :)
Seriously, I *wanted* to use a stripped down version, but had not the
time to strip the current configuration. The current configuration is
based on the Sun conventions with a few modifications.
Carsten
--
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Reinhard Poetz wrote:
> Vadim Gritsenko wrote:
>> Reinhard Poetz wrote:
>>> If not, we should vote on the rules. It will be a lot of fun to read
>>> dozens of mails about coding conventions ;-)
>>
>> Yet again? Give it a rest, follow the book [1].
>
> aren't you missing it? We haven't had a coding conventions discussion
> for months (or even years)! :-p
:)
>> http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
>
> Carsten, in a previous mail you said that you used a stripped down
> version of rules. But of what rules, the Sun rules that Vadim refers to?
> I assume you did this because the Sun rules caused too many errors and
> warnings and made the report unreadable, didn't it?
My guess: he does not like Sun's whitespace policies :-P
Vadim
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Reinhard Poetz <re...@apache.org>.
Vadim Gritsenko wrote:
> Reinhard Poetz wrote:
>> If not, we should vote on the rules. It will be a lot of fun to read
>> dozens of mails about coding conventions ;-)
>
> Yet again? Give it a rest, follow the book [1].
aren't you missing it? We haven't had a coding conventions discussion for months
(or even years)! :-p
> Vadim
>
> http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
Carsten, in a previous mail you said that you used a stripped down version of
rules. But of what rules, the Sun rules that Vadim refers to? I assume you did
this because the Sun rules caused too many errors and warnings and made the
report unreadable, didn't it?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Reinhard Poetz wrote:
> If not, we should vote on the rules. It will be a lot of fun to read
> dozens of mails about coding conventions ;-)
Yet again? Give it a rest, follow the book [1].
Vadim
http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Carsten Ziegeler <cz...@apache.org>.
Reinhard Poetz wrote:
> I commented the extension for now as Maven doesn't use the artifact created by
> the build but already needs it in a repository. We can only solve this problem
> by releasing the extension (AFAIU).
>
> Carsten, have we ever agreed formally on the checkstyle rules, which are the
> content of the extension? If yes, could you release the cocoon-maven-reports
> module together with the Spring configurator?
>
> If not, we should vote on the rules. It will be a lot of fun to read dozens of
> mails about coding conventions ;-)
>
Oh no, please not! We have not agreed on all checkstyle rules contained
in the current configuration. My idea is to add the basic rules, like
checking the correct header and some more and remove all other ones.
I followed the Maven documentation to add checkstyle checking for multi
projects, but it seems that following these rules creates to many
problems. Sigh. So let's leave this commented out for now :(
Carsten
--
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Reinhard Poetz <re...@apache.org>.
Jean-Christophe Kermagoret wrote:
> I have the following error with a fresh updated code from cocoon svn
> repository :
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.cocoon:cocoon-maven-reports:jar:1.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.cocoon
> -DartifactId=cocoon-maven-reports \
> -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
>
> Path to dependency:
> 1) org.apache.cocoon:cocoon-webapp:war:2.2.0-M2-SNAPSHOT
> 2) org.apache.cocoon:cocoon-maven-reports:jar:1.0
>
> ----------
>
> How to deal with this ?
I commented the extension for now as Maven doesn't use the artifact created by
the build but already needs it in a repository. We can only solve this problem
by releasing the extension (AFAIU).
Carsten, have we ever agreed formally on the checkstyle rules, which are the
content of the extension? If yes, could you release the cocoon-maven-reports
module together with the Spring configurator?
If not, we should vote on the rules. It will be a lot of fun to read dozens of
mails about coding conventions ;-)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: org.apache.cocoon:cocoon-maven-reports:jar:1.0 missing
Posted by Felix Knecht <fe...@otego.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jean-Christophe
Goto the [cocoon-src]/tools/cocoon-maven-reports directory and execute
mvn install
This will install it.
Regards
Felix
> I have the following error with a fresh updated code from cocoon
> svn repository :
>
> [INFO]
> ------------------------------------------------------------------------
>
>
> [ERROR] BUILD ERROR [INFO]
> ------------------------------------------------------------------------
>
>
> [INFO] Failed to resolve artifact.
>
> Missing: ---------- 1)
> org.apache.cocoon:cocoon-maven-reports:jar:1.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command: mvn install:install-file
> -DgroupId=org.apache.cocoon -DartifactId=cocoon-maven-reports \
> -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
>
> Path to dependency: 1)
> org.apache.cocoon:cocoon-webapp:war:2.2.0-M2-SNAPSHOT 2)
> org.apache.cocoon:cocoon-maven-reports:jar:1.0
>
> ----------
>
> How to deal with this ?
>
> Cheers,
>
> -- Jean-Christophe
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFsIFw2lZVCB08qHERAgF0AKDOqJgcgejfExOxxdPuP4FYjJjhHACfdttB
uRUcJVPLq3YiLFAc94d/zKY=
=GGfo
-----END PGP SIGNATURE-----