> 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) a
Hello there,
I am a newbie maven user, looking at
http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.2.1/src/main/resources/assemblies/jar-with-dependencies.xml?view=log
.
It looks like revision 1000938 has reverted the fix for MASSEMBLY-416 (revision
783036). Is it intenti
Thanks! solved, I had to edit the .project file
On 09/01/2011 07:34 PM, Hilco Wijbenga wrote:
On 1 September 2011 05:19, Luka Stopar wrote:
Greetings!
I'm having a problem using gwt-maven-plugin. The project compiles fine, but
I cannot run it as a web application, I can only run it by doing
On 1 September 2011 05:19, Luka Stopar wrote:
> Greetings!
>
> I'm having a problem using gwt-maven-plugin. The project compiles fine, but
> I cannot run it as a web application, I can only run it by doing run
> as->maven build...->gwt:run, in which case I cannot debug the code.
What do you mean
On 01/09/2011 9:42 AM, Matta, Sunil wrote:
Ron, all: this is exactly what I have been going through over the last few
weeks.
Coming from a C++/makefile environment, this is my first foray into the maven
world.
We have 70+ projects as well, and the plan has been to only release that were
modif
On 01/09/2011 10:45 AM, Eric Kolotyluk wrote:
Interesting - thanks for sharing that.
At the moment I do not really need to change versions, I was experimenting
to see if I could understand the process. Do I have the following ideas
right?
1. I changed my version from 0.0.1-SNAPSHOT to 0.0.2
On 1 September 2011 15:51, Eric Kolotyluk wrote:
> @guillaume
>
> OK, it seems that because the version in my child POMs had version
> 0.0.1-SNAPSHOT for the parent, but the parent was assuming everything was
> 0.0.2-SNAPSHOT, things were just not building properly. Now that my versions
> all matc
Le 1/09/2011 16:45, Eric Kolotyluk a écrit :
Interesting - thanks for sharing that.
At the moment I do not really need to change versions, I was experimenting
to see if I could understand the process. Do I have the following ideas
right?
1. I changed my version from 0.0.1-SNAPSHOT to 0.0.2-
@guillaume
OK, it seems that because the version in my child POMs had version
0.0.1-SNAPSHOT for the parent, but the parent was assuming everything was
0.0.2-SNAPSHOT, things were just not building properly. Now that my versions
all match up doing a package on the parent recursively does a package
Interesting - thanks for sharing that.
At the moment I do not really need to change versions, I was experimenting
to see if I could understand the process. Do I have the following ideas
right?
1. I changed my version from 0.0.1-SNAPSHOT to 0.0.2-SNAPSHOT as a test
to see what happens. Since
Well, it also aggregates your whole build together.
If you do an 'mvn package' on your parent project, it will package your
parent and all its children. If you don't define the modules in your
parent, doing an 'mvn package' will only result in the packaging of your
parent pom.
Guillaume
Le
OK, I think I am strategy (1) - although the only thing the parent actually
agrregates is the javadoc. Or does aggregator have another meaning here?
Is there some way I can set things up so that I only have to change the
parent version and the children will all follow. The problem I ran into is
th
Ron, all: this is exactly what I have been going through over the last few
weeks.
Coming from a C++/makefile environment, this is my first foray into the maven
world.
We have 70+ projects as well, and the plan has been to only release that were
modified, followed by projects that depend on them
We started by changing the version of every module but eventually went
to a policy of only changing the versions of modules that changed.
The project was a portal with 70+ modules so it was a PITA to change all
the versions.
Not a big project overhead but we got tired of it and once we had move
The gwt-maven-plugin has its own user mailing list. You might want to
send your questions there.
http://mojo.codehaus.org/gwt-maven-plugin/mail-lists.html
On 9/1/11 8:14 AM, Luka Stopar wrote:
Greetings!
I'm having a problem using gwt-maven-plugin. The project compiles
fine, but I cannot run
Ok, it's been a while since I launched a GWT-app, but here are few pointers:
* Make sure your project has the appropriate natures (see .project
file):org.eclipse.jdt.core.javanature and
com.google.gwt.eclipse.core.gwtNature
* Make sure Google can find your modules/entry points-->Select your
pro
Yes I have, but the GWT tab is disabled and the run button also
On 09/01/2011 02:24 PM, Guillaume Polet wrote:
As far as I can see, this is not really related to Maven but rather to
the Google Eclipse Plugin.
Have you tried creating a launch configuration from the menu?
--
Guillaume
Le 1/09/2
Greetings!
I'm having a problem using gwt-maven-plugin. The project compiles fine,
but I cannot run it as a web application, I can only run it by doing run
as->maven build...->gwt:run, in which case I cannot debug the code.
I've attached my pom.xml, it may not look best, because I already did
As far as I can see, this is not really related to Maven but rather to
the Google Eclipse Plugin.
Have you tried creating a launch configuration from the menu?
--
Guillaume
Le 1/09/2011 14:19, Luka Stopar a écrit :
Greetings!
I'm having a problem using gwt-maven-plugin. The project compiles
Greetings!
I'm having a problem using gwt-maven-plugin. The project compiles fine,
but I cannot run it as a web application, I can only run it by doing run
as->maven build...->gwt:run, in which case I cannot debug the code.
I've attached my pom.xml, it may not look best, because I already did
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
For me, there are two strategies there:
1) You use the parent pom as an aggregator (your parent pom reference
its children through modules) of several projects that always work
together and make a coherent package-->parent/children should keep the
same version, it's just simpler to anyone's min
Hello,
One month ago I opened similar issue:
https://jira.codehaus.org/browse/MSITE-604
The lack of settings.xml properties interpretation by m-site-p is
really strange. Command mvn help:effective-pom reports properties as I
expected.
I don't know Maven internals, but it looks that there is no s
23 matches
Mail list logo
