RE: XML entities and forward compatibility

2004-06-11 Thread Jörg Schaible
Nicol, Carl wrote on Friday, June 11, 2004 1:55 AM:

 I tried to use an external entity file for the list of
 developers and could not get it to work.
 
 Can you inherit from more than one file? I'm autogenerating
 the developers list file from several others so I don't want
 to muck about my project.xml file.

http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities
Does this help ?

-- Jörg

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



javadoc:deploy failure

2004-06-11 Thread Daniel Frey
The artifact plugin specifies to set up a repo. I did:

maven.repo.list = xmatrix
maven.repo.xmatrix = scp://www.xmatrix.ch
maven.repo.xmatrix.directory = /my/maven/repository
maven.repo.xmatrix.username = my_username
maven.repo.xmatrix.password = my_password

And I still get the same error. maven -X javadoc:deploy does not feedback
the exact problem. I just get:

Will deploy to 1 repository(ies): xmatrix
Deploying to repository: xmatrix
host: 'www.xmatrix.ch'
com.jcraft.jsch.JSchException: Auth fail

Is there a way to get a more detailed debug message?

Thanks
Daniel Frey

 From: Emmanuel Venisse [EMAIL PROTECTED]
 Subject: javadoc:deploy failure
 Date: Thu, 10 Jun 2004 14:16:07 +0200
 Content-Type: text/plain;
   charset=iso-8859-1
 
 javadoc:deploy goal use the artifact plugin
 (http://maven.apache.org/reference/plugins/artifact/) and the jar:deploy
 goal use the deploy plugin.
 
 You must set properties diffently for this txo plugins.
 
 Emmanuel
 
 - Original Message - 
 From: Daniel Frey [EMAIL PROTECTED]
 To: 'Maven Users List' [EMAIL PROTECTED]
 Sent: Thursday, June 10, 2004 12:52 PM
 Subject: javadoc:deploy failure
 
 
 Hello

 I try to deploy javadoc to the repository without success:

 maven -X javadoc:deploy
 ...
 Will deploy to 1 repository(ies): xmatrix
 Deploying to repository: xmatrix
 host: 'www.xmatrix.ch'
 Failed to deploy to: xmatrix Reason: Cannot connect. Reason: Auth
fail

 I don't understand that, and the debug feedback is sparesly. Deployment
of
 the jars work perfect (maven jar:deploy). Do you see any hint you can
give
 me to solve that problem?

 Thanks
 Daniel Frey


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



Re: Maven User Guide not available?

2004-06-11 Thread Erik Husby
Arnaud Heritier wrote:
I cleaned my IE cache and it works:
http://maven.apache.org/reference/user-guide.html
The PDF file size is 500Ko.
Don't you have a problem with your internet connection?
Arnaud
 

Well I cleaned the Firefox cache and the page is no visible.  Strange!
--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard 
Rm. 2192  320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]

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


AW: XML entities and forward compatibility

2004-06-11 Thread Oliver Noelle
By the way, is it correct that the goal convert-snapshots does not 
work together with external entities in maven-rc-3?

At least my tests showed that it would mess up the POM (and I understand 
that this is hard to do, how would you convert a dependency which is 
actually an entitiy reference?).

We also thought about ensuring project consistency with entities, but 
details like this make me also believe that a separate, clean solution 
for maven would be better than abusing entities for this.

Oliver


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



Jar help

2004-06-11 Thread Bielby, Randy J
Hello,
 
First, I'm a newbie and just getting started.  I'm trying to proof out
an existing build that is currently using Ant, while also making a
determination of Maven is a good choice for new projects.
 
I have a situation that I don't believe is unique but I can't seem to
find all the info I'm looking for.  I have several projects with a
number of dependent jars.  The development team is anywhere from 10-30
developers depending upon the project.  We are using WSAD and have as
one of the projects in our workspace a webapp.  This webapp contains all
the dependent jars within the WEB-INF/lib folder.  All the other project
within the workspace are included as dependent jars in the EAR.  I would
prefer that the compile uses the jars in the lib folder.  This is the
ensure that the deployed runtime code is the same as what the developers
have developed against.  I know this goes against Maven's perferred
method of retrieving dependencies for the repository.  I know that I can
override this behavior, but I'm struggling with how to go about it.   
 
