date:20051220

Hi Olivier

You can enable it in usePluginRegistry/ from your settings.xml
and the file will be in ~/.m2/plugin-registry.xml

-allan

Olivier Lamy wrote:

Hi,
I search documentation on plugin-registry.xml.
I found this
http://maven.apache.org/guides/introduction/introduction-to-plugin-regis
try.html.
But I need the full format explanation/sample as this documentation
http://maven.apache.org/maven-model/maven.html.
Is this available somewhere ?
Thanks a lot,
- Olivier

This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s). If
you have received this message in error please send it back to the sender and delete it.
Unauthorized publication, use, dissemination or disclosure of this message, either in
whole or in part is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci apres le message ), sont confidentiels et destines exclusivement a l'usage de la personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites.
**

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005

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

RE : [m2]plugin-registry.xml format

2005-12-20 Thread Olivier Lamy

Thanks.
I didn't knwon it was generated automatically with this ;-)

- Olivier

-Message d'origine-
De : Allan Ramirez [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 20 décembre 2005 13:00
À : Maven Users List
Objet : Re: [m2]plugin-registry.xml format


Hi Olivier

You can enable it in usePluginRegistry/ from your settings.xml and the
file will be in ~/.m2/plugin-registry.xml

-allan

Olivier Lamy wrote:

Hi,
I search documentation on plugin-registry.xml.
I found this 
http://maven.apache.org/guides/introduction/introduction-to-plugin-regi
s
try.html.
But I need the full format explanation/sample as this documentation
http://maven.apache.org/maven-model/maven.html.
Is this available somewhere ?
Thanks a lot,
- Olivier


This e-mail, any attachments and the information contained therein 
(this message) are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
** 
Ce message electronique et tous les fichiers joints ainsi que  les
informations contenues dans ce message ( ci apres le message ), sont
confidentiels et destines exclusivement a l'usage de la  personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci  de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.
** 


  

---
-

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 
12/16/2005
  





This e-mail, any attachments and the information contained therein (this 
message) are confidential and intended solely for the use of the addressee(s). 
If you have received this message in error please send it back to the sender 
and delete it. Unauthorized publication, use, dissemination or disclosure of 
this message, either in whole or in part is strictly prohibited.
** 
Ce message électronique et tous les fichiers joints ainsi que  les informations 
contenues dans ce message ( ci après le message ), sont confidentiels et 
destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. 
Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur 
et de le détruire. Toutes diffusion, publication, totale ou partielle ou 
divulgation sous quelque forme que se soit non expressément autorisées de ce 
message, sont interdites.
** 


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

Re: How to configure default plugins (exclude test)

2005-12-20 Thread cameron101

I too wish to exclude specific TestCase's but have tried the above
suggestion


 reporting
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
excludes
exclude**/*TransactionalTestCase.java/exclude
/excludes
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjxr-maven-plugin/artifactId
/plugin
/plugins
/reporting

/project
including updating the pluggins and the exclude does not appear to work !!
Any help greatly appreciated :-)




On 29/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Emmanuel

 Thanks for helping me.

 Stephen


 Quoting [EMAIL PROTECTED]:

  Hi
 
  Ok, I have figured this out now.  The key fact is that I had my
 configuration
  for my plugin in my POM was defined inside an executions tag.
 
  Basically for anyone else who needs to know this,
 
  You can configure the default behaviour of plugins in your build by
  adding a tag
  for the plugin to the build section of your pom.
 
  However you must NOT put the configuration section inside an
 Executions
  section or it will think that you are asking it to run the plugin again.
 
  your plugin should look like this:
 
  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-surefire-plugin/artifactId
  configuration
excludes
exclude**/*Test.java/exclude
/excludes
  /configuration
  /plugin
 
 
  and NOT like this
 
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
 executions
   execution
phasetest/phase
configuration
  excludes
exclude**/*ABCTest.java/exclude
  /excludes
/configuration
goals
   goaltest/goal
/goals
   /execution
 /executions
  /plugin
 
 
  Quoting [EMAIL PROTECTED]:
 
  Hi Emmanuel
 
  Thanks, I have tried that now but it has made no difference.
 
  Below is my trace and below that is my POM.  If you look at the
  trace you will
  see that the tests are getting run twice and the second time, the
 exclusions
  are being applied.
 
  I do appreciate your help.
 
  regards
 
  Stephen
 
 
  C:\workspaces\bdplus\bdp-coremvn -U install
  [INFO] Scanning for projects...
  [INFO]
 
 
  [INFO] Building Core
  [INFO]task-segment: [install]
  [INFO]
 
 
  [INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
  checking for
  updates from snapshots
  [INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
  checking for
  updates from central
  [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:checking for
  updates from snapshots
  [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:checking for
  updates from central
  [INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:checking for
  updates from snapshots
  [WARNING] repository metadata for: 'artifact
  org.apache.maven.plugins:maven-surefire-plugin' could not be retrieved
 from
  repository: snapshots due to an error: Error transferring file
  [INFO] Repository 'snapshots' will be blacklisted
  [INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:checking for
  updates from central
  [INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking
  for updates
  from central
  [INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking
 for
  updates from central
  [INFO] [resources:resources]
  [INFO] Using default encoding to copy filtered resources.
  [INFO] [compiler:compile]
  [INFO] Nothing to compile - all classes are up to date
  [INFO] [bdp-buildcreateenv:create {execution: default}]
  [INFO] Starting
  [INFO] Creating 4 directories
  [INFO] Directory
  C:\workspaces\bdplus\bdp-core\target\TestData\Output already
  exists.
  [INFO] Directory
  C:\workspaces\bdplus\bdp-core\target\TestData\Output\Bills\Standard
 already
  exists.
  [INFO] Directory
  C:\workspaces\bdplus\bdp-core\target\TestData\Output\Bills\Diverted
 already
  exists.
  [INFO] Directory C:\workspaces\bdplus\bdp-core\target\TestData\temp
 already
  exists.
  [INFO] Finished
  [INFO] [resources:testResources]
  [INFO] Using default encoding to copy filtered resources.
  [INFO] [compiler:testCompile]
  [INFO] Nothing to compile - all classes are up to date
  Downloading:
  http://repo1.maven.org/maven2/surefire/surefire/1.4/surefire-1.4.pom
  663b downloaded
  Downloading:
 
 http://repo1.maven.org/maven2/surefire/surefire-root/1.1/surefire-root-1.1.pom
  3K downloaded
  Downloading:
 
 http://repo1.maven.org/maven2/surefire/surefire-booter/1.4/surefire-booter-1.4.pom
  539b downloaded
  Downloading:

Antw: RE: Which variables are available, e.g. for thexdoclet-maven-plugin?

2005-12-20 Thread Stefan Rademacher

Hi,

thanks for your reply. It was already a little helpful. But I have one 
further question:
Obviously I can't find out all available variables in this way. For example the 
variable ${java.home} (which is used on 
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html)
 is available, but is set somwhere else. 

Does anybody know, where these variables are initialized and where I can find 
them? Additionally I would like to set some variables on my own. I just don't 
understand the mechanism behind this.

thanks a lot in advance,
Stefan

 [EMAIL PROTECTED] 19.12.2005 19:56 
Hi,

AFAIK this variable (project.build.outputDirectory) comes from pom.xml as 
follows:

project
...
build
outputDirectorytarget/classes/outputDirectory
/build
...
/project

Hope this helps.
Dário



-Original Message-
From: Stefan Rademacher [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 19 de dezembro de 2005 13:35
To: Maven Users List
Subject: Which variables are available, e.g. for
thexdoclet-maven-plugin?


Hello,

on the page for the xdoclet-maven-plugin there is an example, which
contains a variable ${project.build.outputDirectory}.
Where can I find out generally, which variables are available in a
pom.xml? And another question is: Can I define my own variables
somwhere?

Would be great, if anyone can tell me.
Bye,
Stefan

-
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: including empty directories in a war build

2005-12-20 Thread Frank Russo

It should. I consider this a bug, but I'll defer to the developers...

Frank Russo
Senior Developer
FX Alliance, LLC

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 19, 2005 9:06 PM
 To: Maven Users List
 Cc: Maven Users List
 Subject: RE: including empty directories in a war build
 
 
 
 Dear all,
Maven war plugin doesn't copy empty folder to .war file.
 
 
 
 
 
 
 
 thanks.
 Tel: (020)36315358-328 Fax: (020)36315170
 
 
   
   

   Brian E. Fox  
   

   [EMAIL PROTECTED]To:   
 Maven Users List users@maven.apache.org   
 
   inity.nucc:
   

Subject:  RE: 
 including empty directories in a war build
 
   20/12/2005 07:42
   

   Please respond to   
   

   Maven Users
   

   List   
   

   
   

   
   

 
 
 
 
 Ah, I misunderstood you. I thought you already had the folder 
 but the war plugin was skipping the empty dirs. Glad you got 
 it working.
 
 -Original Message-
 From: Frank Russo [mailto:[EMAIL PROTECTED]
 Sent: Monday, December 19, 2005 4:39 PM
 To: Maven Users List
 Subject: RE: including empty directories in a war build
 
 I got it working using the antrun plugin as follows (not sure 
 if the best way, but it was the only way it worked):
  plugins
  plugin
  artifactIdmaven-antrun-plugin/artifactId
  executions
  execution
  phasecompile/phase
  configuration
  tasks
  mkdir 
 dir=target/fxalladmin/WEB-INF/bigbrother/
  /tasks
  /configuration
  goals
  goalrun/goal
  /goals
  /execution
  /executions
  /plugin
  /plugins
 
 Alternate solutions are welcome...
 
 
 Frank Russo
 Senior Developer
 FX Alliance, LLC
 
  -Original Message-
  From: Brian E. Fox [mailto:[EMAIL PROTECTED]
  Sent: Monday, December 19, 2005 4:10 PM
  To: Maven Users List
  Subject: RE: including empty directories in a war build
 
 
  Bummer. I'm not sure how that would work without code changes then.
 
  -Original Message-
  From: Frank Russo [mailto:[EMAIL PROTECTED]
  Sent: Monday, December 19, 2005 2:50 PM
  To: Maven Users List
  Subject: RE: including empty directories in a war build
 
  I see where you meant. The includes element is for configuring a 
  resource. By doing that, if I could get it to work, that would 
  automatically put it in web-inf/classes. All resources go into the 
  web-inf/classes directory. I need it to go in web-inf.
 
  Also, I tried a bunch of combinations with the includes 
 just to see if
 
  it would copy the empty folder, but it didn't work...
 
  Frank Russo
  Senior Developer
  FX Alliance, LLC
 
   -Original Message-
   From: Frank Russo
   Sent: Monday, December 19, 2005 2:15 PM
   To: Maven Users List
   Subject: RE: including empty directories in a war build
  
  
   Do you mean for the plugin element in the pom? Just want
  to clarify
   where you are suggesting this.
  
   Thanks...
  
   Frank Russo
   Senior Developer
   FX Alliance, LLC
  
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 1:13 PM
To: Maven Users List
Subject: RE: including empty directories in a war build
   
   
Although hardly an expert, I have poked around in the war
  plugin. It

Re: Antw: RE: Which variables are available, e.g. for thexdoclet-maven-plugin?

2005-12-20 Thread ir. ing. Jan Dockx

You can add a section to the pom like this:

properties>
ppw.javaSourceDirectory>src/main/java/ppw.javaSourceDirectory>

ppw.torytSourceDirectory>src/test/toryt/ppw.torytSourceDirectory>
...
/properties>


and access those properties as ${ppw.javaSourceDirectory} and ${ppw.torytSourceDirectory}.


For the rest: you are absolutely right. It is impossible to find out which properties do exist. For us, ${project.build.outputDirectory} does not work, whatever the docs say. Point is, these must be some ant/velocity style properties that are defined somewhere, hard coded. It would be incredibly helpful if maven would phase that out, and instead use an EL, like Commons EL or OGNL.

To see what doesn't work, we use ant echo's bound to some phase, like this:

build>
...
plugins>

x-tad-smaller plugin>
artifactId>maven-antrun-plugin/artifactId>
executions>
execution>
phase>validate/phase>
configuration>
tasks>

echo>/echo>

echo>/echo>

echo>/echo>

echo>/echo>
echo>user.name: ${user.name}/echo>
echo>pom: ${pom}/echo>
echo>settings: ${settings}/echo>
echo>pom.groupId: ${pom.groupId}/echo>
echo>pom.artifactId: ${pom.artifactId}/echo>
echo>pom.packaging: ${pom.packaging}/echo>
echo>pom.name: ${pom.name}/echo>
echo>pom.description: ${pom.description}/echo>
echo>pom.url: ${pom.url}/echo>
echo>pom.mailingLists: ${pom.mailingLists}/echo>
echo>pom.developers: ${pom.developers}/echo>
echo>pom.scm.connection: ${pom.scm.connection}/echo>
echo>pom.organization: ${pom.organization}/echo>
echo>project: ${project}/echo>
echo>maven: ${maven}/echo>
echo>maven.project: ${maven.project}/echo>
echo>project.build.sourceDirectory: ${project.build.sourceDirectory}/echo>
echo>pom.build: ${project.build}/echo>
echo>toedeloe: ${toedeloe}/echo>
echo>user.language: ${user.language}/echo>
echo>user.country: ${user.country}/echo>

echo>/echo>

echo>/echo>

echo>/echo>

echo>/echo>
/tasks>
/configuration>
goals>
goal>run/goal>
/goals>
/execution>
/executions>
/plugin>
/plugins>
/build>
/x-tad-smaller



On 20 Dec 2005, at 14:04, Stefan Rademacher wrote:

Hi,

thanks for your reply. It was already a little helpful. But I have one further question:
Obviously I can't find out all available variables in this way. For example the variable ${java.home} (which is used on http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) is available, but is set somwhere else. 

Does anybody know, where these variables are initialized and where I can find them? Additionally I would like to set some variables on my own. I just don't understand the mechanism behind this.

thanks a lot in advance,
Stefan

[EMAIL PROTECTED] 19.12.2005 19:56 >>>
Hi,

AFAIK this variable (project.build.outputDirectory) comes from pom.xml as follows:

project>
...
build>
outputDirectory>target/classes/outputDirectory>
/build>
...
/project>

Hope this helps.
Dário



-Original Message-
From: Stefan Rademacher [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 19 de dezembro de 2005 13:35
To: Maven Users List
Subject: Which variables are available, e.g. for
thexdoclet-maven-plugin?


Hello,

on the page for the xdoclet-maven-plugin there is an example, which
contains a variable ${project.build.outputDirectory}.
Where can I find out generally, which variables are available in a
pom.xml? And another question is: Can I define my own variables
somwhere?

Would be great, if anyone can tell me.
Bye,
Stefan

-
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]


x-tad-smallerMet vriendelijke groeten,

Jan Dockx
/x-tad-smallerx-tad-smaller
PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller
Cdt.Weynsstraat 85 
B-2660 Hoboken 
Tel: +32 3 448.33.38 
Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger
/x-tad-biggerx-tad-smaller
PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25/x-tad-smallerx-tad-bigger
/x-tad-biggerx-tad-smaller
http://www.peopleware.be/
/x-tad-smallerx-tad-smallerhttp://www.mobileware.be//x-tad-smaller


smime.p7s
Description: S/MIME cryptographic signature

RE: including empty directories in a war build

2005-12-20 Thread Frank Russo

No. There wasn't a misunderstanding. I did have the folder. This was a
workaround in my opinion. The war plugin should do this. I'm pretty sure
ant will copy empty folders as part of the war task. I'm not certain of
this though.

Personally, I think the war plugin is very incomplete. All is does is
copy a standard web-inf as is, puts any defined resources into the
web-inf/classes folder, and adds dependencies to the web-inf/lib folder.
In ant, I can specify other things that I want moved from one folder in
my source structure to the web-inf folder. 

Here is an example of what I mean:
war destfile=my.war webxml=src/main/webapp/conf/web.xml
webinf
fileset dir=src/main/scripts/
/webinf
/war
In this example, anything that is in src/main/scripts would be included
in the war under web-inf. This kind of mechanism is missing from the war
plugin, or if it's not, then it's not documented clearly. 

Again, I'm not sure if this would have copied my empty folder, but it
would have copied my bin folder that contains my shell script files, and
I still could have used the mkdir command I used below. 

As far as building the rest of a webapp, for things like javascript,
images, css files, etc, I would like to have them in src/main/webapp/js,
etc, and then have them moved to the war's web-inf as they are above. As
of now, I have to have them in src/main/webapp/web-inf/js for them to be
war'd up properly.

How do the rest of you using this plugin feel? Any input from the
developers on your thoughts about this would be greatly appreciated as
well.

Thanks...

Frank Russo
Senior Developer
FX Alliance, LLC

 -Original Message-
 From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 19, 2005 6:42 PM
 To: Maven Users List
 Subject: RE: including empty directories in a war build
 
 
 Ah, I misunderstood you. I thought you already had the folder 
 but the war plugin was skipping the empty dirs. Glad you got 
 it working. 
 
 -Original Message-
 From: Frank Russo [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 19, 2005 4:39 PM
 To: Maven Users List
 Subject: RE: including empty directories in a war build
 
 I got it working using the antrun plugin as follows (not sure 
 if the best way, but it was the only way it worked):
   plugins
   plugin
   artifactIdmaven-antrun-plugin/artifactId
   executions
   execution
   phasecompile/phase
   configuration
   tasks
   mkdir
 dir=target/fxalladmin/WEB-INF/bigbrother/
   /tasks
   /configuration
   goals
   goalrun/goal
   /goals
   /execution
   /executions
   /plugin
   /plugins
 
 Alternate solutions are welcome...
 
 
 Frank Russo
 Senior Developer
 FX Alliance, LLC
 
  -Original Message-
  From: Brian E. Fox [mailto:[EMAIL PROTECTED]
  Sent: Monday, December 19, 2005 4:10 PM
  To: Maven Users List
  Subject: RE: including empty directories in a war build
  
  
  Bummer. I'm not sure how that would work without code changes then.
  
  -Original Message-
  From: Frank Russo [mailto:[EMAIL PROTECTED]
  Sent: Monday, December 19, 2005 2:50 PM
  To: Maven Users List
  Subject: RE: including empty directories in a war build
  
  I see where you meant. The includes element is for configuring a
  resource. By doing that, if I could get it to work, that would 
  automatically put it in web-inf/classes. All resources go into the 
  web-inf/classes directory. I need it to go in web-inf.
  
  Also, I tried a bunch of combinations with the includes 
 just to see if
 
  it would copy the empty folder, but it didn't work...
  
  Frank Russo
  Senior Developer
  FX Alliance, LLC
  
   -Original Message-
   From: Frank Russo
   Sent: Monday, December 19, 2005 2:15 PM
   To: Maven Users List
   Subject: RE: including empty directories in a war build
   
   
   Do you mean for the plugin element in the pom? Just want
  to clarify
   where you are suggesting this.
   
   Thanks...
   
   Frank Russo
   Senior Developer
   FX Alliance, LLC
   
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 1:13 PM
To: Maven Users List
Subject: RE: including empty directories in a war build


Although hardly an expert, I have poked around in the war
  plugin. It
  
uses the plexus directory scanner to gen a list of artifacts to
include. This is probably why it won't find empty
  folders. You may
be able to override this using the includes/excludes
  settings (note
that currently , separated lists don't work). (ie you
  could add an
include to /foldername that you wanted to keep)

-Original

null pointer exception in ejbdoclet

2005-12-20 Thread Karthik V

 Please help me understand this stack trace .. got this while trying to run 
ejbdoclet on a bunch of files... 
 
Deploy TEMPLATE URL: jar:file:C:\Documents and 
Settings\karthikv\.maven\repository\xdoclet\jars\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-deploy_wsdd.xdt
Undeploy TEMPLATE URL: jar:file:C:\Documents and 
Settings\karthikv\.maven\repository\xdoclet\jars\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-undeploy_wsdd.xdt
java.lang.NullPointerException
at java.util.StringTokenizer.init(StringTokenizer.java:182)
at 
xdoclet.tagshandler.PackageTagsHandler.getPackageNameFor(PackageTagsHandler.java:60)
at 
xdoclet.tagshandler.PackageTagsHandler.getPackageNameFor(PackageTagsHandler.java:35)
at 
xdoclet.tagshandler.PackageTagsHandler.packageNameAsPathFor(PackageTagsHandler.java:114)
at 
xdoclet.GenerationManager.isGenerationNeeded(GenerationManager.java:345)
at 
xdoclet.GenerationManager.isGenerationNeeded(GenerationManager.java:182)
at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:615)
at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597)
at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198)
at 
xdoclet.modules.ejb.dd.EjbDotXmlSubTask.execute(EjbDotXmlSubTask.java:217)
at xdoclet.XDocletMain.start(XDocletMain.java:48)
at xdoclet.DocletTask.start(DocletTask.java:464)
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at 
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.PreGoalTag$1.firePreGoal(PreGoalTag.java:87)
at com.werken.werkz.Goal.firePreGoalCallbacks(Goal.java:691)
at com.werken.werkz.Goal.fire(Goal.java:616)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:488)
at org.apache.maven.cli.App.main(App.java:1239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
 
BUILD FAILED
File.. C:\Documents and 
Settings\karthikv\.maven\cache\maven-xdoclet-plugin-1.2.3\plugin.jelly
Element... ejbdoclet
Line.. 27
Column 20
Unexpected error 


Thanks
Karthik.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

fileset doesnt seem to work

2005-12-20 Thread Karthik V

 I'm new to maven. Trying to use maven 1.0.2 xdoclet:ejbdoclet on some ejb code 
to generate home interfaces and compile them. I'm using fileset in 
project.properties to compile only the files ending with Bean.java, and also 
exclude some of these Bean files. My problem is, maven doesnt seem to use my 
fileset. It just runs ejbdoclet on all files, and complains of errors. I dont 
care about the errors in the other files, but I know the Bean files are error 
free ... the same build runs properly with an ANT script. Below is the fileset 
part -
 
maven.xdoclet.ejbdoclet.fileset.0=true
maven.xdoclet.ejbdoclet.fileset.0.include=**/beans/**/*Bean.java
maven.xdoclet.ejbdoclet.fileset.0.exclude=**/xyz/beans/**/*Bean.java
 
The error starts like this -
Generating EJB deployment descriptor (ejb-jar.xml).
Error parsing File C:\beans\util\EJBUtils.java:Encountered  at line 37, 
column 22.
Was expecting one of:
IDENTIFIER ...
[ ...
 
As you can see, the file EJBUtils.java is being touched when its not supposed 
to be.
 

Thanks
Karthik.



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[m2] stop password being requested on site deploy

2005-12-20 Thread Patrick O'shea

Hi,

I want to deploy a site without any user interaction, currently it asks me 
for a password
even though it is in the settings.xml

In my pom.xml i have defined:
distributionManagement
site
  idscmsite/id
  namedeploy site/name
  urlscp://cassiusgroup-3.internal.org/var/www/projname//url   
 
/site
  /distributionManagement 

And in the settings.xml i have defined:
server
  idscmsite/id
  usernamepo82266/username
  passwordpo82266/password
/server


Is there something else, i'm missing ?
thanks
Patrick

Re: How do I build maven-artifact-ant-2.0.2-dep.jar?

2005-12-20 Thread Matt Raible

Hmmm, I'm able to build the JAR just fine by cd-ing into
maven-artifact-ant and running mvn assembly:assembly.  However, when
I copy it to my project, I get:

BUILD FAILED
C:\Source\equinox\build.xml:24: Unable to find component: org.apache.maven.artif
act.repository.layout.ArtifactRepositoryLayout[default]

Total time: 0 seconds

I've tried running mvn install on a number of other modules before
running assembly, but I can't get maven-repository-tools to build. 
The error I'm getting is:

[INFO] Failed to resolve artifact.

required artifacts missing:
  org.apache.maven:maven-core:jar:2.0-SNAPSHOT
  org.apache.maven:maven-artifact:jar:2.0-SNAPSHOT
  plexus:plexus:jar:1.0-alpha-1
  org.apache.maven:maven-model:jar:2.0-SNAPSHOT
  xstream:xstream:jar:1.0-SNAPSHOT

for the artifact:
  org.apache.maven:maven-repository-tools:jar:1.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

Also, the Repository.java has a System.out.println that should
probably be removed.

Index: src/main/java/org/apache/maven/artifact/ant/Repository.java

===

--- src/main/java/org/apache/maven/artifact/ant/Repository.java (revision
357937)

+++ src/main/java/org/apache/maven/artifact/ant/Repository.java (working copy)

@@ -36,7 +36,6 @@


 public String getId()
 {
-   System.out.println(Repository.getId() ==  + getInstance().id);
if (getInstance().id == null)
{
throw new BuildException(id must be specified for a
repository definition);

Thanks,

Matt

On 12/19/05, Brett Porter [EMAIL PROTECTED] wrote:
 The 2.0.2-SNAPSHOT is here:

 https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/

 Sorry, the dev docs haven't been updated to reflect this yet, it was a
 recent change.

 - Brett

 On 12/20/05, Matt Raible [EMAIL PROTECTED] wrote:
  I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for
  distribution with a project of mine (Equinox).  I could wait for the
  2.0.2 release, but I'd prefer to get the release done before COB
  tomorrow b/c that's when I go on vacation. ;-)
 
  I checked out maven from svn using:
 
  svn co https://svn.apache.org/repos/asf/maven/trunks maven
 
  I've been able to build everything, but versions are showing up with
  version 2.1-SNAPSHOT, and I can't figure out how to build the
  artifact-ant-*-dep.jar.  Am I checking out from the wrong repository?
 
  Thanks,
 
  Matt
 
  -
  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: problem with maven2 on OS X and JDK 1.5

2005-12-20 Thread Carlos Sanchez

The problem is at this line
c = cl.loadClass( com.sun.tools.javac.Main );
in
http://svn.plexus.codehaus.org/trunk/plexus-components/plexus-compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java?rev=2727view=auto

I don't know why this should be a problem as nobody else is reporting
problems under mac and some of the developers are using it. Maybe you
have different security options in your JDK?

Workarounds may be using some of the compiler options, like fork or compilerId
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html


BTW Sources for the compile plugin are at
http://svn.apache.org/viewcvs.cgi/maven/plugins/trunk/maven-compiler-plugin/
svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-compiler-plugin


On 12/20/05, Conrad O'Dea [EMAIL PROTECTED] wrote:
 Hi Carlos,

 On 19 Dec 2005, at 22:26, Carlos Sanchez wrote:

  Can you try with 2.0?

 I tried this with 2.0 and the same exception is being raised.

 It looks like a ClassLoader in the maven-compiler-plugin is trying to
 define a class from the java.lang package, which is not allowed.
 I've been trying to get to the source code of the plugin to try and
 dig a little deeper into what's going on but it does not seem to be
 available. Trying to view through web-access at [1] gets a 404 and
 trying a subversion checkout [2] results in a 'path not found' error.

 Any clues as to what may be going on or how to get the relevant
 source would be appreciated.

 thanks
 Conrad


 [1] http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-
 plugins/maven-compiler-plugin
 [2] svn checkout http://svn.apache.org/repos/asf/maven/components/
 trunk/maven-plugins/maven-compiler-plugin maven-compiler-plugin

 
  On 12/19/05, Conrad O'Dea [EMAIL PROTECTED] wrote:
  Hi,
 
  I've run into a problem with maven on OS X and JDK 1.5.  We're just
  starting to migrate our project over to Maven 2 and the initial
  project will not build on my Mac.  I can reproduce the problem by
  creating a 'Hello World' project using this command:
 
  $ mvn archetype:create -DgroupId=foo.bar -DartifactId=foo-bar
 
  and after a chunk of output, it printed 'BUILD SUCCESSFUL'.  However,
  when compiling the project, it fails with the following error (full
  stack trace at end of mail).
 
  [ERROR] BUILD ERROR
  [INFO]
  -
  ---
  
  [INFO] Fatal error compiling
 
  Embedded error: Prohibited package name: java.lang
 
  If I switch to a 1.4 JDK, the project builds without problems.
  Unfortunately our actual project requires JDK 1.5.
 
  Can anyone give advice on what, if anything, I can do to workaround
  this?
 
  thanks
  Conrad
 
  $ mvn --version
  Maven version: 2.0.1
  [EMAIL PROTECTED] ~/scratch/maven/foo-bar]
  $ java -version
  java version 1.5.0_05
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-83)
  Java HotSpot(TM) Client VM (build 1.5.0_05-48, mixed mode, sharing)
 
  $ mvn -e compile
  + Error stacktraces are turned on.
  [INFO] Scanning for projects...
  [INFO]
  -
  ---
  
  [INFO] Building Maven Quick Start Archetype
  [INFO]task-segment: [compile]
  [INFO]
  -
  ---
  
  [INFO] [resources:resources]
  [INFO] Using default encoding to copy filtered resources.
  [INFO] [compiler:compile]
  Compiling 1 source file to /Users/codea/scratch/maven/foo-bar/target/
  classes
  [INFO]
  -
  ---
  
  [ERROR] BUILD ERROR
  [INFO]
  -
  ---
  
  [INFO] Fatal error compiling
 
  Embedded error: Prohibited package name: java.lang
  [INFO]
  -
  ---
  
  [INFO] Trace
  org.apache.maven.lifecycle.LifecycleExecutionException: Fatal error
  compiling
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
  (DefaultLifecycleExecutor.java:555)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
  fec
  ycle(DefaultLifecycleExecutor.java:472)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
  (DefaultLifecycleExecutor.java:451)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
  dle
  Failures(DefaultLifecycleExecutor.java:303)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
  ts(
  DefaultLifecycleExecutor.java:270)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
  (DefaultLifecycleExecutor.java:139)
  at org.apache.maven.DefaultMaven.doExecute
  (DefaultMaven.java:322)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
  115)

Re: my first m2 plugin

2005-12-20 Thread Wim Deblauwe


  What if I only want the direct deps instead of the transitive ones?
 
  ${project.dependencies} - but these are just model dependencies, not
  artifacts. If you need the artifacts, take the union of this and
  ${project.artifacts}.


I think that many plugins use this functionality, so maybe that should be
moved to the maven core to avoid that this code is duplicated in many
places?

regards,

Wim

Maven snapshot dependencies and recompilation

2005-12-20 Thread Peter De Velder

Situation: project B depends on project A (snapshot jar)

When building B for the first time, it correctly downloads the latest
A-version-SNAPSHOT.jar
Building B a second time without making any changes to the B source files
(and without a maven clean first), correctly sees the B doesn't need to
be recompiled.

My question : If a new version of the A-version-SNAPSHOT.jar is detected in
the remote repository and downloaded during the build B process, it doesn't
seem to recompile B.  As a consequence possible compilation errors of B due
to a changed interface in A, remain  invisible until a full
recompile (= clean + compile) of B takes place, or the B-source files have
been changed  !  This is something we like to avoid, especially in our
continuous integration (cruisecontrol) process, without having to do a clean
first.

Did I miss something or do we need to code this behaviour ourselves
e.gusing the ant-dependset explicitly in our own plugin or
maven.xml, cleaning the target directory when A-version-SNAPSHOT.jar is more
recent then target/B-version-SNAPSHOT.jar  ?
(Yes, we are  still using maven 1.0.2.   Is maven 2 behaving differently ? )

Thanks in advance,
Peter

Problems using ejb3

2005-12-20 Thread Edwin van der Elst

Hi,

I compiled the latest Maven from SVN and did the same for the maven-ejb3-plugin 
and maven-ear-plugin.
I am trying to get the ejb.jar in the ear file with the .ejb3 extension for 
deployment under JBoss. The ear file will probably be ok, once I get Maven to 
store my jar file with the corerct extension in the repository.

Some fragments from my pom.xml:

...
packagingejb3/packaging
...


plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb3-plugin/artifactId
version2.1-SNAPSHOT/version
executions
execution
phasepackage/phase
goals
goalejb3/goal
/goals
/execution
/executions


I now get a NPE during the build:
[INFO] [ejb3:ejb3]
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Error assembling EJB3

[INFO] 

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
..
..
Caused by: java.lang.NullPointerException
at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136)
... 18 more


