date:20060612

I have a set of modules and each module has its own independent 
repository. As an example top level module A contains modules B and C.


When I attempt to execute mvn scm:checkout on A it tries to checkout 
files for A (and I assume subsequently it would try to do the same for 
B and C). However A does not have any independent sources / files 
and is merely a container for B and C from a dependency perspective.


How can I configure the scm:checkout goal on module A 's  pom.xml so 
that it does not execute the goal for A but acts as a passthru command 
to both B and C.


Thanks

Dhananjay


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

RE: problem with adding findbugs plugin

2006-06-12 Thread janhavi.phirke

After pointing pluginsrepository to codehaus, I did mvn install and
then mvn findbugs:findbugs. But I am getting the following error:

mvn findbugs:findbugs
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'findbugs'.
[INFO]

-
---
[INFO] Building Maven Quick Start Archetype
[INFO]task-segment: [findbugs:findbugs]
[INFO]

-
---
[INFO] Preparing findbugs:findbugs
[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] [findbugs:findbugs]
[INFO]   No threshold provided, using default threshold.
Jaws uses plugin: \C:\Documents and
Settings\janhavi.phirke\.m2\repository\findb
ugs\coreplugin\0.9.3\coreplugin-0.9.3.jar
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] org/jaxen/JaxenException
[INFO]

[INFO] Trace
java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at
org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
at
org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)
at org.dom4j.tree.AbstractNode.valueOf(AbstractNode.java:189)
at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:125)
at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:88)
at
edu.umd.cs.findbugs.DetectorFactoryCollection.loadPlugins(DetectorFac
toryCollection.java:188)
at
edu.umd.cs.findbugs.DetectorFactoryCollection.init(DetectorFactoryC
ollection.java:52)
at
edu.umd.cs.findbugs.DetectorFactoryCollection.instance(DetectorFactor
yCollection.java:73)
at
edu.umd.cs.findbugs.config.UserPreferences.enableAllDetectors(UserPre
ferences.java:314)
at
org.codehaus.mojo.findbugs.FindBugsMojo.initialiseFindBugs(FindBugsMo
jo.java:312)
at
org.codehaus.mojo.findbugs.FindBugsMojo.executeReport(FindBugsMojo.ja
va:254)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven
Report.java:98)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenR
eport.java:73)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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)

Regards,
Janhavi Phirke
Accenture - Mumbai Delivery Center,
Direct Dial: +91-22-6600 7046
AIM: janhaviphirke
 


Disclaimer 
This e-mail and any attachments to it (in part or in whole the
Communication) are confidential, may constitute inside information and
are for the use only of the addressee. The Communication is the property
of Accenture and its affiliates and may contain copyright material or
intellectual property of Accenture and/or any of its related entities or
of third parties. If you are not the intended recipient of the
Communication or have received the Communication in error, please notify
the sender or Accenture immediately, return the Communication (in
entirety) and delete the Communication (in entirety and copies included)
from your records and systems. Unauthorized use, disclosure or copying
of this Communication or any part thereof is strictly prohibited and may
be unlawful.

Re: Dependency causes 'compiler message file broken' error

2006-06-12 Thread Kanakambaran Nair


Any suggestions on this. This problem is really bugging me.



On 5/22/06, Kanakambaran Nair [EMAIL PROTECTED] wrote:


This issue is solved when module C is given as a dependency in the
project.xml of module A. I do not understand why this works, because A
does not have any compile time dependency on C.

Could somebody please explain ?

RE: How to setup log4j with different settings for main, test and developmen

2006-06-12 Thread Shute, James

I use this setup which works for me (Idea 5.1 / Maven 1.0.2) and looks
like it covers what you want:

Put the appropriate log4j.properties file in:
1. main/resources
2. test/resources
3. test/java

(plus the relevant resource location definition in the pom for 1  2)

So for me 3 always gets precedence over 1  2 when running in the IDE
and 2 gets precedence over 1 when running the tests under maven.

The only limitation is that if you don't do a clean before running the
tests then 3 can get precedence when running the tests under maven if
you've run the tests in the IDE.  

A fairly simple solution to this is to call file 2
maven-log4j.properties, and then in your project.properties add:
  maven.junit.sysproperties=log4j.configuration
  log4j.configuration=maven-log4j.properties

Hope that helps

James


On 6/10/06, Jimisola Laursen [EMAIL PROTECTED] wrote:


 Hi!

 I've seen various posts on log4j and Maven, but I haven't seen any 
 answer to what I want to do. I want to be able to use different 
 settings for log4j
 for:

 1. main (releases using mvn assembly)
 2. tests (unit tests)
 3. development (when running/debugging the program within Eclipse or 
 outside with more extra logging)

 I know that I should place log4j.properties under main/resources and 
 test/resources. This will hopefully solve 1) and 2) . However,  I read

 something about Maven giving precedence to main/resources instead of 
 test/resources - is that still the case?

 I would like to avoid a long line of system properties on the command 
 line since they're easy to forget and especially for new develepors to

 get. I'd then prefer to just add one environment property (main, 
 test,
 development)
 which can then be used throughout our Maven environment in case we 
 have similiar situations.

 Any ideas?

 Regards,
 Jimisola
 --
 View this message in context:
 http://www.nabble.com/How-to-setup-log4j-with-different-settings-for-m
 ain%2C-test-and-developmen-t1766805.html#a4808936
 Sent from the Maven - Users forum at Nabble.com.


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





--
This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.


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

prevent update on a per plugin basis?

2006-06-12 Thread Franz Fehringer


Hello,

With mvn -o it is possible, to prevent updates entirely.
Now say i want to prevent updates for a specific plugin (junit for 
example) only.

How do i achieve this, i.e. which pom change(s) do i need?

Thanks and best regards

Franz


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

Re: prevent update on a per plugin basis?


lock down your plugins thru pluginManagement in your root pom

http://maven.apache.org/ref/current/maven-model/maven.html#class_pluginManagement

-D


On 6/12/06, Franz Fehringer [EMAIL PROTECTED] wrote:


Hello,

With mvn -o it is possible, to prevent updates entirely.
Now say i want to prevent updates for a specific plugin (junit for
example) only.
How do i achieve this, i.e. which pom change(s) do i need?

Thanks and best regards

Franz




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

RE: Dependency causes 'compiler message file broken' error

2006-06-12 Thread Jörg Schaible

Kanakambaran Nair wrote on Monday, May 22, 2006 8:11 AM:

 This issue is solved when module C is given as a dependency in the
 project.xml of module A. I do not understand why this works, because
 A does not have any compile time dependency on C.

Are you sure? Do you make usage of classes that extend types of C?

 Could somebody please explain ?

The compiler must know all base classes to compile sources - even if there's no 
directly usage. Further explanantions might be possible if you post the exact 
error/exception (run Maven with -e option).

- Jörg

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

Profiles for sub-projects

2006-06-12 Thread Boden, David

As part of a multi-project build, I have defined a profile/ in my
*parent* pom. I would like this profile to be switched on for some of
the sub-projects (my GUI components), and off for other subprojects (my
shared and server components).

In the example I've given, I want the profile to be activated on a
per-sub-project basis when the file plugin.xml is located in the root
directory of the sub-project.

At the moment, Maven decides *once* for the multi-project whether to
activate the profile depending on whether a plugin.xml file is present
in the *aggregator* pom's root directory (multi-project pom). Is this
behaviour a bug? If so, I'll raise a Jira. Is there some other way that
I can get around this other than copying the plugin configurations to
every single one of my sub-projects?

Many thanks,
Dave






Configuration in the *parent* pom:

profiles
!--
The guibundle profile prepares and signs an RCP
bundle. It is activated in the projects which
need to be distributed as RCP plugins, i.e. the
ones which get distributed to the GUI.

It is activated when a plugin.xml file exists.
-- 
profile
idguibundle/id
activation
file
existsplugin.xml/exists
/file
/activation
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
configuration
archive
 
manifestFileMETA-INF/MANIFEST.MF/manifestFile
/archive
descriptors
 
descriptor../SSBuild/bundle-assembly.xml/descriptor
/descriptors
/configuration
/plugin
/plugins
/build
/profile
/profiles


--
This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.


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

Re: Best practices for multi-flavour build?

2006-06-12 Thread badaud


I will try something like this, thanks.
--
View this message in context: 
http://www.nabble.com/Best-practices-for-multi-flavour-build--t1741483.html#a4826563
Sent from the Maven - Users forum at Nabble.com.


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

Multiproject: Merge Javadoc's into parents site?

2006-06-12 Thread Jochen Wiedmann


Hi,

I have a project (Apache XML-RPC) with three subprojects (common,
client, server), each of which are building a jar file. The site is
created by the parent project.

Now I'd like to integrate the Javadoc's into the site. But how to do that?

Regards,

Jochen

--
Whenever you find yourself on the side of the
majority, it is time to pause and reflect.
(Mark Twain)

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

RE: Error looking up lifecycle mapping to retrieve optional mojos

2006-06-12 Thread andreas.ebbert-karroum

Hi Eric, Dan,

Thanks a lot for your support! I was thinking that I am too stupid to get this 
straigt.

= I will try the workaround as proposed by Eric
= I will open a JIRA for maven-plugin-plugin

I agree, plexus documentation is bad - even with the book, there could be a lot 
more material.

Andreas 

-Original Message-
From: ext dan tran [mailto:[EMAIL PROTECTED] 
Sent: 10 June, 2006 18:44
To: Maven Users List
Subject: Re: Error looking up lifecycle mapping to retrieve 
optional mojos

native-maven-plugin experience the same thing, sound like a bug

Please file a JIRA

Eric, where do have the work around?  your plugin's pom?  or 
the the project that use it?

-D


On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote:

 Component descriptor cannot be found in the component repository:
 
org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica
 tion

 Component role-hints in Plexus are tacked onto the end of the role 
 name, and loaded like a role (someone correct me if I'm wrong about 
 this... good Plexus documentation is nonexistant). The 
problem is that 
 your classloader isn't finding your component.xml file, and 
so when it 
 tries to load your tigerstripe-application packaging role-hint, its 
 not there. You have to tell the maven-plugin-plugin about your 
 project. What I ended up having to do was add my plugin as a 
 dependency of maven-plugin-plugin in the POM that was using it:

 plugins
 plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
  prefixruby/prefix
/configuration
dependencies
  dependency
groupIdorg.codehaus.mojo/groupId
artifactIdrubyscript-maven-plugin/artifactId
version1.0-alpha-3-SNAPSHOT/version
  /dependency
/dependencies
 /plugin
 /plugins

 Its kind of ugly, so I created a parent that all plugin projects may 
 inherit from. It works. If you find a better way to make the 
 plugin-plugin find your components, however, please be good 
enough to 
 post it.

 Eric


 On 6/10/06, [EMAIL PROTECTED]  
 [EMAIL PROTECTED] wrote:
 
  Has somebody else also had this error? What can I do about it?
 
  Thanks,
  _ ___  _
  //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com
 `-`
 Andreas Ebbert-Karroum
 Senior Software Design Engineer
  Nokia Networks Services / Middleware
  phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer 
Straße 1, 
  40472 Düsseldorf, Germany
 
  

  -- This message is confidential. If you have received this message 
  in
 error,
  please delete it from your system. You should not copy it for any
 purpose,
  or disclose its contents to any other person. Internet 
  communications
 are
  not secure and therefore Nokia GmbH does not accept legal 
  responsibility for the contents of this message as it has been 
  transmitted over a
 public
  network. Thank you.
  Nokia GmbH, Nokia Networks is a German Company. Further 
information 
  about the Company is available from its principal offices at 
  Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the 
  website at http://www.nokia.com/
  

  --
 
  -Original Message-
  From: ext
  [EMAIL PROTECTED]
  e.org
  [mailto:[EMAIL PROTECTED]
  en.apache.org]
  Sent: 08 June, 2006 01:09
  To: users@maven.apache.org
  Subject: Error looking up lifecycle mapping to retrieve optional 
  mojos
  
  Hi,
  
  I've defined my own plugin (with the maven-plugin-tools-ant
  plugin) with it's own lifecycle and artifact handler. when I now 
  try to use the plugin in another project, it works fine, but I'm 
  getting this debug warning - and I have no clue, what it 
is about - 
  can it be fixed, and if yes, how?
  
  [DEBUG] Error looking up lifecycle mapping to retrieve optional 
  mojos. Lifecycle ID: default. Error:
   Component descriptor cannot be found in the component
  repository: org.apache.maven.lifecycle.mappin 
  g.LifecycleMappingtigerstripe-application.
  org.codehaus.plexus.component.repository.exception.ComponentLoo
  kupException: Component descriptor ca nnot be found in the 
  component repository:
  org.apache.maven.lifecycle.mapping.LifecycleMappingtigers
  tripe-application.
  at
  org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus
  Container.java:323)
  at
  org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus
  Container.java:440)
  at
  
org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona
  lMojosForLifecycle(Default
  LifecycleExecutor.java:1106)
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc
  leForPackaging(DefaultLife
  cycleExecutor.java:994)
  at

Re: Trouble with profile activation

2006-06-12 Thread Roland Asmann

You could switch activation of your profiles to properties and define the 
MyFaces with the 'not available' and the
reference-implementation wth the 'available' version.

Example:

profiles
profile
idmyfaces/id
activation
property
name!jsfri/name
/property
/activation
!-- Your MyFaces-specific stuff --
/profile
profile
idjsfri/id
activation
property
namejsfri/name
/property
/activation
!-- Your Reference-implementation-specific stuff --
/profile
/profiles

Now, if you would run 'mvn install', it should activate the myfaces-profile per 
default. If you want to activate the JSF
Reference-implementation you should run 'mvn -Djsfri=true'.

Hope this helped,

Roland



On Saturday 10 June 2006 23:01, Wendy Smoak wrote:
 I need help understanding this:

 If a profile that's embedded in POM is activated by a means other
 than activeByDefault/, then all activeByDefault/ triggers are
 suppressed. -- http://jira.codehaus.org/browse/MNG-2136

 I have a profile that gets activated when JDK 1.5 is in use.

 I need another profile (id=myfaces) to be active by default and bring
 in the MyFaces JSF implementation and API jars.  That is, 'mvn
 install' should Just Work, and use MyFaces.

 And then I need a way to say, Don't use MyFaces, use the JSF
 Reference Implementation from Sun instead. (Another profile with
 id=jsfri)

 Right now, I have the 'myfaces' profile set as activeByDefault, but it
 gets suppressed by the rule quoted above, since the jdk15 profile was
 activated by the use of JDK 1.5 to compile.

 That means we always have to specify -Pmyfaces or -Pjsfri, or the
 project won't compile.

 Here's the pom in question:
  * http://svn.apache.org/repos/asf/struts/shale/branches/mvn_reorg/pom.xml

 Any ideas on how to get exactly one of the myfaces or jsfri profiles
 activated?

 Thanks,


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

integration builds and version numbers

2006-06-12 Thread EJ Ciramella

How are people updating their pom.xml files with version numbers from
say cruisecontrol?
 
