date:20061204

Hello,

We're using maven for internal development. Since the internet as a whole 
and our connection to it especially are not always reliable (for example, 
a new version of a virus checker sometimes starts to block out maven 
downloads), we wanted to use Archiva as a local cache of the central maven 
repositories.

As it is right now, I have to configure each repository individually. What 
we would prefer is a setting which makes Archiva the default proxy for 
maven so all external connections are made over it.

This would allow us to keep local copies of all artefacts so internet 
outages wouldn't affect us anymore. Also, we could fix broken packages 
locally. Ideally, there should be two caches: One with stable version for 
development and one which can update itself with the current versions from 
the internet.

Is this possible?

Regards,

-- 
Aaron Digulla

maven-javadoc-plugin fails to find packages and classes

2006-12-04 Thread Steinar Bang

Platform: Intel Pentium M,
  Ubuntu Dapper Drake,
  Sun java 1.5.0_06,
  maven 2.0.4,
  maven-javadoc-plugin 2.0

I'm trying to run aggregate javadoc on a multiproject, and I'm getting
errors when it runs into packages and classes outside of the project
(ie. from jar files pulled down from my local repo).

I wonder if I've run into the problem described here?
http://jira.codehaus.org/browse/MJAVADOC-72

And if I have run into the problem, is there something (simple) I
could do to fix it?  (eg. put in a version tag to some version where
it works?)  Is eg. version 2.1 mentioned in the above bug released?
(but if so, why isn't my maven already using it, since I currently
have no version tag in the pom.xml?)

Thanx!


- Steinar


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

RE: Proxy settings

2006-12-04 Thread Mohni, Daniel

Hello Aaron

this can be done setting the mirror in settings.xml

 mirrors
   mirror
 idproxy.central/id
mirrorOfcentral/mirrorOf
nameInternal Mirror of central./name
urlhttp://archiva/proxy/maven_release/url
/mirror
  /mirrors

- if you use proxy in the url then archiva will try to download
   missing artefacts from the proxied repo setup in archiva

http://archiva/proxy/maven_release
   
- if you use repository in the url then archiva will only be
   a cache provider for your already downloaded artefacts

http://archiva/repository/maven_release

maven_release is our internal proxy repository...

I don't know if this is still like this in the current daily build
as I didn't tried it...

hth

Daniel

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 04, 2006 11:19 AM
 To: archiva-users@maven.apache.org
 Subject: Proxy settings
 
 Hello,
 
 We're using maven for internal development. Since the 
 internet as a whole 
 and our connection to it especially are not always reliable 
 (for example, 
 a new version of a virus checker sometimes starts to block out maven 
 downloads), we wanted to use Archiva as a local cache of the 
 central maven 
 repositories.
 
 As it is right now, I have to configure each repository 
 individually. What 
 we would prefer is a setting which makes Archiva the default 
 proxy for 
 maven so all external connections are made over it.
 
 This would allow us to keep local copies of all artefacts so internet 
 outages wouldn't affect us anymore. Also, we could fix broken 
 packages 
 locally. Ideally, there should be two caches: One with stable 
 version for 
 development and one which can update itself with the current 
 versions from 
 the internet.
 
 Is this possible?
 
 Regards,
 
 -- 
 Aaron Digulla

Re: dependencies on eclipse 3.2 plugins

2006-12-04 Thread Bhupendra Bhardwaj


Thanks Tom,

That was very helpful.

Regards,
Bhupendra


On 12/2/06, Tom Huybrechts [EMAIL PROTECTED] wrote:


There is a Maven repository with the Eclipse bundles at
http://repo1.maven.org/eclipse/
I don't expect this to be around forever, but I guess it will
eventually be integrated in the central repository.

On 12/2/06, Bhupendra Bhardwaj [EMAIL PROTECTED] wrote:
 Hi,

 I have developed an eclipse RCP and it can run as an standalone
application.
 Now I need to do a maven build for it. This project will be part of
another
 open source project. As the eclipse plugins are not available in maven
 repository, do I need to add those plugins like swt3.2.., jface3.2 etc
etc
 in the repository?
 I know that eclipse doesn't ship these as seperate plugins.
 If the jars are available in maven repository, then I can just add the
 dependency in the pom file, but for these eclipse plugin jars what can
be
 done?

 any pointers in the right direction will be helpful.

 Regards,
 Bhupendra



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

Continuum Clearcase

2006-12-04 Thread Robert Langridge

 
Hi All,

I have a project that uses clearcase for scm. The viewstore location is
not the default so I created a .scm folder in the location of the
pom.xml file and added a clearcase-settings.xml file with the location
of the viewstore as instructed by the maven site.

However when I come to run the project through continuum, it's like it
doesn't pick up the .scm folder and tries to use the default viewstore
location causing an error.

Does anyone have any suggestions?

Thanks a lot!

Rob Langridge 


This communication together with any attachments transmitted with it (this 
E-Mail) is intended only for the use of the addressee and may contain 
information which is privileged and confidential.  If the reader of this E-Mail 
is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient you are hereby notified that any use, 
dissemination, forwarding, printing or copying of this E-Mail is strictly 
prohibited.  Addressees should check this E-mail for viruses.  The Company 
makes no representations as regards the absence of viruses in this E-Mail.  If 
you have received this E-Mail in error please notify our IT Service Desk 
immediately by e-mail at [EMAIL PROTECTED]  Please then immediately delete, 
erase or otherwise destroy this E-Mail and any copies of it.

Any opinions expressed in this E-Mail are those of the author and do not 
necessarily constitute the views of the Company.  Nothing in this E-Mail shall 
bind the Company in any contract or obligation.

For the purposes of this E-Mail the Company means The Carphone Warehouse 
Group Plc and/or any of its subsidiaries.

Please feel free to visit our website:  http:// www.carphonewarehouse.com or 
http://www.phonehouse.com

The Carphone Warehouse Group Plc (Registered in England No. 3253714) 1 Portal 
Way, London W3 6RS


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

Surefire tests occasionally failing because the classpath is wrong

2006-12-04 Thread Nigel Magnay


In my multiproject, I use commons-lang. In my pom.xml (atend) I have the
dependency set (excluded once to avoid a conflict).

However, the build sometimes fails, but not always, trying to find a class
in commons-lang. Doing a mvn -X shows it isn't present
on the test classpath.

Is there some way I can persuade it to be on the classpath correctly?

dependency
 groupIdacegisecurity/groupId
 artifactIdacegi-security/artifactId
 version1.0.0/version
 exclusions
   exclusion
 !-- don't use this old version of commons-lang --
 artifactIdcommons-lang/artifactId
 groupIdcommons-lang/groupId
   /exclusion
...
dependency
...
dependency
 !-- this ought to be fetched transitively --
 groupIdcommons-lang/groupId
 artifactIdcommons-lang/artifactId
 version2.1/version
 typejar/type
 scopetest/scope
   /dependency

AW: Re: dependencies on eclipse 3.2 plugins

2006-12-04 Thread thorsten

Hi,

which maven plugin do you use for building your rcp application or eclipse 
plugins? Do you have a sample pom.xml for me? 


Best Regards,
Thorsten


Thanks Tom,

That was very helpful.

Regards,
Bhupendra


On 12/2/06, Tom Huybrechts [EMAIL PROTECTED] wrote:

 There is a Maven repository with the Eclipse bundles at
 http://repo1.maven.org/eclipse/
 I don't expect this to be around forever, but I guess it will
 eventually be integrated in the central repository.

 On 12/2/06, Bhupendra Bhardwaj [EMAIL PROTECTED] wrote:
  Hi,
 
  I have developed an eclipse RCP and it can run as an standalone
 application.
  Now I need to do a maven build for it. This project will be part of
 another
  open source project. As the eclipse plugins are not available in maven
  repository, do I need to add those plugins like swt3.2.., jface3.2 etc
 etc
  in the repository?
  I know that eclipse doesn't ship these as seperate plugins.
  If the jars are available in maven repository, then I can just add the
  dependency in the pom file, but for these eclipse plugin jars what can
 be
  done?
 
  any pointers in the right direction will be helpful.
 
  Regards,
  Bhupendra
 
 

 -
 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 and jar

2006-12-04 Thread Khabot, Zakaria

Hi all,

I'm new in maven.

I'm trying to execute maven withing eclipse.

How to customise jar-plugin so to put src directory, the name of the
jar

Thanks



This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

EAR plugin problem

2006-12-04 Thread Lars Rosenberg Nielsen

I have a problem with configuring the EAR plugin so it copies the depended jar 
files to by APP-INF/lib directory in the EAR file; the plugin places the jar 
files in the root directory, which makes my deployment fail. See the 
configuration of the EAR file below. Can anyone point me to a fix?

  build
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
defaultLibBundleDirAPP-INF/lib/defaultLibBundleDir
   modules
 ejbModule
 ...
 /ejbModule
  /modules
/configuration
  /plugin
/plugins
  /build




Best regards

Lars Rosenberg Nielsen, 
SI Center of Excellence


All manner of good things come from writing less code: delivery of business 
value in much less time; a far less complex code base which is then much easier 
to change and maintain; and less technical debt accumulated over the long term



-

Alt i én. Få Yahoo! Mail med adressekartotek, kalender og notesblok.

Re: EAR plugin problem


Try defaultJavaBundleDirAPP-INF/lib/defaultJavaBundleDir instead.  I
believe the BBwMaven book is inaccurate at this point.

-aps

On 12/4/06, Lars Rosenberg Nielsen [EMAIL PROTECTED] wrote:


I have a problem with configuring the EAR plugin so it copies the depended
jar files to by APP-INF/lib directory in the EAR file; the plugin places the
jar files in the root directory, which makes my deployment fail. See the
configuration of the EAR file below. Can anyone point me to a fix?

  build
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
defaultLibBundleDirAPP-INF/lib/defaultLibBundleDir
   modules
 ejbModule
 ...
 /ejbModule
  /modules
/configuration
  /plugin
/plugins
  /build




Best regards

Lars Rosenberg Nielsen,
SI Center of Excellence


All manner of good things come from writing less code: delivery of
business value in much less time; a far less complex code base which is then
much easier to change and maintain; and less technical debt accumulated over
the long term



-

Alt i én. Få Yahoo! Mail med adressekartotek, kalender og notesblok.





--
What lies behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson

[M2] Unable Disable a Repository?


Hi 

I need to find out how to undisable a repository, when Maven 
thinks it is unavailable.

(Testing an internal repository with an artifacts which Maven claims it
is missing,
but actually does exist. )

[DEBUG] Skipping disabled repository ptsp-internal
[INFO] snapshot com.ubs.firc.ptsp:xmlbeans-cse:0.1-SNAPSHOT: checking
for updates from ptsp-repository
[DEBUG] repository metadata for: 'snapshot
com.ubs.firc.ptsp:xmlbeans-cse:0.1-SNAPSHOT' could not be found on
repository: ptsp-repository
[DEBUG] Skipping disabled repository central
[DEBUG] xmlbeans-cse: using locally installed snapshot
[DEBUG] Skipping disabled repository ptsp-internal
[DEBUG] Trying repository ptsp-repository
Downloading:
file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository/com/ubs/firc/ptsp/xm
lbeans-cse/0.1-SNAPSHOT/xmlbeans-cse-0.1-SNAPSHOT.pom
[WARNING] Unable to get resource from repository ptsp-repository
(file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository)
[DEBUG] Skipping disabled repository central
[DEBUG] Artifact not found - using stub model: Unable to download the
artifact from any repository

  com.ubs.firc.ptsp:xmlbeans-cse:pom:0.1-SNAPSHOT

from the specified remote repositories:


--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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

Antwort: RE: Proxy settings

Hi Daniel,

What do I do if POM.xml of a plugin says this:

repositories
repository
idapache-snapshots/id
nameSnapshot repository/name
urlhttp://people.apache.org/maven-snapshot-repository//url
/repository
/repositories

but the plugin cannot be found in this repository? Like in the JSP 
compiler maven plugin from codehaus.

My problem is the id. Every project defines their own id. For some, it's 
codehaus, for others it's codehaus.org. For another group, codehaus 
is for releases, while codehaus.org is for snapshots.

This means the id *cannot* be used to map mirrors to URLs.

Therefore, I need a solution in archiva which I can feed with arbitrary 
URLs and which either goes to a stable inhouse repository or downloads the 
resource from the URL and caches it.

Having users define proxied repositories manually and map them to managed 
repositories is not the solution, it's another layer of problems. Archia 
should support a generic proxy/cache which just stores a resource under an 
URL. So when I ask for apache.org/.../plugin-1.3.pom and for 
codehaus.org/.../plugin-1.3.pom, I should get two different files if they 
are different on the respective servers.

On disk, you can just use the hostname as the first item in the path to 
distinguish between the different artefacts.

In the webapp, it should be possible to freeze certain URLs (for 
example, if the files on the web are broken or I'm using a patched version 
inhouse).

