Re: Script/plugin to play sound when maven build finishes?

[Henrique Prange]

Hi John,

The following tutorial shows how to integrate Maven + Growl (Mac OS X program). 
I think you can adapt it to your needs.

http://blank.jasonwhaley.com/2009/02/growl-maven-integration.html

Cheers,

Henrique

On 18/03/2011, at 13:47, John Lussmyer wrote:

> ??? How would a build running on a Server play a sound on my machine when I 
> do a build on my machine?
> I need this for builds I run on my machine BEFORE I check them in.
> 
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com] 
> Sent: Friday, March 18, 2011 9:38 AM
> To: Maven Users List
> Subject: Re: Script/plugin to play sound when maven build finishes?
> 
> Sounds like something I would do using my continuous integration
> server. Look into Hudson/Jenkins and there's probably a plugin to do
> this kind of thing for you.
> 
> Wayne
> 
> On Fri, Mar 18, 2011 at 10:22 AM, John Lussmyer
>  wrote:
>> I'm using Maven on a Fedora system, and it would be REALLY helpful if Maven 
>> would play a sound when a build finished.
>> Anyone have any easy way to do that?
>> (and I am NOT a shell script expert, so please don't say "just write a 
>> script".  If you must say that, please provide the script.)
>> 
>> This message and the information contained herein is proprietary and 
>> confidential and subject to the Amdocs policy statement,
>> you may review at http://www.amdocs.com/email_disclaimer.asp
>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Deploying "Fake" Releases

[Henrique Prange]

Hi Todd,

The more I think about the problem, the more I believe I should 
negotiate a way to straighten the release process of the project, 
instead of warping Maven configuration.


Thank you for your answer.

Cheers,

Henrique

Todd Thiessen wrote:

You could change the POM to point to an SCM you do have access to and
cut a real release.

---
Todd Thiessen
 


-Original Message-
From: Henrique Prange [mailto:hpra...@gmail.com] 
Sent: Monday, March 09, 2009 2:55 PM

To: Maven Users List
Subject: Re: Deploying "Fake" Releases

Hi Kalle,

This is valid if I can't found another solution.

I want to have daily builds of this project producing 
SNAPSHOT versions. 
However, I don't want to store every SNAPSHOT produced. That 
is why I want to make those "fake" releases monthly or 
weekly. I want to store only "fake" releases indefinitely.


Anyway, thanks for your idea.

Cheers,

Henrique

Kalle Korhonen wrote:
Why not use just uniquely versioned snapshots in that case? Even in 
other poms you can refer to unique snapshot version of a 
dependency if 

you so wish.

Kalle


On Mon, Mar 9, 2009 at 7:10 AM, Henrique Prange 

 wrote:

Hello there,

Is there a way to deploy "fake" releases of a project into 

a repository?
I need to make releases based on the SCM revision periodically. 
Something like "my-project-1.0-r". But I can't make 
real releases 

because I don't have privilege to write to the SCM.

I tried the buildnumber-maven-plugin, which works for the binary 
artifacts produced. But it doesn't work for parent pom artifacts. 
This is a problem in a multi-project because an artifact 
my-project-1.0-r will depend on a parent pom 

my-parent-1.0-SNAPSHOT instead of my-parent-1.0-r.
I also took a look at the release:stage goal, but it 
doesn't seem to 

solve my problem.

I appreciate any advice on this subject.

Cheers,

Henrique



-

To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Deploying "Fake" Releases

[Henrique Prange]

Hi Kalle,

This is valid if I can't found another solution.

I want to have daily builds of this project producing SNAPSHOT versions. 
However, I don't want to store every SNAPSHOT produced. That is why I 
want to make those "fake" releases monthly or weekly. I want to store 
only "fake" releases indefinitely.


Anyway, thanks for your idea.

Cheers,

Henrique

Kalle Korhonen wrote:

Why not use just uniquely versioned snapshots in that case? Even in other
poms you can refer to unique snapshot version of a dependency if you so
wish.

Kalle


On Mon, Mar 9, 2009 at 7:10 AM, Henrique Prange  wrote:


Hello there,

Is there a way to deploy "fake" releases of a project into a repository?

I need to make releases based on the SCM revision periodically. Something
like "my-project-1.0-r". But I can't make real releases because I don't
have privilege to write to the SCM.

I tried the buildnumber-maven-plugin, which works for the binary artifacts
produced. But it doesn't work for parent pom artifacts. This is a problem in
a multi-project because an artifact my-project-1.0-r will depend on a
parent pom my-parent-1.0-SNAPSHOT instead of my-parent-1.0-r.

I also took a look at the release:stage goal, but it doesn't seem to solve
my problem.

I appreciate any advice on this subject.

Cheers,

Henrique

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Deploying "Fake" Releases

[Henrique Prange]

Hello there,

Is there a way to deploy "fake" releases of a project into a repository?

I need to make releases based on the SCM revision periodically. 
Something like "my-project-1.0-r". But I can't make real releases 
because I don't have privilege to write to the SCM.


I tried the buildnumber-maven-plugin, which works for the binary 
artifacts produced. But it doesn't work for parent pom artifacts. This 
is a problem in a multi-project because an artifact my-project-1.0-r 
will depend on a parent pom my-parent-1.0-SNAPSHOT instead of 
my-parent-1.0-r.


I also took a look at the release:stage goal, but it doesn't seem to 
solve my problem.


I appreciate any advice on this subject.

Cheers,

Henrique

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [2.0.10 RC6] please test

[Henrique Prange]

Hi Brian,

RC4 also works correctly.

Cheers,

Henrique

Brian E. Fox wrote:

Interesting, what about RC4?

-Original Message-
From: Henrique Prange [mailto:hpra...@gmail.com] 
Sent: Wednesday, December 17, 2008 12:54 PM

To: Maven Developers List
Cc: Maven Users List
Subject: Re: [2.0.10 RC6] please test

Hi Brian,

RC6 - ERROR!
RC5 - ERROR!
RC3 - OK!

Sorry for not detecting the problem in the RC5. I didn't find time to 
test this release candidate. :(


Cheers,

Henrique

Brian E. Fox wrote:

Henrique, could you also try with RC5 to see if it is a new issue in
this RC? I'm betting it is related to the Modello change introduced in
RC6.

RC5 is at:


http://people.apache.org/~brianf/RC-5/org/apache/maven/apache-maven/2.0.

10-RC5/

-Original Message-----
From: Henrique Prange [mailto:hpra...@gmail.com] 
Sent: Wednesday, December 17, 2008 8:51 AM

To: Maven Developers List
Cc: Maven Users List
Subject: Re: [2.0.10 RC6] please test

Hi Brian,

I found a problem while executing 'mvn clean install' in one of my 
projects. (See the error below)


I verified and the build works with 2.0.9 and 2.1.0-M1 without

problems.

Cheers,

Henrique





[ERROR] FATAL ERROR
[INFO] 




[INFO] null
[INFO] 




[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.model.Extension.hashCode(Extension.java:147)
at java.lang.Object.toString(Object.java:209)
at java.lang.String.valueOf(String.java:2615)
at java.lang.StringBuffer.append(StringBuffer.java:220)
	at 


org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(Defau

ltLifecycleExecutor.java:157)
	at 


org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec

ycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 


sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav

a:39)
	at 


sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
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)
[INFO] 





Brian E. Fox wrote:

Hello,
Thanks everyone for sticking with us this far. I have high hopes of

this

being the last RC.

This RC fixes MNG-3898 and updates the default plugin versions in the
super pom. You can see the changes to the super pom and specific
versions used here:


http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m
aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r

1=708789&r2=726765&diff_format=h

Here's the list of issues fixed in 2.0.10 (updated to remove the

wagon

fixes that were rolled back):