We have two types of codelines (in perforce) here, project and release
lines.  Everything starts out life as a project then over time one (or
more) projects can be integrated to a release line.
 
I'm curious, we're forcefully editing (with the ant replace task) some
templated version.html files to reflect what version was built.  Do I
need to be doing this to the pom.xml files also?
 
When something is getting built from a project branch, the build number
looks like this:
 
X.projectbranchname.buildnumber
 
So:
 
8.P01.1
 
In the maven world, all the project branches would look like this:
 
versionX.X-SNAPSHOT/version
 
So in the above case - 
 
version8.0-P01-SNAPSHOT/version
 
And when that goes to release
 
version8.0.X/version
 
Where X is a build number.
 
This has a problem though - I'll have to remember the dependency order
to build and make sure that module C gets built before B which is
built before A (or the replace at least happens in that order).
 
So what are people doing for this?  Manually updating before every
build?  I _really_ don't want to have to go back to that

RE: Assembly and multi-levels multi-modules

2006-06-12 Thread LECAN Damien

  Not 100% sure on this, but what if you try to make 2 assemblies  
  here? the first one for the subsub-modules (inside the subparent)
  and the second one with the result of the subparent (=assembly of  
  subsub-modules) and submodule?
  Not sure on how to do this, but it seems kind of logical this way  
  to me...
 
 I think this is a really cool idea I tried to do it for my  
 project but unfortunately I couldn't find a way to reference the  
 assembly of the subModule in the moduleSet of the parent 
 module.  The  
 submodule assembly gets set as an 'attached' artifact and not the  
 main one.. by the binaries tag in the moduleSet only supports the  
 main modules.  If we could add the classifier's on this would work  
 very well I think!
I looked at the code and a kind of filter restricts the content of the reactor 
(in AbstractAssemblyMojo#getModulesFromReactor(MavenProject, boolean), with 
method isProjectModule(...)).

If I remove this filter, I get everything I need in my assembly. But this 
should produce issues in the special cases I think.

I think I will fill a new jira issue for that.

Damien Lecan

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

RE: Wagon-webdav distribution - where to put username/password

I'm testing with SVN 413644, and I still can not get this to work with
authentication. Looking at my original post, are the username/passwords
supposed to be placed in settings.xml?

 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 07, 2006 2:48 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put 
 username/password

 I think it's due to a bug that was fixed in SVN, check
 http://jira.codehaus.org/browse/WAGON-48

 On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
  Hey all,
  I'm trying to distribute artifacts to a webdav server, but I do not 
  seem to know where to put the username/password.  When the webdav 
  server (apache 2.2) is un-secured, it works fine.

  Configured Maven as follows:

  Pom.xml
  =
  distributionManagement
  repository
  idmy-secure-repo/id
  urldav:http://reposerver/myrepo/url
  ...
  ==

  Then tried settings.xml
  ==
  servers
  server
idmy-secure-repo/id
usernameuserthingy/username
  passwordpasswordthingy/password
  ..
  ==

  Any ideas please?  If this is documented somewhere, please 
 point me to 
  the location. Been 'working' with this for most of this 
 week, a quick 
  answer would definitely help!

  -D

 -

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

RE: Error looking up lifecycle mapping to retrieve optional mojos

On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote:

Hi,

I believe the workaround is unneccesary.

You just need to specify extensionstrue/extensions in the plugin
setion in the depending pom.

-- Kenney

 Hi Eric, Dan,

 Thanks a lot for your support! I was thinking that I am too stupid to get 
 this straigt.

 = I will try the workaround as proposed by Eric
 = I will open a JIRA for maven-plugin-plugin

 I agree, plexus documentation is bad - even with the book, there could be a 
 lot more material.

 Andreas

 -Original Message-
 From: ext dan tran [mailto:[EMAIL PROTECTED]
 Sent: 10 June, 2006 18:44
 To: Maven Users List
 Subject: Re: Error looking up lifecycle mapping to retrieve
 optional mojos
 
 native-maven-plugin experience the same thing, sound like a bug
 
 Please file a JIRA
 
 Eric, where do have the work around?  your plugin's pom?  or
 the the project that use it?
 
 -D
 
 
 On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote:
 
  Component descriptor cannot be found in the component repository:
 
 org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica
  tion
 
  Component role-hints in Plexus are tacked onto the end of the role
  name, and loaded like a role (someone correct me if I'm wrong about
  this... good Plexus documentation is nonexistant). The
 problem is that
  your classloader isn't finding your component.xml file, and
 so when it
  tries to load your tigerstripe-application packaging role-hint, its
  not there. You have to tell the maven-plugin-plugin about your
  project. What I ended up having to do was add my plugin as a
  dependency of maven-plugin-plugin in the POM that was using it:
 
  plugins
  plugin
 artifactIdmaven-plugin-plugin/artifactId
 configuration
   prefixruby/prefix
 /configuration
 dependencies
   dependency
 groupIdorg.codehaus.mojo/groupId
 artifactIdrubyscript-maven-plugin/artifactId
 version1.0-alpha-3-SNAPSHOT/version
   /dependency
 /dependencies
  /plugin
  /plugins
 
  Its kind of ugly, so I created a parent that all plugin projects may
  inherit from. It works. If you find a better way to make the
  plugin-plugin find your components, however, please be good
 enough to
  post it.
 
  Eric
 
 
  On 6/10/06, [EMAIL PROTECTED] 
  [EMAIL PROTECTED] wrote:
  
   Has somebody else also had this error? What can I do about it?
  
   Thanks,
   _ ___  _
   //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com
  `-`
  Andreas Ebbert-Karroum
  Senior Software Design Engineer
   Nokia Networks Services / Middleware
   phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer
 Straße 1,
   40472 Düsseldorf, Germany
  
  
 
   -- This message is confidential. If you have received this message
   in
  error,
   please delete it from your system. You should not copy it for any
  purpose,
   or disclose its contents to any other person. Internet
   communications
  are
   not secure and therefore Nokia GmbH does not accept legal
   responsibility for the contents of this message as it has been
   transmitted over a
  public
   network. Thank you.
   Nokia GmbH, Nokia Networks is a German Company. Further
 information
   about the Company is available from its principal offices at
   Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the
   website at http://www.nokia.com/
  
 
   --
  
   -Original Message-
   From: ext
   [EMAIL PROTECTED]
   e.org
   [mailto:[EMAIL PROTECTED]
   en.apache.org]
   Sent: 08 June, 2006 01:09
   To: users@maven.apache.org
   Subject: Error looking up lifecycle mapping to retrieve optional
   mojos
   
   Hi,
   
   I've defined my own plugin (with the maven-plugin-tools-ant
   plugin) with it's own lifecycle and artifact handler. when I now
   try to use the plugin in another project, it works fine, but I'm
   getting this debug warning - and I have no clue, what it
 is about -
   can it be fixed, and if yes, how?
   
   [DEBUG] Error looking up lifecycle mapping to retrieve optional
   mojos. Lifecycle ID: default. Error:
Component descriptor cannot be found in the component
   repository: org.apache.maven.lifecycle.mappin
   g.LifecycleMappingtigerstripe-application.
   org.codehaus.plexus.component.repository.exception.ComponentLoo
   kupException: Component descriptor ca nnot be found in the
   component repository:
   org.apache.maven.lifecycle.mapping.LifecycleMappingtigers
   tripe-application.
   at
   org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus
   Container.java:323)
   at
   org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus
   Container.java:440)
   at
  
 org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120)

Maven-proxy not downloading depdencies

2006-06-12 Thread Carlos.Fernandez

I am having problems setting up the maven-proxy as a web application.

I have maven-proxy deployed in tomcat and it seems to be up and running.
I can navigate config and repository screens.  If I copy files into the
local repository it uses I can also search for them.

I removed the Jakarta commons http-client v3.0 from my local repository
and tried to run my unit tests via maven.  I assumed that the proxy
would download the missing jar and pom and then pass them to my maven
client.  I should then see the http-client v3 dir and files in the
maven-proxy repository.

However, when I try to build something in maven, it doesn't seem to
download any required dependencies.  It just 404s.

Any ideas?

I pasted the relevant messages and configs from maven, tomcat and
maven-proxy.properties.

Carlos

#Excerpts from mvn test on the CL.

It seems to be looking for the file from the proxy - and the URL
should be correct.  When I check it firefox, it pulls up a 404.
Downloading:
http://localhost:8008/maven-proxy-webapp/repository/commons-httpclient/c
ommons-httpclient/3.0/commons-httpclient-3.0.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)

Error message
1) commons-httpclient:commons-httpclient:jar:3.0

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=commons-httpclient
-DartifactId=commons
-httpclient \
  -Dversion=3.0 -Dpackaging=jar -Dfile=/path/to/file

#3Tomcat logs
2006-06-12 08:32:32,866 [INFO ] proxy.servlets.RepositoryServlet  -
Received req
uest:
/commons-httpclient/commons-httpclient/3.0/commons-httpclient-3.0.jar
2006-06-12 08:32:32,866 [DEBUG] proxy.engine.DownloadEngine  - Request:
source=1
27.0.0.1,
path=/commons-httpclient/commons-httpclient/3.0/commons-httpclient-3.0
.jar, lastModified=-1, headOnly=false, ifModifiedSince=-1
2006-06-12 08:32:32,866 [DEBUG] proxy.config.FileRepoConfiguration  -
Repo[globa
l]: Checking last modified time for
C:\tools\maven-proxy\repo\commons-httpclient
\commons-httpclient\3.0\commons-httpclient-3.0.jar
2006-06-12 08:32:32,866 [DEBUG] proxy.config.FileRepoConfiguration  -
Repo[local
-repo]: Checking last modified time for
C:\tools\maven-proxy\repo\commons-httpcl
ient\commons-httpclient\3.0\commons-httpclient-3.0.jar
2006-06-12 08:32:32,866 [INFO ] components.impl.DefaultSnapshotCache  -
Updating
 /commons-httpclient/commons-httpclient/3.0/commons-httpclient-3.0.jar
in snapsh
ot cache
2006-06-12 08:32:32,866 [INFO ] components.impl.DefaultSnapshotCache  -
Updating
 /commons-httpclient/commons-httpclient/3.0/commons-httpclient-3.0.jar
in snapsh
ot cache


##maven-proxy config
#These are just some default properties for testing with.

 GLOBAL SETTINGS
# This is where maven-proxy stores files it has downloaded
repo.local.store=C:\\tools\\maven-proxy\\repo

#The port to listen on
#port=

#This is the base area that all files are loaded from. While it is
possible to leave this blank, this behaviour
#is deprecated and will be disabled in version 2.0.  There are too many
namespace conflicts caused by not using
#a prefix.
#The repository will be shown at http://localhost:/repository/
#for the .war loaded into a webapp server, the default prefix is
repository (edit the web.xml to change)
# As maven doesn't like a trailing slash, this address shouldn't have
one either.
prefix=repository
#prefix=maven-proxy-webapp

#This is the simple date format used to display the last modified date
while browsing the repository.
lastModifiedDateFormat=/MM/dd HH:mm:ss

 SNAPSHOT HANDLING
#If you want the proxy to look for newer snapshots, set to true
snapshot.update=true
#snapshot.update=false

 PROMOTION HANDLING
# * NOT CURRENTLY IMPLEMENTED *
#Promotion describes the process by which new artifacts are loaded to
global maven-proxy repository.  It
# is designed to be used by higher security installations that do not
want to acquire artifacts from 
# remote repositories without approval.
#
#If promotion handling is enabled, then the proxy will not download
remote artifacts without permission
# (local repositories with copy=false are considered to be local)
#
#Permission to download is granted via the Promotion menu which will be
enabled 
#  when promotion handling is enabled.
#
#If promotion is false, artifacts are sourced from any repository as per
normal.
#
#Promotion and snapshots:  If promotion is enabled, snapshots are not
downloadable.  The concept of using
# a snapshot in a production build (which is primarily what promotion is
for) is counterintuitive.
## 
promotion=false

 WEB INTERFACE
# This defines the absolute URL the server should use to identify
itself.
# This can often be determined automatically, but we recommend you
specify
# it explicitly to prevent problems during startup.
# The prefix will be added to this

Re: Wagon-webdav distribution - where to put username/password


Yes, http://maven.apache.org/guides/mini/guide-deployment-security-settings.html

On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:

I'm testing with SVN 413644, and I still can not get this to work with
authentication. Looking at my original post, are the username/passwords
supposed to be placed in settings.xml?


 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, June 07, 2006 2:48 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put
 username/password

 I think it's due to a bug that was fixed in SVN, check
 http://jira.codehaus.org/browse/WAGON-48

 On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
  Hey all,
  I'm trying to distribute artifacts to a webdav server, but I do not
  seem to know where to put the username/password.  When the webdav
  server (apache 2.2) is un-secured, it works fine.
 
  Configured Maven as follows:
 
  Pom.xml
  =
  distributionManagement
  repository
  idmy-secure-repo/id
  urldav:http://reposerver/myrepo/url
  ...
  ==
 
  Then tried settings.xml
  ==
  servers
  server
idmy-secure-repo/id
usernameuserthingy/username
  passwordpasswordthingy/password
  ..
  ==
 
  Any ideas please?  If this is documented somewhere, please
 point me to
  the location. Been 'working' with this for most of this
 week, a quick
  answer would definitely help!
 
  -D
 
 
 -


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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

nice repos :-)

2006-06-12 Thread cameron101


http://www.mvnrepository.com

Cactus plugin?

2006-06-12 Thread vitaliy . shevchuk

Hi,

I have heard that Cactus plugin for Maven 2 is currently under development.
For us, it is the last peace of the puzzle for lossless migration from
maven 1 to maven 2.

Is there any alpha or beta version of maven 2 cactus plugin available?

Thanks a lot for the great job you are doing!
Vitaliy Shevchuk


This message and any attachments (the message) is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

-

Ce message et toutes les pieces jointes (ci-apres le 
message) sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.


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

Re: Cactus plugin?

On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote:

Hi,

I believe there's nothing usable yet, but I could be wrong. In the mean
time you could use the maven-antrun-plugin to call the cactus ant tasks.
It's not ideal but it'll help you migrate.

You could also take a look at
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html.

-- Kenney

 Hi,

 I have heard that Cactus plugin for Maven 2 is currently under development.
 For us, it is the last peace of the puzzle for lossless migration from
 maven 1 to maven 2.

 Is there any alpha or beta version of maven 2 cactus plugin available?

 Thanks a lot for the great job you are doing!
 Vitaliy Shevchuk


 This message and any attachments (the message) is
 intended solely for the addressees and is confidential.
 If you receive this message in error, please delete it and
 immediately notify the sender. Any use not in accord with
 its purpose, any dissemination or disclosure, either whole
 or partial, is prohibited except formal approval. The internet
 can not guarantee the integrity of this message.
 BNP PARIBAS (and its subsidiaries) shall (will) not
 therefore be liable for the message if modified.

 -

 Ce message et toutes les pieces jointes (ci-apres le
 message) sont etablis a l'intention exclusive de ses
 destinataires et sont confidentiels. Si vous recevez ce
 message par erreur, merci de le detruire et d'en avertir
 immediatement l'expediteur. Toute utilisation de ce
 message non conforme a sa destination, toute diffusion
 ou toute publication, totale ou partielle, est interdite, sauf
 autorisation expresse. L'internet ne permettant pas
 d'assurer l'integrite de ce message, BNP PARIBAS (et ses
 filiales) decline(nt) toute responsabilite au titre de ce
 message, dans l'hypothese ou il aurait ete modifie.


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