Has anyone got a clue how to get this working? 
Being used to Ant, this seems such a trivial problem (In Ant: just name the jar 
'myejbs.ejb3' and be done with it).

Any help appreciated,

Edwin van der Elst

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

Re: [m2] release plugin problems - solved

2005-12-20 Thread Jurgen Lust

OK, I finally succeeded in making the release plugin work with SVN:

1. beta-3 does not work, you need beta-4-SNAPSHOT, otherwise you get
the error
Cannot copy path '.' into its own child '../tags/0.3'

2. Using svn and ssh from cygwin does not work, you get errors about the path of the basedir

3. Install the windows command line subversion 1.2.3, and add the bin directory to your path

4. Install Putty

5. edit %APPDATA%/Subversion/config and add the following in the [tunnels] section:
ssh="c:/program files/putty/plink.exe" -T

6. You should use Pageant to keep your ssh private key in memory.

After all this, The release:prepare goal finally completed successfully.

Kind regards,

Jurgen

Jurgen Lust schreef:

Hello,

Has anyone found a solution to this problem yet? I'm getting the same
error message using subversion 1.2.3 on cygwin with maven 2.0.1 and
release plugin version 2.0 beta 3.

Jurgen
I tried running the command 'svn cp .
../tags/0.4' and that gave the same error message. I'm
starting to think it may be a problem with svn. I ran 'svn cp
/full/path/to/trunk ../tags/0.4' and that worked without a
problem.
Rich