With this solution, I could use the Maven proxy settings (instead of the 
broken mirror stuff) to download artefacts for my development team *once*.

Regards,

-- 
Aaron Digulla

Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 
11:31:28:

 Hello Aaron
 
 this can be done setting the mirror in settings.xml
 
  mirrors
mirror
  idproxy.central/id
mirrorOfcentral/mirrorOf
 nameInternal Mirror of central./name
urlhttp://archiva/proxy/maven_release/url
 /mirror
   /mirrors
 
 - if you use proxy in the url then archiva will try to download
missing artefacts from the proxied repo setup in archiva
 
http://archiva/proxy/maven_release
 
 - if you use repository in the url then archiva will only be
a cache provider for your already downloaded artefacts
 
http://archiva/repository/maven_release
 
 maven_release is our internal proxy repository...
 
 I don't know if this is still like this in the current daily build
 as I didn't tried it...
 
 hth
 
 Daniel
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sent: Monday, December 04, 2006 11:19 AM
  To: archiva-users@maven.apache.org
  Subject: Proxy settings
  
  Hello,
  
  We're using maven for internal development. Since the 
  internet as a whole 
  and our connection to it especially are not always reliable 
  (for example, 
  a new version of a virus checker sometimes starts to block out maven 
  downloads), we wanted to use Archiva as a local cache of the 
  central maven 
  repositories.
  
  As it is right now, I have to configure each repository 
  individually. What 
  we would prefer is a setting which makes Archiva the default 
  proxy for 
  maven so all external connections are made over it.
  
  This would allow us to keep local copies of all artefacts so internet 
  outages wouldn't affect us anymore. Also, we could fix broken 
  packages 
  locally. Ideally, there should be two caches: One with stable 
  version for 
  development and one which can update itself with the current 
  versions from 
  the internet.
  
  Is this possible?
  
  Regards,
  
  -- 
  Aaron Digulla

RE: MAVEN_INSTALL_DIR/conf/settings.xml

 -Original Message-
 From: Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) 
====

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
  Sent: Friday, December 01, 2006 2:53 AM
  To: users@maven.apache.org
  Subject: RE: MAVEN_INSTALL_DIR/conf/settings.xml

   -Original Message-
   From: Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) 
   [mailto:[EMAIL PROTECTED]
   Sent: 01 December 2006 00:15
   To: Maven Users List
   Subject: RE: MAVEN_INSTALL_DIR/conf/settings.xml

   I tried the suggestion below for invoking Maven and it
  worked.  I also
   defined the maven.repo.local property in the ant script for
  our mixed
   build, hoping antlib would pick up on it and use the same local 
   repository for the Maven ant tasks.  No such luck.

   It seems there is no way to pass the location of the local
  repository
   to antlib except through ~/.m2/settings.xml or
  ~/.m2/ant/settings.xml.  
   Thus there is no way to have multiple repositories per user 
   simultaneously.  I will file a JIRA request for an enhancement.

  Hi Jason et Al

  We need to export some important system variables through Maven 2 
  Ant[Run] and Exec similar plugins. Perhaps the developer 
 can devise a 
  way to create or export system variables as environment variables 
  generally through Maven core.

  Marilyn

  I also worked around this problem by using `sed' on UNIX 
 with a simple 
  placeholder inside `settings.xml.in'.

  I did it in a shell script that called Maven like this

  /bin/rm -rf ${XYZ_M2_LOCAL}/settings.xml sed -e 
  's,@BUILD_REPO@,'${XYZ_M2_LOCAL_REPO}',g'
  src/release-control/settings.xml.in   ${XYZ_M2_LOCAL}/settings.xml

  The settings.xml.in looks like this, of course:

  settings xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 

 http://maven.apache.org/xsd/settings-1.0.0.xsd;

localRepository@BUILD_REPO@/localRepository

interactiveMode/
usePluginRegistry/
...
  /setting

 Peter,
 Thanks for your reply and for this suggestion.  We are 
 already doing something like that in order to keep the 
 repositories for different builds separate.  But we still 
 have the problem that each build must be allowed to complete 
 before another one can run for the same user , because the 
 ant tasks that use Maven can run very late in the build.

(Where are the gears grinding?)

I see: You have a build that has a dependency that relates to
build-time.
Despite the fact that Maven creates it artifacts and install them 
in a local repository, there is some other thing in your 
corporate environment that it is time conscience.

If this is the case then what would be case if you are build with Apache
Ant, then this build-time dependency will still exist regardless of the
infrastructure technology.

I am not sure, then, if Maven can solve this, especially f you cannot 
isolate the build-time dependency.

Having said, I think a user-profile related dependency can be a problem 
for you. If you a user-profile that shared between teams, divisions,
departments
then the environment variables can be changed ad hoc. Therefore again
Maven cannot 

 I've filed the JIRA request.  I got the automated 
 acknowledgment (MNG-2684), but that's all so far.
 --Marilyn

   Meantime, our mixed builds are not scalable at all.  We 
 can do only 
   one build per user per machine at a time.  I hope the
  enhancement will
   come through fairly quickly.

  ====

  --
  Peter Pilgrim
  UBS Investment Bank,
  PTS Portal / IT FIRC OPS LDN,
  100 Liverpool Street, London EC2M 2RH, United Kingdom
  +44 (0) 20 75 75692
  :: Java EE / E-Commerce / Enterprise Integration / Development ::

  Visit our website at http://www.ubs.com

  This message contains confidential information and is intended only 
  for the individual named.  If you are not the named addressee you 
  should not disseminate, distribute or copy this e-mail.  
 Please notify 
  the sender immediately by e-mail if you have received this 
 e-mail by 
  mistake and delete this e-mail from your system.

  E-mail transmission cannot be guaranteed to be secure or 
 error-free as 
  information could be intercepted, corrupted, lost, 
 destroyed, arrive 
  late or incomplete, or contain viruses.  The sender 
 therefore does not 
  accept liability for any errors or omissions in the 
 contents of this 
  message which arise as a result of e-mail transmission.  If 
  verification is required please request a hard-copy version.  This 
  message is provided for informational purposes and should not be 
  construed as a solicitation or offer to buy or sell any 
 securities or 
  related financial instruments.

 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]

RE: Antwort: RE: Proxy settings

2006-12-04 Thread Mohni, Daniel

Hello again

all I can say about this is that a lot of the current maven2 plugins
are still in development and not in release state. this is
also why they have this snapshot repositories in their pom...

but they are going to be stable quite soon, hopefully...

using snapshot dependency that you can not control is a mess, in 
a customer project.

If you realy need a snapshot version for your project, then the
workaround is to build the plugin from source with your custom
artifactId and deploy it to your repository. it's not very nice
but in this case you have control over the used version in your project
until the plugin is stable.

A released plugin should not have a repository entry in his pom.xml !!!
that's my opinion, but maybe it's wrong... 

Maybe someone else can help you out

sorry

Daniel
 

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 04, 2006 2:51 PM
 To: archiva-users@maven.apache.org
 Subject: Antwort: RE: Proxy settings
 
 Hi Daniel,
 
 What do I do if POM.xml of a plugin says this:
 
 repositories
 repository
 idapache-snapshots/id
 nameSnapshot repository/name
 urlhttp://people.apache.org/maven-snapshot-repository//url
 /repository
 /repositories
 
 but the plugin cannot be found in this repository? Like in the JSP 
 compiler maven plugin from codehaus.
 
 My problem is the id. Every project defines their own id. 
 For some, it's 
 codehaus, for others it's codehaus.org. For another 
 group, codehaus 
 is for releases, while codehaus.org is for snapshots.
 
 This means the id *cannot* be used to map mirrors to URLs.
 
 Therefore, I need a solution in archiva which I can feed with 
 arbitrary 
 URLs and which either goes to a stable inhouse repository or 
 downloads the 
 resource from the URL and caches it.
 
 Having users define proxied repositories manually and map 
 them to managed 
 repositories is not the solution, it's another layer of 
 problems. Archia 
 should support a generic proxy/cache which just stores a 
 resource under an 
 URL. So when I ask for apache.org/.../plugin-1.3.pom and for 
 codehaus.org/.../plugin-1.3.pom, I should get two different 
 files if they 
 are different on the respective servers.
 
 On disk, you can just use the hostname as the first item in 
 the path to 
 distinguish between the different artefacts.
 
 In the webapp, it should be possible to freeze certain URLs (for 
 example, if the files on the web are broken or I'm using a 
 patched version 
 inhouse).
 
 With this solution, I could use the Maven proxy settings 
 (instead of the 
 broken mirror stuff) to download artefacts for my development 
 team *once*.
 
 Regards,
 
 -- 
 Aaron Digulla
 
 Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 
 11:31:28:
 
  Hello Aaron
  
  this can be done setting the mirror in settings.xml
  
   mirrors
 mirror
   idproxy.central/id
 mirrorOfcentral/mirrorOf
  nameInternal Mirror of central./name
 urlhttp://archiva/proxy/maven_release/url
  /mirror
/mirrors
  
  - if you use proxy in the url then archiva will try to download
 missing artefacts from the proxied repo setup in archiva
  
 http://archiva/proxy/maven_release
  
  - if you use repository in the url then archiva will only be
 a cache provider for your already downloaded artefacts
  
 http://archiva/repository/maven_release
  
  maven_release is our internal proxy repository...
  
  I don't know if this is still like this in the current daily build
  as I didn't tried it...
  
  hth
  
  Daniel
  
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
   Sent: Monday, December 04, 2006 11:19 AM
   To: archiva-users@maven.apache.org
   Subject: Proxy settings
   
   Hello,
   
   We're using maven for internal development. Since the 
   internet as a whole 
   and our connection to it especially are not always reliable 
   (for example, 
   a new version of a virus checker sometimes starts to 
 block out maven 
   downloads), we wanted to use Archiva as a local cache of the 
   central maven 
   repositories.
   
   As it is right now, I have to configure each repository 
   individually. What 
   we would prefer is a setting which makes Archiva the default 
   proxy for 
   maven so all external connections are made over it.
   
   This would allow us to keep local copies of all artefacts 
 so internet 
   outages wouldn't affect us anymore. Also, we could fix broken 
   packages 
   locally. Ideally, there should be two caches: One with stable 
   version for 
   development and one which can update itself with the current 
   versions from 
   the internet.
   
   Is this possible?
   
   Regards,
   
   -- 
   Aaron Digulla

[M2] list of available goals (for all plugins)?


Hi,

i'm searching for a plugin that lists all available goals of ALL Maven2
plugins?
If this feature is not implemented yet, will it be taken into consideration?

i know about the 'maven-projecthelp-plugin' and the 'maven-help-plugin', but
they don't show available goals...

thx 4 help
R.C.
-- 
View this message in context: 
http://www.nabble.com/-M2--list-of-available-goals-%28for-all-plugins%29--tf2753173s177.html#a7678351
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: [M2] list of available goals (for all plugins)?

2006-12-04 Thread ir. ing. Jan Dockx

Define ALL Maven2 plugins. Since Maven is an open system of  
plugins, the best answer is probably Google ;-). If you mean all  
build lifecycle phases, they are static, and can be found at http:// 
cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html  
and at other places.



On 4 Dec 2006, at 15:15, CodingPlayer wrote:



Hi,

i'm searching for a plugin that lists all available goals of ALL  
Maven2

plugins?
If this feature is not implemented yet, will it be taken into  
consideration?


i know about the 'maven-projecthelp-plugin' and the 'maven-help- 
plugin', but

they don't show available goals...

thx 4 help
R.C.
--
View this message in context: http://www.nabble.com/-M2--list-of- 
available-goals-%28for-all-plugins%29--tf2753173s177.html#a7678351

Sent from the Maven - Users mailing list archive at Nabble.com.


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




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

[M2] different maven-...help-plugins?


Hi,

does anyone know about the difference of these two plugins?

http://maven.apache.org/plugins/maven-help-plugin/
http://maven.apache.org/plugins/maven-projecthelp-plugin/

Which one is used most common?

thx
R.C.

-- 
View this message in context: 
http://www.nabble.com/-M2--different-maven-...help-plugins--tf2753567s177.html#a7678912
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: [M2] different maven-...help-plugins?

2006-12-04 Thread Mark Hobson


On 04/12/06, CodingPlayer [EMAIL PROTECTED] wrote:

does anyone know about the difference of these two plugins?

http://maven.apache.org/plugins/maven-help-plugin/
http://maven.apache.org/plugins/maven-projecthelp-plugin/


maven-projecthelp-plugin was renamed to maven-help-plugin a while back.

Mark

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

Re: Re: dependencies on eclipse 3.2 plugins

2006-12-04 Thread Bhupendra Bhardwaj


Hi,

