date:20070206


build
extensions
  extension
groupIdmysql-connector-java/groupId
artifactIdmysql-connector-java/artifactId
version5.0.4/version
  /extension
/extensions


hth,

Manos

Quoting lemon dumpling [EMAIL PROTECTED]:

 Hi Johann,

 Yes, I tried that thing but it always throws no suitable driver
 exception:
 [ERROR] SchemaExport - schema export unsuccessful
 java.sql.SQLException: No
 sui
 table driverjava.sql.SQLException: No suitable driver
 at
 java.sql.DriverManager.getConnection(DriverManager.java:545)
 at
 java.sql.DriverManager.getConnection(DriverManager.java:140)
 at
 org.hibernate.connection.DriverManagerConnectionProvider.getConnectio
 n(DriverManagerConnectionProvider.java:110)

 My pom.xml:

 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdhibernate3-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
 configuration
   componentProperties
 outputfilenameschema.sql/outputfilename
   /componentProperties
 /configuration
 /plugin


 But then if I have something like this, it actually works - it auto
 connects
 to my database and creates the schema:


 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdhibernate3-maven-plugin/artifactId
 version2.0-SNAPSHOT/version

 configuration
   components
 component
   namehbm2ddl/name
 /component
   /components
   componentProperties
 droptrue/drop
 createtrue/create
 jdk5true/jdk5


configurationfilesrc/main/resources/hibernate.cfg.xml/configurationfile
   /componentProperties
 /plugin

 Cheers



 On 2/5/07, Johann Reyes [EMAIL PROTECTED] wrote:
 
  Hello
 
  First you need to set up the element outputfilename as seen here:
 
 
 

http://mojo.codehaus.org/maven-hibernate3/hibernate3-maven-plugin/examples/s
  chema_output.html
 
  Also you need to include the annotated classes in your
 hibernate.cfg.xml
  file
 
  Regards
 
  Johann Reyes
 
  -Original Message-
  From: lemon dumpling [mailto:[EMAIL PROTECTED]
  Sent: Saturday, February 03, 2007 8:33 PM
  To: users@maven.apache.org
  Subject: Maven2+Hibernate3 Annotation Problem
 
  Hi,
 
  I want to generate database schema to a sql file and feed the
 schema into
  my
  database. I have hibernate annotations instead of hbm.xml files.
 
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdhibernate3-maven-plugin/artifactId
  version2.0-SNAPSHOT/version
  configuration
components
  component
namehbm2ddl/name
  /component
/components
componentProperties
  droptrue/drop
  createtrue/create
 
 
 

configurationfilesrc/main/resources/etc/hibernate.cfg.xml/configurationfi
  le
/componentProperties
  /configuration
  /plugin
 
  I believe something is missing. Thanks!
 
  Cheers
 
 
 
 
 -
  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: Maven2+Hibernate3 Annotation Problem

2007-02-06 Thread Johann Reyes

Hello;

That's a base example, the plugin configuration should go something like
this:

plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-SNAPSHOT/version
configuration
componentProperties
droptrue/drop
createtrue/create
jdk5true/jdk5

configurationfilesrc/main/resources/hibernate.cfg.xml/configurationfile
outputfilenameschema.sql/outputfilename
/componentProperties
/configuration
/plugin

Regards

Johann Reyes

-Original Message-
From: lemon dumpling [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 8:29 AM
To: Maven Users List
Subject: Re: Maven2+Hibernate3 Annotation Problem

Hi Johann,

Yes, I tried that thing but it always throws no suitable driver exception:
[ERROR] SchemaExport - schema export unsuccessful java.sql.SQLException: No
sui
table driverjava.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnectio
n(DriverManagerConnectionProvider.java:110)

My pom.xml:

plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-SNAPSHOT/version
configuration
  componentProperties
outputfilenameschema.sql/outputfilename
  /componentProperties
/configuration
/plugin


But then if I have something like this, it actually works - it auto connects
to my database and creates the schema:


plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-SNAPSHOT/version

configuration
  components
component
  namehbm2ddl/name
/component
  /components
  componentProperties
droptrue/drop
createtrue/create
jdk5true/jdk5

configurationfilesrc/main/resources/hibernate.cfg.xml/configurationfile
  /componentProperties
/plugin

Cheers



On 2/5/07, Johann Reyes [EMAIL PROTECTED] wrote:

 Hello

 First you need to set up the element outputfilename as seen here:



http://mojo.codehaus.org/maven-hibernate3/hibernate3-maven-plugin/examples/s
 chema_output.html

 Also you need to include the annotated classes in your hibernate.cfg.xml
 file

 Regards

 Johann Reyes

 -Original Message-
 From: lemon dumpling [mailto:[EMAIL PROTECTED]
 Sent: Saturday, February 03, 2007 8:33 PM
 To: users@maven.apache.org
 Subject: Maven2+Hibernate3 Annotation Problem

 Hi,

 I want to generate database schema to a sql file and feed the schema into
 my
 database. I have hibernate annotations instead of hbm.xml files.

 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdhibernate3-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
 configuration
   components
 component
   namehbm2ddl/name
 /component
   /components
   componentProperties
 droptrue/drop
 createtrue/create



configurationfilesrc/main/resources/etc/hibernate.cfg.xml/configurationfi
 le
   /componentProperties
 /configuration
 /plugin

 I believe something is missing. Thanks!

 Cheers



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

EAR libs and MANIFEST.MF generation



Hello,

Back in my Ant-based projects i used the pathconvert to generate
manifest files from myruntime.classpathref. I also filtered all those
jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
(thanks to the manifests) both EJBs and WAR classes could access them,
avoiding duplication of library JARs.

I'm getting ready to port the same logic through the antrun plugin, then
use exclusions and what not to finally end up with the same structure
and was wondering if there is a better way to do this.

Thanks in advance,

Manos

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

Re: EAR libs and MANIFEST.MF generation

2007-02-06 Thread Marco Mistroni


Hi,
any particular reason for not using maven-ear-plugin, since it will
generate manifest classpath entries based on dependencies of your projects?

hth
marco

On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:




Hello,

Back in my Ant-based projects i used the pathconvert to generate
manifest files from myruntime.classpathref. I also filtered all those
jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
(thanks to the manifests) both EJBs and WAR classes could access them,
avoiding duplication of library JARs.

I'm getting ready to port the same logic through the antrun plugin, then
use exclusions and what not to finally end up with the same structure
and was wondering if there is a better way to do this.

Thanks in advance,

Manos

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

Eclipse plugin development with Maven 2

2007-02-06 Thread Sebastien Pennec


Hi there,

Anybody in the list has used Maven 2 to develop plugins for Eclipse?

Is there any best practice related to this kind of project that I should know about 
before I start?


Any advice appreciated :)

Sébastien

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

Re: Maven2+Hibernate3 Annotation Problem

2007-02-06 Thread lemon dumpling


Thanks for everyone's help! Finally made it work!

Cheers

On 2/7/07, Manos Batsis [EMAIL PROTECTED] wrote:



build
extensions
  extension
groupIdmysql-connector-java/groupId
artifactIdmysql-connector-java/artifactId
version5.0.4/version
  /extension
/extensions


hth,

Manos

Quoting lemon dumpling [EMAIL PROTECTED]:

 Hi Johann,

 Yes, I tried that thing but it always throws no suitable driver
 exception:
 [ERROR] SchemaExport - schema export unsuccessful
 java.sql.SQLException: No
 sui
 table driverjava.sql.SQLException: No suitable driver
 at
 java.sql.DriverManager.getConnection(DriverManager.java:545)
 at
 java.sql.DriverManager.getConnection(DriverManager.java:140)
 at
 org.hibernate.connection.DriverManagerConnectionProvider.getConnectio
 n(DriverManagerConnectionProvider.java:110)

 My pom.xml:

 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdhibernate3-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
 configuration
   componentProperties
 outputfilenameschema.sql/outputfilename
   /componentProperties
 /configuration
 /plugin


 But then if I have something like this, it actually works - it auto
 connects
 to my database and creates the schema:


 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdhibernate3-maven-plugin/artifactId
 version2.0-SNAPSHOT/version

 configuration
   components
 component
   namehbm2ddl/name
 /component
   /components
   componentProperties
 droptrue/drop
 createtrue/create
 jdk5true/jdk5



configurationfilesrc/main/resources/hibernate.cfg.xml/configurationfile
   /componentProperties
 /plugin

 Cheers



 On 2/5/07, Johann Reyes [EMAIL PROTECTED] wrote:
 
  Hello
 
  First you need to set up the element outputfilename as seen here:
 
 
 


http://mojo.codehaus.org/maven-hibernate3/hibernate3-maven-plugin/examples/s
  chema_output.html
 
  Also you need to include the annotated classes in your
 hibernate.cfg.xml
  file
 
  Regards
 
  Johann Reyes
 
  -Original Message-
  From: lemon dumpling [mailto:[EMAIL PROTECTED]
  Sent: Saturday, February 03, 2007 8:33 PM
  To: users@maven.apache.org
  Subject: Maven2+Hibernate3 Annotation Problem
 
  Hi,
 
  I want to generate database schema to a sql file and feed the
 schema into
  my
  database. I have hibernate annotations instead of hbm.xml files.
 
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdhibernate3-maven-plugin/artifactId
  version2.0-SNAPSHOT/version
  configuration
components
  component
namehbm2ddl/name
  /component
/components
componentProperties
  droptrue/drop
  createtrue/create
 
 
 


configurationfilesrc/main/resources/etc/hibernate.cfg.xml/configurationfi
  le
/componentProperties
  /configuration
  /plugin
 
  I believe something is missing. Thanks!
 
  Cheers
 
 
 
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 





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

[M2] No xref report when executing site:stage?

2007-02-06 Thread Rodrigo Ruiz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

Using Maven 2.0.4, if I do the following on my (multi-module) project:

mvn clean site site:stage -DstagingDirectory=Z:\

The resulting site has no xref pages.

I can see them in each [module]\target\site\xref folder, but they are
not copied to Z:\. There, only a stylesheet.css and an empty index.html
(0 bytes) are generated.

Is this a known issue?

Regards

- --
- ---
GRID SYSTEMS, S.A. Rodrigo Ruiz
Parc Bit - Edificio 17 Research Coordinator
07121 Palma de Mallorca
Baleares - Spain   Tel: +34 971 435 085
http://www.gridsystems.com/Fax: +34 971 435 082
- ---
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)

iD8DBQFFyI1cp9m/F5UenDoRAmWaAJ0UIsOW90jcot31qTW4ybo7djmqLACeJtSg
FMoC5czqz6WupmfO34JBmkA=
=/DC/
-END PGP SIGNATURE-

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

Re: EAR libs and MANIFEST.MF generation


Hey Marco,

Thanks for your email.

Quoting Marco Mistroni [EMAIL PROTECTED]:
  any particular reason for not using maven-ear-plugin, since it will
 generate manifest classpath entries based on dependencies of your
 projects?


I use it already, but i probably not to its full extent. The manifest it
creates for the EAR has no classpath entry. Do i have to tell the plugin
to create it using jarModule elements for all the runtime dependencies
or is there an other way?

Even then:

* Do i have to manually exclude the deps from my WAR using the plugin?
* Will the WAR and EJB-JAR obey the EAR manifest? I used to create the
manifest for those modules with Ant for this structure to work.


Many thanks,

Manos


 hth
  marco

 On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
 
 
 
  Hello,
 
  Back in my Ant-based projects i used the pathconvert to generate
  manifest files from myruntime.classpathref. I also filtered all
 those
  jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
  (thanks to the manifests) both EJBs and WAR classes could access
 them,
  avoiding duplication of library JARs.
 
  I'm getting ready to port the same logic through the antrun plugin,
 then
  use exclusions and what not to finally end up with the same
 structure
  and was wondering if there is a better way to do this.
 
  Thanks in advance,
 
  Manos
 
 
 -
  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: EAR libs and MANIFEST.MF generation



Finaly got it:

http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html

Cheers,

Manos


Quoting Manos Batsis [EMAIL PROTECTED]:


 Hey Marco,

 Thanks for your email.

 Quoting Marco Mistroni [EMAIL PROTECTED]:
   any particular reason for not using maven-ear-plugin, since it
 will
  generate manifest classpath entries based on dependencies of your
  projects?


 I use it already, but i probably not to its full extent. The manifest
 it
 creates for the EAR has no classpath entry. Do i have to tell the
 plugin
 to create it using jarModule elements for all the runtime
 dependencies
 or is there an other way?

 Even then:

 * Do i have to manually exclude the deps from my WAR using the
 plugin?
 * Will the WAR and EJB-JAR obey the EAR manifest? I used to create
 the
 manifest for those modules with Ant for this structure to work.


 Many thanks,

 Manos

 
  hth
   marco
 
  On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
  
  
  
   Hello,
  
   Back in my Ant-based projects i used the pathconvert to generate
   manifest files from myruntime.classpathref. I also filtered all
  those
   jars out of my WARs/WEB-INF/lib and put them in the EAR/lib,
 where
   (thanks to the manifests) both EJBs and WAR classes could access
  them,
   avoiding duplication of library JARs.
  
   I'm getting ready to port the same logic through the antrun
 plugin,
  then
   use exclusions and what not to finally end up with the same
  structure
   and was wondering if there is a better way to do this.
  
   Thanks in advance,
  
   Manos
  
  
 
 -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 




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





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

MRM-60 Repository Manager should have a means to remove old snapshot builds

2007-02-06 Thread Antoine Véret


Hello, in order to manage the size of a repo i would like to automatically
remove old snapshots.
I have seen the closed MRM-60 issue, which seems to correspond to my needs
but i don't find the way of remove snapshot.
This issue has been renamed, so the feature added was oldArtifact (and
oldSnapshot) reports.
Is there another issue linked with this one, or is there another way to do
the job?
Thanks
--
Antoine Véret

Copyright on the stylus skin images

2007-02-06 Thread Rodrigo Ruiz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I would like to know if we need explicit permissions for publishing a
site generated with the Maven stylus skin and using some slightly
modified images from it (for inserting our project and company logos).

Regards

- --
- ---
GRID SYSTEMS, S.A. Rodrigo Ruiz
Parc Bit - Edificio 17 Research Coordinator
07121 Palma de Mallorca
Baleares - Spain   Tel: +34 971 435 085
http://www.gridsystems.com/Fax: +34 971 435 082
- ---
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)

iD8DBQFFyJDKp9m/F5UenDoRAn6fAJ9IT5A94lv7z+hsfAdxuvpKCj0bCwCbB0Vg
fg68IZo0Pel561Yq2oHabZU=
=4mja
-END PGP SIGNATURE-

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

Re: EAR libs and MANIFEST.MF generation

2007-02-06 Thread Marco Mistroni


Hi Manos

mmm, why would the manifest of the .ear have classpath entries?
the classpath entries you need are in the manifest of your project for which
you have
jars (pls anyone correct me if i m wrong)

what your ear should contain is artifacts for your project,
META-INF\application.xml and common libraries.

I believe maven ear plugin is clever enough to know, if two projects depends
on the same library, to add it to the .EAR (of course, this will depend on
the scope of your dependencies)

Pls anyone correct me if i m wrong..  Manos, best suggestion is that you try
a simple .ear project for yourself and see what maven does with Manifest

i think you'll find solution to your problems quite soon...

if not, let me know, i'll mail you a sample that i have at home so you can
see where all dependencies go

If your war are dependent to libraries which are common to other projects,
don't put them in the war, change their scope so that they won't be
included..

hth
marco




On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:



Hey Marco,

Thanks for your email.

Quoting Marco Mistroni [EMAIL PROTECTED]:
  any particular reason for not using maven-ear-plugin, since it will
 generate manifest classpath entries based on dependencies of your
 projects?


I use it already, but i probably not to its full extent. The manifest it
creates for the EAR has no classpath entry. Do i have to tell the plugin
to create it using jarModule elements for all the runtime dependencies
or is there an other way?

Even then:

* Do i have to manually exclude the deps from my WAR using the plugin?
* Will the WAR and EJB-JAR obey the EAR manifest? I used to create the
manifest for those modules with Ant for this structure to work.


Many thanks,

Manos


 hth
  marco

 On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
 
 
 
  Hello,
 
  Back in my Ant-based projects i used the pathconvert to generate
  manifest files from myruntime.classpathref. I also filtered all
 those
  jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
  (thanks to the manifests) both EJBs and WAR classes could access
 them,
  avoiding duplication of library JARs.
 
  I'm getting ready to port the same logic through the antrun plugin,
 then
  use exclusions and what not to finally end up with the same
 structure
  and was wondering if there is a better way to do this.
 
  Thanks in advance,
 
  Manos
 
 
 -
  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: EAR libs and MANIFEST.MF generation

2007-02-06 Thread Stephane Nicoll


Hi,

On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:


Hey Marco,

Thanks for your email.

Quoting Marco Mistroni [EMAIL PROTECTED]:
  any particular reason for not using maven-ear-plugin, since it will
 generate manifest classpath entries based on dependencies of your
 projects?



Even if you do this, it won't work AFAIK since it's not part of the
spec. The way to define dependencies between an EJB module and
third-party libs is to define a manifest for the *EJB* module.

Does this actually work? On which app server?


* Will the WAR and EJB-JAR obey the EAR manifest? I used to create the
manifest for those modules with Ant for this structure to work.


I am pretty sure it won't work and this way of working is not compliant anyway.

Back to your original question, this is an interesting use case. Why
don't you generate the manifest when you actually build your EJB
modules? Maven can do this for your (see the archive settings).

Regards,
Stéphane




Many thanks,

Manos


 hth
  marco

 On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
 
 
 
  Hello,
 
  Back in my Ant-based projects i used the pathconvert to generate
  manifest files from myruntime.classpathref. I also filtered all
 those
  jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
  (thanks to the manifests) both EJBs and WAR classes could access
 them,
  avoiding duplication of library JARs.
 
  I'm getting ready to port the same logic through the antrun plugin,
 then
  use exclusions and what not to finally end up with the same
 structure
  and was wondering if there is a better way to do this.
 
  Thanks in advance,
 
  Manos
 
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 





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




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

Re: Eclipse plugin development with Maven 2

2007-02-06 Thread Stéphane Bouchet


Hi,

there is some docs on codehaus about it :

http://docs.codehaus.org/display/MAVEN/Maven+and+Eclipse

http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin

http://docs.codehaus.org/display/MAVEN/Barriers+to+Building+Eclipse+with+Maven

Cheers,

Stéphane


Sebastien Pennec a écrit :

Hi there,

Anybody in the list has used Maven 2 to develop plugins for Eclipse?

Is there any best practice related to this kind of project that I 
should know about before I start?


Any advice appreciated :)