--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

deleting projects

2006-06-12 Thread Jonathan Tilley

Hi,

 

I am trying to delete a project from Continuum.

I click the red cross, confirm that I want to delete the project and I
get the stack trace below.

Any ideas?

 

Also how does one delete a particular build?

We have many cases where Continuum thinks the build for a project is
still going, but in fact the build has completed.

Where is the project built information stored? I.e. stuff like Build#,
Start Time, End Time, state etc.

Is it in the Derby database? If so how does one for example change the
state of a project from building to Build in Failure.

 

 

Cheers

 

jonathan

 

ognl.MethodFailedException: Method removeProject failed for object
[EMAIL PROTECTED]
[org.apache.maven.continuum.ContinuumException: Error while deleting
project working directory.]
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796)
at
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
at ognl.SimpleNode.getValue(SimpleNode.java:210)
at ognl.Ognl.getValue(Ognl.java:333)
at ognl.Ognl.getValue(Ognl.java:378)
at ognl.Ognl.getValue(Ognl.java:357)
at
org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation
(DeleteEntity.java:57)
at
org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav
a:47)
at
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve
.java:68)
at
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe
line.java:70)
at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
andler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
text.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218
)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
/-- Encapsulated exception \
org.apache.maven.continuum.ContinuumException: Error while deleting
project working directory.
at
org.apache.maven.continuum.DefaultContinuum.logAndCreateException(Defaul
tContinuum.java:2114)
at
org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinu
um.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491)
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785)
at
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
at ognl.SimpleNode.getValue(SimpleNode.java:210)
at ognl.Ognl.getValue(Ognl.java:333)
at ognl.Ognl.getValue(Ognl.java:378)
at ognl.Ognl.getValue(Ognl.java:357)
at
org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation
(DeleteEntity.java:57)
at
org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav
a:47)
at
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve
.java:68)
at
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe
line.java:70)
at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at

Re: Trouble with profile activation

2006-06-12 Thread Wendy Smoak


On 6/12/06, Roland Asmann [EMAIL PROTECTED] wrote:


You could switch activation of your profiles to properties and define the 
MyFaces with the 'not available' and the reference-implementation wth the 
'available' version.


Thanks!  This works perfectly.  I made one small change, using the
property 'jsf' so that !jsf means MyFaces, and jsf=ri means the RI.
That way when someone writes a third JSF implementation, we can
support it.

--
Wendy

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

include dependencies in a plugin

2006-06-12 Thread rebels_mascot


I'm using the spring-mock plugin and also need the spring-jdbc, the
spring-jdbc is a dependency in the spring-mock pom but is set to optional
true. How do I set the spring-mock dependency to include the spring-jdbc? 
--
View this message in context: 
http://www.nabble.com/include-dependencies-in-a-plugin-t1774087.html#a4828762
Sent from the Maven - Users forum at Nabble.com.


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

Re: Trouble with profile activation

2006-06-12 Thread Roland Asmann

Be carefull with that, then you'd also need to add the value-tag for the 
property, but I that's documented
pretty well I believe...

Roland



On Monday 12 June 2006 15:20, Wendy Smoak wrote:
 On 6/12/06, Roland Asmann [EMAIL PROTECTED] wrote:
  You could switch activation of your profiles to properties and define the
  MyFaces with the 'not available' and the reference-implementation wth the
  'available' version.

 Thanks!  This works perfectly.  I made one small change, using the
 property 'jsf' so that !jsf means MyFaces, and jsf=ri means the RI.
 That way when someone writes a third JSF implementation, we can
 support it.


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

Re: Trouble with profile activation

2006-06-12 Thread Wendy Smoak


On 6/12/06, Roland Asmann [EMAIL PROTECTED] wrote:

Be carefull with that, then you'd also need to add the value-tag for the 
property, but I that's documented
pretty well I believe...


Right, that's what I meant.  (I think.)

For MyFaces:  name!jsf/name

For JSF RI: namejsf/namevalueri/value

Are you saying I need a value for the MyFaces profile?

Thanks,
Wendy

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

Re: Trouble with profile activation

2006-06-12 Thread Roland Asmann

No, I meant that you need one for the RI, just like you did. ;-)
I just said it, because in my example you could only have 2 profiles, since I 
left the value out.

Roland



On Monday 12 June 2006 15:40, Wendy Smoak wrote:
 On 6/12/06, Roland Asmann [EMAIL PROTECTED] wrote:
  Be carefull with that, then you'd also need to add the value-tag for
  the property, but I that's documented pretty well I believe...

 Right, that's what I meant.  (I think.)

 For MyFaces:  name!jsf/name

 For JSF RI: namejsf/namevalueri/value

 Are you saying I need a value for the MyFaces profile?

 Thanks,
 Wendy

 -
 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: deleting projects

2006-06-12 Thread Emmanuel Venisse




Jonathan Tilley a écrit :

Hi,

 


I am trying to delete a project from Continuum.

I click the red cross, confirm that I want to delete the project and I
get the stack trace below.

Any ideas?


You have a lock in your working directory :

Caused by: java.io.IOException: Directory
D:\java\test\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-dire
ctory\1\mform_presentation\mform_pres_Admin\target\mform_pres_Admin\WEB-
INF\classes\com\rdf\mform\ui\admin\maintainincentives\view unable to be
deleted.

it's perhaps a dos console opened on it.



 


Also how does one delete a particular build?


You can't actually. It will be perhaps a 1.1 feature.



We have many cases where Continuum thinks the build for a project is
still going, but in fact the build has completed.

Where is the project built information stored? I.e. stuff like Build#,
Start Time, End Time, state etc.

Is it in the Derby database? If so how does one for example change the
state of a project from building to Build in Failure.


Yes, it's in database. If you modify it directly, you'll need to change the state value from '6' to 
'3' in PROJECT table and perhaps in BUILDRESULT table


Emmanuel



 

 


Cheers

 


jonathan

 


ognl.MethodFailedException: Method removeProject failed for object
[EMAIL PROTECTED]
[org.apache.maven.continuum.ContinuumException: Error while deleting
project working directory.]
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796)
at
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
at ognl.SimpleNode.getValue(SimpleNode.java:210)
at ognl.Ognl.getValue(Ognl.java:333)
at ognl.Ognl.getValue(Ognl.java:378)
at ognl.Ognl.getValue(Ognl.java:357)
at
org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation
(DeleteEntity.java:57)
at
org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.jav
a:47)
at
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve
.java:68)
at
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe
line.java:70)
at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
andler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
text.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218
)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
/-- Encapsulated exception \
org.apache.maven.continuum.ContinuumException: Error while deleting
project working directory.
at
org.apache.maven.continuum.DefaultContinuum.logAndCreateException(Defaul
tContinuum.java:2114)
at
org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinu
um.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491)
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785)
at
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
at ognl.SimpleNode.getValue(SimpleNode.java:210)
at ognl.Ognl.getValue(Ognl.java:333)
at ognl.Ognl.getValue(Ognl.java:378)
at ognl.Ognl.getValue(Ognl.java:357)
at
org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation

Re: include dependencies in a plugin

On Mon, 12 Jun 2006, rebels_mascot wrote:

You have to manually add the spring-jdbc dependency to your pom.

-- Kenney


 I'm using the spring-mock plugin and also need the spring-jdbc, the
 spring-jdbc is a dependency in the spring-mock pom but is set to optional
 true. How do I set the spring-mock dependency to include the spring-jdbc?
 --
 View this message in context: 
 http://www.nabble.com/include-dependencies-in-a-plugin-t1774087.html#a4828762
 Sent from the Maven - Users forum at Nabble.com.


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


--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

Problems with mvn site

2006-06-12 Thread alexis parratte


Hi,
I have a problem when i run mvn site this is the log i obtain


C:\Maven_Repository\mavenPim\target\checkoutsite.bat

C:\Maven_Repository\mavenPim\target\checkoutcall clean.bat

C:\Maven_Repository\mavenPim\target\checkoutmvn clean
[INFO] Scanning for projects...
[INFO]

[INFO] Building Dematerialisation de la fiche produit
[INFO]task-segment: [clean]
[INFO]

[INFO] [clean:clean]
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target\classes
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target\test-classes
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Mon Jun 12 16:22:33 CEST 2006
[INFO] Final Memory: 2M/5M
[INFO]

[INFO] Scanning for projects...
[INFO]

[INFO] Building Dematerialisation de la fiche produit
[INFO]task-segment: [site]
[INFO]

[INFO] [cobertura:clean {execution: default}]
[INFO] Setting property: classpath.resource.loader.class = '
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] Setting property: classpath.resource.loader.class = '
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
any resource loader.
[INFO] Velocimacro : error using  VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundExcepti
on: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] null
[INFO]

[INFO] Trace
java.lang.NullPointerException
   at org.apache.maven.plugin.DefaultPluginManager.addPlugin(
DefaultPluginManager.java:292)
   at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(
DefaultPluginManager.java:198)
   at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(
DefaultPluginManager.java:487)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(
DefaultLifecycleExecutor.java:1292)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(
DefaultLifecycleExecutor.java:657)
   at

RE: Problems with mvn site

2006-06-12 Thread EJ Ciramella

H- I get something similar:

[ERROR] BUILD FAILURE
[INFO]

[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE 

-Original Message-
From: alexis parratte [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 12, 2006 10:25 AM
To: users@maven.apache.org
Subject: Problems with mvn site

Hi,
I have a problem when i run mvn site this is the log i obtain


C:\Maven_Repository\mavenPim\target\checkoutsite.bat

C:\Maven_Repository\mavenPim\target\checkoutcall clean.bat

C:\Maven_Repository\mavenPim\target\checkoutmvn clean
[INFO] Scanning for projects...
[INFO]


[INFO] Building Dematerialisation de la fiche produit
[INFO]task-segment: [clean]
[INFO]


[INFO] [clean:clean]
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target\classes
[INFO] Deleting directory
C:\Maven_Repository\mavenPim\target\checkout\target\test-classes
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Mon Jun 12 16:22:33 CEST 2006
[INFO] Final Memory: 2M/5M
[INFO]

[INFO] Scanning for projects...
[INFO]


[INFO] Building Dematerialisation de la fiche produit
[INFO]task-segment: [site]
[INFO]


[INFO] [cobertura:clean {execution: default}]
[INFO] Setting property: classpath.resource.loader.class = '
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] Setting property: classpath.resource.loader.class = '
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
in
any resource loader.
[INFO] Velocimacro : error using  VM library template
VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundExcepti
on: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
may
NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
be
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] null
[INFO]

Re: Error looking up lifecycle mapping to retrieve optional mojos


Kenney,

The annoying warning is there even with extensionstrue/extensions.

BTW, lifecycle extension will not work at all if you dont have
extensionstrue/extensions specified thou

-D


On 6/12/06, Kenney Westerhof [EMAIL PROTECTED] wrote:


On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote:

Hi,

I believe the workaround is unneccesary.

You just need to specify extensionstrue/extensions in the plugin
setion in the depending pom.

-- Kenney

 Hi Eric, Dan,

 Thanks a lot for your support! I was thinking that I am too stupid to
get this straigt.

 = I will try the workaround as proposed by Eric
 = I will open a JIRA for maven-plugin-plugin

 I agree, plexus documentation is bad - even with the book, there could
be a lot more material.

 Andreas

 -Original Message-
 From: ext dan tran [mailto:[EMAIL PROTECTED]
 Sent: 10 June, 2006 18:44
 To: Maven Users List
 Subject: Re: Error looking up lifecycle mapping to retrieve
 optional mojos
 
 native-maven-plugin experience the same thing, sound like a bug
 
 Please file a JIRA
 
 Eric, where do have the work around?  your plugin's pom?  or
 the the project that use it?
 
 -D
 
 
 On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote:
 
  Component descriptor cannot be found in the component repository:
 
 org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica
  tion
 
  Component role-hints in Plexus are tacked onto the end of the role
  name, and loaded like a role (someone correct me if I'm wrong about
  this... good Plexus documentation is nonexistant). The
 problem is that
  your classloader isn't finding your component.xml file, and
 so when it
  tries to load your tigerstripe-application packaging role-hint, its
  not there. You have to tell the maven-plugin-plugin about your
  project. What I ended up having to do was add my plugin as a
  dependency of maven-plugin-plugin in the POM that was using it:
 
  plugins
  plugin
 artifactIdmaven-plugin-plugin/artifactId
 configuration
   prefixruby/prefix
 /configuration
 dependencies
   dependency
 groupIdorg.codehaus.mojo/groupId
 artifactIdrubyscript-maven-plugin/artifactId
 version1.0-alpha-3-SNAPSHOT/version
   /dependency
 /dependencies
  /plugin
  /plugins
 
  Its kind of ugly, so I created a parent that all plugin projects may
  inherit from. It works. If you find a better way to make the
  plugin-plugin find your components, however, please be good
 enough to
  post it.
 
  Eric
 
 
  On 6/10/06, [EMAIL PROTECTED] 
  [EMAIL PROTECTED] wrote:
  
   Has somebody else also had this error? What can I do about it?
  
   Thanks,
   _ ___  _
   //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com
  `-`
  Andreas Ebbert-Karroum
  Senior Software Design Engineer
   Nokia Networks Services / Middleware
   phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer
 Straße 1,
   40472 Düsseldorf, Germany
  
  
 
   -- This message is confidential. If you have received this message
   in
  error,
   please delete it from your system. You should not copy it for any
  purpose,
   or disclose its contents to any other person. Internet
   communications
  are
   not secure and therefore Nokia GmbH does not accept legal
   responsibility for the contents of this message as it has been
   transmitted over a
  public
   network. Thank you.
   Nokia GmbH, Nokia Networks is a German Company. Further
 information
   about the Company is available from its principal offices at
   Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the
   website at http://www.nokia.com/
  
 
   --
  
   -Original Message-
   From: ext
   [EMAIL PROTECTED]
   e.org
   [mailto:[EMAIL PROTECTED]
   en.apache.org]
   Sent: 08 June, 2006 01:09
   To: users@maven.apache.org
   Subject: Error looking up lifecycle mapping to retrieve optional
   mojos
   
   Hi,
   
   I've defined my own plugin (with the maven-plugin-tools-ant
   plugin) with it's own lifecycle and artifact handler. when I now
   try to use the plugin in another project, it works fine, but I'm
   getting this debug warning - and I have no clue, what it
 is about -
   can it be fixed, and if yes, how?
   
   [DEBUG] Error looking up lifecycle mapping to retrieve optional
   mojos. Lifecycle ID: default. Error:
Component descriptor cannot be found in the component
   repository: org.apache.maven.lifecycle.mappin
   g.LifecycleMappingtigerstripe-application.
   org.codehaus.plexus.component.repository.exception.ComponentLoo
   kupException: Component descriptor ca nnot be found in the
   component repository:
   org.apache.maven.lifecycle.mapping.LifecycleMappingtigers
   tripe-application.
   at

What does this mean?

2006-06-12 Thread Jeff Mutonho


Better Builds With Maven , page 83 ,second bulleted paragraph

As you're compiling J2EE code you need to have the J2EE
specifications JAR in the project's build classpath. This is achieved
by specifying a dependency element on the J2EE JAR. You could instead
specify a dependency on Sun's J2EE JAR. However, this JAR is not
redistributable and as such cannot be found on ibiblio. Fortunately,
the Geronimo project has made the J2EE JAR available under an Apache
license and this JAR can be found on ibiblio.

What does You could instead specify a dependency on Sun's J2EE JAR.
However, this JAR is not redistributable and as such cannot be found
on ibiblio  mean?Is this a consequence of Sun's licensing?

--


Jeff  Mutonho

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Re: What does this mean?

2006-06-12 Thread Eric Redmond


Correct. If a commonly required jar is not in ibiblio, its usually a
licensing issue.

On 6/12/06, Jeff Mutonho [EMAIL PROTECTED] wrote:


Better Builds With Maven , page 83 ,second bulleted paragraph

As you're compiling J2EE code you need to have the J2EE
specifications JAR in the project's build classpath. This is achieved
by specifying a dependency element on the J2EE JAR. You could instead
specify a dependency on Sun's J2EE JAR. However, this JAR is not
redistributable and as such cannot be found on ibiblio. Fortunately,
the Geronimo project has made the J2EE JAR available under an Apache
license and this JAR can be found on ibiblio.

What does You could instead specify a dependency on Sun's J2EE JAR.
However, this JAR is not redistributable and as such cannot be found
on ibiblio  mean?Is this a consequence of Sun's licensing?

--


Jeff  Mutonho

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Re: exported pom encoding


Hi Jörg,


2006/6/12, Jörg Schaible [EMAIL PROTECTED]:


Hi Stefan,

Stefan Hübner wrote on Sunday, June 11, 2006 9:25 AM:

 Hi all,

 an issue has been created on this over at
 http://jira.codehaus.org/browse/MECLIPSE-56, already. Fixing it
 decently seems to be quite a hassle though, because maven doesn't care
 much about pom.xml's encoding. at the moment the developers seem to
 consider rewriting the whole parsing stuff from scratch.

well, this might be another effect of the encoding problem, but this has nothing to do with 
Eclipse in special. As stated, the deployed POM will have the entities (like 
#xf6;) resolved and the XML is simply invalid.


[snip]

you're absolutely right, Jörg. The encoding misery is not limited to
Eclipse at all. This is just one symptom of many. Maven doesn't read
POMs using their declared encoding properly. It's certainly able to
resolve all sorts of entities but only with the effect, that those
characters will lead to new problems during POM-exports.

Maven simply uses the local system's default character set while
parsing or writing a POM. The same probably happens while writing
POMs.

To me it seems, that lots of those different sorts of character set
problems will only be resolved, if Maven starts to fully take into
account the POM's declared encoding.

You might have a look at http://jira.codehaus.org/browse/PLX-214 for
further discussions.


jm2c,
Stefan

RE: Profiles for sub-projects

2006-06-12 Thread Boden, David

I've managed to track this down. The profiles work correctly.

However, this bit is not working:
activation
file
existsplugin.xml/exists
/file
/activation

It is not looking for plugin.xml at ${basedir}/plugin.xml for each
sub-project as I'd expect. Instead, for each subproject it's just
evaluating the same multi-project-base/plugin.xml. I'm going to come up
with a simple scenario and raise a Jira.

Regards,
Dave
 
-Original Message-
From: Boden, David 
Sent: Monday, June 12, 2006 11:26 AM
To: 'users@maven.apache.org'
Subject: Profiles for sub-projects

As part of a multi-project build, I have defined a profile/ in my
*parent* pom. I would like this profile to be switched on for some of
the sub-projects (my GUI components), and off for other subprojects (my
shared and server components).

In the example I've given, I want the profile to be activated on a
per-sub-project basis when the file plugin.xml is located in the root
directory of the sub-project.

At the moment, Maven decides *once* for the multi-project whether to
activate the profile depending on whether a plugin.xml file is present
in the *aggregator* pom's root directory (multi-project pom). Is this
behaviour a bug? If so, I'll raise a Jira. Is there some other way that
I can get around this other than copying the plugin configurations to
every single one of my sub-projects?

Many thanks,
Dave






Configuration in the *parent* pom:

profiles
!--
The guibundle profile prepares and signs an RCP
bundle. It is activated in the projects which
need to be distributed as RCP plugins, i.e. the
ones which get distributed to the GUI.

It is activated when a plugin.xml file exists.
-- 
profile
idguibundle/id
activation
file
existsplugin.xml/exists
/file
/activation
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions
configuration
archive
 
manifestFileMETA-INF/MANIFEST.MF/manifestFile
/archive
descriptors
 
descriptor../SSBuild/bundle-assembly.xml/descriptor
/descriptors
/configuration
/plugin
/plugins
/build
/profile
/profiles


--
This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.


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

[m2] How can a plugin change the value of a variable?

2006-06-12 Thread Thomas Will

How can a maven2 plugin change the value of a
variable, which could be used then later by another
plugin?

The usage of System.get/setProperty is probably very
limited from a maven2 point of view.
Are there other options?

Thanks for any hints, 
Tom.

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

Re: Cactus plugin?

2006-06-12 Thread Raphaël Piéroni


There is one...
check it at cargo.codehaus.org

If you search for an example of use, the axistools archetype in the
mojo.codehaus.org sandbox's use it for testing.

Hope this helps.

Raphël

2006/6/12, Kenney Westerhof [EMAIL PROTECTED]:


On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote:

Hi,

I believe there's nothing usable yet, but I could be wrong. In the mean
time you could use the maven-antrun-plugin to call the cactus ant tasks.
It's not ideal but it'll help you migrate.

You could also take a look at
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html.

-- Kenney

 Hi,

 I have heard that Cactus plugin for Maven 2 is currently under
development.
 For us, it is the last peace of the puzzle for lossless migration from
 maven 1 to maven 2.

 Is there any alpha or beta version of maven 2 cactus plugin available?

 Thanks a lot for the great job you are doing!
 Vitaliy Shevchuk


 This message and any attachments (the message) is
 intended solely for the addressees and is confidential.
 If you receive this message in error, please delete it and
 immediately notify the sender. Any use not in accord with
 its purpose, any dissemination or disclosure, either whole
 or partial, is prohibited except formal approval. The internet
 can not guarantee the integrity of this message.
 BNP PARIBAS (and its subsidiaries) shall (will) not
 therefore be liable for the message if modified.

 -

 Ce message et toutes les pieces jointes (ci-apres le
 message) sont etablis a l'intention exclusive de ses
 destinataires et sont confidentiels. Si vous recevez ce
 message par erreur, merci de le detruire et d'en avertir
 immediatement l'expediteur. Toute utilisation de ce
 message non conforme a sa destination, toute diffusion
 ou toute publication, totale ou partielle, est interdite, sauf
 autorisation expresse. L'internet ne permettant pas
 d'assurer l'integrite de ce message, BNP PARIBAS (et ses
 filiales) decline(nt) toute responsabilite au titre de ce
 message, dans l'hypothese ou il aurait ete modifie.


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


--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

wrong status of ant project

2006-06-12 Thread Maksimenko Alexander


 hi!
I've got some strange behavior :
after building mine ant project I've got  success  status but  in  
output i see


deploy:
  [delete] Deleting directory jboss-3.2.7\server\default\deploy\workflow.ear

BUILD FAILED
working-directory\1\build.xml:140: The following error occurred while executing 
this line:
working-directory\1\build.xml:123: Unable to delete file 
jboss-3.2.7\server\default\deploy\workflow.ear\processbuilder.war\WEB-INF\lib\activation.jar

Total time: 19 seconds



so the build is actually failed

here is the scartch from ant file:

- 
mailbox:///C%7C/Documents%20and%20Settings/sasha/Application%20Data/Thunderbird/Profiles/u8d30cg2.default/Mail/bird.cris.net/Sent?number=19645# 
target name=*continium*

 antcall target=*create* /
 antcall target=*deploy* /
/target

am I missed something?

Re: Cactus plugin?


Hi Raphael,

2006/6/12, Raphaël Piéroni [EMAIL PROTECTED]:

There is one...
check it at cargo.codehaus.org

If you search for an example of use, the axistools archetype in the
mojo.codehaus.org sandbox's use it for testing.


[SNIP]

Do you meen the cargo-maven2-plugin? Does this actually help cactifying WARs?

Stefan

Re: Cactus plugin?


Hi Kenney,

2006/6/12, Kenney Westerhof [EMAIL PROTECTED]:

On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote:

Hi,

I believe there's nothing usable yet, but I could be wrong. In the mean
time you could use the maven-antrun-plugin to call the cactus ant tasks.
It's not ideal but it'll help you migrate.


[SNIP]

I'm currently trying to go that direction. But I didn't manage to
cactify the web application to test. That web application is different
from it's i-test-module and is referred as a dependency.

Do you have an example how to achieve this?


Cheers,
Stefan

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

RE: Wagon-webdav distribution - where to put username/password

I must be ignorant, I am following that example, have settings in
settings.xml, using wagon-webdav-1.0-beta-1-SNAPSHOT from Subversion
today (6/12/2006), and still unable to authenticate (with a known
username/password that is tested on the WebDAV site that works fine with
other tools, as well as manually with full PUT/MKCOL permissions).

Maven Debug Output:
=
[DEBUG] -- end configuration --
[INFO] deploy:deploy
WAGON_VERSION: 1.0-beta-1-SNAPSHOT
[DEBUG] not adding permissions to wagon connection
Jun 12, 2006 11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
processAuthenticationResponse
WARNING: No credentials available for the 'my webdav secure realm'
authentication realm at myserver
..
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: http://myserver/repo/myfile. Return code is: 401
Unauthorized
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java
:280)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(Defa
ultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defaul
tWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
tArtifactDeployer.java:77)
... 11 more
=

What else should I test? When authentication is disabled on the WebDAV
server, everything works fine. I tried changing the ID in settings.xml
to be 'my webdav secure realm', but that didn't work either.

Note above: [DEBUG] not adding permissions to wagon connection

-D
 

 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED] 
 Sent: Monday, June 12, 2006 8:36 AM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put 
 username/password
 
 Yes, 
 http://maven.apache.org/guides/mini/guide-deployment-security-
 settings.html
 
  On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
   Hey all,
   I'm trying to distribute artifacts to a webdav server, but I do 
   not seem to know where to put the username/password.  When the 
   webdav server (apache 2.2) is un-secured, it works fine.
  
   Configured Maven as follows:
  
   Pom.xml
   =
   distributionManagement
   repository
   idmy-secure-repo/id
   urldav:http://reposerver/myrepo/url
   ...
   ==
  
   Then tried settings.xml
   ==
   servers
   server
 idmy-secure-repo/id
 usernameuserthingy/username
   passwordpasswordthingy/password
   ..
   ==

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

Re: wrong status of ant project

2006-06-12 Thread Emmanuel Venisse


You need to modify ant script.

http://maven.apache.org/continuum/faqs.html#how-does-continuum-detect-a-successful-build

Emmanuel

Maksimenko Alexander a écrit :

 hi!
I've got some strange behavior :
after building mine ant project I've got  success  status but  in  
output i see


deploy:
  [delete] Deleting directory 
jboss-3.2.7\server\default\deploy\workflow.ear


BUILD FAILED
working-directory\1\build.xml:140: The following error occurred while 
executing this line:
working-directory\1\build.xml:123: Unable to delete file 
jboss-3.2.7\server\default\deploy\workflow.ear\processbuilder.war\WEB-INF\lib\activation.jar 



Total time: 19 seconds



so the build is actually failed

here is the scartch from ant file:

- 
mailbox:///C%7C/Documents%20and%20Settings/sasha/Application%20Data/Thunderbird/Profiles/u8d30cg2.default/Mail/bird.cris.net/Sent?number=19645# 
target name=*continium*

 antcall target=*create* /
 antcall target=*deploy* /
/target

am I missed something?

CVS connection unsuccessful while doing release:prepare (error: password is required)

I am using maven 2.0.4 and have been trying to do a release:prepare. I 
have attempted to work through a number of options but am having trouble 
connecting to my CVS repository for release:prepare (Note: scm:checkout 
works just fine - the settings are identical for connection and 
developerConnections). The data output from the log also seems to be all 
right. I have ensured that I do a cvs login, the .cvspass has the 
records for the password, and have attempted both with and without 
supplying one or both of -Dusername and -Dpassword with identical 
results. Identical results irrespective of whether I supply the -DdryRun 
parameter.The relevant part of the output with debug turned on follows. 
Please help if you can.


Thanks
Dhananjay
--
prompt mvn -X -up -Dusername=danny -Dpassword=my_password 
release:prepare -DdryRun=true


