[m2] Migrating mockobject calls to Maven2

[Dennis Ho]

Hi,

I am in the process of migrating some existing maven tasks to
use maven 2.  We use mockobjects in our code for testing purposes, and I
would like to know if anyone has experience using maven2 with
mockobjects can give me some pointer as to how the pom should look like.

When we did it with maven 1.x we have to use ant like the
following:



  
  
  
  
  
  

  


Is there a more natural way to do it in Maven 2?   I can't find anything
from the web so any advice is welcome.  

Thanks in advance for your help!

Regards,

Dennis Ho.

Re: Any easy way to list all goals available for a plugin?

[Allan Ramirez]

I believe that the TODO output is already fixed.
Please see http://jira.codehaus.org/browse/MPH-2

-allan

Treloar, Barrie (SAPOL) wrote:


They might have meant "projecthelp:describe".
See http://maven.apache.org/plugins/maven-projecthelp-plugin/

However when I run it there are lots of "TODO" output and nothing of
interest.

Also the documentation at the above link is sparse.

-Original Message-
From: Man-Chi Leung [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 28 December 2005 2:43 PM

To: Maven Users List
Subject: Re: Any easy way to list all goals available for a plugin?

hi allan,

thanks for your advice. but may I know where I can download maven- 
help-plugin ?
neither I can find in  http://svn.mojo.codehaus.org/trunk/mojo/  NOR  
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/


[ERROR] BUILD ERROR
[INFO]  
 

The plugin 'org.apache.maven.plugins:maven-help-plugin' does not  
exist or no valid version could be found
[INFO]  
 




On Dec 28, 2005, at 11:42 AM, Allan Ramirez wrote:

 


Hi Manchi,

Or you can use the maven-help-plugin, it can list all the goals for  
a certain plugin.


i.e.
mvn help:describe -Dplugin=org.apache.maven.plugins:maven-eclipse- 
plugin -Dfull=true


-allan

Yann Le Du wrote:

   


Hi Manchi

If you want the site to contain plugin goal documentation, you  
must include

the plugin report :


  

  org.apache.maven.plugins
  maven-plugin-plugin

  


Hope this helps,
--
Yann

2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:

 


hi,

after anyway new plug-in installation, I will very much rely on "mvn
site" to generate a html site for checking out all Goals available.

sometimes, there is nothing.  very often, I need to dig all the way
to view a plug-in's source code.

yes, look at the @goal  annotation stated for the mojo class.

I am wondering whether there is a better way to list all available
goals in M2.

in Maven1, we have $maven -P  or  $maven -g

how about M2? pls advise.

Best Regards,

Manchi Leung


   

- 
---


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


 


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




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

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


 



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

Re: anyone is running surefire-report-plugin 2.1 on m2?

[Brett Porter]

You have this back to front.

When you run tests, that runs the maven-surefire-plugin (v2.1.1). This
uses the surefire library v1.5.1. This is the latest release:
http://svn.apache.org/viewcvs.cgi/maven/surefire/tags/

It is only 2 weeks old, and there has only been one fix since that
release (MSUREFIRE-20).

If you still have a problem with this release, please file it in JIRA,
but check that it is not first recorded there.

- Brett

On 12/28/05, Man-Chi Leung <[EMAIL PROTECTED]> wrote:
> hi Brett,
>
> thanks for your advice. but it seems that the current release ver of
> Surefire is pretty old (1.5) which is causing a xml validation
> problem on surefire-report.
>
> [INFO] Generate "Maven Surefire Report" report.java.lang.Exception:
> Failure to parse file at: ~/myproject/my-app/target/surefire-reports/
> TEST-com.mycompany.app.AppTest.xml at
> org.codehaus.mojo.surefire.ReportTestSuite.
>
> to my understanding, Maven 2.0.1 is preconfigured with surefire-booter
> (1.5),  which calls surefire plugin(1.5)
>
> so I go ahead to get surefire ver 2.1.1 from 'svn checkout http://
> svn.apache.org/repos/asf/maven/components/tags/maven-surefire-
> plugin-2.1 maven-surefire-plugin-2.1'
>
> after 'mvn install' (2.1)
>
> how can I config surefire booter(1.5) to run surefire plugin(2.1) then?
>
> pls advice
>
> ~manchi
>
>
> On Dec 28, 2005, at 11:12 AM, Brett Porter wrote:
>
> > This is just a little bit of confusion.
> >
> > The Maven surefire plugin (version 2.1) uses version 1.5 of surefire
> > and surefire-booter. So it all sounds correct.
> >
> > Users should only ever need to use -U to update plugins, not build
> > anything from source. Likewise, -DupdateReleaseInfo is completely
> > unnecessary for plugins in 2.0+ of Maven.
> >
> > - Brett
> >
> > On 12/28/05, Nik Gonzalez <[EMAIL PROTECTED]> wrote:
> >> Man-Chi Leung,
> >>
> >> Build the maven-surefire-plugin-2.1 that you checked out again but
> >> this
> >> time using "mvn install -DupdateReleaseInfo=true.  This will
> >> update your
> >> plugin registry and the next time you call on this plugin, maven will
> >> use the updated version.
> >>
> >> hth,
> >>
> >> Nik
> >>
> >> Man-Chi Leung wrote:
> >>
> >>> hi,
> >>>
> >>> surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5
> >>> xml file
> >>>
> >>> I used surefire-report plugin to parse surefire generated xml file
> >>> but encountered the following exception.
> >>> I checked out surefire-report jira, and got a reply that it is
> >>> due to
> >>> the invalid xml format in surefire generated TEST-
> >>> com.mycompany.app.AppTest.xml file.
> >>>
> >>> 
> >>> I tried the following attempt:
> >>> -
> >>> since surefire-plugin that bundles with m2 release is version
> >>> 1.5, in
> >>> fact, I tried to checkout the latest 2.1 from
> >>> http://svn.apache.org/repos/asf/maven/components/tags/maven-
> >>> surefire-
> >>> plugin-2.1. I did a mvn compile and install to my local .m2
> >>> repository, trying to run it again.
> >>> However, M2 , by default only depends surefire 1.5 version, NOT
> >>> running ver 2.1 . may I know how to make m2 to run surefire 2.1
> >>> instead? pls help
> >>> btw, the surefire report 2.1 DOES generate correct, just that there
> >>> are a lot of exception as the followings!
> >>>
> >>> ---
> >>> ERROR MSG:
> >>> ---
> >>> [INFO] Generate "Maven Surefire Report" report.
> >>> java.lang.Exception: Failure to parse file at: ~/myproject/my-app/
> >>> target/surefire-reports/TEST-com.mycompany.app.AppTest.xml
> >>> at org.codehaus.mojo.surefire.ReportTestSuite.
> >>> (ReportTestSuite.java:68)
> >>> at
> >>> org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles
> >>> (SurefireReportParser.java:49)
> >>> at
> >>> org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport
> >>> (SurefireReportGenerator.java:44)
> >>> at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport
> >>> (SurefireReportMojo.java:77)
> >>> at org.apache.maven.reporting.AbstractMavenReport.generate
> >>> (AbstractMavenReport.java:98)
> >>> at org.apache.maven.plugins.site.SiteMojo.generateReportsPages
> >>> (SiteMojo.java:802)
> >>> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> >>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> >>> (DefaultPluginManager.java:432)
> >>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> >>> (DefaultLifecycleExecutor.java:530)
> >>> at
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
> >>> ifec
> >>> ycle(DefaultLifecycleExecutor.java:472)
> >>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> >>> (DefaultLifecycleExecutor.java:451)
> >>> at
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
> >>> ndle
> >>> Failures(DefaultLifecycleExecutor.java:303)
> >>> at
> >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.e

Re: Any easy way to list all goals available for a plugin?

[Allan Ramirez]

Hi Man-chi,

Sorry for that, I thought it was already released in ibiblio.

Use maven-projecthelp-plugin instead. It was the original name of the 
maven-help-plugin so it should do the same. :)


mvn projecthelp:describe 
-Dplugin=org.apache.maven.plugins:maven-eclipse-plugin -Dfull=true


Regards,
-allan

Man-Chi Leung wrote:


hi allan,

thanks for your advice. but may I know where I can download maven- 
help-plugin ?
neither I can find in  http://svn.mojo.codehaus.org/trunk/mojo/  NOR  
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/


[ERROR] BUILD ERROR
[INFO]  
 

The plugin 'org.apache.maven.plugins:maven-help-plugin' does not  
exist or no valid version could be found
[INFO]  
 




On Dec 28, 2005, at 11:42 AM, Allan Ramirez wrote:


Hi Manchi,

Or you can use the maven-help-plugin, it can list all the goals for  
a certain plugin.


i.e.
mvn help:describe -Dplugin=org.apache.maven.plugins:maven-eclipse- 
plugin -Dfull=true


-allan

Yann Le Du wrote:


Hi Manchi

If you want the site to contain plugin goal documentation, you  must 
include

the plugin report :

 
   
 
   org.apache.maven.plugins
   maven-plugin-plugin
 
   
 

Hope this helps,
--
Yann

2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:


hi,

after anyway new plug-in installation, I will very much rely on "mvn
site" to generate a html site for checking out all Goals available.

sometimes, there is nothing.  very often, I need to dig all the way
to view a plug-in's source code.

yes, look at the @goal  annotation stated for the mojo class.

I am wondering whether there is a better way to list all available
goals in M2.

in Maven1, we have $maven -P  or  $maven -g

how about M2? pls advise.

Best Regards,

Manchi Leung





- 
---


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




-
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: anyone is running surefire-report-plugin 2.1 on m2?

[Man-Chi Leung]

hi Brett,

thanks for your advice. but it seems that the current release ver of  
Surefire is pretty old (1.5) which is causing a xml validation  
problem on surefire-report.


[INFO] Generate "Maven Surefire Report" report.java.lang.Exception:  
Failure to parse file at: ~/myproject/my-app/target/surefire-reports/ 
TEST-com.mycompany.app.AppTest.xml at  
org.codehaus.mojo.surefire.ReportTestSuite.


to my understanding, Maven 2.0.1 is preconfigured with surefire-booter 
(1.5),  which calls surefire plugin(1.5)


so I go ahead to get surefire ver 2.1.1 from 'svn checkout http:// 
svn.apache.org/repos/asf/maven/components/tags/maven-surefire- 
plugin-2.1 maven-surefire-plugin-2.1'


after 'mvn install' (2.1)

how can I config surefire booter(1.5) to run surefire plugin(2.1) then?

pls advice

~manchi


On Dec 28, 2005, at 11:12 AM, Brett Porter wrote:


This is just a little bit of confusion.

The Maven surefire plugin (version 2.1) uses version 1.5 of surefire
and surefire-booter. So it all sounds correct.

Users should only ever need to use -U to update plugins, not build
anything from source. Likewise, -DupdateReleaseInfo is completely
unnecessary for plugins in 2.0+ of Maven.

- Brett

On 12/28/05, Nik Gonzalez <[EMAIL PROTECTED]> wrote:

Man-Chi Leung,

Build the maven-surefire-plugin-2.1 that you checked out again but  
this
time using "mvn install -DupdateReleaseInfo=true.  This will  
update your

plugin registry and the next time you call on this plugin, maven will
use the updated version.

hth,

Nik

Man-Chi Leung wrote:


hi,

surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5
xml file

I used surefire-report plugin to parse surefire generated xml file
but encountered the following exception.
I checked out surefire-report jira, and got a reply that it is  
due to

the invalid xml format in surefire generated TEST-
com.mycompany.app.AppTest.xml file.


I tried the following attempt:
-
since surefire-plugin that bundles with m2 release is version  
1.5, in

fact, I tried to checkout the latest 2.1 from
http://svn.apache.org/repos/asf/maven/components/tags/maven- 
surefire-

plugin-2.1. I did a mvn compile and install to my local .m2
repository, trying to run it again.
However, M2 , by default only depends surefire 1.5 version, NOT
running ver 2.1 . may I know how to make m2 to run surefire 2.1
instead? pls help
btw, the surefire report 2.1 DOES generate correct, just that there
are a lot of exception as the followings!

---
ERROR MSG:
---
[INFO] Generate "Maven Surefire Report" report.
java.lang.Exception: Failure to parse file at: ~/myproject/my-app/
target/surefire-reports/TEST-com.mycompany.app.AppTest.xml
at org.codehaus.mojo.surefire.ReportTestSuite.
(ReportTestSuite.java:68)
at  
org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles

(SurefireReportParser.java:49)
at  
org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport

(SurefireReportGenerator.java:44)
at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport
(SurefireReportMojo.java:77)
at org.apache.maven.reporting.AbstractMavenReport.generate
(AbstractMavenReport.java:98)
at org.apache.maven.plugins.site.SiteMojo.generateReportsPages
(SiteMojo.java:802)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:432)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:530)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL 
ifec

ycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa 
ndle

