Hi,
I have created a custom packaging with a custom lifecycle binding. During
building projects with this packaging, the maven-assembly-plugin is
invoked. This plugin needs a special configuration, which seems to be
impossible within the components.xml. What would be the preferred way to
do
Hi all,
I'm still struggling with forcing maven to create an artifact of a
custom packaging type for a plugin I'm writing. In particular, maven
seems to ignore the ArtifactHandler I specify in my components.xml:
component
roleorg.apache.maven.artifact.handler.ArtifactHandler/role
role
Am 15.04.2010 16:51, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 15:40, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare
a
Hi Maven users,
I'm having problems with two plugins, which both define a custom
packaging type. The packaging types are source-plugin and binary-plugin,
which are defined in a private maven plugin and warpath, which is
defined in the warpath plugin.
If I run the project with both plugins
Hi Henrik,
Henrik Niehaus wrote:
Hi Maven users,
I'm having problems with two plugins, which both define a custom
packaging type. The packaging types are source-plugin and binary-plugin,
which are defined in a private maven plugin and warpath, which is
defined in the warpath plugin
Am 15.04.2010 14:54, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Hi Maven users,
I'm having problems with two plugins, which both define a custom
packaging type. The packaging types are source-plugin and binary-plugin,
which are defined in a private maven plugin and warpath
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare a
dependency to another plugin themselves. If yes, which ones?
- Jörg
Hi Jörg,
thanks for your answer. A colleague of mine seems
Am 15.04.2010 15:40, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare a
dependency to another plugin themselves. If yes, which ones?
- Jörg
Hi Jörg,
thanks
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 15:40, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare
a dependency to another plugin themselves. If yes,
Hello,
I have a question for advanced users: I want to add to an existing custom
packaging a goal of my POJO for the deploy phase.
Normally, a packaging is defined through a Plexus components.xml file where
you have to specify for all phases the inpacted mojos and goals to run.
So if I add
Hi,
I have a number of projects which are built using the
org.apache.felix:maven-bundle-plugin, using packagingbundle/
packaging.
I have another project which I'm trying to use to assemble my bundles
(as well as some additional felix bundles) into a standard directory
hierarchy for
alternatively (and probably preferably), it looks like you need to configure
the ~.ArtifactHandler role (as well as the ~.LifecycleMapping one) in the
components.xml.
2009/3/3 Rob Dickens arctic@googlemail.com
Okay - after some google codesearching, and minimal testing, the following
same story with the new mvn 2.0.10
maven-jar-plugin is at 2.2
Has no one else seen this?
2009/3/2 Rob Dickens arctic@googlemail.com
I get the following message when mvn is run with the -X option:
[DEBUG] Not executing jar:sign as the project is not a Java module
(Am using a custom
same story with the new mvn 2.0.10
maven-jar-plugin is at 2.2
Has no one else seen this?
In all likelihood, you're one of the first people to try using
jar:sign on a custom artifact. So it might be a little painful to get
it working, and may involve changing some code in the Jar plugin. Once
Okay - after some google codesearching, and minimal testing, the following
appears to address the problem:
In the execute() of the Mojo for the goal which precedes the jar:jar one,
add the following:
project.getArtifact().setArtifactHandler(new MyArtifactHandler());
where MyArtifactHandler is
I get the following message when mvn is run with the -X option:
[DEBUG] Not executing jar:sign as the project is not a Java module
(Am using a custom packaging type in order to use a custom lifecycle, that
invokes a custom goal before the jar:jar one.)
If I change the packaging type back to jar
refuses to sign jar artifact of project with custom
packaging type
I get the following message when mvn is run with the -X option:
[DEBUG] Not executing jar:sign as the project is not a Java module
(Am using a custom packaging type in order to use a custom lifecycle,
that
invokes a custom goal before
Hi all,
I'm trying to make my own packaging type for my skin project.
So I create a plugin with a components.xml that define my ArtifactHandler
and my LifecycleMapping.
But when I launch an mvn clean install on a project with my own packaging I
have the following error :
[FATAL ERROR]
Hi,
I found a workaround. I use the version 2.2 of plexus-archiver instead of
version 2.3.
Guillaume Boucherie
2008/7/2 Guillaume Boucherie [EMAIL PROTECTED]:
Hi all,
I'm trying to make my own packaging type for my skin project.
So I create a plugin with a components.xml that define my
that if I will add all the WAR's lifecycle goals to my custom
lifecycle then the build artifact created will be indistinguishable from
that created by the WAR packaging. Is it true?
Is there any way to make the Eclipse plugin believe that some custom
packaging type is a Java type?
Thanks
Eric Redmond [EMAIL PROTECTED] writes:
I wrote a little bit about it here - though I suppose it wouldn't hurt going
into more depth.
http://www.sonatype.com/book/repository.html#tips_and_tricks
Please read, and request any clarifications so I can fix the book. Thanks :)
Hello,
Thanks for
Hello,
While creating a custom packaging, I ran into slight problems with
configuring the components.xml for plexus. I would like to understand
what are the roles/differences of the various configuration elements
for an artifact and how to define them properly. I can see from
maven-core's samples
[EMAIL PROTECTED] wrote:
Hello,
While creating a custom packaging, I ran into slight problems with
configuring the components.xml for plexus. I would like to understand
what are the roles/differences of the various configuration elements
for an artifact and how to define them properly. I can
artifactIduber-docbook-xslt/artifactId
version1.0.0/version
/dependency
/dependencies
/plugin
The other approach does not seem much used (that I could find). The
thought was to use custom packaging definitions for the various types of
ingredients that go into this DocBook mixture
Is it possible to implement your own packaging like the
packagingjar/packaging?
Brandon
I was thinking of asking the same thing actually.
In our current Ant based build we're unjaring the Apache James .sar file,
copying in our own .jar file along with our custom configuration files, and
then rejaring the .sar as our own application.
I could see this being a good use of a custom
own application.
That's called an assembly. Look at the assembly plugin, what you want
is not really packaging.
Jason.
I could see this being a good use of a custom packaging/ plugin.
On 2/16/07, Brandon Goodin [EMAIL PROTECTED] wrote:
Is it possible to implement your own packaging like
On 15 Feb 07, at 5:25 PM 15 Feb 07, Brandon Goodin wrote:
Is it possible to implement your own packaging like the
packagingjar/packaging?
There is a lifecycle associated with making a JAR, which is the
default, if you want to stick different things into the JAR then you
could make a new
I want to replace the jar test phase goal binding from surefire to cobertura
since cobertura fires off surefire on it's own there is no need to run
surefire in the test phase. I've tried every permutation known to man to
prevent the tests from running twice. That's all i want to change. How would
If that does not work, check out the assembly plugin[1].
Eric
[1] http://maven.apache.org/plugins/maven-assembly-plugin/
On 1/31/07, 秋秋 [EMAIL PROTECTED] wrote:
Hi,
I think you have met with the same issue with me,I hope the following
configuration can help you:
--builder jar and war--
Hi,
I have a new project type,
In this type I need to create a zip file that contain both directory
structure from version control and dependency files (e.g. jars/wars...)
(each file should be copied to a specific path - and this should be
configured in the pom.xml file)
It seems that I need to
Hi,
I think you have met with the same issue with me,I hope the following
configuration can help you:
--builder jar and war--
build
sourceDirectorysrc/main/java/sourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
outputDirectorytarget/classes/outputDirectory
into the lifecycle. If
I do, the build fails with the stack seen below.
Is there a step I could have missed here? Does the maven-source-plugin just
not work on a custom packaging?
Thanks,
--Matthew Beermann
[INFO] Preparing source:jar
[DEBUG] Error looking up lifecycle mapping
Hello everybody maybe are repost but my subscribing went wrong,
I am new to maven 2.0. but experienced 1.0 user.
Do i understand correctly that packaging defines the type of product that is
being build. If so, can you define more than one and define your own custom
types. like installer and
take a look at http://mojo.codehause.org/maven-native/native-maven-plugin
it uses build lifecyle extension to provide its own packaging type.
-Dan
On 4/25/06, Marteijn Nouwens [EMAIL PROTECTED] wrote:
Hello everybody maybe are repost but my subscribing went wrong,
I am new to maven 2.0.
On 4/25/06, dan tran [EMAIL PROTECTED] wrote:
take a look at http://mojo.codehause.org/maven-native/native-maven-plugin
That would be:
http://mojo.codehaus.org/maven-native/native-maven-plugin/
(No 'e' on the end of codehaus ;)
--
Martin Cooper
it uses build lifecyle extension to provide
on the second thought, if you can whip you installer easily thru a small ant
script, you can use maven-antrun-plugin
to create the installer, then use build-helper-maven-plugin to attach your
output to be installed/deploy
-D
On 4/25/06, Martin Cooper [EMAIL PROTECTED] wrote:
On 4/25/06, dan
.
My POM is very simple, comprising only the use of the dependency and
exec
plugins. Looking at the M2 docs, the only way I see to have a custom
packaging is to define it within a custom plugin. However, I don't
need
any
additional plugins, and that seems like a complicated way
@maven.apache.org
m cc:
Subject: Re: [M2] Custom
'packaging' without a custom plugin
, the only way I see to have a custom
packaging is to define it within a custom plugin. However, I don't
need
any
additional plugins, and that seems like a complicated way to solve a
simple
problem. Is there some other way I can either define a custom
packaging
(or
just
, the only way I see to have a
custom
packaging is to define it within a custom plugin. However, I don't
need
any
additional plugins, and that seems like a complicated way to solve
a
simple
problem. Is there some other way I can either define a custom
packaging
in packaging types (e.g. war, ear) are no better
suited
to
my
needs.
My POM is very simple, comprising only the use of the dependency
and
exec
plugins. Looking at the M2 docs, the only way I see to have a
custom
packaging is to define it within a custom plugin
built in packaging types (e.g. war, ear) are no better suited to my
needs.
My POM is very simple, comprising only the use of the dependency and exec
plugins. Looking at the M2 docs, the only way I see to have a custom
packaging is to define it within a custom plugin. However, I don't need any
POM is very simple, comprising only the use of the dependency and exec
plugins. Looking at the M2 docs, the only way I see to have a custom
packaging is to define it within a custom plugin. However, I don't need
any
additional plugins, and that seems like a complicated way to solve a
simple
the use of the dependency and
exec
plugins. Looking at the M2 docs, the only way I see to have a custom
packaging is to define it within a custom plugin. However, I don't need
any
additional plugins, and that seems like a complicated way to solve a
simple
problem. Is there some other way
45 matches
Mail list logo
