Prashant,
If those libraries are standard and well known then should be available at some
maven repository. You can try http://mvnrepository.com to find it out.
Generally, you should setup your own repository may be using artifactory and
put all dependencies there. Requirement is maven should ab
if local builds are being run using jetty:run there are some tricks to allow
jetty to add the file to the effective webapp so that the war never needs
context.xml and there is just one and only one war built (thus avoiding the
nasty profile produces different artifact complaint that people make aft
Hi All,
We are starting new web project. But, it has to be built on some proprietary
web framework which is NOT mavenised and comes with its own bunch
of libraries. I am thinking of using maven for this application development.
But, just wondering how to ensure maven uses this proprietary framewor
Hi
the opensource version of java service wrapper ( JSW ) used by
appassembler-maven-plugin does not come with windows_x86_64 bit,
and Sonatype's nexus community distribution has a copy of
wrapper_windows_x86_64_exe, and I believe is from version 3.2.3.
Can we use this with appassembler-plugin
Well I can see some point to that. There are scm tags in the POM where you can
download the source. In this case I like to think of this more like giving me
the files I would put on a website. On the site I would want the real jar,
javadocs, sources, and a real, compilable source code. The secon
I didn't think it moved the file into target. I tried that and ran mvn package
and it didn't happen. However, I checked my .m2 local repository after mvn
install and it DOES appear in there. I just don't think it works.
org.codehaus.mojo
build-helper-maven-plugin
Ahh yes. It isn't meant for software development. It is the source you can
debug through. I think of this as the "real" source. Your terminology threw me
for a loop.
Software you development from is usually denoted as a trunk or branch that you
check out from source control. I find it unusual
Well, you can't unpack that jar then run mvn, because there's no pom.xml in
the root. I think there is a way to get the POM in there but it goes into
META-INF. It also never seems to include files like README, COPYING, NOTICE,
etc. The sources jar also doesn't have my layout with src/main/java e
Jason Winnebeck wrote:
> I have an existing Maven project which deploys currently source, javadocs,
> and a jar. I realize now that the sources jar is not a real source of the
> project. I would like to deploy:
>
> 1. A zip archive of the svn export of the tag created in
> maven-release-plugin:
It's not the sources? Then what is it? It's the actual source for any release
that I have ever done ;-). How do you define REAL source?
> -Original Message-
> From: Jason Winnebeck [mailto:jpw...@rit.edu]
> Sent: Wednesday, September 28, 2011 4:11 PM
> To: Maven Users List
> Subject: R
Thanks, that works very well. I was using Maven for awhile before I learned
that the -sources.jar is not actually the project sources. If I don't find a
better way to do the second task, my only other thought is to use the ant
plugin to do a with build-helper, but it looked like it was tricky t
On 2011-09-28 18:18, codingplayer wrote:
> Hi everybody,
>
> I'm currently reworking my master pom to use the section
> as proposed.
>
> For me it is still unclear which parts of a plugin-definition need to be
> placed in which section? (pluginManagment, plugins, reporting)
>
> As i would inter
For the first task, I think that this is what is done for Apache
projects nowadays. Either someone active on such a project could fill
in the blanks or you go have a look in this pom:
http://repo1.maven.org/maven2/org/apache/apache/10/apache-10.pom
Look for the profile with id "apache-release".
/A
Thank you all!
I was starting to lose it a bit - I'm glad I persisted.
Nexus community confirmed it's a bug in mvn that shall be addressed in
version 3.0.4.
2011/9/28 Tamás Cservenák
> Mark, you were right:
>
> The "Maven User" (initial poster) uses jersey together with Jersey Spring
> integ
> We use context.xml in our local builds, but when building a war for
> other environments, we would like to not include the context.xml file.
>
> Any ideas on how to exclude context.xml for non-local builds?
Any time you have a question like this, the answer is almost always
"use a profile."
Way
I have an existing Maven project which deploys currently source, javadocs, and
a jar. I realize now that the sources jar is not a real source of the project.
I would like to deploy:
1. A zip archive of the svn export of the tag created in
maven-release-plugin:prepare during release:perform
2.
Hi, I am working on a Spring/Tomcat project and am stuck on how to best package
the context.xml file.
We use context.xml in our local builds, but when building a war for other
environments, we would like to not include the context.xml file.
Any ideas on how to exclude context.xml for non-loc
Hi everybody,
I'm currently reworking my master pom to use the section
as proposed.
For me it is still unclear which parts of a plugin-definition need to be
placed in which section? (pluginManagment, plugins, reporting)
As i would interpret, the default config for a plugin should be placed into
We have aggregation projects that build a jar file containing all the
dependencies for that set of libraries.
We exclude anything that is being provided in another library so we know
exactly what version of transitive dependencies are being used.
I finally wrote up a description on our technica
2011/9/27 Frédéric Conrotte
> See this post for more infos:
>
> http://stackoverflow.com/questions/6336340/with-the-maven-release-plugin-how-to-branch-a-module-and-its-children
>
Thanks to all posters here! General rule I'm taking away is: use svn info
(if you're using Subversion).
Best,
Laird
I submitted a bug on the maven-ear-plugin:
http://jira.codehaus.org/browse/MEAR-143
I think that in the comments I'm being told that dependency management works
in a particular way that I don't see any (documentation) evidence for. I am
happy to admit I am wrong, if indeed I am wrong.
I would li
Mark, you were right:
The "Maven User" (initial poster) uses jersey together with Jersey Spring
integration:
http://repo1.maven.org/maven2/com/sun/jersey/contribs/jersey-spring/1.4/jersey-spring-1.4.pom
And if you take a peek at POM above, it does declare ranges. So, even if
"Maven user" does not
Hmm - digging slightly deeper, we have a direct dependency on spring-web
3.0.5.RELEASE.
But that is resolving to
org.springframework:spring-web:jar:2.5.6.SEC03:compile
I'm guessing this is a transitive dependency, but I don't see it with
dependency:tree.
On Tue, Sep 27, 2011 at 7:59 PM, Mark Der
I happen to have the same issue with a maven 3.0.3 and nexus 1.9.2.2
It happens with a couple dependencies when activated a default-to-false
profile
The dependencies which are constantly downloading the metadata are not
declared by me and a mvn dependency:tree wouldn't show them. These
dependencie
Hi,
usually, most dependencies can be found in maven central (you can browse
it here: http://search.maven.org) and by default this is where Maven
looks to resolve dependencies. If your dependencies cannot be found in
central but can be found in another repository (like codehaus, for
example),
Hi,
I am having a project that I have created in Eclipse.This project conatins
hibernate,drools.So I have added all the necessary jars in the project build
path.Now I have created a maven quickstart archetype where inside main
folder I have kept my java source and inside test directory I have ke
I've not looked at the dependency resolution code ( which I believe is mostly,
if not all now contained in the eclipse aether project ), but I've heard its
one of the darker, more mysterious and complex parts of the codebase, that not
enough many people understand - I could be wrong here tho.
I
Yes we use version ranges in our poms.
The only problem we have is speed and memory.
Everytime a build of a project is kicked off from the command line or
within eclipse maven downloads the meta data files for each dependent
and transitive dependencies. You can understand this since maven need
You can create a pom project declaring those dependencies and then add a
dependency toward that pom project in each project (don't forget to
specify pom when declaring that dependency.
Cheers,
Guillaume
Le 28/09/2011 06:52, Behrang Saeedzadeh a écrit :
Thanks for affirming this Ron. By the way
29 matches
Mail list logo