Failures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme 
nts(

DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java: 
315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode 
(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.xml.sax.SAXParseException: Whitespace required before
attributes.
at org.apac

RE: Any easy way to list all goals available for a plugin?

[Treloar, Barrie (SAPOL)]

They might have meant "projecthelp:describe".
See http://maven.apache.org/plugins/maven-projecthelp-plugin/

However when I run it there are lots of "TODO" output and nothing of
interest.

Also the documentation at the above link is sparse.

-Original Message-
From: Man-Chi Leung [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 28 December 2005 2:43 PM
To: Maven Users List
Subject: Re: Any easy way to list all goals available for a plugin?

hi allan,

thanks for your advice. but may I know where I can download maven- 
help-plugin ?
neither I can find in  http://svn.mojo.codehaus.org/trunk/mojo/  NOR  
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/

[ERROR] BUILD ERROR
[INFO]  
 

The plugin 'org.apache.maven.plugins:maven-help-plugin' does not  
exist or no valid version could be found
[INFO]  
 



On Dec 28, 2005, at 11:42 AM, Allan Ramirez wrote:

> Hi Manchi,
>
> Or you can use the maven-help-plugin, it can list all the goals for  
> a certain plugin.
>
> i.e.
> mvn help:describe -Dplugin=org.apache.maven.plugins:maven-eclipse- 
> plugin -Dfull=true
>
> -allan
>
> Yann Le Du wrote:
>
>> Hi Manchi
>>
>> If you want the site to contain plugin goal documentation, you  
>> must include
>> the plugin report :
>>
>>  
>>
>>  
>>org.apache.maven.plugins
>>maven-plugin-plugin
>>  
>>
>>  
>>
>> Hope this helps,
>> --
>> Yann
>>
>> 2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:
>>
>>> hi,
>>>
>>> after anyway new plug-in installation, I will very much rely on "mvn
>>> site" to generate a html site for checking out all Goals available.
>>>
>>> sometimes, there is nothing.  very often, I need to dig all the way
>>> to view a plug-in's source code.
>>>
>>> yes, look at the @goal  annotation stated for the mojo class.
>>>
>>> I am wondering whether there is a better way to list all available
>>> goals in M2.
>>>
>>> in Maven1, we have $maven -P  or  $maven -g
>>>
>>> how about M2? pls advise.
>>>
>>> Best Regards,
>>>
>>> Manchi Leung
>>>
>>>
>>
>>
>> - 
>> ---
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.1.371 / Virus Database: 267.14.8/215 - Release Date:  
>> 12/27/2005
>>
>
> -
> 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: Any easy way to list all goals available for a plugin?

[Man-Chi Leung]

hi allan,

thanks for your advice. but may I know where I can download maven- 
help-plugin ?
neither I can find in  http://svn.mojo.codehaus.org/trunk/mojo/  NOR  
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/


[ERROR] BUILD ERROR
[INFO]  
 

The plugin 'org.apache.maven.plugins:maven-help-plugin' does not  
exist or no valid version could be found
[INFO]  
 




On Dec 28, 2005, at 11:42 AM, Allan Ramirez wrote:


Hi Manchi,

Or you can use the maven-help-plugin, it can list all the goals for  
a certain plugin.


i.e.
mvn help:describe -Dplugin=org.apache.maven.plugins:maven-eclipse- 
plugin -Dfull=true


-allan

Yann Le Du wrote:


Hi Manchi

If you want the site to contain plugin goal documentation, you  
must include

the plugin report :

 
   
 
   org.apache.maven.plugins
   maven-plugin-plugin
 
   
 

Hope this helps,
--
Yann

2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:


hi,

after anyway new plug-in installation, I will very much rely on "mvn
site" to generate a html site for checking out all Goals available.

sometimes, there is nothing.  very often, I need to dig all the way
to view a plug-in's source code.

yes, look at the @goal  annotation stated for the mojo class.

I am wondering whether there is a better way to list all available
goals in M2.

in Maven1, we have $maven -P  or  $maven -g

how about M2? pls advise.

Best Regards,

Manchi Leung





- 
---


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




-
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: reverse dependency management

[Brett Porter]

This is actually a feature in the repository manager we've been discussing
on the dev list. It's not ready yet, but its an app on the repository that
you could use to browse such a relationship. A Maven plugin could query
that.

- Brett

On 12/24/05, David Sag <[EMAIL PROTECTED]> wrote:
>
>
> We have many interdependent projects here.  When someone releases a
> project upon which many other projects depend we need some way of knowing
> automatically which projects will also need to be retested.
>
> is there a m2 plugin that manages reverse dependency lookups?  For
> simplicity I am really mostly concerned with changes to our internal
> projects here.
>
> Kind regards,
> Dave Sag
>
>
>
>
>

Re: Any easy way to list all goals available for a plugin?

[Allan Ramirez]

Hi Manchi,

Or you can use the maven-help-plugin, it can list all the goals for a 
certain plugin.


i.e.
mvn help:describe -Dplugin=org.apache.maven.plugins:maven-eclipse-plugin 
-Dfull=true


-allan

Yann Le Du wrote:


Hi Manchi

If you want the site to contain plugin goal documentation, you must include
the plugin report :

 
   
 
   org.apache.maven.plugins
   maven-plugin-plugin
 
   
 

Hope this helps,
--
Yann

2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:
 


hi,

after anyway new plug-in installation, I will very much rely on "mvn
site" to generate a html site for checking out all Goals available.

sometimes, there is nothing.  very often, I need to dig all the way
to view a plug-in's source code.

yes, look at the @goal  annotation stated for the mojo class.

I am wondering whether there is a better way to list all available
goals in M2.

in Maven1, we have $maven -P  or  $maven -g

how about M2? pls advise.

Best Regards,

Manchi Leung

   



 




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



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

Re: anyone is running surefire-report-plugin 2.1 on m2?

[Brett Porter]

This is just a little bit of confusion.

The Maven surefire plugin (version 2.1) uses version 1.5 of surefire
and surefire-booter. So it all sounds correct.

Users should only ever need to use -U to update plugins, not build
anything from source. Likewise, -DupdateReleaseInfo is completely
unnecessary for plugins in 2.0+ of Maven.

- Brett

On 12/28/05, Nik Gonzalez <[EMAIL PROTECTED]> wrote:
> Man-Chi Leung,
>
> Build the maven-surefire-plugin-2.1 that you checked out again but this
> time using "mvn install -DupdateReleaseInfo=true.  This will update your
> plugin registry and the next time you call on this plugin, maven will
> use the updated version.
>
> hth,
>
> Nik
>
> Man-Chi Leung wrote:
>
> > hi,
> >
> > surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5
> > xml file
> >
> > I used surefire-report plugin to parse surefire generated xml file
> > but encountered the following exception.
> > I checked out surefire-report jira, and got a reply that it is due to
> > the invalid xml format in surefire generated TEST-
> > com.mycompany.app.AppTest.xml file.
> >
> > 
> > I tried the following attempt:
> > -
> > since surefire-plugin that bundles with m2 release is version 1.5, in
> > fact, I tried to checkout the latest 2.1 from
> > http://svn.apache.org/repos/asf/maven/components/tags/maven-surefire-
> > plugin-2.1. I did a mvn compile and install to my local .m2
> > repository, trying to run it again.
> > However, M2 , by default only depends surefire 1.5 version, NOT
> > running ver 2.1 . may I know how to make m2 to run surefire 2.1
> > instead? pls help
> > btw, the surefire report 2.1 DOES generate correct, just that there
> > are a lot of exception as the followings!
> >
> > ---
> > ERROR MSG:
> > ---
> > [INFO] Generate "Maven Surefire Report" report.
> > java.lang.Exception: Failure to parse file at: ~/myproject/my-app/
> > target/surefire-reports/TEST-com.mycompany.app.AppTest.xml
> > at org.codehaus.mojo.surefire.ReportTestSuite.
> > (ReportTestSuite.java:68)
> > at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles
> > (SurefireReportParser.java:49)
> > at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport
> > (SurefireReportGenerator.java:44)
> > at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport
> > (SurefireReportMojo.java:77)
> > at org.apache.maven.reporting.AbstractMavenReport.generate
> > (AbstractMavenReport.java:98)
> > at org.apache.maven.plugins.site.SiteMojo.generateReportsPages
> > (SiteMojo.java:802)
> > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> > at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> > (DefaultPluginManager.java:432)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> > (DefaultLifecycleExecutor.java:530)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> > ycle(DefaultLifecycleExecutor.java:472)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> > (DefaultLifecycleExecutor.java:451)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> > Failures(DefaultLifecycleExecutor.java:303)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> > DefaultLifecycleExecutor.java:270)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> > (DefaultLifecycleExecutor.java:139)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke
> > (NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke
> > (DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > Caused by: org.xml.sax.SAXParseException: Whitespace required before
> > attributes.
> > at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376)
> > at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3364)
> > at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1556)
> > at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
> > at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
> > at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
> > at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
> > at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
> > at org.apache.crimson.parser.

Re: anyone is running surefire-report-plugin 2.1 on m2?

[Nik Gonzalez]

Man-Chi Leung,

Build the maven-surefire-plugin-2.1 that you checked out again but this 
time using "mvn install -DupdateReleaseInfo=true.  This will update your 
plugin registry and the next time you call on this plugin, maven will 
use the updated version.


hth,

Nik

Man-Chi Leung wrote:


hi,

surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5  
xml file


I used surefire-report plugin to parse surefire generated xml file  
but encountered the following exception.
I checked out surefire-report jira, and got a reply that it is due to  
the invalid xml format in surefire generated TEST-

com.mycompany.app.AppTest.xml file.


I tried the following attempt:
-
since surefire-plugin that bundles with m2 release is version 1.5, in  
fact, I tried to checkout the latest 2.1 from
http://svn.apache.org/repos/asf/maven/components/tags/maven-surefire- 
plugin-2.1. I did a mvn compile and install to my local .m2  
repository, trying to run it again.
However, M2 , by default only depends surefire 1.5 version, NOT  
running ver 2.1 . may I know how to make m2 to run surefire 2.1  
instead? pls help
btw, the surefire report 2.1 DOES generate correct, just that there  
are a lot of exception as the followings!


---
ERROR MSG:
---
[INFO] Generate "Maven Surefire Report" report.
java.lang.Exception: Failure to parse file at: ~/myproject/my-app/ 
target/surefire-reports/TEST-com.mycompany.app.AppTest.xml
at org.codehaus.mojo.surefire.ReportTestSuite. 
(ReportTestSuite.java:68)
at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles 
(SurefireReportParser.java:49)
at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport 
(SurefireReportGenerator.java:44)
at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport 
(SurefireReportMojo.java:77)
at org.apache.maven.reporting.AbstractMavenReport.generate 
(AbstractMavenReport.java:98)
at org.apache.maven.plugins.site.SiteMojo.generateReportsPages 
(SiteMojo.java:802)

at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPluginManager.java:432)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(DefaultLifecycleExecutor.java:530)
at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec 
ycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(DefaultLifecycleExecutor.java:451)
at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle 
Failures(DefaultLifecycleExecutor.java:303)
at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( 
DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
(DefaultLifecycleExecutor.java:139)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.xml.sax.SAXParseException: Whitespace required before  
attributes.

at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376)
at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3364)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1556)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:281)
at org.codehaus.mojo.surefire.ReportTestSuite. 
(ReportTestSuite.java:64)

... 24 more

-
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] maven-eclipse-plugin and wtp 1.0

[Rinku]

Hi,

I have submitted a patch for maven-eclipse-plugin to work with WTP 1.0.
http://jira.codehaus.org/browse/MECLIPSE-47

Regards bug related to external dependencies:
As a workaround the project dependencies are copied to under 
/WEB-INF/lib, such that these get published for 
respective containers.


Appreciate any review comments/suggestions.

Cheers,

Rahul


- Original Message - 
From: "Alexandre Poitras" <[EMAIL PROTECTED]>

To: "Maven Users List" 
Sent: Wednesday, December 28, 2005 11:15 AM
Subject: Re: [m2] maven-eclipse-plugin and wtp 1.0


Anyway wtp 1.0 is buggy, external libraries don't work anymore so you have 
to

stay with r7 till the bug is resolved.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 for details,
the issue is scheduled for 1.0.1. Please add a vote to the issue in
bugzilla to raise the priority for eclipse developers!

On 12/27/05, Rinku <[EMAIL PROTECTED]> wrote:

Yes, there will be changes to m2 eclipse plugin for wtp1.0.

I am in process of adding support for wtp 1.0 and testing, and submit a
patch on JIRA shortly.
http://jira.codehaus.org/browse/MECLIPSE-47?page=all

Cheers,
Rahul


- Original Message -
From: "Srepfler Srgjan" <[EMAIL PROTECTED]>
To: "Maven Users List" 
Sent: Wednesday, December 28, 2005 12:03 AM
Subject: [m2] maven-eclipse-plugin and wtp 1.0


> Will there be any changes to the maven-eclipse-plugin to integrate with
> the WTP 1.0 way of managing j2ee projects?
>
> Cheers
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


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





--
Alexandre Poitras
Québec, Canada

-
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: Any easy way to list all goals available for a plugin?

[Yann Le Du]

Hi Manchi

If you want the site to contain plugin goal documentation, you must include
the plugin report :

  

  
org.apache.maven.plugins
maven-plugin-plugin
  

  

Hope this helps,
--
Yann

2005/12/27, Man-Chi Leung <[EMAIL PROTECTED]>:
>
> hi,
>
> after anyway new plug-in installation, I will very much rely on "mvn
> site" to generate a html site for checking out all Goals available.
>
> sometimes, there is nothing.  very often, I need to dig all the way
> to view a plug-in's source code.
>
> yes, look at the @goal  annotation stated for the mojo class.
>
> I am wondering whether there is a better way to list all available
> goals in M2.
>
> in Maven1, we have $maven -P  or  $maven -g
>
> how about M2? pls advise.
>
> Best Regards,
>
> Manchi Leung
>

RE: Plugin Question: Loading resources from dependency JARs

[Brian E. Fox]

There is code in the dependency-maven-plugin (http://mojo.codehaus.org)
that can allow you to either pull the artifacts from the project
dependencies, or to specify them in the plugin configuration. You could
use that code and it would get you a file handle to the jar. Presumably
you could then load the xml from the jar that way. Alternatively, you
could use the plugin in your project to unpack the jars and get your xml
files that way.

Or, if the dependencies are listed in the pom, they should be on the
classpath when the plugin runs. You could use the classloader to load
your xml files that way. I recently found an issue with the plugin
classpath that may affect you if you try this method:
http://jira.codehaus.org/browse/MNG-1898?rc=1
 

-Original Message-
From: Lewis, Allan E. (Number Six) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 27, 2005 2:28 PM
To: users@maven.apache.org
Subject: Plugin Question: Loading resources from dependency JARs

I have a code generation MOJO that currently reads all XML files from
the resources folder of the current project and generates code based on
each file.  The XML for each file is digested and loaded into an
in-memory structure used when the actual .java files get generated.  Our
issue now is that some of the metadata needed to generate the output for
the current project may reside in JARs for other projects.  Is there a
clean/easy way to specify the dependent projects as dependencies in the
project being built, and then reference XML files from the dependent
JARs within the code generation MOJO? 




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

Re: [M2] Checkstyle plugin "issue"

[Lee Meador]

Yes the release version does NOT use checkstyle 4 ... the release version
has no way to tell it a config file of your own. So the fact that the
eclipse plugin that I am using works with checkstyle 4 wouldn't matter.
(Well ... not yet.) I didn't give it a config file when I was using the
release version. Perhaps I am confused about it having no way to take a
config file.

It also fails with the built in config file (config/maven_checks.xml) and it
fails when there is no specified config file.

It went spelunking in the source code. The place where the exception bubbles
up into the maven plugin was rearranged in the 12/7/05 version of
CheckstyleReport.java. I know this doesn't mean the problem came up there
but it does make it suspicious.

Do you know which version in SVN reflects the release version beta-1?

Further, do you know which version in SVN added checkstyle 4.1?

I need to go look at the difference between 4.0 and 4.1.

Thanks.

On 12/27/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> But the release version doesn't use checkstyle 4
>
> On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> > The only other version I tried was beta-1, the release version.
> >
> > I just found out that the error occurs even with no config file
> specified. I
> > guess that's what you are telling me. The SVN version has that bug.
> >
> >
> >
> > On 12/27/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > > Yes, that's the problem the current plugin has.
> > > Did a previous version work for you? what day was it built?
> > >
> > > On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> > > > I am getting an exception running the maven2 checkstyle plugin.
> > > >
> > > > Since I need a custom checkstyle configuration, I'm running the
> > Checkstyle
> > > > plugin version from SVN. I updated around noon today, built and
> > installed
> > > > the snapshot.
> > > >
> > > > Previously, running the release plugin and "sun" checks, the plugin
> ran
> > > > without error and I got some results from checkstyle.
> > > >
> > > > I have read the Jira issue about checkstyle config files and read
> recent
> > > > comments in the archive for this mailing list that contain the word
> > > > "checkstyle" I have generated and read the new site docs for for the
> > > > checkstyle plugin that I just got from SVN.
> > > >
> > > > Here is a bit of the POM:
> > > >
> > > > 
> > > > 
> > > > 
> > > > org.apache.maven.plugins
> > > >
> > maven-project-info-reports-plugin
> > > > 
> > > > 
> > > > org.codehaus.mojo
> > > >
> > surefire-report-maven-plugin
> > > > 
> > > > 
> > > > org.apache.maven.plugins 
> > > >
> > maven-checkstyle-plugin
> > > > 2.0-beta-2-SNAPSHOT
> > > > 
> > > > 
> > > > ../AA-IFS-checkstyle-rules.xml
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > NOTE: I get the same error whether I use my xml file (as shown) or
> > > > config/maven_checks.xml (which is currently commented out). If I
> change
> > the
> > > > config file name to some non-existent filename, I get a different
> error
> > > > saying that it can't find the config file. My config file was
> generated
> > by
> > > > the eclipse 3.1 checkstyle 4.? plugin.
> > > >
> > > > This bit of POM is in the parent. The error occurs in the 1st child
> > project
> > > > that is processed. The parent doesn't have any source and does
> nothing
> > but
> > > > serve as a base POM.
> > > >
> > > > Here is the error: (with -e)
> > > >
> > > > [INFO] Generate "Checkstyle" report.
> > > > [INFO]
> > > >
> >
> 
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> >
> 
> > > > [INFO] Error during report generation
> > > >
> > > > Embedded error: Failed during checkstyle configuration
> > > > [INFO]
> > > >
> >
> 
> > > > [INFO] Trace
> > > > org.apache.maven.lifecycle.LifecycleExecutionException:
> > Error during report
> > > > generation
> > > > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> > > > DefaultLifecycleExecutor.java:544)
> > > > at
> > > >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > > > (DefaultLifecycleExecutor.java:469)
> > > > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> > > > DefaultLifecycleExecutor.java:448)
> > > > at
> > > >
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> > > > (DefaultLifecycleExecutor.java:301)
> > > > at
> > > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> > > > DefaultLifecycleExecutor.java