Richard Wallace wrote:

I
tried setting the tagBase via the -DtagBase option, but that didn't seem
to make a difference.
Arik Kfir wrote:

Hi,

Make sure you define the following in your pom.xml:
build
plugins
plugin
artifactIdmaven-release-plugin/artifactId
configuration
tagBasehttp://www.mysvnserver.com/myproject/tags/tagBase
/configuration
/plugin
/plugins
/build

This tells the release plugin where to place tagged sources (see svn
docs for info how tagging in svn).

cheers,
Arik.

On 11/15/05, Richard Wallace [EMAIL PROTECTED] wrote:

I'm
trying to use the release plugin to do a release of my project. I'm

using subversion 1.2.3 and everything proceeds to the point where m2

tries to do the svn copy but svn kicks back the following
error message:
svn: Cannot copy path '.' into its own child '../tags/0.3'

I was able to do releases with the m1 plugin, but this is
the first time
I've tried with m2. Any ideas?

Thanks,
Rich

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

--
Among flowers, the cherry blossom.
Among men, me.

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

Re: Problems using ejb3

2005-12-20 Thread Tim Kettler


Hi,

see http://jira.codehaus.org/browse/MNG-1690

-Tim

Edwin van der Elst schrieb:

Hi,

I compiled the latest Maven from SVN and did the same for the maven-ejb3-plugin 
and maven-ear-plugin.
I am trying to get the ejb.jar in the ear file with the .ejb3 extension for 
deployment under JBoss. The ear file will probably be ok, once I get Maven to 
store my jar file with the corerct extension in the repository.

Some fragments from my pom.xml:

...
packagingejb3/packaging
...


plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb3-plugin/artifactId
version2.1-SNAPSHOT/version
executions
execution
phasepackage/phase
goals
goalejb3/goal
/goals
/execution
/executions


I now get a NPE during the build:
[INFO] [ejb3:ejb3]
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Error assembling EJB3

[INFO] 

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
..
..
Caused by: java.lang.NullPointerException
at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136)
... 18 more


Has anyone got a clue how to get this working? 
Being used to Ant, this seems such a trivial problem (In Ant: just name the jar 'myejbs.ejb3' and be done with it).


Any help appreciated,

Edwin van der Elst

-
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]

[m2] xmlbeans plugin

2005-12-20 Thread Paolo Donà

Hi guys,
I'm trying to use the xmlbeans plugin but it fails saying that
xmlbeans-jsr173-api-2.0-dev.jar is not available.
I cannot find it on ibiblio.. can someone help my finding this?

Regards,
Paolo

**

Re: [m2] xmlbeans plugin

2005-12-20 Thread Nathan Sowatskey

Yes, I just had to copy one into my repository and rename it. I  
couldn't fine one anywhere else.


Regards

Nathan

Nathan Sowatskey - Technical Leader, NMTG CTO Engineering -  
+34-638-083-675, +34-91-201-2139 - AIM NathanCisco - [EMAIL PROTECTED]


On 20 Dec 2005, at 16:33, Paolo Donà wrote:


Hi guys,
I'm trying to use the xmlbeans plugin but it fails saying that
xmlbeans-jsr173-api-2.0-dev.jar is not available.
I cannot find it on ibiblio.. can someone help my finding this?

Regards,
Paolo

**


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

Re: problem with maven2 on OS X and JDK 1.5

2005-12-20 Thread Conrad O'Dea


Hi Carlos,

thanks for the information.  Configuring the compiler to fork works  
for me.


On 20 Dec 2005, at 14:49, Carlos Sanchez wrote:


The problem is at this line
c = cl.loadClass( com.sun.tools.javac.Main );
in
http://svn.plexus.codehaus.org/trunk/plexus-components/plexus- 
compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/ 
codehaus/plexus/compiler/javac/JavacCompiler.java?rev=2727view=auto


I don't know why this should be a problem as nobody else is reporting
problems under mac and some of the developers are using it. Maybe you
have different security options in your JDK?


The security options are the default and are pretty much identical as  
the 1.4 JDK that I have installed and that works fine.  Odd.  Perhaps  
none of the developers are using JDK 1.5 and maven 2 but I guess  
that's unlikely.


If I get the time I'll dig a little more.


thanks
Conrad


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

[m2] - WAR file generation

Hi,

I am building a J2EE project. My WAR file includes all the dependency jars
(including the common jars and ejb jars) in the WEB-INF/lib directory. This
creates additional copies of jar files within the EAR file and the size of
the WAR file gets huge. Is there a way to avoid bundling of the dependencies
within the WAR file? The scope attribute value (provided/runtime) doesnt
seem to have an effect on this behaviour.

Thanks and regards,
Karthik.

Re: Problems using ejb3

2005-12-20 Thread Tim Kettler


Hi,

see http://jira.codehaus.org/browse/MNG-1690

-Tim

Edwin van der Elst schrieb:

Hi,

I compiled the latest Maven from SVN and did the same for the maven-ejb3-plugin 
and maven-ear-plugin.
I am trying to get the ejb.jar in the ear file with the .ejb3 extension for 
deployment under JBoss. The ear file will probably be ok, once I get Maven to 
store my jar file with the corerct extension in the repository.

Some fragments from my pom.xml:

...
packagingejb3/packaging
...


plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb3-plugin/artifactId
version2.1-SNAPSHOT/version
executions
execution
phasepackage/phase
goals
goalejb3/goal
/goals
/execution
/executions


I now get a NPE during the build:
[INFO] [ejb3:ejb3]
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Error assembling EJB3

[INFO] 

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
..
..
Caused by: java.lang.NullPointerException
at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136)
... 18 more


Has anyone got a clue how to get this working? 
Being used to Ant, this seems such a trivial problem (In Ant: just name the jar 'myejbs.ejb3' and be done with it).


Any help appreciated,

Edwin van der Elst

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





--
Freundliche Grüße / Best Regards

Tim Kettler
_
Lieterweg 24
58285 Gevelsberg
Tel.: +49 2332 149814
Fax: +49 2332 149814
e-mail: [EMAIL PROTECTED]
Internet :  http://www.tk-ai.de


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

RE: Problems using ejb3

2005-12-20 Thread Edwin van der Elst

Thank you very much,
it works after aplying the patch.

Edwin

-Oorspronkelijk bericht-
Van: Tim Kettler [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 20 december 2005 16:23
Aan: Maven Users List
Onderwerp: Re: Problems using ejb3


Hi,

see http://jira.codehaus.org/browse/MNG-1690

-Tim

Edwin van der Elst schrieb:
 Hi,
 
 I compiled the latest Maven from SVN and did the same for the 
 maven-ejb3-plugin and maven-ear-plugin.
 I am trying to get the ejb.jar in the ear file with the .ejb3 extension for 
 deployment under JBoss. The ear file will probably be ok, once I get Maven to 
 store my jar file with the corerct extension in the repository.
 
 Some fragments from my pom.xml:
 
 ...
   packagingejb3/packaging
 ...
 
 
 plugins
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-ejb3-plugin/artifactId
   version2.1-SNAPSHOT/version
   executions
   execution
   phasepackage/phase
   goals
   goalejb3/goal
   /goals
   /execution
   /executions
 
 
 I now get a NPE during the build:
 [INFO] [ejb3:ejb3]
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Error assembling EJB3
 
 [INFO] 
 
 [INFO] Trace
 org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
 ..
 ..
 Caused by: java.lang.NullPointerException
 at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136)
 ... 18 more
 
 
 Has anyone got a clue how to get this working? 
 Being used to Ant, this seems such a trivial problem (In Ant: just name the 
 jar 'myejbs.ejb3' and be done with it).
 
 Any help appreciated,
 
 Edwin van der Elst
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 


-- 
Freundliche Grüße / Best Regards

Tim Kettler
_
Lieterweg 24
58285 Gevelsberg
Tel.: +49 2332 149814
Fax: +49 2332 149814
e-mail: [EMAIL PROTECTED]
Internet :  http://www.tk-ai.de


-
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: Maven and Continuous Integration

2005-12-20 Thread David Jackman

I never had the time to set up two separate build projects to make it faster, 
so each build deletes the entire source tree, gets the code from source 
control, does a multiproject:deploy, then a multiproject:site, then finally a 
site:deploy.  I know this is very inefficient (all the tests wind up getting 
run 3 times), but that's the way it is now.

..David..

-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 19, 2005 9:25 PM
To: 'Maven Users List'
Subject: RE: Maven and Continuous Integration

David,

What is the scope of each CI build, compile and test, site too, etc?

I have CI only on compile and test for all our product codelines, and 1 nightly 
for site generation as the site gen takes hours to run.

Just wondering if you have an trick to share :-D


-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 12:40 PM
To: Maven Users List
Subject: RE: Maven and Continuous Integration

In our department, we use Maven (v1.0 currently) to do continuous integration 
builds and a few will use it to do builds on their own machines but most do 
their own builds using an IDE and use Maven only to update dependencies as 
necessary.

We don't do separate nightly builds--only continuous builds.

I'm not sure what you mean by source references in your IDE.  If you're 
referring to where the IDE gets the source for a particular project, then this 
comes out of source control like any other project (i.e. Maven isn't affecting 
the source at all).  If you're referring to where the IDE finds a particular 
project's binary dependencies, then the IDE refers to these in the user's local 
repository (we use the IDEA and Eclipse plugins to generate the projects, and 
they create the references automatically).  If you're referring to where the 
IDE finds the source code for a particular project's binary dependencies, then 
we haven't really addressed this problem.  Users can access the source code for 
other projects within our department from source control.  With Maven 2 we were 
hoping to make source references like this work more automatically (there's 
ways to make it work better in Maven 1, but we haven't wanted to invest much 
time into making M1 work better while trying to move to M2).

Hope this helps,
..David..
 

-Original Message-
From: Michael Böckling [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 10:54 AM
To: Maven Users List
Subject: Maven and Continuous Integration

Hi folks,

this question might be a little OT, but just a little:
I'd like to know how you handle your continuous integration builds and the 
source references in your IDE.
Suppose you got nightly builds as well as CI builds, to which sources would you 
link the project to you are currently working on? The snapshot build from last 
night? The latest result of the CI build? Not use Maven
(repository) at all for that because you check integration whithin your IDE, 
using checked-out sources of the dependen projects?
I'm really curious to know how others solved that...

Good night,
Michael

--
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; 
http://www.giniality.com/



-
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]


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

RE: Maven and Continuous Integration

2005-12-20 Thread David Jackman

This is close to what I wanted to be able to do in M2 as well.