http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName

=Html&projectId=10500&Create=Create

And I've staged RC-6 here:



http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa

che-maven/2.0.10-RC6/



Please try it out and see if we have any remaining regressions over
2.0.9.

Thanks,
Brian


--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/brian/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For addi

Re: [2.0.10 RC6] please test

[Henrique Prange]

Hi Brian,

RC6 - ERROR!
RC5 - ERROR!
RC3 - OK!

Sorry for not detecting the problem in the RC5. I didn't find time to 
test this release candidate. :(


Cheers,

Henrique

Brian E. Fox wrote:

Henrique, could you also try with RC5 to see if it is a new issue in
this RC? I'm betting it is related to the Modello change introduced in
RC6.

RC5 is at:
http://people.apache.org/~brianf/RC-5/org/apache/maven/apache-maven/2.0.
10-RC5/

-Original Message-----
From: Henrique Prange [mailto:hpra...@gmail.com] 
Sent: Wednesday, December 17, 2008 8:51 AM

To: Maven Developers List
Cc: Maven Users List
Subject: Re: [2.0.10 RC6] please test

Hi Brian,

I found a problem while executing 'mvn clean install' in one of my 
projects. (See the error below)


I verified and the build works with 2.0.9 and 2.1.0-M1 without problems.

Cheers,

Henrique


[ERROR] FATAL ERROR
[INFO] 


[INFO] null
[INFO] 


[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.model.Extension.hashCode(Extension.java:147)
at java.lang.Object.toString(Object.java:209)
at java.lang.String.valueOf(String.java:2615)
at java.lang.StringBuffer.append(StringBuffer.java:220)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(Defau

ltLifecycleExecutor.java:157)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec

ycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav

a:39)
	at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
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)
[INFO] 




Brian E. Fox wrote:

Hello,
Thanks everyone for sticking with us this far. I have high hopes of

this

being the last RC.

This RC fixes MNG-3898 and updates the default plugin versions in the
super pom. You can see the changes to the super pom and specific
versions used here:


http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m
aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r

1=708789&r2=726765&diff_format=h

Here's the list of issues fixed in 2.0.10 (updated to remove the wagon
fixes that were rolled back):



http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName

=Html&projectId=10500&Create=Create

And I've staged RC-6 here:



http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa

che-maven/2.0.10-RC6/



Please try it out and see if we have any remaining regressions over
2.0.9.

Thanks,
Brian


--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/brian/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [2.0.10 RC6] please test

[Henrique Prange]

Hi Brian,

I found a problem while executing 'mvn clean install' in one of my 
projects. (See the error below)


I verified and the build works with 2.0.9 and 2.1.0-M1 without problems.

Cheers,

Henrique


[ERROR] FATAL ERROR
[INFO] 


[INFO] null
[INFO] 


[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.model.Extension.hashCode(Extension.java:147)
at java.lang.Object.toString(Object.java:209)
at java.lang.String.valueOf(String.java:2615)
at java.lang.StringBuffer.append(StringBuffer.java:220)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:157)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
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)
[INFO] 




Brian E. Fox wrote:

Hello,
Thanks everyone for sticking with us this far. I have high hopes of this
being the last RC.

This RC fixes MNG-3898 and updates the default plugin versions in the
super pom. You can see the changes to the super pom and specific
versions used here:
http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m
aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r
1=708789&r2=726765&diff_format=h

Here's the list of issues fixed in 2.0.10 (updated to remove the wagon
fixes that were rolled back):

http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create

And I've staged RC-6 here:

http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.10-RC6/



Please try it out and see if we have any remaining regressions over
2.0.9.

Thanks,
Brian


--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/brian/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [2.0.10 RC] Please test

[Henrique Prange]

Hi Brian,

Brian E. Fox wrote:

The version is correct but it does seem to have the wrong embedded
version. There must be a property in the pom that the release plugin
didn't update.

On the wagon-ssh, I'm not having issues, can you give more info on how
to reproduce it?


Sure. It's an open source project. You can find the pom.xml here [1] and 
the project source here [2].


If you change the version of wagon-ssh to 1.0-beta-4 or remove the 
version tag, it doesn't work.


Following is the snippet of my settings.xml with the server connection data.


   webobjects.mdimension.com/dist/snapshots
   myusername
   