Sébastien

-
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: EAR libs and MANIFEST.MF generation

2007-02-06 Thread Marco Mistroni


Oh dear, thanx Stephane for the clarifications..
I completely forgot that EAR i built were EJB3 based, where i didnt have an
ejb artifact as
i can deploy ejbs as jars

thanks for pointing that out.

regards
marco


On 2/6/07, Stephane Nicoll [EMAIL PROTECTED] wrote:


Hi,

On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:

 Hey Marco,

 Thanks for your email.

 Quoting Marco Mistroni [EMAIL PROTECTED]:
   any particular reason for not using maven-ear-plugin, since it will
  generate manifest classpath entries based on dependencies of your
  projects?


Even if you do this, it won't work AFAIK since it's not part of the
spec. The way to define dependencies between an EJB module and
third-party libs is to define a manifest for the *EJB* module.

Does this actually work? On which app server?

 * Will the WAR and EJB-JAR obey the EAR manifest? I used to create the
 manifest for those modules with Ant for this structure to work.

I am pretty sure it won't work and this way of working is not compliant
anyway.

Back to your original question, this is an interesting use case. Why
don't you generate the manifest when you actually build your EJB
modules? Maven can do this for your (see the archive settings).

Regards,
Stéphane



 Many thanks,

 Manos

 
  hth
   marco
 
  On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
  
  
  
   Hello,
  
   Back in my Ant-based projects i used the pathconvert to generate
   manifest files from myruntime.classpathref. I also filtered all
  those
   jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where
   (thanks to the manifests) both EJBs and WAR classes could access
  them,
   avoiding duplication of library JARs.
  
   I'm getting ready to port the same logic through the antrun plugin,
  then
   use exclusions and what not to finally end up with the same
  structure
   and was wondering if there is a better way to do this.
  
   Thanks in advance,
  
   Manos
  
  
  -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 




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



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