One thing to be clear about is what source code a developer may be using 
directly from source control (as opposed to a source distribution of a 
dependency artifact).  We have taken our product and divided it up into many 
smaller (and independent) projects which produce individual artifacts (and we 
haven't looked back).  This means a developer will only get the code out of 
source control for the (relatively few--usually one or two) projects he is 
actually working on.  The other source code would be for dependencies to those 
projects (and provided as source distributions alongside the artifacts for 
those dependencies).

Right now, for the most part, we just make do without the source distribution 
for dependencies.  For the rare instance that we need to debug into a 
dependency (which really doesn't happen much), the developer will usually get 
the code for that project from source control and build it locally (to be sure 
the code matches the jar he's using).  There are times that this can't work, 
though (e.g. when the dependency isn't for the latest version of the artifact).

For a developer working primarily in an IDE, if their project has snapshot 
dependencies, it's up to the developer to make sure he's got the latest 
versions in his local repository.  He can do this by occasionally building the 
project using maven (instead of the IDE).  One problem here is that a normal 
build will download the latest dependencies, but not the source distributions 
for those dependencies.  If all he wants are the latest versions and their 
source distributions, I'm hoping there's a goal in the eclipse/idea plugin that 
can facilitate this.  If not, then I'll write a plugin that does this.  Once 
there's a single plugin that gets them up to date, then the source distribution 
will always be in sync with the version of the dependency in the developer's 
local repository.  It would be even better if the Eclipse plugin for Maven 2 
could automatically check the dependencies and verify that the source 
distribution is up to date (and download it if it isn't).  I don't know if it 
will do that sort of thing or not (I haven't taken the time to research what's 
possible and straightforward when working with the IDEs yet).

..David..


-Original Message-
From: Michael Böckling [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 20, 2005 2:18 AM
To: Maven Users List
Subject: Re: Maven and Continuous Integration

Hi David,

thank you for your answer.
Sorry for being unclear, but I guess all the issues you brought up are 
important.
I'm really new to the CI concept, and I'm not sure if there is only one way to 
do it, so thats why I'm asking.

I just thought that if developers are expected to write their code in such a 
way that it will work in conjunction with the latest sources of all dependent 
projects, it would also be a necessity to have the latest sources (and 
binaries, maybe) also in their IDE, and not only  in a snapshot repo or 
Continuum or so.

So once there is a new build (nightly or even CI), binary and source references 
in Eclipse (for instance) should point to that newest version, or am I wrong? 
But wouldn't it be a bit unpractical for all developers to update projects in 
their IDE several times a day? I was hoping that we could use some Maven 
automatism.
I know source jars can be released with Maven, but I don't know if these 
sources can be attached to the binary dependencies using the M2 plugin (but I 
know the Eclipse userlibraries concept allows that, so maybe a Mojo that 
automatically creates those as a temporary workaround would be feasible).

What I envision is this:
- CI builds upon commits to SVN (released to a special CI snapshot repo), 
whithout any ballast because of performance issues (no site generation etc.).
- Nightly builds with all bells and whistles

When the dev starts working in the morning, all binary and source references of 
dependent projects in his IDE automatically point to the result of the last 
nightly build, which would reside in some snapshot repository. I guess it would 
take two different snapshot repos, one for CI and one for nightly builds, but 
I'm not sure if it is enough for the devs to just use the nightly builds as 
references or also the CI results.

Does that make any sense to you? I'm still uncertain how to adress this whole 
nightly/ci thing properly...
Thank you very much,

Michael

David,

What is the scope of each CI build, compile and test, site too, etc?

I have CI only on compile and test for all our product codelines, and 1 
nightly for site generation as the site gen takes hours to run.

Just wondering if you have an trick to share :-D


-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 12:40 PM
To: Maven Users List
Subject: RE: Maven and Continuous Integration

In our department, we use Maven (v1.0 currently) to do

RE: [m2] production ready? any experience?

2005-12-20 Thread David Jackman

I didn't attend JavaPolis (sounds like I missed out), but I have been
working for a few weeks to move our Maven 1 projects to Maven 2.  At
this point I would agree that Maven 2 is not quite ready for prime time.
It's getting closer, though.  I've found problems (both in the core and
in plugins) and tried to create patches when I file the jira issues, so
hopefully Maven 2 will do what we need it to before too much longer.  I
doubt it will really be ready before 2.1, though I'm not sure what the
timeframe of that release is (hopefully it's enough time for me to
finish my migration and file fixes for the problems I encountered along
the way).

..David..


-Original Message-
From: Rik Bosman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 20, 2005 1:15 AM
To: Maven Users List
Subject: [m2] production ready? any experience?

Hi Everyone,

Some colleages of mine visited javapolis. Vincent Massol told there that
maven2 is not production ready (if I rephrase it correctly).

- When will it be production ready? 2.02? 2.1?
- Are there any stories from developers using maven2 in production?

I'm a maven2 fan, and I hope to adopt it for our company soon.

Regards,

Rik Bosman

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

Re: Problems using ejb3

2005-12-20 Thread Arik Kfir

Hi Edwin,

Note that there's also a required patch for the maven-par-plugin (I
think its MNG-1691, but not sure) - should you need to make a 'par'
module as well.

On 12/20/05, Edwin van der Elst [EMAIL PROTECTED] wrote:
 Thank you very much,
 it works after aplying the patch.

 Edwin

 -Oorspronkelijk bericht-
 Van: Tim Kettler [mailto:[EMAIL PROTECTED]
 Verzonden: dinsdag 20 december 2005 16:23
 Aan: Maven Users List
 Onderwerp: Re: Problems using ejb3


 Hi,

 see http://jira.codehaus.org/browse/MNG-1690

 -Tim

 Edwin van der Elst schrieb:
  Hi,
 
  I compiled the latest Maven from SVN and did the same for the 
  maven-ejb3-plugin and maven-ear-plugin.
  I am trying to get the ejb.jar in the ear file with the .ejb3 extension for 
  deployment under JBoss. The ear file will probably be ok, once I get Maven 
  to store my jar file with the corerct extension in the repository.
 
  Some fragments from my pom.xml:
 
  ...
packagingejb3/packaging
  ...
 
 
  plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb3-plugin/artifactId
version2.1-SNAPSHOT/version
executions
execution
phasepackage/phase
goals
goalejb3/goal
/goals
/execution
/executions
  
 
  I now get a NPE during the build:
  [INFO] [ejb3:ejb3]
  [INFO] 
  
  [ERROR] BUILD ERROR
  [INFO] 
  
  [INFO] Error assembling EJB3
 
  [INFO] 
  
  [INFO] Trace
  org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling 
  EJB3
  at 
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
  at 
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
  ..
  ..
  Caused by: java.lang.NullPointerException
  at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136)
  ... 18 more
 
 
  Has anyone got a clue how to get this working?
  Being used to Ant, this seems such a trivial problem (In Ant: just name the 
  jar 'myejbs.ejb3' and be done with it).
 
  Any help appreciated,
 
  Edwin van der Elst
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Freundliche Grüße / Best Regards

 Tim Kettler
 _
 Lieterweg 24
 58285 Gevelsberg
 Tel.: +49 2332 149814
 Fax: +49 2332 149814
 e-mail: [EMAIL PROTECTED]
 Internet :  http://www.tk-ai.de


 -
 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]




--
Regards,
_
Arik Kfir[EMAIL PROTECTED]

Re: Maven and Continuous Integration

2005-12-20 Thread Lee Meador

I suspect the best way to think of it is that some of the company libraries
are treated like third party libraries and other company libraries are
treated differently because they are being worked on.

You don't update compiled or source for, say, Spring that often. When you do
update its a big enough deal to change version numbers for your build that
you can download the source if you need it for debugging. Lots of times
the changes between two of these versions are minor enough that using the
old source with the new binary works good enough and you don't really care.

Treat some of your in-house libraries the same way. Update rarely because it
takes time to do it.

The rest of the in-house libraries are those you are working on and will
need to be updated from source control often enough.

Usually the pain of debugging a problem when using old source is enough to
encourage people to update that source. Or the pain of breaking the build
(or the tests) by checking in code that doesn't work because you didn't
update your source will do it.

Someone finds there is a key issue and tells everyone else to update. It
just sort of works if you keep the lines of communication open.

--
-- Lee Meador
Sent from gmail. My real email address is [EMAIL PROTECTED]

Re: null pointer exception in ejbdoclet

2005-12-20 Thread Karthik V

I'm going mad with this error. Not able to proceed at all. Can somebody help me 
out? I'll give more details if needed.



Karthik V [EMAIL PROTECTED] wrote:  Please help me understand this stack 
trace .. got this while trying to run ejbdoclet on a bunch of files... 
 
Deploy TEMPLATE URL: jar:file:C:\Documents and 
Settings\karthikv\.maven\repository\xdoclet\jars\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-deploy_wsdd.xdt
Undeploy TEMPLATE URL: jar:file:C:\Documents and 
Settings\karthikv\.maven\repository\xdoclet\jars\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-undeploy_wsdd.xdt
java.lang.NullPointerException
at java.util.StringTokenizer.(StringTokenizer.java:182)
at 
xdoclet.tagshandler.PackageTagsHandler.getPackageNameFor(PackageTagsHandler.java:60)
at 
xdoclet.tagshandler.PackageTagsHandler.getPackageNameFor(PackageTagsHandler.java:35)
at 
xdoclet.tagshandler.PackageTagsHandler.packageNameAsPathFor(PackageTagsHandler.java:114)
at 
xdoclet.GenerationManager.isGenerationNeeded(GenerationManager.java:345)
at 
xdoclet.GenerationManager.isGenerationNeeded(GenerationManager.java:182)
at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:615)
at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597)
at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198)
at 
xdoclet.modules.ejb.dd.EjbDotXmlSubTask.execute(EjbDotXmlSubTask.java:217)
at xdoclet.XDocletMain.start(XDocletMain.java:48)
at xdoclet.DocletTask.start(DocletTask.java:464)
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at 
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.PreGoalTag$1.firePreGoal(PreGoalTag.java:87)
at com.werken.werkz.Goal.firePreGoalCallbacks(Goal.java:691)
at com.werken.werkz.Goal.fire(Goal.java:616)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:488)
at org.apache.maven.cli.App.main(App.java:1239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
 
BUILD FAILED
File.. C:\Documents and 
Settings\karthikv\.maven\cache\maven-xdoclet-plugin-1.2.3\plugin.jelly
Element... ejbdoclet
Line.. 27
Column 20
Unexpected error 


Thanks
Karthik.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: IDE build and debugging

2005-12-20 Thread Sebastien Arbogast


  Well actually, it was the JBoss
  developer's notebook I had in my hands but it could have been yours ;o)

 Lol


Don't be sad Vincent ;o) I already have you book for quite some time :
http://www.mail-archive.com/users@maven.apache.org/msg22132.html

M2 is brilliant at generating and updating IntelliJ multi-module projects
 (caveat w.r.t. jdk5 setting) but I've not managed to get any of the Maven
 GUI pluggins working with Idea v5.02. I'd be very grateful if someone can
 provide step by step instructions or perhaps links to pluggins.  The maven
 pluggin  http://www.intellij.org/twiki/bin/view/Main/MavenPlugin


The problem is that no current IDE (at least not that I know of) really
integrates Maven as much as it would really be useful. The integration seems
to be forced to stop at the running level. Let's hope that the new modular
architecture of M2 will make IDE editors think of integrating it with their
debugger. All the power of Maven automation and dependency management, with
the developer-friendly interface of an advanced debugger : that would be
great !

At least it reassures me : it's not that I did something wrong :oP

--
Sébastien Arbogast

Blog : http://www.sebastien-arbogast.com
The Epseelon Project : http://www.epseelon.org
Projet Phénix : http://phenix.netbios.fr
Lens : http://www.squidoo.com/useful-computers/

Re: Problems using ejb3

2005-12-20 Thread Stephane Nicoll

Guys,

I just applied the patch for par and ejb3 plugins in the sandbox.

Cheers,
Stéphane

On 12/20/05, Arik Kfir [EMAIL PROTECTED] wrote:

 Hi Edwin,

 Note that there's also a required patch for the maven-par-plugin (I
 think its MNG-1691, but not sure) - should you need to make a 'par'
 module as well.

 On 12/20/05, Edwin van der Elst [EMAIL PROTECTED] wrote:
  Thank you very much,
  it works after aplying the patch.
 
  Edwin
 
  -Oorspronkelijk bericht-
  Van: Tim Kettler [mailto:[EMAIL PROTECTED]
  Verzonden: dinsdag 20 december 2005 16:23
  Aan: Maven Users List
  Onderwerp: Re: Problems using ejb3
 
 
  Hi,
 
  see http://jira.codehaus.org/browse/MNG-1690
 
  -Tim
 
  Edwin van der Elst schrieb:
   Hi,
  
   I compiled the latest Maven from SVN and did the same for the
 maven-ejb3-plugin and maven-ear-plugin.
   I am trying to get the ejb.jar in the ear file with the .ejb3
 extension for deployment under JBoss. The ear file will probably be ok, once
 I get Maven to store my jar file with the corerct extension in the
 repository.
  
   Some fragments from my pom.xml:
  
   ...
 packagingejb3/packaging
   ...
  
  
   plugins
 plugin
 groupIdorg.apache.maven.plugins
 /groupId
  
 artifactIdmaven-ejb3-plugin/artifactId
 version2.1-SNAPSHOT/version
 executions
 execution
 phasepackage/phase
 goals
  
 goalejb3/goal
 /goals
 /execution
 /executions
   
  
   I now get a NPE during the build:
   [INFO] [ejb3:ejb3]
   [INFO]
 
   [ERROR] BUILD ERROR
   [INFO]
 
   [INFO] Error assembling EJB3
  
   [INFO]
 
   [INFO] Trace
   org.apache.maven.lifecycle.LifecycleExecutionException: Error
 assembling EJB3
   at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:555)
   at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
 (DefaultLifecycleExecutor.java:472)
   ..
   ..
   Caused by: java.lang.NullPointerException
   at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java
 :136)
   ... 18 more
  
  
   Has anyone got a clue how to get this working?
   Being used to Ant, this seems such a trivial problem (In Ant: just
 name the jar 'myejbs.ejb3' and be done with it).
  
   Any help appreciated,
  
   Edwin van der Elst
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  Freundliche Grüße / Best Regards
 
  Tim Kettler
  _
  Lieterweg 24
  58285 Gevelsberg
  Tel.: +49 2332 149814
  Fax: +49 2332 149814
  e-mail: [EMAIL PROTECTED]
  Internet :  http://www.tk-ai.de
 
 
  -
  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]
 
 


 --
 Regards,
 _
 Arik Kfir[EMAIL PROTECTED]




--
.::You're welcome ::.

[m2] Pushing out new plugin versions?

2005-12-20 Thread Matthew Beermann

I notice that the site and clover plugins haven't had a new version pushed 
out, even to the snapshot repository, for one to three (!) months, 
respectively. Which is a pity, because there's a lot of nice fixes I'd like to 
pick up without having to compile from source.
   
  This page 
(http://maven.apache.org/guides/development/guide-testing-development-plugins.html)
 warns that not all plugins are being automatically published to the snapshot 
site - yet, at least. Any progress being made on this? Any chance the two 
plugins I mentioned could get a new snapshot version kicked out if I ask real 
nicely? Pretty please? :)
   
  --Matthew Beermann

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: [m2] - WAR file generation

2005-12-20 Thread Stephane Nicoll

Could you please describe a bit more your situation. You have an WAR inside
an EAR and librarires got duplicated?

Maybe show your poms.

s/