URGENT - weired problem Need help - Not finding the ant task def

[raghurajan . x . gurunathan]

Hi all

I have following structure

MyModule +
   |- EJB Module
   | - - - pom.xml
   |- WebService Module
   | - - - pom.xml
   +--- pom.xml

I do use some ant task def stuff in Webservice module

when i do "mvn clean package" from WebService Module it goes fine it does 
whatever ant taskdef suppose to do no problem. but when do same command 
from top level/project level like from MyModule directory its not finding 
the taskdef defined in Webservices Module. its very confusing. 

Any one can tell me whats wrong with thisPlease???
 





Thanks,
===
Raghurajan Gurunathan 
===

Plugin Question: Loading resources from dependency JARs

[Lewis, Allan E. \(Number Six\)]

I have a code generation MOJO that currently reads all XML files from
the resources folder of the current project and generates code based on
each file.  The XML for each file is digested and loaded into an
in-memory structure used when the actual .java files get generated.  Our
issue now is that some of the metadata needed to generate the output for
the current project may reside in JARs for other projects.  Is there a
clean/easy way to specify the dependent projects as dependencies in the
project being built, and then reference XML files from the dependent
JARs within the code generation MOJO? 

Any easy way to list all goals available for a plugin?

[Man-Chi Leung]

hi,

after anyway new plug-in installation, I will very much rely on "mvn  
site" to generate a html site for checking out all Goals available.


sometimes, there is nothing.  very often, I need to dig all the way  
to view a plug-in's source code.


yes, look at the @goal  annotation stated for the mojo class.

I am wondering whether there is a better way to list all available  
goals in M2.


in Maven1, we have $maven -P  or  $maven -g

how about M2? pls advise.

Best Regards,

Manchi Leung 

anyone is using Groovy plugin for unit testing?

[Man-Chi Leung]

hi ,

anyone is using Groovy plugin for writing Junit test cases on M2?
this article mentioned about using groovy for junit , but with maven 1.
http://www-128.ibm.com/developerworks/java/library/j-pg11094/

i got the groovy plugin from mojo.codehuas  but having the questions

I will not able to use sure-fire to generate any xml report?
therefore I would not have any surefire-report  in my site. am i  
correct?


anyone is playing on this?


Regards,
manchi

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

Re: [m1] Using the collapse attribute of item in navigation.xml

[Arnaud HERITIER]

Yes you cannot use relative paths in the navigation.xml because the links
are used in every page thus you can't know from where the relative path is.

Arnaud

On 12/28/05, Philip Mark Donaghy <[EMAIL PROTECTED]> wrote:
>
> Thanks Arnaud,
>
> I found the problem. We were using relative paths in the href attributes.
> But apparently the first slash is required to expand and collapse menus.
>
> 
>
> NOT:
>
> 
>
> Philip
>
> Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Did you check if the link you
> use on the collapsed/expanded link is good.
> I remember that there was a problem if the link wasn't found : it was
> impossible to collapse/expand the item.
>
> Arnaud
>
> On 12/27/05, Philip Mark Donaghy
> wrote:
> >
> > We are using Maven 1 for the Jetspeed website. When I use the value true
> > the menu item is always collapsed, otherwise it is always expanded.
> > Navigating around the site  does not change the menu. Is there a missing
> tag
> > in the xdoc, that makes the menu interactive? I am using maven 1.0.2.
> >
> > Thanks,
> > Philip
> >   --
> >
> > --
> > Yahoo! for Good - Make a difference this year.
> >
> >
> > -- Forwarded message --
> > From: Philip Mark Donaghy
>
> > To: [EMAIL PROTECTED]
> > Date: Mon, 26 Dec 2005 11:20:21 -0800 (PST)
> > Subject: [m1] Using the collapse attribute of item in navigation.xml
> > When I use the value true the menu item is always collapsed, otherwise
> it
> > is always expanded. Navigating around the site  does not change the
> menu. Is
> > there a missing tag in the xdoc? I am using maven 1.0.2.
> >
> > Thanks,
> > Philip
> >
> > --
> > Yahoo! DSLSomething to write home about. Just $16.99/mo. or less
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
>
>
>
> -
> Yahoo! Photos
> Ring in the New Year with Photo Calendars. Add photos, events, holidays,
> whatever.
>

Re: [m1] Using the collapse attribute of item in navigation.xml

[Philip Mark Donaghy]

Thanks Arnaud,
 
 I found the problem. We were using relative paths in the href attributes. But 
apparently the first slash is required to expand and collapse menus.
 
 
 
 NOT:
 
 
 
 Philip

Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Did you check if the link you use on 
the collapsed/expanded link is good.
I remember that there was a problem if the link wasn't found : it was
impossible to collapse/expand the item.

Arnaud

On 12/27/05, Philip Mark Donaghy 
 wrote:
>
> We are using Maven 1 for the Jetspeed website. When I use the value true
> the menu item is always collapsed, otherwise it is always expanded.
> Navigating around the site  does not change the menu. Is there a missing tag
> in the xdoc, that makes the menu interactive? I am using maven 1.0.2.
>
> Thanks,
> Philip
>   --
>
> --
> Yahoo! for Good - Make a difference this year.
>
>
> -- Forwarded message --
> From: Philip Mark Donaghy 

> To: [EMAIL PROTECTED]
> Date: Mon, 26 Dec 2005 11:20:21 -0800 (PST)
> Subject: [m1] Using the collapse attribute of item in navigation.xml
> When I use the value true the menu item is always collapsed, otherwise it
> is always expanded. Navigating around the site  does not change the menu. Is
> there a missing tag in the xdoc? I am using maven 1.0.2.
>
> Thanks,
> Philip
>
> --
> Yahoo! DSLSomething to write home about. Just $16.99/mo. or less
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>






-
Yahoo! Photos
 Ring in the New Year with Photo Calendars. Add photos, events, holidays, 
whatever.

Re: [M2] Checkstyle plugin "issue"

[Carlos Sanchez]

But the release version doesn't use checkstyle 4

On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> The only other version I tried was beta-1, the release version.
>
> I just found out that the error occurs even with no config file specified. I
> guess that's what you are telling me. The SVN version has that bug.
>
>
>
> On 12/27/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > Yes, that's the problem the current plugin has.
> > Did a previous version work for you? what day was it built?
> >
> > On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> > > I am getting an exception running the maven2 checkstyle plugin.
> > >
> > > Since I need a custom checkstyle configuration, I'm running the
> Checkstyle
> > > plugin version from SVN. I updated around noon today, built and
> installed
> > > the snapshot.
> > >
> > > Previously, running the release plugin and "sun" checks, the plugin ran
> > > without error and I got some results from checkstyle.
> > >
> > > I have read the Jira issue about checkstyle config files and read recent
> > > comments in the archive for this mailing list that contain the word
> > > "checkstyle" I have generated and read the new site docs for for the
> > > checkstyle plugin that I just got from SVN.
> > >
> > > Here is a bit of the POM:
> > >
> > > 
> > > 
> > > 
> > > org.apache.maven.plugins
> > >
> maven-project-info-reports-plugin
> > > 
> > > 
> > > org.codehaus.mojo
> > >
> surefire-report-maven-plugin
> > > 
> > > 
> > > org.apache.maven.plugins 
> > >
> maven-checkstyle-plugin
> > > 2.0-beta-2-SNAPSHOT
> > > 
> > > 
> > > ../AA-IFS-checkstyle-rules.xml
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > NOTE: I get the same error whether I use my xml file (as shown) or
> > > config/maven_checks.xml (which is currently commented out). If I change
> the
> > > config file name to some non-existent filename, I get a different error
> > > saying that it can't find the config file. My config file was generated
> by
> > > the eclipse 3.1 checkstyle 4.? plugin.
> > >
> > > This bit of POM is in the parent. The error occurs in the 1st child
> project
> > > that is processed. The parent doesn't have any source and does nothing
> but
> > > serve as a base POM.
> > >
> > > Here is the error: (with -e)
> > >
> > > [INFO] Generate "Checkstyle" report.
> > > [INFO]
> > >
> 
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> 
> > > [INFO] Error during report generation
> > >
> > > Embedded error: Failed during checkstyle configuration
> > > [INFO]
> > >
> 
> > > [INFO] Trace
> > > org.apache.maven.lifecycle.LifecycleExecutionException:
> Error during report
> > > generation
> > > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> > > DefaultLifecycleExecutor.java:544)
> > > at
> > >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > > (DefaultLifecycleExecutor.java:469)
> > > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> > > DefaultLifecycleExecutor.java:448)
> > > at
> > >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> > > (DefaultLifecycleExecutor.java:301)
> > > at
> > >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> > > DefaultLifecycleExecutor.java:268)
> > > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (
> > > DefaultLifecycleExecutor.java:137)
> > > at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> > > at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> > > at org.apache.maven.cli.MavenCli.main
> (MavenCli.java:249)
> > > at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > NativeMethodAccessorImpl.java:39)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (
> > > DelegatingMethodAccessorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java: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)
> > > Caused by:
> org.apache.maven.plugin.MojoExecutionException : Error
> during
> > > report generation
> > > at
> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389)
> > > at
> org.apache.maven.plugin.DefaultPluginMa

Re: [m2] maven-eclipse-plugin and wtp 1.0

[Alexandre Poitras]

Anyway wtp 1.0 is buggy, external libraries don't work anymore so you have to
stay with r7 till the bug is resolved.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 for details,
the issue is scheduled for 1.0.1. Please add a vote to the issue in
bugzilla to raise the priority for eclipse developers!

On 12/27/05, Rinku <[EMAIL PROTECTED]> wrote:
> Yes, there will be changes to m2 eclipse plugin for wtp1.0.
>
> I am in process of adding support for wtp 1.0 and testing, and submit a
> patch on JIRA shortly.
> http://jira.codehaus.org/browse/MECLIPSE-47?page=all
>
> Cheers,
> Rahul
>
>
> - Original Message -
> From: "Srepfler Srgjan" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Sent: Wednesday, December 28, 2005 12:03 AM
> Subject: [m2] maven-eclipse-plugin and wtp 1.0
>
>
> > Will there be any changes to the maven-eclipse-plugin to integrate with
> > the WTP 1.0 way of managing j2ee projects?
> >
> > Cheers
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Alexandre Poitras
Québec, Canada

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

Re: [m1] Using the collapse attribute of item in navigation.xml

[Arnaud HERITIER]

Did you check if the link you use on the collapsed/expanded link is good.
I remember that there was a problem if the link wasn't found : it was
impossible to collapse/expand the item.

Arnaud

On 12/27/05, Philip Mark Donaghy <[EMAIL PROTECTED]> wrote:
>
> We are using Maven 1 for the Jetspeed website. When I use the value true
> the menu item is always collapsed, otherwise it is always expanded.
> Navigating around the site  does not change the menu. Is there a missing tag
> in the xdoc, that makes the menu interactive? I am using maven 1.0.2.
>
> Thanks,
> Philip
>   --
>
> --
> Yahoo! for Good - Make a difference this 
> year.
>
>
> -- Forwarded message --
> From: Philip Mark Donaghy <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Mon, 26 Dec 2005 11:20:21 -0800 (PST)
> Subject: [m1] Using the collapse attribute of item in navigation.xml
> When I use the value true the menu item is always collapsed, otherwise it
> is always expanded. Navigating around the site  does not change the menu. Is
> there a missing tag in the xdoc? I am using maven 1.0.2.
>
> Thanks,
> Philip
>
> --
> Yahoo! 
> DSLSomething
>  to write home about. Just $16.99/mo. or less
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

[m1] Using the collapse attribute of item in navigation.xml

[Philip Mark Donaghy]

We are using Maven 1 for the Jetspeed website. When I use the value true the menu item is always collapsed, otherwise it is always expanded. Navigating around the site  does not change the menu. Is there a missing tag in the xdoc, that makes the menu interactive? I am using maven 1.0.2.  Thanks,Philip   
		Yahoo! for Good - 
Make a difference this year. --- Begin Message ---
When I use the value true the menu item is always collapsed, otherwise it is always expanded. Navigating around the site  does not change the menu. Is there a missing tag in the xdoc? I am using maven 1.0.2.  Thanks, Philip 
		 Yahoo! DSL Something to write home about. Just $16.99/mo. or less--- End Message ---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] Checkstyle plugin "issue"