[DEBUG] 
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
org.apache.maven:maven-artifact-manager:jar:2.0 from the repository.
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0:runtime 
(selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
org.apache.maven:maven-artifact:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
org.apache.maven:maven-repository-metadata:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime 
(selected for runtime)
[DEBUG] 
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project: 
null:maven-scm-api:jar:1.0-alpha-2 from the repository.
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2:runtime 
(selected for runtime)

[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: plexus:plexus-root::1.0.3 for project: 
plexus:plexus-utils:jar:1.0.3 from the repository.

[DEBUG] plexus:plexus-utils:jar:1.0.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-managers::1.0-alpha-2 for project: 
null:maven-scm-manager-plexus:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project: 
null:maven-scm-managers:pom:1.0-alpha-2 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: plexus:plexus-containers::1.0 for 
project: plexus:plexus-container-default:jar:1.0-alpha-5 from the 
repository.
[DEBUG] Retrieving parent-POM: plexus:plexus-root::1.0 for project: 
plexus:plexus-containers:pom:1.0 from the repository.
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5:runtime 
(selected for runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-alpha-2 for project: 
null:maven-scm-provider-svn:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project: 
null:maven-scm-providers:pom:1.0-alpha-2 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2:runtime 
(selected for runtime)

[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
null:maven-project:jar:2.0 from the repository.
[DEBUG]   org.apache.maven:maven-project:jar:2.0:runtime (selected for 
runtime)
[DEBUG] 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
org.apache.maven:maven-model:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for 
runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: 
null:maven-profile:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for 
runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-alpha-2 for project: 
null:maven-scm-provider-cvs:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project: 
null:maven-scm-providers:pom:1.0-alpha-2 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-alpha-2:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM:

Re: Wagon-webdav distribution - where to put username/password


are you trying to deploy a snapshot? if so repository doesn't apply,
snapshotRepository does

Paste your pom else

On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:

I must be ignorant, I am following that example, have settings in
settings.xml, using wagon-webdav-1.0-beta-1-SNAPSHOT from Subversion
today (6/12/2006), and still unable to authenticate (with a known
username/password that is tested on the WebDAV site that works fine with
other tools, as well as manually with full PUT/MKCOL permissions).

Maven Debug Output:
=
[DEBUG] -- end configuration --
[INFO] deploy:deploy
WAGON_VERSION: 1.0-beta-1-SNAPSHOT
[DEBUG] not adding permissions to wagon connection
Jun 12, 2006 11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
processAuthenticationResponse
WARNING: No credentials available for the 'my webdav secure realm'
authentication realm at myserver
..
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: http://myserver/repo/myfile. Return code is: 401
Unauthorized
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java
:280)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(Defa
ultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defaul
tWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
tArtifactDeployer.java:77)
... 11 more
=

What else should I test? When authentication is disabled on the WebDAV
server, everything works fine. I tried changing the ID in settings.xml
to be 'my webdav secure realm', but that didn't work either.

Note above: [DEBUG] not adding permissions to wagon connection

-D


 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 12, 2006 8:36 AM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put
 username/password

 Yes,
 http://maven.apache.org/guides/mini/guide-deployment-security-
 settings.html

  On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
   Hey all,
   I'm trying to distribute artifacts to a webdav server, but I do
   not seem to know where to put the username/password.  When the
   webdav server (apache 2.2) is un-secured, it works fine.
  
   Configured Maven as follows:
  
   Pom.xml
   =
   distributionManagement
   repository
   idmy-secure-repo/id
   urldav:http://reposerver/myrepo/url
   ...
   ==
  
   Then tried settings.xml
   ==
   servers
   server
 idmy-secure-repo/id
 usernameuserthingy/username
   passwordpasswordthingy/password
   ..
   ==

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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: CVS connection unsuccessful while doing release:prepare (error: password is required)


You are using maven-release-plugin-2.0-beta-3, the current version is beta-4
which has lots of bug fixes since then

-Dan



On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:


I am using maven 2.0.4 and have been trying to do a release:prepare. I
have attempted to work through a number of options but am having trouble
connecting to my CVS repository for release:prepare (Note: scm:checkout
works just fine - the settings are identical for connection and
developerConnections). The data output from the log also seems to be all
right. I have ensured that I do a cvs login, the .cvspass has the
records for the password, and have attempted both with and without
supplying one or both of -Dusername and -Dpassword with identical
results. Identical results irrespective of whether I supply the -DdryRun
parameter.The relevant part of the output with debug turned on follows.
Please help if you can.

Thanks
Dhananjay

--
prompt mvn -X -up -Dusername=danny -Dpassword=my_password
release:prepare -DdryRun=true

[DEBUG]

org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
org.apache.maven:maven-artifact-manager:jar:2.0 from the repository.
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0:runtime
(selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
org.apache.maven:maven-artifact:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
org.apache.maven:maven-repository-metadata:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
(selected for runtime)
[DEBUG]
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project:
null:maven-scm-api:jar:1.0-alpha-2 from the repository.
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2:runtime
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: plexus:plexus-root::1.0.3 for project:
plexus:plexus-utils:jar:1.0.3 from the repository.
[DEBUG] plexus:plexus-utils:jar:1.0.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-managers::1.0-alpha-2 for project:
null:maven-scm-manager-plexus:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project:
null:maven-scm-managers:pom:1.0-alpha-2 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM: plexus:plexus-containers::1.0 for
project: plexus:plexus-container-default:jar:1.0-alpha-5 from the
repository.
[DEBUG] Retrieving parent-POM: plexus:plexus-root::1.0 for project:
plexus:plexus-containers:pom:1.0 from the repository.
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5:runtime
(selected for runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-alpha-2 for project:
null:maven-scm-provider-svn:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project:
null:maven-scm-providers:pom:1.0-alpha-2 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2:runtime
(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
null:maven-project:jar:2.0 from the repository.
[DEBUG]   org.apache.maven:maven-project:jar:2.0:runtime (selected for
runtime)
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
org.apache.maven:maven-model:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
null:maven-profile:jar:2.0 from the repository.
[DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-alpha-2 for project:
null:maven-scm-provider-cvs:jar:1.0-alpha-2 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-alpha-2 for project:
null:maven-scm-providers:pom:1.0-alpha-2 from the repository.
[DEBUG]

[M2] Struts and XDoclet

2006-06-12 Thread Rémy Sanlaville


Hi,

I try to use XDoclet with Maven 2 in order to generate Struts (v1.2.9)
descriptors (struts-config.xml and validation.xml).
All seems to be OK, but in the struts-config.xml file the form Bean section
is empty !

 !-- == Form Bean Definitions ===
--
 form-beans

   !--
If you have non XDoclet forms, define them in a file called
struts-forms.xml and
place it in your merge directory.
   --
 /form-beans


If I try in the same project with ANT, I have no trouble

!-- == Form Bean Definitions ===
--
 form-beans

   form-bean
 name=BookSearchForm
 type=test.struts.model.form.BookSearchForm
   /

   !--
If you have non XDoclet forms, define them in a file called
struts-forms.xml and
place it in your merge directory.
   --
 /form-beans

Do you have any idea ?

Rémy


My pom.xml :


?xml version= 1.0?project
 modelVersion4.0.0/modelVersion
 groupIdtest/groupId
 artifactIdlibrary/artifactId
 nameProject for managing a library/name
 version1.0-SNAPSHOT/version
 packagingwar/packaging
 dependencies
   dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version3.8.1/version
 scopetest/scope
   /dependency
   dependency
 groupIdlog4j/groupId
 artifactIdlog4j/artifactId
 version1.2.13/version
 optionaltrue/optional
   /dependency
   dependency
 groupIdstruts/groupId
 artifactIdstruts/artifactId
 version1.2.9/version
   /dependency
   dependency
 groupIdorg.apache.geronimo.specs/groupId
 artifactIdgeronimo-j2ee_1.4_spec/artifactId
 version1.0/version
 scopeprovided/scope
   /dependency
 /dependencies

 build
plugins
  plugin
groupId org.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId

dependencies
dependency
 groupId javax.servlet/groupId
 artifactIdservlet-api/artifactId
 version2.4/version
 scopeprovided/scope
/dependency
/dependencies

executions
  execution
phasegenerate-sources/phase
goals
  goalxdoclet/goal
/goals
configuration
  tasks
webdoclet destdir=${project.build.directory}/${
project.build.finalName}/WEB-INF
excludedtags= @version,@author
 verbose= true
  fileset dir=${project.build.sourceDirectory}
   include name=**/* Form.java /
   include name=**/*Action.java /
  /fileset
   strutsconfigxml
   mergeDir=
${basedir}/src/main/webapp/WEB-INF/merge
   validatexml= true
   version= 1.2/
   strutsvalidationxml
   validatexml= true
   version= 1.1.3/
/webdoclet
  /tasks
/configuration
  /execution
/executions
  /plugin
/plugins
  /build
/project

RE: [M2] Struts and XDoclet

2006-06-12 Thread Mick Knutson


Are the beans getting generated by xdoclet?


---
Thank You
Mick Knutson

BASE logic, inc.
(415) 648-1804 (San Francisco, CA)
http://www.BASELogic.com

http://www.djmick.com
---





From: Rémy Sanlaville [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
To: Maven Users List users@maven.apache.org
Subject: [M2] Struts and XDoclet
Date: Mon, 12 Jun 2006 19:06:52 +0200

Hi,

I try to use XDoclet with Maven 2 in order to generate Struts (v1.2.9)
descriptors (struts-config.xml and validation.xml).
All seems to be OK, but in the struts-config.xml file the form Bean section
is empty !

 !-- == Form Bean Definitions ===
--
 form-beans

   !--
If you have non XDoclet forms, define them in a file called
struts-forms.xml and
place it in your merge directory.
   --
 /form-beans


If I try in the same project with ANT, I have no trouble

!-- == Form Bean Definitions ===
--
 form-beans

   form-bean
 name=BookSearchForm
 type=test.struts.model.form.BookSearchForm
   /

   !--
If you have non XDoclet forms, define them in a file called
struts-forms.xml and
place it in your merge directory.
   --
 /form-beans

Do you have any idea ?

Rémy


My pom.xml :


?xml version= 1.0?project
 modelVersion4.0.0/modelVersion
 groupIdtest/groupId
 artifactIdlibrary/artifactId
 nameProject for managing a library/name
 version1.0-SNAPSHOT/version
 packagingwar/packaging
 dependencies
   dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version3.8.1/version
 scopetest/scope
   /dependency
   dependency
 groupIdlog4j/groupId
 artifactIdlog4j/artifactId
 version1.2.13/version
 optionaltrue/optional
   /dependency
   dependency
 groupIdstruts/groupId
 artifactIdstruts/artifactId
 version1.2.9/version
   /dependency
   dependency
 groupIdorg.apache.geronimo.specs/groupId
 artifactIdgeronimo-j2ee_1.4_spec/artifactId
 version1.0/version
 scopeprovided/scope
   /dependency
 /dependencies

 build
plugins
  plugin
groupId org.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId

dependencies
dependency
 groupId javax.servlet/groupId
 artifactIdservlet-api/artifactId
 version2.4/version
 scopeprovided/scope
/dependency
/dependencies

executions
  execution
phasegenerate-sources/phase
goals
  goalxdoclet/goal
/goals
configuration
  tasks
webdoclet destdir=${project.build.directory}/${
project.build.finalName}/WEB-INF
excludedtags= @version,@author
 verbose= true
  fileset dir=${project.build.sourceDirectory}
   include name=**/* Form.java /
   include name=**/*Action.java /
  /fileset
   strutsconfigxml
   mergeDir=
${basedir}/src/main/webapp/WEB-INF/merge
   validatexml= true
   version= 1.2/
   strutsvalidationxml
   validatexml= true
   version= 1.1.3/
/webdoclet
  /tasks
/configuration
  /execution
/executions
  /plugin
/plugins
  /build
/project




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

Re: [m2] Cobertura plugin generates empty report

2006-06-12 Thread David Hay

I finally got the report working.  It turns out that it has to do with
the forkMode defined in the maven-surefire-plugin configuration.  If I
have it set to 'never', I get the problem I was seeing earlier.  If I
set it back to 'once', the report generates correctly.

David



On 6/9/06 Doug Douglass wrote:

David,

We've had cobertura reporting working for quite some time. My pom is very
similar except we don't have the phase element.

Note that we're still using version 2.0-SNAPSHOT. Maybe that's a clue?

Doug

On 6/9/06, David Hay [EMAIL PROTECTED] wrote:
Hello,

I've been trying to get the cobertura plugin running on our project, but
I'm having the same problems Daun DeFrance was having (March 28:
Continued Cobertura Plugin Issues).  That is, if I run the site goal
after the clean goal, I end up with a report that shows 0% test
coverage for every class.  If I run the site again (without running
clean again) then I get the coverage information that I would expect.

My pluginManagement section contains this:

plugin
artifactIdcobertura-maven-plugin/artifactId
version2.0/version
/plugin

In the build section I have this:

plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
executions
execution
phaseclean/phase
goals
goalclean/goal
/goals
/execution
/executions
/plugin

And my reporting section looks like this:

reporting
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
/plugin
/plugins
/reporting

Any suggestions on what might be going on?  Is this a known issue with
the cobertura-maven-plugin?  Or do I have something misconfigured?

Thanks!
David

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

How do I specify checkout directory for release:prepare ?

My pom.xml has been configured to checkout the project 
${basedir}/target/checkout/source  (I have configured the 
checkoutDirectory for maven-scm-plugin). However release:prepare 
continuously fails since the cvs update command does not contain the 
directory where the project is checked out. The log shows the following 
command being executed  :


cvs -z3 -f -d cvs_root -n -q update -d

The command fails since there is no parameter after the -d above to 
indicate the directory (it needs to be the same as the source directory 
which is used by scm:checkout). I tried passing command line parameters 
(-D) and by using prepareVerifyArgs. However I am unable to pass the 
directory name.


How do I pass the parameter to indicate the directory where the code is 
checked out to maven-release-plugin ?


Dhananjay



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

RE: Wagon-webdav distribution - where to put username/password

I'm not sure how snapshotRepository impacts no credentials available
-- but it is not a snapshot, version16/version  from the POM,
packaging is packagingpom/packaging as this would be the simplest
use-case.  Again, based on the Debug:

[DEBUG] not adding permissions to wagon connection 

Not sure what to do

-D

 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED] 
 Sent: Monday, June 12, 2006 12:18 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put 
 username/password
 
 are you trying to deploy a snapshot? if so repository 
 doesn't apply, snapshotRepository does
 
 Paste your pom else
 
 On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:
  I must be ignorant, I am following that example, have settings in 
  settings.xml, using wagon-webdav-1.0-beta-1-SNAPSHOT from 
 Subversion 
  today (6/12/2006), and still unable to authenticate (with a known 
  username/password that is tested on the WebDAV site that works fine 
  with other tools, as well as manually with full PUT/MKCOL 
 permissions).
 
  Maven Debug Output:
  =
  [DEBUG] -- end configuration --
  [INFO] deploy:deploy
  WAGON_VERSION: 1.0-beta-1-SNAPSHOT
  [DEBUG] not adding permissions to wagon connection Jun 12, 2006 
  11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
  processAuthenticationResponse
  WARNING: No credentials available for the 'my webdav secure realm'
  authentication realm at myserver
  ..
  Caused by: org.apache.maven.wagon.TransferFailedException: 
 Failed to 
  transfer file: http://myserver/repo/myfile. Return code is: 401 
  Unauthorized
  at
  
 org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.ja
  va
  :280)
  at
  
 org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(De
  fa
  ultWagonManager.java:180)
  at
  
 org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defa
  ul
  tWagonManager.java:109)
  at
  
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defa
  ul
  tArtifactDeployer.java:77)
  ... 11 more
  =
 
  What else should I test? When authentication is disabled on 
 the WebDAV 
  server, everything works fine. I tried changing the ID in 
 settings.xml 
  to be 'my webdav secure realm', but that didn't work either.
 
  Note above: [DEBUG] not adding permissions to wagon connection
 
  -D
 
 
   -Original Message-
   From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
   Sent: Monday, June 12, 2006 8:36 AM
   To: Maven Users List
   Subject: Re: Wagon-webdav distribution - where to put 
   username/password
  
   Yes,
   http://maven.apache.org/guides/mini/guide-deployment-security-
   settings.html
  
On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
 Hey all,
 I'm trying to distribute artifacts to a webdav 
 server, but I do 
 not seem to know where to put the username/password.  
 When the 
 webdav server (apache 2.2) is un-secured, it works fine.

 Configured Maven as follows:

 Pom.xml
 =
 distributionManagement
 repository
 idmy-secure-repo/id
 urldav:http://reposerver/myrepo/url
 ...
 ==

 Then tried settings.xml
 ==
 servers
 server
   idmy-secure-repo/id
   usernameuserthingy/username
 passwordpasswordthingy/password
 ..
 ==
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 --
 I could give you my word as a Spaniard.
 No good. I've known too many Spaniards.
  -- The Princess Bride
 

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

Seam with Maven2 WAS: + JBoss Embedded EJB3 and Surefire Plugin Maven 2 PROBLEM+

2006-06-12 Thread Steve Lewis


Marco Mistroni wrote:


i have anohter app (that uses seam) that has been tested using


Is that other app, that uses Seam also using Maven2 by any chance?

http://jira.jboss.com/jira/browse/JBSEAM-225

It looks like there will be no official Maven 2 jar for the ibiblio 
repository.


This is my first Maven2 project and I have been we are using Seam, and I 
could use a little help figuring out how to get the JBoss Application 
Server 4.0.4.GA jar into the classpath.


I can't readily create a repository proxy and can't just install it in 
my local repository (even if I could figure out the pom.xml) as we will 
have at least a half-dozen developers with no experience with Maven 
working on this project and that kind of thing will kill any 
organizational support for using Maven.


Does anyone have any recommendations?

--
SteveL

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

1.0.2-1.0.3 upgrade - JDODataStoreException: ...trying to shrink VARCHAR...ContinuumBuildExecutorE

2006-06-12 Thread Chris Wall

After upgrading from 1.0.2 to 1.0.3 (via
http://maven.apache.org/continuum/upgrade.html), we are experiencing the
stacktrace below.  Is this an outdated schema issue?
 
I saw two related responses in the archives (we don't know why and
nothing to do with Maven or Continuum) and a couple open bugs.  What
is the suggested workaround?
 
Could this be related?  Is it correct to overwrite 1.0.3 with 1.0.2?:
Replace Continuum 1.0.3's apps/continuum/database with Continuum
1.0.2's apps/continuum/database. 
 
Thanks!
 
-Chris
 
 
Stacktrace

javax.jdo.JDODataStoreException: Update request failed: UPDATE
BUILDRESULT SET ERROR=? WHERE ID=?
   at
org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:26
7)
   at
org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2200)
   at
org.jpox.store.StoreManager.update(StoreManager.java:786)
   at
org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4596)
   at
org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav
a:3167)
   at
