Imo version ranges are best used for developing plugins, more specifically
plugin dependencies. By using a version range for a dependency rather then a
specific version, the plugin can be more easily used in a different poms
using different versions of dependencies.
I've done a full lock down of
+1
I also could not find out which repo maven would try first and which one
after that, etc. It would be nice to make this behaviour more transparant.
Martin Gilday wrote:
Hi,
I have just added the Clover 2 plugin to my POM and now Maven keeps
attempting to download Doxia jars from
, but wasn't able to
find one which seems feasable.
Thank you very much,
Thomas
-Ursprüngliche Nachricht-
Von: ext Wouter Hermeling [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 8. Mai 2008 13:32
An: users@maven.apache.org
Betreff: Re: Generation of ibm-application-bnd.xmi files
I've done this in the past (before maven2) using an xdoclet maven1 plugin.
There is an XDoclet plugin available for maven2 too. I suggest you give it a
try. If you're totally stuck, i might be able to help you by providing you
the old xdoclet maven1 plugin configuration.
kind regards,
Wouter
Yes, you can.
Take a look at:
maven-assembly-plugin (version 2.2-beta-2 i believe)
Define an assembly descriptor project as
project
modelVersion4.0.0/modelVersion
artifactIdyour-artifact-id/artifactId
groupIdyour-group_id/groupId
versionyour-version/version
Actually,
I've found a way to tweak this kind of parent-child property problems. I
have set-up a corporate pom which is the parent for a lot of projects (each
project being a multimodule project on it's own).
There's a nice trick when it comes to inheriting properties: use the
profiles.xml!
It would be very nice if this plugin would be release finally. I had to
create a release myself because releasing with plugin snapshots is
prohibited.
Also i've used the following configuration to compile against an other
jasperreports version (in my case 1.3.0). This works like a charm and has
I've already made a patch. This allows the use of ant patterns to include and
exclude files for rmic. It has been submitted with JIRA issue:
htttp://bugs.freehep.org/browse/RMICPLUGIN-1
NOTE: I'm working on an additional patch which includes:
* Some missing options for rmic (i.e. -nolocalstubs,
Realized i could post the second patch right away, see
htttp://bugs.freehep.org/browse/RMICPLUGIN-1 -
freehep-rmic-plugin-patch2.txt for the new features.
Wouter Hermeling wrote:
I've already made a patch. This allows the use of ant patterns to include
and exclude files for rmic. It has
also, but it uses bcel to discover all classes that
extend RemoteObject, so the user does not have to provide file patterns at
all.
I am not finished yet, as I don't know how to make compiled classes
available to the mojo at the moment.
-Borut
2007/11/22, Wouter Hermeling [EMAIL
Are you sure the artifact isn't attached? If the code would work the artifact
will only be attached after the site:site goals had been run. If you want to
deploy the attached artifact you would have to run:
mvn site deploy
So my question is: In what way are you going to use the attached
I've been having the same problem. I had to use multiple dependencySets, each
having its own include element. i've noticed some other strange behaviour
with include elements. I'll make a comment on that in your JIRA issue
MASSEMBLY-241.
Paul Austin wrote:
Looking at the schema for an
Only f or running JasperReports with maven2 i can provide you some
tips/hints.
Antonio Petrelli-3 wrote:
2007/9/10, Mick Knutson [EMAIL PROTECTED]:
Sorry for the OT, but I have a last minute issue with converting 2
crystal
reports to jasper as Crystal Reports does NOT work on HPUX.
Is
13 matches
Mail list logo