Does 2.1M1 work for you? (I ported back the exact fix
from that branch)


I've tried it again and it didn't work too. :( On both versions (2.1-M1 
and 2.0.10-RC3), it only work with wagon-ssh-1.0-beta-2.


I don't know why it have worked the first time. As I've cleaned my local 
repo, I can't reproduce the same environment I had at that time. :(


[1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/pom.xml
[2]https://svn.objectstyle.org/repos/woproject/trunk/woproject/

Cheers,

Henrique



-----Original Message-
From: Henrique Prange [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 14, 2008 5:04 PM

To: Maven Users List
Cc: [EMAIL PROTECTED]
Subject: Re: [2.0.10 RC] Please test

Hi Brian,

I've tried the RC3 but it seems to be the old RC2. I've downloaded 
distinct packages (tar.gz and zip) on different browsers (Safari and 
Firefox) to avoid any cache problems. :(


Following is the mvn -v output:

Maven version: 2.0.10-RC2
Java version: 1.5.0_16
OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix"

I've tested anyway and the wagon-ssh issue is still there. Are you sure 
the staged version is the right one?


Cheers,

Henrique

Brian Fox wrote:

Hello,
This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No
other issues where identified in RC2 so hopefully this will become the
last RC.


Here's the list of issues fixed in 2.0.10:



http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName

=Html&projectId=10500&Create=Create

And I've staged RC-3 here:



http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa

che-maven/2.0.10-RC3/



Please try it out and see if we have any remaining regressions over

2.0.9.

Thanks,

Brian

--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/people/brian/

-
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: [2.0.10 RC] Please test

[Henrique Prange]

Hi Brian,

I've tried the RC3 but it seems to be the old RC2. I've downloaded 
distinct packages (tar.gz and zip) on different browsers (Safari and 
Firefox) to avoid any cache problems. :(


Following is the mvn -v output:

Maven version: 2.0.10-RC2
Java version: 1.5.0_16
OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix"

I've tested anyway and the wagon-ssh issue is still there. Are you sure 
the staged version is the right one?


Cheers,

Henrique

Brian Fox wrote:

Hello,
This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No
other issues where identified in RC2 so hopefully this will become the
last RC.


Here's the list of issues fixed in 2.0.10:

http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create

And I've staged RC-3 here:

http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.10-RC3/



Please try it out and see if we have any remaining regressions over 2.0.9.

Thanks,

Brian

--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/people/brian/

-
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: [2.0.10 RC] Please test

[Henrique Prange]

Hi Brian,

I'm using wagon-ssh (for scp:// url).

I've probably used the latest version, since it was not specified in my 
pom.xml.


I did two tests with the same project:

1) Specified the wagon-ssh version as 1.0-beta-4 (I suppose it is the 
latest):


I had the same problem.

2) Specified the wagon-ssh version as 1.0-beta-2:

Maven did what it was supposed to do without asking me to type any password.

Hope this helps.

Cheers,

Henrique

P.S.: I have the following message printed on console for both versions 
of the wagon plug-in (beta-2 or beta-4).


WAGON_VERSION: 1.0-beta-2

Brian E. Fox wrote:

What wagon/url is being used?

-Original Message-----
From: Henrique Prange [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 07, 2008 8:55 AM

To: Maven Users List
Subject: Re: [2.0.10 RC] Please test

Hi Brian,

I've tried to deploy a project with 2.0.10-RC2 and I receive a message 
asking me to type the password a lot of times.


[INFO] Retrieving previous build number from myhost.com/dist/snapshots
Keyboard interactive required, supplied password is ignored
Password::

I've rechecked and the password is correctly configured in my 
settings.xml. I've tried with 2.1.0-M1 and it worked fine.


Cheers,

Henrique

Brian Fox wrote:

Hello,
We're moving forward with the 2.0.10 RC process. We have have not
turned up any new issues within the Dev team, so as usual we're
widening our net.

Here's the list of issues fixed in 2.0.10:



http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName

=Html&projectId=10500&Create=Create

And I've staged RC-2 here:



http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa

che-maven/2.0.10-RC2/



Please try it out and see if we have any remaining regressions over

2.0.9.

Thanks,

Brian

--

Brian Fox

Apache Maven PMC

http://blogs.sonatype.com/brian/

-
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: [2.0.10 RC] Please test

[Henrique Prange]

Hi Brian,

I've tried to deploy a project with 2.0.10-RC2 and I receive a message 
asking me to type the password a lot of times.


[INFO] Retrieving previous build number from myhost.com/dist/snapshots
Keyboard interactive required, supplied password is ignored
Password::

I've rechecked and the password is correctly configured in my 
settings.xml. I've tried with 2.1.0-M1 and it worked fine.


Cheers,

Henrique

Brian Fox wrote:

Hello,
We're moving forward with the 2.0.10 RC process. We have have not
turned up any new issues within the Dev team, so as usual we're
widening our net.

Here's the list of issues fixed in 2.0.10:

http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create

And I've staged RC-2 here:

http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.10-RC2/



Please try it out and see if we have any remaining regressions over 2.0.9.

Thanks,

Brian

--

Brian Fox

Apache Maven PMC

http://blogs.sonatype.com/brian/

-
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: Where is maven-archetype-plugin 2.0-alpha-4 located?

[Henrique Prange]

Hi Trent,

The 2.0-alpha-4 version of this plug-in was not released yet. Raphaël is 
preparing to release this version on Maven Dev list.


Cheers,

Henrique

Trent Rosenbaum wrote:

Hi there,
I was wondering if someone could point me in the right direction to locate
the repository for the 2.0-alpha-4 release of the maven archetype plugin?
The Jira entry ARCHETYPE-188  has been confirmed to have been fixed in this
release, but it is not present within the main maven repository.

 http://jira.codehaus.org/browse/ARCHETYPE-188

I can see all the other releases under the following location


http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/.

Should the release be found at this location or should I have another
repository configured within Archiva?

Trent



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

Re: [PLEASE TEST] 2.1.0-M1-RC12 of Maven (was: Maven 2.0.10-RC*)

[Henrique Prange]

Hi John,

FYI, I've tried this RC with a couple of projects (including the plug-in 
project) and no problems found.


Thank you very much.

Cheers,

Henrique

John Casey wrote:

Hi everyone,

Sorry if the subject of this message is a little confusing, but we're in 
the process of relabeling the code in this release candidate to be part 
of a new version, a departure from the 2.0.x codebase. This release 
candidate contains some large modifications, even though it's meant to 
be backward compatible, and the risk that entails makes the relabeling 
appropriate.


In any case, I'm anticipating one of a set of possible results from this 
relabeling discussion, and calling this RC 2.1.0-M1-RC12 (since it needs 
*some* name). You can find it here:


http://people.apache.org/~jdcasey/stage/apache-maven/2.1.0-M1-RC12/org/apache/maven/apache-maven/2.1.0-M1-RC12/ 



Please give it a try when you have time. I think you'll find this the 
most stable of all our attempts so far, and possibly even the one we'll 
promote for a final release, whatever version it winds up having.


Thanks,

-john



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

Re: System Scope

[Henrique Prange]

Hi Mike,

Couldn't you create a secured place into your Repository Manager? Only 
people with the required credentials will have access to those jars.


Cheers,

Henrique

CORUM, M E [AG/1000] wrote:

I assume that you would be replacing that with some equivalent
functionality, right?  Otherwise, you would be taking away the
capability for large companies to use Maven.  Let me give an example
(actually two).  We have jar files from vendors that our Maven projects
must depend on.  In one case, there is a licensing agreement that
disallows us from putting these jars into Maven/Nexus.  In another case,
the jar is "security-sensitive" and must not be put in Maven due to
audit or security requirements.  The company I work at has over 200
Maven projects now.  Taking out system scope would immediately cause us
to have to look for an alternative to Maven due to legal, audit, and
security requirements.  System scope (or an equivalent capability) must
stay in Maven for it to be used by many companies.

Mike Corum

-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 29, 2008 9:25 AM

To: Maven Users List
Cc: Maven Users List; Asif
Subject: Re: RE:

because the system scope is scheduled for removal post 2.0.x (or is  
that post 2.1 now ;-) )


Sent from my iPod

On 29 Aug 2008, at 14:21, Martin Gainty <[EMAIL PROTECTED]> wrote:


Good Morning Asif

why sparingly?

thanks
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the  
official business of Sender. This transmission is of a confidential  
nature and Sender does not endorse distribution to any party other  
than intended recipient. Sender does not necessarily endorse content  
contained within this transmission.




From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: users@maven.apache.org
Date: Fri, 29 Aug 2008 16:44:28 +0530
Subject: RE:

One way is to use the  system.setting, helps  
you point to jars on the File System but this should be used  
SPARINGLY

Use the maven repository, that's the true power of Maven.



From: Asif [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2008 3:43 PM
To: Saket Lakshminarayan Chiluveru
Cc: users@maven.apache.org
Subject:

Hey Guys,
Thank you for all the support.
I achieved making a  war using maven for a very simple web-app.
One more doubt though, how can I refer to the jars needed by the  
app from pom.xml.

I know one way is by defining dependencies.
Isn't there a simple entry that could be made in pom.xml that acts  
as a classpath.


DISCLAIMER == This e-mail may contain privileged and  
confidential information which is the property of Persistent  
Systems Ltd. It is intended only for the use of the individual or  
entity to which it is addressed. If you are not the intended  
recipient, you are not authorized to read, retain, copy, print,  
distribute or use this message. If you have received this  
communication in error, please notify the sender and delete all  
copies of this message. Persistent Systems Ltd. does not accept any  
liability for virus infected mails.


 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION  
intended solely
for the use of the addressee(s). If you are not the intended  
recipient, please
notify the sender by e-mail and delete the original message.  
Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any  
other person and
any such actions are unlawful. This e-mail may contain viruses.  
Infosys has taken
every reasonable precaution to minimize this risk, but is not  
liable for any damage
you may sustain as a result of any virus in this e-mail. You should  
carry out your
own virus checks before opening the e-mail or attachment. Infosys  
reserves the
right to monitor and review the content of all messages sent to or  
from this e-mail
address. Messages sent to or from this e-mail address may be stored  
on the

Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***

_
Be the filmmaker you always wanted to be-learn how to burn a DVD wit 
h Windows(r).

http://clk.atdmt.com/MRT/go/108588797/direct/01/


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



-
This e-mail message may contain privileged and/or confidential information, and 
is intended to be received only by persons entitled to receive such 
information. If you have received this e-mail in error, please notify the 
sender immediately. Please delete it and all attachments from any servers, hard 
drives or any other media. Other use of this e-

Re: [PLEASE TEST] Maven 2.0.10-RC11

[Henrique Prange]

Hi John,

I compared the contents of the artifacts generated by 2.0.9 and 
2.0.10-RC11 and they are different. The latter doesn't have the Ant 
build file and has a different plug-in descriptor.


Another difference is the version of maven-plugin-plugin. Maven 2.0.9 
uses 2.4.1 and Maven 2.0.10-RC11 uses 2.4.2. I tried to fix the version 
in my pom to use 2.4.1 and rebuild with 2.0.10-RC11. I had the same 
problem though. :(


Cheers,

Henrique

Henrique Prange wrote:

Hi John,

I found something, but I can't ensure it is caused by 2.0.10-RC11. I 
have a Maven plug-in that extends the lifecycle and adds a new kind of 
package. It also uses some Ant tasks. When I build the plug-in with 
2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I 
try to build a project that depends upon this plug-in and use my custom 
package, I get an "required goal not found" error (below is the entire 
exception message).


I have no problems if I build the plug-in with 2.0.9. You can access the 
code of this plug-in on [1].


[1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/maven2/maven-wolifecycle-plugin 



Cheers,

Henrique

[INFO] 


[ERROR] BUILD FAILURE
[INFO] 

[INFO] Required goal not found: 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
[INFO] 


[INFO] Trace
org.apache.maven.BuildFailureException: Required goal not found: 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1820) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1295) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1259) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:516) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330) 