org.jpox.AbstractPersistenceManager.markDirty(AbstractPersistenceManager
.java:3126)
   at
org.jpox.state.StateManagerImpl.postWriteField(StateManagerImpl.java:433
4)
   at
org.jpox.state.StateManagerImpl.makeDirty(StateManagerImpl.java:1050)
   at
org.jpox.state.AttachFieldManager.storeIntField(AttachFieldManager.java:
255)
   at
org.jpox.state.StateManagerImpl.providedIntField(StateManagerImpl.java:2
571)
   at
org.apache.maven.continuum.model.project.Project.jdoProvideField(Project
.java)
   at
org.apache.maven.continuum.model.project.Project.jdoProvideFields(Projec
t.java)
   at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2964
)
   at
org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java
:4028)
   at
org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3963)
   at
org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage
r.java:1336)
   at
org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersi
stenceManager.java:1109)
   at
org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceMa
nager.java:1201)
   at
org.apache.maven.continuum.store.JdoContinuumStore.updateBuildResult(Jdo
ContinuumStore.java:238)
   at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(
DefaultBuildController.java:324)
   at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec
uteTask(BuildProjectTaskExecutor.java:47)
   at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
orRunnable.run(ThreadedTaskQueueExecutor.java:103)
   at java.lang.Thread.run(Thread.java:595)
NestedThrowablesStackTrace:
ERROR 22001: A truncation error was encountered trying to shrink VARCHAR
'org.apache.maven.continuum.execution.ContinuumBuildExecutorE' to
length 8192.
   at
org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
   at
org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source)
   at
org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source)
   at
org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source)
   at
org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source)
   at
org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknow
n Source)
   at
org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unkn
own Source)
   at
org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unkno
wn Source)
   at
org.apache.derby.impl.sql.execute.UpdateResultSet.collectAffectedRows(Un
known Source)
   at
org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
   at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown
Source)
   at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
Source)
   at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unkno
wn Source)
   at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown
Source)
   at
org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78)
   at
org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25
3)
   at
org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2200)
   at
org.jpox.store.StoreManager.update(StoreManager.java:786)
   at
org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4596)
   at
org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav
a:3167)
   at

Re: How do I specify checkout directory for release:prepare ?

release:prepare is attempting an update. My assumption is that the same 
is for ensuring that the source has not changed and thus it will need 
need to know exactly where the source has been checked out earlier. Not 
sure if I have made a mistake in understanding the process. The log 
output is as follows. My assumption is that there would require to be a 
parameter I could pass to release:prepare which would be appended to the 
update command in the log below. Have I misunderstood the process ?


[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-check-modifications'
[INFO] Verifying that there are no local modifications...
[DEBUG] cvsRoot: [.. correct cvs root ..]
[DEBUG] passFile: [.. correct cvs password file ..]
[DEBUG] cvsroot [.. correct cvs root..] already exist in [.. correct cvs 
password file ..] SKIPPED.

[INFO] Executing: cvs -z3 -f -d [.. correct cvs root ..] -n -q update -d
[INFO] Working directory: [.. correct base directory ie. the one which 
contains pom.xml ..]
[INFO] 


[ERROR] BUILD FAILURE
[INFO] 


[INFO] Unable to check for local modifications
Provider message:
The cvs command failed.
Command output:
cvs update: in directory .:
cvs [update aborted]: there is no version here; run 'cvs checkout' first

[INFO] 


[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to check for local 
modifications

Provider message:
The cvs command failed.
Command output:
cvs update: in directory .:
cvs [update aborted]: there is no version here; run 'cvs checkout' first

dan tran wrote:
release-plugin does not use maven-scm-plugin, it, however, talks 
directory

to maven-scm-api layer.
So your maven-scm-plugin settings are ignored.  Also, the release:prepare
does not do any checkout.
release:perform does. You can change the checkout directory thru
release:perform's workingDirectory

http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html

-D

On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:


My pom.xml has been configured to checkout the project
${basedir}/target/checkout/source  (I have configured the
checkoutDirectory for maven-scm-plugin). However release:prepare
continuously fails since the cvs update command does not contain the
directory where the project is checked out. The log shows the following
command being executed  :

cvs -z3 -f -d cvs_root -n -q update -d

The command fails since there is no parameter after the -d above to
indicate the directory (it needs to be the same as the source directory
which is used by scm:checkout). I tried passing command line parameters
(-D) and by using prepareVerifyArgs. However I am unable to pass the
directory name.

How do I pass the parameter to indicate the directory where the code is
checked out to maven-release-plugin ?

Dhananjay



-
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: How do I specify checkout directory for release:prepare ?


What version of release-plugin do yo use?

try to remove release.properties in your root dir and run mvn
release:prepare -DdryDrun -X

-D


On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:


release:prepare is attempting an update. My assumption is that the same
is for ensuring that the source has not changed and thus it will need
need to know exactly where the source has been checked out earlier. Not
sure if I have made a mistake in understanding the process. The log
output is as follows. My assumption is that there would require to be a
parameter I could pass to release:prepare which would be appended to the
update command in the log below. Have I misunderstood the process ?

[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-check-modifications'
[INFO] Verifying that there are no local modifications...
[DEBUG] cvsRoot: [.. correct cvs root ..]
[DEBUG] passFile: [.. correct cvs password file ..]
[DEBUG] cvsroot [.. correct cvs root..] already exist in [.. correct cvs
password file ..] SKIPPED.
[INFO] Executing: cvs -z3 -f -d [.. correct cvs root ..] -n -q update -d
[INFO] Working directory: [.. correct base directory ie. the one which
contains pom.xml ..]
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to check for local modifications
Provider message:
The cvs command failed.
Command output:
cvs update: in directory .:
cvs [update aborted]: there is no version here; run 'cvs checkout' first

[INFO]

[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to check for local
modifications
Provider message:
The cvs command failed.
Command output:
cvs update: in directory .:
cvs [update aborted]: there is no version here; run 'cvs checkout' first

dan tran wrote:
 release-plugin does not use maven-scm-plugin, it, however, talks
 directory
 to maven-scm-api layer.
 So your maven-scm-plugin settings are ignored.  Also, the
release:prepare
 does not do any checkout.
 release:perform does. You can change the checkout directory thru
 release:perform's workingDirectory

 http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html

 -D

 On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:

 My pom.xml has been configured to checkout the project
 ${basedir}/target/checkout/source  (I have configured the
 checkoutDirectory for maven-scm-plugin). However release:prepare
 continuously fails since the cvs update command does not contain the
 directory where the project is checked out. The log shows the following
 command being executed  :

 cvs -z3 -f -d cvs_root -n -q update -d

 The command fails since there is no parameter after the -d above to
 indicate the directory (it needs to be the same as the source directory
 which is used by scm:checkout). I tried passing command line parameters
 (-D) and by using prepareVerifyArgs. However I am unable to pass the
 directory name.

 How do I pass the parameter to indicate the directory where the code is
 checked out to maven-release-plugin ?

 Dhananjay



 -
 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: Wagon-webdav distribution - where to put username/password


well, if you can provide a use case then we'll take a look. With this
info I can't go further

On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:

I'm not sure how snapshotRepository impacts no credentials available
-- but it is not a snapshot, version16/version  from the POM,
packaging is packagingpom/packaging as this would be the simplest
use-case.  Again, based on the Debug:

[DEBUG] not adding permissions to wagon connection

Not sure what to do

-D

 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 12, 2006 12:18 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put
 username/password

 are you trying to deploy a snapshot? if so repository
 doesn't apply, snapshotRepository does

 Paste your pom else

 On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:
  I must be ignorant, I am following that example, have settings in
  settings.xml, using wagon-webdav-1.0-beta-1-SNAPSHOT from
 Subversion
  today (6/12/2006), and still unable to authenticate (with a known
  username/password that is tested on the WebDAV site that works fine
  with other tools, as well as manually with full PUT/MKCOL
 permissions).
 
  Maven Debug Output:
  =
  [DEBUG] -- end configuration --
  [INFO] deploy:deploy
  WAGON_VERSION: 1.0-beta-1-SNAPSHOT
  [DEBUG] not adding permissions to wagon connection Jun 12, 2006
  11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
  processAuthenticationResponse
  WARNING: No credentials available for the 'my webdav secure realm'
  authentication realm at myserver
  ..
  Caused by: org.apache.maven.wagon.TransferFailedException:
 Failed to
  transfer file: http://myserver/repo/myfile. Return code is: 401
  Unauthorized
  at
 
 org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.ja
  va
  :280)
  at
 
 org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(De
  fa
  ultWagonManager.java:180)
  at
 
 org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defa
  ul
  tWagonManager.java:109)
  at
 
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defa
  ul
  tArtifactDeployer.java:77)
  ... 11 more
  =
 
  What else should I test? When authentication is disabled on
 the WebDAV
  server, everything works fine. I tried changing the ID in
 settings.xml
  to be 'my webdav secure realm', but that didn't work either.
 
  Note above: [DEBUG] not adding permissions to wagon connection
 
  -D
 
 
   -Original Message-
   From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
   Sent: Monday, June 12, 2006 8:36 AM
   To: Maven Users List
   Subject: Re: Wagon-webdav distribution - where to put
   username/password
  
   Yes,
   http://maven.apache.org/guides/mini/guide-deployment-security-
   settings.html
  
On 6/7/06, Darren Hartford [EMAIL PROTECTED] wrote:
 Hey all,
 I'm trying to distribute artifacts to a webdav
 server, but I do
 not seem to know where to put the username/password.
 When the
 webdav server (apache 2.2) is un-secured, it works fine.

 Configured Maven as follows:

 Pom.xml
 =
 distributionManagement
 repository
 idmy-secure-repo/id
 urldav:http://reposerver/myrepo/url
 ...
 ==

 Then tried settings.xml
 ==
 servers
 server
   idmy-secure-repo/id
   usernameuserthingy/username
 passwordpasswordthingy/password
 ..
 ==
 
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 I could give you my word as a Spaniard.
 No good. I've known too many Spaniards.
  -- The Princess Bride


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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: How do I specify checkout directory for release:prepare ?

I am using release plugin 2.0-beta-4. The output of the command (after 
deleting release.properties) follows :

--
[DEBUG] Using defaults for missing POM 
javax.xml.bind:jaxb-api:pom:1.0.1:compile

[DEBUG]   javax.xml.bind:jaxb-api:jar:1.0.1:compile (selected for compile)
[DEBUG] 
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-4:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers-cvs::1.0-beta-3 for project: 
null:maven-scm-provider-cvsexe:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project: 
null:maven-scm-providers-cvs:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-beta-3 for project: 
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for 
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: 
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-cvsexe:jar:1.0-beta-3:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.codehaus.plexus:plexus::1.0.4 for 
project: null:plexus-utils:jar:1.1 from the repository.
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-beta-3 for project: 
null:maven-scm-api:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for 
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: 
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0-beta-3:runtime 
(selected for runtime)

[DEBUG]   junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers-cvs::1.0-beta-3 for project: 
null:maven-scm-provider-cvs-commons:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project: 
null:maven-scm-providers-cvs:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-beta-3 for project: 
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for 
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: 
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.0-beta-3:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project: 
null:maven-scm-provider-perforce:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-beta-3 for project: 
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for 
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: 
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-3:runtime 
(selected for runtime)

[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project: 
null:maven-scm-provider-starteam:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm::1.0-beta-3 for project: 
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for 
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: 
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-3:runtime 
(selected for runtime)
[DEBUG]   
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:runtime 
(selected for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected 
for runtime)

[DEBUG]   jaxen:jaxen:jar:1.1-beta-8:runtime (selected for runtime)
[DEBUG] jaxen:jaxen:jar:1.0-FCS:runtime (removed - causes a cycle in 
the graph)

[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG]   jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:

Re: How do I specify checkout directory for release:prepare ?


cvs provider uses cvs update to check for your local modification(s),
however it fails.

You will need to trouble shoot they that command fails thou

-D


On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:


I am using release plugin 2.0-beta-4. The output of the command (after
deleting release.properties) follows :

--
[DEBUG] Using defaults for missing POM
javax.xml.bind:jaxb-api:pom:1.0.1:compile
[DEBUG]   javax.xml.bind:jaxb-api:jar:1.0.1:compile (selected for compile)
[DEBUG]

org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-4:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers-cvs::1.0-beta-3 for project:
null:maven-scm-provider-cvsexe:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project:
null:maven-scm-providers-cvs:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-beta-3 for project:
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-provider-cvsexe:jar:1.0-beta-3:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.codehaus.plexus:plexus::1.0.4 for
project: null:plexus-utils:jar:1.1 from the repository.
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-beta-3 for project:
null:maven-scm-api:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0-beta-3:runtime
(selected for runtime)
[DEBUG]   junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers-cvs::1.0-beta-3 for project:
null:maven-scm-provider-cvs-commons:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project:
null:maven-scm-providers-cvs:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-beta-3 for project:
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.0-beta-3:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project:
null:maven-scm-provider-perforce:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-beta-3 for project:
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-3:runtime
(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm-providers::1.0-beta-3 for project:
null:maven-scm-provider-starteam:jar:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM:
org.apache.maven.scm:maven-scm::1.0-beta-3 for project:
null:maven-scm-providers:pom:1.0-beta-3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.scm:maven-scm:pom:1.0-beta-3 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
[DEBUG]
org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-3:runtime
(selected for runtime)
[DEBUG]
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:runtime
(selected for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected
for runtime)
[DEBUG]   jaxen:jaxen:jar:1.1-beta-8:runtime (selected for runtime)
[DEBUG] jaxen:jaxen:jar:1.0-FCS:runtime (removed - causes a cycle in
the graph)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG]

RE: Wagon-webdav distribution - where to put username/password

I'm surprised this hasn't been tested already.  Again, from using Maven
DEBUG mode, it is NOT using authentication.

[DEBUG] not adding permissions to wagon connection


Use case:

Httpd.conf
===
# apache 2.2 w/ webdav
# manually w/ authentication this works fine.
Location /repo
Dav On
LimitExcept GET HEAD OPTIONS
# put your security reqs here
# known, already tested security works
/LimitExcept
/Location
===

Pom.xml
=
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
  parent
artifactIdwagon-providers/artifactId
groupIdorg.apache.maven.wagon/groupId
version1.0-beta-1-SNAPSHOT/version
  /parent
  modelVersion4.0.0/modelVersion
  artifactIdwagon-webdav-testpom/artifactId
  version16/version
  packagingpom/packaging
  nameMaven Wagon WebDav test/name
  description
  Test pom for authentication-required webdav
  /description
  
  distributionManagement
repository
idwebdav-secure-repo/id
urldav:http://myserver/repo/url
/repository
 /distributionManagement
/project
=

Settings.xml
==
?xml version=1.0 encoding=UTF-8?
settings
  servers
  !--  secured repo --
server
  idwebdav-secure-repo/id
  usernameusernamethingy/username
passwordpasswordthingy/password
/server
  /servers
/settings
=

Maven Debug Output:
=
[DEBUG] -- end configuration --
[INFO] deploy:deploy
WAGON_VERSION: 1.0-beta-1-SNAPSHOT
[DEBUG] not adding permissions to wagon connection 
Jun 12, 2006 11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
processAuthenticationResponse
WARNING: No credentials available for the 'my webdav secure realm'
authentication realm at myserver ..
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: http://myserver/repo/myfile. Return code is: 401
Unauthorized
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java
:280)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(Defa
ultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defaul
tWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
tArtifactDeployer.java:77)
... 11 more
=



 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED] 
 Sent: Monday, June 12, 2006 3:18 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put 
 username/password
 
 well, if you can provide a use case then we'll take a look. 
 With this info I can't go further
 

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