I could compile using the repository repo1.maven.org/eclipse
but later I found a problem. The plugins are in format pluginname-version
and in the eclipse plugins are in format pluginname_version.
because of change in plugin names my RCP didn't run. i still couldn't find
why the plugin jar name change affects it.
so currently I am building using ant without taking plugins from
respository.

But if you just want to have a look at how i compiled using maven, then here
is the part of the pom file-

build
   resources
 resource
   targetPathicons//targetPath
   directoryicons//directory
   includes
 include**/include
   /includes
 /resource
 resource
   targetPath//targetPath
   directory${basedir}/directory
   includes
 includeplugin.xml/include
 includeplugin.properties/include
 includeMETA-INF/MANIFEST.MF/include
   /includes
 /resource
   /resources
   finalName${artifactId}_${version}/finalName
   plugins
 plugin
   artifactIdmaven-jar-plugin/artifactId
   configuration
 archive
   manifestFileMETA-INF/MANIFEST.MF/manifestFile
 /archive
   /configuration
 /plugin
 plugin
   artifactIdmaven-surefire-plugin/artifactId
 /plugin
   /plugins
 /build
 repositories
   repository
 idrepo1.maven.org/id
 nameMaven eclipse Repository/name
 urlhttp://repo1.maven.org/eclipse/url
   /repository
 /repositories
 dependencies
   dependency
 groupIdcom.ibm.icu/groupId
 artifactIdcom.ibm.icu/artifactId
 version3.4.4/version
 scopecompile/scope
   /dependency
  --
  other dependencies
  

/dependencies
 distributionManagement
   statusdeployed/status
 /distributionManagement
 properties
   topDirectoryLocation../..//topDirectoryLocation
 /properties
/project


hope it helps
Bhupendra


On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Hi,

which maven plugin do you use for building your rcp application or eclipse
plugins? Do you have a sample pom.xml for me?


Best Regards,
Thorsten


Thanks Tom,

That was very helpful.

Regards,
Bhupendra


On 12/2/06, Tom Huybrechts [EMAIL PROTECTED] wrote:

 There is a Maven repository with the Eclipse bundles at
 http://repo1.maven.org/eclipse/
 I don't expect this to be around forever, but I guess it will
 eventually be integrated in the central repository.

 On 12/2/06, Bhupendra Bhardwaj [EMAIL PROTECTED] wrote:
  Hi,
 
  I have developed an eclipse RCP and it can run as an standalone
 application.
  Now I need to do a maven build for it. This project will be part of
 another
  open source project. As the eclipse plugins are not available in
maven
  repository, do I need to add those plugins like swt3.2.., jface3.2etc
 etc
  in the repository?
  I know that eclipse doesn't ship these as seperate plugins.
  If the jars are available in maven repository, then I can just add
the
  dependency in the pom file, but for these eclipse plugin jars what
can
 be
  done?
 
  any pointers in the right direction will be helpful.
 
  Regards,
  Bhupendra
 
 

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



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

Re: [M2] list of available goals (for all plugins)?

hi,

What i mean is, that i would love to write something like,

e.g. mvn list-goals

and get an output like:

phase: XXX
goals: AAA, BBB, CCC

phase: YYY
goals: DDD, EEE

e.g.:
phase: compile
goals: compile, test-compile, ...

...

phase: package
goals: package, jar:jar, jar:test-jar, source:jar, source:test-jar,

the plugin should not only point out the corresponding lifecycle-phase, it
should also list ALL goals for each plugin...

Since most of the plugins provide more than one goal, a COMPLETE list would
be nice.

The fact is, that when the developers team of a company switches lets say,
from ant to maven2, every single developer has to know quite a lot about
maven, to simple find out how to build and run the project.

Therefore such a simple command to list all available goals (of all plugins,
correlated to the corresponding life-cycle-phase) would help quite a lot.

thx 4 help
R.C.

ir. ing. Jan Dockx wrote:

Define ALL Maven2 plugins. Since Maven is an open system of
plugins, the best answer is probably Google ;-). If you mean all
build lifecycle phases, they are static, and can be found at http://
cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html
and at other places.

On 4 Dec 2006, at 15:15, CodingPlayer wrote:

Hi,

i'm searching for a plugin that lists all available goals of ALL
Maven2
plugins?
If this feature is not implemented yet, will it be taken into
consideration?

i know about the 'maven-projecthelp-plugin' and the 'maven-help-
plugin', but
they don't show available goals...

thx 4 help
R.C.
--
View this message in context: http://www.nabble.com/-M2--list-of-
available-goals-%28for-all-plugins%29--tf2753173s177.html#a7678351
Sent from the Maven - Users mailing list archive at Nabble.com.

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

--
View this message in context:
http://www.nabble.com/-M2--list-of-available-goals-%28for-all-plugins%29--tf2753173s177.html#a7679539
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: [M2] different maven-...help-plugins?


Mark, thx 4 help, that was what i expected.

R.C.


Mark Hobson wrote:
 
 On 04/12/06, CodingPlayer [EMAIL PROTECTED] wrote:
 does anyone know about the difference of these two plugins?

 http://maven.apache.org/plugins/maven-help-plugin/
 http://maven.apache.org/plugins/maven-projecthelp-plugin/
 
 maven-projecthelp-plugin was renamed to maven-help-plugin a while back.
 
 Mark
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-M2--different-maven-...help-plugins--tf2753567s177.html#a7679766
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: Antwort: RE: Proxy settings

2006-12-04 Thread Sam Wilson

I completely agree with both statements:

1) snapshot dependency that you can not control is a mess, in 
a customer project ... build the plugin from source with your custom
artifactId and deploy it to your repository

and

2) A released plugin should not have a repository entry in his pom.xml

I ran into this recently when people.apache.org was down during a data
center move. I was just setting up my repository the day before so I got
caught in the maelstrom before I could take corrective action. 

However, a fair number of released plugins had references to
people.apache.org that should not have been there. This tends to be a
real problem with codehaus projects.

At the very least, snapshot and release repositories should be properly
labeled as such if they are going to be included.

sw

-Original Message-
From: Mohni, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 04, 2006 9:15 AM
To: archiva-users@maven.apache.org
Subject: RE: Antwort: RE: Proxy settings

Hello again

all I can say about this is that a lot of the current maven2 plugins
are still in development and not in release state. this is
also why they have this snapshot repositories in their pom...

but they are going to be stable quite soon, hopefully...

using snapshot dependency that you can not control is a mess, in 
a customer project.

If you realy need a snapshot version for your project, then the
workaround is to build the plugin from source with your custom
artifactId and deploy it to your repository. it's not very nice
but in this case you have control over the used version in your project
until the plugin is stable.

A released plugin should not have a repository entry in his pom.xml !!!
that's my opinion, but maybe it's wrong... 

Maybe someone else can help you out

sorry

Daniel
 

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 04, 2006 2:51 PM
 To: archiva-users@maven.apache.org
 Subject: Antwort: RE: Proxy settings
 
 Hi Daniel,
 
 What do I do if POM.xml of a plugin says this:
 
 repositories
 repository
 idapache-snapshots/id
 nameSnapshot repository/name
 urlhttp://people.apache.org/maven-snapshot-repository//url
 /repository
 /repositories
 
 but the plugin cannot be found in this repository? Like in the JSP 
 compiler maven plugin from codehaus.
 
 My problem is the id. Every project defines their own id. 
 For some, it's 
 codehaus, for others it's codehaus.org. For another 
 group, codehaus 
 is for releases, while codehaus.org is for snapshots.
 
 This means the id *cannot* be used to map mirrors to URLs.
 
 Therefore, I need a solution in archiva which I can feed with 
 arbitrary 
 URLs and which either goes to a stable inhouse repository or 
 downloads the 
 resource from the URL and caches it.
 
 Having users define proxied repositories manually and map 
 them to managed 
 repositories is not the solution, it's another layer of 
 problems. Archia 
 should support a generic proxy/cache which just stores a 
 resource under an 
 URL. So when I ask for apache.org/.../plugin-1.3.pom and for 
 codehaus.org/.../plugin-1.3.pom, I should get two different 
 files if they 
 are different on the respective servers.
 
 On disk, you can just use the hostname as the first item in 
 the path to 
 distinguish between the different artefacts.
 
 In the webapp, it should be possible to freeze certain URLs (for 
 example, if the files on the web are broken or I'm using a 
 patched version 
 inhouse).
 
 With this solution, I could use the Maven proxy settings 
 (instead of the 
 broken mirror stuff) to download artefacts for my development 
 team *once*.
 
 Regards,
 
 -- 
 Aaron Digulla
 
 Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 
 11:31:28:
 
  Hello Aaron
  
  this can be done setting the mirror in settings.xml
  
   mirrors
 mirror
   idproxy.central/id
 mirrorOfcentral/mirrorOf
  nameInternal Mirror of central./name
 urlhttp://archiva/proxy/maven_release/url
  /mirror