On 12/20/05, Karthik Manimaran [EMAIL PROTECTED] wrote:

 Hi,

 I am building a J2EE project. My WAR file includes all the dependency jars
 (including the common jars and ejb jars) in the WEB-INF/lib directory.
 This
 creates additional copies of jar files within the EAR file and the size of
 the WAR file gets huge. Is there a way to avoid bundling of the
 dependencies
 within the WAR file? The scope attribute value (provided/runtime) doesnt
 seem to have an effect on this behaviour.

 Thanks and regards,
 Karthik.




--
.::You're welcome ::.

RE: [m2] Pushing out new plugin versions?

2005-12-20 Thread Vincent Massol

Yeah we really need to release the clover plugin.

However there are issues that have been raised to it and that are not fixed.
An important one is related to multimodule projects where it seems it's
failing. I think at least this issue  needs to be fixed before the release.
I started working again on the plugin yesterday but I'm hitting some issues
with integration tests for plugins...

I agree that it would be nice if continuum was publishing snaphost versions
of all plugins.

-Vincent

 -Original Message-
 From: Matthew Beermann [mailto:[EMAIL PROTECTED]
 Sent: mardi 20 décembre 2005 17:41
 To: users@maven.apache.org
 Subject: [m2] Pushing out new plugin versions?
 
 I notice that the site and clover plugins haven't had a new version
 pushed out, even to the snapshot repository, for one to three (!) months,
 respectively. Which is a pity, because there's a lot of nice fixes I'd
 like to pick up without having to compile from source.
 
   This page (http://maven.apache.org/guides/development/guide-testing-
 development-plugins.html) warns that not all plugins are being
 automatically published to the snapshot site - yet, at least. Any progress
 being made on this? Any chance the two plugins I mentioned could get a new
 snapshot version kicked out if I ask real nicely? Pretty please? :)
 
   --Matthew Beermann
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around
 http://mail.yahoo.com


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

overridding the output directory

2005-12-20 Thread Christopher Cobb

I would occasionally like to put my jar file in a different directory.  Is
there something along the lines of:

 

mvn -Dproject.build.outputDirectory=/tmp/outputDirectory package

 

that will allow me to do a one-off build without having to modify
configuration files?  The line above does not do anything different than the
standard build.

 

 

 

 




-
Attention:
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized
to state them to be the views of any such entity. The information
contained in this message and or attachments is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material.  If you received this in error, please
contact the sender and delete the material from any system and destroy
any copies.

maven-eclipse-plugin dealing with generated resources

2005-12-20 Thread scowx

Hi

I am running a maven2 project and I am making use of the eclipse:eclipse goal to
set up my eclipse eenvironment nicely for development.

I have a small problem, I hope somebody can help me with it.

A Project  Clean action in Eclipse clears out the target/classes directory
and recreates all of the class files.

In my case this causes difficulties because I am compiling a .dll to this
directory during the build so that I can find it on the classpath at runtime
(for JNI).  Whenever I do a Project  Clean, the dll gets wiped out and I have
to run the build again.  This is frustrating because I always have to do Refresh
and a Project  Clean in eclipse after every build.

The only workaround I can think of is to compile the .dll to one of the src
folders in the project and let eclipse copy it across for me when I choose to
do a Project  Clean in eclipse.

This isn't ideal because it is actually a generated file and not a source file.

Any idea's?

Ideally, the eclipse plugin would allow you to add specific classpath entries to
your .classpath file.

e.g. I would add target/generated-sources/lib

Is this already possible?

regards

Stephen





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

two problems

2005-12-20 Thread Michael Fiedler

Hi,

 

   I am getting two problems.  One is that when mail notifiers are being
entered, they are being persisted with all options on even though I
explicitly unchecked the success option.  Even when I edit the entry and
re-uncheck them, they eventually become checked again.

 

   My second issue is that I am getting an exception when I edit the
mail notifier entry, but not every time.  When I do get an exception, it
is similar to this:

jvm 1| 2005-12-20 13:03:34,253 [Thread-1] WARN  SQL
- Object with id 1069 not found !

jvm 1| 2005-12-20 13:03:34,503 [Thread-1] WARN  SQL
- Object with id 1069 not found !

jvm 1| 2005-12-20 13:03:34,643 [Thread-1] ERROR BuildController
- Error while building project.

jvm 1| javax.jdo.JDODataStoreException: Put request failed : INSERT
INTO PROJECTNOTIFIER_CONFIGURATION (STRING_VAL,ID_OID,STRING_KEY) VALUES
(?,?,?)

jvm 1|  at
org.jpox.store.rdbms.scostore.NormalMapStore.put(NormalMapStore.java:467
)

jvm 1|  at org.jpox.sco.Map.put(Map.java:709)

jvm 1|  at
org.jpox.sco.SCOUtils.updateMapWithMapKeysValues(SCOUtils.java:626)

jvm 1|  at org.jpox.sco.Map.attachCopy(Map.java:376)

jvm 1|  at
org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.ja
va:107)

jvm 1|  at
org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.jav
a:2394)

jvm 1|  at
org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideField
(ProjectNotifier.java)

jvm 1|  at
org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideField
s(ProjectNotifier.java)

jvm 1|  at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732
)

jvm 1|  at
org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java
:3518)

jvm 1|  at
org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446)

jvm 1|  at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1644)

jvm 1|  at org.jpox.sco.List.attachCopy(List.java:326)

jvm 1|  at
org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.ja
va:107)

jvm 1|  at
org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.jav
a:2394)

jvm 1|  at
org.apache.maven.continuum.model.project.Project.jdoProvideField(Project
.java)

jvm 1|  at
org.apache.maven.continuum.model.project.Project.jdoProvideFields(Projec
t.java)

jvm 1|  at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732
)

jvm 1|  at
org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java
:3518)

jvm 1|  at
org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446)

jvm 1|  at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1644)

jvm 1|  at org.jpox.sco.List.attachCopy(List.java:326)

jvm 1|  at
org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.ja
va:107)

jvm 1|  at
org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.jav
a:2394)

jvm 1|  at
org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideField(Pr
ojectGroup.java)

jvm 1|  at
org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideFields(P
rojectGroup.java)

jvm 1|  at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732
)

jvm 1|  at
org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java
:3518)

jvm 1|  at
org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446)

jvm 1|  at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1644)

jvm 1|  at
org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.ja
va:120)

jvm 1|  at
org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.jav
a:2394)

jvm 1|  at
org.apache.maven.continuum.model.project.Project.jdoProvideField(Project
.java)

jvm 1|  at
org.apache.maven.continuum.model.project.Project.jdoProvideFields(Projec
t.java)

jvm 1|  at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732
)

jvm 1|  at
org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java
:3518)

jvm 1|  at
org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446)

jvm 1|  at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1644)

jvm 1|  at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1660)

jvm 1|  at
org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti
nuumStore.java:679)

jvm 1|  at
org.apache.maven.continuum.store.JdoContinuumStore.updateProject(JdoCont
inuumStore.java:841)

jvm 1|  at
org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.exe

Re: [m2] stop password being requested on site deploy

2005-12-20 Thread dan tran

I would suggest to use dsa or rsa

http://www.jdmz.net/ssh/

-D


On 12/20/05, Patrick O'shea [EMAIL PROTECTED] wrote:

 Hi,

 I want to deploy a site without any user interaction, currently it asks me
 for a password
 even though it is in the settings.xml

 In my pom.xml i have defined:
 distributionManagement
site
  idscmsite/id
  namedeploy site/name
  urlscp://cassiusgroup-3.internal.org/var/www/projname//url

/site
 /distributionManagement

 And in the settings.xml i have defined:
server
  idscmsite/id
  usernamepo82266/username
  passwordpo82266/password
/server


 Is there something else, i'm missing ?
 thanks
 Patrick

How to override the maven central repository completely

2005-12-20 Thread Venkat Muthusamy

Hi,



I like to maintain our own internal repository instead of
http://repo1.maven.org/maven2 due to some restrictions.


I created internal server and downloaded necessary plugins and directory
structures same as http://repo1.maven.org/maven2. I updated the pom file
repository setting as follows. But it is still goes to look in to
http://repo1.maven.org/maven2.


  repository

   idcentral/id

   namecentral/name

   urlhttp://PHX51682:8080/mvn//url

   layoutdefault/layout

  /repository



I like to know how to override the central repository.



Thanks in advance
Venkat M

Re: How to configure default plugins (exclude test)

2005-12-20 Thread Benedict Heal

I had the same problem, until I was helped to exclude some tests from 
being compiled, until on this list (5/12/05) Nik Gonzalez pointed out

the use of testIncludes and testExcludes.
The script below works fine for me.

Benedict

---
...

plugin!-- what to compile --
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-compiler-plugin/artifactId
   configuration
  source1.5/source
  target1.5/target
 
  includes

 include**/model/*.java/include
  /includes
 
  excludes

 exclude**/*Action.java/exclude
  /excludes
 
  testIncludes

 testIncludeou/erd/**/model/**/*Test.java/testInclude
  /testIncludes
 
  testExcludes

 testExclude**/*MutabilityTest.java/testExclude
  /testExcludes
 
   /configuration

/plugin

cameron101 wrote:


I too wish to exclude specific TestCase's but have tried the above
suggestion


reporting
   plugins
   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdsurefire-report-maven-plugin/artifactId
   configuration
   excludes
   exclude**/*TransactionalTestCase.java/exclude
   /excludes
   /configuration
   /plugin
   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdjxr-maven-plugin/artifactId
   /plugin
   /plugins
   /reporting

/project
including updating the pluggins and the exclude does not appear to work !!
Any help greatly appreciated :-)




On 29/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 


Emmanuel

Thanks for helping me.

Stephen


Quoting [EMAIL PROTECTED]:

   


Hi

Ok, I have figured this out now.  The key fact is that I had my
 


configuration
   


for my plugin in my POM was defined inside an executions tag.

Basically for anyone else who needs to know this,

You can configure the default behaviour of plugins in your build by
adding a tag
for the plugin to the build section of your pom.

However you must NOT put the configuration section inside an
 


Executions
   


section or it will think that you are asking it to run the plugin again.

your plugin should look like this:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
 excludes
 exclude**/*Test.java/exclude
 /excludes
/configuration
/plugin


and NOT like this

plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-surefire-plugin/artifactId
  executions
execution
 phasetest/phase
 configuration
   excludes
 exclude**/*ABCTest.java/exclude
   /excludes
 /configuration
 goals
goaltest/goal
 /goals
/execution
  /executions
/plugin


Quoting [EMAIL PROTECTED]:

 


Hi Emmanuel

Thanks, I have tried that now but it has made no difference.

Below is my trace and below that is my POM.  If you look at the
trace you will
see that the tests are getting run twice and the second time, the
   


exclusions
   


are being applied.

I do appreciate your help.

regards

Stephen


C:\workspaces\bdplus\bdp-coremvn -U install
[INFO] Scanning for projects...
[INFO]

   



   


[INFO] Building Core
[INFO]task-segment: [install]
[INFO]

   



   


[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for
updates from snapshots
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:checking for
updates from snapshots
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:checking for
updates from snapshots
[WARNING] repository metadata for: 'artifact
org.apache.maven.plugins:maven-surefire-plugin' could not be retrieved
   


from
   


repository: snapshots due to an error: Error transferring file
[INFO] Repository 'snapshots' will be blacklisted
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking
for updates
from central
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking
   


for
   


updates from central
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [bdp-buildcreateenv:create {execution: default}]
[INFO] Starting
[INFO] Creating 4

Re: [m2] - WAR file generation

Oops . Didn't know attachements arent accepted. Details below:

Folder structure
remo
- applications
   -DotCom
--modules
  --ContentManager
   --DotComCommon
   --PrivacyWeb

PrivacyWeb POM:
project
   modelVersion4.0.0/modelVersion
   groupIdremo.gtvx2/groupId
   artifactIdPrivacyWeb/artifactId
   packagingwar/packaging
   version1.0/version
   namePrivacy Web/name

   dependencies
  dependency
 groupIdremo.gtvx2/groupId
 artifactIdDotComCommon/artifactId
 version1.0/version
 scopeprovided/scope
  /dependency
  dependency
 groupIdremo.gtvx2/groupId
 artifactIdContentManager/artifactId
 version1.0/version
 scopeprovided/scope
  /dependency


dependency
  groupIdjavax.servlet/groupId
  artifactIdservlet-api/artifactId
  version2.3/version
  scopeprovided/scope
/dependency
dependency
  groupIdjavax.mail/groupId
  artifactIdmail/artifactId
  version1.3.3/version
  scopeprovided/scope
/dependency
dependency
  groupIdjavax.activation/groupId
  artifactIdactivation/artifactId
  version1.0.2/version
  scopeprovided/scope
/dependency

 dependency
  groupIdcommons-beanutils/groupId
  artifactIdcommons-beanutils/artifactId
  version1.7.0/version
  scopeprovided/scope
/dependency
dependency
  groupIdlog4j/groupId
  artifactIdlog4j/artifactId
  version1.2.8/version
  scopeprovided/scope
/dependency
dependency
  groupIdstruts/groupId
  artifactIdstruts/artifactId
  version1.0/version
  scopeprovided/scope
/dependency
dependency
  groupIdcommons-collections/groupId
  artifactIdcommons-collections/artifactId
  version2.0/version
  scopeprovided/scope
/dependency
dependency
  groupIdcommons-logging/groupId
  artifactIdcommons-logging/artifactId
  version1.0.2/version
  scopeprovided/scope
/dependency
dependency
  groupIdcommons-lang/groupId
  artifactIdcommons-lang/artifactId
  version1.0/version
  scopeprovided/scope
/dependency
dependency
  groupIdcommons-fileupload/groupId
  artifactIdcommons-fileupload/artifactId
  version1.0/version
  scopeprovided/scope
/dependency
dependency
  groupIdcommons-digester/groupId
  artifactIdcommons-digester/artifactId
  version1.0/version
  scopeprovided/scope
/dependency

   /dependencies

   build
  plugins
 plugin
artifactIdmaven-war-plugin/artifactId
version2.0-beta-2/version
configuration
   archive
  manifest
 addClasspathtrue/addClasspath
  /manifest
   /archive
/configuration
 /plugin
  /plugins
   /build

/project

DotCom POM:
project
   modelVersion4.0.0/modelVersion
   groupIdremo.gtvx2/groupId
   artifactIdDotComEar/artifactId
   packagingear/packaging
   version1.0/version
   nameDot Com EAR/name
   dependencies
  dependency
 groupIdremo.gtvx2/groupId
 artifactIdContentManager/artifactId
 version1.0/version
 typeejb/type
  /dependency
  dependency
 groupIdremo.gtvx2/groupId
 artifactIdPrivacyWeb/artifactId
 version1.0/version
 typewar/type
  /dependency
  dependency
 groupIdremo.gtvx2/groupId
 artifactIdDotComCommon/artifactId
 version1.0/version
  /dependency
   /dependencies
   build
  plugins
 plugin
artifactIdmaven-ear-plugin/artifactId
version2.0/version
configuration
   archive
  manifest
 addClasspathtrue/addClasspath
  /manifest
   /archive
/configuration
 /plugin
  /plugins
   /build
/project

remo POM:
project
   modelVersion4.0.0/modelVersion
   groupIdremo/groupId
   version1.0/version
   artifactIdgtvx/artifactId
   packagingpom/packaging
   namegtvx .com Build/name
   modules
  moduleapplications/module
  modulemodules/module
   /modules
   build
  plugins
 plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
 /plugin
  /plugins
   /build
/project

DotComCommon POM:

project
   modelVersion4.0.0/modelVersion
   groupIdremo.gtvx2/groupId
   artifactIdDotComCommon/artifactId
   packagingjar/packaging
   version1.0/version
   nameDot Com Common Components/name
   dependencies

dependency
  groupIdremo.gtvx2/groupId
  artifactIdContentManager/artifactId
  version1.0/version
/dependency
dependency
  groupIdjavax.servlet/groupId
  artifactIdservlet-api/artifactId

m2 site-deploy Help

2005-12-20 Thread raghurajan . x . gurunathanv

Hi All, 

I'm getting the following error when i execute mvn -e site-deploy  my 
scp works fine from command line any ideas?

The authenticity of host 'Tiger' can't be established.
RSA key fingerprint is 73:47:7e:3d:5d:3c:33:71:07:f2:7d:01:43:06:fd:33.
Are you sure you want to continue connecting? (yes/no): yes
scp://Tiger - Session: Opened
Executing command: mkdir -p /.
scp://10.72.87.103 - Session: Disconnecting
scp://10.72.87.103 - Session: Disconnected
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Error uploading site

Embedded error: Error performing commands for file transfer
bash: /c/Program Files/AdminTools/Resource Kit/mkdir: No such file or 
directory
[INFO] 

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading 
site
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:30
1)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading 
site
at 
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:142)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
... 16 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error 
performing commands for file transfer
at 
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.putDirectory(AbstractSshWagon.java:498)
at 
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:134)
... 18 more
Caused by: org.apache.maven.wagon.CommandExecutionException: bash: 
/c/Program Files/AdminTools/Resource Kit/mkdir: No such f
ile or directory
at 
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.executeCommand(AbstractSshWagon.java:287)
at 
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.putDirectory(AbstractSshWagon.java:494)
... 19 more
[INFO] 