RE: Seam with Maven2 WAS: + JBoss Embedded EJB3 and Surefire Plugin Maven 2 PROBLEM+

2006-06-12 Thread Mike Perham

Any jar can be uploaded to ibiblio, you just need to create an upload
bundle for it and enter a MAVENUPLOAD issue.

http://maven.apache.org/guides/mini/guide-ibiblio-upload.html 
http://jira.codehaus.org/browse/MAVENUPLOAD

 -Original Message-
 From: Steve Lewis [mailto:[EMAIL PROTECTED] 
 Sent: Monday, June 12, 2006 1:53 PM
 To: Maven Users List
 Subject: Seam with Maven2 WAS: + JBoss Embedded EJB3 and 
 Surefire Plugin Maven 2 PROBLEM+

 Marco Mistroni wrote:

  i have anohter app (that uses seam) that has been tested using

 Is that other app, that uses Seam also using Maven2 by any chance?

 http://jira.jboss.com/jira/browse/JBSEAM-225

 It looks like there will be no official Maven 2 jar for the 
 ibiblio repository.

 This is my first Maven2 project and I have been we are using 
 Seam, and I could use a little help figuring out how to get 
 the JBoss Application Server 4.0.4.GA jar into the classpath.

 I can't readily create a repository proxy and can't just 
 install it in my local repository (even if I could figure out 
 the pom.xml) as we will have at least a half-dozen developers 
 with no experience with Maven working on this project and 
 that kind of thing will kill any organizational support for 
 using Maven.

 Does anyone have any recommendations?

 --
 SteveL

 -
 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: Wagon-webdav distribution - where to put username/password


It's not possible that this works for you at all.

Check an example here http://docs.codehaus.org/display/HAUSMATES/Maven+Guide

On 6/12/06, Darren Hartford [EMAIL PROTECTED] wrote:

I'm surprised this hasn't been tested already.  Again, from using Maven
DEBUG mode, it is NOT using authentication.

[DEBUG] not adding permissions to wagon connection


Use case:

Httpd.conf
===
# apache 2.2 w/ webdav
# manually w/ authentication this works fine.
Location /repo
Dav On
LimitExcept GET HEAD OPTIONS
# put your security reqs here
# known, already tested security works
/LimitExcept
/Location
===

Pom.xml
=
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
  parent
artifactIdwagon-providers/artifactId
groupIdorg.apache.maven.wagon/groupId
version1.0-beta-1-SNAPSHOT/version
  /parent
  modelVersion4.0.0/modelVersion
  artifactIdwagon-webdav-testpom/artifactId
  version16/version
  packagingpom/packaging
  nameMaven Wagon WebDav test/name
  description
  Test pom for authentication-required webdav
  /description

  distributionManagement
repository
idwebdav-secure-repo/id
urldav:http://myserver/repo/url
/repository
 /distributionManagement
/project
=

Settings.xml
==
?xml version=1.0 encoding=UTF-8?
settings
  servers
  !--  secured repo --
server
  idwebdav-secure-repo/id
  usernameusernamethingy/username
passwordpasswordthingy/password
/server
  /servers
/settings
=

Maven Debug Output:
=
[DEBUG] -- end configuration --
[INFO] deploy:deploy
WAGON_VERSION: 1.0-beta-1-SNAPSHOT
[DEBUG] not adding permissions to wagon connection
Jun 12, 2006 11:41:14 AM org.apache.commons.httpclient.HttpMethodBase
processAuthenticationResponse
WARNING: No credentials available for the 'my webdav secure realm'
authentication realm at myserver ..
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: http://myserver/repo/myfile. Return code is: 401
Unauthorized
at
org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java
:280)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(Defa
ultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defaul
tWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
tArtifactDeployer.java:77)
... 11 more
=



 -Original Message-
 From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 12, 2006 3:18 PM
 To: Maven Users List
 Subject: Re: Wagon-webdav distribution - where to put
 username/password

 well, if you can provide a use case then we'll take a look.
 With this info I can't go further





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Parent vs. Multi Project super pom


Hi all,

this is kind of a best-practise-question about your habbits of using
the concepts of multi-project-super-pom.

First of all, are there distinctive terms commonly agreed upon for
each of those concepts?

Second, those two ways of using POMs appear to me to be orthogonal to
each other, really. Parent POMs are used to define common
characterisitics for a group of projects. Multi Project POMs on the
other hand aggregate modules belonging to a greater project. I usually
have the habbit of defining two diffent poms for multiproject
situations. e.g.:

/multiproject-pom X
-parent-pom Y
-module A / pom A (parent pom: Y)
-module B / pom B (parent pom: Y)