at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) 


at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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)
[INFO] 



John Casey wrote:

Hi again,

One bug was identified in 2.0.10-RC10 last Friday night. This release 
candidate addresses that issue. You can find it here:


http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ 



Please give this a spin when you get a chance, and let us know if you 
find any problems. We'll file any issues in JIRA against version 
2.0.10 for tracking purposes, and to give us a JIRA # to use when 
writing the integration test to verify the fix.


Thanks,

-john





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

Re: [PLEASE TEST] Maven 2.0.10-RC11

[Henrique Prange]

Hi John,

I found something, but I can't ensure it is caused by 2.0.10-RC11. I 
have a Maven plug-in that extends the lifecycle and adds a new kind of 
package. It also uses some Ant tasks. When I build the plug-in with 
2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I 
try to build a project that depends upon this plug-in and use my custom 
package, I get an "required goal not found" error (below is the entire 
exception message).


I have no problems if I build the plug-in with 2.0.9. You can access the 
code of this plug-in on [1].


[1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/maven2/maven-wolifecycle-plugin

Cheers,

Henrique

[INFO] 


[ERROR] BUILD FAILURE
[INFO] 

[INFO] Required goal not found: 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
[INFO] 


[INFO] Trace
org.apache.maven.BuildFailureException: Required goal not found: 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in 
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1820)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1295)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1259)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:516)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330)
	at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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)