[INFO] Total time: 14 seconds
[INFO] Finished at: Tue Dec 20 13:41:19 CST 2005
[INFO] Final Memory: 6M/11M
[INFO] 







Thanks,
=
Raghurajan Gurunathan 
Desk : 713.427.5305 
=

how to find dependencies programatically from within Mojo

2005-12-20 Thread Helenek, Kris

Hi, 

 

I'm currently writing a plugin to replace the WsCompile ant task that
comes with the JWSDP.  

 

To do this i hunted down the class that gets called when you run
wscompile from the command line, and make 

an array of String objects and pass them into the main() method. 

 

Everything was going great until it complains about not finding classes
on the classpath.  The WsCompile class takes a

parameter for classpath, so i had to pass it in manually.  I did that by
concatenating the relevant artifacts from the

project.getArtifacts() map and adding the result as an argument. 

 

The problem is that I also need to pass in the artifacts that are the
dependencies of the *plugin*, as described in the plugin's pom.xml. 

 

I cannot seem to find any reference to these artifacts anywhere.  Is
there any possible way for me to get these at 

runtime? There doesn't seem to be anything in the project object that
points to them.  Perhaps another object that I 

can bind to a property of the Mojo?  I also cannot find any javadocs so
i've been working alot with trial and error and reflection logging. 

 

Thanks for any help. 

 

_kris h

Re: [m2] - WAR file generation

2005-12-20 Thread Stephane Nicoll

Well this does not sound a mistake to me.  What are you actually expecting
from Maven?

s/

On 12/20/05, Karthik Manimaran [EMAIL PROTECTED] wrote:

 Oops . Didn't know attachements arent accepted. Details below:

 Folder structure
 remo
 - applications
-DotCom
 --modules
   --ContentManager
--DotComCommon
--PrivacyWeb

 PrivacyWeb POM:
 project
modelVersion4.0.0/modelVersion
groupIdremo.gtvx2/groupId
artifactIdPrivacyWeb/artifactId
packagingwar/packaging
version1.0/version
namePrivacy Web/name

dependencies
   dependency
  groupIdremo.gtvx2/groupId
  artifactIdDotComCommon/artifactId
  version1.0/version
  scopeprovided/scope
   /dependency
   dependency
  groupIdremo.gtvx2/groupId
  artifactIdContentManager/artifactId
  version1.0/version
  scopeprovided/scope
   /dependency


 dependency
   groupIdjavax.servlet/groupId
   artifactIdservlet-api/artifactId
   version2.3/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdjavax.mail/groupId
   artifactIdmail/artifactId
   version1.3.3/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdjavax.activation/groupId
   artifactIdactivation/artifactId
   version1.0.2/version
   scopeprovided/scope
 /dependency

  dependency
   groupIdcommons-beanutils/groupId
   artifactIdcommons-beanutils/artifactId
   version1.7.0/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdlog4j/groupId
   artifactIdlog4j/artifactId
   version1.2.8/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdstruts/groupId
   artifactIdstruts/artifactId
   version1.0/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdcommons-collections/groupId
   artifactIdcommons-collections/artifactId
   version2.0/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdcommons-logging/groupId
   artifactIdcommons-logging/artifactId
   version1.0.2/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdcommons-lang/groupId
   artifactIdcommons-lang/artifactId
   version1.0/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdcommons-fileupload/groupId
   artifactIdcommons-fileupload/artifactId
   version1.0/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdcommons-digester/groupId
   artifactIdcommons-digester/artifactId
   version1.0/version
   scopeprovided/scope
 /dependency

/dependencies

build
   plugins
  plugin
 artifactIdmaven-war-plugin/artifactId
 version2.0-beta-2/version
 configuration
archive
   manifest
  addClasspathtrue/addClasspath
   /manifest
/archive
 /configuration
  /plugin
   /plugins
/build

 /project

 DotCom POM:
 project
modelVersion4.0.0/modelVersion
groupIdremo.gtvx2/groupId
artifactIdDotComEar/artifactId
packagingear/packaging
version1.0/version
nameDot Com EAR/name
dependencies
   dependency
  groupIdremo.gtvx2/groupId
  artifactIdContentManager/artifactId
  version1.0/version
  typeejb/type
   /dependency
   dependency
  groupIdremo.gtvx2/groupId
  artifactIdPrivacyWeb/artifactId
  version1.0/version
  typewar/type
   /dependency
   dependency
  groupIdremo.gtvx2/groupId
  artifactIdDotComCommon/artifactId
  version1.0/version
   /dependency
/dependencies
build
   plugins
  plugin
 artifactIdmaven-ear-plugin/artifactId
 version2.0/version
 configuration
archive
   manifest
  addClasspathtrue/addClasspath
   /manifest
/archive
 /configuration
  /plugin
   /plugins
/build
 /project

 remo POM:
 project
modelVersion4.0.0/modelVersion
groupIdremo/groupId
version1.0/version
artifactIdgtvx/artifactId
packagingpom/packaging
namegtvx .com Build/name
modules
   moduleapplications/module
   modulemodules/module
/modules
build
   plugins
  plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
  /plugin
   /plugins
/build
 /project

 DotComCommon POM:

 project
modelVersion4.0.0/modelVersion
groupIdremo.gtvx2/groupId
artifactIdDotComCommon/artifactId

Re: [m2] - WAR file generation

The jar file DotComCommon-1.0.jar is duplicated in the EAR file.

1. It is present in the EAR file as a separate jar at the root.
2. It is also present inside PrivacyWeb.war file (inside WEB-INF/lib folder)

The same duplication occurs for all other jars used by PrivacyWeb (runtime,
commons-*, ContentManager etc)

Now the EAR is twice as big as what it is supposed to be. I do not need
Maven to include all the depencies required for the WAR file inside lib
directory as it is already available as separate jars in the EAR file.

Thanks and regards,
Karthik.



On 12/20/05, Stephane Nicoll [EMAIL PROTECTED] wrote:

 Well this does not sound a mistake to me.  What are you actually expecting
 from Maven?

 s/

 On 12/20/05, Karthik Manimaran [EMAIL PROTECTED] wrote:
 
  Oops . Didn't know attachements arent accepted. Details below:
 
  Folder structure
  remo
  - applications
 -DotCom
  --modules
--ContentManager
 --DotComCommon
 --PrivacyWeb
 
  PrivacyWeb POM:
  project
 modelVersion4.0.0/modelVersion
 groupIdremo.gtvx2/groupId
 artifactIdPrivacyWeb/artifactId
 packagingwar/packaging
 version1.0/version
 namePrivacy Web/name
 
 dependencies
dependency
   groupIdremo.gtvx2/groupId
   artifactIdDotComCommon/artifactId
   version1.0/version
   scopeprovided/scope
/dependency
dependency
   groupIdremo.gtvx2/groupId
   artifactIdContentManager/artifactId
   version1.0/version
   scopeprovided/scope
/dependency
 
 
  dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.3/version
scopeprovided/scope
  /dependency
  dependency
groupIdjavax.mail/groupId
artifactIdmail/artifactId
version1.3.3/version
scopeprovided/scope
  /dependency
  dependency
groupIdjavax.activation/groupId
artifactIdactivation/artifactId
version1.0.2/version
scopeprovided/scope
  /dependency
 
   dependency
groupIdcommons-beanutils/groupId
artifactIdcommons-beanutils/artifactId
version1.7.0/version
scopeprovided/scope
  /dependency
  dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.8/version
scopeprovided/scope
  /dependency
  dependency
groupIdstruts/groupId
artifactIdstruts/artifactId
version1.0/version
scopeprovided/scope
  /dependency
  dependency
groupIdcommons-collections/groupId
artifactIdcommons-collections/artifactId
version2.0/version
scopeprovided/scope
  /dependency
  dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.0.2/version
scopeprovided/scope
  /dependency
  dependency
groupIdcommons-lang/groupId
artifactIdcommons-lang/artifactId
version1.0/version
scopeprovided/scope
  /dependency
  dependency
groupIdcommons-fileupload/groupId
artifactIdcommons-fileupload/artifactId
version1.0/version
scopeprovided/scope
  /dependency
  dependency
groupIdcommons-digester/groupId
artifactIdcommons-digester/artifactId
version1.0/version
scopeprovided/scope
  /dependency
 
 /dependencies
 
 build
plugins
   plugin
  artifactIdmaven-war-plugin/artifactId
  version2.0-beta-2/version
  configuration
 archive
manifest
   addClasspathtrue/addClasspath
/manifest
 /archive
  /configuration
   /plugin
/plugins
 /build
 
  /project
 
  DotCom POM:
  project
 modelVersion4.0.0/modelVersion
 groupIdremo.gtvx2/groupId
 artifactIdDotComEar/artifactId
 packagingear/packaging
 version1.0/version
 nameDot Com EAR/name
 dependencies
dependency
   groupIdremo.gtvx2/groupId
   artifactIdContentManager/artifactId
   version1.0/version
   typeejb/type
/dependency
dependency
   groupIdremo.gtvx2/groupId
   artifactIdPrivacyWeb/artifactId
   version1.0/version
   typewar/type
/dependency
dependency
   groupIdremo.gtvx2/groupId
   artifactIdDotComCommon/artifactId
   version1.0/version
/dependency
 /dependencies
 build
plugins
   plugin
  artifactIdmaven-ear-plugin/artifactId
  version2.0/version
  configuration
 archive
manifest

Re: groupId springframework vs. org.springframework

2005-12-20 Thread Matt Raible

Unfortunately, this change seems to have hosed everything.  Using
springframework/spring was working *beautifully* before, and now
neither works.

required artifacts missing:
  javax.mail:mail:jar:1.3.2
  javax.transaction:jta:jar:1.0.1B
  javax.resource:connector:jar:1.0
  javax.activation:activation:jar:1.0.2

Is it possible to revert things back to what they were?

Matt

On 12/19/05, Carlos Sanchez [EMAIL PROTECTED] wrote:
 Hi,

 I have the poms for org.springframework 1.2.6 ready and will upload them soon.
 The messages you get on springframwork are just warnings because the
 poms don't yet exist, but should work the same as the
 org.springframework ones that have minimalistic poms.

 Regards

 On 12/19/05, Matt Raible [EMAIL PROTECTED] wrote:
  I like to follow best practices, and it appears that you (the Maven
  Team) would prefer we use org.springframework for Spring's groupId,
  rather than springframework.
 
  If I change my pom.xml setting to use org.springframework for the
  groupId (for spring and spring-mock (v 1.2.6)), I get the following
  warning:
 
  [INFO] [resources:resources]
  [INFO] Using default encoding to copy filtered resources.
  Downloading: 
  http://repo1.maven.org/maven2/org/springframework/spring-mock/1.2.6
  /spring-mock-1.2.6.pom
  [WARNING] Unable to get resource from repository central 
  (http://repo1.maven.org
  /maven2)
  Downloading: 
  http://repo1.maven.org/maven2/org/springframework/spring/1.2.6/spri
  ng-1.2.6.pom
  [WARNING] Unable to get resource from repository central 
  (http://repo1.maven.org
  /maven2)
 
  If I change my groupId to be springframework, I don't get any
  warnings.  It seems like org.springframework is not as up-to-date as
  springframework, especially since its directories are missing *.pom
  files.
 
  Any ideas?
 
  Thanks,
 
  Matt
 
  -
  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: groupId springframework vs. org.springframework

Isn't this just because those artifacts are not in your local
repository and must be installed manually?

They were possibly installed under the other groupIds previously.

- Brett

On 12/21/05, Matt Raible [EMAIL PROTECTED] wrote:
 Unfortunately, this change seems to have hosed everything.  Using
 springframework/spring was working *beautifully* before, and now
 neither works.

 required artifacts missing:
   javax.mail:mail:jar:1.3.2
   javax.transaction:jta:jar:1.0.1B
   javax.resource:connector:jar:1.0
   javax.activation:activation:jar:1.0.2

 Is it possible to revert things back to what they were?

 Matt

 On 12/19/05, Carlos Sanchez [EMAIL PROTECTED] wrote:
  Hi,
 
  I have the poms for org.springframework 1.2.6 ready and will upload them 
  soon.
  The messages you get on springframwork are just warnings because the
  poms don't yet exist, but should work the same as the
  org.springframework ones that have minimalistic poms.
 
  Regards
 
  On 12/19/05, Matt Raible [EMAIL PROTECTED] wrote:
   I like to follow best practices, and it appears that you (the Maven
   Team) would prefer we use org.springframework for Spring's groupId,
   rather than springframework.
  
   If I change my pom.xml setting to use org.springframework for the
   groupId (for spring and spring-mock (v 1.2.6)), I get the following
   warning:
  
   [INFO] [resources:resources]
   [INFO] Using default encoding to copy filtered resources.
   Downloading: 
   http://repo1.maven.org/maven2/org/springframework/spring-mock/1.2.6
   /spring-mock-1.2.6.pom
   [WARNING] Unable to get resource from repository central 
   (http://repo1.maven.org
   /maven2)
   Downloading: 
   http://repo1.maven.org/maven2/org/springframework/spring/1.2.6/spri
   ng-1.2.6.pom
   [WARNING] Unable to get resource from repository central 
   (http://repo1.maven.org
   /maven2)
  
   If I change my groupId to be springframework, I don't get any
   warnings.  It seems like org.springframework is not as up-to-date as
   springframework, especially since its directories are missing *.pom
   files.
  
   Any ideas?
  
   Thanks,
  
   Matt
  
   -
   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] stop password being requested on site deploy

