On Fri, Oct 1, 2010 at 8:08 PM, Jon Paynter wrote:
> I suspect we are missing something in the way maven was designed to work.
> How is multi-module development intended to work?
You have it right. Maven will not go build a sibling module, it will
use what's in the local repository.
Most IDEs
I run into the same problems...
running mvn install, puts module 'A' in your local repository where it can
be found when doing a compile for module 'B'
-but-
if im doing development on both modules.. I dont want the old version of
module 'A' to be used when im compiling module 'B' - I want it to p
Have you run mvn install?
david jencks
On Oct 1, 2010, at 4:12 PM, Iron Eagle wrote:
> Hi there,
>
> I have a multi module project with a parent, module A and module B. I
> configured each module pom with the parent and added the modules to the
> parent pom.
>
> Module B depends on module A,
Hi there,
I have a multi module project with a parent, module A and module B. I
configured each module pom with the parent and added the modules to the parent
pom.
Module B depends on module A, so I added the dependency in module B. When I now
package or compile the entire project within the p
On Oct 1, 2010, at 12:38 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 1:14 PM, David Jencks wrote:
>>
>> On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
>>>
>>> We are planning to make things consistent so that this automation will
>>> be possible, e.g.:
>>> 1. Each "component"
Glad it has helped.
but id still like to know why unpack-dependencies tries to unpack a pom file
On Fri, Oct 1, 2010 at 3:21 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 4:09 PM, Haszlakiewicz, Eric
> wrote:
> >
> > I'm talking about the dependency section in the pom.xml file where yo
On Fri, Oct 1, 2010 at 4:09 PM, Haszlakiewicz, Eric
wrote:
>
> I'm talking about the dependency section in the pom.xml file where you're
> trying to unpack your artifact. It doesn't matter if the pom.xml of your
> artifact has an overall packaging of pom, if you're using the assmbly plugin
> i
On 2010-09-30 09:37, Antonio Petrelli wrote:
> 2010/9/30 Robert Reiner :
>> This Maven 2 plugin generates reports on issues retrieved from an issue
>> management system. Currently only Bugzilla is supported.
>
> Cool! But since you already licensed with Apache License v2, why don't
> you donate it
On Fri, Oct 1, 2010 at 4:07 PM, Jon Paynter wrote:
>
> you can also try adding:
> true
Thank you. That sounds like a key piece I was missing.
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
>-Original Message-
>From: Phillip Hellewell [mailto:ssh...@gmail.com]
>
>On Fri, Oct 1, 2010 at 3:52 PM, Haszlakiewicz, Eric
> wrote:
>>
>> Do you have the right type specified in your
>/project/dependencies/dependency element? If you're trying to unpack a zip
>type dependency it needs to
On Fri, Oct 1, 2010 at 3:02 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 3:58 PM, Jon Paynter wrote:
> > Also it seems I misspoke earlier:
> >
> http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
> > the copy-dependencies goal Does have listed as an ava
On Fri, Oct 1, 2010 at 3:58 PM, Jon Paynter wrote:
> Also it seems I misspoke earlier:
> http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
> the copy-dependencies goal Does have listed as an available
> option.
>
> What does your plugin configuration look like?
On Fri, Oct 1, 2010 at 3:52 PM, Haszlakiewicz, Eric
wrote:
>
> Do you have the right type specified in your /project/dependencies/dependency
> element? If you're trying to unpack a zip type dependency it needs to be
> listed as such in both the dependency element and the plugin configuration.
On Fri, Oct 1, 2010 at 2:51 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 3:46 PM, Jon Paynter wrote:
> > yeah i got the same problem. No amount of google searching seemed to
> turn
> > up a proper solution. Eventually I found this in one of the other
> > dependency plugin goals (not a
>-Original Message-
>From: Phillip Hellewell [mailto:ssh...@gmail.com]
>Sent: Friday, October 01, 2010 4:46 PM
>To: Maven Users List
>Subject: Re: Problem unpacking dependencies
>
>On Fri, Oct 1, 2010 at 3:34 PM, Phillip Hellewell wrote:
>> On Fri, Oct 1, 2010 at 3:23 PM, Phillip Hellewell
On Fri, Oct 1, 2010 at 3:46 PM, Jon Paynter wrote:
> yeah i got the same problem. No amount of google searching seemed to turn
> up a proper solution. Eventually I found this in one of the other
> dependency plugin goals (not a part of unpack-dependencies)
> false
>
> It seems to fix the problem
On Fri, Oct 1, 2010 at 3:34 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 3:23 PM, Phillip Hellewell wrote:
>>
>> Thank you very much. I will give it a try.
>
> Hmm, it's giving me this error: "Embedded error: No such archiver: 'pom'."
>
> I tried adding zip to my configuration but that
yeah i got the same problem. No amount of google searching seemed to turn
up a proper solution. Eventually I found this in one of the other
dependency plugin goals (not a part of unpack-dependencies)
false
It seems to fix the problem.
FYI - when using maven 3.0, you get a message "No such archi
On Fri, Oct 1, 2010 at 3:23 PM, Phillip Hellewell wrote:
>
> Thank you very much. I will give it a try.
Hmm, it's giving me this error: "Embedded error: No such archiver: 'pom'."
I tried adding zip to my configuration but that didn't
help. What could I be doing wrong?
Phillip
---
On Fri, Oct 1, 2010 at 3:18 PM, Jon Paynter wrote:
>
> Try something like this. It works fairly well for me
>
> (snip)
Oh, no wonder why. I was trying to use the "unpack" goal but I should
be using the "unpack-dependencies".
Thank you very much. I will give it a try.
Phillip
---
On Fri, Oct 1, 2010 at 2:02 PM, Phillip Hellewell wrote:
> Hi all,
>
> I'm using the dependency plugin to unpack artifacts, and I've ran into
> a little problem. I can leave out the tag for the artificat
> if it is an immediate dependency listed earlier in the pom.xml, but
> for a dependency of
Hi all,
I'm using the dependency plugin to unpack artifacts, and I've ran into
a little problem. I can leave out the tag for the artificat
if it is an immediate dependency listed earlier in the pom.xml, but
for a dependency of a dependency, I can't leave it out; It gives an
error :(
How come no
On Fri, Oct 1, 2010 at 1:11 PM, Anders Hammar wrote:
>> What I still don't quite understand is the documentation for
>> dependency:resolve says that it binds by default to the
>> generate-sources phase, yet when I do a mvn generate-sources, it does
>> not fetch the dependencies to my local reposit
On Fri, Oct 1, 2010 at 1:14 PM, David Jencks wrote:
>
> On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
>>
>> We are planning to make things consistent so that this automation will
>> be possible, e.g.:
>> 1. Each "component" will live in a specific place in SVN (e.g.,
>> /components/COMPNAM
On Fri, Oct 1, 2010 at 12:55 PM, Justin Edelson wrote:
> On 10/1/10 2:25 PM, Phillip Hellewell wrote:
>> So I'll know exactly what to check out for that component just from
>> its name and version, which I can get from dependency:resolve.
>
> You'll also need to create a branch from the tag when y
On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>>> that would scan all the dependencies and print out their versions,
>>> that would suffice and I could do the c
> What I still don't quite understand is the documentation for
> dependency:resolve says that it binds by default to the
> generate-sources phase, yet when I do a mvn generate-sources, it does
> not fetch the dependencies to my local repository.
>
What that means is that if you bind that plugin go
On Fri, Oct 1, 2010 at 12:36 PM, Wayne Fay wrote:
>> Is there any way to just do just the dependency resolution without
>> doing the rest of the phase?
>
> dependency:go-offline perhaps?
> http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html
Sweet, that worked great! Also
On 10/1/10 2:25 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>>> that would scan all the dependencies and print out their versions,
>>> that would suffice and I could do the checking out
On 10/1/10 2:32 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 12:11 PM, Justin Edelson
> wrote:
>> Dependencies are resolved by Maven whenever a Mojo's metadata indicates that
>> dependency resolution is a prerequisite to Mojo execution. This can happen
>> in any phase.
>
> Is there an
> Is there any way to just do just the dependency resolution without
> doing the rest of the phase?
dependency:go-offline perhaps?
http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html
Wayne
-
To unsubscri
On Fri, Oct 1, 2010 at 12:11 PM, Justin Edelson wrote:
> Dependencies are resolved by Maven whenever a Mojo's metadata indicates that
> dependency resolution is a prerequisite to Mojo execution. This can happen in
> any phase.
Is there any way to just do just the dependency resolution without
d
On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>> that would scan all the dependencies and print out their versions,
>> that would suffice and I could do the checking out myself.
>
> does mvn dependency:tree do what you
Dependencies are resolved by Maven whenever a Mojo's metadata indicates that
dependency resolution is a prerequisite to Mojo execution. This can happen in
any phase.
Justin
On Oct 1, 2010, at 2:04 PM, Phillip Hellewell wrote:
> It appears that dependencies get downloaded from a remote reposit
It appears that dependencies get downloaded from a remote repository
to local repository during the "compile" phase, but which goal of the
compile phase does that?
Is it just the compiler:compile goal? If so, does that mean I can't
fetch dependencies to my local repository without also doing a
co
On Oct 1, 2010, at 8:29 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 9:10 AM, Justin Edelson
> wrote:
>>
>> There's nothing in Maven or the core plugins that will do this for you
>> out of the box. But there's also nothing stopping you from writing a
>> plugin to do this yourself. The
Hi
I used to have in my multiproject in maven1 a dashboard report with a
summary with the test results of each modules.
How can I set up maven so that it will create a similar report like that in
maven 2, with 1 line per module and the total of tests, number of failing
tests, pass rate, etc?
Reg
Dear Maven Users,
I am using the maven-deploy-plugin to deploy snapshot builds to a shared
repository. This works fine for all my "standard" projects, but I have one
project that uses the maven-pde-plugin to build an Eclipse plugin, and this
involves attaching an extra artifact to the build. My
On Fri, Oct 1, 2010 at 9:17 AM, Antonio Petrelli
wrote:
>
> I think all of this mess is solvable by using a private Maven
> repository, like Nexus.
> If I understand you correctly, you want to do this since you cannot
> access to a pre-built version of B. Deploy a repository, you'll
> (development
On Fri, Oct 1, 2010 at 9:10 AM, Justin Edelson wrote:
>
> There's nothing in Maven or the core plugins that will do this for you
> out of the box. But there's also nothing stopping you from writing a
> plugin to do this yourself. There are core Maven plugins which do parts
> of this (primarily dep
2010/10/1 Phillip Hellewell :
> On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
> wrote:
> I want Maven to help check out B for me (and other dependencies). I
> can check out A manually, but I want Maven's dependency mechanism to
> find B in the (local or remote) repository, and instead of copyi
On 10/1/10 11:03 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
> wrote:
>> If you control B this is not necessary. Simply add a dependency to a
>> snapshot of B and, when you build B and, after it, build A, the latter
>> will get the latest build of B.
>> Or am I
On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
wrote:
> If you control B this is not necessary. Simply add a dependency to a
> snapshot of B and, when you build B and, after it, build A, the latter
> will get the latest build of B.
> Or am I missing something?
Yes, of course I can check out B,
My pom structure is: pom.xml has a parent: parent-pom.xml.
Both have a section to include files.
The (child) pom.xml is executed directly and has the effect of only copying
the child's resources. Commenting out this resource section, results in
the parent's resources being copied.
I believe
2010/10/1 Phillip Hellewell :
> In case I want to make changes to the dependency.
>
> This won't be the general workflow, but if I'm working on artifact A, which
> depends on artifact B, and I notice a change needs to be made to B, rather
> than have to manually checkout B and make changes there, I
On Thu, Sep 30, 2010 at 5:18 PM, Brett Porter wrote:
>
> Yes, though native support for (8) isn't particularly strong or easy.
> Different Maven plugins tend to help with that support in specific domains.
Thanks. Now I just need to figure out exactly how do to all of this.
I'll take a look at N
In case I want to make changes to the dependency.
This won't be the general workflow, but if I'm working on artifact A, which
depends on artifact B, and I notice a change needs to be made to B, rather
than have to manually checkout B and make changes there, I want to make it
more seamless by provi
thanks! -Marshall
On 10/1/2010 6:31 AM, Benjamin Bentmann wrote:
> Marshall Schor wrote:
>
>> Is a workaround (until Nexus is patched), to use
>> -Dmaven.metadata.legacy=true on
>> the maven command line?
>
> The workaround is no longer necessary to deploy Apache snapshots, r.a.o has
> been upd
Marshall Schor wrote:
Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
the maven command line?
The workaround is no longer necessary to deploy Apache snapshots, r.a.o
has been updated to Nexus 1.8.0 by now.
Benjamin
-
Thanks ,
i do it now.
Tom.
2010/10/1 Antonio Petrelli
> Please ask Mojo project:
> http://mojo.codehaus.org/sql-maven-plugin/mail-lists.html
>
> 2010/10/1 Tom Joad :
> > Hello all,
> > I'd like to know how to retrieve sql select results with sql maven
> plugin. I
> > tried output.log but
> > i
Please ask Mojo project:
http://mojo.codehaus.org/sql-maven-plugin/mail-lists.html
2010/10/1 Tom Joad :
> Hello all,
> I'd like to know how to retrieve sql select results with sql maven plugin. I
> tried output.log but
> it doesn't work.
> Thanks in advance.
>
> Tom
>
---
Hello all,
I'd like to know how to retrieve sql select results with sql maven plugin. I
tried output.log but
it doesn't work.
Thanks in advance.
Tom
Hi,
acually I´m working on a SAP Web AS integration, so I need to access some
classes from external 3rd party jars.
these jars seem to be OSGI bundels, with a MANIFEST.MF containing for
example:
Require-Bundle: com.tssap.sap.libs.logging
Bundle-Vendor: %provider.name
Bundle-ClassPath: lib/sap.
2010/9/30 Phillip Hellewell :
> The biggest question for me is in how these all fit together, e.g., is it a
> normal mechanism to want to fetch an artifact into the local repository,
> copying and extracting it to a subfolder, and then (if it includes source)
> compile it when compiling the "parent
54 matches
Mail list logo