I guess I could override the local repository to be the WEB-INF/lib, but
I'm not sure that will work due to the expected folder structure of the
repo.  I could also just not use the dependencies and add the jar to the
classpath.
 
Also, due to corporate defined standards, my jar names cannot contain
the version number (don't ask).  So I also need my jar dependencies to
be something like, log4j.jar instead of log4j-1.2.6.jar.  I have tried
eliminating the version from the dependency but I get, log4j-.jar
instead.
 
Randy Bielby
 
 
 


Re: Jar help

2004-06-11 Thread Julian C. Dunn
On Fri, 2004-06-11 at 14:32, Bielby, Randy J wrote:

 I have a situation that I don't believe is unique but I can't seem to
 find all the info I'm looking for.  I have several projects with a
 number of dependent jars.  The development team is anywhere from 10-30
 developers depending upon the project.  We are using WSAD and have as
 one of the projects in our workspace a webapp.  This webapp contains all
 the dependent jars within the WEB-INF/lib folder.  All the other project
 within the workspace are included as dependent jars in the EAR.  I would
 prefer that the compile uses the jars in the lib folder.  This is the
 ensure that the deployed runtime code is the same as what the developers
 have developed against.  I know this goes against Maven's perferred
 method of retrieving dependencies for the repository.  I know that I can
 override this behavior, but I'm struggling with how to go about it.   

Could you override the dependency retrieving by setting
maven.jar.override=true in your project.properties and then listing
the path to each of the JARs explicitly? In this case, the structure
does not have to respect the regular repo structure since you're not
overriding maven.repo.remote.

 Also, due to corporate defined standards, my jar names cannot contain
 the version number (don't ask).  So I also need my jar dependencies to
 be something like, log4j.jar instead of log4j-1.2.6.jar.  I have tried
 eliminating the version from the dependency but I get, log4j-.jar
 instead.

If you use the jar tag you can specify the filename explicitly.

- Julian

-- 
Julian C. Dunn, B.A.Sc.  [EMAIL PROTECTED]
Software Developer, CBC New Media Operations
Office: 2C310-I  *  Tel.: (416) 205-3311 x5592

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



Re: Jar help

2004-06-11 Thread Erik Husby
Bielby, Randy J wrote:
Hello,
First, I'm a newbie and just getting started.  I'm trying to proof out
an existing build that is currently using Ant, while also making a
determination of Maven is a good choice for new projects.
I have a situation that I don't believe is unique but I can't seem to
find all the info I'm looking for.  I have several projects with a
number of dependent jars.  The development team is anywhere from 10-30
developers depending upon the project.  We are using WSAD and have as
one of the projects in our workspace a webapp.  This webapp contains all
the dependent jars within the WEB-INF/lib folder.  All the other project
within the workspace are included as dependent jars in the EAR.  I would
prefer that the compile uses the jars in the lib folder.  This is the
ensure that the deployed runtime code is the same as what the developers
have developed against.  I know this goes against Maven's perferred
method of retrieving dependencies for the repository.  I know that I can
override this behavior, but I'm struggling with how to go about it.   

I guess I could override the local repository to be the WEB-INF/lib, but
I'm not sure that will work due to the expected folder structure of the
repo.  I could also just not use the dependencies and add the jar to the
classpath.
Also, due to corporate defined standards, my jar names cannot contain
the version number (don't ask).  So I also need my jar dependencies to
be something like, log4j.jar instead of log4j-1.2.6.jar.  I have tried
eliminating the version from the dependency but I get, log4j-.jar
instead.
Randy Bielby

 

Well one thing you can do which is what I've done for my WebLogic builds 
is to copy the dependencies from the repository to the WEB-INF/lib 
folder. I do this with

   deploy:copy-deps todir=${wli.app.lib.dir}/
Where wli.app.lib.dir is a property pointing at the WEB-INF/lib folder.
As for getting rid of the version numbers, I believe you could do 
something like
j:forEach var=lib items=${pom.artifacts}
   j:set var=dep value=${lib.dependency}/
   j:if test=${dep.getProperty('javalib')=='true'}
   ant:mkdir dir=${maven.war.webapp.dir}/javalib/
   j:if test=${dep.type =='jar'}
   ant:copy file=${lib.path}
   
tofile=${maven.war.webapp.dir}/javalib/${dep.artifactId}.jar
   verbose=${squid.verbose}/
   /j:if
   /j:if
   /j:forEach

In the above, I have some jars in my dependency list that need to go to 
a /javalib directory because they
are used by some applets. I tagged the dependency with the property 
javalib so I only copy the jars
that need to be in the /javalib directory.  I also don't want the 
version number on the resulting file which is accomplished by the 
${dep.artifactId}.jar name.

A dependency targeted for /javalib looks like
   dependency
   groupIdSquid/groupId
   artifactIdtaskmaster/artifactId
   version${squid.version}/version
   properties
   javalibtrue/javalib
   /properties
   /dependency
Hope this helps. I too have embarked on the task of replacing Ant with 
Maven, and have been pleased at
how easy it has been.

--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard 
Rm. 2192  320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]

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


Bulk Project Mavenizing tool?

2004-06-11 Thread Thomas . Lageson

I know about the genapp goal if you are starting out with a brand new
project.  I know about the eclipse goal to generate the .classpath and
.project files for eclipse.  I know about Mevenide that will help build
dependencies from within Eclipse (and other IDEs) and its POM builder.

But are there any tools, scripts or templates that will let me take my
multiple projects, with many subprojects and add in the additional files
(project.xml and project.properties) on a somewhat automated basis?

I have mavenized two projects so far and it seems fairly repetitious with
regards to copying the files, modifying to change the name, etc.  They are
fairly standard J2EE apps with jars, ejbs, wars, ears, but having a utility
would speed up the process.

Any ideas?

- Tom




==
This communication, together with any attachments hereto or links contained herein, is 
for the sole use of the intended recipient(s) and may contain information that is 
confidential or legally protected. If you are not the intended recipient, you are 
hereby notified that any review, disclosure, copying, dissemination, distribution or 
use of this communication is STRICTLY PROHIBITED.  If you have received this 
communication in error, please notify the sender immediately by return e-mail message 
and delete the original and all copies of the communication, along with any 
attachments hereto or links herein, from your system.

==
The St. Paul Travelers e-mail system made this annotation on 06/11/2004, 04:17:55 PM.


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



Re: javadoc:deploy failure

2004-06-11 Thread Paul Spencer
Danial,
Try connecting via ssh.  Using the command below, it should prompt for a 
password.

  ssh -l my_username www.matrix.ch
Some notes from my experience:
1) When using the property maven.repo.x.privatekey, you must also set 
maven.repo.x.passphrase.

2) I found setting maven.deployer.scp.compress to false helped.
3) site:deploy did not work on maven-rc2.  It works with rc3
From my build.properties, but these entries can also be in 
project.properties:
  # Common Remote repository definitions
  maven.repo.foo=scp://developer.foo.com
  maven.repo.foo.compress=false
  maven.repo.foo.privatekey=/cygwin/home/my_username/.ssh/id_rsa
  maven.repo.foo.passphrase=
  maven.repo.foo.username=my_username
  maven.deployer.scp.compress=false