That said, it should owrk, and I have tested it sucessfully in the
past. You might require a more recent version, but other than that
there aren't enough details in the OP to determine the problem.

- Brett

On 12/21/05, dan tran [EMAIL PROTECTED] wrote:
 I would suggest to use dsa or rsa

 http://www.jdmz.net/ssh/

 -D


 On 12/20/05, Patrick O'shea [EMAIL PROTECTED] wrote:
 
  Hi,
 
  I want to deploy a site without any user interaction, currently it asks me
  for a password
  even though it is in the settings.xml
 
  In my pom.xml i have defined:
  distributionManagement
 site
   idscmsite/id
   namedeploy site/name
   urlscp://cassiusgroup-3.internal.org/var/www/projname//url
 
 /site
  /distributionManagement
 
  And in the settings.xml i have defined:
 server
   idscmsite/id
   usernamepo82266/username
   passwordpo82266/password
 /server
 
 
  Is there something else, i'm missing ?
  thanks
  Patrick
 
 
 



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

Re: [m2] Pushing out new plugin versions?

I think it would be a really good idea to push out a dev version of
the clover plugin, hence I've done it.

The site plugin is getting some work done right now to improve the
multimodule support and a release forthcoming in the near future.
Snapshot published, regardless.

- Brett

On 12/21/05, Vincent Massol [EMAIL PROTECTED] wrote:
 Yeah we really need to release the clover plugin.

 However there are issues that have been raised to it and that are not fixed.
 An important one is related to multimodule projects where it seems it's
 failing. I think at least this issue  needs to be fixed before the release.
 I started working again on the plugin yesterday but I'm hitting some issues
 with integration tests for plugins...

 I agree that it would be nice if continuum was publishing snaphost versions
 of all plugins.

 -Vincent

  -Original Message-
  From: Matthew Beermann [mailto:[EMAIL PROTECTED]
  Sent: mardi 20 décembre 2005 17:41
  To: users@maven.apache.org
  Subject: [m2] Pushing out new plugin versions?
 
  I notice that the site and clover plugins haven't had a new version
  pushed out, even to the snapshot repository, for one to three (!) months,
  respectively. Which is a pity, because there's a lot of nice fixes I'd
  like to pick up without having to compile from source.
 
This page (http://maven.apache.org/guides/development/guide-testing-
  development-plugins.html) warns that not all plugins are being
  automatically published to the snapshot site - yet, at least. Any progress
  being made on this? Any chance the two plugins I mentioned could get a new
  snapshot version kicked out if I ask real nicely? Pretty please? :)
 
--Matthew Beermann
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam protection around
  http://mail.yahoo.com


 -
 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: my first m2 plugin

Can someone provide a reason why this is needed? I can't think of a
single reason to use it off the top of my head...

- Brett

On 12/21/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
 
   What if I only want the direct deps instead of the transitive ones?
  
   ${project.dependencies} - but these are just model dependencies, not
   artifacts. If you need the artifacts, take the union of this and
   ${project.artifacts}.


 I think that many plugins use this functionality, so maybe that should be
 moved to the maven core to avoid that this code is duplicated in many
 places?

 regards,

 Wim



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

Re: groupId springframework vs. org.springframework

I've been reminded that this is exactly the problem - these are
supposed to be optional.

Sorry!

- Brett

On 12/21/05, Brett Porter [EMAIL PROTECTED] wrote:
 Isn't this just because those artifacts are not in your local
 repository and must be installed manually?

 They were possibly installed under the other groupIds previously.

 - Brett

 On 12/21/05, Matt Raible [EMAIL PROTECTED] wrote:
  Unfortunately, this change seems to have hosed everything.  Using
  springframework/spring was working *beautifully* before, and now
  neither works.
 
  required artifacts missing:
javax.mail:mail:jar:1.3.2
javax.transaction:jta:jar:1.0.1B
javax.resource:connector:jar:1.0
javax.activation:activation:jar:1.0.2
 
  Is it possible to revert things back to what they were?
 
  Matt
 
  On 12/19/05, Carlos Sanchez [EMAIL PROTECTED] wrote:
   Hi,
  
   I have the poms for org.springframework 1.2.6 ready and will upload them 
   soon.
   The messages you get on springframwork are just warnings because the
   poms don't yet exist, but should work the same as the
   org.springframework ones that have minimalistic poms.
  
   Regards
  
   On 12/19/05, Matt Raible [EMAIL PROTECTED] wrote:
I like to follow best practices, and it appears that you (the Maven
Team) would prefer we use org.springframework for Spring's groupId,
rather than springframework.
   
If I change my pom.xml setting to use org.springframework for the
groupId (for spring and spring-mock (v 1.2.6)), I get the following
warning:
   
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading: 
http://repo1.maven.org/maven2/org/springframework/spring-mock/1.2.6
/spring-mock-1.2.6.pom
[WARNING] Unable to get resource from repository central 
(http://repo1.maven.org
/maven2)
Downloading: 
http://repo1.maven.org/maven2/org/springframework/spring/1.2.6/spri
ng-1.2.6.pom
[WARNING] Unable to get resource from repository central 
(http://repo1.maven.org
/maven2)
   
If I change my groupId to be springframework, I don't get any
warnings.  It seems like org.springframework is not as up-to-date as
springframework, especially since its directories are missing *.pom
files.
   
Any ideas?
   
Thanks,
   
Matt
   
-
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: groupId springframework vs. org.springframework

2005-12-20 Thread Carlos Sanchez

Hi,

Probably it worked because there were no dependencies in them, now
that they are maven tries to download them.

I'm putting them as optional in the spring pom (almost everything
should be), but you'll miss a lot of the transitive dependency
features. That's why I really encourage the use of the smaller jars.

Regards

On 12/20/05, Matt Raible [EMAIL PROTECTED] wrote:
 Unfortunately, this change seems to have hosed everything.  Using
 springframework/spring was working *beautifully* before, and now
 neither works.

 required artifacts missing:
   javax.mail:mail:jar:1.3.2
   javax.transaction:jta:jar:1.0.1B
   javax.resource:connector:jar:1.0
   javax.activation:activation:jar:1.0.2

 Is it possible to revert things back to what they were?

 Matt

 On 12/19/05, Carlos Sanchez [EMAIL PROTECTED] wrote:
  Hi,
 
  I have the poms for org.springframework 1.2.6 ready and will upload them 
  soon.
  The messages you get on springframwork are just warnings because the
  poms don't yet exist, but should work the same as the
  org.springframework ones that have minimalistic poms.
 
  Regards
 
  On 12/19/05, Matt Raible [EMAIL PROTECTED] wrote:
   I like to follow best practices, and it appears that you (the Maven
   Team) would prefer we use org.springframework for Spring's groupId,
   rather than springframework.
  
   If I change my pom.xml setting to use org.springframework for the
   groupId (for spring and spring-mock (v 1.2.6)), I get the following
   warning:
  
   [INFO] [resources:resources]
   [INFO] Using default encoding to copy filtered resources.
   Downloading: 
   http://repo1.maven.org/maven2/org/springframework/spring-mock/1.2.6
   /spring-mock-1.2.6.pom
   [WARNING] Unable to get resource from repository central 
   (http://repo1.maven.org
   /maven2)
   Downloading: 
   http://repo1.maven.org/maven2/org/springframework/spring/1.2.6/spri
   ng-1.2.6.pom
   [WARNING] Unable to get resource from repository central 
   (http://repo1.maven.org
   /maven2)
  
   If I change my groupId to be springframework, I don't get any
   warnings.  It seems like org.springframework is not as up-to-date as
   springframework, especially since its directories are missing *.pom
   files.
  
   Any ideas?
  
   Thanks,
  
   Matt
  
   -
   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: my first m2 plugin

2005-12-20 Thread Torsten Curdt


Ok ...got the plugin working!

Here is the output for commons-jci :-D

[INFO] jakarta-commons-jci-1.0-SNAPSHOT.jar classes:44 dependencies: 
130 = 100.0% (58798-59159)
[INFO] commons-collections-3.1.jar classes:446 dependencies:518 =  
2.0% (559366-13901)
[INFO] core-3.1.0.jar classes:1255 dependencies:1469 = 31.0%  
(3555707-1116189)
[INFO] groovy-all-1.0-jsr-03.jar classes:915 dependencies:1220 =  
47.0% (1587529-746634)
[INFO] janino-2.3.7.jar classes:333 dependencies:414 = 64.0% (351643- 
227840)
[INFO] commons-logging-api-1.0.4.jar classes:13 dependencies:57 =  
45.0% (26202-11936)
[INFO] commons-io-1.1.jar classes:41 dependencies:98 = 48.0% (61562- 
29818)
[INFO] commons-lang-2.1.jar classes:110 dependencies:161 = 2.0%  
(207723-5730)


It requires to be called after jar:jar as it also
needs the final artifact that got built. So I've
added @phase package and expected a simple mvn
minijar:minijar would also build the jar.

What am I missing?

Ah... and the next question - where to put that plugin? :)

cheers
--
Torsten


PGP.sig
Description: This is a digitally signed message part

Re: my first m2 plugin

Why does it require the JAR?

Wher eit goes depends on what you want to do with it. We could vote to
have it as part of the Maven SVN, but that would require that the
existing committers are willing/able to work on it. For independantly
run plugins, or licensing that is open source but not ASF friendly we
offer easy hosting at mojo.codehaus.org.

- Brett

On 12/21/05, Torsten Curdt [EMAIL PROTECTED] wrote:
 Ok ...got the plugin working!

 Here is the output for commons-jci :-D

 [INFO] jakarta-commons-jci-1.0-SNAPSHOT.jar classes:44 dependencies:
 130 = 100.0% (58798-59159)
 [INFO] commons-collections-3.1.jar classes:446 dependencies:518 =
 2.0% (559366-13901)
 [INFO] core-3.1.0.jar classes:1255 dependencies:1469 = 31.0%
 (3555707-1116189)
 [INFO] groovy-all-1.0-jsr-03.jar classes:915 dependencies:1220 =
 47.0% (1587529-746634)
 [INFO] janino-2.3.7.jar classes:333 dependencies:414 = 64.0% (351643-
  227840)
 [INFO] commons-logging-api-1.0.4.jar classes:13 dependencies:57 =
 45.0% (26202-11936)
 [INFO] commons-io-1.1.jar classes:41 dependencies:98 = 48.0% (61562-
  29818)
 [INFO] commons-lang-2.1.jar classes:110 dependencies:161 = 2.0%
 (207723-5730)

 It requires to be called after jar:jar as it also
 needs the final artifact that got built. So I've
 added @phase package and expected a simple mvn
 minijar:minijar would also build the jar.

 What am I missing?

 Ah... and the next question - where to put that plugin? :)

 cheers
 --
 Torsten




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

Re: How do I build maven-artifact-ant-2.0.2-dep.jar?

Fixed the issues with repository IDs and built this:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/maven-artifact-ant/2.0.2-SNAPSHOT/maven-artifact-ant-2.0.2-20051220.231658-1-dep.jar
It successfully run through the test builds script.

This is not an officially endorsed release by the Maven PMC. Use at
your own risk :)

You shouldn't need to build maven-repository-tools (and it is not
included in the root POM - in fact it should be sandboxed). To build
shoul djust require mvn install at the root of the project, then a
follow up build maven-artifact-ant.

- Brett