[Carlos Sanchez]

Yes, that's the problem the current plugin has.
Did a previous version work for you? what day was it built?

On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> I am getting an exception running the maven2 checkstyle plugin.
>
> Since I need a custom checkstyle configuration, I'm running the Checkstyle
> plugin version from SVN. I updated around noon today, built and installed
> the snapshot.
>
> Previously, running the release plugin and "sun" checks, the plugin ran
> without error and I got some results from checkstyle.
>
> I have read the Jira issue about checkstyle config files and read recent
> comments in the archive for this mailing list that contain the word
> "checkstyle" I have generated and read the new site docs for for the
> checkstyle plugin that I just got from SVN.
>
> Here is a bit of the POM:
>
> 
> 
> 
> org.apache.maven.plugins
> maven-project-info-reports-plugin
> 
> 
> org.codehaus.mojo
> surefire-report-maven-plugin
> 
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.0-beta-2-SNAPSHOT
> 
> 
> ../AA-IFS-checkstyle-rules.xml
> 
> 
> 
> 
> 
>
> NOTE: I get the same error whether I use my xml file (as shown) or
> config/maven_checks.xml (which is currently commented out). If I change the
> config file name to some non-existent filename, I get a different error
> saying that it can't find the config file. My config file was generated by
> the eclipse 3.1 checkstyle 4.? plugin.
>
> This bit of POM is in the parent. The error occurs in the 1st child project
> that is processed. The parent doesn't have any source and does nothing but
> serve as a base POM.
>
> Here is the error: (with -e)
>
> [INFO] Generate "Checkstyle" report.
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error during report generation
>
> Embedded error: Failed during checkstyle configuration
> [INFO]
> 
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during report
> generation
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:544)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:469)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:448)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecycleExecutor.java:301)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:268)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:137)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java: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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
> report generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:399)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:519)
> ... 16 more
> Caused by: org.apache.maven.reporting.MavenReportException: Failed during
> checkstyle configuration
> at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(
> CheckstyleReport.java:461)
> at org.apache.maven.reporting.AbstractMavenReport.generate(
> AbstractMavenReport.java:98)
> at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
> SiteMojo.java:802)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> ... 18 more
> Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: unable
> to read default package names
> at com.puppycrawl.tool

[M2] Checkstyle plugin "issue"

[Lee Meador]

I am getting an exception running the maven2 checkstyle plugin.

Since I need a custom checkstyle configuration, I'm running the Checkstyle
plugin version from SVN. I updated around noon today, built and installed
the snapshot.

Previously, running the release plugin and "sun" checks, the plugin ran
without error and I got some results from checkstyle.

I have read the Jira issue about checkstyle config files and read recent
comments in the archive for this mailing list that contain the word
"checkstyle" I have generated and read the new site docs for for the
checkstyle plugin that I just got from SVN.

Here is a bit of the POM:




org.apache.maven.plugins
maven-project-info-reports-plugin


org.codehaus.mojo
surefire-report-maven-plugin


org.apache.maven.plugins
maven-checkstyle-plugin
2.0-beta-2-SNAPSHOT


../AA-IFS-checkstyle-rules.xml






NOTE: I get the same error whether I use my xml file (as shown) or
config/maven_checks.xml (which is currently commented out). If I change the
config file name to some non-existent filename, I get a different error
saying that it can't find the config file. My config file was generated by
the eclipse 3.1 checkstyle 4.? plugin.

This bit of POM is in the parent. The error occurs in the 1st child project
that is processed. The parent doesn't have any source and does nothing but
serve as a base POM.

Here is the error: (with -e)

[INFO] Generate "Checkstyle" report.
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error during report generation

Embedded error: Failed during checkstyle configuration
[INFO]

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during report
generation
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:544)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:469)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java: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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
report generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:399)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:519)
... 16 more
Caused by: org.apache.maven.reporting.MavenReportException: Failed during
checkstyle configuration
at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(
CheckstyleReport.java:461)
at org.apache.maven.reporting.AbstractMavenReport.generate(
AbstractMavenReport.java:98)
at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
SiteMojo.java:802)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
... 18 more
Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: unable
to read default package names
at com.puppycrawl.tools.checkstyle.PackageNamesLoader.loadModuleFactory(
PackageNamesLoader.java:198)
at com.puppycrawl.tools.checkstyle.PackageNamesLoader.loadModuleFactory(
PackageNamesLoader.java:146)
at org.apache.maven.plugin.checkstyle.CheckstyleReport.getModuleFactory(
CheckstyleReport.java:823)
at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(
CheckstyleRepo

Re: [m2] maven-eclipse-plugin and wtp 1.0

[Rinku]

Yes, there will be changes to m2 eclipse plugin for wtp1.0.

I am in process of adding support for wtp 1.0 and testing, and submit a 
patch on JIRA shortly.

http://jira.codehaus.org/browse/MECLIPSE-47?page=all

Cheers,
Rahul


- Original Message - 
From: "Srepfler Srgjan" <[EMAIL PROTECTED]>

To: "Maven Users List" 
Sent: Wednesday, December 28, 2005 12:03 AM
Subject: [m2] maven-eclipse-plugin and wtp 1.0



Will there be any changes to the maven-eclipse-plugin to integrate with
the WTP 1.0 way of managing j2ee projects?

Cheers

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




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

Re: maven-jetty6-plugin

[Koen Maes]

try this:


org.mortbay.jetty

maven-jetty6-plugin


10

/koma-web



org.apache.commons.logging.Log


org.apache.commons.logging.impl.SimpleLog






I think that the reason for this is explained in the maven-jetty6-plugin page.

rgds,

koen

On Tuesday 27 December 2005 17:13, Chris Richardson wrote:
> Hi,
>
> When I try running jetty6:run I get this error, which seems to be related
> to log4j.
> Any suggestions?
>
> Thanks.
>
> Chris
>
> [DEBUG] Trace
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(
> NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(
> WebXmlConfiguration.java:553)
> at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(
> WebXmlConfiguration.java:345)
> at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(
> WebXmlConfiguration.java:267)
> at org.mortbay.jetty.plugin.JettyMavenConfiguration.configureWebApp(
> JettyMavenConfiguration.java:114)
> at org.mortbay.jetty.webapp.WebAppContext.startContext(
> WebAppContext.java:781)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java
>
> :345)
>
> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java
>
> :209)
>
> at
> org.mortbay.thread.AbstractLifeCycle.start(AbstractLifeCycle.java:37) at
> org.mortbay.jetty.handler.HandlerCollection.doStart(
> HandlerCollection.java:90)
> at org.mortbay.jetty.Server.doStart(Server.java:138)
> at
> org.mortbay.thread.AbstractLifeCycle.start(AbstractLifeCycle.java:37) at
> org.mortbay.jetty.plugin.JettyMojo.startJetty(JettyMojo.java:424) at
> org.mortbay.jetty.plugin.JettyMojo.execute(JettyMojo.java:370) at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:432)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:530)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
> DefaultLifecycleExecutor.java:485)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:455)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai
>lures (DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:270)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java: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)
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: No suitable Log
> constructor [Ljava.lang.Class;@1cda59b for
> org.apache.commons.logging.impl.Log4JLogger
> at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
> LogFactoryImpl.java:532)
> at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
> LogFactoryImpl.java:272)
> at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
> LogFactoryImpl.java:24

RE: About the "package" goal

[Brian E. Fox]

Assembly can't be run as part of the build lifecycle. You can get this
functionality using the dependency plugin at the mojo site:
http://mojo.codehaus.org 

-Original Message-
From: Scokart Gilles [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 27, 2005 4:21 AM
To: Maven Users List
Subject: RE: About the "package" goal

Look at the assembly plugin.

> -Original Message-
> From: Luiz Eduardo Guida Valmont [mailto:[EMAIL PROTECTED]
> Sent: 27 December 2005 00:33
> To: users@maven.apache.org
> Subject: About the "package" goal
> 
> Hi everyone,
> 
> I'm working on a simple command-line project and it has log4j as one 
> of its dep's. As I didn't find (or wasn't able to find, so to say) any

> documentation on the subject, here is my question: how can I package 
> log4j along with my project's classes in the jar generated by the 
> "package" target? I know how I should setup the main class for the 
> jar, but I still cannot package loj4j along.
> 
> I can bundle the lo4j-1.2.12.jar as a resource and that'd be the end 
> of it, but that would be far from "elegant" (as I would have to keep 
> track of changes in the pom.xml (if I decided to change to 
> log4j-1.3.jar I'd have to copy it over).
> 
> Sorry if this is a question of old. I'd appreciate if anyone would 
> just point me links that I can follow. ;-)
> 
> Thanks in advance,
> Luiz Eduardo
> 
> -
> 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: Reports: Where are the docs?

[Lee Meador]

I did notice the generated docs seem to assume an HTTPS connection to
Subversion for developers. Is there a way to change that text? Or am I
making a mistake using svn:// for our developers since it's all on the
intranet? (That is sort of off topic though.)

On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> To answer the question about filling in the default informational bits
> with more interesting stuff, I found this in the source code. I looked in
> POM.xml in the root folder of the source. Evidently you put these tags in
> your parent POM to cause things to get filled in in the docs. I copied some
> from one POM and some from another but the examples should help.
>
> (You can get more information on the tags here -
> http://maven.apache.org/maven-model/maven.html - search for
> "issueManagement" or "license" to find the part of that page that matters.
> This page confused me at first. The top part of the page shows all the XML
> tags that there can be and those tags have links down to the bottom part
> where there are explanations of what the tags do.)
>
> 
>
> 
>
>   Development List
>   [EMAIL PROTECTED]
>   
> [EMAIL PROTECTED]
>   dev@mojo.codehaus.org
>   
> http://archive.mojo.codehaus.org/dev/
> 
>   
>
>   
> jira
> 
> http://jira.codehaus.org/browse/MOJO
>   
>
>   
> scm:svn:svn://svn.codehaus.org/mojo/scm/trunk/mojo
> 
> 
> scm:svn:https://svn.codehaus.org/mojo/trunk/mojo
> 
> http://svn.mojo.codehaus.org/trunk/mojo
>   
>
>   
> continuum
> 
>   
> 
>   commits@maven.apache.org
> 
>   
> 
>   
>
>   
> 
>   jvanzyl
>   Jason van Zyl
>[EMAIL PROTECTED]
>   ASF
>   
> PMC Chair
>   
>   -5
> 
>   
>
>   
> 
>   The Apache Software License, Version 2.0
>http://www.apache.org/licenses/LICENSE-2.0.txt
>   repo
> 
>   
>
>   
> Apache Software Foundation
> http://www.apache.org/
>   
>
>
> On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> >
> > I'm replying to my own email. Duh?
> >
> > On 12/27/05, Lee Meador < [EMAIL PROTECTED]> wrote:
> > >
> > > Several things:
> > >
> > > 1) This page: 
> > > http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html
> > > has an example of using the surefire report. Their example gives the
> > > version number with SNAPSHOT on the end. That doesn't work. Your
> > > example, without a version number, works to generate the junit report
> > >
> > > 2) There only seems to be a JUnit report on the parent project. I just
> > > put the reporting stuff in the parent project's POM. The children don't 
> > > have
> > > it. The children generate reports with all the default text but the 
> > > children
> > > don't seem to generate the JUnit report. Does the one thing inherit and 
> > > the
> > > other not?
> >
> >
> > The JUnit report only gets generated if there are JUnit tests in the
> > child project.  That makes sense. I was looking for an empty report in a
> > project with no tests yet. Oh well.
> >
> > 3) Your example has the  tag duplicated. It should look like
> > > this:
> > >
> > > 
> > >
> > > 
> > >  org.apache.maven.plugins
> > > maven-javadoc-plugin
> > > 
> > > 
> > >  org.apache.maven.plugins 
> > > maven-checkstyle-plugin
> > > 
> > >
> > > 
> > >
> > > 4) How do I tell it my checkstyle xml configuration file's name so it
> > > checks the right stuff.
> > >
> > > 5) Finally, and its really my fault for asking several questions at
> > > once, how do I get it to fill in interesting values for.
> > >
> > > Document Description
> > > Continuous Integration
> > > Dependencies
> > > Issue Tracking
> > > Mailing Lists
> > > Project License
> > > Project Team
> > > Source Repository
> > >
> > > There are currently only defaults in the generated reports.
> >
> >
> > One correction, the "dependencies" section does have lists of any of my
> > projects upon which the project depends and any 3rd party libraries on which
> > it depends--stuff like Spring and commons-logging.
> >
> > thanks.
> > >
> > > -- Lee Meador
> >
> >
> > And one other thing--is there a way to tie the reports together in some
> > way so you can click around and get to all the related projects or see them
> > in a unified report or something?
> >
> > On 12/22/05, Allan Ramirez < [EMAIL PROTECTED]> wrote:
> > >
> > > > Hi Lee,
> > > >
> > > > Have a look in
> > > > http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F
> > > >
> > > >
> > > > just replace the value in  element to the report plugin
> > > > you
> > > > want to generate
> > > > i.e.
> > > >
> > > > 
> > > >
> > > > 
> > > >  org.apache.maven.plugins
> > > > maven-javadoc-plugin
> > > > 
> > > >
> > > >  

Re: Reports: Where are the docs?

[Lee Meador]

To answer the question about filling in the default informational bits with
more interesting stuff, I found this in the source code. I looked in
POM.xmlin the root folder of the source. Evidently you put these tags
in your
parent POM to cause things to get filled in in the docs. I copied some from
one POM and some from another but the examples should help.

(You can get more information on the tags here -
http://maven.apache.org/maven-model/maven.html - search for
"issueManagement" or "license" to find the part of that page that matters.
This page confused me at first. The top part of the page shows all the XML
tags that there can be and those tags have links down to the bottom part
where there are explanations of what the tags do.)




  Development List
  [EMAIL PROTECTED]
  [EMAIL PROTECTED]
  dev@mojo.codehaus.org
  http://archive.mojo.codehaus.org/dev/

  

  
jira
http://jira.codehaus.org/browse/MOJO
  

  
scm:svn:svn://svn.codehaus.org/mojo/scm/trunk/mojo

scm:svn:https://svn.codehaus.org/mojo/trunk/mojo
http://svn.mojo.codehaus.org/trunk/mojo
  

  
continuum

  

  commits@maven.apache.org

  

  

  

  jvanzyl
  Jason van Zyl
  [EMAIL PROTECTED]
  ASF
  
PMC Chair
  
  -5

  

  

  The Apache Software License, Version 2.0
  http://www.apache.org/licenses/LICENSE-2.0.txt
  repo

  

  
Apache Software Foundation
http://www.apache.org/
  


