Re: [vote] separate mailings lists for humans/JIRA/CI/commits

2006-03-02 Thread Incze Lajos
Altough a mailfilter can do the job, it's allways better to keep
the traffic as low as possible. So, here it is a lurker

+1

incze

On Thu, Mar 02, 2006 at 06:20:43AM -0500, Vincent Siveton wrote:
 +0
 
 Vincent
 
 2006/3/1, Jason van Zyl [EMAIL PROTECTED]:
  Hi,
 
  I just wanted to close this up as I think it's a good idea and anything
  that let's people manage their mail better IMO is a good thing.
 
  +1
 
  In this type of vote it is non-technical so simple majority wins, but if
  it's close we can continue the discussion but I think a majority wanted
  preferred the separation.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: m2.. or mvn?

2005-10-15 Thread Incze Lajos
On Sat, Oct 15, 2005 at 02:38:10PM +0200, Arnaud HERITIER wrote:
 I prefer it too (essentially for the 1st reason). I hope that m3 (if there's 
 one) will not be incompatible with m2 projects !! ;-)
 
 Arnaud
 

Either solution is good for me, but should be mirrored
in the shell file, too (seems to me too small error
to deserve a private jira issue):

$ m2 --help
usage: maven [options] [goal(s)] [phase(s)]

[...]

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Compilation problems with latest from SVN

2005-08-24 Thread Incze Lajos
On Wed, Aug 24, 2005 at 12:03:55PM +0200, Carsten Ziegeler wrote:
 After updating from alpha-3 to the latest from SVN I can't compile
 Cocoon anymore. I think the problem is related to classloading or
 handling of classes.
 As one dependency we have the xml-apis-1.3.02 implementing DOM level 3
 interfaces. Although we have declared this dependency in the POM and the
 jar is downloaded, the DOM level 3 classes are not found. So I guess
 that classes inside the org.w3c.dom package (and others) comming from
 the dependencies are ignored and the system classes are used instead.
 (But this is just a guess).
 
 Any idea how to solve this?
 
 Carsten

It smelles as an endorsed problem. Maybe, there should be a way
to annotate a dependency to be endorsed. Until that, you'd better
to install that jar by hand somewhere in your java infrastructure.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Proposal for filtering of resources

2005-08-24 Thread Incze Lajos
On Wed, Aug 24, 2005 at 04:21:58PM +1000, Brett Porter wrote:
 I think this is reasonable, but I'd like to allow multiple sources
 (properties, and multiple files). The existence of the filtering element
 can be used to trigger it.
 
 filtering
   filterTokens
 tokenvalue/token
   /filterTokens
   filterFiles
 filterFilefoo.properties/filterFile
 filterFilebar.properties/filterFile
   /filterFiles
 /filtering

And what if you use something like this (in resource):
resource
  ...
  filteringprofile-reference/filtering
/resource

where the profile id references a filter specification
along the above line augmented with an context name,
which can be referenced. E.g.

  filteringWAS-5.1/filtering

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MNG-765) make it possible to use ${basedir}/xdocs for xdoc source in site plugin

2005-08-22 Thread Incze Lajos (JIRA)
[ http://jira.codehaus.org/browse/MNG-765?page=comments#action_44924 ] 

Incze Lajos commented on MNG-765:
-

I would welcome this possibility. The migration from maven1 to maven2 is not a 
one step process. Many projects should coexist in a maven1 cc environment (with 
other maven1 projects) AND get refactored to maven2. So, they'll have a 
project.xml and a pom.xml identity. It makes sense that projects living in a 
maven1 env don't have to be modified just because they are moving to maven2.

 make it possible to use ${basedir}/xdocs for xdoc source in site plugin
 ---

  Key: MNG-765
  URL: http://jira.codehaus.org/browse/MNG-765
  Project: Maven 2
 Type: Improvement
 Reporter: Brett Porter
  Fix For: 2.0-beta-2





-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: M2 Build from svn: Failed to parse model from file maven-plugin-parent-2.0-beta-1-SNAPSHOT.pom

2005-08-17 Thread Incze Lajos
On Wed, Aug 17, 2005 at 03:44:22AM +0200, Trygve Laugstøl wrote:
 On Wed, Aug 17, 2005 at 02:44:15AM +0300, Andrius Karpavicius wrote:
  Hello,
  
  Wanted to try the latest version of M2 as described in 
  http://maven.apache.org/maven2/building.html.
  
  Compilation and etc.. of Maven worked fine, but when trying to build my 
  project I get this error. The same task worked fine with alpha-3 release.
  
  Something should I change?
 
 It seems like you're still using the alpha-3 version as the POM format
 changed slighly from alpha 3 to trunk.
 
 Make sure that your PATH include the newly built Maven 2 and that M2_HOME
 also is pointing to the correct location.
 
 --
 Trygve

Wouldn't be good to start versioning the POM (it's allways 4.0.0, altough
changing)?

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding

2005-08-15 Thread Incze Lajos (JIRA)
[ http://jira.codehaus.org/browse/MNG-722?page=comments#action_44485 ] 

Incze Lajos commented on MNG-722:
-

You are not alone. No, at the moment it works with UTF-8, but not e.g. with 
ISO-8859-1.

I have a pom.xml. It is an UTF-8 xml file with accented characters. If I set 
the new outputEncoding
conf parameter, now I have a well rendered team list with UTF-8 output. But if 
I set outputEncoding
to ISO-8859-1, I'm given the same garbage az at the start.

The problem, I think, is with the above mentioned velocity properties (namely, 
output.encoding, the
input.encoding doesn't matter, as the maven-site.vm is pure ascii). The 
outputEncoding param is
rendered only into the output xhtml, regardless of the output.encoding velocity 
parameter (which
seems to be UTF-8 for some reason, I don't know, it is hard to find where it is 
set). So, before
merging the template this parameter should be set for velocity.

 maven-site-plugin maven-site.vm contains wired encoding
 ---

  Key: MNG-722
  URL: http://jira.codehaus.org/browse/MNG-722
  Project: Maven 2
 Type: Bug
   Components: maven-plugins
 Versions: 2.0-beta-1
  Environment: all
 Reporter: Incze Lajos
 Assignee: Vincent Siveton



 maven-site-plugin maven-site.vm contains wired encoding:
 meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 /
 It probably needs a conf. parameter and changed to
 meta http-equiv=Content-Type content=text/html; charset=$outputEncoding 
 /

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding

2005-08-15 Thread Incze Lajos (JIRA)
[ http://jira.codehaus.org/browse/MNG-722?page=comments#action_44500 ] 

Incze Lajos commented on MNG-722:
-

OK. I've tracked down the problem. The velocity propery is involved only when it
is the template engine that creates the output writer. In this case it is the 
DoxiaMojo
that crates the output writer using the java.io.FileWriter which uses the 
platform
default encoding (nowadays it is mostly UTF-8).

So, every place, where DoxiaMojo uses
new FileWriter(..)
this should be replaced by
   new OutputStreamWriter(new FileOutputStream(...), outputEncoding)

 maven-site-plugin maven-site.vm contains wired encoding
 ---

  Key: MNG-722
  URL: http://jira.codehaus.org/browse/MNG-722
  Project: Maven 2
 Type: Bug
   Components: maven-plugins
 Versions: 2.0-beta-1
  Environment: all
 Reporter: Incze Lajos
 Assignee: Vincent Siveton



 maven-site-plugin maven-site.vm contains wired encoding:
 meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 /
 It probably needs a conf. parameter and changed to
 meta http-equiv=Content-Type content=text/html; charset=$outputEncoding 
 /

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding

2005-08-15 Thread Incze Lajos (JIRA)
 [ http://jira.codehaus.org/browse/MNG-722?page=all ]

Incze Lajos updated MNG-722:


Attachment: patch.txt

FileWriter(...) - OutputStreamWriter(FileOutputStream(...), outputEncoding)

Works for me. Tested with ISO-8859-1, UTF-8 outputEncoding and
without outputEncoding conf. param., which defaults to ISO-8859-1.

 maven-site-plugin maven-site.vm contains wired encoding
 ---

  Key: MNG-722
  URL: http://jira.codehaus.org/browse/MNG-722
  Project: Maven 2
 Type: Bug
   Components: maven-plugins
 Versions: 2.0-beta-1
  Environment: all
 Reporter: Incze Lajos
 Assignee: Vincent Siveton
  Attachments: patch.txt


 maven-site-plugin maven-site.vm contains wired encoding:
 meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 /
 It probably needs a conf. parameter and changed to
 meta http-equiv=Content-Type content=text/html; charset=$outputEncoding 
 /

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding

2005-08-10 Thread Incze Lajos (JIRA)
maven-site-plugin maven-site.vm contains wired encoding
---

 Key: MNG-722
 URL: http://jira.codehaus.org/browse/MNG-722
 Project: Maven 2
Type: Bug
  Components: maven-plugins  
Versions: 2.0-beta-1
 Environment: all
 Reporter: Incze Lajos


maven-site-plugin maven-site.vm contains wired encoding:

meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 /

It probably needs a conf. parameter and changed to

meta http-equiv=Content-Type content=text/html; charset=$outputEncoding /

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding

2005-08-10 Thread Incze Lajos (JIRA)
[ http://jira.codehaus.org/browse/MNG-722?page=comments#action_44277 ] 

Incze Lajos commented on MNG-722:
-

The diagnosis OK, but the cure is bad. It basically depends on
the velocity settings what the output encoding will be. So, the
velocity properties should be adjusted to the required encoding, too.

 maven-site-plugin maven-site.vm contains wired encoding
 ---

  Key: MNG-722
  URL: http://jira.codehaus.org/browse/MNG-722
  Project: Maven 2
 Type: Bug
   Components: maven-plugins
 Versions: 2.0-beta-1
  Environment: all
 Reporter: Incze Lajos



 maven-site-plugin maven-site.vm contains wired encoding:
 meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 /
 It probably needs a conf. parameter and changed to
 meta http-equiv=Content-Type content=text/html; charset=$outputEncoding 
 /

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (MAVENUPLOAD-416) jmorph upload request

2005-06-23 Thread Incze Lajos (JIRA)
jmorph upload request
-

 Key: MAVENUPLOAD-416
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-416
 Project: maven-upload-requests
Type: Task
Reporter: Incze Lajos


An affix stripping stemmer and morphological analyzer in java (for Hungarian 
language, at the moment.)

Home: http://jhunlang.sourceforge.net/jmorph/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Improving the ease of access to metadata at runtime

2005-05-15 Thread Incze Lajos
On Sun, May 15, 2005 at 02:03:12PM -0400, Jason van Zyl wrote:
[...]
 META-INF/maven/${groupId}-${artifactId}.pom
[...]
 META-INF/maven/${groupId}-${artifactId}.properties

Why not ${groupId}/${artifactId}? The other scheme seems
to be unresolvable if you don't have restrictions on the
groupid/artifactid naming. (E.g. gid = a-b, aid = c; or
gid = a; aid = b-c.)

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XmlPullParser

2004-02-17 Thread Incze Lajos
On Tue, Feb 17, 2004 at 12:50:12PM +1000, Ben Walding wrote:
 I was merely responding to the but it's not in the repository part of 
 your email.
 
 As to how the bootstrap works - not sure what the preconditions are for 
 that.
 

Ben,

don't get me wrong, I've appeciated your reply. Simply tried to indicate
that the ant -f build-bootstrap.xml has to be able to build by itself
independently of the content of the current repository, and if it
needs the pull parser, then the pull parser has to be a core dependency
in the maven POM.

I did not want to go to jira becasue it seemed me to be a really simple
oversight.

Thanks again,

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



XmlPullParser

2004-02-16 Thread Incze Lajos
Hi,

seemingly, the curent HEAD wants to use some XmlPullParser,
but it's not in the repository. at the moment, and I can't
see it as a core dependency, either.

Here it is the dependency resolving section, no pullparser
dependency is here:
---
[mkdir] Created dir: /opt/incze/w/maven/bootstrap/bin
[bootstrap] Using the following for your maven.repo.local: /opt/sw/maven/repository
[bootstrap] Destination file /opt/sw/maven/repository/dom4j/jars/dom4j-1.4-dev-8.jar 
exists. Not dowloading.
[bootstrap] Destination file /opt/sw/maven/repository/ant/jars/ant-1.5.3-1.jar exists. 
Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/ant/jars/ant-optional-1.5.3-1.jar exists. Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-betwixt/jars/commons-betwixt-1.0-beta-1.20030111.103454.jar
 exists. Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-digester/jars/commons-digester-1.4.1.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-jelly/jars/commons-jelly-20030902.160215.jar exists. 
Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-jelly/jars/commons-jelly-tags-ant-20030625.032346.jar 
exists. Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-jelly/jars/commons-jelly-tags-define-20030211.142932.jar
 exists. Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-jelly/jars/commons-jelly-tags-util-20030211.141939.jar
 exists. Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-graph/jars/commons-graph-0.8.1.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-jexl/jars/commons-jexl-1.0-beta-1.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-logging/jars/commons-logging-1.0.1.jar exists. Not 
dowloading.
[bootstrap] Downloading dependency: 
http://www.ibiblio.org/maven/werkz/jars/werkz-20040114.081319.jar
[bootstrap] ...
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-beanutils/jars/commons-beanutils-1.6.1.jar exists. 
Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-cli/jars/commons-cli-1.0-beta-2.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-collections/jars/commons-collections-2.1.jar exists. 
Not dowloading.
[bootstrap] Downloading dependency: 
http://www.ibiblio.org/maven/commons-grant/jars/commons-grant-1.0-beta-5.jar
[bootstrap] 
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-io/jars/commons-io-20030203.000550.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/commons-lang/jars/commons-lang-1.0-b1.1.jar exists. Not 
dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/forehead/jars/forehead-1.0-beta-5.jar exists. Not dowloading.
[bootstrap] Destination file /opt/sw/maven/repository/log4j/jars/log4j-1.2.8.jar 
exists. Not dowloading.
[bootstrap] Destination file /opt/sw/maven/repository/which/jars/which-1.0.jar exists. 
Not dowloading.
[bootstrap] Destination file 
/opt/sw/maven/repository/xml-apis/jars/xml-apis-1.0.b2.jar exists. Not dowloading.
[bootstrap] Destination file /opt/sw/maven/repository/xerces/jars/xerces-2.4.0.jar 
exists. Not dowloading.
[bootstrap] Destination file /opt/sw/maven/repository/plexus/jars/plexus-0.6.jar 
exists. Not dowloading.
---

And after that a couple of compile fail of this type:

[javac] import org.xmlpull.v1.XmlPullParserFactory;
[javac]   ^
[javac] 
/opt/incze/w/maven/src/java/org/apache/maven/DefaultProjectMarshaller.java:73: package 
org.xmlpull.v1 does not exist
---

Am I missing something?

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XmlPullParser

2004-02-16 Thread Incze Lajos
On Tue, Feb 17, 2004 at 09:25:16AM +1000, Ben Walding wrote:
 XPP = http://www.ibiblio.org/maven/xpp3/jars/
 
 Incze Lajos wrote:
 

That's all right, and I know it, but a bootstrap build should
download it itself, shouldn't it? If it's needed to the bootstrap
build, it's a core dependency.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Bug in Jelly ?

2004-01-26 Thread Incze Lajos
On Mon, Jan 26, 2004 at 10:57:22PM +0100, Stoffels, Ralf (FWI-AW2) wrote:
 Hi,
 
 what is wrong with ${pom.artifacts.size()} ?
 [JellyException: Unable to create expression]
 
 E.g. ${pom.artifacts.clear()} does work.
 
 
 Ralf

Maybe you have the same problem that I had. Try this:

j:set var=paSizeLong value=${pom.artifacts.size()} /
j:set var=paSizeInt value=${paSizeLong.intValue()} /

Many times you can't use directly the long values returned from
the various length, size etc. operations, as the underlying
language is strongly typed.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Continuum: Maven Model

2004-01-18 Thread Incze Lajos
On Sun, Jan 18, 2004 at 04:31:10PM -0600, [EMAIL PROTECTED] wrote:
 Build OK.
 

Happy, to see. I'm not allways so lucky.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cvs commit: maven-components/surefire-runner/src/main/org/apache/maven/test MavenJUnitTestSuite.java MavenTestSuiteLoader.java ResultPrinter.java TestRunner.java

2004-01-14 Thread Incze Lajos
On Wed, Jan 14, 2004 at 03:56:44PM -, [EMAIL PROTECTED] wrote:
 evenisse2004/01/14 07:56:44
 
   Added:   surefire-runner .cvsignore project.xml
surefire-runner/src/main/org/apache/maven/test
 MavenJUnitTestSuite.java MavenTestSuiteLoader.java
 ResultPrinter.java TestRunner.java
   Log:
   Move from surefire maven plugin

Is it intentional that you avoid the java element in the
source path?

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: b10

2003-07-14 Thread Incze Lajos
On Mon, Jul 14, 2003 at 04:21:47PM +0200, Siegfried Gschl wrote:
 Hi folks,
 
 did I miss Maven B9 or was this release dropped ?!
 
 Siegfried Goeschl
 CTO

You missed it. It's been out for monthes.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Deploy API (artifact plugin)

2003-06-27 Thread Incze Lajos

 BTW:
 
 For the moment I have tested my API with username, user password 
 kept in properties file. I think such approach is not acceptable.
 
 You can use command line to pass properties to maven: 
 
 maven  war:deloy -Dmaven.repo.ibiblio.password = **
 
 
 This is already better ... but still not perfect.
 
 I will try to implement/use(if I find one) simple Prompter which will ask
 to type your password (eventually to enter other required parameters which
 are missing)
 
 regards
 
 
 Michal

I would avoid the command line passed password. It is much less secure
on unix than the password kept in a file. Command line can be seen by
simple ps commands, or e.g. linux systems store the in the /proc filesystem.
It should be used only from command files.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



clean build fails

2003-06-24 Thread Incze Lajos
On a fresh CVS clean bootstrap build I get (building maven with itself phase):


...
 [exec] [junit] dir attribute ignored if running in the same VM
 [exec] [junit] Running org.apache.maven.project.ProjectInheritanceTest
 [exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.397 sec
 [exec] [junit] [ERROR] TEST org.apache.maven.project.ProjectInheritanceTest 
FAILED
...
 [exec] BUILD FAILED
 [exec] There were test failures.

BUILD FAILED
file:/home/s/tmp/maven/build-bootstrap.xml:313: exec returned: 70


RedHat 8.0 (all recent patches), J2SDK 1.4.1_03.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: clean build fails

2003-06-24 Thread Incze Lajos
On Tue, Jun 24, 2003 at 11:24:00PM +0200, Rafal Krzewski wrote:
 Incze Lajos wrote:
  On a fresh CVS clean bootstrap build I get (building maven with itself phase):
  
  
  ...
   [exec] [junit] dir attribute ignored if running in the same VM
   [exec] [junit] Running org.apache.maven.project.ProjectInheritanceTest
   [exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.397 
  sec
   [exec] [junit] [ERROR] TEST 
  org.apache.maven.project.ProjectInheritanceTest FAILED
  ...
   [exec] BUILD FAILED
   [exec] There were test failures.
  
  BUILD FAILED
  file:/home/s/tmp/maven/build-bootstrap.xml:313: exec returned: 70
  
 
 I've seen that yesterday too, I even tried to post a message on that but
 it got munched by my email client (bad network day, or rather week to
 be more specific...)
 
 Could you please locate the associated failure report in 
 target/test-reports (it'll be something-ProjectInheritanceTest.txt) and 
 post it? I don't have mine handy ATM.
 

Yes, that's it:

line 122 (from src/test/java/test/org/apache/maven/project/ProjectInheritenceTest.java)

// Test Source Directories
assertEquals( src/java, p.getBuild().getSourceDirectory() );

and the fail:

FAILED
expected:... but was:/home/s/tmp/maven/src/test/extend/...
junit.framework.ComparisonFailure: expected:... but 
was:/home/s/tmp/maven/src/test/extend/...
-

So, it expects relative path and gets an absolute.

iSeems to me, that time to stick with on econvention (basedir relative,
or ${basedir}/... in POM) and gow through all the plugins and tests
to behave accordingly.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cvs commit: maven/src/test/java/org/apache/maven/project ProjectInheritanceTest.java

2003-06-24 Thread Incze Lajos
On Tue, Jun 24, 2003 at 10:14:05PM +, [EMAIL PROTECTED] wrote:
 jvanzyl 2003/06/24 15:14:05
 
   Modified:src/test/java/org/apache/maven/project
 ProjectInheritanceTest.java
   Log:
   o Need to use basedir.

That's ok for this test case. But there are other points
where (as we don't have a strict convention) the
programmer works according to the one (src/java) or the
other (${basedir}/src/java) convention in her/his mind.

E.g. if you use this style, the checkstyle report will go
wrong, as it's stylesheet allways preprends with ${basedir}
what it finds in the sourceDirectory tag.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: clean build (next round)

2003-06-24 Thread Incze Lajos
On Wed, Jun 25, 2003 at 12:53:39AM +0200, Incze Lajos wrote:
 Now, the problem is that we have a jsch-0.1.5 dependency, but no artifact
 at ibiblio to download.
 
 incze
 

Artifact plugin has compile error with jsch-0.1.5.jar, so no build yet.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



ProjectInheritenceTest doesn't compile

2003-06-24 Thread Incze Lajos
There is a basedir/baseDir mismatch in the recent patch.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: ProjectInheritenceTest doesn't compile

2003-06-24 Thread Incze Lajos
On Wed, Jun 25, 2003 at 01:31:39AM +0200, Incze Lajos wrote:
 There is a basedir/baseDir mismatch in the recent patch.
 
 incze
 

Other problem:

private String PS = System.getProperty( path.separator );

Should be:

private String FS = System.getProperty( file.separator );

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Maven.log - bootstrap build

2003-06-13 Thread Incze Lajos
On Fri, Jun 13, 2003 at 07:05:37PM +0100, [EMAIL PROTECTED] wrote:
 
 Has anyone had a look lately at their maven.log when bootstrap building
 maven?
 
 I dont know whether its something particular to my machine - but the log
 file has literally thousands of null chars at he beginning (nearly 3000!).
 
 Anyone else seeing this?
 
 -Nick
 

Yes.

incze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]