tomcat:deploy could possibly fork a new process performing a maven
build with the lifecycle (the docs should tell). I haven't used that
plugin as I'm a Cargo addict...:-)
/Anders
On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote:
BTW - this is totally not the behavior we're
Hi,
Thorsten Heit wrote:
...snip ...
But what puzzles me is that the archives created by Maven 2.2.1 and
Maven
3.0.3 are different, and I don't see a reason why...
...snip...
Hi there,
Did you ever get anywhere with this? I'm seeing the same problem: Maven
3.0.3 adds
Hi,
Just a wild guess, do you have a dependencyManagament handling these
artifacts where the scope is defined? I've seen different behavior
between Maven 2.x and 3.0.x due to this (MJBOSSPACK-40 [1]).
No, I haven't used dependency management. I simply referenced xerces
and/or xalan (don't
While building a sub-project where I am trying to find the jar dependency
showing up in compliation which i am not able to locate in code/pom.
Tried command ;- mvn dependency:tree
this doesnt show up the dependency tree
this jar doesnt exist on nexus even, so i wanna see where is this defined
Heh - yeah a quick look at the docs and it says:
- Requires a Maven 2.0 project to be executed.
- Since version: 1.0-alpha-2.
- Invokes the execution of the lifecycle phase package prior to executing
itself.
There's no mention of forking and all the documentation around this plugin
There has never been such native Maven support (i.e. in Maven core).
/Anders
On Tue, Sep 20, 2011 at 14:57, Maven User maven.2.u...@gmail.com wrote:
Heh - yeah a quick look at the docs and it says:
- Requires a Maven 2.0 project to be executed.
- Since version: 1.0-alpha-2.
- Invokes
In 2.2.1, this worked flawlessly.
In 3.X this (known) feature no longer works.
http://www.mailinglistarchive.com/html/users@maven.apache.org/2011-01/msg00729.html
Ok, I'm clear now :-)
On Tue, Sep 20, 2011 at 9:13 AM, Anders Hammar and...@hammar.net wrote:
There has never been such native
That's something different. I said Maven 2 core doesn't have support
for reading properties from a file. There might be plugins, but no
such support in core.
/Anders
On Tue, Sep 20, 2011 at 15:20, Maven User maven.2.u...@gmail.com wrote:
In 2.2.1, this worked flawlessly.
In 3.X this (known)
Well you are sort of right. Let me clarify.
1. yes.. Google/Android does not publish to Maven Central (although imho
they should)
2. the android4maven project, led by Robert Manning, and myself got the
android jar and some others into Maven central. This is done off the
Android Open Source
Hi
On 2011-09-20 14:30, kapila wrote:
While building a sub-project where I am trying to find the jar dependency
showing up in compliation which i am not able to locate in code/pom.
Tried command ;- mvn dependency:tree
this doesnt show up the dependency tree
this jar doesnt exist on
Hello all,
I have been asked to drive a legacy build for the first time,
and I am getting the error in the Subject above.
It is a Maven 1.0 build and supposedly has been working for
quite some time.
The console output of the action that has the error is here:
It is a Maven 1.0 build and supposedly has been working for
quite some time.
Does anyone recall this issue when working with Maven 1.0?
No, but I haven't touched M1 in a very long time. You should seriously
just spend an hour +/- converting it to work with Maven2 or M3 rather
than
On 2011-09-20 21:31, Wayne Fay wrote:
It is a Maven 1.0 build and supposedly has been working for
quite some time.
Does anyone recall this issue when working with Maven 1.0?
No, but I haven't touched M1 in a very long time. You should seriously
just spend an hour +/- converting it to work
13 matches
Mail list logo