[INFO] 



John Casey wrote:

Hi again,

One bug was identified in 2.0.10-RC10 last Friday night. This release 
candidate addresses that issue. You can find it here:


http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ 



Please give this a spin when you get a chance, and let us know if you 
find any problems. We'll file any issues in JIRA against version 2.0.10 
for tracking purposes, and to give us a JIRA # to use when writing the 
integration test to verify the fix.


Thanks,

-john



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

Re: [PLEASE TEST] Maven 2.0.10-RC10

[Henrique Prange]

Hi Peter,

It seems that you don't have the maven-compiler-plugin configured 
correctly. You must set the source as 1.5 to use Enums. See [1] for more 
information.


[1]http://maven.apache.org/general.html#Compiling-J2SE-5

Cheers,

Henrique

Peter Horlock wrote:

Using RC10, the following fails, which was working with 2.0.9:
(seems like it doesn't like enums?!)

mvn clean tomcat:deploy -o
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.

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

[INFO] Building webclient
[INFO]task-segment: [clean, tomcat:deploy]
[INFO]

[INFO] [clean:clean]
[INFO] Deleting directory target
[INFO] Preparing tomcat:deploy
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 57 source files to target\classes
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

MyClass.java:[22,1] annotations are not supported in -source 1.3
(try -source 1.5 to enable annotations)
@SuppressWarnings("nls")

*MyEnum.java:[17,7] 'class' or 'interface' expected*

[...other, similar errors...]

[INFO]

[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
... 20 more
[INFO]

[INFO] Total time: 3 seconds
[INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008
[INFO] Final Memory: 11M/20M
[INFO] -



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

Re: assembly help

[Henrique Prange]

Hi Lachlan,

On Wed, Apr 23, 2008 at 2:24 AM, Lachlan Deck <[EMAIL PROTECTED]> wrote:
>  Okay - making progress...
>
>  If I create a maven-archetype-j2ee-simple, cd into the dir, comment out the
> site module from the parent pom and do 'mvn package' it all works without
> having to install the sub-modules.
>
>  However, with my structure it doesn't grab the jars from the sub-modules
> for the app - but complains that they're not installed. The app (with
> packaging = woapplication) fails to build.

Does it fail because Maven cannot find a dependency? Or is it another problem?

>
>  What am I missing? What's the 'trick' for making this work?
>

Have you tried "mvn clean install" in the parent module? The package
goal doesn't install the jars into the your local repository.

Have you declared the sub-module dependency in your application pom.xml?

Cheers,

Henrique

>  with regards,
>  --
>
>  Lachlan Deck
>
>
>
>

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

Re: assembly help

[Henrique Prange]

Hi Lachlan,

On Tue, Apr 22, 2008 at 9:31 PM, Lachlan Deck <[EMAIL PROTECTED]> wrote:
>  The documentation, for WOProject-Maven2 is not very verbose however.

Yeah. The documentation is poor. :(

>My dependent frameworks are not of packaging woframework, but jar

I think you really should try to use the woframework packaging. You
will have to write much less configuration.

> - so I can't see what options/configurations to provide to bundle the 
> relevant dependent
> jars (or indeed - what scope they should be).

Why do you need the dependencies packaged inside a woframework jar?
The dependencies are declared in the pom.xml. When you declare a
woframework as dependency, Maven automatically adds the transitive
dependencies to your project. For example, if you have a woframework
that depends upon a library A. When you add this woframework to a
project, Maven will add the dependency A transitively to your project.

Cheers,

Henrique

>  I've got the relevant repo and plugin repo declarations in my parent pom
> but I'm getting this in the app project:
>  Cannot find lifecycle mapping for packaging: 'woapplication'.
>  Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingwoapplication.
>
>
>
>  with regards,
>  --
>
>  Lachlan Deck
>
>
>
>
>  -
>  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: assembly help

[Henrique Prange]

Hi Lachlan,

What do you want to do exactly? It seems that you are trying to package 
a WebObjects application. Have you tried the maven-wolifecycle-plugin [1]?


[1]http://wiki.objectstyle.org/confluence/display/WOL/WOProject-Maven2

Cheers,

Henrique

Lachlan Deck wrote:

Hi there,

I'm still quite new to maven... so any demos appreciated :-)

I'm needing to create a directory-based assembly (ideally it would be 
tgz or zipped up afterwards) - but I'm not quite sure how to go about 
the following.


The project looks like this:
/pom.xml
frameworks/
pom.xml
moduleA
etc
apps/
app1
etc

The apps need to be built as application bundles...e.g.,

.someExtension/
Dependencies/*.jar 
Resources/Java/.jar
etc

I also need to append to a textfile the list of dependencies prefixed by 
a custom path (one entry per line).


Any examples/ideas?
Thanks

with regards,
--

Lachlan Deck


-
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: [newby] how to include/package private libs/*.jar

[Henrique Prange]

Hi Lachlan,

On Sat, Apr 19, 2008 at 8:31 AM, Lachlan Deck <[EMAIL PROTECTED]> wrote:
> On 19/04/2008, at 8:51 PM, Stephen Connolly wrote:
>
> > Deleting old releases is not really the way a repository is designed to
> > work.
> >
>
>  Not really - but is there a command for doing so?
>

Could you try the purge-local-repository goal of the
maven-dependency-plugin? See the docs here [1]. I never used this
goal, but I think it can help you.

[1]http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html

Cheers

Henrique

>
>
>  Thanks again.
>
>  with regards,
>  --
>
>  Lachlan Deck
>
>  -
>  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: [newby] how to include/package private libs/*.jar

[Henrique Prange]

Hi Lachan,

It is not recommended that you store your jars in SVN. So, there is no 
simple way to do what you want with Maven. But you can create a 
repository to share your own libraries (Maven can generate the pom.xml 
for you). Take a look at [1] and [2].


[1]http://maven.apache.org/guides/introduction/introduction-to-repositories.html
[2]http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html

Cheers from your WO friend, ;)

Henrique


Lachlan Deck wrote:

Hi there,

I'm quite new to maven, but I would have thought this question would 
have been included on the FAQ page for maven - but it's not. I've 
googled around but mustn't be putting in the right search phrase or 
something... as obviously I've not found the answer :-)


The simple question is how do I define dependencies on libs/*.jar for 
one of my projects where I have jars from a 3rd party (a payment 
gateway) in the project's lib folder. These libs live in svn with the 
project - not in a repo (and don't have a version or a pom of their own 
- they're just libs).


i.e., they obviously need to be on the classpath + packaged with the 
final jar?


I'm sure it's something simple... thanks in advance.

with regards,
--

Lachlan Deck




-
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: Documentation and/or examples for Maven Embedder

[Henrique Prange]

Hi Bill,

The newest version of the embedder was not released yet.

Look here [1]. I think you can find a way to solve your problems without 
having to make use of the Maven embedder.


[1]http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook

Cheers,

Henrique

Bill Rye wrote:

I'm looking for something beyond
http://maven.apache.org/guides/mini/guide-embedding-m2.html
as I want to do things like read pom.xml (done), add a jar to the
repository, and get the URL for the
location of a jar in the local repository given the artifact.

Thanks,
Bill



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

Re: Compile fails during install, while running compile succeeds

[Henrique Prange]

Hi Jeroen,

I have a similar problem here. It appears only if I have a submodule A 
referencing another submodule B and try "mvn install" on parent. The 
submodule A cannot find the classes from B. If I do a "mvn install" on 
submodule A, it works.


I tried "mvn compile" on parent, as you described, and surprisingly it 
works.


Everything works fine with Maven 2.0.5.

Cheers,

Henrique

Jeroen Leenarts wrote:

I'm not sure how to debug this, but this is what happened after having
upgraded to Maven 2.0.6. I have checked my dependency management 
sections as

described in the release notes. No conflicts there.

1. Get a fresh code base.
2. When I run "mvn install" the build fails during the compile phase of a
project.
3. While running "mvn compile" always succeeds on the same set of source
files.
4. Running "mvn install" again results in a successful build.
5. Running "mvn clean install" again results in a failure during the 
compile

phase.

Seems like a problem I should be capable of narrowing down, right? Well, 
the

thing is, the compile can fail and abort maven 2 at several different
projects.
I've tried running with the -X option and diff-ed the relevant sections of
output. Nothing there.

Anybody got any clues what could cause such behavior? Or even how I might
debug this?
In my opinion running "mvn install" or "mvn compile" followed by "mvn
install" should make no difference. Install requires passing the install
phase.

Regards,
Jeroen



--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

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

Re: Cannot build maven project

[Henrique Prange]

Thank you, Robert. I changed the log level to DEBUG, but no more useful 
information was logged.


As a desperate solution, I made a backup of Continuum and installed a 
new one from the scratch. I created a very simple project that works 
outside Continuum. The "mvn help:effective-pom help:effective-settings" 
command don't reveal anything suspicious for this project. But the 
problem still remains. Now, even with a fresh installation, Continuum 
doesn't work and I can't add any project.


Following is the pom.xml of the project:


4.0.0
moleque.test
simple-app
jar
1.0-SNAPSHOT
simple-app
http://maven.apache.org

   
  scm:svn:http://dev.moleque.com.br:8086/svn/simple-app/trunk
   
   
  scm:svn:http://dev.moleque.com.br:8086/svn/simple-app/trunk
   


   
  simple-app.site
  
 file:///Library/WebServer/Documents/docs/simple-app
  
   
   
  dev.moleque.repo.snapshot
  Snapshot Repository Moleque
  file:///Users/devadmin/proximity/inhouse
   



I don't know if it's a bug. But if it is, I don't know how to reproduce. :(

Any suggestions are very welcome. :)

Thanks in advance,

Henrique

Robert Dale wrote:

/apps/continuum/conf/application.xml:
There's a logging component at the bottom.  Modify LEVEL.



--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

Re: Cannot build maven project

[Henrique Prange]

Hi Rahul,

Maybe it is a stupid question, but how can I turn on DEBUG level on 
Continuum?


I removed the settings.xml from the user .m2 configuration folder. Also, 
I verified that settings.xml from maven installation folder is the 
original version (without changes). I think the problem is not on Maven 
settings, because "mvn clean deploy" command works with the projects on 
Continuum working directory. Could a Continuum specific option be the 
problem?


Thanks,

Henrique

Rahul Thakur wrote:

Hi,

I don't think if there is a way to verify the settings.xml (someone can 
correct if I am wrong). You can turn on the DEBUG level for continuum 
and see what settings.xml it logs on the console in the scenario where 
this error occurs.


I ran into same error few weeks ago and ended up reverting the 
settings.xml to a sane revision and then making small incremental 
updates to it.  Is that new repository location missing a property like 
- id, name?


Cheers,
Rahul


Henrique Prange wrote:

Hi Rahul,

Thank you to answer. I've changed the settings.xml to add a new 
repository location (this configuration seems to work correctly). 
Anyway, I removed the settings.xml file from ~/.m2 and the error 
persists. I really can't figure out what is the reason for that 
problem. Is there a way to verify the correctness of Continuum 
configuration?


Cheers,

Henrique

Rahul Thakur wrote:


Has something changed in the settings.xml lately for the user account 
under with Continuum is running?



Henrique Prange wrote:

Hi List,

I'm using Continuum for a time without problems. Today, however, my 
projects stop building with the following error:


 


Build Error:
 

org.apache.maven.continuum.execution.ContinuumBuildExecutorException: 
Error while mapping metadata.
at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) 

at 
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) 

at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) 

at 
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) 

at 
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) 


at java.lang.Thread.run(Thread.java:613)
Caused by: 
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: 
Cannot build maven project from 
/usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null).


at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) 

at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) 


... 5 more
Caused by: java.lang.NullPointerException
at 
org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) 

at 
org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) 

at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) 

at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) 


... 7 more

The projects were building normally sometime ago. If I try to build 
using maven manually on working directory, the build works.


Also, I can't add new projects to the project list too, because of 
the same problem. Any ideas?


Thanks,

Henrique









--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

Re: Cannot build maven project

[Henrique Prange]

Hi Rahul,

Thank you to answer. I've changed the settings.xml to add a new 
repository location (this configuration seems to work correctly). 
Anyway, I removed the settings.xml file from ~/.m2 and the error 
persists. I really can't figure out what is the reason for that problem. 
Is there a way to verify the correctness of Continuum configuration?


Cheers,

Henrique

Rahul Thakur wrote:


Has something changed in the settings.xml lately for the user account 
under with Continuum is running?



Henrique Prange wrote:

Hi List,

I'm using Continuum for a time without problems. Today, however, my 
projects stop building with the following error:


 


Build Error:
 

org.apache.maven.continuum.execution.ContinuumBuildExecutorException: 
Error while mapping metadata.
at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) 

at 
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) 

at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) 

at 
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) 

at 
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) 


at java.lang.Thread.run(Thread.java:613)
Caused by: 
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: 
Cannot build maven project from 
/usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null).


at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) 

at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) 


... 5 more
Caused by: java.lang.NullPointerException
at 
org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) 

at 
org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) 

at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) 

at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) 

at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) 


... 7 more

The projects were building normally sometime ago. If I try to build 
using maven manually on working directory, the build works.


Also, I can't add new projects to the project list too, because of the 
same problem. Any ideas?


Thanks,

Henrique





--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

Cannot build maven project

[Henrique Prange]

Hi List,

I'm using Continuum for a time without problems. Today, however, my 
projects stop building with the following error:



Build Error:

org.apache.maven.continuum.execution.ContinuumBuildExecutorException: 
Error while mapping metadata.
at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117)
at 
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64)
at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273)
at 
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47)
at 
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)

at java.lang.Thread.run(Thread.java:613)
Caused by: 
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: 
Cannot build maven project from 
/usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null).


at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339)
at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112)
at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113)

... 5 more
Caused by: java.lang.NullPointerException
at 
org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912)
at 
org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776)
at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581)
at 
org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71)
at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489)
at 
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301)

... 7 more

The projects were building normally sometime ago. If I try to build 
using maven manually on working directory, the build works.


Also, I can't add new projects to the project list too, because of the 
same problem. Any ideas?


Thanks,

Henrique

--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

Re: Create non-conventional archetype

[Henrique Prange]

Hi Eric,

Yes, you can do that. Take a look at:

http://maven.apache.org/guides/mini/guide-creating-archetypes.html

But you really can't use the standard directory layout of Maven? 
Standard over configuration is one of the best values of Maven. Take a 
look at:


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

Cheers,

Henrique

eric.frigot wrote:

Hi All,

I would like to create an archetype for my own project
structure. I made a framework with a lot of config files and
when i create a new project base on this framework, i must
copy all the files and directories structures. Is-it possible
to create such archetype ?

Here is a typical directory structure :
project
  |
  +- JavaSource
  |   |
  |   + com.myentreprise.myproject
  |   |  |
  |   |  + /* sources files go here */
  |   |
  |   + config /* files and sub-directories */
  |   |
  |   + /* others config files */
  | 
  + TestSource

  |
  + WebContent
  |
  + /* directories and files, WEB-INF, META-INF, ... */

Can an archetype create such structure ?
I am using Eclipse, is-it possible to extend its archetype and
this way create the dependancies ?

Thanks a lot for any information.

Accédez au courrier électronique de La Poste 
sur www.laposte.net ou sur 3615 LAPOSTENET (0,34€ TTC /mn) 
1 Giga de stockage gratuit – Antispam et antivirus intégrés 





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




--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

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

Re: How to write plugin in maven 2.0

[Henrique Prange]

Hi Neeraj,

Take a look at:

http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html

The book Better Builds with Maven contains a section about this topic. 
You can download the book at Mergere site:


http://www.mergere.com/m2book_download.jsp

Good luck,

Henrique

Neeraj Bisht wrote:

hi all
Actully i want to write the plugin in maven 2.0  but i am unable
can any one help me to write plugin in maven 2.0
i saw the maven intern plugin but they did not use any annotation like  *
@goal*  @parameter how all that plugin r working i am unable to understand

Regards
Neeraj



--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

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

Maven Embedder without MavenProject

[Henrique Prange]

Hi list,

I want to execute mvn install:install-file inside of a maven plug-in. 
I'm trying to use MavenEmbedder, but it depends at least on one 
MavenProject to call execute() method.


I want to use install:install-file, but like this plug-in, I don't want 
to require a project to run my plug-in. Is it possible with maven 
embedder? How can I do that?


Thanks in advance,

Henrique
--

\o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda
 |  Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED]
/ \ http://www.moleque.com.br

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

Re: [M2] Managing Repositories

[Henrique Prange]

Hi Andreas,

Take a look at Proximity:

http://proximity.abstracthorizon.org/

Bests,

Henrique

Andreas Guther wrote:

Hi,

I am struggling with the question on how to maintain a controlled
internal repository with Maven 2.

We want to have full control over the downloaded dependencies and
configured Maven to use as central repository our internal repository
server.  With this configuration no external repository is used.

In my settings.xml file I have configured Ibiblio as external repository
server and activate the profile whenever I have to use components with
dependencies that are not in our internal repository.

The problem I have is that getting the internal/central repository
updated with the new dependencies is rather a tedious and time intensive
task, especially if for example a maven plug-in is added that comes with
lots of transient dependencies.

My question is:  Ho do other teams deal with that problem?  Are there
tools that list differences between two different repositories (local
and internal)?

I used Maven Archiva as proxy repository but that does not give us the
control over what gets added to the repository.

Thanks in advance for any hint and suggestion.

Andreas
 


-
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: [ANN] Proximity RC4 rolled out!

[Henrique Prange]

Tamás,

I've found this error whenever I try to start Tomcat with the last 
release candidate:


- Deploying web application archive proximity.war
- Error deploying web application archive proximity.war
java.lang.IncompatibleClassChangeError
at 
org.apache.commons.logging.impl.SLF4JLog.isDebugEnabled(SLF4JLog.java:29)
at 
org.apache.tomcat.util.digester.Digester.addRuleSet(Digester.java:1682)
at 
org.apache.catalina.startup.DigesterFactory.newDigester(DigesterFactory.java:85)
at 
org.apache.catalina.startup.TldConfig.createTldDigester(TldConfig.java:408)
at 
org.apache.catalina.startup.TldConfig.tldScanStream(TldConfig.java:508)
at 
org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:472)
at 
org.apache.catalina.startup.TldConfig.execute(TldConfig.java:307)
at 
org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4278)
at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4115)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at 
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at 
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
at 
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
at 
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
at 
org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at 
org.apache.catalina.core.StandardService.start(StandardService.java:450)
at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)

