These builds are pretty handy, but they only consist of m2 core - what
about the plugins? It appears you still need to bootstrap m2 to
obtain the latest versions of these in your local repo.
Mark
On 19/08/05, Kevin McNamee [EMAIL PROTECTED] wrote:
OK. Just what I need. Thanks.
Could you add
I've got a custom m2 plugin which I install successfully using the
normal m2 install, but when I go to use the plugin I get the error
below.
If I copy the 'maven-tomcat-plugin-LATEST.version.txt' file to an
identical parallel 'maven-tomcat-plugin-RELEASE.version.txt' file then
everything works as
On 27/08/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
That is true. We figured that most people that would like to try the
latest Maven from the Subversion repository would do a normal checkout and
built it themselfs.
If there's a general demand for the same process for the plugin we might
I was wondering if there's any command-line equivalent of the
@requiresDependencyResolution MOJO annotation? i.e. something like
m2 -d compile to resolve all compile-scoped dependencies.
This would be handy for downloading a project's dependencies when
importing into eclipse. I understand
Cool, it's here for future reference:
http://jira.codehaus.org/browse/MNG-799
Mark
On 27/08/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
On Sat, Aug 27, 2005 at 06:33:50PM +0100, Mark Hobson wrote:
I was wondering if there's any command-line equivalent of the
@requiresDependencyResolution
On 28/08/05, Brett Porter [EMAIL PROTECTED] wrote:
You can use --check-plugin-latest (I thought this was the default...)
This doesn't seem to make any difference. I'm not sure how the
bootstrap process of installing the plugins differs from a manual m2
install within a plugin dir, but the
On 28/08/05, Brett Porter [EMAIL PROTECTED] wrote:
It is the currently intended behaviour, but I wholeheartedly agree
that it is not right. If you do m2 install, you intend to use it and
it should be the default. I'll file a bug to change it.
Great, thanks Brett.
The bootstrap uses
Do you have to configure anything differently for m2 to auto-discover
plugins that aren't in the org.apache.maven.plugins groupId? For
example, I have a simple plugin POM:
project
modelVersion4.0.0/modelVersion
groupIda/groupId
artifactIda/artifactId
[added back to users list]
On 28/08/05, Brett Porter [EMAIL PROTECTED] wrote:
... for now, which was in April.
The docs are out of date. You should use your own group ID, not
o.a.m.plugins.
There are two things you need to do to make it available from the
command line:
[snip]
Great that
Hi there,
On 31 Aug 2005, at 13:14, Ralph Pöllath wrote:
Is it currently possible to use the tomcat plugin [1] with maven
2.0-alpha-3? I understand it's work in progress, but I'd like to
start playing with it if possible.
It should be - I don't believe it relies on any m2 beta features, but
Just wondering when does http://maven.apache.org/maven-v4_0_0.xsd get
updated? I noticed that it's missing
distributionManagement/snapshotRepository but not sure if it gets
updated when you publish the site?
Cheers,
Mark
-
To
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
It will next be updated when the next Maven release goes out. It will be
locked down at 2.0 final, and after that changes to the POM will cause a
model increment (4.0.1, etc).
Thanks for the clarification guys.
Mark
I've just svn up'd to the latest m2 and seem to be having issues with
using deployed snapshots of custom plugins that was working
previously.
I deploy the custom plugin with m2 -DupdateReleaseInfo=true deploy.
All seems to deploy okay, complete with the new XML metadata files.
I then delete any
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
It sounds like you've got it right. It should simply work.
what is the contents of maven-metadata.xml for the artifact and version on
the remote server? what about the various copies in the local repository?
The remote artfiact metadata is:
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
That's the problem. Will fix.
Thanks Brett - I did think that was a bit strange but couldn't find
any docs on the new metadata format so didn't look into it further.
Mark
-
To
Hmm, still having probs with this, albeit slightly different. The
remote artifact metadata now reads:
metadata
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-tomcat-plugin/artifactId
versioning
release1.0-SNAPSHOT/release
versions
version1.0-SNAPSHOT/version
/versions
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
ugh. My last fix was a bit short sighted - sorry about that.
I'll keep looking into it.
That's working now thanks.
Cheers,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Hi there,
I've got an applet that I'd like to be included in a war - both of
which are m2 projects. Is there any current or proposed way for the
war pom to specify a non-WEB-INF jar dependency?
Cheers,
Mark
-
To unsubscribe,
On 12/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
ugh. My last fix was a bit short sighted - sorry about that.
I'll keep looking into it.
That's working now thanks.
Think I spoke too soon - I'm trying this again with the proposed
2.0
On 13/09/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Mark,
it's activeByDefault and not activatedByDefault
You're right - thanks. I'll check the maven.mdo file myself next time ;)
Mark
-
To unsubscribe, e-mail: [EMAIL
Raised http://jira.codehaus.org/browse/MNG-874
Would like to set fix for beta-1 (being quite a blocker) but don't
wanna get shouted at ;)
On 13/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 12/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote
Didn't want to file a bug if this was a conscious design decision, but
with the following POM:
project
...
build
resources
resourcea/resource
/resources
/build
profiles
profile
...
build
resources
resourceb/resource
/resources
Hi Ashley,
I would see the advantages of using a Maven-specific plugin rather
than an ant-based one as being:
* Reuse of ant targets - not having to specify repeated ant tasks over
many POMs (one of the main reasons for the existence of Maven itself)
* Tighter integration with the Maven build
task such
as deploying a webapp to tomcat. So is this a summary of the build
lifecycle?
compile..package..install[ANYTHING GOES]
That's fine if it is but I just want to make sure I'm making full use
of the lifecycle.
Thanks
-AW
On 14 Sep 2005, at 13:16, Mark Hobson wrote
On 14/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
[snip]
Excuse the ill thought through syntax, especially when it comes to
the group/artifact/version values, but hopefully this would be
similar syntax as you'd use to configure any other plugin. And from
the point of view of a maven user,
On 14/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
[snip]
Well if an ant adapter was worked upon, wouldn't this mean some of
the existing plugin work is redundant, thus freeing up time? I mean
fast forward to a time where we have an ant adapter - I can't see
anyone choosing to use
On 14/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
Mark, I see what you mean about autodeducing the war file with a pure
maven plugin. However wouldn't it be easier to write a mapping layer
that passes the maven war location to the ant task and any other
properties too?
So instead of
Have you checked the assembly plugin? A good example is the one used
to package maven itself:
http://svn.apache.org/viewcvs.cgi/*checkout*/maven/components/trunk/maven-core/src/assemble/bin.xml?rev=267344
Mark
On 14/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
I also think there is a bunch
http://jira.codehaus.org/browse/MNG-895
On 13/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
Didn't want to file a bug if this was a conscious design decision, but
with the following POM:
project
...
build
resources
resourcea/resource
/resources
/build
profiles
http://jira.codehaus.org/browse/MNG-896
On 12/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
Hi there,
I've got an applet that I'd like to be included in a war - both of
which are m2 projects. Is there any current or proposed way for the
war pom to specify a non-WEB-INF jar dependency
On 15/09/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Thanks, it the meantime I had the same idea.
Do you have an advice to achieve the right naming for the jar file? (for
example domain-prod.jar, domain-test.jar and so on.)
You can use the finalName element in profile/build to customise
On 15/09/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi Mark,
This is by design. For simplicity, it is intended that profiles behave
identically to inheritence, and inheritence doesn't merge resource sets.
This may or may not be the right behaviour though - but we should discuss in
that
On 15/09/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
Well, there's one 'problem': a tomcat plugin. Why would you want
a tomcat plugin? Using tomcat is the choice of the person deploying
it. It should just have a 'deployer' plugin that can handle more than just
tomcat, and is configured using
pom.
Emmanuel
Mark Hobson wrote:
Hi there,
I'm having problems with authenticated POM URLs with the build
continuum-20050920.033000.tar.gz. Our SVN repository is accessible
via authenticated https and authenticated http internally, so I've
been trying the following and get
Isn't this covered by http://jira.codehaus.org/browse/MNG-932 ?
Mark
On 20/09/05, John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Another solution might be an attached artifact (logically attached to
the main .jar in the repository via the metadata) that
Hi all,
I have a project that is targetted for a JDK 1.4.2 environment and
implements the DOM Level 2 API that is supplied in the corresponding
rt.jar. I need to be able to build this project with m2 on a system
that has both JDK 1.5 (the default) and JDK 1.4.2 installed. The
project cannot be
Hi Ashley,
(Not sure if this should be on the mojo users mailing list?)
Are you running the svn head of maven-tomcat-plugin? I've recently
submitted a few patches that should fix that NPE. Note that there is
also a final patch (#7) in MOJO-23 that's waiting to be applied which
fixes the
On 22/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 22/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
I did a svn co https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
maven-tomcat-plugin/
which put me at revision 558.
I would like to bind tomcat:deploy to the package phase
On 22/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
I did a svn co https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
maven-tomcat-plugin/
which put me at revision 558.
I would like to bind tomcat:deploy to the package phase as it needs
to run as part of
my Continuum build - unless
On 22/09/05, Mohamed Talhaoui [EMAIL PROTECTED] wrote:
I found that maven 2 beta 1 has been released last week.
What about plugins ?
Plugins have their own release schedule, independent from maven itself.
I cannot find any 2 beta 1 plugin on the maven 2 repostory.
Are 2 alpha 3 plugins still
On 22/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
Grrr, you've made me join that list now ;)
So which message numbers should I request, assuming you posted before
I joined?
[EMAIL PROTECTED] should do the trick - looks like we need
to start some traffic there :)
Mark
For any avid readers..
On 21/09/05, Mark Hobson [EMAIL PROTECTED] wrote:
[snip]
I'm not a big fan of (1) since system-specific information will be
held within the POM. Even if I use an expression like
${java.home}/../jdk1.4.2/bin/javac, this still assumes something
about the whereabouts
What's the official stance for plugin issues that span both m1 and m2?
I opened MNG-1020 as a m2 version of MPECLIPSE-104 - is this good
practice? I know ultimately m1 plugins will become wrappers around
their m2 counterparts, but what about in the meantime?
Cheers,
Mark
On 25/09/05, Brett Porter [EMAIL PROTECTED] wrote:
There is an open JIRA for the war plugin to allow this (specifically
for applets and jnlp). It has not yet been implemented.
For those interested this is http://jira.codehaus.org/browse/MNG-896.
Mark
On 25/09/05, Brett Porter [EMAIL PROTECTED] wrote:
You can work around it by writing your own small plugin (or use the
antrun plugin), to copy the jar into place in an earlier phase.
BTW, I tried this with antrun using the maven ant tasks for transitive
deps, but encountered MNG-1017.
On 26/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
This error goes away if I delete the testResources section. As far as
I can tell I'm using the syntax specified on the plugin descriptor page.
Yep, the page is wrong :) Use testResource rather than resource
within the testResources block.
On 26/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
Works now - you know I _nearly_ tried that as a last ditch attempt,
honestly! Seems the
project descriptor isn't auto-generated from the code like I thought
it was though.
Yeah it got me first time too - not too sure why the doc differs
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote:
It will next be updated when the next Maven release goes out. It will be
locked down at 2.0 final, and after that changes to the POM will cause a
model increment (4.0.1, etc).
Anyone know if the 4.0.0 XSD has been updated for beta1? I'm still
On 26/09/05, Stephen Duncan [EMAIL PROTECTED] wrote:
I didn't see this discussed anywhere. Are there plans to bring back
this functionality on the Maven 2 plugin? If so, is there a proposed
timeline? If not, why not? Should I put a feature request against
the war plugin into JIRA?
On 26/09/05, Stephen Duncan [EMAIL PROTECTED] wrote:
My only other issue is that I need to write a plugin to clean-up my
Tomcat META-INF/context.xml file to fix the DocBase to match the war
file name, change debugging settings, etc. and have that run during
the WAR process.
Sounds like you
On 27/09/05, Brett Porter [EMAIL PROTECTED] wrote:
The intended replacement for the deprecated mode is to have a
war:inplace and war:exploded goal (like m1), that will also perform
compile first.
Ah right, no-one mentioned this - thanks for clarifying.
Mark
On 28/09/05, Brett Porter [EMAIL PROTECTED] wrote:
If there isn't already, yes. It is currently part of a TODO in the
code I think...
Done.. http://jira.codehaus.org/browse/MNG-1037
Mark
-
To unsubscribe, e-mail: [EMAIL
I believe Brett very kindly fixed this in trunk last night:
http://jira.codehaus.org/browse/MNG-230
This should fix the deploying snapshot issue with eclipse, but haven't
had a chance to check it yet.
Thanks again to Brett for getting this in before 2.1! :)
Mark
On 29/09/05, Kenney Westerhof
Hi,
I'm trying to resolve MEV-3 which led to this discussion:
http://thread.gmane.org/gmane.comp.java.picocontainer.user/723
It appears that multiproject m1 poms and project.properties are the
core problems - MAVEN-1390 and friends. What is the official maven
stance regarding these features
On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6
as included in Maven 1.1 beta 2) now deploys a complete pom instead. I
have closed MAVEN-1390 as won't fix.
Okay thanks, I just wanted to make sure this was the right way
On 06/10/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6
as included in Maven 1.1 beta 2) now deploys a complete pom instead. I
have closed MAVEN-1390 as won't fix.
Okay
On 06/10/05, Brett Porter [EMAIL PROTECTED] wrote:
They look good to me.
Thanks, they should be in the next release.
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 07/10/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
is it in your path? We find m2 in path.
Yep, the logs show it's checking the correct dirs in path, but it
still reports that it can't find m2 before proceeding to use it.
Mark
On 07/10/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Do you have try the command I wrote in my previous mail?
I've just tried that it works fine from the console.
By default, we don't use a specific settings.xml file. I suppose you don't
define the use
of an other settings.xml file in
On 07/10/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
I think I understand the pb.
When you run m2 in cli, m2 doesn't use parent in repo but find parent in
parent
directories. In continuum, we have a project directory by module that doesn't
contains the
parent pom, so m2 need to find
On 07/10/05, Jesse McConnell [EMAIL PROTECTED] wrote:
are you saying that you get each number of the download streamed to the
console?
that might be an issue with your console if that is the case, my window just
updates the number on the same line...
if you are asking about the more general
On 07/10/05, Allison, Bob [EMAIL PROTECTED] wrote:
The way I got around this issue was to alter the POM on disk (the one
uploaded into Continuum) so that it was packaging=jar and no modules. It
uploaded fine, built a single job for the whole project and checked
everything out of SCM
On 07/10/05, Russell, Mark [EMAIL PROTECTED] wrote:
I knew it wouldn't/couldn't be in the central repo. Was more looking to
see how it was handled by someone else.
The primary reason I ask is because none of the jars actually have any
version information on them, so is everyone else just
On 07/10/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
we don't have update it for the moment it will be in the next version.
You can replace maven* libs in apps/continuum/lib by 2.0-beta-3 files
So continuum has it's own version of m2 within itself? When does
continuum use it's private
On 07/10/05, Russell, Mark [EMAIL PROTECTED] wrote:
That was similar to the route I was starting down. Specifically all the
jars the come from the jwsdp were going to end up in a jwsdp group.
Primarily this was to ensure that everything from each jwsdp release
stays in one place, and it
On 10/10/05, Kees de Kooter [EMAIL PROTECTED] wrote:
Thanks Andrius. I am wondering if this is not a little inefficient,
filtering the entire dir (in my case containing some 180 files) while
I only need to do replacements in 2 files?
See also http://jira.codehaus.org/browse/MNG-791.
Mark
On 14/10/05, Frank Zhao [EMAIL PROTECTED] wrote:
Hi,
I run into a situation that the project status is Building however the
continuum is hanging there without building the project. (It is possible that
something is wrong with the project configuration).
My question is how to delete this
On 19/10/05, Pete Thomas [EMAIL PROTECTED] wrote:
I was looking for some example projects that are using M2 and have a
reasonably comprehensive set of artifacts e.g.
EAR
WARs
JARs
etc.
I read that Cargo was ported to M2 successfully in
Fantastic - thanks for all the great work everyone!
Mark
On 20/10/05, Orjan Nygaard Austvold [EMAIL PROTECTED] wrote:
Congratulations to all of you!
Best regards,
Ørjan Austvold
Brett Porter wrote:
We are pleased to announce that Maven 2.0 has been released, and is
available for
On 23/10/05, Pete [EMAIL PROTECTED] wrote:
Hi there,
I would like to use cargo to start my app server / deploy via maven ?
I'm guessing that the cargo maven plugin support will allow this ?
But I'm using M2, is the plugin M2 compatible ?
Any advice greatfully received ? e.g. any examples of
Hi Janek,
Filtering is obviously the best way to achieve this, but we need to
resolve MNG-791 first.
An alternative way which I'm using in the interim is to use profiles.
You'll need to create multiple versions of your context.xml and
configure the war plugin accordingly, e.g.:
src
|_
Hi there,
I'm trying to realign the tomcat plugin to the recent war plugin
changes and having some trouble specifying my prerequisites.
I basically want the following:
* tomcat:deploy: @execute phase=package
* tomcat:exploded: @execute goal=war:exploded
* tomcat:inplace: @execute
On 25/10/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
And I also wanted to know is it possible to use the WebDav protocol with the
repository goal instead of FTP or SCP to upload my jar?
Regarding webdav, my colleague has written a webdav wagon provider
(wagon is what m2 uses internally for
On 25/10/05, Jason van Zyl [EMAIL PROTECTED] wrote:
Howdy,
Not a whole lot but a tiny start for the Maven SCM and Maven Wagon
sites. Just enough to make people ask where the real documentation
is :-)
Maven SCM
http://maven.apache.org/scm
Maven Wagon
http://maven.apache.org/wagon
I see
Hi there,
We've been using continuum 1.0-beta-1 since it's release and it's
currently happily building away 86 projects. Now I'm wanting to
upgrade to 1.0 final - is there any easy way to migrate the data from
beta-1 to final without having to re-add all these projects? I see
the db schema has
On 26/10/05, Brian Bonner [EMAIL PROTECTED] wrote:
I presume these are both for M2? It's probably because I'm new, but
it's difficult to discriminate between M1 and M2 stuff (it's getting
easier when I see jelly references, pom3.0, etc.). Maybe some sort of
indicator for Maven2 stuff would
Hi there,
Just trying out the test-jar artifact support as detailed in MNG-932,
and not sure if the transitive dependencies are being calculated
correctly.
The situation is demonstrated nicely in it0077:
* module sub1 has a test-scoped dependency of commons-lang
* module sub2 has a test-scoped
That's great news! I loved using jetty under m1 for speed for
development and always meant to look into writing a scanner for hot
deployment.
One thing - I noticed that the plugin misses a few project
dependencies at runtime. You'll need to add the following to
JettyMojo:
On 28/10/05, Brett Porter [EMAIL PROTECTED] wrote:
I believe all should execute phase=package. For the last two, create
a custom lifecycle that binds war:inplace to the package phase, for
example. See the core-it-plugin for an example.
Thanks Brett, I've had a look but it's not clear whether I
obviously want to keep war packaging on war
projects, so is it possible to override the default war lifecycle? If
I change the role-hint to 'war' then the default war lifecycle gets
executed instead of mine.
Mark
On 29/10/05, Mark Hobson [EMAIL PROTECTED] wrote:
On 28/10/05, Brett Porter [EMAIL
On 31/10/05, Brett Porter [EMAIL PROTECTED] wrote:
You actually just need the lifecycle.xml as described in the build
lifecycle document, not the custom packaging. That lifecycle
overlay, inc onjunction with the original packaging and the
lifecycle-exploded attribute on @execute should do the
On 31/10/05, Brett Porter [EMAIL PROTECTED] wrote:
We deferred this until 2.1, as it was preferable to have a transitive
dependency-less solution in place for 2.0 rather than deferring the
whole feature.
Please file a new JIRA to track this topic.
http://jira.codehaus.org/browse/MNG-1378
On 31/10/05, Brett Porter [EMAIL PROTECTED] wrote:
I see - you are right, that was by design.
Thanks for clarifying, it seemed that way but wasn't sure if I was
missing something.
I'll have to think about the best path forward on this. Can we move it
to the dev list?
Sure, I've posted to dev
Moving to [EMAIL PROTECTED]
On 31/10/05, Franck de Bruijn [EMAIL PROTECTED] wrote:
Hi Mark,
Thanks for your reply. I have been mixing 2 things. That's at least clear to
me, now :).
Still, I do believe that the user should have the flexibility to decide
whether the 'package' goal is
Hi Piotr,
There's a similar issue open regarding including artifacts at the
root-level of a war:
http://jira.codehaus.org/browse/MNG-896
This would be for applets, JNLP apps, etc. but could be extended to
explode specified dependencies as well - maybe worth adding your use
case there to keep
On 02/11/05, Piotr Bzdyl [EMAIL PROTECTED] wrote:
Actually, I already added my comment on this
(http://jira.codehaus.org/browse/MNG-896#action_49155), but I am asking
here because maybe somebody solve this problem in other way.
So you did, that'll teach me to read properly.. :)
I currently
On 02/11/05, Piotr Bzdyl [EMAIL PROTECTED] wrote:
http://jira.codehaus.org/browse/MNG-896
BTW: when is it expected to be solved?
It's destined for 2.0.1, so hopefully soonish.
Mark
-
To unsubscribe, e-mail: [EMAIL
On 02/11/05, phillip rhodes [EMAIL PROTECTED] wrote:
I have a project that will be using hibernate, but it
appears that the hibernate plugin has not been
developed yet for maven 2.
There's plugins at mojo.codehaus.org for both Hibernate 2 and 3:
Hi Barry,
I noticed this yesterday too and raised an issue:
http://jira.codehaus.org/browse/MNG-1410
You may want to supply patches there.
Cheers,
Mark
On 04/11/05, Barry Kaplan [EMAIL PROTECTED] wrote:
Below is what I did to get a proper project to be created. Now I don't
really understand
On 04/11/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
Sorry guys, but I closed the issue with a Won't fix,
see http://jira.codehaus.org/browse/MNG-1410 for an explanation.
Should you really have a good reason this is a bug/improvement,
NOT breaking maven 2's dependency handling, you can
Hi Janek,
I also use a similar configuration, but I move all the profile-related
files into src/main/profiles, e.g.:
src
|_ main
|_ filters
|_ filter.properties
|_ java
|_ *.java
|_ profiles
|_ default
|_ filters
|_ filter.properties
|_ resources
|_
Hi Fabrice,
mvn currently mediates dependency versions using a nearest-wins
strategy. This means that the dependency version specified highest in
the dependency tree (i.e. nearest to the project being built) is used.
As a side note, I really need the highest-wins strategy - any pointers
to open
Hi there,
My colleague has written the WebDAV wagon referred to on the website
and I'm bugging him to submit it :)
It's based on apache slide and we use it fine internally. The blocker
to submitting was sorting out the slide pom on ibiblio - I've just
submitted an issue summarising the problem:
On 08/11/05, Jason van Zyl [EMAIL PROTECTED] wrote:
As a side note, I really need the highest-wins strategy - any pointers
to open issues or code required?
It's slated for 2.1.
Right thanks. Just found the issue if anyone's interested:
http://jira.codehaus.org/browse/MNG-612
And the code
Hi Fabrice,
On 08/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi Mark,
Thank you for your answer! :)
No probs.
Then I have another question: when 2 different dependency versions are at
the same level in the dependency tree, which one wins? Because in my case,
I have version 2.0 and
This discussion kinda overlaps with an issue I raised with the eclipse plugin:
http://jira.codehaus.org/browse/MNG-1412
I think the order should be nearest first, and then the order
specified in the pom.
Mark
On 14/11/05, Nigel Magnay [EMAIL PROTECTED] wrote:
The artifact being generated is
On 09/08/07, Sommers, Elizabeth [EMAIL PROTECTED] wrote:
Where is the scm for this module?
http://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree/
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 03/09/07, Alexandre Gomes [EMAIL PROTECTED] wrote:
Hi,
based on [1], how can I pass a diferent username for Tomcat Manager,
using -D command option (and not settings.xml) ?
I tried -D tomcat.server.username=root, but it doesn't seem to work.
[1]
Aside from license issues, I'm confused as to why we now have two
Maven plugins for Eclipse? Surely it'd make sense for the two
projects to collaborate to accelerate development, rather than having
two plugins that are both rather thin on the ground in terms of
features?
Mark
On 04/09/07,
Thanks - patches are welcome!
Mark
On 06/09/2007, Alexandre Gomes [EMAIL PROTECTED] wrote:
Ok Mark,
isseu created in [1].
Thanks a lot.
[1] http://jira.codehaus.org/browse/MOJO-906
[]s
Alê!
On 9/4/07, Mark Hobson [EMAIL PROTECTED] wrote:
On 03/09/07, Alexandre Gomes [EMAIL
1 - 100 of 328 matches
Mail list logo