Re: Eclipse plugin development with Maven 2

2007-02-06 Thread Dan Tran


and

http://mojo.codehaus.org/pde-maven-plugin/


On 2/6/07, Stéphane Bouchet [EMAIL PROTECTED] wrote:


Hi,

there is some docs on codehaus about it :

http://docs.codehaus.org/display/MAVEN/Maven+and+Eclipse

http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin


http://docs.codehaus.org/display/MAVEN/Barriers+to+Building+Eclipse+with+Maven

Cheers,

Stéphane


Sebastien Pennec a écrit :
 Hi there,

 Anybody in the list has used Maven 2 to develop plugins for Eclipse?

 Is there any best practice related to this kind of project that I
 should know about before I start?

 Any advice appreciated :)

 Sébastien

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

[solved] Re: EAR libs and MANIFEST.MF generation


I thought i sent this [1] earlier but it never got through. Still, this
can be improved, the solution forces the EAR POM to include explicitly
all WAR dependencies, which results in duplicate markup between the
POMs.

[1]
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html

Thanks for the help all,

Manos

Quoting Stephane Nicoll [EMAIL PROTECTED]:

 Hi,

 On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
 
  Hey Marco,
 
  Thanks for your email.
 
  Quoting Marco Mistroni [EMAIL PROTECTED]:
any particular reason for not using maven-ear-plugin, since it
 will
   generate manifest classpath entries based on dependencies of your
   projects?
 

 Even if you do this, it won't work AFAIK since it's not part of the
 spec. The way to define dependencies between an EJB module and
 third-party libs is to define a manifest for the *EJB* module.

 Does this actually work? On which app server?

  * Will the WAR and EJB-JAR obey the EAR manifest? I used to create
 the
  manifest for those modules with Ant for this structure to work.

 I am pretty sure it won't work and this way of working is not
 compliant anyway.

 Back to your original question, this is an interesting use case. Why
 don't you generate the manifest when you actually build your EJB
 modules? Maven can do this for your (see the archive settings).

 Regards,
 Stéphane

 
 
  Many thanks,
 
  Manos
 
  
   hth
marco
  
   On 2/6/07, Manos Batsis [EMAIL PROTECTED] wrote:
   
   
   
Hello,
   
Back in my Ant-based projects i used the pathconvert to
 generate
manifest files from myruntime.classpathref. I also filtered all
   those
jars out of my WARs/WEB-INF/lib and put them in the EAR/lib,
 where
(thanks to the manifests) both EJBs and WAR classes could
 access
   them,
avoiding duplication of library JARs.
   
I'm getting ready to port the same logic through the antrun
 plugin,
   then
use exclusions and what not to finally end up with the same
   structure
and was wondering if there is a better way to do this.
   
Thanks in advance,
   
Manos
   
   
  
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
 
 
 
 
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

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






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

Three plugins bound to the package phase

I'm close to having a beautiful maven (2.0.4) build using 3 handy
plugins:  appassembler, assembly, and rpm.

My app is a simple command line thing.  I use appassembler to create
wrapper shell scripts, and assembly to package it as a tarball.

I occasionally need to build an RPM, so I added a profile 'rpm' that
invokes the rpm-maven-plugin, but activating this profile reverses the
order of the executions of the other two.

In other words, this command runs appassembler, then assembly, as
expected:
  $ mvn package
But this one runs assembly *BEFORE* appassembler, and then rpm:
  $ mvn -Prpm package

WTF?  I require appassembler to run first, obviously.  I've tried
binding appassembler to an earlier phase, but it always fails,
apparently because it requires the jar built only in the package phase.

I could do away with the profile and always try to build the rpm (that
solves my plugin ordering problem) but it breaks the build when run on a
Windows platform.

Any other ideas?

Thanks,
Jim

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

RE: compile tries to bundle up the ear - should it?

2007-02-06 Thread EJ Ciramella

So in essence you're suggesting shutting of unittests via a switch (most
developers already think it takes too long and use -Dtest=asdf).

I personally find this unacceptable.  I still think it's silly that mvn
tries to build an ear/war/ejbs when all it needs are the underlying
classes.

There's part of the picture I think I'm not emphasizing enough which is
the inherently long drawn out process building an atg app requires
(their assembly phase) which we've linked to the package lifecycle goal.
Having to do an install of each module takes too much time moving around
and doing an install of everything takes too long if all you want to do
is compile.

To build an ejb, the underlying java source needs to be compiled and
stashed somewhere doesn't it?  I just still don't understand why there
would be this dependency on an ear file to simply compile something in
one of the main applications.

I have a feeling this will be the straw that breaks the development
camels back.



-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 05, 2007 8:05 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

Hopefully they're all using Eclipse and they can run 'mvn
eclipse:eclipse'
to generate the Eclipse project files they need so that they can compile
their Java code as they develop.

You don't need to build your EJB, WAR and EAR files just to get your
classes
to compile UNLESS other modules depend on them.

For example, if I have modules A, B and C and module B is dependent on A
but
C is independent of both of them, I can build C without needing access
to
artifacts from A and B. If, however, I want to build B, I will need
access
to A.jar. A.jar would normally come from my local repository since I've
run
'mvn clean install' in module A.

The whole point is that you've decided when designing your project
structure
that A, B and C are separately managed modules (with dependencies
between
them). Therefore, to access A's classes from B you need to package them
in
some way. In Maven, the way to do this is to package them as a jar file
and
place them in your local repository (and eventually in your snapshot
repository and, finally, in your production repository).

As for running tests, developers can turn off running the tests during
their
development cycle (see the Maven Website for details). The actual
package/install steps of creating a jar and copying it to a local
repository
are very quick so no developer is really going to notice the lost time.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 6 February 2007 10:37 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

Yeah, I mentioned cruisecontrol, just not looking forward to telling
developers they need to run the install process now even if all they
want is
a simple compile.

I still don't see any good reason why you'd have to build up an ejb file
(or
war or ear) just to get your classes to compile.  These things shouldn't
even be attempted until the package stage.  

This seems like a shortcoming. 

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:29 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

You need to run 'mvn install' at least once to ensure your dependencies
are
in a repository. In fact, if your cruisecontrol build is running on
another
machine, you will need to run 'mvn deploy' at least once to get a
snapshot
in your corporate repository.

Then, you can run 'mvn compile' at will, as long as your Java sources
don't
change enough to make your compiles fail.

Having said that, I would recommend that you run 'mvn clean deploy'
every
night so that you are getting a complete build and test-cycle run every
night (or use a continuous integration server like Continuum). You can
also
add the 'findbugs' report to your projects so this is run for you
automatically as well.


-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 6 February 2007 10:18 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

So if (in my case) we do a compile prior to running findbugs each night
(a
case where we DON'T need an ear file), I'm going to have to start
performing
a mvn install instead?

P.S - this is running via cruisecontrol and always from the top
directory.
We're very used to an ant based build where we can run various stages as
we
wish.  Compile being a very desirable thing.  If we can no longer run
compile to compile source without having to wait for a much longer
process
(unit tests, site building, atg assembler, ejb building, war building
then
finally ear building), I think I may be in a bind (being the soul
release
engineer forced to support maven 2).

Can I forcefully de-couple these two things? 

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent:

Re: Eclipse plugin development with Maven 2

2007-02-06 Thread Sebastien Pennec


Hello Stéphane and Dan,

Thanks for your links!

Cheers,

Sébastien

Dan Tran wrote:

and

http://mojo.codehaus.org/pde-maven-plugin/


On 2/6/07, Stéphane Bouchet [EMAIL PROTECTED] wrote:


Hi,

there is some docs on codehaus about it :

http://docs.codehaus.org/display/MAVEN/Maven+and+Eclipse

http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin


http://docs.codehaus.org/display/MAVEN/Barriers+to+Building+Eclipse+with+Maven 



Cheers,

Stéphane


Sebastien Pennec a écrit :
 Hi there,

 Anybody in the list has used Maven 2 to develop plugins for Eclipse?

 Is there any best practice related to this kind of project that I
 should know about before I start?

 Any advice appreciated :)

 Sébastien

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






--
Sébastien Pennec
[EMAIL PROTECTED]

Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch/

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

maven2 warning when using company super pom ?

2007-02-06 Thread Attila Ravai

We have a company super pom with no modules. Just common dependencies, java 
compile version, etc. 

It is included in all of our projects as parent. 

However when I run mvn clean package on my project pom I get a warning in phase 
site:attach-descriptor
saying that the parent pom does not exist in the parent folder.

[INFO] [site:attach-descriptor]
[WARNING] Unable to load parent project from a relative path: Could not find 
the model file 'C:\${path_to_myproject}\..\pom.xml'.

Is there a way to get rid of this message? I thought a parent pom should not 
necessary be in a parent folder unless includes the child pom as module. In 
my case it does not so I would expect to have no warnings.

thanks,
Attila

 
-
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.

Re: Three plugins bound to the package phase

2007-02-06 Thread franz see


Good day to you, Jim

There is no assurance to the order of the goals executed in a single phase
with maven 2.0.4. This is fixed however in 2.0.5 and in the trunk.

So you may want to use those instead of 2.0.4 so that you can fix the order
of your goals in your phases.

Cheers,
Franz


Crossley, Jim wrote:
 
 I'm close to having a beautiful maven (2.0.4) build using 3 handy
 plugins:  appassembler, assembly, and rpm.
 
 My app is a simple command line thing.  I use appassembler to create
 wrapper shell scripts, and assembly to package it as a tarball.
 
 I occasionally need to build an RPM, so I added a profile 'rpm' that
 invokes the rpm-maven-plugin, but activating this profile reverses the
 order of the executions of the other two.
 
 In other words, this command runs appassembler, then assembly, as
 expected:
   $ mvn package
 But this one runs assembly *BEFORE* appassembler, and then rpm:
   $ mvn -Prpm package
 
 WTF?  I require appassembler to run first, obviously.  I've tried
 binding appassembler to an earlier phase, but it always fails,
 apparently because it requires the jar built only in the package phase.
 
 I could do away with the profile and always try to build the rpm (that
 solves my plugin ordering problem) but it breaks the build when run on a
 Windows platform.
 
 Any other ideas?
 
 Thanks,
 Jim
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Three-plugins-bound-to-the-package-phase-tf3181036s177.html#a8828459
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Maven 2.0.5 release plans?