/mirrors
  
  - if you use proxy in the url then archiva will try to download
 missing artefacts from the proxied repo setup in archiva
  
 http://archiva/proxy/maven_release
  
  - if you use repository in the url then archiva will only be
 a cache provider for your already downloaded artefacts
  
 http://archiva/repository/maven_release
  
  maven_release is our internal proxy repository...
  
  I don't know if this is still like this in the current daily build
  as I didn't tried it...
  
  hth
  
  Daniel
  
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
   Sent: Monday, December 04, 2006 11:19 AM
   To: archiva-users@maven.apache.org
   Subject: Proxy settings
   
   Hello,
   
   We're using maven for internal development. Since the 
   internet as a whole 
   and our connection to it especially are not always reliable 
   (for example, 
   a new version of a

[M2] pluginManagement vs. plugin in parent pom.xml


Hi,

i just found out about the existence of the pluginManagement section in a
pom.xml.

But i wonder, what is the difference to a plugin section??


Until now, i only use a plugin section in my parent pom.xml, and all of
the plugins still work in my sub-projects.
So, why should i put these plugins under the pluginManagement section?

thx 4 help
R.C.
-- 
View this message in context: 
http://www.nabble.com/-M2--%3CpluginManagement%3E-vs.-%3Cplugin%3E-in-parent-pom.xml-tf2754489s177.html#a7680557
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: [M2] pluginManagement vs. plugin in parent pom.xml

2006-12-04 Thread nicolas de loof


AFAIK the plugins section is inherited by modules, and the
pluginmanagement only defines a common configuration for plugins BUT does
not enable them on child modules.

You can then configure commons plugin for all your modules in plugins and
define a common configuration for some plugin that are only used in some
modules (but not all). Those module will then only add a plugin entry with
no configuration.

Nico.

2006/12/4, CodingPlayer [EMAIL PROTECTED]:



Hi,

i just found out about the existence of the pluginManagement section in
a
pom.xml.

But i wonder, what is the difference to a plugin section??


Until now, i only use a plugin section in my parent pom.xml, and all of
the plugins still work in my sub-projects.
So, why should i put these plugins under the pluginManagement section?

thx 4 help
R.C.
--
View this message in context:
http://www.nabble.com/-M2--%3CpluginManagement%3E-vs.-%3Cplugin%3E-in-parent-pom.xml-tf2754489s177.html#a7680557
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: [M2] different maven-...help-plugins?


On 12/4/06, Mark Hobson [EMAIL PROTECTED] wrote:

On 04/12/06, CodingPlayer [EMAIL PROTECTED] wrote:
 does anyone know about the difference of these two plugins?

 http://maven.apache.org/plugins/maven-help-plugin/
 http://maven.apache.org/plugins/maven-projecthelp-plugin/

maven-projecthelp-plugin was renamed to maven-help-plugin a while back.


I've removed the maven-projecthelp-plugin docs from the server, it
will disappear in a day or so.

Thanks,
Wendy

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

[M2] Some troubles with maven-surefire-plugin and testng

2006-12-04 Thread Alexandre Touret


hello,
I m trying to run maven-surefire-plugin with testng.
I have some troubles:
1 - if I dont specify teh testsuites path in pom.xml, surefire doesnt 
find any test, even if I try to specify include elements

My pattern : include**/*Test.java/include

I decided to specify a testsuite in a xml file. Unfortunately, I have 
the following problem:
2 - I try to run only one testcase described in a testsuite I always 
have the following behaviour: The surefire plugin runs all the test 
suite and not only the specified test case


I did the following command : mvn -Dtest=LoginTest test

How to run only one testcase ?

Thanks in advance for your help!

Regards,
Alexandre


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

Re: [M2] list of available goals (for all plugins)?

2006-12-04 Thread Wayne Fay

This is where people new to Maven go wrong... With Ant, you need to
generate such a list of available/useful targets. With Maven, assuming
your project is set up by someone who knows what they're doing, the
plugins should be attached to the proper phases and you will simply
run mvn package or mvn test or mvn deploy and automatically the
proper plugins will be executed at the proper time etc.

Wayne

On 12/4/06, CodingPlayer [EMAIL PROTECTED] wrote:

hi,

What i mean is, that i would love to write something like,

e.g. mvn list-goals

and get an output like:

phase: XXX
goals: AAA, BBB, CCC

phase: YYY
goals: DDD, EEE

e.g.:
phase: compile
goals: compile, test-compile, ...

...

phase: package
goals: package, jar:jar, jar:test-jar, source:jar, source:test-jar,

the plugin should not only point out the corresponding lifecycle-phase, it
should also list ALL goals for each plugin...

Since most of the plugins provide more than one goal, a COMPLETE list would
be nice.

Therefore such a simple command to list all available goals (of all plugins,
correlated to the corresponding life-cycle-phase) would help quite a lot.

thx 4 help
R.C.

ir. ing. Jan Dockx wrote:

On 4 Dec 2006, at 15:15, CodingPlayer wrote:

Hi,

i'm searching for a plugin that lists all available goals of ALL
Maven2
plugins?
If this feature is not implemented yet, will it be taken into
consideration?

i know about the 'maven-projecthelp-plugin' and the 'maven-help-
plugin', but
they don't show available goals...

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

--
View this message in context:
http://www.nabble.com/-M2--list-of-available-goals-%28for-all-plugins%29--tf2753173s177.html#a7679539
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: Putting resources to somewhere else

2006-12-04 Thread rudy.bistrovich

In order to stop Maven from putting your resources into your jar you
need to override the default targetpath directory for the resources.
This is done in the POM in the resources section. If you take a look
at what I have below...this is telling maven to output any files found
in the src/main/resources to target/resources. This way...the maven pkg
cmd won't add them to your jar.  As you can see I also have maven setup
to exclude certain sub folders in there because I customize maven to
only filter files found in the filtered folder and only put files found
in the packaged folder into the jar. I then use assemblies as Wendy
described to create the structure similar to what you listed below. If
you want more details on how I set all this up you can email me
directly.

Ie. resources
resource
targetPath../resources/targetPath
filteringfalse/filtering
directorysrc/main/resources/directory
excludes
excludefiltered/**/exclude
excludepackaged/**/exclude
excludedir.info/exclude
/excludes
/resource
resource

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 01, 2006 8:46 AM
To: Maven Users List
Subject: Re: Putting resources to somewhere else

On 12/1/06, [EMAIL PROTECTED]
[EMAIL PROTECTED]

 I would like maven to put my resources not into the jar file, but next
 to classes in a resources directory, so my structure would be:

 Component +
   - lib +
 - mycomponent.jar
   - resources +
   - myresource.xml

 Etc.

 Could anybody help how to tell the resource processor plugin where to
 put it? I could tell only relative path within target/classes, but not
 relative to output directory.

If you want to build something that contains jars and other files,
look at the assembly plugin:

http://maven.apache.org/plugins/maven-assembly-plugin/
(The current version is actually 2.1, not 2.2 as it says.)

Otherwise, whatever you put in src/main/resources will be mirrored in
the jar.  So if you want something at the top level of the jar, put
it directly in src/main/resources.  Then create the desired directory
structure from there.  It will overlay (or sit beside) the classes
compiled from code in src/main/java.  You can use resources in the
pom to identify things to copy into the jar.

-- 
Wendy

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


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

Re: [M2] Unable Disable a Repository?


On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


I need to find out how to undisable a repository, when Maven
thinks it is unavailable.


AFAIK, any 'blacklisting' only lasts for that build.

--
Wendy

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

Antwort: RE: Antwort: RE: Proxy settings

Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 
15:15:13:

 A released plugin should not have a repository entry in his pom.xml !!!
 that's my opinion, but maybe it's wrong... 

My position is that the POMs which come from the main sites can (and will) 
contain anything (even illegal XML, broken checksums, etc). The proxy has 
to handle all these case gracefully or at least to support the admin in 
doing so.

I'm missing these functions in archiva:

- Generic proxy (so the POMs can't mess with your mirror settings).
- Regenerate checksum (for all downloads which I needed to fix)
- Lock down file (so Archiva will not try to download it again even if the 
remote site says but I have new version or the user says get the 
newest, hottest snapshots!).

I can live without the last two but the first one is a must, IMHO.

Regards,

-- 
Aaron Digulla

Re: Putting resources to somewhere else


On 12/4/06, Aaron Digulla [EMAIL PROTECTED] wrote:


Is there a simple way to have the resources next to the Java classes (ie. in
src/main/java)? When developing with Hibernate, it's tedious to switch back
and forth between the directories.

I've checked the docs for the plugin but there is no example to do this.
This made me think it might be dangerous to do (side effects, etc).


If you prefer to keep your non-Java resources under src/main/java,
then use resources to pick them up.

This pom has an example:
http://svn.apache.org/repos/asf/struts/struts1/trunk/core/pom.xml

You can also do it by adding a resource for src/main/java and
excluding **/*.java to get everything but the Java sources.  (That
might pick up Javadoc package summaries, though.)

The only thing to keep in mind is that once you specify any
resources, you're responsible for specifying *all* of them.  (For
example, the 'default' of src/main/resources has to be stated
explicitly in addition to anything under src/main/java.)

--
Wendy

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

[M2] Just need the open source eyes on this

Hi

Maven says it cant download the file from the internal repository.

Anything out of the ordinary of this maven-metadata.xml file.


?xml version=1.0?
metadata
  groupIdorg.easymock/groupId
  artifactIdeasymock/artifactId
  version2.2/version
  versioning
latest2.2/latest
release2.2/release

versions
  version1.2/version
  version2.2/version
/versions
lastUpdated20061120170542/lastUpdated
  /versioning
/metadata
!--*PP* Mon Nov 20 17:05:42 GMT 2006 --

Error

[INFO] Error building POM (may not be this project's POM).


Project ID: org.easymock:easymock

Reason: Error getting POM for 'org.easymock:easymock' from the
repository: Error
 transferring file
  org.easymock:easymock:pom:1.2

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  ptsp-repository (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
  ptsp-internal
(http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
tory)

--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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

RE: Proxy settings

Sam Wilson [EMAIL PROTECTED] schrieb am 04.12.2006 16:27:59:

 At the very least, snapshot and release repositories should be properly
 labeled as such if they are going to be included.

No matter how hard you wish, there will always be a broken POM out there 
and there should be a reliable, understandable, simple way to make my 
build work again (and that of my 15 colleagues who depend on my work on 
the proxy).

Regards,

-- 
Aaron Digulla

RE: [M2] Just need the open source eyes on this

 -Original Message-
 From: Pilgrim, Peter 
 Sent: 04 December 2006 16:10
 To: 'Maven Users List'
 Subject: [M2] Just need the open source eyes on this 

 Hi

 Maven says it cant download the file from the internal repository.

 Anything out of the ordinary of this maven-metadata.xml file.

Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.

BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.

 ?xml version=1.0?
 metadata
   groupIdorg.easymock/groupId
   artifactIdeasymock/artifactId
   version2.2/version
   versioning
 latest2.2/latest
 release2.2/release

 versions
   version1.2/version
   version2.2/version
 /versions
 lastUpdated20061120170542/lastUpdated
   /versioning
 /metadata
 !--*PP* Mon Nov 20 17:05:42 GMT 2006 --

 Error

 [INFO] Error building POM (may not be this project's POM).

 Project ID: org.easymock:easymock

 Reason: Error getting POM for 'org.easymock:easymock' from 
 the repository: Error  transferring file
   org.easymock:easymock:pom:1.2

 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   ptsp-repository 
 (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
   ptsp-internal 
 (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
 tory)

--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

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

Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Wayne Fay


Do you have the corresponding sha1 and md5 files next to the pom file
named ie blah-1.0.pom, blah-1.0.pom.sha1, blah-1.0.pom.md5? You will
need this for all files in the repository.

This can cause those error messages, IIRC.

Wayne

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 -Original Message-
 From: Pilgrim, Peter
 Sent: 04 December 2006 16:10
 To: 'Maven Users List'
 Subject: [M2] Just need the open source eyes on this

 Hi

 Maven says it cant download the file from the internal repository.

 Anything out of the ordinary of this maven-metadata.xml file.


Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.



BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.


 ?xml version=1.0?
 metadata
   groupIdorg.easymock/groupId
   artifactIdeasymock/artifactId
   version2.2/version
   versioning
 latest2.2/latest
 release2.2/release

 versions
   version1.2/version
   version2.2/version
 /versions
 lastUpdated20061120170542/lastUpdated
   /versioning
 /metadata
 !--*PP* Mon Nov 20 17:05:42 GMT 2006 --

 Error

 [INFO] Error building POM (may not be this project's POM).


 Project ID: org.easymock:easymock

 Reason: Error getting POM for 'org.easymock:easymock' from
 the repository: Error  transferring file
   org.easymock:easymock:pom:1.2

 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   ptsp-repository
 (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
   ptsp-internal
 (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
 tory)

--
Peter Pilgrim
UBS Investment Bank,
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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




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

Re: [M2] Just need the open source eyes on this


On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.


Based on other problems you've reported, that sounds likely.  FWIW, I
think releases are discovered directly, by constructing the path to
the artifact, not by reading the metadata.


BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.


No, but feel free to add a page to the wiki.  'Guide to Maven
Repository Metadata' sounds like a useful thing to have. :)

--
Wendy

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

Including an assembly as part of another assembly


Hi, I'm new to Maven so forgive me if this something really obvious. I
looked through the assembly plugin documentation and searched the
archives, but couldn't find anything covering my use case.

I'm building an assembly using the built-in jar-with-dependencies
descriptor. That works great. I'd like to include the generated
assembly inside another custom assembly. The custom assembly would be
a zip file containing my jar (generated with the
jar-with-dependencies descriptor) along with some other supporting
files located in my project root folder.

Is something like this possible? I've tried messing around with my
custom descriptor, but to no avail. I can generate the zip file, but
it doesn't contain my jar, only the supporting files. If I'm going in
the wrong direction with this, I'd appreciate if someone could let me
know. Thanks.

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

Re: checkstyles

2006-12-04 Thread Trevor Torrez


Thanks; I had thought about that, I was hoping there was something simpler
and just as transparent.  It kinda grates me to create a maven project and
repository jar file for one file; using a simple URL is tempting, but
anywhere we can stick the file we can stick the jar, and the simple URL idea
doesnt let us control changes to it;

thanks again

-t.


On 12/2/06, Robert Reiner [EMAIL PROTECTED] wrote:




Trevor Torrez wrote:

 What is the best way to have all subprojects use the same checkstyles
 file?



Hi Trevor,

I do not know what the best way is, but this is how it works for me:

I have a parent POM to all POMs of my subprojects. In this I declare my
checkstyle configuration as an extension like this:

  extensions
 extension
   groupIdde.smartics.config/groupId
   artifactIdcheckstyle-config-smartics/artifactId
   version0.2.1/version
 /extension
   /extensions

The plugin is defined in the same POM:

plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-checkstyle-plugin/artifactId
   version2.1/version
   extensionstrue/extensions
   inheritedtrue/inherited
   configuration
 configLocationcheckstyle.xml/configLocation
   /configuration
 /plugin

The checkstyle project referenced in the extension section is a project on
its own, containing only the checkstyle.xml. So the build section in this
project looks like this:

build
   resources
 resource
   directorysrc/main/resources/directory
 /resource
   /resources
/build

And in the resources directory I place the checkstyle.xml file. I had some
difficulties placing it in a subdir and naming it other than this, but
this
may have been a fault on my side...

Hope this helps.

Greetings,
Robert
--
View this message in context:
http://www.nabble.com/checkstyles-tf2734779s177.html#a7652646
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: Resources with different encoding

2006-12-04 Thread franz see


Good day to you, Robert,

You must declare your UTF-8 files as one resource and your ISO-8859-1 files
as another. For example,

project
  ...
  build
resources
  resource
directorysrc/main/resources/directory
encodingUTF-8/encoding
includes
  include**/*.xml/include
/includes
  /resource
  resource
directorysrc/main/resources/directory
encodingISO-88591/encoding
includes
  include**/*.properties/include
/includes
  /resource
  resource
directorysrc/main/resources/directory
excludes
  exclude**/*.xml/exclude
  exclude**/*.properties/exclude
/excludes
  /resource
/resources
/project

For more information, kindly take a look at [1].

Cheers,
Franz

[1] http://maven.apache.org/plugins/maven-resources-plugin/

Robert Reiner wrote:
 
 Hi!
 
 I have a question concerning the maven-resources-plugin: In my resource
 folder I have files with different encodings. The XML files are UTF-8, the
 properties files are ISO-8859-1. Since I set the encoding for copying the
 files to UTF-8, my property files are not copied properly.
 
 A workaround I can think of is running the resources plugin a second time
 and include only the property files with the encoding set to ISO-8859-1.
 But how can I specify these files in the configuration of the second
 execution block?
 
 Maybe there is a more maven-like way to do this: Can someone give me
 advice how to handle resource files with different encodings? 
 
 Thanks for your answer.
 
   Robert
 

-- 
View this message in context: 
http://www.nabble.com/Resources-with-different-encoding-tf2736719s177.html#a7682184
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: Including an assembly as part of another assembly


Quick question, why can't you have two sub modules under your POM, one that
generates an assembly, the other generating the final output with the other
assembly included?  (you get the idea)

-aps

On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:


Hi, I'm new to Maven so forgive me if this something really obvious. I
looked through the assembly plugin documentation and searched the
archives, but couldn't find anything covering my use case.

I'm building an assembly using the built-in jar-with-dependencies
descriptor. That works great. I'd like to include the generated
assembly inside another custom assembly. The custom assembly would be
a zip file containing my jar (generated with the
jar-with-dependencies descriptor) along with some other supporting
files located in my project root folder.

Is something like this possible? I've tried messing around with my
custom descriptor, but to no avail. I can generate the zip file, but
it doesn't contain my jar, only the supporting files. If I'm going in
the wrong direction with this, I'd appreciate if someone could let me
know. Thanks.

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





--
What lies behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson

Re: checkstyles


On 12/4/06, Trevor Torrez [EMAIL PROTECTED] wrote:


Thanks; I had thought about that, I was hoping there was something simpler
and just as transparent.  It kinda grates me to create a maven project and
repository jar file for one file; using a simple URL is tempting, but
anywhere we can stick the file we can stick the jar, and the simple URL idea
doesnt let us control changes to it;


Yep... this is one of those times when Maven is (not so) gently
encouraging you to do the right thing, (version everything associated
with your build) even if it seems a bit over the top to have to
release a jar containing a single file. :)

--
Wendy

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

Re: checkstyles

2006-12-04 Thread Mark Hobson


On 04/12/06, Wendy Smoak [EMAIL PROTECTED] wrote:

Yep... this is one of those times when Maven is (not so) gently
encouraging you to do the right thing, (version everything associated
with your build) even if it seems a bit over the top to have to
release a jar containing a single file. :)


Can't Jason's remote resources plugin be used for this?

http://people.apache.org/~jvanzyl/maven-remote-resources-plugin/

Mark

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

RE: [M2] Just need the open source eyes on this

 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 16:50
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this

 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

  Ignore I think firewall proxy issues are preventing the 
 routing access 
  direct to internal repository from the machine.

 Based on other problems you've reported, that sounds likely.  
 FWIW, I think releases are discovered directly, by 
 constructing the path to the artifact, not by reading the metadata.

That's very interesting, Wendy.
In my experience you do need a maven-metadata.xml file with 
information that points to the versions of the artifact. 

  BTW: Any one got a good guide to the metadata format and 
 explanation?
  Most of it I did was guess work.

 No, but feel free to add a page to the wiki.  'Guide to Maven 
 Repository Metadata' sounds like a useful thing to have. :)

--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

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

RE: [M2] Just need the open source eyes on this

Hi

 -Original Message-
 From: Wayne Fay [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 16:48
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this

 Do you have the corresponding sha1 and md5 files next to the 
 pom file named ie blah-1.0.pom, blah-1.0.pom.sha1, 
 blah-1.0.pom.md5? You will need this for all files in the 
 repository.

 This can cause those error messages, IIRC.

Thanks Wayne

I wrote a Java tool that regenerates the MD5 and SHA-1 files based on
Brett's DigestUtils.
The only thing I did was append a '\n' to the end of the files. Just so
I could 
execute `cat *.md5' and get a newline character on the command line. I
don't think 
that cause Maven fail though.

BTW: Your schema worked out quite well in the end. It is just so hard
find out when
Maven cant transfer a file down or work out what possible else has gone
wrong.

 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   -Original Message-
   From: Pilgrim, Peter
   Sent: 04 December 2006 16:10
   To: 'Maven Users List'
   Subject: [M2] Just need the open source eyes on this

   Hi

   Maven says it cant download the file from the internal repository.

   Anything out of the ordinary of this maven-metadata.xml file.

  Ignore I think firewall proxy issues are preventing the 
 routing access 
  direct to internal repository from the machine.

  BTW: Any one got a good guide to the metadata format and 
 explanation?
  Most of it I did was guess work.

   ?xml version=1.0?
   metadata
 groupIdorg.easymock/groupId
 artifactIdeasymock/artifactId
 version2.2/version
 versioning
   latest2.2/latest
   release2.2/release

   versions
 version1.2/version
 version2.2/version
   /versions
   lastUpdated20061120170542/lastUpdated
 /versioning
   /metadata
   !--*PP* Mon Nov 20 17:05:42 GMT 2006 --

   Error

   [INFO] Error building POM (may not be this project's POM).

   Project ID: org.easymock:easymock

   Reason: Error getting POM for 'org.easymock:easymock' from the 
   repository: Error  transferring file
 org.easymock:easymock:pom:1.2

   from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 ptsp-repository
   (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
 ptsp-internal
   (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
   tory)

====
--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

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

Re: Including an assembly as part of another assembly


My project is a simple command-line application. I didn't think it
required multiple modules so I never looked into that. Is that the
preferred way to accomplish what I'm describing? Basically, I just
want to include my assembly jar along with a few other files inside a
zip file.


On 12/4/06, Alexander Sack [EMAIL PROTECTED] wrote:

Quick question, why can't you have two sub modules under your POM, one that
generates an assembly, the other generating the final output with the other
assembly included?  (you get the idea)

-aps

On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:

 Hi, I'm new to Maven so forgive me if this something really obvious. I
 looked through the assembly plugin documentation and searched the
 archives, but couldn't find anything covering my use case.

 I'm building an assembly using the built-in jar-with-dependencies
 descriptor. That works great. I'd like to include the generated
 assembly inside another custom assembly. The custom assembly would be
 a zip file containing my jar (generated with the
 jar-with-dependencies descriptor) along with some other supporting
 files located in my project root folder.

 Is something like this possible? I've tried messing around with my
 custom descriptor, but to no avail. I can generate the zip file, but
 it doesn't contain my jar, only the supporting files. If I'm going in
 the wrong direction with this, I'd appreciate if someone could let me
 know. Thanks.

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




--
What lies behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson




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

Re: [M2] Just need the open source eyes on this


On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


That's very interesting, Wendy.
In my experience you do need a maven-metadata.xml file with
information that points to the versions of the artifact.


If that were true across the board, no one would be able to use MyFaces 1.1.4.
  http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
(The metadata only mentions the 1.1.2 version.)

Archiva may be more sensitive to incorrect metadata, however.

--
Wendy

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

RE: [M2] Just need the open source eyes on this



--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
 

 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 17:13
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this
 
 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
  That's very interesting, Wendy.
  In my experience you do need a maven-metadata.xml file with 
  information that points to the versions of the artifact.
 

I wonder if the problem is that the easymock 1.2 does not exist at the
moment
on central 

http://repo1.maven.org/maven2/org/easymock/easymock/


Hence Maven complains when over here we try to overrule the repository.
From the BBWM book in terms of precedure the local-most profiles wins
out. 
(Page 70)

I ran maven so that it activates a profile that points to the internal
repo. Is there a setting for a repository definiton inside a ``local
profile''
that overrules completely? 


 If that were true across the board, no one would be able to 
 use MyFaces 1.1.4.
http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
 (The metadata only mentions the 1.1.2 version.)
 
 Archiva may be more sensitive to incorrect metadata, however.
 
I am not using Archiva because I could get Maven to download from the
Tomcat Server. I am just using a Tomcat with the DefaultServlet that
serves files from a directory instead.

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

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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

Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Tom Huybrechts

For dependencies, the path in a local or remote repository can be
constructed using groupId, artifactId, version, classifier and type
since all of these are always known from the POM (or parent POMs).

For plugins the version is not always known. If no version is
specified for a given plugin, the resolver will use the metadata
(which are version independent) to retrieve the latest or release
version from the artifact metadata in local or remote repository.
e.g.
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ejb-plugin/maven-metadata.xml

In case you specify a short version for a plugin goal (like
eclipse:eclipse), then the resolver can map this on artifactIds using
group metadata for the registered plugin groups.
e.g. http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml

Tom

On 12/4/06, Wendy Smoak [EMAIL PROTECTED] wrote:

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

That's very interesting, Wendy.
In my experience you do need a maven-metadata.xml file with
information that points to the versions of the artifact.

If that were true across the board, no one would be able to use MyFaces 1.1.4.
http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
(The metadata only mentions the 1.1.2 version.)

Archiva may be more sensitive to incorrect metadata, however.

--
Wendy

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

Maven with XDoclet - Failing to generate code

2006-12-04 Thread Leonardo Postacchini


 Hello there!

 I am trying to run XDoclet 2 through Maven 2 and I am getting build
failures saying the acess to the diretory where the generated sources was
denied.

 I am running it under Windows XP professional, I checked the directory
permissions and all seems fine. All processes are running under my user that
is the system administrator.

 Does someone have gone through similar case? Any Ideas where to find the
cause of the acess denial? I am fairly new to Maven and I have no clue about
how it works.

 I have being digging the documentation for the past few days, but could
not find the answer by myself.

 Thanks for your time and the attention,

 Notivago.

Re: Including an assembly as part of another assembly


I won't speak for best practices but typically you would create another
module to do the packaging (similar to some of the EAR examples).

For a simple command-line application, my guess is one pom and one assembly
descriptor will be enough.  For my command-line tool I generate the jar and
then assemble the whole applicaiton like so:

snippet from my assembly descriptor XML file:

fileSets
   fileSet
 directorytarget/directory
   outputDirectory/outputDirectory
   includes
 include*.jar/include
   /includes
 /fileSet
 fileSet
 outputDirectory/outputDirectory
 directorydist/directory
 includes
   include*/include
 /includes
  /fileSet
 /fileSets

Basically dist has some extra static files in it, target is where the JAR
gets built, and then the assembly plugin builds everything together.


-aps

On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:


My project is a simple command-line application. I didn't think it
required multiple modules so I never looked into that. Is that the
preferred way to accomplish what I'm describing? Basically, I just
want to include my assembly jar along with a few other files inside a
zip file.


On 12/4/06, Alexander Sack [EMAIL PROTECTED] wrote:
 Quick question, why can't you have two sub modules under your POM, one
that
 generates an assembly, the other generating the final output with the
other
 assembly included?  (you get the idea)

 -aps

 On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:
 
  Hi, I'm new to Maven so forgive me if this something really obvious. I
  looked through the assembly plugin documentation and searched the
  archives, but couldn't find anything covering my use case.
 
  I'm building an assembly using the built-in jar-with-dependencies
  descriptor. That works great. I'd like to include the generated
  assembly inside another custom assembly. The custom assembly would be
  a zip file containing my jar (generated with the
  jar-with-dependencies descriptor) along with some other supporting
  files located in my project root folder.
 
  Is something like this possible? I've tried messing around with my
  custom descriptor, but to no avail. I can generate the zip file, but
  it doesn't contain my jar, only the supporting files. If I'm going in
  the wrong direction with this, I'd appreciate if someone could let me
  know. Thanks.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 What lies behind us and what lies in front of us is of little concern
to
 what lies within us. -Ralph Waldo Emerson



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





--
What lies behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson

Re: Maven with XDoclet - Failing to generate code

2006-12-04 Thread Mick Knutson


Post your xdoclet code please.


On 12/4/06, Leonardo Postacchini [EMAIL PROTECTED] wrote:


  Hello there!

  I am trying to run XDoclet 2 through Maven 2 and I am getting build
failures saying the acess to the diretory where the generated sources was
denied.

  I am running it under Windows XP professional, I checked the directory
permissions and all seems fine. All processes are running under my user
that
is the system administrator.

  Does someone have gone through similar case? Any Ideas where to find the
cause of the acess denial? I am fairly new to Maven and I have no clue
about
how it works.

  I have being digging the documentation for the past few days, but could
not find the answer by myself.

  Thanks for your time and the attention,

  Notivago.





--

Thanks

DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson

Re: [M2] pluginManagement vs. plugin in parent pom.xml

2006-12-04 Thread Eric Redmond

On 12/4/06, nicolas de loof [EMAIL PROTECTED] wrote:

AFAIK the plugins section is inherited by modules, and the
pluginmanagement only defines a common configuration for plugins BUT
does
not enable them on child modules.

Sort of... modules don't inherit anything from their multi-module grouping
projects. Rather, child projects inherit from their parents. Don't confuse
multi-module project management with inheritence (though often they tend to
be the same pom project).

You can then configure commons plugin for all your modules in plugins and

define a common configuration for some plugin that are only used in some
modules (but not all). Those module will then only add a plugin entry
with
no configuration.

Nico.

2006/12/4, CodingPlayer [EMAIL PROTECTED]:

Hi,

i just found out about the existence of the pluginManagement section
in
a
pom.xml.

But i wonder, what is the difference to a plugin section??

Until now, i only use a plugin section in my parent pom.xml, and all
of
the plugins still work in my sub-projects.
So, why should i put these plugins under the pluginManagement section?

thx 4 help
R.C.
--
View this message in context:

http://www.nabble.com/-M2--%3CpluginManagement%3E-vs.-%3Cplugin%3E-in-parent-pom.xml-tf2754489s177.html#a7680557
Sent from the Maven - Users mailing list archive at Nabble.com.

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

--
Eric Redmond
http://codehaus.org/~eredmond

setting dependency to a project with pom packaging?

2006-12-04 Thread Victor Okunev


Can I create a dependency to a project with pom packaging? This would
be convenient rather than creating separate dependencies on each
module it contains. I tried but unsuccessfully, it seems that Maven is
looking for a jar.  Perhaps I am missing something?

Victor

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

Re: setting dependency to a project with pom packaging?


On 12/4/06, Victor Okunev [EMAIL PROTECTED] wrote:


Can I create a dependency to a project with pom packaging? This would
be convenient rather than creating separate dependencies on each
module it contains. I tried but unsuccessfully, it seems that Maven is
looking for a jar.  Perhaps I am missing something?


The default type is jar.  You could try typepom/type but I don't
think it's going to do what you want.

What are you trying to do?  It sounds like you have a pom with
modules and you expect that declaring a dependency on that pom will
add those modules as dependencies.

--
Wendy

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

Re: assembly file and descriptorRefs

2006-12-04 Thread Yann Albou


Thanks Wendy it was very helpful.

You're right it is working with the extensions tag. But I found another 
solution: use the dependencies tag inside the plugin:


I think this tips should be in the assembly plugin documentation.
Here is how I did:

project ...
artifactIdmyAssemblies/artifactId
groupIdcom.mycompany.mygroup/groupId
version1.0.0/version
packagingjar/packaging
/project

Your project just need to contain the assambly descriptor file (the 
directory assemblies is required):

src\main\resources\assemblies\my-distribution.xml
In this project be sure to disable filtering on resources folder 
otherwise variables like ${artifactId} will be replaced


Then in a pom parent  (my-pom-parent) you need to declare the assembly 
configuration:


build
 pluginManagement
  plugins
   plugin
artifactIdmaven-assembly-plugin/artifactId
 configuration
  descriptorRefs
   descriptorRefmy-distribution/descriptorRef
  /descriptorRefs
 /configuration
 executions
  execution
   idmy-assembly/id
   phasepackage/phase
   goals
goalassembly/goal
   /goals
  /execution
 /executions
 dependencies
  dependency
   groupIdcom.mycompany.mygroup/groupId
   artifactIdmyAssemblies/artifactId
   version1.0.0/version
  /dependency
 /dependencies
/plugin
   /plugins
  /pluginManagement
/build


And Then in your project (that inherite from the my-pom-parent) you 
just need to declare the usage of the assembly plugin:


   build
plugins
 plugin
artifactIdmaven-assembly-plugin/artifactId
 /plugin
/plugins
   /build

Of course you can overwrite default plugin configuration.

Hope it will help other people.
Yann.



Wendy Smoak wrote:

On 12/2/06, Yann Albou [EMAIL PROTECTED] wrote:


I saw I can configure a descriptorRefs, but it seems limited to
predefined assembly files (bin, jar-with-dependencies, or src).
I would like to add my own descriptorRef and make it availables to other
projects.


Maybe as a build extension?  Try creating another module and putting
your assembly descriptor in a jar.  Deploy that to your Maven repo,
then pull it in with buildextensionsextension.

I haven't tried it with assembly, but it works for Checkstyle config files.




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

Re: assembly file and descriptorRefs


On 12/3/06, Yann Albou [EMAIL PROTECTED] wrote:


I think this tips should be in the assembly plugin documentation.


Each plugin has a page on the wiki where we encourage users to
contribute examples.  It would be great if you could add this example
to the Assembly plugin's page:

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

--
Wendy

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

Re: setting dependency to a project with pom packaging?

2006-12-04 Thread Victor Okunev


What are you trying to do?  It sounds like you have a pom with
modules and you expect that declaring a dependency on that pom will
add those modules as dependencies.


Yes, that's the idea. Is it possible or I misunderstand the purpose of
projects with pom packaging?

--Vic


On 12/4/06, Wendy Smoak [EMAIL PROTECTED] wrote:

On 12/4/06, Victor Okunev [EMAIL PROTECTED] wrote:

 Can I create a dependency to a project with pom packaging? This would
 be convenient rather than creating separate dependencies on each
 module it contains. I tried but unsuccessfully, it seems that Maven is
 looking for a jar.  Perhaps I am missing something?

The default type is jar.  You could try typepom/type but I don't
think it's going to do what you want.

What are you trying to do?  It sounds like you have a pom with
modules and you expect that declaring a dependency on that pom will
add those modules as dependencies.

--
Wendy

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




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

RE: setting dependency to a project with pom packaging?

2006-12-04 Thread Maven Users List

The project that depends on pom artifact will be depending on all this pom's
dependencies. The pom dependency can be a replacement of a group of other
dependencies. I've tried this two years back and I guess this behavior
didn't change in maven 2.0.4

-Jiaqi

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 04, 2006 11:13 AM
To: Maven Users List
Subject: Re: setting dependency to a project with pom packaging?

On 12/4/06, Victor Okunev [EMAIL PROTECTED] wrote:

 Can I create a dependency to a project with pom packaging? This would 
 be convenient rather than creating separate dependencies on each 
 module it contains. I tried but unsuccessfully, it seems that Maven is 
 looking for a jar.  Perhaps I am missing something?

The default type is jar.  You could try typepom/type but I don't think
it's going to do what you want.

What are you trying to do?  It sounds like you have a pom with modules and
you expect that declaring a dependency on that pom will add those modules as
dependencies.

--
Wendy

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


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

Re: setting dependency to a project with pom packaging?


On 12/4/06, Victor Okunev [EMAIL PROTECTED] wrote:

 What are you trying to do?  It sounds like you have a pom with
 modules and you expect that declaring a dependency on that pom will
 add those modules as dependencies.

Yes, that's the idea. Is it possible or I misunderstand the purpose of
projects with pom packaging?


Pom packaging is typically used for
  1) 'parent' poms (a list of modules, dependencyManagement, dependencies)
  2) 'master' poms (organization level defaults, usually no modules)
  3) overriding the default lifecycle by binding plugin executions
