On Mon, Jul 11, 2011 at 8:15 PM, Olaf Klischat wrote:
> mvn deploy:deploy-file -Dfile=mylib.jar DpomFile=mypom.pom
> -DgeneratePom=false -Durl=
>
> , it apparently just uploads the jar under the name mypom.pom>-.pom.
You mentioned a timestamp, so... you're deploying a snapshot? And
even though
OK, thanks, in my scenario I can't assume that Maven 2/3 will be installed
and there typically won't be a pom file either. I guess I'll await 2.2.2
(or more specifically a new m.a.t release) with hopefully a fix for:
http://jira.codehaus.org/browse/MANTTASKS-213
I'll look at a hacked solution in t
I have a jar file and an accompanying POM file that describes the jar
file's metadata (name etc.) and dependencies, but contains no
repo/deployment info. Can I upload both files to my (Sonatype Nexus or
local/filesystem) repo so that they end up as one project/artifact, just
as they would if I
Well m-a-t shades the maven classes that it uses inside the m-a-t jar
file... so adding maven 3 jars to the classpath will have no effect.
By forking I meant the artifact:mvn task:
http://maven.apache.org/ant-tasks/examples/mvn.html
which can be used to fork a m2 or m3 build and will handle downl
Thanks Stephen, where can I find out more info about "forking Maven 3"?
To give some context, I am trying to resolve this bug in the Groovy jira
(2.1.3 still has this problem):
http://jira.codehaus.org/browse/GROOVY-4562
My guess is that we may be hitting:
http://jira.codehaus.org/browse/MNG-4738
Thanks for quick answers! Actually we want the exactly solution you suggest:
one pom - one distribution package. Packing a config in a jar file is not
acceptable because configuration can be altered by the end-user and in case
of component update he will loose all the modifications.
Solution with
Thanks for quick answers! Actually we want the exactly solution you suggest:
one pom - one distribution package. Packing a config in a jar file is not
acceptable because configuration can be altered by the end-user and in case
of component update he will loose all the modifications.
Solution with
Guillaume's suggestion is in line with the "Maven way" of "one pom - one
product".
If you follow his advice you will not be in a constant battle with Maven.
Once you have you packages set up, they should require little
maintenance and with good package ids will be easy to document.
Ron
On
http://maven.apache.org/ant-tasks/download.html
and
http://repo1.maven.org/maven2/org/apache/maven/maven-ant-tasks/2.1.3/
Don't mind the 2.x version number it can fork Maven 3 if you need it to
-Stephen
On 11 July 2011 10:41, Paul King wrote:
>
> Hi,
>
> I was trying to find where in a snapsh
Hi,
I was trying to find where in a snapshot repo or source repository
the latest version of the maven ant tasks reside?
Thanks, Paul.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-ma
Hi,
I have set up this kind of project by using Multi-module project;
packages are built with the assembly plugin. The thing is that I have
two main branches in my multi-module project:
1) for all the jars of code: this branch configures all the general
presets for all jars of the application.
This isn't a Maven thing, but we usually name all our component configuration
files the same name in the respective jars. Spring has a means to find all the
files of the same name in the different jars (you can go check it out there,
they use the "classpath*:" nomenclature for it). That way, o
Hi,
The Mojo team is pleased to announce the release of Animal Sniffer version 1.7.
This is the fifth release of Animal Sniffer
(http://mojo.codehaus.org/animal-sniffer/) since it moved from
java.net to the mojo project at codehaus. We have fixed a number of
bugs
(http://jira.codehaus.org/secur
It is currently possible but it's not guaranteed to run forever. If there is no
unique feature which you can only do with guice, then I'd still suggest doing
it the 'old' way.
There have been discussions about switching from JSR-330 to the more powerful
JSR-299 spec for DI. So if you like to k
Hi,
The Mojo team is pleased to announce the release of the Build Helper
Maven Plugin version 1.7.
This plugin contains various small independent goals to assist with
the Maven build lifecycle.
http://mojo.codehaus.org/build-helper-maven-plugin/
To get this update, simply specify the version in
The Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.3
This plugin is used to copy and unpack artifacts and dependencies. It
also provides visualization and optimization tools for your project
dependencies.
http://maven.apache.org/plugins/maven-dependency-pl
16 matches
Mail list logo
