Problems with Maven Eclipse Plugin

This may be the wrong place to ask this question, if so please advise where the issue should be reported. When Eclipse starts up I encounter the following error: ___ 5/12/08 12:11:07 PM MDT: Downloaded [central] -> http://repo1.maven.org/maven2/.index/nexus-maven-repository-index.zip 5/12/

RE: [m1.1] jar/war deploy doesn't Deploy

ent: Wednesday, August 17, 2005 1:03 AM To: Curtis, Harrison Cc: Maven Users List Subject: Re: [m1.1] jar/war deploy doesn't Deploy Thanks. Can you do a search to find out where the actually did end up? (it would be very strange for it to show progress and not save them). With that info, please

m[1.1] custom plugin using

Is there any way for a plugin to default logging at the error level? Can the plugin supply a log4j.xml or log4j.properties if one hasn't been provided by the users environment? So far the only way I can get jelly logging to work is to use MAVEN_OPTS and define the log4j.configuration parameter wi

RE: [m1.1] jar/war deploy doesn't Deploy

ay, August 15, 2005 7:07 PM To: Maven Users List Subject: Re: [m1.1] jar/war deploy doesn't Deploy You'll find them in c:\ The bug was fixed in the 1.6 release of the artifact plugin. - Brett On 8/16/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote: > In Maven 1.1 when a jar:depl

[m1.1] jar/war deploy doesn't Deploy

In Maven 1.1 when a jar:deploy is performed the jar files in the local repository should be copied to the specified remotes. My build.properties has the following entries to specify the remote: maven.repo.list=R1 maven.repo.R1=file://c:\\temp\\Maven maven.repo.R1.directory=repository The followi

Plugin passing values to a Jelly Swing display?

It appears that the best way to execute a jelly:swing is with the following script: Since in this case the jelly:swing is running in a forked process, how would you pass the information to be displayed in the script. The only thing I can think of is to write out a file in

M[1.1] plugin:repository-deploy does not deploy

The maven 1.1 plugin:repository-deploy did not deploy to the repository. The following shows it went through the motions but after inspecting the R1 repository the plugin wasn't there. plugin:repository-deploy: [echo] Deploying... Will deploy to 1 repository(ies): R1 Deploying to repository: R

M[1.1] and the Eclipse MavenIDE

I'm trying to run a simple plugin:install within the Eclipse 3.1 MavenIDE. All the editing features of the IDE are functional, but it appears there is a new library requirement not satisfied. Within the MavenIDE configuration I changed the Maven Home to point to: C:\Program Files\Apache

RE: M[1.1] Multiproject Issue

. You can download the latest artifact plugin to correct it: maven plugin:download -DartifactId=maven-artifact-plugin -Dversion=1.6 -DgroupId=maven Cheers, Brett On 8/4/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote: > I'm trying to run a multproject under Mave 1.1. This project

M[1.1] Multiproject Issue

I'm trying to run a multproject under Mave 1.1. This project works fine under 1.0.2. There seems to be a problem with the artifact-install (which is probably a configuration problem). Can someone suggest what action to take to get the multiproject to build? The following is the error after the

RE: Maven, EJBs and clashing JNDI names

We have several MDB's which are principally configuration. They all derive from a base class MDB which is developed as a one of the classes in a utilities jar. The base class is a separate Maven project which the customized MDBs depend on. Each of the customized MDB projects have their own deplo