where you want them
  (I'm probably missing something...)

Projects are usually split into modules and arranged in a hierarchy
with inherited dependencies.  Or with dependencyManagement at the
top level to set the version numbers, and then dependencies declared
in the child poms.

It sounds like you either need the normal pom hierarchy so that your
dependencies will be inherited, or possibly some profiles if you're
trying to use different sets of dependencies.

Describe your project and I'm sure someone here can help.

--
Wendy

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

Re: Including an assembly as part of another assembly


Does your jar have any dependencies? If not, then your case is a
little bit different from mine.

My (maybe not so simple) command line application depends on two jars.
If I just run mvn package I get a jar in the target directory like
you. However that jar doesn't include my application's two
dependencies. I have to distribute them separately in order to run my
application.

The assembly plugin's jar-with-dependencies descriptor seems designed
to solve this problem by generating a self-contained jar containing
all dependencies. I want to leverage this to generate a self-contained
jar, and then zip that jar up along with various support files
(readme, etc.).

The approach I'm trying right now is to use the provided
jar-with-dependencies descriptor along a custom descriptor. My pom
looks something like this:

artifactIdmaven-assembly-plugin/artifactId
   configuration
   descriptorRefs
   descriptorRefjar-with-dependencies/descriptorRef
   /descriptorRefs
   descriptors
   descriptormy-custom-descriptor.xml/descriptor
/descriptors
   /configuration

My custom descriptor is similar to yours. The problem is when I enter
mvn assembly:assembly my custom descriptor is always processed
first, before the jar-with-dependencies descriptor. Naturally, the
self-contained jar doesn't exist yet, and I end up with a zip file
full of support files, but no jar.

In a sense, my custom descriptor depends on the jar-with-dependencies
descriptor being run first, but I have no idea how to express this. I
will look into creating multiple modules to see if it will solve my
problem, however it seems somewhat overkill for my application.

Thanks for your help Alexander.


On 12/4/06, Alexander Sack [EMAIL PROTECTED] wrote:

I won't speak for best practices but typically you would create another
module to do the packaging (similar to some of the EAR examples).

For a simple command-line application, my guess is one pom and one assembly
descriptor will be enough.  For my command-line tool I generate the jar and
then assemble the whole applicaiton like so:

snippet from my assembly descriptor XML file:

fileSets
fileSet
  directorytarget/directory
outputDirectory/outputDirectory
includes
  include*.jar/include
/includes
  /fileSet
  fileSet
  outputDirectory/outputDirectory
  directorydist/directory
  includes
include*/include
  /includes
   /fileSet
  /fileSets

Basically dist has some extra static files in it, target is where the JAR
gets built, and then the assembly plugin builds everything together.


-aps


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

Re: setting dependency to a project with pom packaging?

2006-12-04 Thread Daniel Kulp

On Monday 04 December 2006 14:13, Wendy Smoak wrote:
 On 12/4/06, Victor Okunev [EMAIL PROTECTED] wrote:
  Can I create a dependency to a project with pom packaging? This would
  be convenient rather than creating separate dependencies on each
  module it contains. I tried but unsuccessfully, it seems that Maven is
  looking for a jar.  Perhaps I am missing something?

 The default type is jar.  You could try typepom/type but I don't
 think it's going to do what you want.

 What are you trying to do?  It sounds like you have a pom with
 modules and you expect that declaring a dependency on that pom will
 add those modules as dependencies.


Yea, I ran into this this morning as well.I was hoping to depend on 
a pom module so I could then use the dependency 
plugin's copy-dependencies or unpack-dependencies to grab all of them.   
That didn't work.I changed the other projects type to jar which ends up 
deploying an empty jar which works, but that makes that other jar get 
copied/unpacked as well. 


-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

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

Re: Including an assembly as part of another assembly


Eric, I have the eXACT same project.  My command line tool needs a couple of
runtime dependencies.

Let me show how I organize a project which works for me beautifully (maybe
this will help):

dependencies
   dependency
 groupIdacme-depedency-1/groupId
 artifactIdacme-dpendency-1/artifactId
 versionacme-dependency-1/version
   /dependency
   ..
   ..
   ..
 /dependencies
 build
   plugins
   plugin
 artifactIdmaven-compiler-plugin/artifactId
 groupIdorg.apache.maven.plugins/groupId
 configuration
   source1.5/source
   target1.5/target
 /configuration
   /plugin
plugin
   artifactIdmaven-assembly-plugin/artifactId
   version2.0-beta-1/version
   configuration
 descriptorsrc/main/assembly/acme-assembly.xml/descriptor
 outputDirectorytarget/outputDirectory
 workDirectorytarget/assembly/work/workDirectory
 finalNameAcme/finalName
   /configuration
 /plugin
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-jar-plugin/artifactId
 configuration
   archive
 manifest
   addClasspathtrue/addClasspath
 mainClasscom.acme.main.class/mainClass
 /manifest
   /archive
   jarNameacme.jar/jarName
 /configuration
 /plugin
   /plugins
 /build

That creates the JAR file that I need to put in my application zip file to
distribute.  It also adds the runtime dependencies to my manifest.

Then in my acme-assembly.xml:

assembly
 id1.0/id
 formats
   formattar.gz/format
 /formats
 includeBaseDirectoryfalse/includeBaseDirectory
 fileSets
   fileSet
 directorytarget/directory
   outputDirectory/outputDirectory
   includes
 include*.jar/include
   /includes
 /fileSet
 fileSet
 outputDirectory/outputDirectory
 directorydist/directory
 includes
   include*/include
 /includes
  /fileSet
 /fileSets
 dependencySets
   dependencySet
 outputDirectory//outputDirectory
 unpackfalse/unpack
 scoperuntime/scope
   /dependencySet
 /dependencySets
/assembly

The dependencySets tag adds the runtime libraries to the root of my
tar.gzfile so when someone deploys it in a install directory, the
classpath
manifest entry is relative to the current path and everything just works.
When I do mvn package, I get a Acme-1.0.tar.gz with a acme.jar in it a long
with all of its runtime dependencies.  I ALSO in dist have a bunch of
other static files (think license, README, etc.) that gets picked up as
well.

Not sure if this is the absolute best way or only way, but this works for me
every time no hassles!

Let me know,

-aps

On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:


Does your jar have any dependencies? If not, then your case is a
little bit different from mine.

My (maybe not so simple) command line application depends on two jars.
If I just run mvn package I get a jar in the target directory like
you. However that jar doesn't include my application's two
dependencies. I have to distribute them separately in order to run my
application.

The assembly plugin's jar-with-dependencies descriptor seems designed
to solve this problem by generating a self-contained jar containing
all dependencies. I want to leverage this to generate a self-contained
jar, and then zip that jar up along with various support files
(readme, etc.).

The approach I'm trying right now is to use the provided
jar-with-dependencies descriptor along a custom descriptor. My pom
looks something like this:

artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorRefs
descriptorRefjar-with-dependencies/descriptorRef
/descriptorRefs
descriptors
descriptormy-custom-descriptor.xml/descriptor
 /descriptors
/configuration

My custom descriptor is similar to yours. The problem is when I enter
mvn assembly:assembly my custom descriptor is always processed
first, before the jar-with-dependencies descriptor. Naturally, the
self-contained jar doesn't exist yet, and I end up with a zip file
full of support files, but no jar.

In a sense, my custom descriptor depends on the jar-with-dependencies
descriptor being run first, but I have no idea how to express this. I
will look into creating multiple modules to see if it will solve my
problem, however it seems somewhat overkill for my application.

Thanks for your help Alexander.


On 12/4/06, Alexander Sack [EMAIL PROTECTED] wrote:
 I won't speak for best practices but typically you would create another
 module to do the packaging (similar to some of the EAR examples).

 For a simple command-line application, my guess is one pom and one
assembly
 descriptor will be enough.  For my command-line tool I generate the jar
and
 then assemble the whole applicaiton like so:

 snippet from my assembly descriptor XML file:

 fileSets
 fileSet

Re: assembly file and descriptorRefs

2006-12-04 Thread Yann Albou


Done, I added a section How to create your own predefine assembly

Yann.

Wendy Smoak wrote:

On 12/3/06, Yann Albou [EMAIL PROTECTED] wrote:


I think this tips should be in the assembly plugin documentation.


Each plugin has a page on the wiki where we encourage users to
contribute examples.  It would be great if you could add this example
to the Assembly plugin's page:

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




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

Re: Including an assembly as part of another assembly


Our projects are indeed pretty much the same. You just chose to
package it differently than I did (or am trying to).

In your case, you have your dependencies as separate jars. I used the
the jar-with-dependencies descriptor to pack everything into a single
jar.

Unfortunately, I can't seem to get Maven to package up my application
along with it's supporting files the way I want to, so I may just
change my application to use multiple jar files as well.

I appreciate your help with this problem Alexander.


On 12/4/06, Alexander Sack [EMAIL PROTECTED] wrote:

Eric, I have the eXACT same project.  My command line tool needs a couple of
runtime dependencies.

Let me show how I organize a project which works for me beautifully (maybe
this will help):

 dependencies
dependency
  groupIdacme-depedency-1/groupId
  artifactIdacme-dpendency-1/artifactId
  versionacme-dependency-1/version
/dependency
..
..
..
  /dependencies
  build
plugins
plugin
  artifactIdmaven-compiler-plugin/artifactId
  groupIdorg.apache.maven.plugins/groupId
  configuration
source1.5/source
target1.5/target
  /configuration
/plugin
 plugin
artifactIdmaven-assembly-plugin/artifactId
version2.0-beta-1/version
configuration
  descriptorsrc/main/assembly/acme-assembly.xml/descriptor
  outputDirectorytarget/outputDirectory
  workDirectorytarget/assembly/work/workDirectory
  finalNameAcme/finalName
/configuration
  /plugin
  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-jar-plugin/artifactId
  configuration
archive
  manifest
addClasspathtrue/addClasspath
  mainClasscom.acme.main.class/mainClass
  /manifest
/archive
jarNameacme.jar/jarName
  /configuration
  /plugin
/plugins
  /build

That creates the JAR file that I need to put in my application zip file to
distribute.  It also adds the runtime dependencies to my manifest.

Then in my acme-assembly.xml:

assembly
  id1.0/id
  formats
formattar.gz/format
  /formats
  includeBaseDirectoryfalse/includeBaseDirectory
  fileSets
fileSet
  directorytarget/directory
outputDirectory/outputDirectory
includes
  include*.jar/include
/includes
  /fileSet
  fileSet
  outputDirectory/outputDirectory
  directorydist/directory
  includes
include*/include
  /includes
   /fileSet
  /fileSets
  dependencySets
dependencySet
  outputDirectory//outputDirectory
  unpackfalse/unpack
  scoperuntime/scope
/dependencySet
  /dependencySets
/assembly

The dependencySets tag adds the runtime libraries to the root of my
tar.gzfile so when someone deploys it in a install directory, the
classpath
manifest entry is relative to the current path and everything just works.
When I do mvn package, I get a Acme-1.0.tar.gz with a acme.jar in it a long
with all of its runtime dependencies.  I ALSO in dist have a bunch of
other static files (think license, README, etc.) that gets picked up as
well.

Not sure if this is the absolute best way or only way, but this works for me
every time no hassles!

Let me know,

-aps

On 12/4/06, Eric Wang [EMAIL PROTECTED] wrote:

 Does your jar have any dependencies? If not, then your case is a
 little bit different from mine.

 My (maybe not so simple) command line application depends on two jars.
 If I just run mvn package I get a jar in the target directory like
 you. However that jar doesn't include my application's two
 dependencies. I have to distribute them separately in order to run my
 application.

 The assembly plugin's jar-with-dependencies descriptor seems designed
 to solve this problem by generating a self-contained jar containing
 all dependencies. I want to leverage this to generate a self-contained
 jar, and then zip that jar up along with various support files
 (readme, etc.).

 The approach I'm trying right now is to use the provided
 jar-with-dependencies descriptor along a custom descriptor. My pom
 looks something like this:

 artifactIdmaven-assembly-plugin/artifactId
 configuration
 descriptorRefs
 descriptorRefjar-with-dependencies/descriptorRef
 /descriptorRefs
 descriptors
 descriptormy-custom-descriptor.xml/descriptor
  /descriptors
 /configuration

 My custom descriptor is similar to yours. The problem is when I enter
 mvn assembly:assembly my custom descriptor is always processed
 first, before the jar-with-dependencies descriptor. Naturally, the
 self-contained jar doesn't exist yet, and I end up with a zip file
 full of support files, but no jar.

 In a sense, my custom descriptor depends on the jar-with-dependencies
 descriptor being run first, but I

Testing Harness Exception

2006-12-04 Thread Marilyn Sander -X \(marilysa - Digital-X, Inc. at Cisco\)

Hi,

I'm trying to use the testing harness and I get this
exception:

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component
repository:
org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:xml2spec.mojo.

Any idea what this means?

The test I'm running looks like this:

public void testMojoLookup() throws Exception {
File pluginXml = new File(getBasedir(),
src/test/resources/unit/testing/pom.xml);
JPackageMojo mojo = (JPackageMojo)
lookupMojo(xml2spec.mojo,
pluginXml);
assertNotNull(mojo);
}

And the groupId for the mojo
is 

org.jpackage

My pom.xml file that I'm loading in the test code
looks like this:

project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;

build

plugins

plugin

groupIdorg.jpackage/groupId

artifactIdxml2spec.mojo/artifactId

version1.0-SNAPSHOT/version
configuration
/configuration

executions

execution

idgenerate/id

goals

goalgenerate/goal

/goals

/execution

/executions

/plugin

/plugins

/build

/project


Thanks,
- Ole


 

Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com

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

Re: checkstyles

2006-12-04 Thread Trevor Torrez


Yup; i agree; versioning everything associated with the build is a good
idea, and currently we do do this; I was hoping to get rid of the
duplications from project to project in an elegent manner; c'est la vie.

The maven-remote-resources plugin, although it would work, doesn't seem
right either.  After all, I dont want to package the checkstyles.xml file
with anything, it doesnt really get distributed; so thats a no.


On 12/4/06, Wendy Smoak [EMAIL PROTECTED] wrote:


On 12/4/06, Trevor Torrez [EMAIL PROTECTED] wrote:

 Thanks; I had thought about that, I was hoping there was something
simpler
 and just as transparent.  It kinda grates me to create a maven project
and
 repository jar file for one file; using a simple URL is tempting, but
 anywhere we can stick the file we can stick the jar, and the simple URL
idea
 doesnt let us control changes to it;

Yep... this is one of those times when Maven is (not so) gently
encouraging you to do the right thing, (version everything associated
with your build) even if it seems a bit over the top to have to
release a jar containing a single file. :)