On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> I'm replying to my own email. Duh?
>
> On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
> >
> > Several things:
> >
> > 1) This page: 
> > http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html
> > has an example of using the surefire report. Their example gives the
> > version number with SNAPSHOT on the end. That doesn't work. Your
> > example, without a version number, works to generate the junit report
> >
> > 2) There only seems to be a JUnit report on the parent project. I just
> > put the reporting stuff in the parent project's POM. The children don't have
> > it. The children generate reports with all the default text but the children
> > don't seem to generate the JUnit report. Does the one thing inherit and the
> > other not?
>
>
> The JUnit report only gets generated if there are JUnit tests in the child
> project.  That makes sense. I was looking for an empty report in a project
> with no tests yet. Oh well.
>
> 3) Your example has the  tag duplicated. It should look like
> > this:
> >
> > 
> >
> > 
> >  org.apache.maven.plugins
> > maven-javadoc-plugin
> > 
> > 
> >  org.apache.maven.plugins 
> > maven-checkstyle-plugin
> > 
> >
> > 
> >
> > 4) How do I tell it my checkstyle xml configuration file's name so it
> > checks the right stuff.
> >
> > 5) Finally, and its really my fault for asking several questions at
> > once, how do I get it to fill in interesting values for.
> >
> > Document Description
> > Continuous Integration
> > Dependencies
> > Issue Tracking
> > Mailing Lists
> > Project License
> > Project Team
> > Source Repository
> >
> > There are currently only defaults in the generated reports.
>
>
> One correction, the "dependencies" section does have lists of any of my
> projects upon which the project depends and any 3rd party libraries on which
> it depends--stuff like Spring and commons-logging.
>
> thanks.
> >
> > -- Lee Meador
>
>
> And one other thing--is there a way to tie the reports together in some
> way so you can click around and get to all the related projects or see them
> in a unified report or something?
>
> On 12/22/05, Allan Ramirez < [EMAIL PROTECTED]> wrote:
> >
> > > Hi Lee,
> > >
> > > Have a look in
> > > http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F
> > >
> > >
> > > just replace the value in  element to the report plugin
> > > you
> > > want to generate
> > > i.e.
> > >
> > > 
> > >
> > > 
> > >  org.apache.maven.plugins
> > > maven-javadoc-plugin
> > > 
> > >
> > >
> > > 
> > > org.apache.maven.plugins
> > > maven-checkstyle-plugin
> > > 
> > >
> > > 
> > >
> > > junit test report was renamed to surefire report plugin and currently
> > > hosted at mojo codehaus
> > >
> > >
> > > 
> > > org.codehaus.mojo
> > > surefire-report-maven-plugin
> > > 
> > >
> > >
> > > You may also refer to this page for more plugins at codehaus
> > >
> > > http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F
> > >
> > > -allan
> > >
> > > Lee Meador wrote:
> > >
> > > >I want to generate

Re: [m2] Artifact relocations and scope priorities

[Carlos Sanchez]

IIRC there was a jira issue that was fixed

On 12/27/05, Yann Le Du <[EMAIL PROTECTED]> wrote:
> Carlos,
>
> This is no problem, I can do any patch for acegi.
> What I'm asking is if there is a better way to handle this kind of problem.
> Would e.g. relocate jsp-api (as servlet-api is) solve the problem ? Maybe we
> can try this, I guess it has to be done anyway.
> Do you agree ?
>
> --
> Yann
>
> 2005/12/27, Carlos Sanchez <[EMAIL PROTECTED]>:
> >
> > You can probably exclude jspapi in acegi
> >
> > 1.0.0-RC1 has the right dependencies
> >
> > On 12/27/05, Yann Le Du <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > > I noticed something potentially confusing with artifact relocations.
> > >
> > > Say I want to declare a 'provided' jsp-api 2.0 dependency :
> > > ~ javax.servlet
> > > ~ jsp-api
> > > ~ 2.0
> > > ~ provided
> > >
> > > I also have a dependency upon acegi-security 0.8.2, which in turn
> > > unfortunately depends on jsp-api in the "old way" :
> > > ~ jspapi
> > > ~ jsp-api
> > > ~ 2.0
> > >
> > > The result is that jsp-api-2.0.jar is included as a compile dependency.
> > > Of course, I could (and will) send a patch for acegi-security, but this
> > can
> > > happen on any other dependency - and I won't catch it.
> > > The only secure workaround I have found is to dup the dependency - not
> > very
> > > elegant :
> > > ~   
> > > ~ javax.servlet
> > > ~ jsp-api
> > > ~ 2.0
> > > ~ provided
> > > ~   
> > > ~   
> > > ~ jspapi
> > > ~ jsp-api
> > > ~ 2.0
> > > ~ provided
> > > ~   
> > >
> > > Thoughts ?
> > > --
> > > Yann
> > >
> > >
> >
> > -
> > 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: Reports: Where are the docs?

[Lee Meador]

I'm replying to my own email. Duh?

On 12/27/05, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> Several things:
>
> 1) This page:
> http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an
> example of using the surefire report. Their example gives the version number
> with SNAPSHOT on the end. That doesn't work. Your example, without a
> version number, works to generate the junit report
>
> 2) There only seems to be a JUnit report on the parent project. I just put
> the reporting stuff in the parent project's POM. The children don't have it.
> The children generate reports with all the default text but the children
> don't seem to generate the JUnit report. Does the one thing inherit and the
> other not?


The JUnit report only gets generated if there are JUnit tests in the child
project.  That makes sense. I was looking for an empty report in a project
with no tests yet. Oh well.

3) Your example has the  tag duplicated. It should look like this:
>
> 
>
> 
>  org.apache.maven.plugins
> maven-javadoc-plugin
> 
> 
> org.apache.maven.plugins 
> maven-checkstyle-plugin
> 
>
> 
>
> 4) How do I tell it my checkstyle xml configuration file's name so it
> checks the right stuff.
>
> 5) Finally, and its really my fault for asking several questions at once,
> how do I get it to fill in interesting values for.
>
> Document Description
> Continuous Integration
> Dependencies
> Issue Tracking
> Mailing Lists
> Project License
> Project Team
> Source Repository
>
> There are currently only defaults in the generated reports.


One correction, the "dependencies" section does have lists of any of my
projects upon which the project depends and any 3rd party libraries on which
it depends--stuff like Spring and commons-logging.

thanks.
>
> -- Lee Meador


And one other thing--is there a way to tie the reports together in some way
so you can click around and get to all the related projects or see them in a
unified report or something?

On 12/22/05, Allan Ramirez <[EMAIL PROTECTED]> wrote:
>
> > Hi Lee,
> >
> > Have a look in
> > http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F
> >
> >
> > just replace the value in  element to the report plugin you
> > want to generate
> > i.e.
> >
> > 
> >
> > 
> >  org.apache.maven.plugins
> > maven-javadoc-plugin
> > 
> >
> >
> > 
> > org.apache.maven.plugins
> > maven-checkstyle-plugin
> > 
> >
> > 
> >
> > junit test report was renamed to surefire report plugin and currently
> > hosted at mojo codehaus
> >
> >
> > 
> > org.codehaus.mojo
> > surefire-report-maven-plugin
> > 
> >
> >
> > You may also refer to this page for more plugins at codehaus
> >
> > http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F
> >
> > -allan
> >
> > Lee Meador wrote:
> >
> > >I want to generate interesting reports.
> > >
> > >All I have been able to find says that you can get some reports by
> > adding
> > >this
> > >
> > >
> > >
> > >
> > >org.apache.maven.plugins
> > >maven-project-info-reports-plugin
> >
> > >
> > >   
> > >
> > >
> > >to the POM.
> > >
> > >I did that and got a dummy report with nothing interesting in it.
> > >
> > >Here are the main topics that look like you put some info somewhere to
> > make
> > >it appear in the site docs. Maybe someone will fill in some doc links
> > or
> > >mention where they go.
> > >
> > >Document Description
> > >Continuous Integration
> > >Dependencies
> > >Issue Tracking
> > >Mailing Lists
> > >Project License
> > >Project Team
> > >Source Repository
> > >
> > >How do I get things (that I remember from a previous project with Maven
> > 1)
> > >like:
> > >
> > >javadoc
> > >checkstyle report
> > >junit test results
> > >lists of recent changes in the source repository
> > >
> > >Finally, I am generating an EAR with a WAR (or two) and some EJBs and
> > some
> > >other JAR files in it. All told there are about 10 "parts" each with
> > its own
> > >POM and a parent pom for building the whole thing. It builds and the
> > report
> > >stuff seems to get built for each of the subprojects.
> > >
> > >Is the parent going to have stuff consolidated from the children or are
> >
> > >there going to be links in there somewhere? I'm not sure what I'm going
> > to
> > >end up with.
> > >
> > >Really, I have searched the archives of this list and almost all I can
> > find
> > >is folks complaining about the surefire report plugin not working. But
> > I
> > >can't even get it to find that plugin in the central repository.
> > >
> > >And the docs seem to be missing something that I can'

Re: [m2] Artifact relocations and scope priorities

[Yann Le Du]

Carlos,

This is no problem, I can do any patch for acegi.
What I'm asking is if there is a better way to handle this kind of problem.
Would e.g. relocate jsp-api (as servlet-api is) solve the problem ? Maybe we
can try this, I guess it has to be done anyway.
Do you agree ?

--
Yann

2005/12/27, Carlos Sanchez <[EMAIL PROTECTED]>:
>
> You can probably exclude jspapi in acegi
>
> 1.0.0-RC1 has the right dependencies
>
> On 12/27/05, Yann Le Du <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I noticed something potentially confusing with artifact relocations.
> >
> > Say I want to declare a 'provided' jsp-api 2.0 dependency :
> > ~ javax.servlet
> > ~ jsp-api
> > ~ 2.0
> > ~ provided
> >
> > I also have a dependency upon acegi-security 0.8.2, which in turn
> > unfortunately depends on jsp-api in the "old way" :
> > ~ jspapi
> > ~ jsp-api
> > ~ 2.0
> >
> > The result is that jsp-api-2.0.jar is included as a compile dependency.
> > Of course, I could (and will) send a patch for acegi-security, but this
> can
> > happen on any other dependency - and I won't catch it.
> > The only secure workaround I have found is to dup the dependency - not
> very
> > elegant :
> > ~   
> > ~ javax.servlet
> > ~ jsp-api
> > ~ 2.0
> > ~ provided
> > ~   
> > ~   
> > ~ jspapi
> > ~ jsp-api
> > ~ 2.0
> > ~ provided
> > ~   
> >
> > Thoughts ?
> > --
> > Yann
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Reports: Where are the docs?

[Lee Meador]

Several things:

1) This page:
http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an
example of using the surefire report. Their example gives the version number
with SNAPSHOT on the end. That doesn't work. Your example, without a version
number, works to generate the junit report

2) There only seems to be a JUnit report on the parent project. I just put
the reporting stuff in the parent project's POM. The children don't have it.
The children generate reports with all the default text but the children
don't seem to generate the JUnit report. Does the one thing inherit and the
other not?

3) Your example has the  tag duplicated. It should look like this:


   

org.apache.maven.plugins
maven-javadoc-plugin


org.apache.maven.plugins
maven-checkstyle-plugin

   


4) How do I tell it my checkstyle xml configuration file's name so it checks
the right stuff.

5) Finally, and its really my fault for asking several questions at once,
how do I get it to fill in interesting values for.

Document Description
Continuous Integration
Dependencies
Issue Tracking
Mailing Lists
Project License
Project Team
Source Repository

There are currently only defaults in the generated reports.

thanks.

-- Lee Meador


On 12/22/05, Allan Ramirez <[EMAIL PROTECTED]> wrote:
>
> Hi Lee,
>
> Have a look in
>
> http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F
>
> just replace the value in  element to the report plugin you
> want to generate
> i.e.
>
> 
>
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 
>
>
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 
>
> 
>
> junit test report was renamed to surefire report plugin and currently
> hosted at mojo codehaus
>
>
> 
> org.codehaus.mojo
> surefire-report-maven-plugin
> 
>
>
> You may also refer to this page for more plugins at codehaus
>
> http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F
>
> -allan
>
> Lee Meador wrote:
>
> >I want to generate interesting reports.
> >
> >All I have been able to find says that you can get some reports by adding
> >this
> >
> >
> >
> >
> >org.apache.maven.plugins
>
> >maven-project-info-reports-plugin
> >
> >   
> >
> >
> >to the POM.
> >
> >I did that and got a dummy report with nothing interesting in it.
> >
> >Here are the main topics that look like you put some info somewhere to
> make
> >it appear in the site docs. Maybe someone will fill in some doc links or
> >mention where they go.
> >
> >Document Description
> >Continuous Integration
> >Dependencies
> >Issue Tracking
> >Mailing Lists
> >Project License
> >Project Team
> >Source Repository
> >
> >How do I get things (that I remember from a previous project with Maven
> 1)
> >like:
> >
> >javadoc
> >checkstyle report
> >junit test results
> >lists of recent changes in the source repository
> >
> >Finally, I am generating an EAR with a WAR (or two) and some EJBs and
> some
> >other JAR files in it. All told there are about 10 "parts" each with its
> own
> >POM and a parent pom for building the whole thing. It builds and the
> report
> >stuff seems to get built for each of the subprojects.
> >
> >Is the parent going to have stuff consolidated from the children or are
> >there going to be links in there somewhere? I'm not sure what I'm going
> to
> >end up with.
> >
> >Really, I have searched the archives of this list and almost all I can
> find
> >is folks complaining about the surefire report plugin not working. But I
> >can't even get it to find that plugin in the central repository.
> >
> >And the docs seem to be missing something that I can't seem to see. I
> have
> >site docs but nothing is in them.
> >
> >-- Lee Meador
> >Sent from gmail. My real email address is [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >No virus found in this incoming message.
> >Checked by AVG Free Edition.
> >Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date:
> 12/21/2005
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

Re: [m2] Artifact relocations and scope priorities

[Carlos Sanchez]

You can probably exclude jspapi in acegi

1.0.0-RC1 has the right dependencies

On 12/27/05, Yann Le Du <[EMAIL PROTECTED]> wrote:
> Hi,
> I noticed something potentially confusing with artifact relocations.
>
> Say I want to declare a 'provided' jsp-api 2.0 dependency :
> ~ javax.servlet
> ~ jsp-api
> ~ 2.0
> ~ provided
>
> I also have a dependency upon acegi-security 0.8.2, which in turn
> unfortunately depends on jsp-api in the "old way" :
> ~ jspapi
> ~ jsp-api
> ~ 2.0
>
> The result is that jsp-api-2.0.jar is included as a compile dependency.
> Of course, I could (and will) send a patch for acegi-security, but this can
> happen on any other dependency - and I won't catch it.
> The only secure workaround I have found is to dup the dependency - not very
> elegant :
> ~   
> ~ javax.servlet
> ~ jsp-api
> ~ 2.0
> ~ provided
> ~   
> ~   
> ~ jspapi
> ~ jsp-api
> ~ 2.0
> ~ provided
> ~   
>
> Thoughts ?
> --
> Yann
>
>

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

[m2] Artifact relocations and scope priorities

[Yann Le Du]

Hi,
I noticed something potentially confusing with artifact relocations.

Say I want to declare a 'provided' jsp-api 2.0 dependency :
~ javax.servlet
~ jsp-api
~ 2.0
~ provided

I also have a dependency upon acegi-security 0.8.2, which in turn
unfortunately depends on jsp-api in the "old way" :
~ jspapi
~ jsp-api
~ 2.0

The result is that jsp-api-2.0.jar is included as a compile dependency.
Of course, I could (and will) send a patch for acegi-security, but this can
happen on any other dependency - and I won't catch it.
The only secure workaround I have found is to dup the dependency - not very
elegant :
~   
~ javax.servlet
~ jsp-api
~ 2.0
~ provided
~   
~   
~ jspapi
~ jsp-api
~ 2.0
~ provided
~   

Thoughts ?
--
Yann

SV: LOTS of dependencies just not found

[Bengt-Erik Fröberg]

Wrote an issue to maven-repository-plugin-JIRA.
I don't think you should be allowed to publish to repository if dependencies
of the stuff you're publishing does not exist.

Regards,






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

Re: maven-jetty6-plugin

[Chris Richardson]

Hi,

When I try running jetty6:run I get this error, which seems to be related to
log4j.
Any suggestions?

Thanks.

Chris

[DEBUG] Trace
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(
NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(
WebXmlConfiguration.java:553)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(
WebXmlConfiguration.java:345)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(
WebXmlConfiguration.java:267)
at org.mortbay.jetty.plugin.JettyMavenConfiguration.configureWebApp(
JettyMavenConfiguration.java:114)
at org.mortbay.jetty.webapp.WebAppContext.startContext(
WebAppContext.java:781)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java
:345)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java
:209)
at org.mortbay.thread.AbstractLifeCycle.start(AbstractLifeCycle.java:37)
at org.mortbay.jetty.handler.HandlerCollection.doStart(
HandlerCollection.java:90)
at org.mortbay.jetty.Server.doStart(Server.java:138)
at org.mortbay.thread.AbstractLifeCycle.start(AbstractLifeCycle.java:37)
at org.mortbay.jetty.plugin.JettyMojo.startJetty(JettyMojo.java:424)
at org.mortbay.jetty.plugin.JettyMojo.execute(JettyMojo.java:370)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:432)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:530)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
DefaultLifecycleExecutor.java:485)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:455)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java: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)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: No suitable Log
constructor [Ljava.lang.Class;@1cda59b for
org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
LogFactoryImpl.java:532)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
LogFactoryImpl.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at org.acegisecurity.ui.session.HttpSessionEventPublisher.(
HttpSessionEventPublisher.java:50)
... 37 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable
Log constructor [Ljava.lang.Class;@1cda59b for
org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(
LogFactoryImpl.java:432)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
LogFactoryImpl.java:525)
... 41 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
at java.lang.Class.getConstructor0(Class.java:2640)
at java.lang.Class.getConstructor(Class.java:1629)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(
LogFactoryImpl.java:429)
... 42 more
[INFO]

