Re: Failed attempts to download POMs

2005-10-23 Thread Brett Porter
It's a known issue we'll look to fix in 2.0.1. You can alleviate it by
using the main maven2 repository for artifacts that already exist
there, and creating short poms for anything else.

- Brett

On 10/22/05, Trey Moore [EMAIL PROTECTED] wrote:
  How do I prevent Maven 2 from attemping to download a POM for every
 dependency every time I run it?
  Do I actually have to create a local POM for every single one of my
 existing dependencies for which a POM cannot be found online?
  My project is building fine, but I have to wait a long time while it pings
 the repositories for missing POM files.
  -Trey
[WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/jide/poms/jide-components-1.8.3.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/jide/jide-components/1.8.3/jide-components-1.8.3.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/jide/poms/velocity-dep-1.4.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/jide/velocity-dep/1.4/velocity-dep-1.4.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 [INFO] snapshot com.globalshare:datasourcesnew:1.0-SNAPSHOT: checking for
 updates from localrepo
 Downloading: http://dell4500/maven/mssqlserver/poms/mssqlserver-1.0.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/mssqlserver/mssqlserver/1.0/mssqlserver-1.0.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/jbcl/poms/jbcl-2005.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading: http://repo1.maven.org/maven2/jbcl/jbcl/2005/jbcl-2005.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/coroutine/poms/coroutine4java-1.0.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/coroutine/coroutine4java/1.0/coroutine4java-1.0.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/jpedal/poms/jpedal-1.0.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading: http://repo1.maven.org/maven2/jpedal/jpedal/1.0/jpedal-1.0.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/mssqlserver/poms/msutil-1.0.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/mssqlserver/msutil/1.0/msutil-1.0.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/coroutine/poms/javadde-1.0.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/coroutine/javadde/1.0/javadde-1.0.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/j2ee/poms/j2ee-1.4.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading: http://repo1.maven.org/maven2/j2ee/j2ee/1.4/j2ee-1.4.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/poi/poms/poi-2.0-final-20040126.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading:
 http://repo1.maven.org/maven2/poi/poi/2.0-final-20040126/poi-2.0-final-20040126.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/jtidy/poms/jtidy-r8.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading: http://repo1.maven.org/maven2/jtidy/jtidy/r8/jtidy-r8.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading: http://dell4500/maven/j2ee/poms/mail-1.4.pom
 [WARNING] Unable to get resource from repository localrepo (
 http://dell4500/maven)
 Downloading: http://repo1.maven.org/maven2/j2ee/mail/1.4/mail-1.4.pom
 [WARNING] Unable to get resource from repository central (
 http://repo1.maven.org/maven2)
 Downloading:
 http://dell4500/maven/commons-email/poms/commons-email-1.0-dev.pom



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



M2 basic question about generate-sources and xdoclet

2005-10-23 Thread Pete
1) I'm using the xdoclet plugin to generate the EJB .java files for
Home, Remote etc,
these are currently going in the ejb JAR as .java files, surely the
.class files should go in the .jar file.

The only .class file in my EJB jar is the Bean.class that has my
xdoclet tags on it.

2) Where should I store the generated .java files, as I don't want
them in SCM, but I'm thiniking if their not under src\main\java then
they won't get compiled.


I'm using :-

plugin
   artifactIdxdoclet-maven-plugin/artifactId
   groupIdorg.codehaus.mojo/groupId
   version1.0-alpha-1/version
   executions
   execution
   phasegenerate-sources/phase
   goals
   goalxdoclet/goal
   /goals
   configuration
   tasks
   !--
Here is the code that would normally appear inside a
target block in an ant script  : --
  
ejbdoclet destdir=${project.build.outputDirectory}
  
fileset dir=${basedir}/src/main/java includes=**/*Bean.java/
  
entitycmp destDir=${project.build.outputDirectory}/
  
 session/
  
remoteinterface pattern={0}Remote/
  
homeinterface pattern={0}RemoteHome/
  
localhomeinterface/
  
deploymentdescriptor
destDir=${project.build.outputDirectory}/META-INF/
  
orion destdir=${build.dir}/ejb/META-INF /
   /ejbdoclet
   /tasks
   /configuration
   /execution
   /executions
   /plugin

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



RE: Sample plugin.

2005-10-23 Thread Daniel Or
My mistake.

I didn't double check myself.

The source location was missing.

 

__

 

Daniel Or

_._._._._._._._._.



From: Daniel Or 
Sent: Sunday, October 23, 2005 11:57 AM
To: users@maven.apache.org
Subject: Sample plugin.

 

Hi.

I followed the instructions on the site regarding the sample plugin
(http://maven.apache.org/maven2/guides/plugin/guide-java-plugin-developm
ent.html ). 

After I ran 'mvn install' the plugin was installed (all XMLs and a jar
with more XMLs).

However, no classes were created. It seems that the 'sayhi' goal was not
recognized.

 

I used m2 release and JDK 1.5.0_4.

 

I'd appreciate if anyone can give me a clue.

 

10x.

 

   ___

   Daniel Or

   __

 

 



Re: [M2] deployment : session is down

2005-10-23 Thread Piotr Bzdyl

Hi,

We upgraded to a jsch that was supposed to have fixed it, but it seems
to have gotten worse.

The main workaround at this point is to use scpexe:// or ftp:// instead.

http://maven.apache.org/guides/mini/guide-deploy-ftp.html details
using ftp - the steps for scpexe (wagon-ssh-external) are similar.

  
I have notice that it happens more rarely when you do mvn deploy from 
remote host. When the central repository is on the same host where you 
run mvn deploy it happens almost every time.


Best regards,
Piotrek

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



Cargo plugins support M2 ?

2005-10-23 Thread Pete
Hi there,

I would like to use cargo to start my app server / deploy via maven ?
I'm guessing that the cargo maven plugin support will allow this ?
But I'm using M2, is the plugin M2 compatible ?

Any advice greatfully received ? e.g. any examples of how to
configure/use the cargo maven goals ?

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



Re: Cargo plugins support M2 ?

2005-10-23 Thread Mark Hobson
On 23/10/05, Pete [EMAIL PROTECTED] wrote:
 Hi there,

 I would like to use cargo to start my app server / deploy via maven ?
 I'm guessing that the cargo maven plugin support will allow this ?
 But I'm using M2, is the plugin M2 compatible ?

 Any advice greatfully received ? e.g. any examples of how to
 configure/use the cargo maven goals ?

Hi Pete,

The existing Cargo maven plugin is for maven1 only.  I've started the
Cargo plugin for m2 which currently only exists in the Cargo svn
trunk.  I'm hoping to find some time soon to finish it off, but am
unfortunately quite busy at the moment.

You may want to continue this conversation over at [EMAIL PROTECTED]

Cheers,

Mark

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



M2 with oc4j

2005-10-23 Thread Pete
Has anyone out there got any suggestions of how to integrate a M2
build with Oracle's oc4j J2EE container.

I'm looking to be able to start the oc4j container, deploy, run
incontainer JUnitEE tests etc, from M2.

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



Re: Re: [m2] Fatal error trying mvn site

2005-10-23 Thread Wim Deblauwe
The issue in JIRA (http://jira.codehaus.org/browse/MNG-1216) states that it
has been fixed in 2.0, but I was running the released 2.0 of Maven. Is the
fix version of the bug wrong in JIRA?

regards,

Wim

2005/10/22, Brett Porter [EMAIL PROTECTED]:

 It is in JIRA, we'll try and get a fix out as soon as possible.

 On 10/21/05, Bernd Mau [EMAIL PROTECTED] wrote:
  Yes, it really seems to be a bug and I coud not find an issue in the
  JIRA concerning this problem.
 
 
  -
  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: Pulling API and SRC Jars from Repos

2005-10-23 Thread Wim Deblauwe
Cool, hopefully the idea plugin will take advantage of this soon! (and the
documentation of maven will mention how to generate such artifacts)

regards,

Wim

2005/10/22, Brett Porter [EMAIL PROTECTED]:

 In Maven2, yes, it is standardised (-src and -javadoc) and they can be
 published to the repository by default.

 - Brett

 On 10/21/05, Sal Campana [EMAIL PROTECTED] wrote:
  Are there any plans to add support of optionally specifying API and SRC
 jars
  for a given dependency?
 
  We've built a plugin to do this, and then update our IDE, but its not
  standard...but if it were standard in Maven (extra xml tags?) then all
 the
  IDE plugins would support it
 
  Based on this page:
 
  *http://docs.codehaus.org/pages/viewpage.action?pageId=22230*
 
  It seems the classifier attribute can be used to associate src and api
 jars
  with a regular jar dependency. It shows *javasrc and *javadoc...
 
  Will the extensions be standardized?
 
  It seems that if Maven would standardize how these things are defined,
 then
  generic plugins could be made for the IDEs which can take advantage of
 this.
 
 
  Thx!
 
 

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




Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Milos Kleint
well, javadocs culd be published easily in maven 1.x but AFAIK it was almost
completely unused (try searching the ibiblio.org http://ibiblio.orgrepository)
So to get the feature useful, there should be a more aggressive policy IMHO.
Like when uploading to remote repository always upload javadocs and sources
as well by default.. otherwise it will be again unused.

just my 2 cents.

Milos

On 10/21/05, Brett Porter [EMAIL PROTECTED] wrote:

 In Maven2, yes, it is standardised (-src and -javadoc) and they can be
 published to the repository by default.

 - Brett

 On 10/21/05, Sal Campana [EMAIL PROTECTED] wrote:
  Are there any plans to add support of optionally specifying API and SRC
 jars
  for a given dependency?
 
  We've built a plugin to do this, and then update our IDE, but its not
  standard...but if it were standard in Maven (extra xml tags?) then all
 the
  IDE plugins would support it
 
  Based on this page:
 
  *http://docs.codehaus.org/pages/viewpage.action?pageId=22230*
 
  It seems the classifier attribute can be used to associate src and api
 jars
  with a regular jar dependency. It shows *javasrc and *javadoc...
 
  Will the extensions be standardized?
 
  It seems that if Maven would standardize how these things are defined,
 then
  generic plugins could be made for the IDEs which can take advantage of
 this.
 
 
  Thx!
 
 

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




Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Ralph Pöllath

On 23.10.2005, at 14:08, Milos Kleint wrote:
well, javadocs culd be published easily in maven 1.x but AFAIK it  
was almost
completely unused (try searching the ibiblio.org http:// 
ibiblio.orgrepository)
So to get the feature useful, there should be a more aggressive  
policy IMHO.
Like when uploading to remote repository always upload javadocs and  
sources

as well by default.. otherwise it will be again unused.


This has been discussed here previously, but I totally agree that  
javadocs and sources should be uploaded by default.


Cheers,
-Ralph.


On 10/21/05, Brett Porter [EMAIL PROTECTED] wrote:
In Maven2, yes, it is standardised (-src and -javadoc) and they  
can be

published to the repository by default.

- Brett

On 10/21/05, Sal Campana [EMAIL PROTECTED] wrote:

Are there any plans to add support of optionally specifying API  
and SRC



jars


for a given dependency?

We've built a plugin to do this, and then update our IDE, but its  
not
standard...but if it were standard in Maven (extra xml tags?)  
then all



the


IDE plugins would support it

Based on this page:

*http://docs.codehaus.org/pages/viewpage.action?pageId=22230*

It seems the classifier attribute can be used to associate src  
and api



jars


with a regular jar dependency. It shows *javasrc and *javadoc...

Will the extensions be standardized?

It seems that if Maven would standardize how these things are  
defined,



then

generic plugins could be made for the IDEs which can take  
advantage of



this.




Thx!





-
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: Pulling API and SRC Jars from Repos

2005-10-23 Thread Wim Deblauwe
Wow, I was unaware of that being possible. How do you do it?

regards,

Wim

2005/10/23, Ralph Pöllath [EMAIL PROTECTED]:

 On 23.10.2005, at 14:08, Milos Kleint wrote:
  well, javadocs culd be published easily in maven 1.x but AFAIK it
  was almost
  completely unused (try searching the ibiblio.org 
  http://ibiblio.orghttp://
  ibiblio.org http://ibiblio.orgrepository)
  So to get the feature useful, there should be a more aggressive
  policy IMHO.
  Like when uploading to remote repository always upload javadocs and
  sources
  as well by default.. otherwise it will be again unused.

 This has been discussed here previously, but I totally agree that
 javadocs and sources should be uploaded by default.

 Cheers,
 -Ralph.

  On 10/21/05, Brett Porter [EMAIL PROTECTED] wrote:
  In Maven2, yes, it is standardised (-src and -javadoc) and they
  can be
  published to the repository by default.
 
  - Brett
 
  On 10/21/05, Sal Campana [EMAIL PROTECTED] wrote:
 
  Are there any plans to add support of optionally specifying API
  and SRC
 
  jars
 
  for a given dependency?
 
  We've built a plugin to do this, and then update our IDE, but its
  not
  standard...but if it were standard in Maven (extra xml tags?)
  then all
 
  the
 
  IDE plugins would support it
 
  Based on this page:
 
  *http://docs.codehaus.org/pages/viewpage.action?pageId=22230*
 
  It seems the classifier attribute can be used to associate src
  and api
 
  jars
 
  with a regular jar dependency. It shows *javasrc and *javadoc...
 
  Will the extensions be standardized?
 
  It seems that if Maven would standardize how these things are
  defined,
 
  then
 
  generic plugins could be made for the IDEs which can take
  advantage of
 
  this.
 
 
 
  Thx!
 
 
 
 
  -
  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: Re: [m2] Fatal error trying mvn site

2005-10-23 Thread Brett Porter
I think this was a jira miscommunication. It's just waiting for a
release of the plugin for a fix, these have their own release cycles.
We're still trying to determine the most useful technique for doing
this in JIRA.

- Brett

On 10/23/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
 The issue in JIRA (http://jira.codehaus.org/browse/MNG-1216) states that it
 has been fixed in 2.0, but I was running the released 2.0 of Maven. Is the
 fix version of the bug wrong in JIRA?

 regards,

 Wim

 2005/10/22, Brett Porter [EMAIL PROTECTED]:
 
  It is in JIRA, we'll try and get a fix out as soon as possible.
 
  On 10/21/05, Bernd Mau [EMAIL PROTECTED] wrote:
   Yes, it really seems to be a bug and I coud not find an issue in the
   JIRA concerning this problem.
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 



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



Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Brett Porter
We are going to add this to the recommended upload request, and it is
by default in m2 using the release plugin. Just using deploy without
the profile activated does not do it, but this is because we don't
want to build them for snapshots and development builds due to the
time involved.

We'll get this documented, but we'll certainly be encouraging projects
on ibiblio to do so.

- Brett

On 10/23/05, Ralph Pöllath [EMAIL PROTECTED] wrote:
 On 23.10.2005, at 14:08, Milos Kleint wrote:
  well, javadocs culd be published easily in maven 1.x but AFAIK it
  was almost
  completely unused (try searching the ibiblio.org http://
  ibiblio.orgrepository)
  So to get the feature useful, there should be a more aggressive
  policy IMHO.
  Like when uploading to remote repository always upload javadocs and
  sources
  as well by default.. otherwise it will be again unused.

 This has been discussed here previously, but I totally agree that
 javadocs and sources should be uploaded by default.

 Cheers,
 -Ralph.

  On 10/21/05, Brett Porter [EMAIL PROTECTED] wrote:
  In Maven2, yes, it is standardised (-src and -javadoc) and they
  can be
  published to the repository by default.
 
  - Brett
 
  On 10/21/05, Sal Campana [EMAIL PROTECTED] wrote:
 
  Are there any plans to add support of optionally specifying API
  and SRC
 
  jars
 
  for a given dependency?
 
  We've built a plugin to do this, and then update our IDE, but its
  not
  standard...but if it were standard in Maven (extra xml tags?)
  then all
 
  the
 
  IDE plugins would support it
 
  Based on this page:
 
  *http://docs.codehaus.org/pages/viewpage.action?pageId=22230*
 
  It seems the classifier attribute can be used to associate src
  and api
 
  jars
 
  with a regular jar dependency. It shows *javasrc and *javadoc...
 
  Will the extensions be standardized?
 
  It seems that if Maven would standardize how these things are
  defined,
 
  then
 
  generic plugins could be made for the IDEs which can take
  advantage of
 
  this.
 
 
 
  Thx!
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 


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



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



Re: Re: [m2] Fatal error trying mvn site

2005-10-23 Thread Arik Kfir
Hi,

Seems to me that each m2 plugin should reside in its own project, or,
create more *versions* in JIRA that pertain to plugin-issues only.

Currently, it's impossible to track the roadmap/changelog for plugin releases.

Quickest route imo: leave everything as is, but create more versions
in the MNG project, like maven-2.0.1, compile-plugin-2.0,
compile-plugin-2.1, etc.

On 10/23/05, Brett Porter [EMAIL PROTECTED] wrote:
 I think this was a jira miscommunication. It's just waiting for a
 release of the plugin for a fix, these have their own release cycles.
 We're still trying to determine the most useful technique for doing
 this in JIRA.

 - Brett

 On 10/23/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
  The issue in JIRA (http://jira.codehaus.org/browse/MNG-1216) states that it
  has been fixed in 2.0, but I was running the released 2.0 of Maven. Is the
  fix version of the bug wrong in JIRA?
 
  regards,
 
  Wim
 
  2005/10/22, Brett Porter [EMAIL PROTECTED]:
  
   It is in JIRA, we'll try and get a fix out as soon as possible.
  
   On 10/21/05, Bernd Mau [EMAIL PROTECTED] wrote:
Yes, it really seems to be a bug and I coud not find an issue in the
JIRA concerning this problem.
   
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 

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



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



Testing a M2 plugin ??

2005-10-23 Thread mattias.olofsson
Hi,

I’m trying to migrate my m1 plugins to m2,  and have some questions before I
get started.



In m1 there was a directory structure and a specific goal to test the
plugin.
How should I test a plugin in m2.



If the answer to 1. is to junit test it using surefire.
How would I then populate my MOJO object since some instance variables is
and should be private.
For instance:


/**

 * Location of the file.

 * @parameter expression=${project.build.directory}

 * @required

 */

private File outputDirectory;



Is there a tutorial how to do a complete plugin development cycle, with
testing and all ?
( I used the mojo archetype in archetype plugin to create my plugin project
and then read this, which is a good start
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html


.matte




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



Re: M2 basic question about generate-sources and xdoclet

2005-10-23 Thread Pete
I haven't solved by using :-

ejbdoclet destdir=${project.build.directory}/generated-sources/xdoclet

although I notice the output .jar file has both the generated .class
files and the .java
is this able to be corrected ?



On 23/10/05, Pete [EMAIL PROTECTED] wrote:
 1) I'm using the xdoclet plugin to generate the EJB .java files for
 Home, Remote etc,
 these are currently going in the ejb JAR as .java files, surely the
 .class files should go in the .jar file.

 The only .class file in my EJB jar is the Bean.class that has my
 xdoclet tags on it.

 2) Where should I store the generated .java files, as I don't want
 them in SCM, but I'm thiniking if their not under src\main\java then
 they won't get compiled.


 I'm using :-

 plugin
   artifactIdxdoclet-maven-plugin/artifactId
   groupIdorg.codehaus.mojo/groupId
   version1.0-alpha-1/version
   executions
   execution
   phasegenerate-sources/phase
   goals
   goalxdoclet/goal
   /goals
   configuration
   tasks
   !--
 Here is the code that would normally appear inside a
 target block in an ant script  : --

 ejbdoclet destdir=${project.build.outputDirectory}

 fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

 entitycmp destDir=${project.build.outputDirectory}/

  session/

 remoteinterface pattern={0}Remote/

 homeinterface pattern={0}RemoteHome/

 localhomeinterface/

 deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF/

 orion destdir=${build.dir}/ejb/META-INF /
   /ejbdoclet
   /tasks
   /configuration
   /execution
   /executions
   /plugin


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