2007-02-06 Thread Thierry Lach


Any idea when Maven 2.0.5 will be released?

[M2]: Doubts about modules and packing.

2007-02-06 Thread Marcos Silva Pereira


Hello, this is my first post to this list. Usually, I can find any
information I need to use Maven. But, nowadays, because my company is
migrating from Ant to Maven and we have a lot of specific targets, I need to
appeal to this mailing list.
So, we are doing the migration following the steps below:
1. Put projects in Maven layout
2. Split some projects in many modules project
3. Migrate Ant tasks.

Doing theses steps we have some doubts.

Our environment: We have a set of internal projects that work more like libs
to other real projects. So, we desire to add these internal libs as maven
managed dependencies, we´ve even created an internal remote repository to
deploy them. Right now, these libs have only classes, but to us, in a
logical view, they must contain all artifacts related to them - like JSPs,
pictures, and so forth.

First: We have more than one project that share the same web application
structure. In other words, all web artefacts for those projects - including
jsp - are in the same directory/eclipse project, without modules. My
question is: how can I separate web application part in modules and later
take only a single war with all artifacts? How can can separate these
projects and keep taking my whole webapp?

Second: I have some ant´s targets that create jars for java web start
clients. These jars have classes that are part of the dependencies - for
example, from commons-beans. Using Ant, I put these classes in jws's jar
using a zipfileset:

zipfileset id=jar.commons-beans src=${libs}/commons-beans.jar
   include name=org/apache/... /
   ...
/zipfileset

Of course, I manage the dependency manually, so, I could reference it in
src attribute. Using maven, how can I do it? I am already using the antrun
plugin, but I don't know how to reference a dependency jar inside pom.xml.
Do you have any suggestions? Maybe I can use maven-webstart plugin, but how
do I filter classes inside a dependency?

ps.: sorry my poor English.

--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
http://blastemica.blogspot.com

Download artifacts from one repo and upload to another

2007-02-06 Thread ArneD


I'm looking for an easy way to download an artifact from one repository and
deploy it to another, including all transitive dependencies. Ideally in just
one step. Mirroring the whole repository is not a solution.

How would you do it? Any hints what to look at? 

Thanks
- Arne
-- 
View this message in context: 
http://www.nabble.com/Download-artifacts-from-one-repo-and-upload-to-another-tf3181645s177.html#a8829481
Sent from the Maven - Users mailing list archive at Nabble.com.


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

RE: compile tries to bundle up the ear - should it?

2007-02-06 Thread EJ Ciramella

Additionally  - you miss the point about just wanting to compile and
unittest with no startup of the actual app (repeatedly, in quick
succession).

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 05, 2007 8:05 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

Hopefully they're all using Eclipse and they can run 'mvn
eclipse:eclipse'
to generate the Eclipse project files they need so that they can compile
their Java code as they develop.

You don't need to build your EJB, WAR and EAR files just to get your
classes
to compile UNLESS other modules depend on them.

For example, if I have modules A, B and C and module B is dependent on A
but
C is independent of both of them, I can build C without needing access
to
artifacts from A and B. If, however, I want to build B, I will need
access
to A.jar. A.jar would normally come from my local repository since I've
run
'mvn clean install' in module A.

The whole point is that you've decided when designing your project
structure
that A, B and C are separately managed modules (with dependencies
between
them). Therefore, to access A's classes from B you need to package them
in
some way. In Maven, the way to do this is to package them as a jar file
and
place them in your local repository (and eventually in your snapshot
repository and, finally, in your production repository).

As for running tests, developers can turn off running the tests during
their
development cycle (see the Maven Website for details). The actual
package/install steps of creating a jar and copying it to a local
repository
are very quick so no developer is really going to notice the lost time.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 6 February 2007 10:37 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

Yeah, I mentioned cruisecontrol, just not looking forward to telling
developers they need to run the install process now even if all they
want is
a simple compile.

I still don't see any good reason why you'd have to build up an ejb file
(or
war or ear) just to get your classes to compile.  These things shouldn't
even be attempted until the package stage.  

This seems like a shortcoming. 

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:29 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

You need to run 'mvn install' at least once to ensure your dependencies
are
in a repository. In fact, if your cruisecontrol build is running on
another
machine, you will need to run 'mvn deploy' at least once to get a
snapshot
in your corporate repository.

Then, you can run 'mvn compile' at will, as long as your Java sources
don't
change enough to make your compiles fail.

Having said that, I would recommend that you run 'mvn clean deploy'
every
night so that you are getting a complete build and test-cycle run every
night (or use a continuous integration server like Continuum). You can
also
add the 'findbugs' report to your projects so this is run for you
automatically as well.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 6 February 2007 10:18 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

So if (in my case) we do a compile prior to running findbugs each night
(a
case where we DON'T need an ear file), I'm going to have to start
performing
a mvn install instead?

P.S - this is running via cruisecontrol and always from the top
directory.
We're very used to an ant based build where we can run various stages as
we
wish.  Compile being a very desirable thing.  If we can no longer run
compile to compile source without having to wait for a much longer
process
(unit tests, site building, atg assembler, ejb building, war building
then
finally ear building), I think I may be in a bind (being the soul
release
engineer forced to support maven 2).

Can I forcefully de-couple these two things? 

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:05 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

It hasn't tried to build the EAR yet:

 [INFO] Building ltyApp_ear
 [INFO]task-segment: [compile]

You have specified 'mvn compile' in the EAR project and it is simply
trying
to download dependencies at this stage so it can do the compile.

My suggestion would be to not run the compile phase explicitly,
particularly
in the EAR module, but run 'mvn install' even if you are building
virtually
empty artifacts for the other components. In other words, get the whole
build process working correctly first.

Alternatively, the next best thing to do would be to remove the EAR
module
from your modules list for now until you have everything else to a stage
where the repository has all of the artifacts required

RE: compile tries to bundle up the ear - should it?

2007-02-06 Thread EJ Ciramella

Yeah, this is kinda nuts, even after running an install, I see things
getting rebuilt:

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


[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 3 source files to
E:\work\39-FUSED\frontoffice\ltyApp\ejb\withdrawal\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\39-FUSED\frontoffice\ltyApp\ejb\withdrawal\target\withdrawalEJB-
1.0-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
E:\work\39-FUSED\frontoffice\ltyApp\ejb\withdrawal\target\withdrawalEJB-
1.0-SNAPSHOT.jar to E:\work\m2\Repository\lty\withdrawa

Shouldn't this happen just once?  Why each time? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 9:59 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

So in essence you're suggesting shutting of unittests via a switch (most
developers already think it takes too long and use -Dtest=asdf).

I personally find this unacceptable.  I still think it's silly that mvn
tries to build an ear/war/ejbs when all it needs are the underlying
classes.

There's part of the picture I think I'm not emphasizing enough which is
the inherently long drawn out process building an atg app requires
(their assembly phase) which we've linked to the package lifecycle goal.
Having to do an install of each module takes too much time moving around
and doing an install of everything takes too long if all you want to do
is compile.

To build an ejb, the underlying java source needs to be compiled and
stashed somewhere doesn't it?  I just still don't understand why there
would be this dependency on an ear file to simply compile something in
one of the main applications.

I have a feeling this will be the straw that breaks the development
camels back.



-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 05, 2007 8:05 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

Hopefully they're all using Eclipse and they can run 'mvn
eclipse:eclipse'
to generate the Eclipse project files they need so that they can compile
their Java code as they develop.

You don't need to build your EJB, WAR and EAR files just to get your
classes
to compile UNLESS other modules depend on them.

For example, if I have modules A, B and C and module B is dependent on A
but
C is independent of both of them, I can build C without needing access
to
artifacts from A and B. If, however, I want to build B, I will need
access
to A.jar. A.jar would normally come from my local repository since I've
run
'mvn clean install' in module A.

The whole point is that you've decided when designing your project
structure
that A, B and C are separately managed modules (with dependencies
between
them). Therefore, to access A's classes from B you need to package them
in
some way. In Maven, the way to do this is to package them as a jar file
and
place them in your local repository (and eventually in your snapshot
repository and, finally, in your production repository).

As for running tests, developers can turn off running the tests during
their
development cycle (see the Maven Website for details). The actual
package/install steps of creating a jar and copying it to a local
repository
are very quick so no developer is really going to notice the lost time.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 6 February 2007 10:37 AM
To: Maven Users List
Subject: RE: compile tries to bundle up the ear - should it?

Yeah, I mentioned cruisecontrol, just not looking forward to telling
developers they need to run the install process now even if all they
want is
a simple compile.

I still don't see any good reason why you'd have to build up an ejb file
(or
war or ear) just to get your classes to compile.  These things shouldn't
even be attempted until the package stage.  

This seems like a shortcoming. 

-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:29 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?

You need to run 'mvn install' at least once to ensure your dependencies
are
in a repository. In fact, if your cruisecontrol build is running on
another
machine, you will need to run 'mvn deploy' at least once to get a
snapshot
in your corporate repository.

Then, you can run 'mvn compile' at will, as long as your Java sources
don't
change enough to make your compiles fail.

Having said that, I would recommend that you run 'mvn clean deploy'
every
night so that you are

Re: continuum - scm update error

2007-02-06 Thread raghurajan . x . gurunathan

No, this is working fine in windows system, same thing when i moved to 
unix box its started acting now

even i checked for some new files, (there are some logfile) i removed them 
and tried to run continuum its failing again with the same error...

Again its working fine with no problem in windows xp machine,

The only way its working is everytime i have to delete the working copy , 
but i don't want to do it that way

Is there anything else i can configure??








Thanks,
Raghurajan Gurunathan






Emmanuel Venisse [EMAIL PROTECTED]
02/02/2007 12:55 PM
Please respond to continuum-users
 
To: continuum-users@maven.apache.org
cc: 
Subject:Re: continuum - scm update error


you have a directory created locally then added in svn so when svn try to 
update the working copy, it can't add the new directory because a 
directory with the same name already exist.
clean your working copy by deleting the directory or remove your working 
copy and all will work

[EMAIL PROTECTED] a écrit :
 Hi All
 
 I just created some projects using continuum to check out from svn, 
source 
 code and did one build on those worked fine no problem, 
 
 
 But now i'm trying to run build again from continuum, but for all 
project 
 in continuum i'm getting
 
 Provider message: The svn command failed.
 Command output: 
 
---
 svn: REPORT request failed on '/svn/repos/myProejct/!svn/vcc/default'
 svn: Cannot replace a directory from within
 
---
 
 
 
 I couldn't figure out whats going on here, please help
 
 
 Thanks,
 Raghurajan Gurunathan
 
 
 
 
 -
 This transmission may contain information that is privileged,
 confidential, legally privileged, and/or exempt from disclosure
 under applicable law.  If you are not the intended recipient, you
 are hereby notified that any disclosure, copying, distribution, or
 use of the information contained herein (including any reliance
 thereon) is STRICTLY PROHIBITED.  Although this transmission and
 any attachments are believed to be free of any virus or other
 defect that might affect any computer system into which it is
 received and opened, it is the responsibility of the recipient to
 ensure that it is virus free and no responsibility is accepted by
 JPMorgan Chase  Co., its subsidiaries and affiliates, as
 applicable, for any loss or damage arising in any way from its use.
 If you received this transmission in error, please immediately
 contact the sender and destroy the material in its entirety,
 whether in electronic or hard copy format. Thank you.

dependencies are bloated in M2

2007-02-06 Thread Tandon, Pankaj

Hi all,
We've been using Maven 1.1 for more that a year now and are looking to
move to M2. 
With M1 our project.xml file had dependencies specified explicitly
because there was no support for transitive dependencies. As a result,
the jar files we downloaded for our webapp weighed in at about 11Meg.
While building our M2 pom.xml file(s), we kept adding dependencies (in
the pom.xml) till we got a clean compile. However now the size of the
dependent artifacts has doubled to a whopping 23Meg! And they make it to
the WEB-INF/lib increasing the size of our final artifact.
 
So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help. There used to be a
propertieswar.bundletrue/war.bundle/properties in the dependency
node in M1, but that is no longer available in M2. So even if I have
more depoendencies at compile time, how can I prevent my war artifact
from getting bloated?
 
2. How can we exclude second and third level dependencies. And IF we can
do so, how do I know what the dependency graph is for some of the
downloaded jars. 
For instance, there is a jar file (that is about 3Meg in size) called
apacheds-core-0.9.jar. We know our app does not need this becuase if we
delete this file, the app works just fine.
 
2a. How do I find out what top level dependecny that is specified in the
pom caused a certain file to be downloaded? If we figure that out maybe
we can use the exclude element in each dependency to NOT load this
dependency.
For instance, how do I find out what top level dependency in my pom
caused this apacheds-core-0.9.jar to land up in my local repository.
Infact, this jar does not even exist on http://repo1.maven.org/maven2/
unless I google it out and find it is tucked away here
http://repo1.maven.org/maven2/directory/. 
 
3. Is there a way to go back to explicit dependencies (non-transitive)
in the pom.xml?
 
 
Thanks in advance,
Pankaj

[mojo-user] [ANN] OpenJPA Maven Plugin 1.0-alpha released

2007-02-06 Thread Rahul Thakur


Not sure why got filtered. Sending again...


Hi,

I am pleased to announce the release of OpenJPA Maven Plugin version 
1.0-alpha.


This release includes:
1)   Mojo to invoke OpenJPA PCEnhancer tool on mapped persistable 
classes.