[INFO] Total time: 13 seconds
[INFO] Finished at: Tue Dec 27 08:04:04 PST 2005
[INFO] Final Memory: 5M/9M
[INFO]

Re: Support for mojos written in Ant

[Nitko2]

Ok, that's it. I just didn't find anything(in JIRA issue) about getting 
included in the release.

Thanks.

Brett Porter wrote:

On 12/24/05, Chris Berry <[EMAIL PROTECTED]> wrote:


FWIW, what I've done is create a specialized Mojo that allows you to create
an Ant build.xml and then build a reusable Mojo that use it. I submitted
this into JIRA, but don't know if its been integrated yet. You can get the
code here (its attached to the Issue)...
http://jira.codehaus.org/browse/MNG-897
BTW: this code illustrates using Ant form Java...



That's exactly what it is. Looks like the issue was not closed.

- Brett

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

SV: LOTS of dependencies just not found

[Bengt-Erik Fröberg]

Great.
So I can exclude the dependencies of my dependencies.
That'll do it!

Regards,

-Ursprungligt meddelande-
Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Carlos Sanchez
Skickat: den 27 december 2005 16:35
Till: Maven Users List
Ämne: Re: LOTS of dependencies just not found

You can exclude dependencies by yourself using 
Faulty poms are automatically ignored

On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> Hi
>
> I actually would prefer that dependencies with incomplete and faulty POMs
> be discarded.
> Because today all I get is messages on errors and warnings, and there is
not
> a thing I can do to correct them myself. Spending the minutes that remains
> of the workday when all the other fixing and trixing around maven
publishing
> issues on a JIRA well, I have to check if that is OK with my employer
;)
> Better to get a message: "Sorry, the dependency you are requesting has
> an incomplete or non-valid POM. Choose another version"
>
> Regards,
>
>
> -Ursprungligt meddelande-
> Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Carlos Sanchez
> Skickat: den 27 december 2005 16:18
> Till: Maven Users List
> Ämne: Re: LOTS of dependencies just not found
>
> Well, we could prevent the upload of some artifacts whose dependencies
> are not available, but then you would complain about them being
> missing, it's a matter of taste.
>
> Some pointers:
> http://maven.apache.org/guides/mini/guide-maven-evangelism.html
> http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
> http://jira.codehaus.org/browse/MNG-1689
>
>
> On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> > Trying to introduce Maven2 (2.0.1) in my organization, the idea is
great,
> > but alas I find
> > the practice to be somewhat dissatisfying.
> >
> > Trace of a perfectly normal use-case below. POM is very simple with a
few
> > dependencies,
> > but still the number of 'WARNING', 'relocated' and 'missing' is far too
> high
> > for me to
> > dare present it for my fellow programmers.
> >
> > What can you do about this?
> > Should I abandon Maven2 as a tool entirely or just wait for it to
mature?
> > I really need advice on this, because right now it feels as if I'm
> spending
> > most effort in manually installing missing libraries and dependencies
and
> > trying to resolve things that just should work. Out of the box.
> >
> > You probably can argue that the dependencies and POMs are the
> responsibility
> > of the ones publishing their work at ibiblio. True.
> > But if they can't handle it, well then there's has to be some kind of
> > control or validation of the poms to ensure the 'dependencies of the
> > dependencies' really exist. Because if this goes on, I won't be the only
> one
> > to doubt the usability of Maven2
> >
> > Regards,
> >
> > /C
> >
> >
> >
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'eclipse'.
> > [INFO]
> >
>

> > [INFO] Building Maven Webapp Archetype
> > [INFO]task-segment: [eclipse:eclipse]
> > [INFO]
> >
>

> > [INFO] Preparing eclipse:eclipse
> > [INFO] No goals needed for project - skipping
> > Downloading:
> > http://repo1.maven.org/maven2/asn1-ber/asn1-codec/0.3/asn1-codec-0.3.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > [WARNING] While downloading servletapi:servletapi:2.3
> >   This artifact has been relocated to javax.servlet:servlet-api:2.3.
> >
> >
> > [WARNING] While downloading jcifs:jcifs:1.2.6
> >   This artifact has been relocated to org.samba.jcifs:jcifs:1.2.6.
> >
> >
> > [WARNING] POM for 'springframework:spring-mock:pom:1.2.5' is invalid. It
> > will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> > Downloading:
> >
>
http://repo1.maven.org/maven2/xdoclet-plugins/xdoclet-plugin-qtags/${pom.cur
> > rentVersion}/xdoclet-plugin-qtags-${pom.currentVersion}.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > Downloading:
> >
>
http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
> > 4207.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > [WARNING] While downloading servletapi:servletapi:2.3
> >   This artifact has been relocated to javax.servlet:servlet-api:2.3.
> >
> >
> > [WARNING] While downloading jstl:jstl:1.0.6
> >   This artifact has been relocated to javax.servlet:jstl:1.0.6.
> >
> >
> > Downloading:
> >
>
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1
> > .pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > Downloading:
> >
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
> > [WARNING] Unable to get resource from repository c

Re: LOTS of dependencies just not found

[Carlos Sanchez]

You can exclude dependencies by yourself using 
Faulty poms are automatically ignored

On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> Hi
>
> I actually would prefer that dependencies with incomplete and faulty POMs
> be discarded.
> Because today all I get is messages on errors and warnings, and there is not
> a thing I can do to correct them myself. Spending the minutes that remains
> of the workday when all the other fixing and trixing around maven publishing
> issues on a JIRA well, I have to check if that is OK with my employer ;)
> Better to get a message: "Sorry, the dependency you are requesting has
> an incomplete or non-valid POM. Choose another version"
>
> Regards,
>
>
> -Ursprungligt meddelande-
> Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Carlos Sanchez
> Skickat: den 27 december 2005 16:18
> Till: Maven Users List
> Ämne: Re: LOTS of dependencies just not found
>
> Well, we could prevent the upload of some artifacts whose dependencies
> are not available, but then you would complain about them being
> missing, it's a matter of taste.
>
> Some pointers:
> http://maven.apache.org/guides/mini/guide-maven-evangelism.html
> http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
> http://jira.codehaus.org/browse/MNG-1689
>
>
> On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> > Trying to introduce Maven2 (2.0.1) in my organization, the idea is great,
> > but alas I find
> > the practice to be somewhat dissatisfying.
> >
> > Trace of a perfectly normal use-case below. POM is very simple with a few
> > dependencies,
> > but still the number of 'WARNING', 'relocated' and 'missing' is far too
> high
> > for me to
> > dare present it for my fellow programmers.
> >
> > What can you do about this?
> > Should I abandon Maven2 as a tool entirely or just wait for it to mature?
> > I really need advice on this, because right now it feels as if I'm
> spending
> > most effort in manually installing missing libraries and dependencies and
> > trying to resolve things that just should work. Out of the box.
> >
> > You probably can argue that the dependencies and POMs are the
> responsibility
> > of the ones publishing their work at ibiblio. True.
> > But if they can't handle it, well then there's has to be some kind of
> > control or validation of the poms to ensure the 'dependencies of the
> > dependencies' really exist. Because if this goes on, I won't be the only
> one
> > to doubt the usability of Maven2
> >
> > Regards,
> >
> > /C
> >
> >
> >
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'eclipse'.
> > [INFO]
> >
> 
> > [INFO] Building Maven Webapp Archetype
> > [INFO]task-segment: [eclipse:eclipse]
> > [INFO]
> >
> 
> > [INFO] Preparing eclipse:eclipse
> > [INFO] No goals needed for project - skipping
> > Downloading:
> > http://repo1.maven.org/maven2/asn1-ber/asn1-codec/0.3/asn1-codec-0.3.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > [WARNING] While downloading servletapi:servletapi:2.3
> >   This artifact has been relocated to javax.servlet:servlet-api:2.3.
> >
> >
> > [WARNING] While downloading jcifs:jcifs:1.2.6
> >   This artifact has been relocated to org.samba.jcifs:jcifs:1.2.6.
> >
> >
> > [WARNING] POM for 'springframework:spring-mock:pom:1.2.5' is invalid. It
> > will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> > Downloading:
> >
> http://repo1.maven.org/maven2/xdoclet-plugins/xdoclet-plugin-qtags/${pom.cur
> > rentVersion}/xdoclet-plugin-qtags-${pom.currentVersion}.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > Downloading:
> >
> http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
> > 4207.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > [WARNING] While downloading servletapi:servletapi:2.3
> >   This artifact has been relocated to javax.servlet:servlet-api:2.3.
> >
> >
> > [WARNING] While downloading jstl:jstl:1.0.6
> >   This artifact has been relocated to javax.servlet:jstl:1.0.6.
> >
> >
> > Downloading:
> >
> http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1
> > .pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > Downloading:
> > http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
> > [WARNING] While downloading xml-apis:xml-apis:2.0.2
> >   This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
> >
> >
> > [WARNING] While downloading icu4j:icu4j:2.6.1
> >   This artifact has been relocated to com.ibm.icu:icu4j:2.6.1.
> >

SV: LOTS of dependencies just not found

[Bengt-Erik Fröberg]

Hi

I actually would prefer that dependencies with incomplete and faulty POMs
be discarded.
Because today all I get is messages on errors and warnings, and there is not
a thing I can do to correct them myself. Spending the minutes that remains
of the workday when all the other fixing and trixing around maven publishing
issues on a JIRA well, I have to check if that is OK with my employer ;)
Better to get a message: "Sorry, the dependency you are requesting has 
an incomplete or non-valid POM. Choose another version"

Regards,


-Ursprungligt meddelande-
Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Carlos Sanchez
Skickat: den 27 december 2005 16:18
Till: Maven Users List
Ämne: Re: LOTS of dependencies just not found

Well, we could prevent the upload of some artifacts whose dependencies
are not available, but then you would complain about them being
missing, it's a matter of taste.

Some pointers:
http://maven.apache.org/guides/mini/guide-maven-evangelism.html
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
http://jira.codehaus.org/browse/MNG-1689


On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> Trying to introduce Maven2 (2.0.1) in my organization, the idea is great,
> but alas I find
> the practice to be somewhat dissatisfying.
>
> Trace of a perfectly normal use-case below. POM is very simple with a few
> dependencies,
> but still the number of 'WARNING', 'relocated' and 'missing' is far too
high
> for me to
> dare present it for my fellow programmers.
>
> What can you do about this?
> Should I abandon Maven2 as a tool entirely or just wait for it to mature?
> I really need advice on this, because right now it feels as if I'm
spending
> most effort in manually installing missing libraries and dependencies and
> trying to resolve things that just should work. Out of the box.
>
> You probably can argue that the dependencies and POMs are the
responsibility
> of the ones publishing their work at ibiblio. True.
> But if they can't handle it, well then there's has to be some kind of
> control or validation of the poms to ensure the 'dependencies of the
> dependencies' really exist. Because if this goes on, I won't be the only
one
> to doubt the usability of Maven2
>
> Regards,
>
> /C
>
>
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO]
>

> [INFO] Building Maven Webapp Archetype
> [INFO]task-segment: [eclipse:eclipse]
> [INFO]
>

> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> Downloading:
> http://repo1.maven.org/maven2/asn1-ber/asn1-codec/0.3/asn1-codec-0.3.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading servletapi:servletapi:2.3
>   This artifact has been relocated to javax.servlet:servlet-api:2.3.
>
>
> [WARNING] While downloading jcifs:jcifs:1.2.6
>   This artifact has been relocated to org.samba.jcifs:jcifs:1.2.6.
>
>
> [WARNING] POM for 'springframework:spring-mock:pom:1.2.5' is invalid. It
> will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> Downloading:
>
http://repo1.maven.org/maven2/xdoclet-plugins/xdoclet-plugin-qtags/${pom.cur
> rentVersion}/xdoclet-plugin-qtags-${pom.currentVersion}.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> Downloading:
>
http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
> 4207.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading servletapi:servletapi:2.3
>   This artifact has been relocated to javax.servlet:servlet-api:2.3.
>
>
> [WARNING] While downloading jstl:jstl:1.0.6
>   This artifact has been relocated to javax.servlet:jstl:1.0.6.
>
>
> Downloading:
>
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1
> .pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading xml-apis:xml-apis:2.0.2
>   This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
>
>
> [WARNING] While downloading icu4j:icu4j:2.6.1
>   This artifact has been relocated to com.ibm.icu:icu4j:2.6.1.
>
>
> [WARNING] While downloading servletapi:servletapi:2.4
>   This artifact has been relocated to javax.servlet:servlet-api:2.4.
>
>
> [WARNING] While downloading tagsoup:tagsoup:0.9.7
>   This artifact has been relocated to
org.ccil.cowan.tagsoup:tagsoup:0.9.7.
>
>
> [WARNING] POM for 'picocontainer:picocontainer:pom:1.0' is invalid. It
will
> be ignored for artifact resolution. Reason: 

Re: LOTS of dependencies just not found

[Carlos Sanchez]

Well, we could prevent the upload of some artifacts whose dependencies
are not available, but then you would complain about them being
missing, it's a matter of taste.

Some pointers:
http://maven.apache.org/guides/mini/guide-maven-evangelism.html
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
http://jira.codehaus.org/browse/MNG-1689


On 12/27/05, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote:
> Trying to introduce Maven2 (2.0.1) in my organization, the idea is great,
> but alas I find
> the practice to be somewhat dissatisfying.
>
> Trace of a perfectly normal use-case below. POM is very simple with a few
> dependencies,
> but still the number of 'WARNING', 'relocated' and 'missing' is far too high
> for me to
> dare present it for my fellow programmers.
>
> What can you do about this?
> Should I abandon Maven2 as a tool entirely or just wait for it to mature?
> I really need advice on this, because right now it feels as if I'm spending
> most effort in manually installing missing libraries and dependencies and
> trying to resolve things that just should work. Out of the box.
>
> You probably can argue that the dependencies and POMs are the responsibility
> of the ones publishing their work at ibiblio. True.
> But if they can't handle it, well then there's has to be some kind of
> control or validation of the poms to ensure the 'dependencies of the
> dependencies' really exist. Because if this goes on, I won't be the only one
> to doubt the usability of Maven2
>
> Regards,
>
> /C
>
>
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO]
> 
> [INFO] Building Maven Webapp Archetype
> [INFO]task-segment: [eclipse:eclipse]
> [INFO]
> 
> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> Downloading:
> http://repo1.maven.org/maven2/asn1-ber/asn1-codec/0.3/asn1-codec-0.3.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading servletapi:servletapi:2.3
>   This artifact has been relocated to javax.servlet:servlet-api:2.3.
>
>
> [WARNING] While downloading jcifs:jcifs:1.2.6
>   This artifact has been relocated to org.samba.jcifs:jcifs:1.2.6.
>
>
> [WARNING] POM for 'springframework:spring-mock:pom:1.2.5' is invalid. It
> will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> Downloading:
> http://repo1.maven.org/maven2/xdoclet-plugins/xdoclet-plugin-qtags/${pom.cur
> rentVersion}/xdoclet-plugin-qtags-${pom.currentVersion}.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
> 4207.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading servletapi:servletapi:2.3
>   This artifact has been relocated to javax.servlet:servlet-api:2.3.
>
>
> [WARNING] While downloading jstl:jstl:1.0.6
>   This artifact has been relocated to javax.servlet:jstl:1.0.6.
>
>
> Downloading:
> http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1
> .pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [WARNING] While downloading xml-apis:xml-apis:2.0.2
>   This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
>
>
> [WARNING] While downloading icu4j:icu4j:2.6.1
>   This artifact has been relocated to com.ibm.icu:icu4j:2.6.1.
>
>
> [WARNING] While downloading servletapi:servletapi:2.4
>   This artifact has been relocated to javax.servlet:servlet-api:2.4.
>
>
> [WARNING] While downloading tagsoup:tagsoup:0.9.7
>   This artifact has been relocated to org.ccil.cowan.tagsoup:tagsoup:0.9.7.
>
>
> [WARNING] POM for 'picocontainer:picocontainer:pom:1.0' is invalid. It will
> be ignored for artifact resolution. Reason: Parse error reading POM. Reason:
> expected START_TAG or END_TAG not TEXT (position: TEXT seen ...\n
> http://codehaus.org/codehaus-small.gif [WARNING] POM for 'dom4j:dom4j:pom:1.4-dev-8' is invalid. It will be ignored
> for artifact resolution. Reason: Parse error reading POM. Reason: TEXT must
> be immediately followed by END_TAG and not START_TAG (position: START_TAG
> seen ...junit... @47:36)
> Downloading:
> http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-04/groovy-all-1.0-js
> r-04.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/xpp3/xpp3/1.1.3.4-RC8_min/xpp3-1.1.3.4-RC8_min
> .pom
> [WARNING] Unable to get resource from reposito

LOTS of dependencies just not found

[Bengt-Erik Fröberg]

Trying to introduce Maven2 (2.0.1) in my organization, the idea is great,
but alas I find 
the practice to be somewhat dissatisfying.

Trace of a perfectly normal use-case below. POM is very simple with a few
dependencies,
but still the number of 'WARNING', 'relocated' and 'missing' is far too high
for me to
dare present it for my fellow programmers.

What can you do about this?
Should I abandon Maven2 as a tool entirely or just wait for it to mature?
I really need advice on this, because right now it feels as if I'm spending 
most effort in manually installing missing libraries and dependencies and
trying to resolve things that just should work. Out of the box.

You probably can argue that the dependencies and POMs are the responsibility
of the ones publishing their work at ibiblio. True.
But if they can't handle it, well then there's has to be some kind of
control or validation of the poms to ensure the 'dependencies of the
dependencies' really exist. Because if this goes on, I won't be the only one
to doubt the usability of Maven2

Regards,

/C 
 


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

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

[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
Downloading:
http://repo1.maven.org/maven2/asn1-ber/asn1-codec/0.3/asn1-codec-0.3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING] While downloading servletapi:servletapi:2.3
  This artifact has been relocated to javax.servlet:servlet-api:2.3.


[WARNING] While downloading jcifs:jcifs:1.2.6
  This artifact has been relocated to org.samba.jcifs:jcifs:1.2.6.


[WARNING] POM for 'springframework:spring-mock:pom:1.2.5' is invalid. It
will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Downloading:
http://repo1.maven.org/maven2/xdoclet-plugins/xdoclet-plugin-qtags/${pom.cur
rentVersion}/xdoclet-plugin-qtags-${pom.currentVersion}.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
4207.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING] While downloading servletapi:servletapi:2.3
  This artifact has been relocated to javax.servlet:servlet-api:2.3.


[WARNING] While downloading jstl:jstl:1.0.6
  This artifact has been relocated to javax.servlet:jstl:1.0.6.


Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1
.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING] While downloading xml-apis:xml-apis:2.0.2
  This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


[WARNING] While downloading icu4j:icu4j:2.6.1
  This artifact has been relocated to com.ibm.icu:icu4j:2.6.1.


[WARNING] While downloading servletapi:servletapi:2.4
  This artifact has been relocated to javax.servlet:servlet-api:2.4.


[WARNING] While downloading tagsoup:tagsoup:0.9.7
  This artifact has been relocated to org.ccil.cowan.tagsoup:tagsoup:0.9.7.


[WARNING] POM for 'picocontainer:picocontainer:pom:1.0' is invalid. It will
be ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...\n
http://codehaus.org/codehaus-small.gifjunit... @47:36) 
Downloading:
http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-04/groovy-all-1.0-js
r-04.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.3.4-RC8_min/xpp3-1.1.3.4-RC8_min
.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING] POM for 'picocontainer:picocontainer:pom:1.0' is invalid. It will
be ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...\n
http://codehaus.org/codehaus-small.gifhttp://repo1.maven.org/maven2/freemarker/freemarker/2.3/freemarker-2.3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/generama/qdox/20051211.114207/qdox-20051211.11
4207.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.3.4-RC8_min/xpp3-1.1.3.4-RC8_min
.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloa

Re: maven-jetty6-plugin

[Koen Maes]

ok I see : suspend=n to start without waiting for the debugger.

On Tuesday 27 December 2005 10:36, Rolf Strijdhorst wrote:
> yes, there is just start maven with:
> jetty6:run
> but have in the environment tap of externaltools
> a variable MAVEN_OPTS with content: -Xdebug -Xnoagent
> -Djava.compiler=NONE-Xrunjdwp:transport=dt_socket,server=y,suspend=y,addres
>s=4000
>
> next run debug on port 4000 or the same portnumber as the address property
> on the line above
> if you also specify that the debugger is able to terminate the jvm then you
> can reuse the debug session the next time you start jetty.
>
> Rolf
>
> On 12/26/05, Koen Maes <[EMAIL PROTECTED]> wrote:
> > maven jetty plugin works great but i would like to debug my webapp via
> > eclipse
> > is there any option - like tomcat : catalina.sh jpda start - to tell
> > jetty that it should open up a JPDA port so I can connect with eclipse
> > remote debugger ?
> >
> >
> > -
> > 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] best practices: cvs, modules, dependency

[Luiz Eduardo Guida Valmont]

From what I understood, there are the two subpackages and the 
application itself depending on them, right?


So, based on this assumption, I sugest you create three modules in a 
single CVS repository: one for each of the subpackages and the third for 
the application itself; each will have its own pom.xml (beacause each is 
a project on its own right). Mind that the application will have bo be 
configured to use the dep's.


Once you install the generated jar (with "mvn install") from the 
subpackages into your local repository (which is, for example, 
$HOME/.m2/repository on *NIX systems), you can proceed to compile the 
application with "mvn compile". If you were developping this project on 
your own, that'd be the end of the story. As you're probably not...


You can setup a central maven repository and (in a timely and organised 
fashion) upload the generated jars to that central repository. One 
developping the app will have to checkout only the application code. 
That has the added benefit that if, for example, I'm developping one of 
the subpackages, you're developing the application and I accidentaly 
intoduce a bug in the subpackage, you won't ge affected at all (provided 
I did not upload the "buggy" jar).


NOTE: If the subpackage gets installed at 
$HOME/.m2/repository/dirA/dirB/1.0, its configuration as a dependency 
would look like:


> 
> dirA
> dirB
> 1.0
> 

--
Sincerely,
Luiz Eduardo

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

Reoccurring problem with library

[Bengt-Erik Fröberg]

Hi

I keep getting this rather obscure-named library as a dependency.
Why can't it's creators put it I Maven2 scope to download as a normal
dependency?



Project ID: asn1-ber:asn1-codec

Reason: Error getting POM for 'asn1-ber:asn1-codec' from the repository:
Error transferring file
  asn1-ber:asn1-codec:pom:0.3

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



The package is placed here:

http://www.ibiblio.org/pub/packages/maven2/directory-asn1/asn1-codec/

Why? Why? Why?

I'm getting just a little fed up with finding and manually installing this
apparently
crucial library.

Anyone know why it is not published?

Regards,

/B-E
 
==
Bengt-Erik Fröberg, Databasadministratör
Institutionen för Epidemiologi och Biostatistik (MEB)
Karolinska Institutet
Box 281
171 77 Stockholm
Tel: (08)-524 823 76
Internet: http://www.meb.ki.se/




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

Re: About the "package" goal

[Luiz Eduardo Guida Valmont]

http://jira.codehaus.org/browse/MASSEMBLY-1?rc=1

There's an issue still open at codehaus. It's precisely what I wrote in 
the previous e-mail. Guess I'll have to stick around with:


$ java -cp target/classes:target/assembly/work/log4j-1.2.12 
br.ufrj.ad.Trabalho


For the time being.

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

Re: maven-jetty6-plugin

[Koen Maes]

Ok, took me some time but it works.
The startup of jetty seems to wait for the debugger to connect before 
resuming. 

many thx for the tip.

rgds,

koen

On Tuesday 27 December 2005 10:36, Rolf Strijdhorst wrote:
> yes, there is just start maven with:
> jetty6:run
> but have in the environment tap of externaltools
> a variable MAVEN_OPTS with content: -Xdebug -Xnoagent
> -Djava.compiler=NONE-Xrunjdwp:transport=dt_socket,server=y,suspend=y,addres
>s=4000
>
> next run debug on port 4000 or the same portnumber as the address property
> on the line above
> if you also specify that the debugger is able to terminate the jvm then you
> can reuse the debug session the next time you start jetty.
>
> Rolf
>
> On 12/26/05, Koen Maes <[EMAIL PROTECTED]> wrote:
> > maven jetty plugin works great but i would like to debug my webapp via
> > eclipse
> > is there any option - like tomcat : catalina.sh jpda start - to tell
> > jetty that it should open up a JPDA port so I can connect with eclipse
> > remote debugger ?
> >
> >
> > -
> > 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: About the "package" goal

[Luiz Eduardo Guida Valmont]

Look at the assembly plugin.
 

That went a long way towards what I really wanted. The only catch is 
that by using the default descriptor "jar-with-dependencies" the 
MANIFEST.MF that I used to have (as generated by the maven-jar-plugin 
plugin) vanished. I mean, it does not get packed in the jar and I cannot 
run it like:


java -jar someFile-jar-with-dependencies.jar

Wich is precisely what I want. Do you know how I can solve that problem?

But nonetheless I think I'm on the way.

Thanks again,
Luiz Eduardo

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

Re: [m2] best practices: cvs, modules, dependency

[Yann Le Du]

At first view, what you could do is :
  * create a parent POM for your application
  * create a module for each component
  * create a pom.xml for each component

I see no need to setup several internal repositories.

For an example, you could have a look at how it's done in Maven itself :
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/

Hope this helps,
--
Yann

2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
>
> Hello,
> we are developing 2 components. at this moment, they are subpackages of
> the
> same application, stored in one single cvs repository.
> also, they share a big ant build file.
>
> we want to split them into independant projects, and take advantage of
> maven
> .
>
> so, what is the best way to approach the problem?:
> -create 2 modules on the same cvs repository ?
> -create 2 independendant pom.xml and if necessary define one to be
> dependant
> from the other one ?
> --to do so, should I setup 2 internal maven repositories ?
> -if we want to package the 2 components toghether, shoudl we create a
> third
> "global" pom, that includes both of the previous ones?
> -are there any guidelines about setting up this kind of things?
>
> is there any issue i should consider first ? what is, in your opinion, the
> best way (or, a good working way) to approach this situation?
>
> thanks,
> valerio
>
> --
> To Iterate is Human, to Recurse, Divine
> James O. Coplien, Bell Labs
>
>