--
Wendy

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

Re: Can a Mojo configure another Mojo?

2006-12-04 Thread Dietrich Schulten

Just to close this thread, I managed to configure the compiler plugin
from within my initialize-phase Mojo like so:

Xpp3Dom dom = null;

List plugins = project.getBuildPlugins();

Plugin plugin = null;

if ( plugins != null) {

 for ( Iterator iterator = plugins.iterator(); iterator.hasNext(); ) {

 plugin = (Plugin) iterator.next();

  if ( org.apache.maven.plugins.equals( plugin.getGroupId() )  
maven-compiler-plugin.equals( plugin.getArtifactId() ) ) { 

   dom = (Xpp3Dom) plugin.getConfiguration();

   break;

  }

 }
 // alter the configuration dom

}


Changes to dom directly apply to the target plugin, I ask the Mobile
Java Unified Emulator Interface for the bootclasspath of an emulated
device and pass it to the compiler plugin. That way the J2ME plugin can
easily be configured for various emulators.
This configuration method must be used with care, you can cause all
kinds of surprises because you do things which are not obvious in the pom.

The J2ME bootclasspath is a special case, it is neither a special
compiler which would need its own compiler id, nor is it a normal
runtime dependency. It is a separate SDK with its own language semantics
and own base libraries which uses a normal JDK for cross-compilation.

