Hi Franz, that seems strange. The jira indicates the problem when groupId
differs, but in the project I sent you, the groupId is all the same (as far
as I can tell).
Thanks for looking!
Davis
On 4/13/07, franz see [EMAIL PROTECTED] wrote:
Good day,
I got your email and I think I saw the
Good day,
After a quick browse to [1], [2], [3], [4], and [5] - I think they are
compiled all at once. I think it's like doing
javac -classpath source locations ...
If you want to do one java on each source location, you may have to run the
maven-compiler-plugin and provide each their own
On 4/13/07, franz see [EMAIL PROTECTED] wrote:
Good,
AFAIK, there's none. But please feel free to file a request in the jira for
that :-)
and send a patch !
J
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Good day,
Ah, yes :-) Thanks for pointing that out...then I guess the proper issue is
[1] :-)
Thanks,
Franz
[1] http://jira.codehaus.org/browse/MNG-2318
Davis Ford-2 wrote:
Hi Franz, that seems strange. The jira indicates the problem when groupId
differs, but in the project I sent you,
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the profile-added module?
Cheers,
Franz
takai wrote:
Hi Franz,
The profile-added module runs the integration tests. Usecase:
Trashes it in what way? Which files are missing?
My understanding is that when you do site:deploy it just copies to file
over, it doesn't delete from the target first. But exactly how this
works probably depends on how you have it configured.
Do you get the same problem if you have:
Hi,
I have a project that creates a tar.gz deliverable that includes unix
shell scripts. In the assembly descriptor, I have:
fileSet
directorytarget/bin/directory
outputDirectorybin/outputDirectory
includes
include*.sh/include
/includes
Good day,
Not really sure what's happening. But you may want to file a jira issue for
that :-)
Cheers,
Franz
takai wrote:
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the
Hi all,
Is it possible to analyze the dependency tree without compiling?
Compiling gives a build failure, so the following commands don't work:
mvn dependency:analyze
mvn site
--
With kind regards,
Geoffrey De Smet
-
To
On 4/13/07, Geoffrey De Smet [EMAIL PROTECTED] wrote:
Hi all,
Is it possible to analyze the dependency tree without compiling?
Compiling gives a build failure, so the following commands don't work:
mvn dependency:analyze
mvn site
I think the analyzer uses the class files to identify unused
Good day,
Try project-info-reports:dependencies to generate the dependency report (
which you can only see from mvn site ). The generated report would be in
target\site\dependencies.html
Cheers,
Franz
Jerome Lacoste-2 wrote:
On 4/13/07, Geoffrey De Smet [EMAIL PROTECTED] wrote:
Hi all,
http://jira.codehaus.org/browse/MNG-2946
Thanks for validating this.
franz see wrote:
Good day,
Not really sure what's happening. But you may want to file a jira issue
for that :-)
Cheers,
Franz
takai wrote:
Exactly.
franz see wrote:
Good day,
Are you saying
-Original Message-
From: Pilgrim, Peter
Sent: 11 April 2007 17:51
To: [EMAIL PROTECTED]
Subject: RE: Maven users in the industry
UBS Investment Bank within Post Trade Services
(Maven 2.0)
Unsubscribing myself. Finishing UBS contract. Upwards and onwards to
find the next one!
--
Hi everyone,
It seems that I've got some missunderstanding of the maven2 mechanisms,
and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
Hi,
Nothing wrong, I have a similar problem myself. If you add the release-plugin
to your POM and tell it to run the targets 'clean install' instead of 'clean
intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that
You have to change the dependency in Module 2 from version 1.12-Snapshot
to 1.12.
Doug Tanner
-Original Message-
From: Bleier Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 7:46 AM
To: [EMAIL PROTECTED]
Subject: relase plugin, multimodule-project and internal
Hey all,
I do not completely agree with some of the principles used in this
[maven-ejb-plugin] plugin when generating the client-jar for the EJB.
Currently when you tell Maven to create a client jar, it uses the same
dependencies as defined for the EJB. I think this is fundamentally wrong.
Hi all,
I am trying to migrate a C++ project to Maven2, but I have troubles to
find out the right way to go.
The current project uses a Makefile for several Unix systems (custom, no
automake used), and separate Visual Studio project files for Windows.
The artifact to generate is a shared
This shouldn't be the correct way to do this. If I'm releasing my projects,
I want to deploy the (only) release build of the projects, not install one
build and then deploy another build. This is especially true if a company
official build server will be doing the deploy--if I've done an
I am getting compilation error when I am using custom jar file,
for eg:
My web project is depend on domainmodel.jar how can I use this ?
And also how can I do also compile, build this jar then reffer this jar and
compile and build my web applications.
As this jar is used by multiple webapps.
Thanks Wayne..
I got the problem...now it fine...thanks for reply...
Wayne Fay wrote:
Looks like you're missing some dependencies you need to compile your code:
package javax.servlet.http does not exist
package org.apache.struts.action does not exist
package javax.servlet.jsp does not
You may try adding this to your pom.xml
dependencies
...
dependency
groupIdmyjar/groupId
artifactIdmyjar/artifactId
version10.1.2/version
scopesystem/scope
systemPathC:/myproject/lib/domainmodel.jar/systemPath
/dependency
...
You must
I think it should be. Anyway, I've noticed that some packaging-types force me
to do this. I however do not really find this a problem, since we have a
build-server (like you suggested), which cleans its repository (read: deletes
the local repo) before releasing. That way we always have the
You should deploy this JAR to your repository. Look at
http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html for info
on how to do this.
When it's in the repo, you can just add a dependency as you would to any other
JAR.
Of course, if the JAR is already a Maven-project, you
This would work, but only on YOUR machine... In team-projects this will cause
lots of problems. The best solution would be to deploy it to the repository
(like I said in my previous post).
Or, in case of some special JARs (in my case GlassFish and JBoss), you could
define a variable
I'm trying to deploy a 3rd party source jar, by setting the classifier
when I use deploy:deploy-file, but it is being deployed without the
classifier. It appears that the classifier is being ignored entirely.
Probably I am just missing something small and stupid. Anyone see a
problem:
I believe that sources have their own packaging-type... And classifier is
indeed unused iirc...
On Friday 13 April 2007 16:19, Siegmann Daniel, NY wrote:
I'm trying to deploy a 3rd party source jar, by setting the classifier
when I use deploy:deploy-file, but it is being deployed without the
Forgot to mention the most important thing: try packaging=java-source or
java-sources... I believe it was something like that.
On Friday 13 April 2007 16:19, Siegmann Daniel, NY wrote:
I'm trying to deploy a 3rd party source jar, by setting the classifier
when I use deploy:deploy-file, but it
Read my email again. It's not the build machine that gets the wrong thing.
It's the machine you used when you did the release:prepare. Because you did an
install on that machine as part of the release:prepare, that machine won't
download the real deployed version of the released project. So
Hi Davis,
There is source code for a plugin named maven-buildinfo-plugin, included
with the free book Better Builds with Maven, that seems to do
something like what you want (and then some). The source is in the
Chapter5 .zip file[1]. Caveat coder: you may need to read Chapter 5 to
understand
True, but since I do the release:prepare on the release-machine -- which
deletes its local repo like I wrote -- I do get the released version on MY
local machine.
Besides, cleaning out your own local repo now and again doesn't hurt...
On Friday 13 April 2007 16:37, David Jackman wrote:
Read
Setting packaging to java-source did the trick, and classifier is indeed
useless). Thanks.
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 10:27 AM
To: Maven Users List
Subject: Re: [M2] deploy-file with classifier not working
Forgot to
On 4/13/07, Rodrigo Ruiz [EMAIL PROTECTED] wrote:
Hi all,
I am trying to migrate a C++ project to Maven2, but I have troubles to
find out the right way to go.
The current project uses a Makefile for several Unix systems (custom, no
automake used), and separate Visual Studio project files for
Answer, you may need more dependencies than me...:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.9.0-SNAPSHOT/version
configuration
Ok I found it - although i'm not quite sure where the issue belongs: mvn or
antrun plugin. Here it is:
Using a project with multiple pom's the antrun plugin dependencies of the
first plugin declaration encountered will be used for all subsequent antrun
executions.
Codehaus Jira Issue updated.
A new maven2 surefire release has been made which should let all
TestNG maven2 users upgrade their version of TestNG to the latest 5.5
version.
Major benefits to upgrade:
-) You'll be able to use TestNG 5.5 with surefire finally.
-) Some issues that have cropped up in the latest version of the
Thanks for the suggestion. I did try it (using the default layout,
omitting META-INF). Unfortunately, the xmi file still doesn't make it
into the ear. Any other suggestions are appreciated.
Johan Eltes
Callista Enterprise AB
Mobil: +46 (0)708-22 41 86
[EMAIL PROTECTED]
- Using again the native plugin, create a multi-module project. The
parent would contain the C++ source code, while each child module would
be devoted to create a single OS/platform specific artifact.
I use this option. However you still need to use profile to do debug/release
type
Hi Christian,
you may have a look at
http://java.freehep.org/freehep-nar-plugin
it does quite a bit of what you suggest, though it is not perfect.
Regards
Mark Donszelmann
On Apr 13, 2007, at 11:48 AM, Christian Goetze wrote:
- Using again the native plugin, create a multi-module project.
I have XD1 HibernateDoclet running fine, but want to switch to XD2 now. Can
someone give me a working example please?
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
I have set the compiler version for the maven-compiler-plugin, but that
does not seem to affect the eclipse plugin.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
verbosetrue/verbose
forktrue/fork
On 4/13/07, Mark Donszelmann [EMAIL PROTECTED] wrote:
Hi Christian,
you may have a look at
http://java.freehep.org/freehep-nar-plugin
it does quite a bit of what you suggest, though it is not perfect.
That is pretty neat - but the devil is in the details :) For example,
you'd want various
Hello,
I'd like to generate release notes as a part of my mvn site command.
If I annotate the site.xml with the following:
menu name=Maven 2.0
item name=Introduction href=index.html/
item name=Download href=download.html/
item name=Release Notes href=release-notes.html /
Pankaj Tandon wrote:
Hello,
I'd like to generate release notes as a part of my mvn site command.
If I annotate the site.xml with the following:
menu name=Maven 2.0
item name=Introduction href=index.html/
item name=Download href=download.html/
item name=Release Notes
Hi,
I've looked at Maven, read quite a bit of the documentation, and I can't
figure out quite how to represent my current typical Ant build with
Maven. Hopefully someone here can help me.
I write a lot of console utilities in Java. These are comprised of the
original code for the utility,
I'm far from the expert in dealing with this, but Maven's assembly
plugin will do what you need: make your staging area, populate it,
and zip it up in the end.
We do something similar: I need to produce an autorun CD image:
we build, with each jar having its own directory and maven pom,
and then
Hello to all,
I have been using Maven for two weeks now and I find it very good.
It's an amazing piece of work, so congratulations on all the people that
made it (and continue to make it) possible.
I'm having an issue with it, which I'm sure somebody must have had, but I
could not find anything
Lacoste, Dana wrote:
I'm far from the expert in dealing with this, but Maven's assembly
plugin will do what you need: make your staging area, populate it,
and zip it up in the end.
We do something similar: I need to produce an autorun CD image:
we build, with each jar having its own directory
Hi !
I have to write a Maven plugin and I need to access to the active
profiles list.
For example, if I execute the command line : mvn
groupId:artifactId:goal -P profile-1,profile-2 ... I need to get in my
java classes the list of active profiles (here profile-1 and profile-2)
Does
49 matches
Mail list logo