Publishing failed
Resource /M2_REPO/commons-logging/commons-logging/1.0/commons-
logging-1.0.jar does not exist.
That's a WTP bug, in any version from WTP 1.0 till recent builds:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783
WTP 1.0 simply ignores external dependencies, later builds
First of all I really like the release plugin it is really useful!
I have been playing around a little and I wonderif there is a way to
get an automatic scm tag?
Right now the release plugin asks me what tag to use, for me it would
be ok if it used the version sans -SNAPSHOT of course? Can I
right - I took it for granted that david will still be using the new
site plugin without the snapshots repo. If you revert to the old site
plugin, you should be ok indeed.
On 2/4/06, Brett Porter [EMAIL PROTECTED] wrote:
No, the skin tag in your site descriptor will be ignored if you use
the
Why do you need to add a war as dependency?
If i's only to get all dependencies, set the dependency type to pom.
Emmanuel
Jason Chaffee a écrit :
If I try to add a dependency of type war to my pom, I get the following
error:
[ERROR] FATAL ERROR
[INFO]
Yes. I use edu.ku.middleware for my team's projects in our local repository.
--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas
On 2/3/06 10:59 AM, Mike Perham [EMAIL PROTECTED] wrote:
The old naming
Hi Fabrizio,
On 2/4/06, Fabrizio Giustina [EMAIL PROTECTED] wrote:
Publishing failed
Resource /M2_REPO/commons-logging/commons-logging/1.0/commons-
logging-1.0.jar does not exist.
That's a WTP bug, in any version from WTP 1.0 till recent builds:
Thanks, I'm convinced its a cvs/ssh setup problem.
I've uploaded my public key to SF, but I can't commit
from cvs commandline without entering a password. The
frustrating thing is that there is no feedback - i.e.
no prompt for the password - it just appears to hang.
But anyway, its not a maven
Hi people,
I'm very new to maven 2, but I've been a maven 1.0 user for a time.
I've read all the theory about profiles, which brings to me a question:
What is the best place to put my username and password for the
maven-scm-plugin. Perhaps the pom.xml is not the best place (In the
plugin
when I create a project with:
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp
-DarchetypeArtifactId=maven-archetype-webapp
the directory structure is:
my-webapp/
|-- pom.xml
`-- src
`-- main
|-- resources
`-- webapp
|-- WEB-INF
Lee,
Have you tried using the exclusions that are available within the
dependency declarations?
If this webservices.jar is needed in a project (say project-a) which
is included within an ear (say ear-project), you would define the
following dependency within the ear-project pom:
dependency
I will be out of the office starting 05-02-2006 and will not return until
13-02-2006.
I will respond to your message when I return. In case of urgency contact
Jean-Christophe Clare ([EMAIL PROTECTED]), Maes Dirk
([EMAIL PROTECTED])
modules
module
pomFilepom_jar.xml/pomFile
/module
...
/modules
Personally, I think this should be allowed...
+1
-Original Message-
From: Frank Russo [mailto:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 8:51 AM
To: Maven Users List
Subject:
Must be a linux issue then? It works ok for me on windows using the
/win32 folder.
-Original Message-
From: Christian Mouttet [mailto:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 8:56 AM
To: Maven Users List
Subject: Re: Continuum Maven 2 not using settings.xml
Hi Brian,
dan tran wrote:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
indicates what maven will zip and deploy the your source if you pass in
-DperformRelease=true.
Give it a try.
-Dan
Still no go :-(
No matter what I put in the pom.xml I have created for the jar,
14 matches
Mail list logo