I'm executing mvn deploy and get the debug output at the bottom of this
message (see the latter portion of that debug output). There's no exception,
but the file isn't getting put into the repository. In my pom I have
following:
deploy-repository
ftp://ro
binding to the test phase? (i.e.
should I remove it altogether?)
matinh wrote:
>
> On 03 Dec 2007, lightbulb432 wrote:
>
>>
>> How can I find out the default plugin executions? For example, how would
>> I
>> know that maven-clean-plugin or maven-site-plugin isn&#
How can I find out the default plugin executions? For example, how would I
know that maven-clean-plugin or maven-site-plugin isn't automatically in the
build lifecycle (therefore requiring me to do a mvn clean or mvn site
specifically or adding it as an execution in pom.xml)?
Also, why does mvn c
I have unit tests and integration tests in /src/test/java (e.g.
Class1UnitTest.java and Class1IntegrationTest.java), and I'd like to have
and cause only unit tests to run during the
development profile, but to cause the unit and integration tests to run
during the integration-testing profile. Ho
ne:
> mvn eclipse:clean eclipse:eclipse -DdownloadSource=true
> -DdownloadJavadocs=true
>
> Hope this helps.
>
> Yaakov.
>
>
> On 11/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>> This was answered on October 31. on this list. Check the archives for a
>
> ../project-a
> ../project-b
>
>
>
>
>
> On Thursday 08 November 2007 16:44, lightbulb432 wrote:
>> Is it possible to specify, as a dependency, another Java project within
>> Eclipse? If I have project A that depends on pro
Is it possible to specify, as a dependency, another Java project within
Eclipse? If I have project A that depends on project B and both are
Maven-managed projects, my current options are as follows:
- package and install project B everytime it changes, then run mvn
eclipse:eclipse of project A to
When I run the mvn install, install:install, or install:install-file command,
only the JAR itself is put into my local repository. How can I get the
source, Javadocs, and other things to also be put into the local repository?
I looked at the following link for any parameters to add, but nothing
r
At a particular source control location, how can I run the eclipse:eclipse
command to turn the file structure into a Java project with a its .classpath
file automatically configured?
The location to which I'm referring has the following folder structure.
root
->pom.xml*
->other folders
->projec
Where's the best place in the standard Maven layout to place configuration
files - I don't mean resources that end up bundled with the classes and
which are available on the final classpath, like property files.
By configuration files, I mean things like development-time web server
scripts that a
How do you exclude a JAR file "A" when you don't know what dependency B
transitively includes A as a dependency? I have a lot of dependencies that
Maven gets from the public and internal repositories - naturally, Maven
retrieves its dependencies too.
Rather than looking through 75 POM files to fi
ote:
>
> I'd assume that it's there so that you can run your app from the IDE -
> that's the behavior I'd expect.
>
> Larry
>
>
> On 5/16/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
>>
>> Why are dependencies with a scope of "run
Why are dependencies with a scope of "runtime" added to Eclipse's .classpath
file? I thought the point of runtime is that it's not a compile-time
dependency; therefore, why the addition to the .classpath?
Perhaps someone can correct me, but my understanding of runtime scope is
that it is not incl
Am I right to assume that the "provided" dependency scope should appear in my
.classpath file when I run an eclipse:eclipse, but it should not appear in
the generated WAR when I run a package/install/deploy?
Right now it's not appearing in my .classpath, which seems wrong...
Thanks.
--
View thi
To add to my confusion in this thread, there's the element
that has a and element.
I'm really confused!
lightbulb432 wrote:
>
> I added a snapshotRepository element in addition to the repository element
> in the distributionManagement section of my pom.xml. Howeve
JAR" would have all the
> other 100 jars (that he depended upon transitively) bundled inside it.
>
> Is that what you want? Or what?
>
> Wayne
>
> On 5/10/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>> On 5/10/07, lightbulb432 <[EMAIL PROTECTED]> wrote
How can I create a project for the sole purpose of its pom.xml serving as a
place to organize several dependencies. For example, if I have a main
project that depends on 100 JARs, could I get this main project to depend on
4-5 subprojects whose sole purpose is to specify a subset of those JARs?
T
I'd like to specify based on properties in profiles.xml some values for
Eclipse's .classpath file. How could I do this? (i.e. Where in the
profiles.xml you could specify the path of a Java Build Path variable, for
example, and the generated .classpath file for the eclipse:eclipse goal
would contai
ssarily a "build
> management best practice". I just would advise you to think long and hard
> about what you're about to do before doing it, though.
>
> Wayne
>
> On 5/7/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
>>
>> What's the difference
What's the difference between a regular repository and a snapshot repository
as specified under distributionManagement? I've tried using both types, but
I didn't see any difference...
Also, does ending the version number of a file in SNAPSHOT have something to
do with this?
Is it okay to end a
see this directory structure in the binary
> repository. it's in the source repository ).
>
> Furthermore, users use pom.xml ( this is where you do your mvn
> whatever:command ), while maven uses the .pom files ( ...i think for
> resolving dependencies ).
>
> Cheers,
> Fran
Any word on when Maven2 support for mevenide in Eclipse will be available?
Milos Kleint wrote:
>
> yup. exactly as you assume.
>
> the eclipse related code at mevenide only supports maven1. The only
> maven2 related codebase we have currently is the netbeans module.
>
> Milos
>
> On 10/30/0
I had a missing dependency on JAR files for JTA when I tried to build a
project, so I did a mvn install:install-file as suggested. The JTA jars that
I downloaded were correctly put into the repository, and in its .pom file I
noticed that it was prepopulated with information about its ,
, , and /.
I'm using JDK 1.5 but for some reason Maven gives a compiler error saying
"use -source 5 or higher to enable annotations". How can I tell Maven which
compiler to use?
I don't know much about Maven so I don't know where to change the setting -
would it be a project-level setting, would it be a cus
NFO] jar:jar
> ...
> [INFO] Building jar:
>
> Then from there, you can take a look at the to
> see whether it really was created.
>
> The same goes for non-jar modules...you would have something like
>
> [INFO] Building
> ...
> [INFO]
> ...
> [INFO] Buildin
I want to build a multi-module project from the following pom, but I'm not
sure if I'm doing it correctly. The POM of the containing project is below:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/1.1/axis2-1.1.pom
When I do a "mvn package" in that directly aft
When I do a mvn -e compiler:compile in the root of my project with a pom.xml
in it, I get the following output. It doesn't work, and I'm not sure why.
Any ideas how I can get it to work?
It's saying that it can't find the file from the remote repository, but
those files were all automatically do
tion/introduction-to-the-pom.html
> ( official version )
> [2]
> http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle
> ( wiki'd version )
>
>
> lightbulb432 wrote:
>>
>> I understand there are Eclipse IDE plugins, but from downloading and
>&
How can I use Maven with external libraries that don't have Maven support?
For example, my application uses libraries from sources that I get from
CVS/SVN, and while there are some libraries that have Maven support (meaning
there are plugins, repositories, etc that make it easy to get the source
u
I installed Maven, created a repository, but it created it in the default
location which is not where I wanted it to be. I tried changing to the
directory I want it to be and re-ran the command, but it didn't create the
repository in that location.
How could I make a brand-new repository in the l
t is dynamically loaded from
> the pom.xml (or from the parent and child pom.xml files if there are
> embedded child modules).
>
>
> On 2/14/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
>>
>>
>> Oh wow, that sounds handy.
>>
>> Now is there an Ec
, and tags.)
Is this layout flexible, or do Maven's usual rules for directory structure
dictate a certain layout when combined with version control layouts?
lightbulb432 wrote:
>
> What's the difference between Maven and version control repositories when
> you're using b
ies in one place, and generate the other.
>
> Wayne
>
> On 2/14/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
>>
>> My biggest point of confusion on this is the intermingling of the "Build
>> Path" set within Eclipse (which creates a .classpath file) an
ion-to-the-pom.html (
> official version )
> [2]
> http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle (
> wiki'd version )
>
>
> lightbulb432 wrote:
>>
>> I understand there are Eclipse IDE plugins, but from downloading and
>> trying one
I understand there are Eclipse IDE plugins, but from downloading and trying
one of them it seems like there's very little it actually does (at least
from what I can tell), and they're quite poorly documented for total
beginners like me.
Based on your experience, do you mostly use Maven from the c
en you can revisit this point, but understand that very few people
> in the world who are using Maven will bother to put their Maven repo
> under source control.
>
> Wayne
>
>
> On 2/13/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
>>
>> Thanks for your answer
;
> On Tue, February 13, 2007 6:40 pm, lightbulb432 wrote:
>
>> What's the difference between Maven and version control repositories when
>> you're using both? Maven has its repository, but so does my version
>> control.
>
> "repository" is the wor
What's the difference between Maven and version control repositories when
you're using both? Maven has its repository, but so does my version control.
As I'm fairly new to this, could somebody explain the division of
responsibility between Maven and version control specifically? e.g. Once
you've
I'm brand new to Maven. How can it help me manage the mess of JARs and the
corresponding source and Javadocs that generally aren't packaged within
those JARs?
Right now my projects are a mess of inconsistency in terms of storing source
and Javadocs for external libraries. Some JARs have this with
39 matches
Mail list logo