From project.properties
  # Common Remote repository definitions
  maven.repo.list=foo
  maven.repo.foo=scp://developer.foo.com
  maven.repo.foo.directory=/cygdrive/f/Maven-Repository
  maven.repo.foo.group=maven
FYI:
  Client platform: Windows XP, Maven 1.0-rc3, jdk 1.4
  Server platform: windows 2000, cygwin for ssh and scp
Paul Spencer
Daniel Frey wrote:
The artifact plugin specifies to set up a repo. I did:
maven.repo.list = xmatrix
maven.repo.xmatrix = scp://www.xmatrix.ch
maven.repo.xmatrix.directory = /my/maven/repository
maven.repo.xmatrix.username = my_username
maven.repo.xmatrix.password = my_password
And I still get the same error. maven -X javadoc:deploy does not feedback
the exact problem. I just get:
Will deploy to 1 repository(ies): xmatrix
Deploying to repository: xmatrix
host: 'www.xmatrix.ch'
com.jcraft.jsch.JSchException: Auth fail
Is there a way to get a more detailed debug message?
Thanks
Daniel Frey

From: Emmanuel Venisse [EMAIL PROTECTED]
Subject: javadoc:deploy failure
Date: Thu, 10 Jun 2004 14:16:07 +0200
Content-Type: text/plain;
charset=iso-8859-1
javadoc:deploy goal use the artifact plugin
(http://maven.apache.org/reference/plugins/artifact/) and the jar:deploy
goal use the deploy plugin.
You must set properties diffently for this txo plugins.
Emmanuel
- Original Message - 
From: Daniel Frey [EMAIL PROTECTED]
To: 'Maven Users List' [EMAIL PROTECTED]
Sent: Thursday, June 10, 2004 12:52 PM
Subject: javadoc:deploy failure


Hello
I try to deploy javadoc to the repository without success:
   maven -X javadoc:deploy
   ...
   Will deploy to 1 repository(ies): xmatrix
   Deploying to repository: xmatrix
   host: 'www.xmatrix.ch'
   Failed to deploy to: xmatrix Reason: Cannot connect. Reason: Auth
fail
I don't understand that, and the debug feedback is sparesly. Deployment
of
the jars work perfect (maven jar:deploy). Do you see any hint you can
give
me to solve that problem?
Thanks
Daniel Frey

-
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: Bulk Project Mavenizing tool?

2004-06-11 Thread Dion Gillard
Could you copy a template project file and do a mass change later on?

On Fri, 11 Jun 2004 15:17:51 -0500, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 
 
 I know about the genapp goal if you are starting out with a brand new
 project.  I know about the eclipse goal to generate the .classpath and
 .project files for eclipse.  I know about Mevenide that will help build
 dependencies from within Eclipse (and other IDEs) and its POM builder.
 
 But are there any tools, scripts or templates that will let me take my
 multiple projects, with many subprojects and add in the additional files
 (project.xml and project.properties) on a somewhat automated basis?
 
 I have mavenized two projects so far and it seems fairly repetitious with
 regards to copying the files, modifying to change the name, etc.  They are
 fairly standard J2EE apps with jars, ejbs, wars, ears, but having a utility
 would speed up the process.
 
 Any ideas?
 
 - Tom
 
 ==
 This communication, together with any attachments hereto or links contained herein, 
 is for the sole use of the intended recipient(s) and may contain information that is 
 confidential or legally protected. If you are not the intended recipient, you are 
 hereby notified that any review, disclosure, copying, dissemination, distribution or 
 use of this communication is STRICTLY PROHIBITED.  If you have received this 
 communication in error, please notify the sender immediately by return e-mail 
 message and delete the original and all copies of the communication, along with any 
 attachments hereto or links herein, from your system.
 
 ==
 The St. Paul Travelers e-mail system made this annotation on 06/11/2004, 04:17:55 PM.
 
 -
 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: Jar help

2004-06-11 Thread John Casey
First of all, sorry for the long email.

The right way according to maven is probably going to seem tedious at
first from your point of view, but in the long run will probably save
you hours of headache:

I understand your desire to use WEB-INF/lib for the source of your
dependencies. However, I have a question about this. When in a
development scenario, are you versioning your dependencies right along
with everything else, such that WEB-INF/lib winds up in version control
too? If so, why?

The way I see it, there are two ways you can go on this. First, you can
choose to stick to the methodology you're using below, and probably use
something other than maven (JAM or ant might be a good choice). Second,
you can change your projects to _build_ the WEB-INF/lib from the
project.xml's set of dependencies, and manage a corporate repository for
proprietary artifacts. The second method is strongly preferred in the
maven world, and I'd like to take a second and try to convince you why
it's a good thing. The name of the jar file is irrelevant to this
choice, and I will explain this later.

If you have multiple projects, you're probably reusing many of the
dependencies in WEB-INF/lib (you even state that you have some
dependencies in the EAR, and probably referenced in the application.xml
or manifest.mf or somesuch). If any of these dependencies is
proprietary, this means that you have to update all the jars in all the
WEB-INF/lib-like locations in all projects in order to incorporate new
versions. It also means that your version control system is experiencing
bloat for storing the same file in different locations. Finally, since
the jar is a derivative of the source code, any proprietary jars are
essentially re-versioning a derivative of code you can already recover
via the sources (which are in version control themselves). From a
version control / codebase maintenance perspective, it's much easier to
centralize your storage of project artifacts (jars) and select from
these in order to make other artifacts (more jars, or wars, or ears, or
whatever).

Additionally, if you chose to publish a full description of your
project, including things like static code check results, and maybe
something like a dependency list, how would you produce this? This is
where the project.xml really becomes a powerful item. If you have the
name and version of a dependency, you can give a full description of
exactly what files are needed to run your code. For the sake of clarity
and recoverability, this can be invaluable. When you place the
project.xml under version control, you can now track these dependencies
(including version numbers, which I'm betting you can't recite to me
about the current version of your project). In the event you have to
recover to some previous incarnation of a project, you'll know exactly
which versions of which dependencies to look for.

As for the jar file names, you can simply use the jarjarname.jar/jar
element within a dependency/ specification. This will allow you to
have the following:

dependency
  groupIdcommons-lang/groupId
  artifactIdcommons-lang/artifactId
  version2.0/version
  jarcommons-lang.jar/jar
/dependency

and have maven look for repo/commons-lang/jars/commons-lang.jar
instead of repo/commons-lang/jars/commons-lang-2.0.jar.


This is a pathetically incomplete reasoning for why you should use the
maven approach, and I'm sure you'll get some more detail from others on
the list, but I wanted to provide at least one voice of reason on this
topic. Maven is hard to get at first, but once you do it will change the
way you think about producing software. It may seem strange to do things
in the recommended way, but in the end it will save you time and effort,
and make your codebase much more usable both for producing software and
for reporting on progress, etc.

Hope it helps,
-john

On Fri, 2004-06-11 at 14:32, Bielby, Randy J wrote:
 Hello,
  
 First, I'm a newbie and just getting started.  I'm trying to proof out
 an existing build that is currently using Ant, while also making a
 determination of Maven is a good choice for new projects.
  
 I have a situation that I don't believe is unique but I can't seem to
 find all the info I'm looking for.  I have several projects with a
 number of dependent jars.  The development team is anywhere from 10-30
 developers depending upon the project.  We are using WSAD and have as
 one of the projects in our workspace a webapp.  This webapp contains all
 the dependent jars within the WEB-INF/lib folder.  All the other project
 within the workspace are included as dependent jars in the EAR.  I would
 prefer that the compile uses the jars in the lib folder.  This is the
 ensure that the deployed runtime code is the same as what the developers
 have developed against.  I know this goes against Maven's perferred
 method of retrieving dependencies for the repository.  I know that I can
 override this behavior, but I'm struggling with how to go about it.   
  
 I 

XP %HOME% and Maven

2004-06-11 Thread niksa_os
I try Maven

In install guide stand: install_repo.bat %HOME%\.maven\repository

Problem is that I get new dir C:\Documents\some_files_and_dir and I should
get
C:\Documents and Settings\mvelic\.maven ???

Also %HOMEDRIVE%%HOMEPATH%\.maven\repository same thing.

I did try with install_repo.bat %HOME%\.maven\repository, but then I get
new dir

C:\maven\bin\%HOME%

Do I need to get C:\Documents and Settings\mvelic\.maven?
And how can I get it?

Thanks.