Hi,
There is a separate mailing list for the m2eclipse plugin. You should
probably try that mailing list to get a quicker reponse.
Oren Livne wrote:
>
> Dear All,
>
> I am using the Maven 2 integration for Eclipse,
> http://m2eclipse.codehaus.org/
> I am trying to set a custom path for my lo
Might the problem be that you have authentication turned on for the
jmx-console? If so, turn it of and see if it makes any difference. If you
want it on you need to define a server id (the 'server' parameter for the
plugin) and add credentials for that server in your settings.xml.
/Anders
Ricky-
Hi,
Siarhei is right about the difference regarding the two goals of the plugin.
I know the deploy target works (tested with JBoss 4.2.2), so you must be
missing something. Is the right port specified? Is JBoss started?
There is some info here:
http://bill.burkecentral.com/2008/02/13/jboss-unit-t
For an example, please have a look at the parent pom for all Apache projects:
http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
This example does not specify anything regarding plugin management, but you
could do that for your scenario. Also, notice that it is located separated
from
Hi,
Is there a specific need to put the artifacts in the repository? If not, the
plugin could produce the three car files and deploy (copy) them to the
Geronimo server. The car files could be named pretty much what ever you like
as groupId, artifactId and classifiers only matters in a repository.
ry, as the
> goal is to create a plugin repository that contains many plugins and
> copy them to a remote repository so that other users can install these
> plugins from the remote repository.
>
> Lin
>
> On Mon, Aug 18, 2008 at 7:51 AM, Anders Hammar <[EMAIL PROTECTED]>
the probs we mentioned in the above posts but we
> 'd like to get your feedback and maybe even a better solution.
>
> Thanks,
>
> Lin
>
> On Mon, Aug 18, 2008 at 10:19 AM, Anders Hammar <[EMAIL PROTECTED]> wrote:
>>
>> Is it attached artifacts we're
Hi,
I've run into a problem with this rc. When using the
org.codehaus.cargo:cargo-maven2-plugin:0.3.1 plugin (the start goal), it
can't retrieve my JBOSS_HOME env. It works with mvn 2.0.8 and 2.0.9, but
with 2.0.10-RC9 the plugin gets 'null' for some reason.
Here's my plugin configuration from m
Also tried the 1.0-alpha-5 version of the cargo maven2 plugin (with mvn
2.0.10-RC9). Same problem.
/Anders
Anders Hammar wrote:
>
> Hi,
>
> I've run into a problem with this rc. When using the
> org.codehaus.cargo:cargo-maven2-plugin:0.3.1 plugin (the start goal), it
top-container
> post-integration-test
>
> stop
>
>
>
>
>
> Marc.
>
> Anders Hammar a écrit :
>> Also tried the 1.0-alpha-5 version of the cargo maven2 plugin (with mvn
>> 2.0.10-RC9). Same problem.
>>
>>
Yes, you're absolutely right. Changing to "env.JBOSS_HOME" did the trick. It
now works with 2.0.10-RC9.
There must have been some kind of "bug" in the older maven releases that
made it work without the pre "env.".
Thanks,
/Anders
davidkarlsen wrote:
>
use to file a JIRA issue? It would be simplest if I have
> something that's supposed to "just work" that I can run in the debugger
> to figure out where it's coming up with the null.
>
> I'll see what I can do with this information in any case.
>
> Th
I'm not sure about the optional tag, but it does apply to version.
DependencyManagement is where you can specify the version to use for
transitive dependencies.
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management
/Anders
softwarepills wro
ency that someone has set as compile but in your context is
> provided, right?
>
>
> Anders Hammar wrote:
>>
>> I'm not sure about the optional tag, but it does apply to version.
>> DependencyManagement is where you can specify the version to use
I've run into the same problem with specifying workingDirectory as a system
property on the command line. Couldn't find a jira filed by you (or anyone
else) so I created one:
http://jira.codehaus.org/browse/MRELEASE-382
Please update it regarding basedir also not being picked up!
/Anders
torste
Hi Torsten,
Found this old post. Any progress? I'm looking into this for a customer and
is working on some best practise for releasing with clearcase through Maven.
Have you tried working with branches?
/Anders
torsten.reinhard wrote:
>
> Hi,
>
> I´m trying to establish our ReleaseBuild wit
Hi,
I've spent quite some time getting the release and the scm plugins to work
together with cc, so I'll try to help you. However, could you try to define
you problem in more detail?
If the problem is the error message you link to, have you really verified
that the view doesn't exist in cc? Me m
Hi,
I've seen the same behavior where version and versioning->release is
different in Nexus. Not sure exactly what it will affect. Possibly that is
the reason for your problem.
What happens if you remove the 1.2.0 artifact from (or even better any
version of that artifact) your local repo and the
Hi,
I think you want to try the jboss-maven-plugin and do a remote deploy. This
is described here:
http://osdir.com/ml/java.maven-plugins.mojo.devel/2006-01/msg00208.html
Please try and let us know if it works. I haven't tried remote deploy, but i
do believe I had some issues with the local depl
Ok, but I think the timestamped snapshot file name is generated by Maven, so
it should be able to get it without querying the remote repo. And the url
for the remote repo you do have.
However, I don't know how to get the timestamped snaphot file name.
/Anders
Gerrit Brehmer wrote:
>
>> I think
Hi,
Just tried it and it works for me, both in Eclipse and from command prompt.
How are you executing?
/Anders
CheapLisa wrote:
>
> I have JUnit 4.5 as a dependency in my maven pom
> and I have imported annotations into my test case but
> it is not recognizing the @Test and @Ignore annotation
Hi,
Try the 'schemaDirectory' parameter. It's documented here:
http://mojo.codehaus.org/jaxb2-maven-plugin/xjc-mojo.html
/Anders
CheapLisa wrote:
>
> thanks! I was able to get a little further but got this error message:
>
> [ERROR] null[-1,-1]
> java.io.FileNotFoundException: \jaxb\first\sr
I wild guess would be that you have misspelled some dependency regarding
upper/lower case. If you, for instance, specify "ESBblabla.jar" Windows will
match that with the file "esbblabla.jar" while Linux will not. The same goes
for paths.
Just something I learned the hard way from an issue we had
plexus-utils-1.1.jar
>
> Or do I misinterpret the error?
>
> Stefan
>
>
>
>
> Anders Hammar wrote:
>> I wild guess would be that you have misspelled some dependency regarding
>> upper/lower case. If you, for instance, specify "ESBblabla.jar" Win
Or "*Test.java", or "*TestCase.java". That's the names surefire is configured
for by default.
(http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#includes)
I would suggest trying it in Eclipse first. If it works there, then there is
some configuration issue for Maven.
/Anders
the surefire
plugin).
/Anders
CheapLisa wrote:
>
> What's Eclipse?
>
> Also JUnit4 annotations have no restrictions on file nameing if
> annotations are used. I simply want
> to use the JUnit4 features and not name my files the JUnit 3.x way.
>
> L
>
>
w
> would happen. But I'm not sure that was a Maven problem.
>
> Justin
>
> ________
>
> From: Anders Hammar [mailto:and...@hammar.net]
> Sent: Wed 12/10/2008 6:31 AM
> To: users@maven.apache.org
> Subject: Re: Is Maven / JUnit 4.x brok
Not happy with the answers in your earlier post?
http://www.nabble.com/-ANN--Maven-Release-Plugin-2.0-beta-8-Released-td20256939.html
I believe a best practise advice is in there. Keep your stable projects in
separate trunks!
/Anders
Gunnar.Bostrom wrote:
>
> Hi,
> I have a multi module proje
I *think* Archiva has this support. I know that there is currently one
person working on tis feature for Nexus as well. I'm guessing it will be
open sourced.
/Anders
On Fri, Jun 10, 2011 at 09:17, Jiaqi wrote:
> Is there easy way to list(in table or graph) all upstream packages that
> directly o
Just to help you clean up your pom: You have some old Jboss repos declared
([1] and [2]). They should be removed.
/Anders
[1] http://repository.jboss.com/maven2
[2] http://snapshots.jboss.org/maven2
On Sat, Jun 11, 2011 at 14:36, Jamshed Katta wrote:
> Thanks Mark,
> i have posted the problem o
I think we need more info. Also, there is no "assembly" phase.
By any chance, are you using Maven 2.x and is using the assembly plugin in
some other module? In that case the problem is likely due to plugin
classpath issues in Maven 2.x - please try Maven 3.
/Anders
On Fri, Jun 10, 2011 at 11:18,
AFAIK m2eclipse does not support global settings.xml. Put it in your user
home .m2 folder instead.
/Anders (mobile)
Den 12 jun 2011 23.52 skrev "samwun" :
> Hello,
>
> I need someone's help for resolve this error.
>
> I an new to Nexus (a maven repository server).
> I have started up Nexus in loca
Have you tried executing your Maven build specifying
-Dinvoker.settingsFile= from command line on your pc. If
it works the issue is related to Jenkins. It should work as it should
override the pom configured value.
/Anders
On Tue, Jun 21, 2011 at 18:56, Asmann, Roland wrote:
> Hi all,
>
> I conf
No, I don't think so. Easiest would be to try, did you?
While on the topic, it's not ${pom.xxx} but ${project.xxx}. The former is
deprecated.
/Anders
On Thu, Jun 23, 2011 at 11:55, Erwin Mueller wrote:
> Hallo,
>
>if I set in the pom.xml information about the developers, can I use
> it
Name the folder "__artifactId__" and it will be expanded when using the
archetype.
/Anders
On Thu, Jun 23, 2011 at 20:40, Christian Schuhegger <
christian.schuheg...@gmx.de> wrote:
> Hello list,
>
> I am writing a maven archetype and it would be useful to convert an
> ${artifactId} (e.g. my.nice
Quickly browsing through the pom I don't see that you have locked down the
version of the javadoc plugin. You have done it for the site generating, but
not for the build.
/Anders
On Fri, Jun 24, 2011 at 16:14, Stevo Slavić wrote:
> Hello Maven users,
>
> When performing release of a pom project
No, you shouldn't be doing that in the parent project. As the parent project
needs to be built before the children, it will not work (or will require
some workaround). The profile you have is what I would suggest. Or, maybe
even keep this module outside of the build all together as a separate
proje
On Thu, Jun 30, 2011 at 09:13, Guillaume Polet wrote:
> It's an M2Eclipse problem. I think you should rather user their ML.
>
>
No, he's using the maven-eclipse-plugin. Not m2eclipse.
/Anders
> --
> Guillaume
>
> Le 29/06/2011 17:15, Sebastian Goldt a écrit :
>
>> Hi all,
>>
>> today, I run int
(images or whatever) you
could handle those the same way. You could bundle those in a jar and put the
jar on the classpath if you want.
/Anders
On Thu, Jul 14, 2011 at 15:58, mark.angrish wrote:
> I sent this to Anders Hammar but i thought i would cross post this to the
> community as well:
&
There is something seriously wrong with the pom. Is it a Maven 2 pom? You
haven't provided a link to it so it's hard to tell...
/Anders
On Sun, Jul 10, 2011 at 09:06, sanjana wrote:
> Hi,
>
>
> I am new to Maven.I want to build a project on orchestration using
> servicemix. I am having serious
__artifactId__ in file or directory name are replaced with the artifactId
value.
/Anders
On Sat, Jul 16, 2011 at 04:20, Sebastian Otaegui wrote:
> I have create an archetype using archetype:create-from-project out of a
> multi module project.
>
> The archetype-metadata.xml is attached and also
I don't think they can be set through configuration in the pom, but only
through system properties or a properties file.
/Anders
On Sun, Jul 17, 2011 at 19:59, Asmann, Roland wrote:
> Hi,
>
> I am trying to setup a project by configuring the archetype-plugin in my
> POM. The problem I am running
You most likely would like a parent project (inheritance) where you define
and control common stuff, like plugin configuration. Then you also most
likely want to an aggregating project to simplify build. Both could be
combined in the same Maven project.
/Anders
On Mon, Jul 18, 2011 at 18:52, Juli
http://repository.codehaus.org/ is an old repo at Codehaus that is not
controlled by Nexus. Thus, I believe it is possible to redeploy or do any
kind of modification. All Codehaus projects should deploy to the Codehaus
Nexus instance.
Regarding Nexus refusing to download due to bad checksum, you c
You will likely get better help on the cargo maven plugin asking on the
Cargo mailing list [1].
/Anders
[1] http://cargo.codehaus.org/Mailing+Lists
On Mon, Jul 25, 2011 at 18:15, John Singleton wrote:
> I have a maven war project and am using maven-cargo-plugin to deploy the
> war
> to the con
It's bad. Your builds should be environment neutral. Try to get the
configuration outside of the binary.
Also, please search the archive on this topic as it has been discussed
several times already this year.
/Anders
On Mon, Jul 25, 2011 at 22:13, Daniel Serodio (lists) <
daniel.lis...@xxx.com.b
Nexus not being able to download the index has no impact on it being able to
proxy an artifact, So that's not the issue.
You should probably move this thread to the Nexus list as clearly the repo
still exists as you can reach it through a browser.
/Anders
On Mon, Jul 25, 2011 at 19:58, Meeusen,
What I *think* Wayne is talking about is deploying the environment
configurations wrapped in jars and deploy them to the repo (you would deploy
a separate jar for each environment). And then during the actual copy to the
runtime environment pick the appropriate one (from the repo).
It does work if
If you file a jira ticket ([1]) suggesting this it could actually get
implemented instead of just being a clever idea...
/Anders
[1] http://jira.codehaus.org/browse/MNG
On Sun, Jul 31, 2011 at 17:16, Hugi Thordarson wrote:
> Hi again,
>
> >> You inspired me to do quick search for "outputDirect
wrote:
> What!? You mean the developers don't pick up messages telepathically? :o)
>
> But really, I'm not sure if it's really that clever. It's a little like
> filing a ticket saying "rm -rf ~ deletes my home directory".
>
> - hugi
>
>
> On
> I'd like to set up a plugin declaration to use the maven-assembly-plugin to
> put together a kind of standalone uber-distribution from the root.
In my opinion it's much better to put this in a separate module.
> But I
> don't want this plugin--any aspect of it, at all--to be inherited by the
chive will be deployed if
you configure the assembly plugin correctly.
/Anders
[1]
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-source-inclusion-simple.html
On Fri, Aug 5, 2011 at 21:57, Laird Nelson wrote:
> On Fri, Aug 5, 2011 at 3:23 PM, Anders
> > I guess [1] could give you some help. You would then do this in the
> > aggregator project.
>
> Right, which is what I think you were saying was to be discouraged. But
> that page says that it is common practice. From the cited link:
>
> It is common practice to create an assembly using the p
We're working on this on the Cargo dev list. For some reason the metadata
for the Cargo plugin is wrong. It should be "cargo" as a prefix, not
"cargo2". The JIRA ticket to get this fixed at Codehaus (and then synced to
central) is HAUS-2107 [1] if anyone wants to follow the progress.
/Anders
[1]
Don't repost! Someone already responded to your question the other day.
/Anders (mobile)
Den 8 aug 2011 01.19 skrev "goutham" :
> Hi
>
> I recently developed a maven plugin , which calls a set of archetype's on
my
> local machine .m2 repository to create a module structure.
>
> 1) Now i want to up
And to add to that, if you're behind a Maven proxy/manager (like Nexus,
Artifactory, or Archiva) forcing a update might still not help as the Maven
proxy also needs to refresh its cached metadata. For Nexus that happens
after 24 hours by default I believe. So if it still doesn't work, wait a day
an
Please create a ticket for this [1]. The users list is not a good way of
reporting bugs.
/Anders
[1] http://jira.codehaus.org/browse/MNGSITE
On Wed, Aug 10, 2011 at 09:13, Dmitry Voronov wrote:
> Hello!
>
>
> I think there's a minor doc flaw in the pom introduction page:
>
>
> http://maven.apa
I very much doubt this.
When build, check the console output for the install plugin. It will say
where it is installing the artifacts. I've never heard of a case where this
would not work (unless you get some very clear error in the console).
/Anders
On Wed, Aug 10, 2011 at 09:46, manukm07 wrote
I ended up writing a custom wsdl packaging type (along with a plugin to
handle it) for a similar customer use case. If there's interest I could most
likely convince the customer to donate it to some open source org.
/Anders
On Wed, Aug 10, 2011 at 11:23, Adrien Ruffie - Petals Link <
adrien.ruf..
Short answer: it's the same command
somewhat longer answer: Maven will first look in your local repo. If not
found there, it will look in the configured remote repos (and download to
your local repo if found).
Maybe reading some of the first chapters in some Maven book will give you a
better idea
The JBoss repo you're using (http://repository.jboss.org/maven2/), is an old
one which I believe has been shut down. (That's why you get access denied.)
It has been migrated to a Nexus instance at JBoss. If you search the JBoss
wiki you will find info about the new repos at that instance.
/Anders
I agree with Stephen. The issues come from the fact that the ant job does
too much, i.e. both generates the classes and compiles them. I have had my
fair share of these issues using tools in Maven which originated from Ant
land. Maven has a different approach.
One possible half-way approach is to s
Use the maven-invoker-plugin. You could have a look at nearly any of the
plugins at Apache Maven or Codehaus Mojo and see how it is used (if the
plugin's docs isn't clear enough).
/Anders
On Thu, Aug 11, 2011 at 11:47, Adrien Ruffie - Petals Link <
adrien.ruf...@petalslink.com> wrote:
> Hello, I
Or you write your own Maven plugin to give you a better Maven
experience. It's not hard!
/Anders
On Fri, Aug 12, 2011 at 10:59, Karl Heinz Marbaise wrote:
> hi,
>
> you can't directly use a plugin cause it doesn't exist
>
> But you could either use the maven-exec-plugin to call sqlloader or
The full output isn't included, but if Maven is only looking i the
'thirdparty' repo of Nexus that's very likely incorrectly setup.
I'm guessing a little bit here and basing things on the default Nexus
config. As you're using localhost I think you're using this.
There should be a proxy repo of Mave
I'm thinking ${project.basedir} combined with filtering. Or possibly
without filtering as you should never include a hard-coded path.
Are we talking about the pom that the archetype produces?
/Anders
2011/8/15 Néstor Boscán :
> Hi
>
> I need in my archetype to get the full path of a the directory
There's a chapter on this in the Nexus book [1].
/Anders
[1] http://www.sonatype.com/books/nexus-book/reference/ch04.html
On Mon, Aug 15, 2011 at 11:22, samwun wrote:
> Hi,
>
> Thank you very much for all the comment and suggestion.
>
> Can you tell me how to change my maven settings.xml file s
Hi,
The Mojo team is pleased to announce the release of the JAXB 2.1 Maven
Plugin version 1.3.1.
http://mojo.codehaus.org/jaxb2-maven-plugin
To get this update, simply specify the version in your project's
plugin configuration:
org.codehaus.mojo
jaxb2-maven-plugin
1.3.1
Rel
Somewhere in the back of my head I recall an issue that a lot of
people ran into due to the fact that some open source project included
some .java files in their jar. I might recall wrong, but I would keep
the java source files in a separate jar file (as is the de facto
standard in maven repos).
/
Today, you should really use Maven 3 which is designed to be
embeddable in tools. I have no experience myself of this, but it has
been discussed a few times on this mailing list although quite some
time has passed since the last time it was brought up. You could try
searching any of the archives.
O
Yep, I believe this is due to syntax change in a newer version of
Doxia. The source files for the site needs to be updated.
I've filed MOJO-1721 [1] regarding this.
/Anders
[1] http://jira.codehaus.org/browse/MOJO-1721
On Wed, Aug 17, 2011 at 22:00, Karl Heinz Marbaise wrote:
> Hi,
>
>> thank y
separate modules!
/Anders
On Thu, Aug 18, 2011 at 09:39, Asplund Marko wrote:
> Hi,
>
> I'm using the jaxws-maven-plugin to build a JAX-WS webservice implementation
> (packaged as an EJB jar).
> The service contract and message type definitions are stored in src/wsdl and
> they're packaged in
My understanding is that maven-embedder stopped being supported for
Maven 2 at v2.0.4 (there is no 2.0.5, 2.1.x, or 2.2.x for example).
Then it was re-introduced with Maven 3, but I'm guessing that the API
changed completely.
But I could be completely off...
/Anders
On Thu, Aug 18, 2011 at 15:31,
Does it work with command line javadoc tool?
/Anders (mobile)
Den 18 aug 2011 16.05 skrev "Benson Margulies" :
> There is exactly one java source file, for a public class, in the
> package cited below. There are no exclusions set up. Anyone have a
> clue?
>
> INFO] [javadoc:javadoc {execution: def
You could even separate out the wsdl/xsd in its own artifact(s).
That's what I normally recommend as it will then allow the client to
use whatever ws service and xml binding technology they like.
/Anders
On Mon, Aug 22, 2011 at 06:50, Asplund Marko wrote:
>
> Anders Hammar wrote:
Yes, you do this as a multi-module project. Anything else is simply
wrong (= will cause you problems) in Maven land.
/Anders
On Tue, Aug 23, 2011 at 07:31, Yuvaraj Vanarase
wrote:
> Well, this seems to me little bit odd.
> Anyways, I believe you should have multi-module maven structure project.
May I also add that try to stuff everything into one Maven project
very often isn't the best solution. Why not split the shared resources
into a separate module?
Regarding the m-assembly-plugin, it's my understanding that it will
attach the produced artifact by default ([1] and [2]). No need to use
There is a Nexus users list (see [1]). Please repost there!
/Anders
[1] http://nexus.sonatype.org/project-information.html
On Tue, Aug 23, 2011 at 08:28, Hoyt, David wrote:
> I'm trying to setup a micro repository (yes, I know they're frowned upon)
> that I can proxy with sonatype nexus v1.9.2
This should do it:
http://maven.apache.org/guides/mini/guide-wagon-providers.html
/Anders
On Wed, Aug 24, 2011 at 14:32, Marshall Schor wrote:
> In trying to do an Apache release, the release:perform goal fails when
> uploading
> to the Apache repository.
>
> I've tried 3 times, with 2 differen
I think I've seen similar issues reported with Artifactory. You should
check on the Artifactory list, but I think it was due to an old
Artifactory version or some setting in Artifactory.
/Anders
On Wed, Aug 24, 2011 at 16:02, Javed Mandary wrote:
> Dear All,
> I have an interesting c
Use a text editor and cut 'n paste? Or is this a trick question?
I'm guessing there's more to it than this though...
/Anders
On Thu, Aug 25, 2011 at 04:59, Stephane-3 wrote:
> Hello,
>
> I have a maven project with different profiles, and I would like it to have
> several modules.
>
> One "core"
No, I just don't understand what it is that is a problem. Have you
tried moving the profile from the parent pom to the core pom? Doesn't
that work?
It's often better trying to explain what you want to accomplish
instead of trying to get help for the (possibly) wrong solution you
have. I'm not sayi
Yep, I've run into a similar thing. In my case the tests were using
classes in my core project, which would have been solvable by
implementing interfaces (in a separate project). So both the tests
artifact and the core artifact would then have a dependency to the
core-api artifact.
But you know the
I get worried when I see something like
${project.basedir}/../blabla
Never EVER walk outside of your Maven project! A Maven project should
be self-contained.
/Anders
On Fri, Aug 26, 2011 at 06:34, Stephen Coy wrote:
> Resources are copied into place by the maven-resources-plugin. You need to
>
It's one of the examples in the usage page of that plugin:
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
/Anders
On Tue, Aug 30, 2011 at 11:14, frank vestris wrote:
> Hi Benson,
>
> I don't really understand what you mean by 'then use the build helper plugin
> to attach the XML f
You can find some examples here:
https://github.com/cstamas/maven-indexer-examples
/Anders
On Tue, Aug 30, 2011 at 12:35, mumbaimuru wrote:
> I am newpie to Maven. Can you tell me how to use maven-indexer to produce an
> index...?
>
> --
> View this message in context:
> http://maven.40175.n5.n
None of your xml snippets went through, which you can thank Nabble
for. You need to post them somewhere else and post the link.
/Anders
On Tue, Aug 30, 2011 at 19:15, fachhoch wrote:
> I am using pom since years and never faced this issue, all of a sudden I am
> getting Authorization failed.
>
When using Maven 3.0 on a multi-module project, this should happen
automagically (you just declare normal dependencies). If this wasn't
the case, "mvn compile" wouldn't work on a multi-module project.
Maven 2.x has some issues in this area though.
What Maven version are you using?
/Anders
On Wed
The reason is that when you only build earPack Maven tries to fetch
the deps for the repository. But you don't have web and ejbs there as
you haven't executed "mvn install".
But when you build the entire multimodule build, Maven looks in the
"reactor" (the current build context sort of) and can fin
Paste? I typed that character by character...:-)
/Anders (mobile)
Den 2 sep 2011 04.52 skrev "Wayne Fay" :
>> The reason is that when you only build earPack Maven tries to fetch
>> the deps for the repository. But you don't have web and ejbs there as
>> you haven't executed "mvn install".
>> But w
But this is a sign of something being wrong. You should not normally have to
do this.
Why do you have to do this?
/Anders (mobile)
Den 2 sep 2011 16.59 skrev "Guillaume Polet" :
> Use 'mvn clean package' instead of 'mvn package'
> Use 'mvn clean install' instead of 'mvn install'
> Use 'mvn clean d
Are you using Eclipse and m2eclipse? If so, I think it is WTP.
If you only build from CLI you don't have this problem, right?
/Anders
On Mon, Sep 5, 2011 at 14:22, Stevo Slavić wrote:
> Hello maven users,
>
> All the plugins which generate sources or resources do generate them
> in build output
Thinking about this some more, I think it might actually be the
wtp-m2e eclipse plugin that does this. You should ask on the m2e
mailing list and Fred (the author) could quickly answer if it has been
fixed in newer versions of that plugin.
/Anders
On Mon, Sep 5, 2011 at 14:35, Anders Hammar
Always specify a version number to ensure reproducable builds!
/Anders (mobile)
Den 6 sep 2011 16.26 skrev "dizzyd" :
> got this fixed, thanks for the suggestion Jason.
>
> I changed this FROM:
>
>>
>> org.mortbay.jetty
>> maven-jetty-plugin
>> 6.1.22
>>
>>
>>
${basedir}/src/main/webapp2
>> ${ba
Do you by any chance have a mirror configured in your settings.xml?
/Anders
On Wed, Sep 7, 2011 at 17:20, Leon Rosenberg wrote:
> Hello,
>
> I have following question/problem.
> We have some open source software and some commercial software. We use
> two different repositories to host them:
>
>
It all depends on what you want to accomplish.
Configuration in pluginMgmt will be used if you execute the plugin
goal specifically from CLI (like "mvn plugin:goal").
So one use case to have move the configuration to the pluginMgmt
section would be if you want to have some config for the build AND
> So the CLI case ignores anything in build/plugins?
Yes.
> What about CLI invocation of report plugins?
> Can they inherit from anywhere?
I don't think so. This has been one of the limitations wrt reporting plugins.
>> So one use case to have move the configuration to the pluginMgmt
>> section
So one use case to have move the configuration to the pluginMgmt
section would be if you want to have some config for the build AND for
when executing the plugin goal directly.
>>> I take it you mean the plugin entry in build/plugins would then just
>>> contain the groupId/artifactId
> So what you appear to be saying is that the pluginManagement execution
> configuration *is* inherited?
Yes, as pluginMgmt.
> But that you might not want to provide the execution config there if
> it is not generic.
If you mean generic for all children, then yes.
> If I understand correctly, t
> Now you're confusing me again.
> You say - below - that CLI (goal) invocations ignore the build/plugins
> settings.
>
> If so, then surely it's better to define everything in pluginMgmt, and
> just leave the build/plugins section to reference the plugin?
>
> In which case both goal and phase inv
1 - 100 of 1856 matches
Mail list logo
