I tried the solution explained in the JIRA :
[del]
For information, I currently used maven-assembly-plugin 2.1 ...
What's wrong ?
That version 2.1 doesn't contain the patch.
It's a snapshot release.
You need to follow the roll-your-own instructions.
Alternatively, just manually rename all
we are using the eclipse plugin to create the Eclipse configuration, and
specify the -DdownloadSources=true switch to download the source JARs and
include them into the .classpath file. This is pretty cool, but
As usual, the .project and .classpath files are checked into CVS to share
them
In the company that I helped setting up a Maven-based build environment, a
public site like ibiblio.org is considered a potentially unsafe source. Like
it or not. Only JARs that have been approved internally may be used for
production. (BTW, this was within finance industry which is partly quite
Our actual testsuite for JBossAS starts and stops different server
configurations 15-20 times as well as starting up clusters of servers.From
what I can see, to do this the maven way, I would need 15-20 integration
projects which would be executed by hand or cruise control or 1 integration
Run mvn site, which by default will include the dependency report.
You can see a hierarchical view of all the dependencies of your project.
The file will be in target/site/dependencies.html
See the nabble archives at
http://www.nabble.com/forum/ViewPost.jtp?post=5496323framed=y for how
to
Go into the module sub-directory and either re-run mvn site or look at
the target/site/dependency.html file there. These reports are not
aggregated.
On 9/1/06, Vinod Panicker [EMAIL PROTECTED] wrote:
Thanks for the help, but the dependency graph is being shown only for
the main project and not
Joe Heck wrote
The how to for the separate functional test module setup was on this
earlier - the big pieces to note being that the functional test module
is set with POM packaging, and then plugins manually bound to the
various steps (in this case, the maven-surefire-plugin bound to the
On 8/30/06, Alexis Midon [EMAIL PROTECTED] wrote:
here is what I have in my parent pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
1. I have a project that is simply a testing utility for our admins to test
their message queue setups. I have the assembler plug in create a zip file
that contains all the jars and the class path for the executable jar. Is it
possible for me to automatically run the assembly and upload the
On 8/31/06, Wayne Fay [EMAIL PROTECTED] wrote:
Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to
On 8/31/06, Dave Hoffer [EMAIL PROTECTED] wrote:
Why does it want to connect to 'people.apache.org'?
If you check the pom files you will find that people.apache.org has
been defined as a repository, probably to get access to the SNAPSHOT
of another plugin.
On 8/31/06, jim stafford [EMAIL PROTECTED] wrote:
Is there any way to limit the number of SNAPSHOTs that accumulate in the
SNAPSHOT repository using only Maven?
I realize I can use shell script pruning tools and cron to help reduce
the clutter, but I was wondering if there was a way of getting
Included module: murex.middleware:middleware-gui:jar:3.1 does not have an
artifact with a file. Please ensure the package phase is run before the
assembly is generated.
but when I add the package goal my jars are always built twice, once by the
package goal and once by assembly after the
On 8/30/06, Siegmann Daniel, NY [EMAIL PROTECTED] wrote:
Could someone explain why running eclipse:eclipse requires that the project
successfully compile? I want to build the eclipse project files so I can fix
the compilation errors. ;)
I think this is fixed in the SVN.
I am using the snapshot
Read Better Builds with Maven.
It has a section on version numbering.
If you follow that standard Maven should be able to increment the
numbers for you.
And as someone rightly pointed out, you never re-release the same version.
Any changes made implies a new version, which would increment the
On 8/30/06, Russ Tremain [EMAIL PROTECTED] wrote:
I am a proponent of Maven 2.
[del]
So bottom line is: Maven 2 solves the dependency problem,
and works now, even for complex projects. The rest of the maven
strong points (standard build lifecycle, standard source layout, etc.)
are helpful,
See http://www.nabble.com/forum/ViewPost.jtp?post=5496323framed=y
A dependencySet copies ALL dependencies.
So if you get rid of your include statement you will get them all by default.
On 8/28/06, hamdard [EMAIL PROTECTED] wrote:
Hi
Is there a way to package the transitive dependencies of my
On 8/25/06, Valerio Schiavoni [EMAIL PROTECTED] wrote:
Eclipse does not support hierarchical project structures.
i thought eclipse 3.2 just introduced this new feature ...
Yes it does.
Hence my original post wondering how to get it to work.
The notes I posted worked for me.
Try to get it
On 8/25/06, Andreas Guther [EMAIL PROTECTED] wrote:
Question: How can I get Maven to deploy version-less SNAPSHOT files to
our SNAPSHOT repository?
Background:
It appears to me as if the mvn deploy command on a SNAPSHOT version
does only deploy numbered snapshot files, but not unnumbered ones.
On 8/23/06, Douglas Ferguson [EMAIL PROTECTED] wrote:
I am not sure I follow, dependencySet is in the assembly.xml.
Can you give an example tag you'd need to add the the xml below to get it to
exclude 1 class file that is picked up from the dependencySet below?
You don't use the
On 8/22/06, Owen Jacobson [EMAIL PROTECTED] wrote:
However I have one last thing to try:
I notice that you have two moduleSet declarations.
Can you not collapse them into one? which contains both the source and
the binary sections?
I suspect that might be the problem.
Just for grins I
On 6/14/06, teknokrat [EMAIL PROTECTED] wrote:
I have a multiproject that builds an ear file out of a war and a sar. It
is virtually identical to the j2ee project in the book. I have gone into
each directory and called mvn install. This has worked in the sar and
web directories. I checked my
I'm trying to use release:prepare and I get to our last module which
is just one that assembles all the binary assemblies of the previous
modules into an uber-archive.
The release:prepare fails because if can not locate the binary dependencies:
my.group:myartifact:zip:bin:0.2
which is obvious
On 8/22/06, J. Matthew Pryor [EMAIL PROTECTED] wrote:
I am trying to exclude dependencies from a dependcySet in an assembly
descriptor, but can't find any examples of how to do it.
From looking at the code it looks like I should be able to exclude
dependencies by groupId/artifactId but I can't
On 8/22/06, J. Matthew Pryor [EMAIL PROTECTED] wrote:
Gee thanks. My google search did much worse, I'll try nabble next time.
Now I have to try get my head around classifier/ ;-)
Your welcome.
Classifier is easy. For most things it is empty!
The assembly plugin uses the classifier to
[INFO] Checking in modified POMs...
[INFO] Executing: cvs -z3 -f -d :pserver:USER@HOST:CVS_ROOT -q
commit -R -F C:\TEMP\scm-commit-message188
38.txt pom.xml module1/pom.xml module2/pom.xml module3/pom.xml
module4/pom.xml [INFO] Working directory:
D:\ide\workspace\working_directory
[INFO] Tagging
[ERROR] BUILD FAILURE
came from mvn release:prepare
I'm going to delete the module definitions and try again.
My parent pom defines the dependencyManagement versions.
Which means that I have to hand edit this section first and promote
the values out rather than get the release plugin to do
foo-1.2/src/com/example/Example.java
[del]
!-- include example src --
moduleSet
includes
includecom.example.foo:foo-examples/include
/includes
sources
outputDirectory/src/outputDirectory
/sources
/moduleSet
/moduleSets
/assembly
I'd
No love there. It still duplicates the foo-1.3-SNAPSHOT part of the
path* in the sources. Good point about not needing to name a
directory 'src' myself, though.
At this point I'd be happy if it just put it in as
foo-1.3-SNAPSHOT/example/pom.xml etc.
* Like this:
On 8/22/06, Owen Jacobson [EMAIL PROTECTED] wrote:
However I have one last thing to try:
I notice that you have two moduleSet declarations.
Can you not collapse them into one? which contains both the source and
the binary sections?
I suspect that might be the problem.
Just for grins I
On 8/23/06, Douglas Ferguson [EMAIL PROTECTED] wrote:
When using the dependencySet, can you exclude individual class files or are you
limited to excluding specific artifacts.
dependency set excludes specific dependencies.
When you create your assembly that is the place to exclude any files
On 8/22/06, Chris Hilton [EMAIL PROTECTED] wrote:
Pardon me asking the obvious, but has the maven nature been added to the
modules?
The maven nature is only needed for the Eclipse IDE Maven Plugin which
allows you to invoke maven from within the IDE.
This is completely different from mvn
How are your dependencies declared?
A parent pom, since it is just a container project and does not create
an artifact, does not have dependencies.
Only your modules have dependencies.
Sorry, my mistake. The dependencies are declared in the module pom.xml.
But the eclipse plugin is not
these applications are separate projects in eclipse. I'm worried that if
I combine them into a maven-ized single project with modules, I will no
longer be able to deploy them as individual web applications within
eclipse (using eclipse web tools project web server - tomcat in this
instance).
On 8/16/06, Barrie Treloar [EMAIL PROTECTED] wrote:
I thought that the snapshot version of the eclipse:eclipse plugin had
the functionality to do this for me, but it is not working how I
expect. I assume I am doing something wrong. Should mvn
eclipse:eclipse at the project root do what I expect
I setup a workspace using the procedure outlined in this thread. The end
result that I get has the root and modules in a flat layout (not
hierarchical) like this:
root
module1
module2
module3
At first I thought that it didn't work for me, but I suspect that this
was the same result that others
On 8/18/06, Kent Tong [EMAIL PROTECTED] wrote:
Hi,
I am trying to use the maven2 eclipse plugin for a module inside a
multi-module project. But it doesn't seem to list the dependencies
defined in the parent pom.xml at all. Am I missing something? Does
it work in a multi-module project?
Kent,
On 8/18/06, Kent Tong [EMAIL PROTECTED] wrote:
Barrie Treloar baerrach at gmail.com writes:
Kent, did you check the archives?
http://www.nabble.com/Maven---Users-f178.html
In particular:
http://www.nabble.com/forum/ViewPost.jtp?post=5849396framed=y
http://www.nabble.com/forum/ViewPost.jtp
On 8/16/06, Denis McCarthy [EMAIL PROTECTED] wrote:
Just got that working - I needed to define a pluginRepository in my
settings.xml. Nothing like sending an email to concentrate the mind.
Have a look at
http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+environment
which
On 8/17/06, Max Cooper [EMAIL PROTECTED] wrote:
I, too, have been anxiously awaiting hierarchical project support in
Eclipse. And I thought that it was going to be available in Eclipse 3.2.
But this feature was omitted from the Eclipse 3.2 release. The feature
is not available yet.
You can do
On 8/17/06, Nick Veys [EMAIL PROTECTED] wrote:
On 8/16/06, Denis McCarthy [EMAIL PROTECTED] wrote:
Hi,
One of my projects depends on a second project. As a result, I've
defined the first project as being packaged as a pom, with an associated
dependency in the second package. However, when I
On 5/11/06, George Zhao [EMAIL PROTECTED] wrote:
We saw the same issue here (two Class-Path entries).
But if we set addClasspath to false and put all the known classpath there,
we can generate one Class-Path entry - not a pretty solution through.
Anybody over there has other workaround for
1) I want to use the directory the M2 repo would use - the example below is
creating a directory com.cswgroup.kms.kes.config when I really want
com/cswgroup/kms/kes/config - is there a way of getting at ${groupId} with /
separators ?
Can't help you on this one. Also can't really see the reason
With Eclipse 3.2 I was lead to believe you could create projects
within projects, so that I could checkout a maven project that
contains modules and wire that up in Eclipse correctly. Instead of
manually checking out the modules as I did under Eclipse 3.1.
I am able to manually add the project
I'm trying to package my application with its dependencies such that the
main jar file is executable. That means have a Class Path entry in the
Manifest of the main jar. I can get this to work with the following in my
pom.xml:
plugin
On 8/11/06, Prashanth Krishnamurthy [EMAIL PROTECTED] wrote:
After the build, I would like to copy the application
war file to a ftp location ( on the same machine ) for
others to pick it up.
use deploy, and deploy your build file to your internal maven repository.
Then people can use http
On 8/11/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Dependent projects aren't build for the moment. It's planned for 1.1
Are you saying they are never built?
I thought that when the schedule kicked off it would check if there
are cvs updates and rebuild, or if an artifact that the project
On 8/7/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hey,
if i have released an artifact, so there is a ...sources.jar in my
releaseRepository that will be downloaded in my local repository. The goal
eclipse:eclipse add's this jar as attached Source to the eclipse build path.
But if I
Does anyone know the reason why filtering is only applied to files?
If I define a fileSet the it is not filtered?
I have a bunch of configuration files in src/main/config which need to
be configured correctly for different environments, dev, int, qa,
production.
I thought it was to define
I just added a dependency on EasyConf
dependency
groupIdeasyconf/groupId
artifactIdeasyconf/artifactId
version0.9.5/version
/dependency
and now I have a lot of dependencies which I don't need.
I think this is because the dependencies listed in EasyConf pom needs
I'm sure there are probably other pom's out there that do not
correctly define the dependencies. So in these cases what is the
suggested way of overriding them so they are not included? Including
the dependency again and using optional doesn't fix the problem,
nor does changing the scope to
On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote:
1. How do you write a pom to build and release an Eclipse RCP
application, including using an Eclipse Product Configuration to build
the final package?
2. How do you then create the Eclipse project from the pom?
As Fabrizio has
http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some
stuff in it of use. I've yet to check. (The website is out of date and
the source repository is not where the link indicates)
SVN is here http://svn.codehaus.org/m2eclipse/trunk/
Specifically, I am trying to use BEA Kodo 4, the enhancer, and it
appears to require that the directory containing the license.bea file be
on the classpath.
From my understanding stuff on the classpath is treated the same,
regardless of whether it came from a jar or a directory.
So if you
On 8/1/06, Damien Viel [EMAIL PROTECTED] wrote:
Hi all,
I'd like to install the last version of the changes-plugin. So I've
downloaded the sources, but when I run the install goal, he can't find
the parent pom.
parent
artifactIdmaven-plugins/artifactId
It would be nice for convenience
to have
a kind of maven project, which for example could be called
'application-x-ejb-client',
that bundles the dependencies for a client and might help deliver
them all
by providing a single dependency declaration on application-x-ejb-client
in thw web client's
Indeed, DRY is one benefit I want to get and we have several clients.
I think it is important to explicit list your dependencies, otherwise
you pull in cruft and the kitchen sink unnecessarily.
You didn't respond to this.
Do all clients have the SAME dependency set?
Unless you are talking
On 7/31/06, Alex Turner [EMAIL PROTECTED] wrote:
Not to ask a stupid question, but why should I have to use a plugin for
this? This is standard functionality that many projects require. Shouldn't
this be part of the standard maven goals?
If you have a standalone app then you probably want to
On 7/31/06, Alex Turner [EMAIL PROTECTED] wrote:
A list of goals isn't really much of an 'about' the plugin. It would be
more usefull to describe what the plugin can do and provide tutorials...
Err,
Did you check the Overview section on the left?
It reads:
* Introduction
* How to Use
On 7/25/06, Damien Viel [EMAIL PROTECTED] wrote:
With the standard goals jar-with-dependencies it works fine on each
modules. But when I call the goal from the parent pom, the assembly is
empty.
[del]
assembly
idjar-with-dependencies/id
formats
formatzip/format
formatdir/format
On 7/25/06, Damien Viel [EMAIL PROTECTED] wrote:
Thank for your help.
I've tried your solution with a dedicated project for the build which
has dependencies on the binary assemblies. But my assembly still empty.
This is because you can not use the built in assemblies.
You need to write your
For those that may be trying to work out how excludes works I'm
posting to the list.
There is probably a JIRA issue (I haven't looked) that will address
pattern matching of excludes, there are comments in the code to
indicate that this would be a good feature.
To summarize my problem:
I have a
And it does not help me to make continuum run in batch.
I'm not suggesting to run continuum in batch.
What I am saying is that you should be able to run the same mvn
command as continuum does. When you that command it should not prompt
for any information and complete correctly (i.e in a batch
On 7/13/06, javaguy1974 [EMAIL PROTECTED] wrote:
It would be nice if Maven provided a capability for a child POM to ignore
some inherited stuff like plugins. Otherwise, it is very difficult to design
a truly top-level organizational POM that is shared by all projects. I'm not
sure what you
I have defined for my top level projects a second build definition
Goals = site site:deploy
Arguments = --batch-mode
POM File =pom.xml
Profile = DEFAULT
Schedule = NIGHTLY_SITE_BUILD
From = Project
Where NIGHTLY_SITE_BUILD is (runs at 7:15 pm mon-fri)
Name =
On 7/5/06, Arnaud Bailly [EMAIL PROTECTED] wrote:
nazim chakik [EMAIL PROTECTED] writes:
May be the following assembly descriptor can help you:
assembly
idbin/id
formats
formattar.gz/format
formatzip/format
/formats
!-- create everything in a base directory --
On 7/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
All,
If you have a project setup where all your projects have a common
parent project, and some are dependend on the others, how can you
accomodate the downloaders of your assemblies such that they still can
build your project using maven
On 7/5/06, Mark Reynolds [EMAIL PROTECTED] wrote:
I have changed my multi-project build so it only builds the parent pom
without --non-recursive.
There are some double negatives here.
Do you mean you have deleted your other projects from the continuum
build and that there is now only one
On 7/5/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Is there anything else that you feel is missing from the current
documentation for this plugin? This is the time to speak up and let us
know. Please submit your wishes here. If you have some example
configurations that you feel others would
Can anyone point me to any documentation on the maven-it-plugin?
I expect I've missed something but
- I can't find the plugin documentation at maven.apache.org
- there is very little in the mail archives about it
- googling hasn't really helped find the scm for the plugin either...
From my
- googling hasn't really helped find the scm for the plugin either...
I'm blind.
It's available at
http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 7/3/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Though I read on a separate thread on this list
(http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080)
that doing a module based build is not working for separated projects.
That is why I didn't put a modules section in the
of course in your parent pom.xml you can happily use ${project.version}
to specify the dependencies on child modules which saves you worrying
about that part :)
I had problems with using ${project.version} as when the artifacts are
deployed to a snapshot repository the pom metadata is using the
For those finding this in the archives the following bugs address this issue:
http://jira.codehaus.org/browse/MASSEMBLY-67
assembling dependent jars or snapshots uses timestamp formatted
version instead of ${version}
http://jira.codehaus.org/browse/MJAR-28
Using the jar plugin with addClasspath
I have the same issue that has no response to it in the archives,
that is the Class-Path entry in manifest has
artifactId-version-SNAPSHOT but the assembled files resolve
SNAPSHOT to the dated version.
Does anyone know the answer?
Thanks
Bae
The original email is on nabble at
http://www.nabble.com/Inconsistency-between-JAR-and-Assembly-tf473891.html#a1290262
On 6/27/06, Barrie Treloar [EMAIL PROTECTED] wrote:
I have the same issue that has no response to it in the archives,
that is the Class-Path entry in manifest has
artifactId
On 6/21/06, Ivo Limmen [EMAIL PROTECTED] wrote:
Strange thing is: my dependencies are like to one you descibe but my builds
are not re-run.
assembly:assembly goal in pom = re-run of lifecycle
assembly:attached goal in pom = no re-run of lifecycle
In case of using an internal repository - what is the analog to mvn install?
For instance I want to share a third party artifact and do something like
mvn install:install-file-Dfile=./jta-1.0.1B.jar
-DgroupId=javax.transaction
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
And my bin.xml looks like this:
assembly
idbin/id
formats
formatdir/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
moduleSets
moduleSet
includes
includeaardrock.cheetah.cheetah-core/include
This error is because your assembly is not including any files to create.
I'm having trouble getting the include tag in the assembly descriptor to work.
I think I would have preferred the moduleSet includes to be
include
groupId/
artifactId/
/include
instead of this custom : separated format.
I think this is a really cool idea I tried to do it for my
project but unfortunately I couldn't find a way to reference the
assembly of the subModule in the moduleSet of the parent module. The
submodule assembly gets set as an 'attached' artifact and not the
main one.. by the binaries tag in
Back on 2005-11-09, ramfree17 send an email [m2] assembly:directory
requires an install?
(see
http://www.nabble.com/-m2--assembly%3Adirectory-requires-an-install--t512277.html#a1387406)
This thread was hijacked and no answer was provided.
I am finding that if I removed the formatdir/format
On 6/20/06, Ivo Limmen [EMAIL PROTECTED] wrote:
Did you try using a different phase and / or goal? I personally only include
and configure the asembly plugin and don't attach it to a specific phase or
goal.
[del]
But still I never used the dir format. My distribution is only created once.
What about re-running of the build lifecycle.
If you are finding that your lifecyles are being re-rerun check
http://jira.codehaus.org/browse/MASSEMBLY-37.
You should not be using the assembly goal but instead the attached
goal (and dont specify a phase)
The pom should look like:
build
On 6/21/06, Barrie Treloar [EMAIL PROTECTED] wrote:
What about re-running of the build lifecycle.
If you are finding that your lifecyles are being re-rerun check
http://jira.codehaus.org/browse/MASSEMBLY-37.
You should not be using the assembly goal but instead the attached
goal (and dont
I've found a JIRA issue that already talks about dir format and
repository installation
http://jira.codehaus.org/browse/MASSEMBLY-39
However it is closed and the documentation doesn't really resolve the
issues around directory format not being something that should be
placed into the repository.
On 6/21/06, dan tran [EMAIL PROTECTED] wrote:
you may want to try
http://maven.apache.org/plugins/maven-assembly-plugin/directory-inline-mojo.html
The attached goal was the one I needed.
I don't see the dir format being any different than the other
formats being created, except that dir
On 6/21/06, Edwin Punzalan [EMAIL PROTECTED] wrote:
They do the same thing... but differs in when you use them.
assembly:attached is used inside poms, i.e. mvn package
assembly:assembly is the command-line version , i.e. mvn assembly:assembly
Plus assembly:attached does not fork the
On 6/17/06, Barrie Treloar [EMAIL PROTECTED] wrote:
But when adding the module pom I think it is failing to find the
parent pom (or even looking for it) and gives you an error that the
version for the dependency is mandatory and missing.
Perhaps the parent pom's module has not been
But when adding the module pom I think it is failing to find the
parent pom (or even looking for it) and gives you an error that the
version for the dependency is mandatory and missing.
Perhaps the parent pom's module has not been 'installed' in continuum's
repository with the
If I re-add the pom file via Maven 2.0+ Project link (I am using
file:// urls to do this) I get a second parent project but not
sub-modules.
which pom do you add? parent or module?
If I re-add the [parent] pom... I get a second parent pom but no extra
sub-modules that have been added.
If
Speaking of definitions, adding support for build definitions in the pom.xml
CI configuration for continuum would be ideal. It would make re-adding
whole trees much more palatable, since less manual re-configuration would be
necessary.
File an issue and we'll look if we can do it.
This
Any chance a continuum developer could take a look at the notes I
added to http://jira.codehaus.org/browse/CONTINUUM-243 and see if what
I have written is on the correct path?
I notice in the continuum logs that the following command is run to
update the project prior to running a build:
cvs -z3 -f -d :pserver:anonymous@host:path -q update -d
The -P for pruning should als be included to clean up when stuff is
deleted from cvs.
Is there a reason that this option is
If I add another module to the parent pom and then rebuild the parent
project in continuum the new module does not get added as another
project.
If I re-add the pom file via Maven 2.0+ Project link (I am using
file:// urls to do this) I get a second parent project but not
sub-modules.
If I try
While I'm discussing this, I notice because I am using the recommended
project layout:
ROOT
- pom.xml
- module1/pom.xml
- moduel2/pom.xml
That to rebuild the ROOT project it takes forever since it has to
checkout the entire CVS tree.
Whereas the module builds only checkout the module
I was hoping to be able to do something like the following to specify
my parent pom, so that it would automatically obtain the latest
version. The parent pom doesn't change often but we should be using
the latest version automatically if it does.
parent
groupIdDummy-groupId/groupId
A JIRA is was raised on 19/Jul/05 for this.
http://jira.codehaus.org/browse/CONTINUUM-243
On 6/6/06, EJ Ciramella [EMAIL PROTECTED] wrote:
Yeah, I bound this to the verify stage properly, but the outstanding
question is how can the directory structure get passed from the parent
pom to the child?
When the parent pom calls the child one, everything is supposed to be
based on the
On 6/1/06, Brett Porter [EMAIL PROTECTED] wrote:
http://maven.apache.org/articles.html
It could probably stand to be more prominent - I might put that link
in the left nav.
I'd be more than happy to plaster it all over the site... but by the
same token I don't want to show any favourtism :)
801 - 900 of 921 matches
Mail list logo