On 12/21/05, Matt Raible [EMAIL PROTECTED] wrote:
 Hmmm, I'm able to build the JAR just fine by cd-ing into
 maven-artifact-ant and running mvn assembly:assembly.  However, when
 I copy it to my project, I get:

 BUILD FAILED
 C:\Source\equinox\build.xml:24: Unable to find component: 
 org.apache.maven.artif
 act.repository.layout.ArtifactRepositoryLayout[default]

 Total time: 0 seconds

 I've tried running mvn install on a number of other modules before
 running assembly, but I can't get maven-repository-tools to build.
 The error I'm getting is:

 [INFO] Failed to resolve artifact.

 required artifacts missing:
   org.apache.maven:maven-core:jar:2.0-SNAPSHOT
   org.apache.maven:maven-artifact:jar:2.0-SNAPSHOT
   plexus:plexus:jar:1.0-alpha-1
   org.apache.maven:maven-model:jar:2.0-SNAPSHOT
   xstream:xstream:jar:1.0-SNAPSHOT

 for the artifact:
   org.apache.maven:maven-repository-tools:jar:1.0-SNAPSHOT

 from the specified remote repositories:
   central (http://repo1.maven.org/maven2)

 Also, the Repository.java has a System.out.println that should
 probably be removed.

 Index: src/main/java/org/apache/maven/artifact/ant/Repository.java

 ===

 --- src/main/java/org/apache/maven/artifact/ant/Repository.java (revision
 357937)

 +++ src/main/java/org/apache/maven/artifact/ant/Repository.java (working copy)

 @@ -36,7 +36,6 @@


  public String getId()
  {
 -   System.out.println(Repository.getId() ==  + getInstance().id);
 if (getInstance().id == null)
 {
 throw new BuildException(id must be specified for a
 repository definition);

 Thanks,

 Matt

 On 12/19/05, Brett Porter [EMAIL PROTECTED] wrote:
  The 2.0.2-SNAPSHOT is here:
 
  https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
 
  Sorry, the dev docs haven't been updated to reflect this yet, it was a
  recent change.
 
  - Brett
 
  On 12/20/05, Matt Raible [EMAIL PROTECTED] wrote:
   I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for
   distribution with a project of mine (Equinox).  I could wait for the
   2.0.2 release, but I'd prefer to get the release done before COB
   tomorrow b/c that's when I go on vacation. ;-)
  
   I checked out maven from svn using:
  
   svn co https://svn.apache.org/repos/asf/maven/trunks maven
  
   I've been able to build everything, but versions are showing up with
   version 2.1-SNAPSHOT, and I can't figure out how to build the
   artifact-ant-*-dep.jar.  Am I checking out from the wrong repository?
  
   Thanks,
  
   Matt
  
   -
   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] - WAR file generation

2005-12-20 Thread Srepfler Srgjan


Karthik Manimaran wrote:


The jar file DotComCommon-1.0.jar is duplicated in the EAR file.

1. It is present in the EAR file as a separate jar at the root.
2. It is also present inside PrivacyWeb.war file (inside WEB-INF/lib folder)

The same duplication occurs for all other jars used by PrivacyWeb (runtime,
commons-*, ContentManager etc)

Now the EAR is twice as big as what it is supposed to be. I do not need
Maven to include all the depencies required for the WAR file inside lib
directory as it is already available as separate jars in the EAR file.

Thanks and regards,
Karthik.

For my team we allow the war module to have it's own libraries, only if 
the lib can be reused between it and the ejb module do we put it in ear, 
otherwise we keep them separated. That's our approach.

Cheers

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

Re: how to find dependencies programatically from within Mojo


Hi there,

Please refer to this page
http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIgetaplugin%27sdependenciesfromaMojo%3F

Hope this helps.

-allan

Helenek, Kris wrote:

Hi, 




I'm currently writing a plugin to replace the WsCompile ant task that
comes with the JWSDP.  




To do this i hunted down the class that gets called when you run
wscompile from the command line, and make 

an array of String objects and pass them into the main() method. 




Everything was going great until it complains about not finding classes
on the classpath.  The WsCompile class takes a

parameter for classpath, so i had to pass it in manually.  I did that by
concatenating the relevant artifacts from the

project.getArtifacts() map and adding the result as an argument. 




The problem is that I also need to pass in the artifacts that are the
dependencies of the *plugin*, as described in the plugin's pom.xml. 




I cannot seem to find any reference to these artifacts anywhere.  Is
there any possible way for me to get these at 


runtime? There doesn't seem to be anything in the project object that
points to them.  Perhaps another object that I 


can bind to a property of the Mojo?  I also cannot find any javadocs so
i've been working alot with trial and error and reflection logging. 




Thanks for any help. 




_kris h


 




No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005
 



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

How do you get a goal to call another goal effectively for reuse?

2005-12-20 Thread Lou Sacco

I have the following where I want to reuse two previous goals I wrote to do
a clean, update from repository, and then build (for our continuous
integration build) as follows:

goal name=buildCI /
attianGoal name=clean/
attainGoal name=updateSource/
attainGoal name=build /
/goal

The clean and updateSource work fine, but the build just says Starting
reactor... and then it ends prematurely before running the build and with
no errors, claiming Build Successful.

Looking at the goals below in more detail, do you see where I might be doing
something wrong?  Can you reuse forEach loops like I do below?  I'm using
Maven 1.0.2.

Please feel free to respond to me directly...thanks!

Lou

j:set var=portlet_projects value=AgileProject /

goal name=updateSource description=Updates source from PVCS call in
ANT script
ant:ant dir=./ antfile=build.xml target=update 
!-- if a label is provided, it will pull the code as such --
property name=label value=${scm.label}/
/ant:ant
/goal

 goal name=clean description=Clean up output files.
u:tokenize var=portlet_projects delim=,
${portlet_projects}
/u:tokenize
j:forEach items=${portlet_projects} var=portlet_project
indexVar=projectNumber
ant:delete dir=${basedir}/../${portlet_project}/build/
ant:delete dir=${basedir}/../${portlet_project}/dist/
ant:delete
dir=${basedir}/../${portlet_project}/WebContent/WEB-INF/lib/
ant:delete dir=${basedir}/../${portlet
_project}/WebContent/WEB-INF/classes/
/j:forEach
/goal

!--
build the projects
--
goal name=build 
u:tokenize var=portlet_projects delim=,
${portlet_projects}
/u:tokenize
j:forEach items=${portlet_projects} var=portlet_project
indexVar=projectNumber
m:reactor basedir=${basedir}/..
includes=${portlet_project}/project.xml
postProcessing=true
ignoreFailures=false goals=war /
/j:forEach
/goal

Re: How to override the maven central repository completely


Hi,

AFAIK, that is the right way on overriding central repository, try to 
check  if central repository is declared in your settings.xml?


-allan

Venkat Muthusamy wrote:


Hi,



I like to maintain our own internal repository instead of
http://repo1.maven.org/maven2 due to some restrictions.


I created internal server and downloaded necessary plugins and directory
structures same as http://repo1.maven.org/maven2. I updated the pom file
repository setting as follows. But it is still goes to look in to
http://repo1.maven.org/maven2.


 repository

  idcentral/id

  namecentral/name

  urlhttp://PHX51682:8080/mvn//url

  layoutdefault/layout

 /repository



I like to know how to override the central repository.



Thanks in advance
Venkat M

 




No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005
 



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

Re: [m2] - WAR file generation

My question here is - How to avoid jars that can be reused from being copied
to the lib directory and have it as a common file in the EAR.

Thanks and regards,
Karthik.


On 12/20/05, Srepfler Srgjan [EMAIL PROTECTED] wrote:

 Karthik Manimaran wrote:

 The jar file DotComCommon-1.0.jar is duplicated in the EAR file.
 
 1. It is present in the EAR file as a separate jar at the root.
 2. It is also present inside PrivacyWeb.war file (inside WEB-INF/lib
 folder)
 
 The same duplication occurs for all other jars used by PrivacyWeb
 (runtime,
 commons-*, ContentManager etc)
 
 Now the EAR is twice as big as what it is supposed to be. I do not need
 Maven to include all the depencies required for the WAR file inside lib
 directory as it is already available as separate jars in the EAR file.
 
 Thanks and regards,
 Karthik.
 
 For my team we allow the war module to have it's own libraries, only if
 the lib can be reused between it and the ejb module do we put it in ear,
 otherwise we keep them separated. That's our approach.
 Cheers

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

Re: How to override the maven central repository completely

2005-12-20 Thread clark . rao


Dear ,
   You can set you reposity id in setting.xml as central .
for example

profiles
profile
   iddevpprofile1/id

  activation
os
  familyunix/family
/os
  /activation
   properties
devep.websiteresource/appserver/devep.website
   /properties
  repositories
repository
  releases
   enabledtrue/enabled
   updatePolicyalways/updatePolicy
   checksumPolicyfail/checksumPolicy
   /releases
   snapshots
 enabledtrue/enabled
 updatePolicyalways/updatePolicy
 checksumPolicyfail/checksumPolicy
   /snapshots
   idmaven2repo1/id
   namedeveloper Resp/name
   urlhttp://repo1.maven.org/maven2//url
/repository
repository
  releases
   enabledtrue/enabled
   updatePolicynever/updatePolicy
   checksumPolicyfail/checksumPolicy
   /releases
   snapshots
 enabledtrue/enabled
 updatePolicynever/updatePolicy
 checksumPolicyfail/checksumPolicy
   /snapshots
   idlocalreposity/id
   namedeveloper local  Resp/name
  urlfile:///d:/m2localrepo//url
/repository
/repositories
   pluginRepositories
 pluginRepository
releases
  enabledtrue/enabled
  updatePolicynever/updatePolicy
  checksumPolicyfail/checksumPolicy
 /releases
idpluginLili/id
namemaven plugin/name
urlhttp://www.ibiblio.org/maven2//url
 /pluginRepository
  pluginRepository
releases
  enabledtrue/enabled
  updatePolicynever/updatePolicy
  checksumPolicyfail/checksumPolicy
 /releases
idlocalplugin/id
namelocal maven plugin/name
urlfile:///d:/m2localrepo//url
 /pluginRepository
/pluginRepositories
/profile

 profile
   iddevpprofile2/id

  activation
!--jdk1.5.0_04/jdk--
os
  familywindows/family
/os
  /activation
   properties
devep.websiteresource/appserver/devep.website
   /properties
  repositories
  repository
snapshots
  enabledfalse/enabled
/snapshots
idcentral/id
nameMaven Repository Switchboard/name

!--urlhttp://repo1.maven.org/maven2/url--

urlfile:///d:/m2localrepo//url
  /repository
  /repositories
pluginRepositories
  pluginRepository
releases
  updatePolicynever/updatePolicy
/releases
snapshots
  enabledfalse/enabled
/snapshots
idcentral/id
nameMaven Plugin Repository/name

   !-- urlhttp://repo1.maven.org/maven2/url--

urlfile:///d:/m2localrepo//url
  /pluginRepository
/pluginRepositories
/profile
  /profiles
  !-- activeProfiles
   | List of profiles that are active for all builds.
   |--
  activeProfiles
!--activeProfiledevpprofile1/activeProfile--
activeProfiledevpprofile2/activeProfile
!--activeProfileanotherAlwaysActiveProfile/activeProfile--
  /activeProfiles









thanks.
Tel: (020)36315358-328 Fax: (020)36315170



   
  Allan Ramirez 
   
  [EMAIL PROTECTED]To:   Maven Users List 
users@maven.apache.org 
  om  cc:  
   
   Subject:  Re: How to override 
the maven central repository completely   
  21/12/2005 09:26  
   
  Please respond to 
   
  Maven Users  
   
  List

Re: Use Maven in multiple Java SDKs

2005-12-20 Thread clark . rao


Dear



build
  plugins
  plugin
 groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-clean-plugin/artifactId
executions
  execution
  idclean/id
  phasevalidate/phase
   goals
goalclean/goal
  /goals
/execution
  /executions
   /plugin
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-compiler-plugin/artifactId
  configuration
source1.5/source
target1.5/target
skiptrue/skip
  /configuration

/plugin

plugins



thanks.
Tel: (020)36315358-328 Fax: (020)36315170




  De Silva, Sam   

  [EMAIL PROTECTED]To:   
'users@maven.apache.org' users@maven.apache.org   
  imited.com   cc: 

Subject:  Use Maven in multiple 
Java SDKs   
  20/12/2005 15:48  

  Please respond to 

  Maven Users List









Hi,

How do I perform the builds using Maven for two projects that are in two
different Java SDKs?



Sam



DISCLAIMER:
---
This Email may contain confidential and/or privileged information and is
intended
solely for the addressee(s) named. If you have received this information in
error, or
are advised that you have been posted this Email by accident, please notify
the
sender by return Email, do not redistribute it, delete the Email and keep
no copies.
--



__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__


Hactl..Moving forward with you.

Best Air Cargo Terminal - Asia 2005
Air Cargo Terminal of the Year 2002, 2003  2004

Web: http://www.hactl.com

DISCLAIMER :-
The information contained in this message, including any attachment, is
confidential and may also be privileged. The information is intended only
for the person or entity to which it is addressed. Any review,
re-transmission, copying, storage, distribution or other use or disclosure
of this information by persons or entities other than the intended
recipient is prohibited. If you are not the intended recipient, please
contact the sender immediately by return email and delete this message from
your system. Thank you.




__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

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

Re: overridding the output directory


Hi Christopher,

You may use another pom for it, let's say pom2.xml. Configure the pom 
with the


build
outputDirectorytmp/outputDirectory/outputDirectory
...
/build
and execute the mvn command mvn install -f pom2.xml

-allan

Christopher Cobb wrote:


I would occasionally like to put my jar file in a different directory.  Is
there something along the lines of:



mvn -Dproject.build.outputDirectory=/tmp/outputDirectory package



that will allow me to do a one-off build without having to modify
configuration files?  The line above does not do anything different than the
standard build.












-
Attention:
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized
to state them to be the views of any such entity. The information
contained in this message and or attachments is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material.  If you received this in error, please
contact the sender and delete the material from any system and destroy
any copies.

 




No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005
 



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

RE: Is it possible to make pom.xml simpler?

2005-12-20 Thread Michael Fiedler

I agree.  Thank you for your work and effort in the other areas - bug fixes and 
functionality.

Michael

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Saturday, December 17, 2005 11:52 AM
To: Maven Users List
Subject: RE: Is it possible to make pom.xml simpler?

 why not keep both camps happy? :) 

I would personally have them spend time on bugs fixes and new functional 
features than rewrite something that is a matter of taste.

-Original Message-
From: Arik Kfir [mailto:[EMAIL PROTECTED] 
Sent: Saturday, December 17, 2005 7:30 AM
To: Maven Users List
Subject: Re: Is it possible to make pom.xml simpler?

We all agree that it is really a matter of taste. That's precisely why Maven 
*should* support another theme.

I definitly agree that whether attributes are more readable or not is arguable 
(at best) - but why not keep both camps happy? :)  (if the costs are reasonable 
of course)

On 12/17/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
 A simple XSLT stylesheet would do the job there. You don't need maven 
 to support this format.

 On 12/17/05, Thomas Van de Velde [EMAIL PROTECTED] wrote:
  -1

  I agree with Brett.  This is a matter of taste.  My taste goes 
  towards the existing solution.  Writing everything on a single line 
  may even become less readable.  Have you ever tried to read an 
  Eclipse .classpath file?  You can hardly say that's more readeable.  
  I also think that mixing attributes with elements is in this case a bad 
  idea and would hurt overall consistency.

  On 12/17/05, Srepfler Srgjan [EMAIL PROTECTED] wrote:

   If your sole concern is the number of lines one must type, it is 
   certainly an option to have meta-pom.xml be in the format you 
   find most comfortable, then xslt it into the more verbose m2 pom.xml.

   This argument of attributes versus elements has existed since the 
   dawn of [xml] time. I am not trying to argue one way or the 
   other, but since
   m1 pom used the more verbose syntax, it eases the transition.

 My USD$0.02,
 -- /v\atthew

   -

   In fact people should develop a plugin that maps the simplified 
   and verbose schemas on the fly :) The advantage of using 
   namespaces is that you can create a your tag and map it to the 
   verbose tag from the official pom.
   That's the way I've seen the spring guys use it for now but the 
   advantage that I see is that in could be much easier to extend the 
   pom and it would be more type safe

   My 0.02MKD

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

 --
 Alexandre Poitras
 Québec, Canada

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

--
Regards,
_
Arik Kfir[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]

Javadoc exclude option in Maven-2

2005-12-20 Thread Venkat Muthusamy

Hi,



I like to know how to exclude packages while creating javadocs.



I included the following plugin in the pom with excludepackaegenames
option.

Looks like it is not excluding the packages. Is there something wrong in my
configuration or do I miss something.



plugin

  groupIdorg.apache.maven.plugins/groupId

artifactIdmaven-javadoc-plugin/artifactId

version2.0-beta-3/version

configuration

  excludepackagenames

   com.xyz.util.ddm.cache.xmlconfig.*

  /excludepackagenames

/configuration

  /plugin



I ran mvn javadoc:javadoc command



Thanks in advance,

Venkat M

Re: [m2] production ready? any experience?

2005-12-20 Thread Dirk Olmes

Rik Bosman wrote:
 Hi Everyone,

Hi Rik,

 Some colleages of mine visited javapolis. Vincent Massol told there that
 maven2 is not production ready (if I rephrase it correctly).
 
 - When will it be production ready? 2.02? 2.1?
 - Are there any stories from developers using maven2 in production?

I began to introduce maven2 just about four weeks ago. Right now we have
one webapp project and one multi-module library build with maven and so
far I've had no major problems. Migrating to maven2 from no structured
build system at all, m2 is a huge gain, especially the explicit
management of dependencies helps a lot.

The largest part is yet to come, though. We have a lot of J22E stuff to
be migrated to maven (coming from a custom ant build system) and I have
the vague feeling that there may come up some problems. This migration
is on a larger timeframe, though so maybe m2 will stabilize more until then.

-dirk


-- 
A: Maybe because some people are too annoyed by top-posting.
Q: Why do I not get an answer to my question(s)?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


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

Re: Javadoc exclude option in Maven-2