2)   Plugin documentation.

Feedback and suggestions are welcome.

Cheers,

Rahul 



-
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email



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

[M2]: how to pass maven properties to ant build using antrun?

2007-02-06 Thread Marcos Silva Pereira


Hello, I am invoking some ant targets using maven antrun plugin but I cant
see how to pass maven properties to Ant build file. For example, I have the
following maven property:

properties
   jws.pathsrc/main/javawebstart/jws.path
/properties

But this properties is not accessible in ant build. Even if I put the ant
target inside pom.xml I cant access it. If I execute the config below:

plugin
   artifactIdmaven-antrun-plugin/artifactId
   executions
   execution
   phasecompile/phase
   configuration
   tasks
   echoproperties /
   /tasks
   /configuration
   goals
   goalrun/goal
   /goals
   /execution
   /executions
   dependencies
   /dependency
   groupIdant/groupId
   artifactIdant-optional/artifactId
   version1.5.3-1/version
   /dependency
   /dependencies
/plugin

I get only theses properties:

[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echoproperties] #Ant properties
[echoproperties] #Tue Feb 06 16:56:03 GMT-03:00 2007
[echoproperties] ant.project.name=DummyProject
[echoproperties] basedir=C\:\\Eclipse3.2.1\\workspace\\Atendimento
[INFO] Executed tasks

I already have try use propertyset with ant task to pass ${
project.properties} but without success.

--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
http://blastemica.blogspot.com

Re: [M2]: how to pass maven properties to ant build using antrun?



Marcos Silva Pereira wrote:
 how to pass maven properties to Ant build file.

This can be found in a frillion places, including googling for your 
subject ;-)


configuration
 tasks
  property name=foobar value=${foobar}/

You can use other attributes instead of value, check the docos around.

hth,

Manos

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

[M2] How do you control order of plugins that execute during the same phase?

2007-02-06 Thread matthewadams


If I have two unrelated plugins, A  B, that need to run during the same
build lifecycle phase, but A needs to run before B, how do I control that?

For example, say I needed some aspect weaving and some persistent
enhancement to go on during the process-classes phase, but I needed the
persistent enhancement to always execute after the aspect weaving.

Thanks,
Matthew
-- 
View this message in context: 
http://www.nabble.com/-M2--How-do-you-control-order-of-plugins-that-execute-during-the-same-phase--tf3183026s177.html#a8833972
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: MRM-60 Repository Manager should have a means to remove old snapshot builds

2007-02-06 Thread Brett Porter

I think I closed that for the report (finished) + the ability to  
process reports (not finished). That would add a 'repair all'/'remove  
all' function.


- Brett

On 07/02/2007, at 1:28 AM, Antoine Véret wrote:

Hello, in order to manage the size of a repo i would like to  
automatically

remove old snapshots.
I have seen the closed MRM-60 issue, which seems to correspond to  
my needs

but i don't find the way of remove snapshot.
This issue has been renamed, so the feature added was oldArtifact (and
oldSnapshot) reports.
Is there another issue linked with this one, or is there another  
way to do

the job?
Thanks
--
Antoine Véret

Re: [M2] How do you control order of plugins that execute during the same phase?

2007-02-06 Thread Barrie Treloar


On 2/7/07, matthewadams [EMAIL PROTECTED] wrote:


If I have two unrelated plugins, A  B, that need to run during the same
build lifecycle phase, but A needs to run before B, how do I control that?

For example, say I needed some aspect weaving and some persistent
enhancement to go on during the process-classes phase, but I needed the
persistent enhancement to always execute after the aspect weaving.


This is the same as my post
http://www.nabble.com/Re%3A--m2--how-to-control-the-plugin-execution-order-tf3178637s177.html

which links to some other threads on Nabble.

I think the answer is that you can't in 2.0.4 but may be able to in
the yet to be released 2.0.5.

Luckily for me the indeterminate order happens to be the order I want
the plugins to run in.

If plugins are at the same lifecycle they are meant to be run in the
order declared.

You may be able to fudge what  you want by binding to a later phase in
the lifecycle that is not yet being used.  See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
for the list of phases. e.g. generate-test-sources or something.

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

Re: [M2]: how to pass maven properties to ant build using antrun?

2007-02-06 Thread Marcos Silva Pereira



This can be found in a frillion places, including googling for your
subject ;-)



Really, sorry. :-)

configuration

  tasks
   property name=foobar value=${foobar}/

You can use other attributes instead of value, check the docos around.



Anyway, this is a quite verbose, especially for maven default properties.
Some good reason to not use System.setProperty? And more, there is other way
to do it? Thanks and sorry for so repeated post. :-)

--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
http://blastemica.blogspot.com

Re: dependencies are bloated in M2

2007-02-06 Thread Christian Goetze


Tandon, Pankaj wrote:




So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

I believe that the scope that should work is provided. The problem is 
that I don't know if maven is smart enough to remove a provided 
dependency from the transitive closure. I would call that a bug if it 
didn't.


--
cg

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

POM inheritance behaving unexpectedly

2007-02-06 Thread Tommy Knowlton


Hello,

I've got a parent POM that declares e.g.,

project
 …
 urlhttp://javabuild2.mycompany.com/${project.artifactId}/url
/project

(in other words, top-level configuration that varies by the project
that has declared this parent).

Problem is, when I look at the effective POM (mvn help:effective-pom),
it shows up as follows:

project
 …
 artifactIdm-installer/artifactId
 urlhttp://javabuild2.mycompany.com/m-installer/m-installer/url
project

See where the duplication is occurring? Should I expect that? How can
I use top-level config in the parent pom that uses values taken from
the child pom?

Note that the problem doesn't only occur when I use
help:effective-pom, that's just been a useful way to help me figure
out wth is going on. Also, it's not just url/ but other values that
are referred using a ${project.XYZ} form. On the other hand, inside
the child POM, I have other values that refer to ${artifactId} (not
${project.artifactId}) and these behave as I would expect.

Is this a bug in the code that resolves ${project} references?

Thanks,
--
Tommy

Re: [M2] How do you control order of plugins that execute during the same phase?

2007-02-06 Thread matthewadams

Thanks for the tip. Is there a JIRA on this?

baerrach wrote:

On 2/7/07, matthewadams [EMAIL PROTECTED] wrote:

If I have two unrelated plugins, A B, that need to run during the same
build lifecycle phase, but A needs to run before B, how do I control
that?

For example, say I needed some aspect weaving and some persistent
enhancement to go on during the process-classes phase, but I needed the
persistent enhancement to always execute after the aspect weaving.

This is the same as my post
http://www.nabble.com/Re%3A--m2--how-to-control-the-plugin-execution-order-tf3178637s177.html

which links to some other threads on Nabble.

I think the answer is that you can't in 2.0.4 but may be able to in
the yet to be released 2.0.5.

Luckily for me the indeterminate order happens to be the order I want
the plugins to run in.

If plugins are at the same lifecycle they are meant to be run in the
order declared.

You may be able to fudge what you want by binding to a later phase in
the lifecycle that is not yet being used. See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
for the list of phases. e.g. generate-test-sources or something.

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

--
View this message in context:
http://www.nabble.com/-M2--How-do-you-control-order-of-plugins-that-execute-during-the-same-phase--tf3183026s177.html#a8835982
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: dependencies are bloated in M2