In most examples found though (e.g. in maven's own sources themselfs)
typically multi project poms at the same time are used as parent poms
for those modules they aggregated.

So, what I can't get my head around yet is, is it just a matter of
habbit or taste to combine those two usages in just one POM? or am I
really missing something important here, if I define two distinctive
POMs the way described above.

I'm thinking about this for quite a while now and any clarification
would be much appreciated.

Stefan

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

maven-proxy problem - NTLM

2006-06-12 Thread Umberto Dissenha Junior


Hi,

The maven-proxy console report the following error while maven start
download from central repository:

---
2006-06-12 17:20:13,189 [WARN ] commons.httpclient.HttpMethodBase  -
Credentials
cannot be used for NTLM authentication:
org.apache.commons.httpclient.UsernameP
asswordCredentials
2006-06-12 17:20:13,189 [INFO ] proxy.config.HttpRepoConfiguration  -
Repo[dist-
codehaus-org]: Unable to find
http://dist.codehaus.org/commons-collections/commo
ns-collections/2.1/commons-collections-2.1.jar because of [407] = Proxy
Authenti
cation Required ( The ISA Server requires authorization to fulfill the
request.
Access to the Web Proxy service is denied.  )
2006-06-12 17:20:13,189 [INFO ] components.impl.DefaultSnapshotCache  -
Adding /
commons-collections/commons-collections/2.1/commons-collections-2.1.jar to
snaps
hot cache
---

My maven-proxy.properties:

proxy.one.host=host
proxy.one.port=8080
proxy.one.username=user
proxy.one.password=pass

Anyone knows what happend???

Regards

Umberto

Status of maven-changes-plugin

2006-06-12 Thread Jochen Wiedmann


Hi,

what is the status of the maven-changes-plugin? (See

http://maven.apache.org/plugins/maven-changes-plugin/howto.html

I can't get it working, which isn't too surprising, as the module is neither
ob ibiblio, nor in the snapshot repository, nor in the SVN. Or did I miss
something?

Thanks,

Jochen



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

RE: integration builds and version numbers

2006-06-12 Thread EJ Ciramella

Someone must be using CC + M2, no? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 12, 2006 8:01 AM
To: Maven Users List
Subject: integration builds and version numbers

How are people updating their pom.xml files with version numbers from
say cruisecontrol?

We have two types of codelines (in perforce) here, project and release
lines.  Everything starts out life as a project then over time one (or
more) projects can be integrated to a release line.

I'm curious, we're forcefully editing (with the ant replace task) some
templated version.html files to reflect what version was built.  Do I
need to be doing this to the pom.xml files also?

When something is getting built from a project branch, the build number
looks like this:

X.projectbranchname.buildnumber

So:

8.P01.1

In the maven world, all the project branches would look like this:

versionX.X-SNAPSHOT/version

So in the above case - 

version8.0-P01-SNAPSHOT/version

And when that goes to release

version8.0.X/version

Where X is a build number.

This has a problem though - I'll have to remember the dependency order
to build and make sure that module C gets built before B which is
built before A (or the replace at least happens in that order).

So what are people doing for this?  Manually updating before every
build?  I _really_ don't want to have to go back to that

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

Re: maven-proxy problem - NTLM

2006-06-12 Thread Wayne Fay


Your statement what happened would imply that this worked in the
past but does not any more... Is this the case, or are you configuring
this proxy for the first time?

Assuming this is your first attempt at configuring the proxy, please
first realize that Commons HttpClient (and thus, Maven) does not
support NTLM proxies. Unless something has changed recently, you will
not be able to use Maven2 (or Maven Proxy) through this NTLM web
proxy.

Wayne

On 6/12/06, Umberto Dissenha Junior [EMAIL PROTECTED] wrote:

Hi,

The maven-proxy console report the following error while maven start
download from central repository:

---
2006-06-12 17:20:13,189 [WARN ] commons.httpclient.HttpMethodBase  -
Credentials
 cannot be used for NTLM authentication:
org.apache.commons.httpclient.UsernameP
asswordCredentials
2006-06-12 17:20:13,189 [INFO ] proxy.config.HttpRepoConfiguration  -
Repo[dist-
codehaus-org]: Unable to find
http://dist.codehaus.org/commons-collections/commo
ns-collections/2.1/commons-collections-2.1.jar because of [407] = Proxy
Authenti
cation Required ( The ISA Server requires authorization to fulfill the
request.
Access to the Web Proxy service is denied.  )
2006-06-12 17:20:13,189 [INFO ] components.impl.DefaultSnapshotCache  -
Adding /
commons-collections/commons-collections/2.1/commons-collections-2.1.jar to
snaps
hot cache
---

My maven-proxy.properties:

proxy.one.host=host
proxy.one.port=8080
proxy.one.username=user
proxy.one.password=pass

Anyone knows what happend???

Regards

Umberto




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

Re: What does this mean?

2006-06-12 Thread Wayne Fay


For more info:
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html

This page might need to be updated, as Sun has been recently releasing
code under the CDDL which does allow redistribution. They apparently
intend to release all of J2EE (nee JEE) under an open license, and
rename it Java Open Enterprise, or something along those lines
(according to my coworker who recently attended Java One).

Wayne

On 6/12/06, Eric Redmond [EMAIL PROTECTED] wrote:

Correct. If a commonly required jar is not in ibiblio, its usually a
licensing issue.

On 6/12/06, Jeff Mutonho [EMAIL PROTECTED] wrote:

 Better Builds With Maven , page 83 ,second bulleted paragraph

 As you're compiling J2EE code you need to have the J2EE
 specifications JAR in the project's build classpath. This is achieved
 by specifying a dependency element on the J2EE JAR. You could instead
 specify a dependency on Sun's J2EE JAR. However, this JAR is not
 redistributable and as such cannot be found on ibiblio. Fortunately,
 the Geronimo project has made the J2EE JAR available under an Apache
 license and this JAR can be found on ibiblio.

 What does You could instead specify a dependency on Sun's J2EE JAR.
 However, this JAR is not redistributable and as such cannot be found
 on ibiblio  mean?Is this a consequence of Sun's licensing?

 --


 Jeff  Mutonho

 GoogleTalk : ejbengine
 Skype: ejbengine
 Registered Linux user number 366042

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

If you drill down in the Central (ibiblio) repo and the Snapshot repo,
you will find a number of Archetypes, including j2ee-simple, webapp,
portlet etc.
http://www.ibiblio.org/maven2/org/apache/maven/archetypes/

Give them all a try and see what kind of directories, poms, etc are
created by each one -- perhaps you will find what you were originally
looking for...

But manually creating directories and modifying poms is the way I
personally create most of my projects.

Wayne

On 6/10/06, Mike Lundin [EMAIL PROTECTED] wrote:

Ben,

That's the kind of feedback I was looking for, yes. For some reason, I had
it in my head that you shouldn't touch the directory structure once the
archetype did it's work, but as I think about it, the pom that both
archetypes create is almost the same. Thinking along those lines, adding
the directories manually begins to make sense.

Thanks much for your responses,
Mike

On 6/10/06, ben short [EMAIL PROTECTED] wrote:

Mike,

I have used maven for a couple of webapps, usally I use the webapp
archetype to generate the pom and initial structure then I create the
java directory manually. Once you have created them maven will compile
the jva source as normal, and the class files get moved to the correct
place in the produced war.

I dont know of a archtype that does this for you, but that dosent mean
there isn't one.

Also I have created a project that has a webapp module and a java
module. For this I used the quick start archetype to create the jar
module, and the webapp to create the webapp module. I then moved the
out directory's produced under a project directory and created the
project pom manually.

I hope this is of some help...

Ben

On 6/10/06, Mike Lundin [EMAIL PROTECTED] wrote:
Ben,

I was assuming that there was an archetype out there that would generate
that structure for me. Is that not the case?

Mike

On 6/9/06, ben short [EMAIL PROTECTED] wrote:

Mike,

You can just create the directorys you need from the link ..

http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

Or you can create a seperate project that has the java source and add
it as a dependacy of your webapp.

Ben

On 6/10/06, Mike Lundin [EMAIL PROTECTED] wrote:
I'm working on creating a new webapp project using maven and the
archetype:create with the maven-archetype-webapp archetype. I may
not
understand things correctly, but I don't see some directories that I
would
assume would be in there. There is nothing for Java src files or
anything
like that in there.

Should those be in there, or is the preferred method to created
multiple
maven projects and make them all dependencies on each other? I
tried
creating archetypes within archetypes (by changing package to pom),
but
that
seem to disregard the archetype I sent in and only ever used the
quickStart
archetype.

Any help on this would be greatly appreciated -- and feel free to
point
me
to a URL that has more information. I've looked through the
resources I
know and am not finding anything definitive.

Thanks much,
Mike

--
Mike Lundin

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

Re: Status of maven-changes-plugin

2006-06-12 Thread Dennis Lundberg


Jochen Wiedmann wrote:

Hi,

what is the status of the maven-changes-plugin? (See

http://maven.apache.org/plugins/maven-changes-plugin/howto.html

I can't get it working, which isn't too surprising, as the module is neither
ob ibiblio, nor in the snapshot repository, nor in the SVN. Or did I miss
something?

Thanks,

Jochen


The plugin recently moved from mojo.codehaus.org and is currently in the 
Maven sandbox:

http://svn.apache.org/viewvc/maven/sandbox/plugins/maven-changes-plugin/

--
Dennis Lundberg

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

Classloader problem with antrun with run from continuum

2006-06-12 Thread Gautham Pamu


Hi Everyone,

I am using antrun plugin to run ant task during generate-resources
phase. I was able to run the task
outside continuum but when I run from continuum. I am getting
classnotfound errors.. Is this bug in maven
or the plugin or continuum.

mvn version 2.0.3
continuum version 1.0.3
plugin version: antrun version 1.1

pom file details

 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-antrun-plugin/artifactId
   executions
 execution
   !-- idcompile/id --
   phasegenerate-resources/phase
   configuration
 tasks
   ant antfile=./src/build1.xml inheritRefs=true
 target name=main/
   /ant
 /tasks
   /configuration
   goals
 goalrun/goal
   /goals
 /execution
   /executions
   dependencies
 dependency
   groupIdorg.apache.ant/groupId
   artifactIdant-antlr/artifactId
   version1.6.5/version
 /dependency
 dependency
   groupIdorg.apache.ant/groupId
   artifactIdantlrall/artifactId
   version2.7.4/version
 /dependency

This is the output of mvn with -X option. when I run it outside
continuum, I clearly see the dependencies in
the artifacts list... from continuum I get following output.. you can
see from the artifacts list..that the dependencies
are missing..

[DEBUG] Found deletable paths: []
[DEBUG] com.sample:sample:jar:1.0 (selected for null)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' --
[DEBUG]   (f) artifacts = [ant:ant:jar:1.6.5:runtime,
ant:ant-launcher:jar:1.6.5:runtime,
org.apache.maven:maven-project:jar:2.0.1:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.1:runtime]
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (f) tasks =
[DEBUG] -- end configuration --
[INFO] [antrun:run]
[INFO] Executing tasks
[INFO] Executed tasks
[DEBUG] rpm-maven-plugin: resolved to version
1.0-alpha-2-20060116.043106-1 from repository Maven Snapshots
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::1 for
project: null:rpm-maven-plugin:maven-plugin:1.0-alpha-2-20060116.043106-1
from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::6 for project:
null:mojo-sandbox:pom:1 from the repository.
[DEBUG] rpm-maven-plugin: resolved to version
1.0-alpha-2-20060116.043106-1 from repository Maven Snapshots
[DEBUG] changelog-maven-plugin: resolved to version
2.0-beta-2-20060307.142230-7 from repository Maven Snapshots
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project:
null:changelog-maven-plugin:maven-plugin:2.0-beta-2-20060307.142230-7
from the repository.
[DEBUG] changelog-maven-plugin: resolved to version
2.0-beta-2-20060307.142230-7 from repository Maven Snapshots
[DEBUG] com.ibm.csdp.resources:csdp.resources:jar:1.0 (selected for null)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' --
[DEBUG]   (f) artifacts = [ant:ant:jar:1.6.5:runtime,
ant:ant-launcher:jar:1.6.5:runtime,
org.apache.maven:maven-project:jar:2.0.1:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.1:runtime]
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (f) tasks =
[DEBUG] -- end configuration --
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
[DEBUG] getProperty(ns=null, name=ant.executor.class, user=false)
[DEBUG] getProperty(ns=null, name=ant.file, user=false)
[INFO] ---



Embedded error: The following error occurred while executing this line:
/opt/continuum/apps/working-directory/2/com.sample/src/build1.xml:4:
taskdef class com.sample.SampleTask cannot be found
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
executing ant tasks
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

Re: Classpath in ant scripts in an Ant mojo

2006-06-12 Thread Gautham Pamu


Hi Margeret,

I am seeing similar problem but different scenario. I have added the
dependencies to antrun plugin, it runs the ant task  but I run the same goal
from continuum, it fails with classnot found error..I ran the goal with -X
option to see what jars are added to the classpath.. I don't see my
dependencies for the mojo when it run from continuum..

Did you come across this problem ?

Thanks
Gautham

On 5/24/06, Margaret Martin [EMAIL PROTECTED] wrote:


Willie,
I've found that if I make the task's jars dependencies on the antrun
plugin, then the taskdefs resolve just fine.

Hope this helps -
-margaret

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Willie
Vu
Sent: Wednesday, May 24, 2006 3:02 AM
To: users@maven.apache.org
Subject: Classpath in ant scripts in an Ant mojo

I'm using Maven 2.0.4.  I am developing a plugin using Ant script.  A
task is declared using taskdef.  The task class is contained in one
of the artifacts of the pom.xml of the project that uses this Ant mojo
plugin.  An error occurred that the task class is not found.  It seems
like Maven doesn't resolve and pass dependency classpath to the Ant
script.  Any idea?

--
Willie Vu

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





--
-Gautham Pamu

antrun classpaths

2006-06-12 Thread Lee Meador


I went to here to see how to let ant get to some maven classpaths:

http://maven.apache.org/plugins/maven-antrun-plugin/classpaths.html

I have a build.xml file that I run with this in my pom:

  build
   plugins
   plugin
   artifactIdmaven-antrun-plugin/artifactId
   executions
   execution
   phasegenerate-sources/phase
   goals
   goalrun/goal
   /goals
   configuration
   tasks
   ant inheritRefs=true
target=axisWsdl2Java antfile=build.xml dir=. /
   /tasks
   sourceRoot${project.build.directory
}/generated-sources/java/sourceRoot
   /configuration
   /execution
   /executions
   /plugin
   /plugins
   /build

But it complains that:

[ERROR] BUILD ERROR
[INFO]

[INFO] Error executing ant tasks

Embedded error: The following error occurred while executing this line:
[path here]\build.xml:31: Reference maven.runtime.classpath not

Any ideas? Is the doc page up to date?

Thanks.

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

[M1] Some new pages on the web site.

2006-06-12 Thread Arnaud HERITIER


Hi all,

 Since some weeks you can find a new page [1] with the list of commands to
upgrade your plugins (be careful that some plugins aren't compatible with
maven 1.0.x).
 You can also find a new feed in the page [2] to be informed about new
releases of m1 plugins. This feed is available in the current snapshot of
the maven-multichanges-plugin that you can test with :

maven plugin:download -DgroupId=maven
-DartifactId=maven-multichanges-plugin -Dversion=1.3-SNAPSHOT
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/

 Cheers,

Arnaud

[1] http://maven.apache.org/maven-1.x/plugins/bundled/downloadPlugins.html
[2]
http://maven.apache.org/maven-1.x/plugins/bundled/multichanges-report.html

Re: [M2] Struts and XDoclet

On Mon, 12 Jun 2006, [ISO-8859-1] R�my Sanlaville wrote:

I see a lot of spaces in the POM, especially

includes=**/* Form.java

This might prevent the Form files from being detected.

-- Kenney

 Hi,

 I try to use XDoclet with Maven 2 in order to generate Struts (v1.2.9)
 descriptors (struts-config.xml and validation.xml).
 All seems to be OK, but in the struts-config.xml file the form Bean section
 is empty !

   !-- == Form Bean Definitions ===
 --
   form-beans

 !--
  If you have non XDoclet forms, define them in a file called
 struts-forms.xml and
  place it in your merge directory.
 --
   /form-beans


 If I try in the same project with ANT, I have no trouble

  !-- == Form Bean Definitions ===
 --
   form-beans

 form-bean
   name=BookSearchForm
   type=test.struts.model.form.BookSearchForm
 /

 !--
  If you have non XDoclet forms, define them in a file called
 struts-forms.xml and
  place it in your merge directory.
 --
   /form-beans

 Do you have any idea ?

 R�my


 My pom.xml :
 

 ?xml version= 1.0?project
   modelVersion4.0.0/modelVersion
   groupIdtest/groupId
   artifactIdlibrary/artifactId
   nameProject for managing a library/name
   version1.0-SNAPSHOT/version
   packagingwar/packaging
   dependencies
 dependency
   groupIdjunit/groupId
   artifactIdjunit/artifactId
   version3.8.1/version
   scopetest/scope
 /dependency
 dependency
   groupIdlog4j/groupId
   artifactIdlog4j/artifactId
   version1.2.13/version
   optionaltrue/optional
 /dependency
 dependency
   groupIdstruts/groupId
   artifactIdstruts/artifactId
   version1.2.9/version
 /dependency
 dependency
   groupIdorg.apache.geronimo.specs/groupId
   artifactIdgeronimo-j2ee_1.4_spec/artifactId
   version1.0/version
   scopeprovided/scope
 /dependency
   /dependencies

   build
  plugins
plugin
  groupId org.codehaus.mojo/groupId
  artifactIdxdoclet-maven-plugin/artifactId

  dependencies
  dependency
   groupId javax.servlet/groupId
   artifactIdservlet-api/artifactId
   version2.4/version
   scopeprovided/scope
  /dependency
  /dependencies

  executions
execution
  phasegenerate-sources/phase
  goals
goalxdoclet/goal
  /goals
  configuration
tasks
  webdoclet destdir=${project.build.directory}/${
 project.build.finalName}/WEB-INF
  excludedtags= @version,@author
   verbose= true
fileset dir=${project.build.sourceDirectory}
 include name=**/* Form.java /
 include name=**/*Action.java /
/fileset
 strutsconfigxml
 mergeDir=
 ${basedir}/src/main/webapp/WEB-INF/merge
 validatexml= true
 version= 1.2/
 strutsvalidationxml
 validatexml= true
 version= 1.1.3/
  /webdoclet
/tasks
  /configuration
/execution
  /executions
/plugin
  /plugins
/build
 /project


--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

Re: antrun classpaths

On Mon, 12 Jun 2006, Lee Meador wrote:

Hi,

I can't reproduce this with 'inheritRefs=true'.

What do you have in your build.xml?

-- Kenney

 I went to here to see how to let ant get to some maven classpaths:

 http://maven.apache.org/plugins/maven-antrun-plugin/classpaths.html

 I have a build.xml file that I run with this in my pom:

build
 plugins
 plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
 execution
 phasegenerate-sources/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 ant inheritRefs=true
 target=axisWsdl2Java antfile=build.xml dir=. /
 /tasks
 sourceRoot${project.build.directory
 }/generated-sources/java/sourceRoot
 /configuration
 /execution
 /executions
 /plugin
 /plugins
 /build

 But it complains that:

 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Error executing ant tasks

 Embedded error: The following error occurred while executing this line:
 [path here]\build.xml:31: Reference maven.runtime.classpath not

 Any ideas? Is the doc page up to date?

 Thanks.

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


--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

Re: Parent vs. Multi Project super pom

2006-06-12 Thread Stephen Duncan


I personally do more as you do.

I have team-wide super-POMs  I have a primary one that has basic
url, issue management, etc. type settings.  Then I have a core POM
with common dependencyManagment section to encourage use of the same
versions of Jar's to prevent incompatibilities, as well as common
reporting configuration.  Then I have a webapp parent POM that
specifically states the provided dependencies for webapps to be
deployed to our target server, as well as webapp specific stuff, such
as setting finalName${project.artifactId}/finalName to remove the
version number from wars, and wtpVersion1.0/wtpVersion for the
Eclipse plugin.

For multi-module project, I have an aggregating POM that defines the
modules, but each module uses the appropriate super-POM as its
parent, not the aggregating POM.

I've found this to work better for us.  But I too have been wondering
what the reasoning for the pattern of using the aggregating POM also
as the parent POM is...

-Stephen

On 6/12/06, Stefan Hübner [EMAIL PROTECTED] wrote:

Hi all,

this is kind of a best-practise-question about your habbits of using
the concepts of multi-project-super-pom.

First of all, are there distinctive terms commonly agreed upon for
each of those concepts?

Second, those two ways of using POMs appear to me to be orthogonal to
each other, really. Parent POMs are used to define common
characterisitics for a group of projects. Multi Project POMs on the
other hand aggregate modules belonging to a greater project. I usually
have the habbit of defining two diffent poms for multiproject
situations. e.g.:

/multiproject-pom X
-parent-pom Y
-module A / pom A (parent pom: Y)
-module B / pom B (parent pom: Y)

In most examples found though (e.g. in maven's own sources themselfs)
typically multi project poms at the same time are used as parent poms
for those modules they aggregated.

So, what I can't get my head around yet is, is it just a matter of
habbit or taste to combine those two usages in just one POM? or am I
really missing something important here, if I define two distinctive
POMs the way described above.

I'm thinking about this for quite a while now and any clarification
would be much appreciated.

Stefan

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





--
Stephen Duncan Jr
www.stephenduncanjr.com

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

Re: Multiproject: Merge Javadoc's into parents site?

2006-06-12 Thread Maria Odea Ching



Hi Jochen,

You can integrate javadoc into the site by putting this in your parent pom:

project
 ...
 reporting
   plugins
 plugin
   artifactIdmaven-javadoc-plugin/artifactId
   aggregatetrue/aggregate
 /plugin
   /plugins
 /reporting
/project

The aggregate parameter specifies that all the generated javadocs of the 
different modules will

be compiled into one javadoc report.

Thanks,
Odea


Jochen Wiedmann wrote:

Hi,

I have a project (Apache XML-RPC) with three subprojects (common,
client, server), each of which are building a jar file. The site is
created by the parent project.

Now I'd like to integrate the Javadoc's into the site. But how to do 
that?


Regards,

Jochen




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

Re: Parent vs. Multi Project super pom