The Tomcat version is 5.5.17 and I have only the proximity WAR in the 
webapps folder.


Am I missing something?

Thanks in advance,

Henrique

Tamás Cservenák wrote:

Hi All,

the Proximity is finally got to RC4.


It has three major improvements: aggregated metadata checksum is correctly
calculated, "emergeGroups" that enables proper selective repository
aggregation and WS interface publishing using XFire.
See:
http://trac.abstracthorizon.org/proximity/milestone/Proximity%20Release%201.0.0-RC4 



Also, the j2ee webapp modules are "exploded", they comes now in different
flavours:

Default - as it was till now: Proximity Webapp (Default) is J2EE Web
Application with "default" configuration that suits in almost all cases.
Default configuration offers Px Core Web Services, uses Spring MVC + 
Jakarta

Velocity for view-tech and DWR as AJAX engine.
Demosite - Proximity Webapp (Demosite) is similar to "default": it is J2EE
Web Application with "default" configuration that runs on Proximity demo
site. Thus, it has few restrictions, including JAR downloading from 
"public"

repositories.
Minimal -  Proximity Webapp (Minimal) is minimal J2EE Web Application that
still have Maven Proxy functionality. To reduce it's weight, view layer 
uses

vanilla JSPs. Indexing is also sacrificed, together with pages that relies
on them (Search, Artifact browse). Fast and small. (on the way)
PxMaster and PxSlave - Proximity Webapp (PxMASTER and PxSLAVE) is J2EE Web
Application similar to "default" configured to act as PxMaster/PxSlave in
Proximity chain. Not usable in "every day" scenarios. Meant as "template"
for chaining setups. (on the way)