2007-02-06 Thread PankajTandon


OK.. I just got the answer to my question 2a on this thread... (The rest are
still unanswered).

mvn package -X is the most useful command I found to get at the depenceny
tree. From there.. it was just a matter of excluding the extra jars. 
I wish there was a top level exclusion (maybe in the dependencyManagement
node where global exclusions could be specified.


Thanks

Pankaj


Christian Goetze-3 wrote:
 
 Tandon, Pankaj wrote:
 
 
 
So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

 I believe that the scope that should work is provided. The problem is 
 that I don't know if maven is smart enough to remove a provided 
 dependency from the transitive closure. I would call that a bug if it 
 didn't.
 
 --
 cg
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/dependencies-are-bloated-in-M2-tf3182336s177.html#a8836160
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: dependencies are bloated in M2


mvn site
see the tree of dependencies
use exclusions in your dependencies
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

On 2/6/07, Tandon, Pankaj [EMAIL PROTECTED] wrote:

Hi all,
We've been using Maven 1.1 for more that a year now and are looking to
move to M2.
With M1 our project.xml file had dependencies specified explicitly
because there was no support for transitive dependencies. As a result,
the jar files we downloaded for our webapp weighed in at about 11Meg.
While building our M2 pom.xml file(s), we kept adding dependencies (in
the pom.xml) till we got a clean compile. However now the size of the
dependent artifacts has doubled to a whopping 23Meg! And they make it to
the WEB-INF/lib increasing the size of our final artifact.

So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help. There used to be a
propertieswar.bundletrue/war.bundle/properties in the dependency
node in M1, but that is no longer available in M2. So even if I have
more depoendencies at compile time, how can I prevent my war artifact
from getting bloated?

2. How can we exclude second and third level dependencies. And IF we can
do so, how do I know what the dependency graph is for some of the
downloaded jars.
For instance, there is a jar file (that is about 3Meg in size) called
apacheds-core-0.9.jar. We know our app does not need this becuase if we
delete this file, the app works just fine.

2a. How do I find out what top level dependecny that is specified in the
pom caused a certain file to be downloaded? If we figure that out maybe
we can use the exclude element in each dependency to NOT load this
dependency.
For instance, how do I find out what top level dependency in my pom
caused this apacheds-core-0.9.jar to land up in my local repository.
Infact, this jar does not even exist on http://repo1.maven.org/maven2/
unless I google it out and find it is tucked away here
http://repo1.maven.org/maven2/directory/.

3. Is there a way to go back to explicit dependencies (non-transitive)
in the pom.xml?


Thanks in advance,
Pankaj




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

Can I get a timestamp?

Do I really have to write an entire plugin just to make a timestamp
available as a maven property?  That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.

Thanks,
Jim

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

RE: Can I get a timestamp?

You can use maven scm plugin:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
addTimestamptrue/addTimestamp
tagbuild/tag
timestampFormatMMddHHmm/timestampFormat
/configuration
/plugin

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 3:57 PM
To: Maven Users List
Subject: Can I get a timestamp?

Do I really have to write an entire plugin just to make a timestamp
available as a maven property?  That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.

Thanks,
Jim

-
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: dependencies are bloated in M2

It will. If you don't want to include a particular dependency in your
generated package just give it the provided scope, it will be excluded even
if it was a transitive dependency of something else.

Bashar

-Original Message-
From: Christian Goetze [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 2:58 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

Tandon, Pankaj wrote:

So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

I believe that the scope that should work is provided. The problem is 
that I don't know if maven is smart enough to remove a provided 
dependency from the transitive closure. I would call that a bug if it 
didn't.

--
cg

-
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: dependencies are bloated in M2


that's not the right solution, you have to use exclusions

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

It will. If you don't want to include a particular dependency in your
generated package just give it the provided scope, it will be excluded even
if it was a transitive dependency of something else.

Bashar

-Original Message-
From: Christian Goetze [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 2:58 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

Tandon, Pankaj wrote:



So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

I believe that the scope that should work is provided. The problem is
that I don't know if maven is smart enough to remove a provided
dependency from the transitive closure. I would call that a bug if it
didn't.

--
cg

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





--
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: Can I get a timestamp?

Thanks for the quick reply, but what does that do, exactly?  In which
property does it make the timestamp available?  I tried ${timestamp}
after adding that snippet to my pom, but it was empty.  What am I
missing?

Thanks,
Jim

-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 6:15 PM
To: 'Maven Users List'
Subject: RE: Can I get a timestamp?

You can use maven scm plugin:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
addTimestamptrue/addTimestamp
tagbuild/tag
timestampFormatMMddHHmm/timestampFormat
/configuration
/plugin

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 3:57 PM
To: Maven Users List
Subject: Can I get a timestamp?

Do I really have to write an entire plugin just to make a timestamp
available as a maven property?  That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.

Thanks,
Jim

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


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

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

RE: dependencies are bloated in M2

It is the right solution. Using exclusions will exclude a dependency from
being downloaded at all, which means it won't be available at any path.
Using provided will still make the dependency available for compile time,
but not in runtime, and will not bundle it in the package.

Read maven FAQ: 

http://maven.apache.org/general.html#scope-provided



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 4:29 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

that's not the right solution, you have to use exclusions

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
 It will. If you don't want to include a particular dependency in your
 generated package just give it the provided scope, it will be excluded
even
 if it was a transitive dependency of something else.

 Bashar

 -Original Message-
 From: Christian Goetze [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 06, 2007 2:58 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 Tandon, Pankaj wrote:

 
 
 So the questions are:
 1. How can we control what get's into WEB-INF/lib. We tried all the
 scopes mentioned, but that did not help.
 
 I believe that the scope that should work is provided. The problem is
 that I don't know if maven is smart enough to remove a provided
 dependency from the transitive closure. I would call that a bug if it
 didn't.

 --
 cg

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




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


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

Maven newbie question, problem with XDoclet destination directory

2007-02-06 Thread Patrick Harms


Hi All

I'm relatively new to Maven so excuse what may seem like silly questions.

At my work, I'm now working on a project that uses Maven. It has multiple
components, jars, ears, wars, etc. Up until now, it had only one EJB
project. It now has two EJB projects. Each project has its own POM file,
linked back to the Super POM. The problem I am having, is that the XDoclet
output from the generate-sources phase, for the two projects is ending up
in the same destination directory, even though the destDir attribute on the
ejbdoclet elements are different. It appears, that the second ejbdoclet
invocation ignores the destDir attribute. If I make the second destDir
attribute, rubbish it doesn't fail. If I swap the order of the EJB POMs in
the Super POM, the output is then switched.

Am I doing something obviously wrong? Or do I need to have two separate
Maven invocations.

Thanks in advance, for any assistance with this issue that I am having.

Regards
Pat Harms

RE: Can I get a timestamp?

The plug-in will allow you to use timestamp tagging to tag your builds. I am
sorry but I don't think you can access the timestamp property directly in
the pom itself. Why do you need to do that anyway?

Bashar

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 4:43 PM
To: Maven Users List
Subject: RE: Can I get a timestamp?

Thanks for the quick reply, but what does that do, exactly?  In which
property does it make the timestamp available?  I tried ${timestamp}
after adding that snippet to my pom, but it was empty.  What am I
missing?

Thanks,
Jim

-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 6:15 PM
To: 'Maven Users List'
Subject: RE: Can I get a timestamp?

You can use maven scm plugin:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
addTimestamptrue/addTimestamp
tagbuild/tag
timestampFormatMMddHHmm/timestampFormat
/configuration
/plugin

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 3:57 PM
To: Maven Users List
Subject: Can I get a timestamp?

Do I really have to write an entire plugin just to make a timestamp
available as a maven property?  That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.

Thanks,
Jim

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

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

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

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

Re: dependencies are bloated in M2


exactly, that's why he needs to use exclusions, you exclude things
that you don't need.

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

It is the right solution. Using exclusions will exclude a dependency from
being downloaded at all, which means it won't be available at any path.
Using provided will still make the dependency available for compile time,
but not in runtime, and will not bundle it in the package.

Read maven FAQ:

http://maven.apache.org/general.html#scope-provided



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 4:29 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

that's not the right solution, you have to use exclusions

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
 It will. If you don't want to include a particular dependency in your
 generated package just give it the provided scope, it will be excluded
even
 if it was a transitive dependency of something else.

 Bashar

 -Original Message-
 From: Christian Goetze [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 06, 2007 2:58 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 Tandon, Pankaj wrote:

 
 
 So the questions are:
 1. How can we control what get's into WEB-INF/lib. We tried all the
 scopes mentioned, but that did not help.
 
 I believe that the scope that should work is provided. The problem is
 that I don't know if maven is smart enough to remove a provided
 dependency from the transitive closure. I would call that a bug if it
 didn't.

 --
 cg

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




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


-
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: dependencies are bloated in M2

2007-02-06 Thread Wayne Fay


As Pankaj originally stated:
For instance, there is a jar file (that is about 3Meg in size) called
apacheds-core-0.9.jar. We know our app does not need this becuase if we
delete this file, the app works just fine.

He needs to use exclusions for this as he does not need this
dependency for anything, in any scope, at any time.

Wayne

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

It is the right solution. Using exclusions will exclude a dependency from
being downloaded at all, which means it won't be available at any path.
Using provided will still make the dependency available for compile time,
but not in runtime, and will not bundle it in the package.

Read maven FAQ:

http://maven.apache.org/general.html#scope-provided



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 4:29 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

that's not the right solution, you have to use exclusions

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
 It will. If you don't want to include a particular dependency in your
 generated package just give it the provided scope, it will be excluded
even
 if it was a transitive dependency of something else.

 Bashar

 -Original Message-
 From: Christian Goetze [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 06, 2007 2:58 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 Tandon, Pankaj wrote:

 
 
 So the questions are:
 1. How can we control what get's into WEB-INF/lib. We tried all the
 scopes mentioned, but that did not help.
 
 I believe that the scope that should work is provided. The problem is
 that I don't know if maven is smart enough to remove a provided
 dependency from the transitive closure. I would call that a bug if it
 didn't.

 --
 cg

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




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


-
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: dependencies are bloated in M2


This is the question I was answering:

Tandon, Pankaj wrote:

1. How can we control what get's into WEB-INF/lib. We tried all the 
scopes mentioned, but that did not help.

And it's follow up:

 Christian Goetze wrote:
 
  I believe that the scope that should work is provided. The problem is
  that I don't know if maven is smart enough to remove a provided
  dependency from the transitive closure. I would call that a bug if it
  didn't.

And the answer to these 2 questions is to use the provided scope. It will
also stop a dependency from being passed on transitively. Using exclusions
is NOT right if you still want to compile against these dependencies.

Bashar


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 5:02 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

exactly, that's why he needs to use exclusions, you exclude things
that you don't need.

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
 It is the right solution. Using exclusions will exclude a dependency from
 being downloaded at all, which means it won't be available at any path.
 Using provided will still make the dependency available for compile time,
 but not in runtime, and will not bundle it in the package.

 Read maven FAQ:

 http://maven.apache.org/general.html#scope-provided



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
 Sanchez
 Sent: Tuesday, February 06, 2007 4:29 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 that's not the right solution, you have to use exclusions

 On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It will. If you don't want to include a particular dependency in your
  generated package just give it the provided scope, it will be excluded
 even
  if it was a transitive dependency of something else.
 
  Bashar
 
  -Original Message-
  From: Christian Goetze [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, February 06, 2007 2:58 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  Tandon, Pankaj wrote:
 
  
  
  So the questions are:
  1. How can we control what get's into WEB-INF/lib. We tried all the
  scopes mentioned, but that did not help.
  
  I believe that the scope that should work is provided. The problem is
  that I don't know if maven is smart enough to remove a provided
  dependency from the transitive closure. I would call that a bug if it
  didn't.
 
  --
  cg
 
  -
  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]
 
 


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


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


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

Re: dependencies are bloated in M2

2007-02-06 Thread Craig McClanahan


On 2/6/07, Carlos Sanchez [EMAIL PROTECTED] wrote:


exactly, that's why he needs to use exclusions, you exclude things
that you don't need.



Exclusions can get you around immediate build problems, but a feedback loop
is necessary to improve the state of the world in general, or the problem
will just repeat itself the next time.

If your project has a dependency x, and that artifact has an optional
dependency y, the POM for x should explicity *say* it is optional.  That
will cause the web project to do the right thing ... *not* copy in the
optional dependencies unless you explicitly declare a dependency on them
yourself.

Thus, people who published depency x in this scenario need to be lobbied
to get their POMs fixed in the next version, to stop causing everyone who
uses Maven and their x library grief down the road.

A classic case that I know of personally :-) is Jakarta Commons Logging,
where the 1.1 version of the POM declares a dependency on the servlet API
but mistakenly did not declare it to be optional.  Yes, you as a user of
Commons Logging can use an exclusion to get rid of the unwanted file, but
why should you (or anyone else) *have* to?  Wouldn't the right thing be to
also go file a bug against C-L to fix their blasted POM?

(You don't actually have to for this particular scenario ... the POM has
been fixed in the trunk and a 1.1.1 release is likely very soon primarily to
address this issue ... but my point is in general it is the people who
publish broken POMs that should be complained at here, not Maven itself.)

Craig McClanahan


On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

 It is the right solution. Using exclusions will exclude a dependency
from
 being downloaded at all, which means it won't be available at any path.
 Using provided will still make the dependency available for compile
time,
 but not in runtime, and will not bundle it in the package.

 Read maven FAQ:

 http://maven.apache.org/general.html#scope-provided



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
 Sanchez
 Sent: Tuesday, February 06, 2007 4:29 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 that's not the right solution, you have to use exclusions

 On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It will. If you don't want to include a particular dependency in your
  generated package just give it the provided scope, it will be excluded
 even
  if it was a transitive dependency of something else.
 
  Bashar
 
  -Original Message-
  From: Christian Goetze [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, February 06, 2007 2:58 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  Tandon, Pankaj wrote:
 
  
  
  So the questions are:
  1. How can we control what get's into WEB-INF/lib. We tried all the
  scopes mentioned, but that did not help.
  
  I believe that the scope that should work is provided. The problem
is
  that I don't know if maven is smart enough to remove a provided
  dependency from the transitive closure. I would call that a bug if it
  didn't.
 
  --
  cg
 
  -
  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]
 
 


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


 -
 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: dependencies are bloated in M2


still not right, you have to use exclusions
provided means the environment (read appserver) provides that
dependency, which is only true for few dependencies in the whole
world, like servlet-api

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:


This is the question I was answering:

Tandon, Pankaj wrote:

1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

And it's follow up:

 Christian Goetze wrote:
 
  I believe that the scope that should work is provided. The problem is
  that I don't know if maven is smart enough to remove a provided
  dependency from the transitive closure. I would call that a bug if it
  didn't.

And the answer to these 2 questions is to use the provided scope. It will
also stop a dependency from being passed on transitively. Using exclusions
is NOT right if you still want to compile against these dependencies.

Bashar


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 5:02 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

exactly, that's why he needs to use exclusions, you exclude things
that you don't need.

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
 It is the right solution. Using exclusions will exclude a dependency from
 being downloaded at all, which means it won't be available at any path.
 Using provided will still make the dependency available for compile time,
 but not in runtime, and will not bundle it in the package.

 Read maven FAQ:

 http://maven.apache.org/general.html#scope-provided



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
 Sanchez
 Sent: Tuesday, February 06, 2007 4:29 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 that's not the right solution, you have to use exclusions

 On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It will. If you don't want to include a particular dependency in your
  generated package just give it the provided scope, it will be excluded
 even
  if it was a transitive dependency of something else.
 
  Bashar
 
  -Original Message-
  From: Christian Goetze [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, February 06, 2007 2:58 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  Tandon, Pankaj wrote:
 
  
  
  So the questions are:
  1. How can we control what get's into WEB-INF/lib. We tried all the
  scopes mentioned, but that did not help.
  
  I believe that the scope that should work is provided. The problem is
  that I don't know if maven is smart enough to remove a provided
  dependency from the transitive closure. I would call that a bug if it
  didn't.
 
  --
  cg
 
  -
  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]
 
 


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


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


-
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: dependencies are bloated in M2


everything you said is right ;)
in an ideal world the only reason to use exclusions is if you are not
using a portion of the library that the developer consider required
for most of the people

On 2/6/07, Craig McClanahan [EMAIL PROTECTED] wrote:

On 2/6/07, Carlos Sanchez [EMAIL PROTECTED] wrote:

 exactly, that's why he needs to use exclusions, you exclude things
 that you don't need.


Exclusions can get you around immediate build problems, but a feedback loop
is necessary to improve the state of the world in general, or the problem
will just repeat itself the next time.

If your project has a dependency x, and that artifact has an optional
dependency y, the POM for x should explicity *say* it is optional.  That
will cause the web project to do the right thing ... *not* copy in the
optional dependencies unless you explicitly declare a dependency on them
yourself.

Thus, people who published depency x in this scenario need to be lobbied
to get their POMs fixed in the next version, to stop causing everyone who
uses Maven and their x library grief down the road.

A classic case that I know of personally :-) is Jakarta Commons Logging,
where the 1.1 version of the POM declares a dependency on the servlet API
but mistakenly did not declare it to be optional.  Yes, you as a user of
Commons Logging can use an exclusion to get rid of the unwanted file, but
why should you (or anyone else) *have* to?  Wouldn't the right thing be to
also go file a bug against C-L to fix their blasted POM?

(You don't actually have to for this particular scenario ... the POM has
been fixed in the trunk and a 1.1.1 release is likely very soon primarily to
address this issue ... but my point is in general it is the people who
publish broken POMs that should be complained at here, not Maven itself.)

Craig McClanahan


On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It is the right solution. Using exclusions will exclude a dependency
 from
  being downloaded at all, which means it won't be available at any path.
  Using provided will still make the dependency available for compile
 time,
  but not in runtime, and will not bundle it in the package.
 
  Read maven FAQ:
 
  http://maven.apache.org/general.html#scope-provided
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
  Sanchez
  Sent: Tuesday, February 06, 2007 4:29 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  that's not the right solution, you have to use exclusions
 
  On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
   It will. If you don't want to include a particular dependency in your
   generated package just give it the provided scope, it will be excluded
  even
   if it was a transitive dependency of something else.
  
   Bashar
  
   -Original Message-
   From: Christian Goetze [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, February 06, 2007 2:58 PM
   To: Maven Users List
   Subject: Re: dependencies are bloated in M2
  
   Tandon, Pankaj wrote:
  
   
   
   So the questions are:
   1. How can we control what get's into WEB-INF/lib. We tried all the
   scopes mentioned, but that did not help.
   
   I believe that the scope that should work is provided. The problem
 is
   that I don't know if maven is smart enough to remove a provided
   dependency from the transitive closure. I would call that a bug if it
   didn't.
  
   --
   cg
  
   -
   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]
  
  
 
 
  --
  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]
 
 
  -
  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: Can't deploy site,Help please.

2007-02-06 Thread sam


Hi,
   yes,I have solved the issue by used file:///path/to/deployment/dir*, *
thanks.


2007/2/6, Tim Kettler [EMAIL PROTECTED]:


Hi,

the URL you give in the distribution management section is the HTTP URL
of your projects site. To deploy it you need to specify a valid
deployment URL. This could be something like:

- scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
- sftp://my.server.com/deployment/dir (for SFTP deployment)
- file:///path/to/deployment/dir (for deploying to a local file system)

Hope this helps
-Tim

Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the url
is
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 distributionManagement
   site
idmaven/id
urlscp://localhost:8080/pcie//url
   /site
  /distributionManagement

 I have start up the server successfull as well as I Have execute site
 command,but when I execute site-deploy,I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
site
  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.embedder.MavenEmbedder.execute(MavenEmbedder.java
:441)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
:382)
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
SiteDeployMojo.java
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by: org.apache.maven.wagon.authentication.AuthenticationException
:
 Cannot connect. Reason: invalid server's version string
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
 AbstractSshWagon.java:239)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
  at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