If you have a better idea to integrate J2ME emulators, let me know.

Regards
Dietrich

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

Re: Testing Harness Exception

2006-12-04 Thread Dietrich Schulten

The first parameter to lookupMojo() must be a goal, not an artifact - in
your case generate should get your Mojo.

HTH
Dietrich

Ole Ersoy schrieb:
 Hi,

 I'm trying to use the testing harness and I get this
 exception:

 org.codehaus.plexus.component.repository.exception.ComponentLookupException:
 Component descriptor cannot be found in the component
 repository:
 org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:xml2spec.mojo.

 Any idea what this means?

 The test I'm running looks like this:

   public void testMojoLookup() throws Exception {
   File pluginXml = new File(getBasedir(),
   src/test/resources/unit/testing/pom.xml);
   JPackageMojo mojo = (JPackageMojo)
 lookupMojo(xml2spec.mojo,
   pluginXml);
   assertNotNull(mojo);
   }

 And the groupId for the mojo
 is 

 org.jpackage

 My pom.xml file that I'm loading in the test code
 looks like this:

 project xmlns=http://maven.apache.org/POM/4.0.0;
   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
 http://maven.apache.org/maven-v4_0_0.xsd;

   build

   plugins

   plugin

   groupIdorg.jpackage/groupId

   artifactIdxml2spec.mojo/artifactId

   version1.0-SNAPSHOT/version
   configuration
   /configuration

   executions

   execution

   idgenerate/id

   goals

   goalgenerate/goal

   /goals

   /execution

   /executions

   /plugin

   /plugins

   /build

 /project


 Thanks,
 - Ole


  
 
 Need a quick answer? Get one in minutes from people who know.
 Ask your question on www.Answers.yahoo.com

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

   


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

RE: MAVEN_INSTALL_DIR/conf/settings.xml

 See below.  I've deleted much of the thread, but the relevant bit
remains.

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, December 04, 2006 6:13 AM
 To: users@maven.apache.org
 Subject: RE: MAVEN_INSTALL_DIR/conf/settings.xml

[ some stuff deleted ]

 (Where are the gears grinding?)

 I see: You have a build that has a dependency that relates to 
 build-time.
 Despite the fact that Maven creates it artifacts and install 
 them in a local repository, there is some other thing in your 
 corporate environment that it is time conscience.

 If this is the case then what would be case if you are build 
 with Apache Ant, then this build-time dependency will still 
 exist regardless of the infrastructure technology.

 I am not sure, then, if Maven can solve this, especially f 
 you cannot isolate the build-time dependency.

 Having said, I think a user-profile related dependency can be 
 a problem for you. If you a user-profile that shared between 
 teams, divisions, departments then the environment variables 
 can be changed ad hoc. Therefore again Maven cannot 

Perhaps I mis-stated a bit.  There is not a time dependency.  There are
two
ways that we invoke maven.  The first is with the mvn command, to do the
java build.
The second is later, after the mvn build has created the local
repository, where we 
invoke a maven copy ant task to fetch some artifacts from the local
repository.  
The fetching from the local repository is so we can build an install
file using a 
commercial tool for building a GUI installer.

We have no problem specifying a repository when initially calling mvn.
We just use
the mvn command line either to directly specify the repository location
using -D, or
use the -s argument to specify the location of the settings.xml file
that in turn
specifies the location of the local repository.  The trouble is, the
copy task will only
look in ~/.m2/settings.xml.  If we are limited to use of
~/.m2/settings.xml for specifying
the location of the local repository, then a second build of a different
product, BY THE SAME
USER before the first build is finished, will clobber the local
repository of the first build.

