Hello Emmanuel,
I've seen that you closed issue CONTINUUM-780 in the meanwhile. Are there
chances to replace just one module in my Continuum 1.0.3 installation by a
snapshot version to get the fix? Thanks for a short hint in which module you
fixed it.
BTW, did you have a look at SCM-231?
On 20 Sep 2006, at 20:04, Leonard Gestrin wrote:
3. if continuum does not have the answer for the problem/questions
to 2.
can someone recommend the alternative solution/intergration server
that
would ensure that snapshots are being incrementally deployed only when
and in the right
Hello,
This is my first post to the list and I am very new to mvn/continuum
world.
We are currently using mvn snapshot features but I think we are not
using it properly. I want to move building of snapshots to build
integration machine where continuum runs and I have few questions about
how
Hi Leonard,
Comment inlined.
Hope this will help.
Raphaël
Leonard Gestrin a écrit :
Hello,
This is my first post to the list and I am very new to mvn/continuum
world.
We are currently using mvn snapshot features but I think we are not
using it properly. I want to move building of
Hi,
How can I exclude a txt file lying in java source folder while packaging
jar file. The same thing can be done using filtering to exclude a file
from resources folder but I could not find any documentation on
excluding a file from source folder.
Regards
Kapil
CONFIDENTIALITY NOTICE
This
Many thanks.
The trick was to to use the URL:
http://localhost:8080/archiva-1.0-SNAPSHOT/proxy
Raphaël
2006/9/19, Tamás Cservenák [EMAIL PROTECTED]:
You should try with
http://localhost:8080/proxy/central
Hope helps,
~t~
On 9/19/06, Raphaël Piéroni [EMAIL PROTECTED] wrote:
Hello,
I
hi u can try this
under your build tag --under resource as given below remove the
include**/*.txt/include from includes under directory
resource
directorysrc/directory
includes
include**/*.xml/include
include**/*.css/include
Thanks for you reply Manoj. I think you didn't get my question. The txt
file is in src\main\java folder and not in the src\main\resources
folder.
Regards,
Kapil
-Original Message-
From: manoj kaushik [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 12:13 PM
To: Maven Users
Hi Kapil,
In your build section define on the following format:
build
resources
resource
directorydoc/directory !-- a directory on the same level
as your pom --
excludes
excludeconfiguration.txt/exclude !-- a file in doc
directory to exclude from the JAR
Markus KARG wrote on Wednesday, September 20, 2006 7:39 AM:
Jörg Schaible schrieb:
[snip]
This does not help, since it is no POM issue! Maven may
select the version declared in the POM but it does not have
to. So it is quite brain dead for any library to define a fix
classpath in the
As previously mentioned, it is quite honestly not possible to fix
that specific version of the pom. For a very brief period of time,
Maven was allowing changes to poms but then realized this was a bad
idea. So instead the proper way to fix issues like this is to actually
release a new version of
There is no error in the POM, it in the jar's manifest and the jar is the one
published by the FOP team.
In that case (Markus), take my instructions sent 2mins ago, modify
slightly to adjust the manifest file in the JAR as well as the other
instructions, and proceed to update pom to
This email is better sent to the Continuum Users list, since it has
very little to do with Maven and most everything to do with
Continuum...
continuum-users@maven.apache.org
Wayne
On 9/20/06, Leonard Gestrin [EMAIL PROTECTED] wrote:
Hello,
This is my first email to the list and I am new to
Wayne Fay wrote on Wednesday, September 20, 2006 9:05 AM:
There is no error in the POM, it in the jar's manifest and
the jar is the one published by the FOP team.
In that case (Markus), take my instructions sent 2mins ago, modify
slightly to adjust the manifest file in the JAR as well as
That's wrong. Maven automatically creates the correct Class-Path
attributes in the manifest, and it's up to the fop team to
decide what
third party library versions to use.
No! If any library would declare a Class-Path in its deps, you could nearly use
none in combination. Just because
Wayne Fay schrieb:
As previously mentioned, it is quite honestly not possible to fix
that specific version of the pom. For a very brief period of time,
Maven was allowing changes to poms but then realized this was a bad
idea. So instead the proper way to fix issues like this is to actually
Site-deploy is how its done in Maven2. I guess site:deploy is a maven1
goal.
I just ran 'mvn site' and I do get index.html in each and every
target/site dir. Could it be that an exception is thrown somewhere in
the process?
-Ronny
-Opprinnelig melding-
Fra: Mick Knutson [mailto:[EMAIL
Markus writes:
That's why I am asking for the name of the maintainer, so that I can ask
him to do that...
As Carlos said in another email:
The repo is mantained in a no guarantees, free time basis, so your
request to get this solved asap because my client needs it doesn't fit
here.
i.e. No
i.e. No on maintains the FOP available in the repo.
It is there as a convenience only.
I might also suggest you adjust your attitude.
Sorry for beeing rude and thank you for telling me.
It wasn't my intention.
But see, I just want to know who is the guy that has write access to the
FOP's
On 9/20/06, Markus KARG [EMAIL PROTECTED] wrote:
i.e. No on maintains the FOP available in the repo.
It is there as a convenience only.
I might also suggest you adjust your attitude.
Sorry for beeing rude and thank you for telling me.
It wasn't my intention.
But see, I just want to know
A good idea, but definitely something we would need the Maven Dev team
to make a decision on... Perhaps one of them is even monitoring this
(lengthy) discussion at this point, and will start a discussion on
Maven Dev ml if necessary?
I'm not personally convinced that simply appending another
Barrie Treloar wrote:
The problem that Jorg points out is still outstanding is what naming
conventions should be used to indicate that this fixes a problem with
an already released version of the artifact.
There is no problem.
If the artifact is actually modified, then it's a different
Barrie Treloar schrieb:
Carlos did tell you who maintains it and the answer is no one.
Carlos is just one of the people who will upload your pom and artifact
if you follow the instructions on the web site.
So you are able to make the necessary changes and get it fixed.
The problem that Jorg
Markus KARG wrote:
If Carlos is able to upload it while I seem not to be, he actually is in
the role of the maintainer.
Where am I going wrong with that assumption?
Your assumption is, that he is able to change files in the repository.
The answer is he isn't. Ok, he may be able to do that
So the policy is A bug cannot be fixed?!
Jochen Wiedmann schrieb:
Markus KARG wrote:
If Carlos is able to upload it while I seem not to be, he actually is
in the role of the maintainer.
Where am I going wrong with that assumption?
Your assumption is, that he is able to change files in
Hi,
Thanks for this, how could I now tell what is the output artifact(s)
produced by the project the embedder just executed? Am I able to query it
some how from the embedder or do artifacts get attached to the original
project?
regards,
Mikko
Olivier Catteau wrote:
Hi,
I think there is
A released jar cannot be modified. A bug can be fixed, but in the next
version/bugfix of the artifact (and maybe you could provide such a
fixed artifact). All this is a community effort where everyone can
participate. It is not right to change anything in a released
artifact, because you are
Yes, this is the point of the discussion. Please search this mail list
(Nabble etc) and Maven Dev to see the entire history of this issue.
Increment version by one, upload it, and allow Maven to find the
updated version the next time your build runs, it will automatically
find and use it.
Wayne
Hi Markus,
Markus KARG wrote on Wednesday, September 20, 2006 9:35 AM:
Wayne Fay schrieb:
[snip]
This is your best approach (imo) to get this updated FOP artifact
installed in the Maven Repo. Unless of course someone else has a
better suggestion...
You asked about quality control
So since bugs once released cannot get fixed without changing the
version (what is problematic with FOP as we have discussed today), this
is one more reason for not let anybody upload things without doing
quality control. :-)
Wayne Fay schrieb:
Yes, this is the point of the discussion.
Actually I never voted for using ibiblio but just added a dependency to
fop:fop to my project, while in fact Maven 2.0.4 automatically has
choosen to pull it from ibiblio. That's why I said: Since ibiblio is
choosen automatically by Maven until manually de-configured, that
repository must
The community itself is the community control. See your case. It is
the user that reports if something fails, and maybe suggests/provides
a patch or has the patience to let other do it. Here, there is no such
a master-slave relationship where someone tells the changes and others
do. If you need
Markus KARG wrote:
So the policy is A bug cannot be fixed?!
The policy is A bug can be fixed in the next version. What else did
you expect?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Markus KARG wrote on Wednesday, September 20, 2006 9:28 AM:
That's wrong. Maven automatically creates the correct Class-Path
attributes in the manifest, and it's up to the fop team to decide
what third party library versions to use.
No! If any library would declare a Class-Path in its
Hi!
I just created my own maven2 archetype for building webapps with a set
of default files (binary files like jpg, text files like xml).
I added these files in the archetype.xml description file.
archetype
idobs-web-app/id
sources
...
/sources
resources
Markus KARG wrote on Wednesday, September 20, 2006 10:15 AM:
Actually I never voted for using ibiblio but just added a
dependency to
fop:fop to my project, while in fact Maven 2.0.4 automatically has
choosen to pull it from ibiblio. That's why I said: Since ibiblio is
choosen automatically
I expected that if the bug is not in the release but the release itself,
then the release can be undone.
All car manufacturers do that. If there is a severe bug that is likely
to kill lots of people, then they take back thousands of cars to fix the
problem on the vendor's cost.
I don't see that
Well, since I am in the business of QA for ten years now, believe me,
there can be a better one:
The bug was detected after months by incident.
A good QA would have detected it before publishing the release.
Also there still is no fix, since I am a beginner with Maven and a
beginner with FOP.
Then all the Sun JRE's are buggy. Sorry, I am using exactly this artifact for a
long time now without ever noticing that weird classpath entry. The only time
it is respected is when you start the jar as app:
java -jar my.jar
In this case your classpath theory applies. The situation is
No, the point is, that you're not satisfied with the procedure, how QA works
with Maven's public repo. While I can understand your point (being hit also by
bogous POMs), you're not going to change it. If you want have better control,
setup an own repository from scratch. Look, not even the
i didn't specify any version in the master POM.
reporting
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jxr-plugin/artifactId
/plugin
/reporting
but in my local repository i found:
Markus KARG wrote on Wednesday, September 20, 2006 10:49 AM:
Then all the Sun JRE's are buggy. Sorry, I am using exactly
this artifact for a long time now without ever noticing that
weird classpath entry. The only time it is respected is when
you start the jar as app:
java -jar my.jar
this is not for the directory structure this is a tag used in build in your
project.xml. this means the types of files u are including in the jar file.
when u dont include .txt file it will not be there in your jar file
i think it will make things clear
On 9/20/06, Kapil Gupta [EMAIL PROTECTED]
Hello,
Im pretty new to M2 I must say. Nevertheless I would like to understand how I
can do things such as calling a test class with VM arguments.
In our project we have got something similar to M2. The module has got a
descriptor in which a user can configure a unit test suite including
Markus KARG wrote on Wednesday, September 20, 2006 10:50 AM:
Why don't you think that we can change it?
You all told me this is a community process.
So community should be able to discuss, and, if needed, change it.
As Jochen pointed out, it can be fixed with a new version. From a QA's PoV
I ment I had tried this before. My conclutions was that outputDirectory
alwas was located in target dir. I think I tested this for the assembly
plugin, and it might be that there are a difference between these two.
-Ronny
-Opprinnelig melding-
Fra: dan tran [mailto:[EMAIL PROTECTED]
As said, the situation is different on AppServers. Neither jBoss nor WebLogic
complain. IONA's possibly would, but it's abandonned. WebLogic *does* respect
the classpath entry of the EJB artifact itself though.
That's not part of this discussion I think.
We have discussed EJB problems
As Jochen pointed out, it can be fixed with a new version. From a QA's PoV you
cannot change a reelased version ever. See, we have relesed own artfiacts using
FOP as dep. If POM or the artifact itsefl would change now, or build is no
longer consistent. Even worse, the build could then be
Hello,
I m programming an ant plugin for maven2. I need to execute a java
command and handle the path of some dependencies of the plugin to
include them in the plugin's classpath and handle the absolute path in
order to execute the java command.
My questions:
1 / Is it right to declare all
Yes, the jar has the class files. As I said in the first sentence of my
email, this has been working fine on another machine with the exact same
jars and sources. The jar came with the toolkit.
One thing I forgot to check yesterday was the Java version. I knew both
systems were running JDK 5
Markus KARG wrote:
But it would be beneficial for you since I would change it in a way that
FOP is valid for everyone, so you can remove your workarounds.
Since in your case the Class-Path isn't taken into account anyways as
you wrote, what have you lost?
It is strange that you as the
It looks like this was caused by a problem fixed between JDK 5.0u1 and
JDK 5.0u5. I installed the latest JDK 5 on my new machine and the
problem went away.
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 05:38
To: Maven Users List
Karl Uppiano wrote:
WebLogic 9.2 does not like the manifest entries…
Extension-Name:
Specification-Vendor:
Implementation-Vendor:
Implementation-Title:
Implementation-Version:
…in the manifest unless I implement the WebLogic SSPI interfaces, which
is not on our schedule. I would
Markus KARG wrote on Wednesday, September 20, 2006 11:05 AM:
As Jochen pointed out, it can be fixed with a new version.
From a QA's PoV you cannot change a reelased version ever.
See, we have relesed own artfiacts using FOP as dep. If POM
or the artifact itsefl would change now, or build is
Dear list,
Last time I looked, Maven wasn't supported 'out of the box'. I've
just written a blog entry about how to make it work, if anyone's
interested: http://jroller.com/page/malformed?entry=emacs_maven_2
Rob
-
To
Hi,
one guy on this mailing list already had such a case: the problem would come
from the fact that he didn't specify his source directory properly in his
POM. And you problem is probably the same: I can see that because the
generated HTML files are place in the folder \target\site\xref\java. So
Hi Lakshman,
Thanks you for your answer.
Between which tags repositories tag has to LOCATE in user's
settings.xml file?
Thanks,
Roman
-Original Message-
From: Lakshman Srilakshmanan
[mailto:[EMAIL PROTECTED]
Sent: Monday, September 18, 2006 2:53 AM
To: Roman Gelfand
Cc: Maven Users
I have problems bulding an example in xFire and iam new to maven , please
help me with this .
C:\work\xFire\1.2.1\xfire-1.2.1\examples\purchase-ordermvn install war:war
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'war'.
[INFO] org.codehaus.mojo: checking
Hello all,
Please help to get out of the following confusions:
I am having many projects which may be dependent on each other or not.But we
need to make one ear having all the archives file made of all projects.
In one project, we can have one jar,jar+war,jar+war+har,or some other
application
I'd like to change the template for the team-list page [1]. How can I do it?
It seems to come from the 'project info reports' plugin, but I don't
see any options that look useful:
http://maven.apache.org/plugins/maven-project-info-reports-plugin/project-team-mojo.html
[1] I'd like to get rid
Hi. There is a requirement where a single Maven build needs to produce
both a jar and a war in the same project. The packaging element can
neither be a .jar nor a .war. I am not sure what it should be. The
only thing I could think of is trying to fork parallel builds within the
Maven package
thx, for your reply.
i just ask myself, is there any project.property that points to the current
source directory?
Since i'm using a parent POM (where i define my plugIns) and some child-poms
that are derived from that parent, i can not declare absolute pathes to the
source-directory. i would
Hello:
See the FATAL ERROR from captured maven output below.
In context, the native maven plugin is being used to compile a C++
source file, prior to linking an .exe application.
Has anyone seen this sort of thing before? Thanks.
Brad
recmods.cpp
[INFO] cl /MT /W3 /GX /DWINDOWS-X86
I made the same mistake a few weeks ago. This is certainly a subject that
should be more clearly addressed in the documentation.
Andreas
-Original Message-
From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006 11:41 PM
To: archiva-users@maven.apache.org
thanks that information helped me out.
Simply changed:
build
sourceDirectorysrc/main/sourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
/build
to:
build
sourceDirectorysrc/main/java/sourceDirectory
Jörg Schaible [EMAIL PROTECTED] wrote on 09/20/2006
03:24:46 AM:
(*) New release of JMock 1.1.0 still uses cglib:cglib-full:2.0 as
dependency although this breaks any app using Hibernate 3.x or
Groovy. Better would have been to use cglib:cglib-nodeps:2.1_3, but
as the official docs state
We are still supporting Java 1.3. Can I run the same unit tests using two
different JVMs with surefire:test. Can I also get a report for the two sets
of testing.
Thanks
Neil
This has always been my approach to get rid of dependencies that were
annoying me. It can have some unintended consequences so make sure you
testing everything after adding exclusions to your poms. ;-)
If someone has a better way, or something specific to this cglib
issue, I'm open to
fop 0.20.5 pom was provided by Joerg Schaible
http://jira.codehaus.org/browse/MEV-386
That was at the point we allowed changing poms in the repo, now it is
not possible to change that pom.
Please create new threads for any other related questions, this one is
becoming unmanageable.
I'm now
2006/9/20, Andreas Guther [EMAIL PROTECTED]:
I made the same mistake a few weeks ago. This is certainly a subject that
should be more clearly addressed in the documentation.
Andreas
Obviously, but I think there is not yet any documentation ;) (if i
correctly saw in the sources)
Raphaël
Hi,
Perhaps you we need to split your project into 2 projects, one with a jar
packaging and an other with a war packaging then use a multi project build.
Regards.
On Wednesday 20 September 2006 15:49, Morgovsky, Alexander (US - Glen Mills)
wrote:
Hi. There is a requirement where a single
Hi Greg,
[EMAIL PROTECTED] wrote on Wednesday, September 20, 2006 4:45 PM:
Jörg Schaible [EMAIL PROTECTED] wrote on
09/20/2006 03:24:46 AM:
(*) New release of JMock 1.1.0 still uses cglib:cglib-full:2.0 as
dependency although this breaks any app using Hibernate 3.x or
Groovy. Better would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
For some reason I am getting builds that are stuck in the building
mode even though the build process has long gone away. is there a quick
way of clearing these out of the status screens?
Thanks,
Johan
- --
you too?
-BEGIN PGP
Hi, I'm trying to checking out 2 subversion modules, Mod1 and Mod2, but,
Maven2 checks out the same module, Mod1, twice.
How can I perform this?
Here is part of my pom.xml:
...
plugins
plugin
artifactIdmaven-scm-plugin/artifactId
executions
Jörg Schaible [EMAIL PROTECTED] wrote on 09/20/2006
10:34:26 AM:
Hi Greg,
[EMAIL PROTECTED] wrote on Wednesday, September 20, 2006 4:45
PM:
Jörg Schaible [EMAIL PROTECTED] wrote on
09/20/2006 03:24:46 AM:
(*) New release of JMock 1.1.0 still uses cglib:cglib-full:2.0 as
What is this plugin then:
http://www.ibiblio.org/maven2/doccheck/maven-doccheck-plugin/1.4-0.1/
Is this just the plugin?
On 9/19/06, Shinobu Kawai [EMAIL PROTECTED] wrote:
Hi Mick,
Does anyone else have doccheck running?
The DocCheck plugin is only for M1.
For usage with M2, please see
Right, there is only the index page: http://maven.apache.org/archiva/
Andreas
-Original Message-
From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 8:21 AM
To: archiva-users@maven.apache.org
Subject: Re: [Solved] Proxing a repository
2006/9/20, Andreas
ReportSets is not valid:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.1-SNAPSHOT/version
reportSets
reportSet
idhtml/id
Hi Finn-Robert,
Sorry to reply just now but I made a lot of tests.
First, I understood why I had this message
Embedded error: Reference maven.plugin.classpath not found.
It's because of a bad version :
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
If I used the
mbatth [EMAIL PROTECTED] wrote on 09/20/2006 12:09:01 PM:
Hello,
I am very new to maven, so please pardon my extremely newbie questions.
I
have a need for standardizing the common framework and components in my
organization. So, i am thinking of managing the frameworks or componets
via
i think you need systemProperties tag; sample bellow:
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
skipfalse/skip
systemProperties
property
nameHOST/name
value${host}/value
I have added the test plugin 1.8 dependency to projectRoot/etc/project.xml, and it caused a build failure. What did I do wrong? and what does this error mean? and How can I correct this build failure caused by this?
here is the dependency I added to the project.xml
dependencies
hi all,
i m trying to run my tests using maven2 and testNG
i followed instructions at http://testng.org/doc/maven.html
here's my pom
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0
This, and the previous fop thread, has made me think about what happens with
versioning and simple fixes.
For example
A-1.5 depends on B-1.0
B-1.0 depends on C-2.0
Now there is an API compatible fix in C, and the version is changed to
C-2.0.1. Now for A to get the bennifit of this change
On 9/20/06, diroussel [EMAIL PROTECTED] wrote:
Now, I'm not a .NET expect, so correct me if I'm wrong. But according to
the CLR book [1] one of the ways the CLR is better than the java JVM is the
handling of versions and version meta-data.
...
Does that make sense? Do people think a similar
Hi Marco,
On Sep 20, 2006, at 10:56 AM, Marco Mistroni wrote:
hi all,
i m trying to run my tests using maven2 and testNG
i followed instructions at http://testng.org/doc/maven.html
You need to have a testing.xml.
See http://www.nabble.com/product-codes-at-java-1.4%2C-test-sources-
Just read the output: it means that one of your tests failed. :) Check
the files generated in target/test-reports/, run maven with -e, check
the properties of the test plugin to ignore test failures/errors [1],
and either fix the test or your code! :)
-Lukas
[1]
On 9/20/06, diroussel [EMAIL PROTECTED] wrote:
This, and the previous fop thread, has made me think about what happens with
versioning and simple fixes.
For example
A-1.5 depends on B-1.0
B-1.0 depends on C-2.0
Now there is an API compatible fix in C, and the version is changed to
C-2.0.1.
I see the following plugins in my local .m2 repository:
maven-jar-plugin 2.1
maven-rar-plugin 2.1
I have tried providing a custom MANIFEST.MF, but it simply merges it with the
default entries. I am packaging a RAR file, if that is significant.
Regards,
Karl
-Original
Hi,
i have a question about release of project that uses parent pom
dependencyManagement to declare dependency versions.
this is the src structure
products/web1/
products/web2/
shared/webcommon/
shared/common/
shared/pom/--contains parent pom.xml (version=1.0-snapshot) that
defines the
I dont think the structure you have would work with release plugin, there ar
JIRA on these issues on using
relative paths to search for parent pom.
You must the have the root pom at the top level. and all subprojects share
the same versionid
(ie use release plugin to release all project in one
It sounds like the JAR plugin v2.1 has added code so these entries are
*not* added, but the RAR plugin v2.1 has not, and so they are added.
I don't use RAR plugin so you can consider this an educated
guess/assumption on my part... Until someone else chimes in and
confirms it.
Wayne
On 9/20/06,
Please check the archive, there are some talks about getting Continuum to do
that for you but not Maven command line.
-D
On 9/20/06, lgestrin [EMAIL PROTECTED] wrote:
Hello,
if i have 5 modules defined (mod1-mod5), and
mod3 depends on mod4 depends on mod 5
mvn knows the right order in which
The type of question happened may times, I wonder what is the key work to
search for this topic in the maven achiver ?
-Dan
On 9/20/06, Eric Brown [EMAIL PROTECTED] wrote:
How do I get a list of these?
Clearly I can reference anything in settings.xml and pom.xml and all
system properties,
I get this error now when running:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven
Hi. I've been reading about and playing with Maven and it looks
great. There's something I want to do that I can't figure out.
Perhaps someone can help.
I have a Java application I'm developing with Eclipse, so all the
dependencies are specified there. It's a rather long classpath. I
How do I get a list of these?
Clearly I can reference anything in settings.xml and pom.xml and all
system properties, but what else? ${basedir} seems to give me
directory of current pom.xml. I can't find one place where all these
useful things are documented. Hell, I'm not even sure what a
Hello,
if i have 5 modules defined (mod1-mod5), and
mod3 depends on mod4 depends on mod 5
mvn knows the right order in which it has to be build them (mod5, mod4,
mod3).
i want to try to leverage same mechanism when deploying snapshots. for
example, deployment of mod4 should trigger eployment of
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Carlos Sanchez-4 wrote:
When you build A you don't know anything about C-2.0.1 because it does
not exist.
Versions in repository explicitly define what versions the have been
released against or tested with.
If I release A 2.0 depending in C 2.0
and then I want to say i'm compatible
1 - 100 of 144 matches
Mail list logo