SiteDeployMojo.java
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
string
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?


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

RE: dependencies are bloated in M2

Yes, but sometimes you will need to use a dependency for compile time only,
and NOT for runtime. You don't need the container to provide it for you
either because it is not required for runtime. Example: aspectjtools.jar.
You can't exclude it because your project will not compile. The only way is
to give it the provided scope. Even if your container doesn't provide it
that's not a problem, maven doesn't care. I know it is not very clean to
give a dependency a provided scope when it's not going to be provided
anywhere, but sometimes you need to do this if you want to compile against
it.

Bashar

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 5:18 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

still not right, you have to use exclusions
provided means the environment (read appserver) provides that
dependency, which is only true for few dependencies in the whole
world, like servlet-api

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

 This is the question I was answering:

 Tandon, Pankaj wrote:
 
 1. How can we control what get's into WEB-INF/lib. We tried all the
 scopes mentioned, but that did not help.

 And it's follow up:

  Christian Goetze wrote:
  
   I believe that the scope that should work is provided. The problem
is
   that I don't know if maven is smart enough to remove a provided
   dependency from the transitive closure. I would call that a bug if it
   didn't.

 And the answer to these 2 questions is to use the provided scope. It will
 also stop a dependency from being passed on transitively. Using exclusions
 is NOT right if you still want to compile against these dependencies.

 Bashar


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
 Sanchez
 Sent: Tuesday, February 06, 2007 5:02 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 exactly, that's why he needs to use exclusions, you exclude things
 that you don't need.

 On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It is the right solution. Using exclusions will exclude a dependency