Thus we are stuck with using the same settings.xml file for all builds
done by one user, and 
therefore also the same local repository for all builds done by one
user.  The only way to 
have one user do multiple builds at the same time is to put the local
repository on a local partition such as /tmp or /var/tmp or some such.
Then, at least, we can do one build per 
machine per user.  This is really wasteful of machine resources,
however. 

--Marilyn

  I've filed the JIRA request.  I got the automated acknowledgment 
  (MNG-2684), but that's all so far.
  --Marilyn

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

Re: Testing Harness Exception

Oooh - 

Thanks Dietrich!  That may have taken a while to
figure out.

- Ole
--- Dietrich Schulten [EMAIL PROTECTED] wrote:

 The first parameter to lookupMojo() must be a goal,
 not an artifact - in
 your case generate should get your Mojo.
 
 HTH
 Dietrich
 
 Ole Ersoy schrieb:
  Hi,
 
  I'm trying to use the testing harness and I get
 this
  exception:
 
 

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
  Component descriptor cannot be found in the
 component
  repository:
 

org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:xml2spec.mojo.
 
  Any idea what this means?
 
  The test I'm running looks like this:
 
  public void testMojoLookup() throws Exception {
  File pluginXml = new File(getBasedir(),
  src/test/resources/unit/testing/pom.xml);
  JPackageMojo mojo = (JPackageMojo)
  lookupMojo(xml2spec.mojo,
  pluginXml);
  assertNotNull(mojo);
  }
 
  And the groupId for the mojo
  is 
 
  org.jpackage
 
  My pom.xml file that I'm loading in the test code
  looks like this:
 
  project xmlns=http://maven.apache.org/POM/4.0.0;
  

xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  

xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
  http://maven.apache.org/maven-v4_0_0.xsd;
 
  build
 
  plugins
 
  plugin
 
  groupIdorg.jpackage/groupId
 
  artifactIdxml2spec.mojo/artifactId
 
  version1.0-SNAPSHOT/version
  configuration
  /configuration
 
  executions
 
  execution
 
  idgenerate/id
 
  goals
 
  goalgenerate/goal
 
  /goals
 
  /execution
 
  /executions
 
  /plugin
 
  /plugins
 
  /build
 
  /project
 
 
  Thanks,
  - Ole
 
 
   
 


  Need a quick answer? Get one in minutes from
 people who know.
  Ask your question on www.Answers.yahoo.com
 
 

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

 
 

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


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

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

Re: MAVEN_INSTALL_DIR/conf/settings.xml


On 12/4/06, Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco)
[EMAIL PROTECTED]

Perhaps I mis-stated a bit.  There is not a time dependency.  There are
two
ways that we invoke maven.  The first is with the mvn command, to do the
java build.
The second is later, after the mvn build has created the local
repository, where we
invoke a maven copy ant task to fetch some artifacts from the local
repository.
The fetching from the local repository is so we can build an install
file using a
commercial tool for building a GUI installer.


The local repository is intended to be used by a single developer.  If
you need to share artifacts, then deploy them to a remote internal
corporate repository.

The snapshot and release deployment urls are set in
distributionManagement for each project.

--
Wendy

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

Re: Testing Harness Exception

Hmmm

I tried it with generate and I still get almost the
same exception:

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component
repository:
org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:generate.

Any other ideas?

Thanks again,
- Ole



--- Dietrich Schulten [EMAIL PROTECTED] wrote:

 The first parameter to lookupMojo() must be a goal,
 not an artifact - in
 your case generate should get your Mojo.
 
 HTH
 Dietrich
 
 Ole Ersoy schrieb:
  Hi,
 
  I'm trying to use the testing harness and I get
 this
  exception:
 
 

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
  Component descriptor cannot be found in the
 component
  repository:
 

org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:xml2spec.mojo.
 
  Any idea what this means?
 
  The test I'm running looks like this:
 
  public void testMojoLookup() throws Exception {
  File pluginXml = new File(getBasedir(),
  src/test/resources/unit/testing/pom.xml);
  JPackageMojo mojo = (JPackageMojo)
  lookupMojo(xml2spec.mojo,
  pluginXml);
  assertNotNull(mojo);
  }
 
  And the groupId for the mojo
  is 
 
  org.jpackage
 
  My pom.xml file that I'm loading in the test code
  looks like this:
 
  project xmlns=http://maven.apache.org/POM/4.0.0;
  

xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  

xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
  http://maven.apache.org/maven-v4_0_0.xsd;
 
  build
 
  plugins
 
  plugin
 
  groupIdorg.jpackage/groupId
 
  artifactIdxml2spec.mojo/artifactId
 
  version1.0-SNAPSHOT/version
  configuration
  /configuration
 
  executions
 
  execution
 
  idgenerate/id
 
  goals
 
  goalgenerate/goal
 
  /goals
 
  /execution
 
  /executions
 
  /plugin
 
  /plugins
 
  /build
 
  /project
 
 
  Thanks,
  - Ole
 
 
   
 


  Need a quick answer? Get one in minutes from
 people who know.
  Ask your question on www.Answers.yahoo.com
 
 

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

 
 

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



 

Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

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

Re: Testing Harness Exception

Hey there,

Never mind - I ran 

mvn eclipse:clean eclipse:eclipse 

and it fixed itself.

Thanks,
- Ole


--- Ole Ersoy [EMAIL PROTECTED] wrote:

 Hmmm
 
 I tried it with generate and I still get almost the
 same exception:
 

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
 Component descriptor cannot be found in the
 component
 repository:

org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:generate.
 
 Any other ideas?
 
 Thanks again,
 - Ole
 
 
 
 --- Dietrich Schulten [EMAIL PROTECTED] wrote:
 
  The first parameter to lookupMojo() must be a
 goal,
  not an artifact - in
  your case generate should get your Mojo.
  
  HTH
  Dietrich
  
  Ole Ersoy schrieb:
   Hi,
  
   I'm trying to use the testing harness and I get
  this
   exception:
  
  
 

org.codehaus.plexus.component.repository.exception.ComponentLookupException:
   Component descriptor cannot be found in the
  component
   repository:
  
 

org.apache.maven.plugin.Mojoorg.jpackage:xml2spec.mojo:1.0-SNAPSHOT:xml2spec.mojo.
  
   Any idea what this means?
  
   The test I'm running looks like this:
  
 public void testMojoLookup() throws Exception {
 File pluginXml = new File(getBasedir(),
 src/test/resources/unit/testing/pom.xml);
 JPackageMojo mojo = (JPackageMojo)
   lookupMojo(xml2spec.mojo,
 pluginXml);
 assertNotNull(mojo);
 }
  
   And the groupId for the mojo
   is 
  
   org.jpackage
  
   My pom.xml file that I'm loading in the test
 code
   looks like this:
  
   project
 xmlns=http://maven.apache.org/POM/4.0.0;
   
 

xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   
 

xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
   http://maven.apache.org/maven-v4_0_0.xsd;
  
 build
  
 plugins
  
 plugin
  
 groupIdorg.jpackage/groupId
  
 artifactIdxml2spec.mojo/artifactId
  
 version1.0-SNAPSHOT/version
 configuration
 /configuration
  
 executions
  
 execution
  
 idgenerate/id
  
 goals
  
 goalgenerate/goal
  
 /goals
  
 /execution
  
 /executions
  
 /plugin
  
 /plugins
  
 /build
  
   /project
  
  
   Thanks,
   - Ole
  
  

  
 


   Need a quick answer? Get one in minutes from
  people who know.
   Ask your question on www.Answers.yahoo.com
  
  
 

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

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


 Cheap talk?
 Check out Yahoo! Messenger's low PC-to-Phone call
 rates.
 http://voice.yahoo.com
 

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



 

Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com

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

ContainerException: Deployable failed to finish deploying within the timeout period

2006-12-04 Thread Brad Harper

Hello:

Has anyone seen this error? It occurred when performing the command

   % mvn clean compile war:war cargo:undeploy cargo:deploy

The war seems to have been properly deployed (Tomcat 5.5.9) when I
look. I get a 404 error when I try the expected URL.

Thanks.

Brad

[INFO] [yer.DeployerWatchdog] Deployable failed to finish deploying within the 
timeout period [2]. The Deployable state is thus unknown.
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Deployable failed to finish deploying within the timeout period [2]. 
The Deployable state is thus unknown.
[INFO] 
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Deployable failed to finish 
deploying within the timeout period [2]. The Deployable state is thus 
unknown.
at 
org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:109)
at 
org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watchForAvailability(DeployerWatchdog.java:78)
at 
org.codehaus.cargo.container.tomcat.internal.AbstractTomcatDeployer.deploy(AbstractTomcatDeployer.java:102)
at 
org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:75)
at 
org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:106)
at 
org.codehaus.cargo.maven2.AbstractDeployerMojo.execute(AbstractDeployerMojo.java:43)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

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

Re: ContainerException: Deployable failed to finish deploying within the timeout period


On 12/4/06, Brad Harper [EMAIL PROTECTED] wrote:


Has anyone seen this error? It occurred when performing the command

   % mvn clean compile war:war cargo:undeploy cargo:deploy

The war seems to have been properly deployed (Tomcat 5.5.9) when I
look. I get a 404 error when I try the expected URL.


For questions about Cargo, please come join us on the Cargo user list:

http://cargo.codehaus.org/Mailing+Lists

--
Wendy

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

How to run checkstyle earlier in the build lifecycle?

I know it runs as part of mvn site, but some people wish to see it run 
earlier, say as part of install, or even test. How do I do that?

--
cg

P.S. I'm still struggling with multi-module project site generation. I 
just can't get the navigation links to work.

--
cg

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

Re: How to run checkstyle earlier in the build lifecycle?


On 12/4/06, Christian Goetze [EMAIL PROTECTED] wrote:


I know it runs as part of mvn site, but some people wish to see it run
earlier, say as part of install, or even test. How do I do that?


You can bind a plugin execution to any phase of the build lifecycle.

  http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

  http://maven.apache.org/plugins/maven-checkstyle-plugin/index.html


P.S. I'm still struggling with multi-module project site generation. I
just can't get the navigation links to work.


Check JIRA to see if you might be running into a known issue, then you
might want to start a new thread with a descriptive subject. :)

--
Wendy

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

How to ignore certain files in the source tree


Sorry if this is another FAQ, but I can't find an easy answer...

I would like to systematically ignore certain source files in the build. 
I don;t want them to appear in my jars or any other artifacts. Is there 
a global way to exclude them?

--
cg

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

Re: How to ignore certain files in the source tree


On 12/4/06, Christian Goetze [EMAIL PROTECTED] wrote:


I would like to systematically ignore certain source files in the build.
I don;t want them to appear in my jars or any other artifacts. Is there
a global way to exclude them?


Where are the files located, and what type of files are they?

One option is to move them to a directory structure that is not used
by default.  For example, I put Selenium tests in src/test/selenium,
and Maven ignores them (unless I activate a profile that is
specifically configured to do something with them.)

If they are under src/main/resources, you can use resourceexcludes
to ignore them.

  http://maven.apache.org/ref/2.0.4/maven-model/maven.html

--
Wendy

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

Re: How to ignore certain files in the source tree


Wendy Smoak wrote:


On 12/4/06, Christian Goetze [EMAIL PROTECTED] wrote:


I would like to systematically ignore certain source files in the build.
I don;t want them to appear in my jars or any other artifacts. Is there
a global way to exclude them?



Where are the files located, and what type of files are they?


They are . files generated by the build system into which I'm 
embedding maven. They contain additional metadata about the files and I 
do not have the option of moving them around. They will appear wherever 
source files exist, and they seem to end up in the jars generated by the 
packaging.



If they are under src/main/resources, you can use resourceexcludes
to ignore them.

  http://maven.apache.org/ref/2.0.4/maven-model/maven.html

I'm wondering if there isn't an option for the maven-jar-plugin, but I 
can't seem to find any.

--
cg


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

Re: How to ignore certain files in the source tree


On 12/4/06, Christian Goetze [EMAIL PROTECTED] wrote:


 Where are the files located, and what type of files are they?

They are . files generated by the build system into which I'm
embedding maven. They contain additional metadata about the files and I
do not have the option of moving them around. They will appear wherever
source files exist, and they seem to end up in the jars generated by the
packaging.


If they are under src/main/java, it's odd that they're getting
included.  IME only .java files from there get compiled, everything
else is ignored.  (For example, if you have .properties files stored
with your source code, you have to add a resource to pick them up.)


I'm wondering if there isn't an option for the maven-jar-plugin, but I
can't seem to find any.


The location of sources and resources is a build level thing, not
specific to the jar plugin.

--
Wendy

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

Re: How to ignore certain files in the source tree