You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <nm...@byteaction.de> on 2006/10/01 00:18:48 UTC
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
plz use maven2 to build jspf..
bye
Norman
Guillermo Grandes (JIRA) schrieb:
> [ http://issues.apache.org/jira/browse/JSPF-33?page=comments#action_12438941 ]
>
> Guillermo Grandes commented on JSPF-33:
> ---------------------------------------
>
> Broken build... (trunk)
>
> compile:
> [javac] Compiling 3 source files to jspf/trunk/target/classes
> [javac] jspf/trunk/src/main/java/org/apache/james/jspf/SPFQuery.java:22: package org.apache.commons.cli does not exist
> [javac] import org.apache.commons.cli.CommandLine;
> [javac] ^
>
> build.xml from svn is correct?
>
>
>> Use commons cli for commandline parsing
>> ---------------------------------------
>>
>> Key: JSPF-33
>> URL: http://issues.apache.org/jira/browse/JSPF-33
>> Project: jSPF
>> Issue Type: Improvement
>> Reporter: Norman Maurer
>> Assigned To: Norman Maurer
>>
>> Now we add much more commandline options .. We should use commons cli for parsing.
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
[mvn assembly:assembly]: throw error (junit missing)
[mvn compile]: work ok... I will use this :-)
----- Original Message -----
From: "Stefano Bagnara" <ap...@bago.org>
To: "James Developers List" <se...@james.apache.org>
Sent: Sunday, October 01, 2006 4:09 PM
Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
parsing
> Hi Guillermo,
>
> you have to install maven2 and then simply follow this doc:
> http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20compile%20my%20application%20sources?
>
> Btw once you have maven installed and "mvn" in your path you just need a
> "mvn compile" or an "mvn assembly:assembly" to create the distributions.
>
> Stefano
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Stefano Bagnara <ap...@bago.org>.
Hi Guillermo,
you have to install maven2 and then simply follow this doc:
http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20compile%20my%20application%20sources?
Btw once you have maven installed and "mvn" in your path you just need a
"mvn compile" or an "mvn assembly:assembly" to create the distributions.
Stefano
Guillermo Grandes wrote:
> How-To? in James-Server trunk exists a BUILDING.txt, in jspf-trunk...
> no, and I have never worked with Maven...
>
> Thanks.
> Guillermo
>
> ----- Original Message ----- From: "Norman Maurer" <nm...@byteaction.de>
> To: "Guillermo Grandes (JIRA)" <se...@james.apache.org>
> Sent: Sunday, October 01, 2006 12:18 AM
> Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
> parsing
>
>
>> plz use maven2 to build jspf..
>>
>> bye
>> Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
How-To? in James-Server trunk exists a BUILDING.txt, in jspf-trunk... no,
and I have never worked with Maven...
Thanks.
Guillermo
----- Original Message -----
From: "Norman Maurer" <nm...@byteaction.de>
To: "Guillermo Grandes (JIRA)" <se...@james.apache.org>
Sent: Sunday, October 01, 2006 12:18 AM
Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
parsing
> plz use maven2 to build jspf..
>
> bye
> Norman
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
Ok! many thanks to both.
Guillermo.
----- Original Message -----
From: "Stefano Bagnara" <ap...@bago.org>
To: "James Developers List" <se...@james.apache.org>
Sent: Sunday, October 01, 2006 4:29 PM
Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
parsing
> Guillermo Grandes wrote:
>> well, I try this... mvn assembly:assembly say: "junit missing"
>> [...]
>> Missing:
>> ----------
>> 1) junit:junit:jar:3.8.1
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>> mvn install:install-file -DgroupId=junit -DartifactId=junit \
>> -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
>>
>> Path to dependency:
>> 1) org.apache.james:jspf:jar:0.9-SNAPSHOT
>> 2) junit:junit:jar:3.8.1
>> [...]
>> Any idea?
>
> Yes, this is a bug.
>
> You can fix this in 3 ways:
> 1) do the think explained above (download the jar and manually call the
> mvn install:install-file).
> 2) download the junit jar and put it in the jspf subfolder
> repos/third-party-m1/junit/jars/junit-3.8.1.jar
> 3) add "-Dmaven.test.skip=true" to your mvn command arguments so you don't
> need the tests to pass to build jspf.
>
> Currently you will need #3 anyway because our tests do not pass in trunk.
>
> I don't know if we should include junit in our repository or not, we'll
> talk about this later.
>
> Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Stefano Bagnara <ap...@bago.org>.
Guillermo Grandes wrote:
> yes, now assembly work OK... (included junits, 0 errors) :-)
You probably checked out it few hours ago: Norman udpated the openspf
yaml tests few hours ago and now the tests do no pass anymore.
Of course we'll try to fix this as soon as possible.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
yes, now assembly work OK... (included junits, 0 errors) :-)
----- Original Message -----
From: "Stefano Bagnara" <ap...@bago.org>
To: "James Developers List" <se...@james.apache.org>
Sent: Sunday, October 01, 2006 4:36 PM
Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
parsing
> Let me add an explanation: maven2 would automatically download junit but
> we added a custom configuration to prevent maven from downloading
> dependencies from untrusted repositories and junit is currently not
> available in the repositories we marked as trusted (ASF ones).
>
> The fourth solution would be to add ibiblio as the last repository in the
> pom.xml:
> -----
> <repository>
> <id>ibiblio</id>
> <name>Main maven repo</name>
> <url>http://repo1.maven.org/maven2</url>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </repository>
> -----
> This will automatically download junit when needed.
>
> Stefano
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
In defense of Stefano, I will say that I know the risks, and he advert to my
from the risks, and I never have worked with Maven, I do not know how-to
doing all that that you comment, so the explanation that Stefano has given
me was the suitable one to my situation. He has given me the option to
choose (and this is important to me, and the people).
Red pill or Blue pill? :-)
But IMHO it would be good that in jSPF-Trunk there was the explanation like
which there is in James-Server-Trunk (BUILDING.txt)...
for the dummies like I! :-)
Sidenote: My primary build tool is javac & black console ;-)
Thanks to both!
Guillermo
----- Original Message -----
SB>>>> The fourth solution would be to add ibiblio as the last repository in
SB>>>> the pom.xml
NJ>>> Please don't encourage people who don't know the risks to use insecure
NJ>>> repositories.
NJ>>> Explain the right way: setup a local repository, download and verify
NJ>>> the artifacts, add them to your local repository.
SB>> Do you do this when you say people to download ant? They should
SB>> download ant, verify it and then use it, but you simply say "download
SB>> ant" :-)
NJ> See the first hyperlink in the first sentence of
NJ> http://ant.apache.org/bindownload.cgi
NJ> For that matter, the entire first paragraph. YES, we tell people to
NJ> verify their downloads!
SB>> You quoted the second sentence from my mail. In the first sentece I was
SB>> explaing that it was not automatically downloaded because we removed
SB>> ibiblio repository because it is *untrusted*.
SB>> I believe Guillermo is smart enough to read 2 related sentences ;-)
NJ> Sure, but since Guillermo is not familiar with Maven, being smart
NJ> doesn't mean that he will immediately make the connection to the
NJ> security exposure.
NJ> Particularly if English is not his primary language, as well as Maven
NJ> not being his primary build tool.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> Noel J. Bergman wrote:
>>> The fourth solution would be to add ibiblio as the last repository in
>>> the pom.xml
>> Please don't encourage people who don't know the risks to use insecure repositories.
>>
>> Explain the right way: setup a local repository, download and verify
>> the artifacts, add them to your local repository.
> Do you do this when you say people to download ant? They should download
> ant, verify it and then use it, but you simply say "download ant" :-)
See the first hyperlink in the first sentence of http://ant.apache.org/bindownload.cgi. For that matter, the entire first paragraph. YES, we tell people to verify their downloads!
> You quoted the second sentence from my mail. In the first sentece I was
> explaing that it was not automatically downloaded because we removed
> ibiblio repository because it is *untrusted*.
> I believe Guillermo is smart enough to read 2 related sentences ;-)
Sure, but since Guillermo is not familiar with Maven, being smart doesn't mean that he will immediately make the connection to the security exposure. Particularly if English is not his primary language, as well as Maven not being his primary build tool.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
>> The fourth solution would be to add ibiblio as the last repository in
>> the pom.xml
>
> Please don't encourage people who don't know the risks to use insecure repositories.
>
> Explain the right way: setup a local repository, download and verify the artifacts, add them to your local repository.
>
> --- Noel
Do you do this when you say people to download ant? They should download
ant, verify it and then use it, but you simply say "download ant" :-)
You quoted the second sentence from my mail. In the first sentece I was
explaing that it was not automatically downloaded because we removed
ibiblio repository because it is *untrusted*.
I believe Guillermo is smart enough to read 2 related sentences ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by "Noel J. Bergman" <no...@devtech.com>.
> The fourth solution would be to add ibiblio as the last repository in
> the pom.xml
Please don't encourage people who don't know the risks to use insecure repositories.
Explain the right way: setup a local repository, download and verify the artifacts, add them to your local repository.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Stefano Bagnara <ap...@bago.org>.
Let me add an explanation: maven2 would automatically download junit but
we added a custom configuration to prevent maven from downloading
dependencies from untrusted repositories and junit is currently not
available in the repositories we marked as trusted (ASF ones).
The fourth solution would be to add ibiblio as the last repository in
the pom.xml:
-----
<repository>
<id>ibiblio</id>
<name>Main maven repo</name>
<url>http://repo1.maven.org/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
-----
This will automatically download junit when needed.
Stefano
Stefano Bagnara wrote:
> Guillermo Grandes wrote:
>> well, I try this... mvn assembly:assembly say: "junit missing"
>> [...]
>> Missing:
>> ----------
>> 1) junit:junit:jar:3.8.1
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>> mvn install:install-file -DgroupId=junit -DartifactId=junit \
>> -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
>>
>> Path to dependency:
>> 1) org.apache.james:jspf:jar:0.9-SNAPSHOT
>> 2) junit:junit:jar:3.8.1
>> [...]
>> Any idea?
>
> Yes, this is a bug.
>
> You can fix this in 3 ways:
> 1) do the think explained above (download the jar and manually call the
> mvn install:install-file).
> 2) download the junit jar and put it in the jspf subfolder
> repos/third-party-m1/junit/jars/junit-3.8.1.jar
> 3) add "-Dmaven.test.skip=true" to your mvn command arguments so you
> don't need the tests to pass to build jspf.
>
> Currently you will need #3 anyway because our tests do not pass in trunk.
>
> I don't know if we should include junit in our repository or not, we'll
> talk about this later.
>
> Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Stefano Bagnara <ap...@bago.org>.
Guillermo Grandes wrote:
> well, I try this... mvn assembly:assembly say: "junit missing"
> [...]
> Missing:
> ----------
> 1) junit:junit:jar:3.8.1
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=junit -DartifactId=junit \
> -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
>
> Path to dependency:
> 1) org.apache.james:jspf:jar:0.9-SNAPSHOT
> 2) junit:junit:jar:3.8.1
> [...]
> Any idea?
Yes, this is a bug.
You can fix this in 3 ways:
1) do the think explained above (download the jar and manually call the
mvn install:install-file).
2) download the junit jar and put it in the jspf subfolder
repos/third-party-m1/junit/jars/junit-3.8.1.jar
3) add "-Dmaven.test.skip=true" to your mvn command arguments so you
don't need the tests to pass to build jspf.
Currently you will need #3 anyway because our tests do not pass in trunk.
I don't know if we should include junit in our repository or not, we'll
talk about this later.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Guillermo Grandes <gu...@gmail.com>.
well, I try this... mvn assembly:assembly say: "junit missing"
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'assembly'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Apache JAMES jSPF
[INFO] task-segment: [assembly:assembly] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[INFO] Preparing assembly:assembly
[INFO] ----------------------------------------------------------------------------
[INFO] Building Apache JAMES jSPF
[INFO] ----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'commons-cli:commons-cli:pom:1.0:compile' is invalid. It
will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Downloading:
file:///opt/james/src/james/jspf/trunk/repos/third-party-m1/org.jvyaml/poms/jvyaml-0.1.pom
[WARNING] Unable to get resource from repository local-jspf-3rd-party-m1
(file:///opt/james/src/james/jspf/trunk/repos/third-party-m1)
Downloading:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/jvyaml/jvyaml/0.1/jvyaml-0.1.pom
[WARNING] Unable to get resource from repository central
(http://people.apache.org/repo/m2-ibiblio-rsync-repository)
Downloading:
http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.jvyaml/poms/jvyaml-0.1.pom
[WARNING] Unable to get resource from repository central-m1
(http://people.apache.org/repo/m1-ibiblio-rsync-repository)
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'commons-cli:commons-cli:pom:1.0:compile' is invalid. It
will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Downloading:
file:///opt/james/src/james/jspf/trunk/repos/third-party-m1/junit/jars/junit-3.8.1.jar
[WARNING] Unable to get resource from repository local-jspf-3rd-party-m1
(file:///opt/james/src/james/jspf/trunk/repos/third-party-m1)
Downloading:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/junit/junit/3.8.1/junit-3.8.1.jar
[WARNING] Unable to get resource from repository central
(http://people.apache.org/repo/m2-ibiblio-rsync-repository)
Downloading:
http://people.apache.org/repo/m1-ibiblio-rsync-repository/junit/jars/junit-3.8.1.jar
[WARNING] Unable to get resource from repository central-m1
(http://people.apache.org/repo/m1-ibiblio-rsync-repository)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) junit:junit:jar:3.8.1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=junit -DartifactId=junit \
-Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.james:jspf:jar:0.9-SNAPSHOT
2) junit:junit:jar:3.8.1
----------
1 required artifact is missing.
for artifact:
org.apache.james:jspf:jar:0.9-SNAPSHOT
from the specified remote repositories:
central (http://people.apache.org/repo/m2-ibiblio-rsync-repository),
local-jspf-3rd-party-m1
(file:///opt/james/src/james/jspf/trunk/repos/third-party-m1),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
central-m1 (http://people.apache.org/repo/m1-ibiblio-rsync-repository)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Sun Oct 01 16:15:28 CEST 2006
[INFO] Final Memory: 4M/8M
[INFO] ------------------------------------------------------------------------
Any idea?
----- Original Message -----
From: "Norman Maurer" <nm...@byteaction.de>
To: "James Developers List" <se...@james.apache.org>
Sent: Sunday, October 01, 2006 4:06 PM
Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
parsing
> Download maven2 (http://maven.apache.org) . Install it. and exec the
> following command in jspf dir:
>
> mvn assembly:assembly.
>
> thats all.
>
> bye
> Norman
>
> Guillermo Grandes schrieb:
>> How-To? in James-Server trunk exists a BUILDING.txt, in jspf-trunk... no,
>> and I have never worked with Maven...
>>
>> Thanks.
>> Guillermo
>>
>> ----- Original Message ----- From: "Norman Maurer" <nm...@byteaction.de>
>> To: "Guillermo Grandes (JIRA)" <se...@james.apache.org>
>> Sent: Sunday, October 01, 2006 12:18 AM
>> Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for commandline
>> parsing
>>
>>
>>> plz use maven2 to build jspf..
>>>
>>> bye
>>> Norman
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>> !EXCUBATOR:1,451fcb0853077934990936!
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Download maven2 (http://maven.apache.org) . Install it. and exec the
> following command in jspf dir:
> mvn assembly:assembly.
Or run Ant? You are maintaining build.xml as we agreed, right?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JSPF-33) Use commons cli for commandline parsing
Posted by Norman Maurer <nm...@byteaction.de>.
Download maven2 (http://maven.apache.org) . Install it. and exec the
following command in jspf dir:
mvn assembly:assembly.
thats all.
bye
Norman
Guillermo Grandes schrieb:
> How-To? in James-Server trunk exists a BUILDING.txt, in jspf-trunk...
> no, and I have never worked with Maven...
>
> Thanks.
> Guillermo
>
> ----- Original Message ----- From: "Norman Maurer" <nm...@byteaction.de>
> To: "Guillermo Grandes (JIRA)" <se...@james.apache.org>
> Sent: Sunday, October 01, 2006 12:18 AM
> Subject: Re: [jira] Commented: (JSPF-33) Use commons cli for
> commandline parsing
>
>
>> plz use maven2 to build jspf..
>>
>> bye
>> Norman
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
> !EXCUBATOR:1,451fcb0853077934990936!
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org