from
  being downloaded at all, which means it won't be available at any path.
  Using provided will still make the dependency available for compile
time,
  but not in runtime, and will not bundle it in the package.
 
  Read maven FAQ:
 
  http://maven.apache.org/general.html#scope-provided
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
  Sanchez
  Sent: Tuesday, February 06, 2007 4:29 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  that's not the right solution, you have to use exclusions
 
  On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
   It will. If you don't want to include a particular dependency in your
   generated package just give it the provided scope, it will be excluded
  even
   if it was a transitive dependency of something else.
  
   Bashar
  
   -Original Message-
   From: Christian Goetze [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, February 06, 2007 2:58 PM
   To: Maven Users List
   Subject: Re: dependencies are bloated in M2
  
   Tandon, Pankaj wrote:
  
   
   
   So the questions are:
   1. How can we control what get's into WEB-INF/lib. We tried all the
   scopes mentioned, but that did not help.
   
   I believe that the scope that should work is provided. The problem
is
   that I don't know if maven is smart enough to remove a provided
   dependency from the transitive closure. I would call that a bug if it
   didn't.
  
   --
   cg
  
   -
   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]
  
  
 
 
  --
  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]
 
 
  -
  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]


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

Re: dependencies are bloated in M2


build dependencies are added in plugin dependencies section so they
don't interfere with your code dependencies

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

Yes, but sometimes you will need to use a dependency for compile time only,
and NOT for runtime. You don't need the container to provide it for you
either because it is not required for runtime. Example: aspectjtools.jar.
You can't exclude it because your project will not compile. The only way is
to give it the provided scope. Even if your container doesn't provide it
that's not a problem, maven doesn't care. I know it is not very clean to
give a dependency a provided scope when it's not going to be provided
anywhere, but sometimes you need to do this if you want to compile against
it.

Bashar

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 5:18 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

still not right, you have to use exclusions
provided means the environment (read appserver) provides that
dependency, which is only true for few dependencies in the whole
world, like servlet-api

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:

 This is the question I was answering:

 Tandon, Pankaj wrote:
 
 1. How can we control what get's into WEB-INF/lib. We tried all the
 scopes mentioned, but that did not help.

 And it's follow up:

  Christian Goetze wrote:
  
   I believe that the scope that should work is provided. The problem
is
   that I don't know if maven is smart enough to remove a provided
   dependency from the transitive closure. I would call that a bug if it
   didn't.

 And the answer to these 2 questions is to use the provided scope. It will
 also stop a dependency from being passed on transitively. Using exclusions
 is NOT right if you still want to compile against these dependencies.

 Bashar


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
 Sanchez
 Sent: Tuesday, February 06, 2007 5:02 PM
 To: Maven Users List
 Subject: Re: dependencies are bloated in M2

 exactly, that's why he needs to use exclusions, you exclude things
 that you don't need.

 On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  It is the right solution. Using exclusions will exclude a dependency
from
  being downloaded at all, which means it won't be available at any path.
  Using provided will still make the dependency available for compile
time,
  but not in runtime, and will not bundle it in the package.
 
  Read maven FAQ:
 
  http://maven.apache.org/general.html#scope-provided
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
  Sanchez
  Sent: Tuesday, February 06, 2007 4:29 PM
  To: Maven Users List
  Subject: Re: dependencies are bloated in M2
 
  that's not the right solution, you have to use exclusions
 
  On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
   It will. If you don't want to include a particular dependency in your
   generated package just give it the provided scope, it will be excluded
  even
   if it was a transitive dependency of something else.
  
   Bashar
  
   -Original Message-
   From: Christian Goetze [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, February 06, 2007 2:58 PM
   To: Maven Users List
   Subject: Re: dependencies are bloated in M2
  
   Tandon, Pankaj wrote:
  
   
   
   So the questions are:
   1. How can we control what get's into WEB-INF/lib. We tried all the
   scopes mentioned, but that did not help.
   
   I believe that the scope that should work is provided. The problem
is
   that I don't know if maven is smart enough to remove a provided
   dependency from the transitive closure. I would call that a bug if it
   didn't.
  
   --
   cg
  
   -
   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]
  
  
 
 
  --
  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]
 
 
  -
  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

maven-ear-plugin not found during cobertura:clean

2007-02-06 Thread Trevor Torrez


I have two boxes using the same install of maven and a project which
consists of a parent and 4 children: two jars, one war, one ear.  On one box
everything works fine, on the other, running 'mvn clean' causes the
triggered 'cobertura:clean' to fail in the ear-project complaining that it
cannot find the maven-ear-plugin or a valid version of it.  What could be
causing this failure on one box and not the other?

Re: [M2] How do you control order of plugins that execute during the same phase?

2007-02-06 Thread Barrie Treloar

Don't know, I asked the same question on my post. Haven't seen an answer yet.

On 2/7/07, matthewadams [EMAIL PROTECTED] wrote:

Thanks for the tip. Is there a JIRA on this?

baerrach wrote:

On 2/7/07, matthewadams [EMAIL PROTECTED] wrote:

If I have two unrelated plugins, A B, that need to run during the same
build lifecycle phase, but A needs to run before B, how do I control
that?

This is the same as my post

http://www.nabble.com/Re%3A--m2--how-to-control-the-plugin-execution-order-tf3178637s177.html

which links to some other threads on Nabble.

I think the answer is that you can't in 2.0.4 but may be able to in
the yet to be released 2.0.5.

Luckily for me the indeterminate order happens to be the order I want
the plugins to run in.

If plugins are at the same lifecycle they are meant to be run in the
order declared.

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

RE: Can I get a timestamp?

2007-02-06 Thread Greg Jones

Kim,

You can use the maven-buildnumber-plugin to get a timestamp, as follows:

  plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-buildnumber-plugin/artifactId
version0.9.4/version
configuration
  format{0,date,-MM-dd HH:mm:ss}/format
  items
itemtimestamp/item
  /items
  doCheckfalse/doCheck
  doUpdatefalse/doUpdate
/configuration
executions
  execution
phasevalidate/phase
goals
  goalcreate/goal
/goals
  /execution
/executions
  /plugin 

The timestamp is put into the ${buildNumber} property. You can also adjust
the format of the timestamp to suit your requirements. Take a look at
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html for
information on how it works.

Regards,

Greg J.

-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 7 February 2007 11:03 AM
To: 'Maven Users List'
Subject: RE: Can I get a timestamp?

The plug-in will allow you to use timestamp tagging to tag your builds. I am
sorry but I don't think you can access the timestamp property directly in
the pom itself. Why do you need to do that anyway?

Bashar

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 4:43 PM
To: Maven Users List
Subject: RE: Can I get a timestamp?

Thanks for the quick reply, but what does that do, exactly?  In which
property does it make the timestamp available?  I tried ${timestamp} after
adding that snippet to my pom, but it was empty.  What am I missing?

Thanks,
Jim

-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 6:15 PM
To: 'Maven Users List'
Subject: RE: Can I get a timestamp?

You can use maven scm plugin:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
addTimestamptrue/addTimestamp
tagbuild/tag
timestampFormatMMddHHmm/timestampFormat
/configuration
/plugin

-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 3:57 PM
To: Maven Users List
Subject: Can I get a timestamp?

Do I really have to write an entire plugin just to make a timestamp
available as a maven property?  That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.

Thanks,
Jim

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


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

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


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


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

Re: dependencies are bloated in M2

2007-02-06 Thread Edwin Punzalan



I don't undestand this... since when did compile-time libraries become 
not needed in runtime ?  even servlet-api is needed at runtime, its just 
that they're being provided by the containers.  Please use exclusions.


From how I see it, let's say we have Artifacts A, B and C.  A depends 
on B and C depends on A.


If C doesn't need use the portion of A that uses the library B, then C 
can put an exclude clause for B in his dependency in A.  That will work.


But if you put B as provided in A, then that may only be correct for C.  
What if there is another artifact D that depends on A entirely, 
including the portion which uses B ?  you then add dependency B into D's 
pom.  Then later on, you'll say why does D depend on B?  its not 
logically correct anymore.  So using exclusions is more appropriate.



Hope that helps.


^_^


Bashar Abdul Jawad wrote:

It is the right solution. Using exclusions will exclude a dependency from
being downloaded at all, which means it won't be available at any path.
Using provided will still make the dependency available for compile time,
but not in runtime, and will not bundle it in the package.

Read maven FAQ: 


http://maven.apache.org/general.html#scope-provided



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Tuesday, February 06, 2007 4:29 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

that's not the right solution, you have to use exclusions

On 2/6/07, Bashar Abdul Jawad [EMAIL PROTECTED] wrote:
  

It will. If you don't want to include a particular dependency in your
generated package just give it the provided scope, it will be excluded


even
  

if it was a transitive dependency of something else.

Bashar

-Original Message-
From: Christian Goetze [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 2:58 PM
To: Maven Users List
Subject: Re: dependencies are bloated in M2

Tandon, Pankaj wrote:



So the questions are:
1. How can we control what get's into WEB-INF/lib. We tried all the
scopes mentioned, but that did not help.

  

I believe that the scope that should work is provided. The problem is
that I don't know if maven is smart enough to remove a provided
dependency from the transitive closure. I would call that a bug if it
didn't.

--
cg

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


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






  


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

RE: Can I get a timestamp?