Hello,
I want to create a new packaging type (for ConnId connectors) with a lifecycle
that is very similar to the default (jar) lifecycle, but with a assembly build
step for the packaging phase. I have a plugin-project with a
'plexus/components.xml' which defines the lifecycle and the artefact
What do you mean by configuration for the assembly build step? You can't
provide the configuration for a plugin through a custom packaging type
(unfortunately). But you could create a shared assembly descriptor that
should be used:
mb-olamy:maven-compiler-sample olamy$ hg diff
diff -r 282cd9fe95c4 pom.xml
--- a/pom.xml Sun Apr 14 14:48:37 2013 +0300
+++ b/pom.xml Mon Apr 15 22:06:35 2013 +1000
@@ -41,6 +41,9 @@
encoding${project.build.sourceEncoding}/encoding
Hi all,
I've sketched a rough plugin
https://github.com/davidecavestro/gradle-jxr-plugin to spread JXR even
to gradle users. It just works, but it is limited by some parsing issues.
I've filed JXR-101 https://jira.codehaus.org/browse/JXR-101 and
JXR-100
CC'ing users@maven because I think my point applies to the entire Maven
community:
Well my view is that such practice is bad practice, there are good ways to
do things and bad ways to do things. Hard-coding references between
projects using the file system is bad practice. For one thing it fails
if anybody submits patches, I can review and commit
Regards,
Hervé
Le lundi 15 avril 2013 06:03:19 davide.cavestro a écrit :
Hi all,
I've sketched a rough plugin
https://github.com/davidecavestro/gradle-jxr-plugin to spread JXR even
to gradle users. It just works, but it is limited by
Hi,
based on the requirement which has been made to introduce a new property
for the root of the reactor I 100% agree with Stephens argumentation.
I have taken a look into those question on SO and all of those things
can be solved in better ways than suggested on SO, cause many people
Mon, 15 Apr 2013 22:10:19 +1000, /Olivier Lamy/:
+ excludes
+exclude**/package-info.java/exclude
+ /excludes
[...]
As all package-info.java files never go to
${project.build.outputDirectory} a compilation is triggered.
This is really
On 15 April 2013 20:42, Karl Heinz Marbaise khmarba...@gmx.de wrote:
A case in point of the improving (though not related to the idea of being
able to get a property exposing the root (never mind the which root:
reactor/inheritence/**inheritence within reactor) but more related to
mirror
idartifactory/id
mirrorOf*/mirrorOf
url
file:///home/diop/artifactory-2.6.7.zip
/url
This url is completely wrong. Point the url not to the Artifactory zip
file on your disk, but to the running Artifactory instance on a server
(which may be localhost or another).
You have to
10 matches
Mail list logo