Re: M2 basic question about generate-sources and xdoclet

2005-10-23 Thread Pete
Meant to say I HAVE solved by using :-

 ejbdoclet destdir=${project.build.directory}/generated-sources/xdoclet

 although I notice the output .jar file has both the generated .class
 files and the .java
 is this able to be corrected ?

On 23/10/05, Pete [EMAIL PROTECTED] wrote:
 I haven't solved by using :-

 ejbdoclet destdir=${project.build.directory}/generated-sources/xdoclet

 although I notice the output .jar file has both the generated .class
 files and the .java
 is this able to be corrected ?



 On 23/10/05, Pete [EMAIL PROTECTED] wrote:
  1) I'm using the xdoclet plugin to generate the EJB .java files for
  Home, Remote etc,
  these are currently going in the ejb JAR as .java files, surely the
  .class files should go in the .jar file.
 
  The only .class file in my EJB jar is the Bean.class that has my
  xdoclet tags on it.
 
  2) Where should I store the generated .java files, as I don't want
  them in SCM, but I'm thiniking if their not under src\main\java then
  they won't get compiled.
 
 
  I'm using :-
 
  plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-1/version
executions
execution

  phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
!--
  Here is the code that would normally appear inside a
  target block in an ant script  : --
 
  ejbdoclet destdir=${project.build.outputDirectory}
 
  fileset dir=${basedir}/src/main/java includes=**/*Bean.java/
 
  entitycmp destDir=${project.build.outputDirectory}/
 
   session/
 
  remoteinterface pattern={0}Remote/
 
  homeinterface pattern={0}RemoteHome/
 
  localhomeinterface/
 
  deploymentdescriptor
  destDir=${project.build.outputDirectory}/META-INF/
 
  orion destdir=${build.dir}/ejb/META-INF /
/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin
 


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



error while make my first maven project

2005-10-23 Thread Rico (privat)

Hi all,

I've made my first maven project with Maven 2.0 and got following error 
while I've done described steps on getting started page with:


mvn archetype:create -DgroupId=com.cando.app -DartifactId=budget

[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.archetypes
ArtifactId: maven-archetype-quickstart
Version: RELEASE

Reason: Unable to determine the release version
 org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE:jar

Can anybody help with that error ?

Thanks in forward
Rico


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



RE: Re: [m2] Fatal error trying mvn site

2005-10-23 Thread Vincent Massol


 -Original Message-
 From: Brett Porter [mailto:[EMAIL PROTECTED]
 Sent: dimanche 23 octobre 2005 20:19
 To: Maven Users List
 Subject: Re: Re: [m2] Fatal error trying mvn site
 
 Interesting idea, but not very scalable (there are already a large
 number of plugins).
 
 I wonder if people prefer this to the create one project per plugin
 alternative? 

Personally I prefer having a JIRA project per release lifecycle. This is
always as JIRA has been intended to be used IMO.

 The biggest issue with that is being unable to search
 across multiple plugins at once - but it works much better now that
 the individual plugins are mostly mature.

With the latest version of JIRA you can search across different projects.

[snip]

-Vincent


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



Cannot get mvn site:site to work

2005-10-23 Thread Greg

Hello,

I am running Java 1.5 and Windows 2000 Pro.  I have just installed 
Maven2 and created a test web application by typing in the following:


  mvn archetype:create -DgroupId=com.mycompany.myapp.app 
-DartifactId=myapp-webapp -DarchetypeArtifactId=maven-archetype-webapp


This produced a fine-looking directory with all of the correct files.

I then cd'd into the myapp-webapp directory and typed the following

 mvn site:site

but I got no site directory or site files.  Can anyone give me a clue to 
fixing this ?  Do I first need to insert some commands into the POM.xml 
?  I  see the ERROR but what macro ?  A macro in the plugin or in Maven2 ?


I tried the same with a mvn site command and got the same thing.

TIA,
Greg

Here is what I got on the console when I ran the site:site command


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


[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [site:site]
[INFO] 

[INFO] Setting property: classpath.resource.loader.class = 
'org.codehaus.plexus.velo

er'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File: 
org\apache\velocity\runtime\defaults\velocity.propert
[INFO] Default ResourceManager initializing. (class 
org.apache.velocity.runtime.resou
[INFO] Resource Loader Instantiated: 
org.codehaus.plexus.velocity.ContextClassLoaderR

[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class 
org.apache.velocity.runtime.resource.Resou

[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: 
org.apache.velocity.runtime.directive.Literal

[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive: 
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive: 
org.apache.velocity.runtime.directive.Foreach

[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template : 
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' 
in any resou
[INFO] Velocimacro : error using  VM library template 
VM_global_library.vm : org.apac

undException: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in 
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline 
may NOT repla
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will 
be  global in

[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [site:site]
[INFO] Generate Continuous Integration report.
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
[INFO] Generate Dependencies report.
[INFO] Generate Issue Tracking report.
[INFO] Generate Project License report.
[INFO] Generate Mailing Lists report.
[INFO] Generate Source Repository report.
[INFO] Generate Project Team report.
[INFO] Generate an index file for the English version.
[INFO] 


[INFO] BUILD SUCCESSFUL
[INFO] 


[INFO] Total time: 5 seconds
[INFO] Finished at: Sun Oct 23 15:17:37 EDT 2005
[INFO] Final Memory: 6M/11M
[INFO] 



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



Re: error while make my first maven project

2005-10-23 Thread Brett Porter
Was there any additional information about why it failed to find the
latest version?

This might correct itself if you try again (perhaps using -U to force
an update check).

- Brett

On 10/23/05, Rico (privat) [EMAIL PROTECTED] wrote:
 Hi all,

 I've made my first maven project with Maven 2.0 and got following error
 while I've done described steps on getting started page with:

 mvn archetype:create -DgroupId=com.cando.app -DartifactId=budget

 [INFO] Failed to resolve artifact.

 GroupId: org.apache.maven.archetypes
 ArtifactId: maven-archetype-quickstart
 Version: RELEASE

 Reason: Unable to determine the release version
   org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE:jar

 Can anybody help with that error ?

 Thanks in forward
 Rico


 -
 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: Cannot get mvn site:site to work

2005-10-23 Thread Brett Porter
Everything here indicates that it successfully created the site in
target/site, and followng your commands works for me.

- Brett

On 10/23/05, Greg [EMAIL PROTECTED] wrote:
 Hello,

 I am running Java 1.5 and Windows 2000 Pro.  I have just installed
 Maven2 and created a test web application by typing in the following:

mvn archetype:create -DgroupId=com.mycompany.myapp.app
 -DartifactId=myapp-webapp -DarchetypeArtifactId=maven-archetype-webapp

 This produced a fine-looking directory with all of the correct files.

 I then cd'd into the myapp-webapp directory and typed the following

   mvn site:site

 but I got no site directory or site files.  Can anyone give me a clue to
 fixing this ?  Do I first need to insert some commands into the POM.xml
 ?  I  see the ERROR but what macro ?  A macro in the plugin or in Maven2 ?

 I tried the same with a mvn site command and got the same thing.

 TIA,
 Greg

 Here is what I got on the console when I ran the site:site command


 [INFO] Scanning for projects...
 [INFO] Searching repository for plugin with prefix: 'site'.
 [INFO]
 
 [INFO] Building Maven Webapp Archetype
 [INFO]task-segment: [site:site]
 [INFO]
 
 [INFO] Setting property: classpath.resource.loader.class =
 'org.codehaus.plexus.velo
 er'.
 [INFO] Setting property: velocimacro.messages.on = 'false'.
 [INFO] Setting property: resource.loader = 'classpath'.
 [INFO] Setting property: resource.manager.logwhenfound = 'false'.
 [INFO] **
 [INFO] Starting Jakarta Velocity v1.4
 [INFO] RuntimeInstance initializing.
 [INFO] Default Properties File:
 org\apache\velocity\runtime\defaults\velocity.propert
 [INFO] Default ResourceManager initializing. (class
 org.apache.velocity.runtime.resou
 [INFO] Resource Loader Instantiated:
 org.codehaus.plexus.velocity.ContextClassLoaderR
 [INFO] ClasspathResourceLoader : initialization starting.
 [INFO] ClasspathResourceLoader : initialization complete.
 [INFO] ResourceCache : initialized. (class
 org.apache.velocity.runtime.resource.Resou
 [INFO] Default ResourceManager initialization complete.
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Literal
 [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
 [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Include
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Foreach
 [INFO] Created: 20 parsers.
 [INFO] Velocimacro : initialization starting.
 [INFO] Velocimacro : adding VMs from VM library template :
 VM_global_library.vm
 [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
 in any resou
 [INFO] Velocimacro : error using  VM library template
 VM_global_library.vm : org.apac
 undException: Unable to find resource 'VM_global_library.vm'
 [INFO] Velocimacro :  VM library template macro registration complete.
 [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
 templates
 [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
 may NOT repla
 [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
 be  global in
 [INFO] Velocimacro : initialization complete.
 [INFO] Velocity successfully started.
 [INFO] [site:site]
 [INFO] Generate Continuous Integration report.
 [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
 [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
 [INFO] Generate Dependencies report.
 [INFO] Generate Issue Tracking report.
 [INFO] Generate Project License report.
 [INFO] Generate Mailing Lists report.
 [INFO] Generate Source Repository report.
 [INFO] Generate Project Team report.
 [INFO] Generate an index file for the English version.
 [INFO]
 
 [INFO] BUILD SUCCESSFUL
 [INFO]
 
 [INFO] Total time: 5 seconds
 [INFO] Finished at: Sun Oct 23 15:17:37 EDT 2005
 [INFO] Final Memory: 6M/11M
 [INFO]
 

 -
 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: Cannot get mvn site:site to work

2005-10-23 Thread Greg
DOP !!! -- Homerism  I was looking for it in the src/site directory - 
like it is here :


http://maven.apache.org/maven2/site.html

I also did a search for it on my hard drive looking for an index.apt 
file but I guess the documentation is a bit out of date or I misread it.


Thanks for the clue - I certainly feel like an idiot now.

Greg

Brett Porter wrote:

Everything here indicates that it successfully created the site in
target/site, and followng your commands works for me.

- Brett

On 10/23/05, Greg [EMAIL PROTECTED] wrote:


Hello,

I am running Java 1.5 and Windows 2000 Pro.  I have just installed
Maven2 and created a test web application by typing in the following:

  mvn archetype:create -DgroupId=com.mycompany.myapp.app
-DartifactId=myapp-webapp -DarchetypeArtifactId=maven-archetype-webapp

This produced a fine-looking directory with all of the correct files.

I then cd'd into the myapp-webapp directory and typed the following

 mvn site:site

but I got no site directory or site files.  Can anyone give me a clue to
fixing this ?  Do I first need to insert some commands into the POM.xml
?  I  see the ERROR but what macro ?  A macro in the plugin or in Maven2 ?

I tried the same with a mvn site command and got the same thing.

TIA,
Greg

Here is what I got on the console when I ran the site:site command


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

[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [site:site]
[INFO]

[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velo
er'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.propert
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resou
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderR
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.Resou
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
in any resou
[INFO] Velocimacro : error using  VM library template
VM_global_library.vm : org.apac
undException: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
may NOT repla
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
be  global in
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [site:site]
[INFO] Generate Continuous Integration report.
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
[INFO] Generate Dependencies report.
[INFO] Generate Issue Tracking report.
[INFO] Generate Project License report.
[INFO] Generate Mailing Lists report.
[INFO] Generate Source Repository report.
[INFO] Generate Project Team report.
[INFO] Generate an index file for the English version.
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 5 seconds
[INFO] Finished at: Sun Oct 23 15:17:37 EDT 2005
[INFO] Final Memory: 6M/11M
[INFO]


-
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 

maven2 and uberjar

2005-10-23 Thread Kevin Galligan
This might be a stupid question.  I'm new to maven in general.  I 
learned 1.1b2, then tried switching to v2.  I've built a simple jar 
project with a couple dependencies.  I'd like to make one big jar, or at 
least copy all dependencies to one directory.  Any easy way to do that?  
In v1 it looks like I could use uberjar.  Any m2 equivalent?


Thanks in advance,
-Kevin

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



Re: org.apache.maven.plugins:maven-compiler-plugin. Reason: Cannot resolve plugin dependencies

2005-10-23 Thread cheethus
Here is the version info of the IBM JDK...

java version 1.4.2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20041210 (JIT
enabled: jitc))

Thanks,
Kris.

Brett Porter wrote:

It's not a known issue. Is there a way we can obtain that specific
version to test it?

- Brett

On 10/21/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

No, I was able to fix it. It was the JDK type. I was using IBM JDK 1.4 and
maven 2(beta as well) doesn't seem to work with IBM JDK. After pointing to
the sun jdk, everything went fine. Just curious, Is this a known issue or I
need to do anything additional if I had to use IBM?

-Kris

Brett Porter wrote:

do you still get this with 2.0?

- Brett

On 10/18/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Nope. I use m2 beta 3. This is the error that i get when i run m2 -X
install. Also, as i said, it used to work for me without changing any proxy
settings.

[DEBUG] 
org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.0(selected
for runtime)
[DEBUG] commons-io:commons-io:jar:1.0 (selected for runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[DEBUG] com.mycompany.app:my-app:jar:1.0-SNAPSHOT (selected for null)
[DEBUG] org.apache.maven.plugins:maven-compiler-plugin:maven-plugin:2.0(selected
for runtime)
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Diagnosis: Error configuring:
org.apache.maven.plugins:maven-compiler-plugin. Reason: Cannot resolve
plugin dependencies
[INFO]

[DEBUG] Trace:

org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for
execution of 'compiler:compile'.
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:390)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:554)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:508)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:494)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:307)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:247)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Error
configuring: org.apache.maven.plugins:maven-compiler-plugin. Reason: Cannot
resolve plugin dependencies
at
org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete
(DefaultPluginManager.java:641)
at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(
DefaultPluginManager.java:532)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:385)
... 16 more
Caused by:
org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException:
Unable to read the metadata file
org.codehaus.plexus:plexus-compiler-api:1.5.1:jar

from the specified remote repositories:
snapshots (http://snapshots.maven.codehaus.org/maven2),
central (http://repo1.maven.org/maven2)
Path to dependency:
1) org.apache.maven.plugins:maven-compiler-plugin:maven-plugin:2.0


at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(
DefaultArtifactCollector.java:270)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(
DefaultArtifactCollector.java:69)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:225)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:213)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
(DefaultArtifactResolver.java:184)
at
org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete
(DefaultPluginManager.java:606)
... 18 more
Caused by:
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
Unable to 

Re: maven2 and uberjar

2005-10-23 Thread Brett Porter
The assembly plugin can do this (but doesn't do the auto-unpack on
execution that uberjar did, which was absurdly slow).

- Brett

On 10/23/05, Kevin Galligan [EMAIL PROTECTED] wrote:
 This might be a stupid question.  I'm new to maven in general.  I
 learned 1.1b2, then tried switching to v2.  I've built a simple jar
 project with a couple dependencies.  I'd like to make one big jar, or at
 least copy all dependencies to one directory.  Any easy way to do that?
 In v1 it looks like I could use uberjar.  Any m2 equivalent?

 Thanks in advance,
 -Kevin

 -
 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: Cannot get mvn site:site to work

2005-10-23 Thread Brett Porter
:)

The docs are right:

Generating the site is very simple, and fast!

m2 site:site

The resulting site will be in target/site/...

src/site is where you put the files you want to add to the site.

- Brett

On 10/23/05, Greg [EMAIL PROTECTED] wrote:
 DOP !!! -- Homerism  I was looking for it in the src/site directory -
 like it is here :

 http://maven.apache.org/maven2/site.html

 I also did a search for it on my hard drive looking for an index.apt
 file but I guess the documentation is a bit out of date or I misread it.

 Thanks for the clue - I certainly feel like an idiot now.

 Greg

 Brett Porter wrote:
  Everything here indicates that it successfully created the site in
  target/site, and followng your commands works for me.
 
  - Brett
 
  On 10/23/05, Greg [EMAIL PROTECTED] wrote:
 
 Hello,
 
 I am running Java 1.5 and Windows 2000 Pro.  I have just installed
 Maven2 and created a test web application by typing in the following:
 
mvn archetype:create -DgroupId=com.mycompany.myapp.app
 -DartifactId=myapp-webapp -DarchetypeArtifactId=maven-archetype-webapp
 
 This produced a fine-looking directory with all of the correct files.
 
 I then cd'd into the myapp-webapp directory and typed the following
 
   mvn site:site
 
 but I got no site directory or site files.  Can anyone give me a clue to
 fixing this ?  Do I first need to insert some commands into the POM.xml
 ?  I  see the ERROR but what macro ?  A macro in the plugin or in Maven2 ?
 
 I tried the same with a mvn site command and got the same thing.
 
 TIA,
 Greg
 
 Here is what I got on the console when I ran the site:site command
 
 
 [INFO] Scanning for projects...
 [INFO] Searching repository for plugin with prefix: 'site'.
 [INFO]
 
 [INFO] Building Maven Webapp Archetype
 [INFO]task-segment: [site:site]
 [INFO]
 
 [INFO] Setting property: classpath.resource.loader.class =
 'org.codehaus.plexus.velo
 er'.
 [INFO] Setting property: velocimacro.messages.on = 'false'.
 [INFO] Setting property: resource.loader = 'classpath'.
 [INFO] Setting property: resource.manager.logwhenfound = 'false'.
 [INFO] **
 [INFO] Starting Jakarta Velocity v1.4
 [INFO] RuntimeInstance initializing.
 [INFO] Default Properties File:
 org\apache\velocity\runtime\defaults\velocity.propert
 [INFO] Default ResourceManager initializing. (class
 org.apache.velocity.runtime.resou
 [INFO] Resource Loader Instantiated:
 org.codehaus.plexus.velocity.ContextClassLoaderR
 [INFO] ClasspathResourceLoader : initialization starting.
 [INFO] ClasspathResourceLoader : initialization complete.
 [INFO] ResourceCache : initialized. (class
 org.apache.velocity.runtime.resource.Resou
 [INFO] Default ResourceManager initialization complete.
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Literal
 [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
 [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Include
 [INFO] Loaded System Directive:
 org.apache.velocity.runtime.directive.Foreach
 [INFO] Created: 20 parsers.
 [INFO] Velocimacro : initialization starting.
 [INFO] Velocimacro : adding VMs from VM library template :
 VM_global_library.vm
 [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
 in any resou
 [INFO] Velocimacro : error using  VM library template
 VM_global_library.vm : org.apac
 undException: Unable to find resource 'VM_global_library.vm'
 [INFO] Velocimacro :  VM library template macro registration complete.
 [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
 templates
 [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
 may NOT repla
 [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
 be  global in
 [INFO] Velocimacro : initialization complete.
 [INFO] Velocity successfully started.
 [INFO] [site:site]
 [INFO] Generate Continuous Integration report.
 [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
 [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
 [INFO] Generate Dependencies report.
 [INFO] Generate Issue Tracking report.
 [INFO] Generate Project License report.
 [INFO] Generate Mailing Lists report.
 [INFO] Generate Source Repository report.
 [INFO] Generate Project Team report.
 [INFO] Generate an index file for the English version.
 [INFO]
 
 [INFO] BUILD SUCCESSFUL
 [INFO]
 
 [INFO] Total time: 5 seconds
 [INFO] Finished at: Sun Oct 23 15:17:37 EDT 2005
 [INFO] Final Memory: 6M/11M
 [INFO]
 

RE: M2 with oc4j

2005-10-23 Thread Vincent Massol
Hi Pete,

 -Original Message-
 From: Pete [mailto:[EMAIL PROTECTED]
 Sent: dimanche 23 octobre 2005 13:47
 To: Maven Users List
 Subject: M2 with oc4j
 
 Has anyone out there got any suggestions of how to integrate a M2
 build with Oracle's oc4j J2EE container.
 
 I'm looking to be able to start the oc4j container, deploy, run
 incontainer JUnitEE tests etc, from M2.

You should definitely have a look at cargo. You don't need a m2 plugin to
use it for testing.

Have a look at http://tinyurl.com/a6325 (don't pay too much attention to the
syntax has it has slightly changed in recent cargo versions) but the
strategy remains the same.

Basically you can start/stop/deploy to your container from within your junit
tests.

-Vincent


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



Re: generate dependancies

2005-10-23 Thread Brill Pappin
Jason van Zyl wrote:

On Tue, 2005-10-11 at 14:49 -0400, Brian E. Fox wrote:
  

Kindof. We are moving from ANT and have a lib folder with 100+ jars. I'd
like to visually see which ones we directly depend on and then have a
tree that shows what those depend on. I experimented with Jdepend, but
it didn't really do what I expect. A lot of dependencies where
suspiciously missing.



In your scenerio do you know for sure what versions of the JARs you
have? We might want to make a tool that uses the technique of taking the
md5 checksum of the JAR and looking up the version first and once we
have all the versions we could probably create some graphs and do some
transitivity determination.
  

Or use the manifest... not all are packaged with version information,
but if the m2 jar doesn't, it should.

- Brill Pappin


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



submitting patches in JIRA

2005-10-23 Thread Jason van Zyl
Howdy,

For anyone supplying patches here's a little blurb that will make it
easier for us to process patches:

http://blogs.codehaus.org/projects/maven/archives/001200_how_to_deal_with_submitted_patches_effectively_using_jira.html

Most people already put patch somewhere in the text, but now there is
a filter to help us.

-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

you are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of 
dogmas or goals, it's always because these dogmas or
goals are in doubt.

  -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance


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



RE: Where should configuration files go?

2005-10-23 Thread Jason van Zyl
On Sat, 2005-10-22 at 14:05 +0200, Vincent Massol wrote:
 Hi Robert,
 
  -Original Message-
  From: Robert Taylor [mailto:[EMAIL PROTECTED]
  Sent: samedi 22 octobre 2005 14:03
  To: users@maven.apache.org
  Subject: Where should configuration files go?
  
  Greetings,
  
  I'm a recent Ant-to-Maven 2.0 convert and am trying to mavenize some
  existing greenfield projects.
  
  In the past I have usually kept my Hibernate *.hbm.xml files in the same
  directory as their corresponding .java files because it facilitates
  referencing. Should I still keep them there, or move them to the
  /resources directory? Personally, I'ld like to keep them close to their
  corresponding .java file.
 
 You should move them in the resources directory but you can keep the same
 package. The notion of close is subjective. They can be in a different
 directory and still be close in your IDE view for example.
  
  For testing, should I place files like log4j.properties,
  *-applicationContext.xml (Spring) files, and other configuration type
  files under the /test/resources directory?

We might want to align our notions:

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

Are we going to make a distinction between resources like i18n files and
things like log4j.properties files or things like app server
configurations?

Just throwing this out for comment and clarification before we start
recommending things wholesale to users.

 Exactly. Note that those files will need to be accessed using the classpath
 as described on
 http://maven.apache.org/guides/getting-started/index.html#How%20do%20add%20r
 esources%20to%20my%20JAR?
 
 -Vincent
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



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



Re: [M2] Docbook support

2005-10-23 Thread Jason van Zyl
On Fri, 2005-10-21 at 13:27 +0200, Jose Gonzalez Gomez wrote:

 Thanks a lot, I'll try to take a look at it as soon as possible.
 Anyway, I've been taking a look at the head revision of
 org.codehaus.doxia.module.docbook.DocBookParser.java, and I doubt that
 this parser is going to generate anything close to useful. I had the
 feeling that this class was copied from some other parser (maybe the
 xdoc parser, as indicated in the header comment): most of the tags
 used there are not part of the Docbook format, and there are some
 commonly used tags missing.

It's simplified docbook and is definitely geared toward site
documentation, but decent PDFs can be produced.

If you have existing tools that work with full docbook I would say stick
with them. What's in Doxia is simplified docbook support.

-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

  -- Ralph Johnson  Don Roberts, Patterns for Evolving Frameworks 


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



[M2]How to change the m2's defalut webapp dir to my own webroot dir?

2005-10-23 Thread Hong Xing
Hi all,

In my previous projects, I have the following project layout:

my-webapp
|-- pom.xml
|-- WebRoot
|   |-- index.jsp
|   `-- WEB-INF
|   `-- classes
|   `-- lib
`-- src

When I used mvn package to package my war, it can't find my WebRoot and 
failed.
So how can I change the m2's defalut webapp dir to my own webroot dir in 
pom.xml?


Re: [M2]How to change the m2's defalut webapp dir to my own webroot dir?

2005-10-23 Thread Brett Porter
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html

warSourceDirectory is the configuration element to set to WebRoot.

On 10/23/05, Hong Xing [EMAIL PROTECTED] wrote:
 Hi all,

 In my previous projects, I have the following project layout:

 my-webapp
 |-- pom.xml
 |-- WebRoot
 |   |-- index.jsp
 |   `-- WEB-INF
 |   `-- classes
 |   `-- lib
 `-- src

 When I used mvn package to package my war, it can't find my WebRoot and 
 failed.
 So how can I change the m2's defalut webapp dir to my own webroot dir in 
 pom.xml?


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