Re: [m2] Setting up m2 internal repository

[Yann Le Du]

To specify the repository where Maven will deploy your artifact to, use
 :
http://maven.apache.org/maven-model/maven.html#class_distributionManagement

Hope this helps,
--
Yann

2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
>
> hello Wim,
>
> 2005/12/27, Wim Deblauwe <[EMAIL PROTECTED]>:
> >
> > 'mvn install' copies your artifact (e.g. a jar or war or ...) to your
> > local
> > repository, along with the additional files.
>
>
> this step  sounds good.
>
> 'mvn deploy' copies it to the remote repository (normally a server in your
> > company)
>
>
> this one is less clear to me: how can maven know where to copy it ?
> i mean: how do I specify to which repository maven will deploy it ?
>
> thanks for the help,
> valerio
>
> regards,
> >
> > Wim
> >
> > 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> > >
> > > Hello Yann,
> > > ok, so I should follow that example. question: who is in charge to
> > create
> > > the directory structure into http://mycompany/maven2/ directory ?
> > > that is, say my application i want to share is called 'acme',
> > > then, i'm expecting to found a repository at this path:
> > >
> > > http://mycompany/maven2/acme/
> > >
> > > than, inside this path, a new directory called acme should be found,
> > like
> > > this:
> > > http://mycompany/maven2/acme/acme
> > >
> > > which should contains files like this:
> > > maven-metadata.xml
> > > maven-metadata.xml.md5
> > > maven-metadata.xml.sha1
> > >
> > > who is in charge to produce those files?
> > > then, for every release (i suppose) there should be a directory (named
> > by
> > > the revision number of the release) which contains a jar file, the
> > digital
> > > signatures, a pom file, and another maven-metadata.xml file.
> > > how can I automate the production of this stuff?
> > > is there any predefined goal to "publish" a release on an internal
> > > repository ?
> > >
> > > the example about "Deploying to the Internal Repository"  is sadly
> > > empty...
> > >
> > > thanks,
> > > valerio
> > >
> > >
> > > 2005/12/27, Yann Le Du <[EMAIL PROTECTED]>:
> > > >
> > > > Hi Valerio,
> > > >
> > > > Actually the Maven 2 central repository is :
> > > > http://www.ibiblio.org/maven2/
> > > > (with a '2')
> > > >
> > > > --
> > > > Yann
> > > >
> > > > 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> > > > >
> > > > > Hello,
> > > > > i'm willing to set-up an internal repository. we're just
> > starting  up
> > > > with
> > > > > maven 2.x , and i found these infos:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
> > > > >
> > > > > i didn't understand if they also refer to m2. In particular, when
> it
> > > is
> > > > > suggested to follow the example on ibiblio, looking at
> > > > > http://www.ibiblio.org/maven/ this look like a maven 1.xrepository.
> > > > >
> > > > > So, which artifacts should be stored there ? How can I safely
> setup
> > > this
> > > > > repo?
> > > > >
> > > > > thanks,
> > > > > valerio
> > > > >
> > > > > --
> > > > > To Iterate is Human, to Recurse, Divine
> > > > > James O. Coplien, Bell Labs
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > To Iterate is Human, to Recurse, Divine
> > > James O. Coplien, Bell Labs
> > >
> > >
> >
> >
>
>
> --
> To Iterate is Human, to Recurse, Divine
> James O. Coplien, Bell Labs
>
>

Re: [m2] Setting up m2 internal repository

[Valerio Schiavoni]

hello Wim,

2005/12/27, Wim Deblauwe <[EMAIL PROTECTED]>:
>
> 'mvn install' copies your artifact (e.g. a jar or war or ...) to your
> local
> repository, along with the additional files.


this step  sounds good.

'mvn deploy' copies it to the remote repository (normally a server in your
> company)


this one is less clear to me: how can maven know where to copy it ?
i mean: how do I specify to which repository maven will deploy it ?

thanks for the help,
valerio

regards,
>
> Wim
>
> 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> >
> > Hello Yann,
> > ok, so I should follow that example. question: who is in charge to
> create
> > the directory structure into http://mycompany/maven2/ directory ?
> > that is, say my application i want to share is called 'acme',
> > then, i'm expecting to found a repository at this path:
> >
> > http://mycompany/maven2/acme/
> >
> > than, inside this path, a new directory called acme should be found,
> like
> > this:
> > http://mycompany/maven2/acme/acme
> >
> > which should contains files like this:
> > maven-metadata.xml
> > maven-metadata.xml.md5
> > maven-metadata.xml.sha1
> >
> > who is in charge to produce those files?
> > then, for every release (i suppose) there should be a directory (named
> by
> > the revision number of the release) which contains a jar file, the
> digital
> > signatures, a pom file, and another maven-metadata.xml file.
> > how can I automate the production of this stuff?
> > is there any predefined goal to "publish" a release on an internal
> > repository ?
> >
> > the example about "Deploying to the Internal Repository"  is sadly
> > empty...
> >
> > thanks,
> > valerio
> >
> >
> > 2005/12/27, Yann Le Du <[EMAIL PROTECTED]>:
> > >
> > > Hi Valerio,
> > >
> > > Actually the Maven 2 central repository is :
> > > http://www.ibiblio.org/maven2/
> > > (with a '2')
> > >
> > > --
> > > Yann
> > >
> > > 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> > > >
> > > > Hello,
> > > > i'm willing to set-up an internal repository. we're just
> starting  up
> > > with
> > > > maven 2.x , and i found these infos:
> > > >
> > > >
> > > >
> > >
> >
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
> > > >
> > > > i didn't understand if they also refer to m2. In particular, when it
> > is
> > > > suggested to follow the example on ibiblio, looking at
> > > > http://www.ibiblio.org/maven/ this look like a maven 1.x repository.
> > > >
> > > > So, which artifacts should be stored there ? How can I safely setup
> > this
> > > > repo?
> > > >
> > > > thanks,
> > > > valerio
> > > >
> > > > --
> > > > To Iterate is Human, to Recurse, Divine
> > > > James O. Coplien, Bell Labs
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > To Iterate is Human, to Recurse, Divine
> > James O. Coplien, Bell Labs
> >
> >
>
>


--
To Iterate is Human, to Recurse, Divine
James O. Coplien, Bell Labs

Re: [m2] Setting up m2 internal repository

[Wim Deblauwe]

'mvn install' copies your artifact (e.g. a jar or war or ...) to your local
repository, along with the additional files.

'mvn deploy' copies it to the remote repository (normally a server in your
company)

regards,

Wim

2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
>
> Hello Yann,
> ok, so I should follow that example. question: who is in charge to create
> the directory structure into http://mycompany/maven2/ directory ?
> that is, say my application i want to share is called 'acme',
> then, i'm expecting to found a repository at this path:
>
> http://mycompany/maven2/acme/
>
> than, inside this path, a new directory called acme should be found, like
> this:
> http://mycompany/maven2/acme/acme
>
> which should contains files like this:
> maven-metadata.xml
> maven-metadata.xml.md5
> maven-metadata.xml.sha1
>
> who is in charge to produce those files?
> then, for every release (i suppose) there should be a directory (named by
> the revision number of the release) which contains a jar file, the digital
> signatures, a pom file, and another maven-metadata.xml file.
> how can I automate the production of this stuff?
> is there any predefined goal to "publish" a release on an internal
> repository ?
>
> the example about "Deploying to the Internal Repository"  is sadly
> empty...
>
> thanks,
> valerio
>
>
> 2005/12/27, Yann Le Du <[EMAIL PROTECTED]>:
> >
> > Hi Valerio,
> >
> > Actually the Maven 2 central repository is :
> > http://www.ibiblio.org/maven2/
> > (with a '2')
> >
> > --
> > Yann
> >
> > 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> > >
> > > Hello,
> > > i'm willing to set-up an internal repository. we're just starting  up
> > with
> > > maven 2.x , and i found these infos:
> > >
> > >
> > >
> >
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
> > >
> > > i didn't understand if they also refer to m2. In particular, when it
> is
> > > suggested to follow the example on ibiblio, looking at
> > > http://www.ibiblio.org/maven/ this look like a maven 1.x repository.
> > >
> > > So, which artifacts should be stored there ? How can I safely setup
> this
> > > repo?
> > >
> > > thanks,
> > > valerio
> > >
> > > --
> > > To Iterate is Human, to Recurse, Divine
> > > James O. Coplien, Bell Labs
> > >
> > >
> >
> >
>
>
> --
> To Iterate is Human, to Recurse, Divine
> James O. Coplien, Bell Labs
>
>

Re: [m2] Setting up m2 internal repository

[Valerio Schiavoni]

Hello Yann,
ok, so I should follow that example. question: who is in charge to create
the directory structure into http://mycompany/maven2/ directory ?
that is, say my application i want to share is called 'acme',
then, i'm expecting to found a repository at this path:

http://mycompany/maven2/acme/

than, inside this path, a new directory called acme should be found, like
this:
http://mycompany/maven2/acme/acme

which should contains files like this:
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1

who is in charge to produce those files?
then, for every release (i suppose) there should be a directory (named by
the revision number of the release) which contains a jar file, the digital
signatures, a pom file, and another maven-metadata.xml file.
how can I automate the production of this stuff?
is there any predefined goal to "publish" a release on an internal
repository ?

the example about "Deploying to the Internal Repository"  is sadly empty...

thanks,
valerio


2005/12/27, Yann Le Du <[EMAIL PROTECTED]>:
>
> Hi Valerio,
>
> Actually the Maven 2 central repository is :
> http://www.ibiblio.org/maven2/
> (with a '2')
>
> --
> Yann
>
> 2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
> >
> > Hello,
> > i'm willing to set-up an internal repository. we're just starting  up
> with
> > maven 2.x , and i found these infos:
> >
> >
> >
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
> >
> > i didn't understand if they also refer to m2. In particular, when it is
> > suggested to follow the example on ibiblio, looking at
> > http://www.ibiblio.org/maven/ this look like a maven 1.x repository.
> >
> > So, which artifacts should be stored there ? How can I safely setup this
> > repo?
> >
> > thanks,
> > valerio
> >
> > --
> > To Iterate is Human, to Recurse, Divine
> > James O. Coplien, Bell Labs
> >
> >
>
>


--
To Iterate is Human, to Recurse, Divine
James O. Coplien, Bell Labs

[m2] best practices: cvs, modules, dependency

[Valerio Schiavoni]

Hello,
we are developing 2 components. at this moment, they are subpackages of the
same application, stored in one single cvs repository.
also, they share a big ant build file.

we want to split them into independant projects, and take advantage of maven
.

so, what is the best way to approach the problem?:
-create 2 modules on the same cvs repository ?
-create 2 independendant pom.xml and if necessary define one to be dependant
from the other one ?
--to do so, should I setup 2 internal maven repositories ?
-if we want to package the 2 components toghether, shoudl we create a third
"global" pom, that includes both of the previous ones?
-are there any guidelines about setting up this kind of things?

is there any issue i should consider first ? what is, in your opinion, the
best way (or, a good working way) to approach this situation?

thanks,
valerio

--
To Iterate is Human, to Recurse, Divine
James O. Coplien, Bell Labs

Re: [m2] Setting up m2 internal repository

[Yann Le Du]

Hi Valerio,

Actually the Maven 2 central repository is :
http://www.ibiblio.org/maven2/
(with a '2')

--
Yann

2005/12/27, Valerio Schiavoni <[EMAIL PROTECTED]>:
>
> Hello,
> i'm willing to set-up an internal repository. we're just starting  up with
> maven 2.x , and i found these infos:
>
>
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
>
> i didn't understand if they also refer to m2. In particular, when it is
> suggested to follow the example on ibiblio, looking at
> http://www.ibiblio.org/maven/ this look like a maven 1.x repository.
>
> So, which artifacts should be stored there ? How can I safely setup this
> repo?
>
> thanks,
> valerio
>
> --
> To Iterate is Human, to Recurse, Divine
> James O. Coplien, Bell Labs
>
>

[m2] Setting up m2 internal repository

[Valerio Schiavoni]

Hello,
i'm willing to set-up an internal repository. we're just starting  up with
maven 2.x , and i found these infos:

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

i didn't understand if they also refer to m2. In particular, when it is
suggested to follow the example on ibiblio, looking at
http://www.ibiblio.org/maven/ this look like a maven 1.x repository.

So, which artifacts should be stored there ? How can I safely setup this
repo?

thanks,
valerio

--
To Iterate is Human, to Recurse, Divine
James O. Coplien, Bell Labs

[m2] maven-eclipse-plugin and wtp 1.0

[Srepfler Srgjan]

Will there be any changes to the maven-eclipse-plugin to integrate with 
the WTP 1.0 way of managing j2ee projects?


Cheers

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

Re: maven-jetty6-plugin

[Rolf Strijdhorst]

yes, there is just start maven with:
jetty6:run
but have in the environment tap of externaltools
a variable MAVEN_OPTS with content: -Xdebug -Xnoagent
-Djava.compiler=NONE-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=4000

next run debug on port 4000 or the same portnumber as the address property
on the line above
if you also specify that the debugger is able to terminate the jvm then you
can reuse the debug session the next time you start jetty.

Rolf

On 12/26/05, Koen Maes <[EMAIL PROTECTED]> wrote:
>
> maven jetty plugin works great but i would like to debug my webapp via
> eclipse
> is there any option - like tomcat : catalina.sh jpda start - to tell jetty
> that it should open up a JPDA port so I can connect with eclipse remote
> debugger ?
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: About the "package" goal

[Scokart Gilles]

Look at the assembly plugin.

> -Original Message-
> From: Luiz Eduardo Guida Valmont [mailto:[EMAIL PROTECTED]
> Sent: 27 December 2005 00:33
> To: users@maven.apache.org
> Subject: About the "package" goal
> 
> Hi everyone,
> 
> I'm working on a simple command-line project and it has log4j as one of
> its dep's. As I didn't find (or wasn't able to find, so to say) any
> documentation on the subject, here is my question: how can I package
> log4j along with my project's classes in the jar generated by the
> "package" target? I know how I should setup the main class for the jar,
> but I still cannot package loj4j along.
> 
> I can bundle the lo4j-1.2.12.jar as a resource and that'd be the end of
> it, but that would be far from "elegant" (as I would have to keep track
> of changes in the pom.xml (if I decided to change to log4j-1.3.jar I'd
> have to copy it over).
> 
> Sorry if this is a question of old. I'd appreciate if anyone would just
> point me links that I can follow. ;-)
> 
> Thanks in advance,
> Luiz Eduardo
> 
> -
> 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]