I'm have a problem using deploy:deploy-file with snapshots I'd like some
advice on please.
I have 2 projects; 1) Ant based and 2) Maven based that consumes the jars of
the other project via Archiva.
I've added a target to the Ant project to deploy snapshots on every
successful build during our
Solved my issue, if your interested see StackOverFlow:
http://stackoverflow.com/questions/2606106/maven-deploydeploy-file-not-found-due-to-version-timestamp-appended-to-jar
Regards.
On 9 April 2010 09:36, James Clinton james.clin...@avexa.co.uk wrote:
I'm have a problem using deploy:deploy
Why can I deploy to the pre-configured internal repository OK, but not
my identical custom repository?
INTERNAL
mvn deploy:deploy-file
-Dfile=commons-logging-1.1.1.jar
-DgroupId=commons-logging
-DartifactId=commons-logging -Dversion=1.1.1
-DrepositoryId=internal
Is there a way where I can upload my entire local repository into
Archiva as a Managed Repository in one hit, or do I need to use the mvn
deploy:deploy-file command for each file?
Regards.
Subject: Re: Deploying Libs to Archiva
En l'instant précis du 15/04/08 13:26, James Clinton s'exprimait en ces
termes:
Is there a way where I can upload my entire local repository into
Archiva as a Managed Repository in one hit, or do I need to use the mvn
deploy:deploy-file command for each file
A module (B) isn't compiling because maven is skipping the packaging of
test-jar in a dependant module (A).
goaltest-jar/goal
The goal above if declared as part of the profile in the module (A) but
Skipping packaging of the test-jar is always outputted.
Advice appreciated.
J
I'd like to change the output directory of the eclipse classpath.
mvn eclipse:eclipse defaults to project/target/classes
Is this possible?
DISCLAIMER: This e-mail is confidential and may also be legally privileged. If
you are not the intended recipient, use of the information contained
Having problems with sub-modules being included.
Followed this example but my child modules are simply ignored?
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodu
le/module-binary-inclusion-simple.html
Has anyone had this working successful? (descriptor snippet
Is it possible to suppress warnings like the following?
[WARNING] Entry: Project-1.3- SomeFile.java longer than 100 characters.
AFAIK these are produced by the assembler plug-in right?
This is a KI.
Use this script to fix.
The fixed script for maven 2.0.7 is :
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven
-core/src/bin/mvn.bat
-Original Message-
From: mfs [mailto:[EMAIL PROTECTED]
Sent: 31 August 2007 00:02
To:
Subject: Re: Continuum version 103 (maven2)
We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7
(http://jira.codehaus.org/browse/MNG-3084 )
James Clinton a écrit :
Opps - should of read my original post!.
Anwser is for Windows the mvn.bat file needs to be altered...I
version
The fixed script for maven 2.0.7 is :
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven
-core/src/bin/mvn.bat
Emmanuel
James Clinton a écrit :
See
http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect
-a-suc
cessful-build
Sounds like
Venisse [mailto:[EMAIL PROTECTED]
Sent: 28 August 2007 16:48
To: [EMAIL PROTECTED]
Subject: Re: Continuum version 103 (maven2)
Do you use maven 2.0.7?
James Clinton a écrit :
Hello,
I have a project structure like so:
- parent
- child
- child
Parent pom is them loaded into CI
Hello,
I have a project structure like so:
- parent
- child
- child
Parent pom is them loaded into CI and the projects are detected.
It builds fine, but if there is a compilation error, the status of the build
is still 'success'.
Is this a known issue?
James
DISCLAIMER: This
( apoligies if you received this twice )
Hello,
Setting up Continuum for the first time using Maven2 for our builds. (which
is a Multi-Project).
Pointed Continuum to the parent POM and this loaded in the projects. When
running the parent the build fails because it cannot find the child POM
15 matches
Mail list logo