Have fun!
~t~



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

Re: m2eclipse and Proximity

[Henrique Prange]

Sorry, I didn't see that...

Thanks,

Henrique

Tamás Cservenák wrote:

It seems that this issue was already known:
http://jira.codehaus.org/browse/MNGECLIPSE-168

~t~

On 8/22/06, Tamás Cservenák <[EMAIL PROTECTED]> wrote:


Hi Henrique,

it seems to me that this is M2eclipse plugin issue (as you said, 
Proximity

works well with mvn on command line)

m2eclipse is still 0.0.9, and I have issues with it too: i cannot 
force it

to use another localRepo instead the default one :(
also, the "offline" switch seems that have no effect at all...


~t~


On 8/22/06, Henrique Prange < [EMAIL PROTECTED]> wrote:
>
> Hi list,
>
> I'm looking for a way to change the central repository used by 
m2eclipse

>
> plug-in in order to point to a proxy repository.
>
> I have set the Proximity repository in the settings.xml located in my
> home folder. Although it works fine at command line, when I'm at 
Eclipse

> and try to add any dependency that is not in my local repository, those
> dependencies are downloaded from http://repo1.maven.org/maven2. I
> expected that m2eclipse plug-in would use the 
settings.xmlconfiguration.

>
> Am I doing something wrong? Can I achieve this with 0.0.9 version?
>
> Thanks,
>
> Henrique
>
> -
> 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]

m2eclipse and Proximity

[Henrique Prange]

Hi list,

I'm looking for a way to change the central repository used by m2eclipse 
plug-in in order to point to a proxy repository.


I have set the Proximity repository in the settings.xml located in my 
home folder. Although it works fine at command line, when I'm at Eclipse 
and try to add any dependency that is not in my local repository, those 
dependencies are downloaded from http://repo1.maven.org/maven2. I 
expected that m2eclipse plug-in would use the settings.xml configuration.


Am I doing something wrong? Can I achieve this with 0.0.9 version?

Thanks,

Henrique

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