You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "J. Matthew Pryor" <jm...@mobiquity.net> on 2005/07/20 09:20:14 UTC
[m2] Assembly-plugin & Manifest.mf
Perhaps I do not understand the purpose of the assembly plug-in, but as it
works in alpha-3, the "assembled" jar gets a new MANIFEST.MF which is
basically empty (and not the MANIFEST.MF from the created artifact).
Maven-jar-plugin writes a lot of stuff to the MANIFEST (and I am writing an
Eclipse PDE plugin that augments that), but sadly it doesn't get copied to
the assembled jar.
Is this intended?
Should I move this to the dev list?
Thanks,
Matthew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Assembly-plugin & Manifest.mf
Posted by Brett Porter <br...@gmail.com>.
Yes, we'd need to switch to MavenArchiver, or move the manifest
support to plexus-archiver (preferred).
- Brett
On 7/21/05, J. Matthew Pryor <jm...@mobiquity.net> wrote:
>
> > This sounds right. Assembly should let you specify your own
> > manifest fields though - if it is not, its a bug.
>
> AFAICT the AssemblyXpp3Reader has no provision for manifest entries and
> AssemblyMojo uses a JarArchiver which doesn't appear to take any manifest
> configuration
>
> jmp
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m2] Assembly-plugin & Manifest.mf
Posted by "J. Matthew Pryor" <jm...@mobiquity.net>.
> This sounds right. Assembly should let you specify your own
> manifest fields though - if it is not, its a bug.
AFAICT the AssemblyXpp3Reader has no provision for manifest entries and
AssemblyMojo uses a JarArchiver which doesn't appear to take any manifest
configuration
jmp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m2] Assembly-plugin & Manifest.mf
Posted by "J. Matthew Pryor" <jm...@mobiquity.net>.
POM Data would work well for a fair bit of it, certainly Bundle-Classpath &
other stuff
What would be the next steps?
jmp
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, July 21, 2005 9:56 AM
> To: jmp@mobiquity.net
> Cc: Maven Users List
> Subject: Re: [m2] Assembly-plugin & Manifest.mf
>
> On 7/20/05, J. Matthew Pryor <jm...@mobiquity.net> wrote:
> > Obviously the assembly plugin suits my needs very well here, as it
> > does all the work, but it also adds its own Manifest.
> >
> > I guess I saw an assembly simply as a 'superjar' but basically the
> > same artifact as the project is meant to produce, just one that
> > includes
> > (transitively) all the dependent classes.
>
> This sounds right. Assembly should let you specify your own
> manifest fields though - if it is not, its a bug. But what
> I'm thinking is that it should have an OSGi JAR format that
> will add these fields automatically using POM data. We could
> use the Maven1 OSGi plugin as a starting point:
> http://mavenosgiplugin.berlios.de/osgidevandbuild.html
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Assembly-plugin & Manifest.mf
Posted by Brett Porter <br...@gmail.com>.
On 7/20/05, J. Matthew Pryor <jm...@mobiquity.net> wrote:
> Obviously the assembly plugin suits my needs very well here, as it does all
> the work, but it also adds its own Manifest.
>
> I guess I saw an assembly simply as a 'superjar' but basically the same
> artifact as the project is meant to produce, just one that includes
> (transitively) all the dependent classes.
This sounds right. Assembly should let you specify your own manifest
fields though - if it is not, its a bug. But what I'm thinking is that
it should have an OSGi JAR format that will add these fields
automatically using POM data. We could use the Maven1 OSGi plugin as a
starting point: http://mavenosgiplugin.berlios.de/osgidevandbuild.html
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m102] multiproject:deploy fails
Posted by Christian Schlaefcke <cs...@wms-network.de>.
Hi,
got a bit further now, but still no luck. I found out that the cause of
the error seems to be the ejb project. I get the error when running
"maven ejb:deploy" in the ejb project folder:
Tag library requested that is not present: 'maven' in plugin:
'maven-xdoclet-plugin-1.2'
BUILD FAILED
File...... C:\Dokumente und
Einstellungen\chris\.maven\cache\maven-xdoclet-plugin-1.2\plugin.jelly
Element... taskdef
Line...... 5746
Column.... 81
taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
Total time: 4 seconds
I also checked my repository. The dependent jar referenced in the ejb´s
pom is also available:
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-ejb-module</artifactId>
<version>1.2</version>
<url>http://xdoclet.sf.net/</url>
</dependency>
Any ideas?
Thanks!
Christian
Christian Schlaefcke schrieb:
> Hi Folks,
>
> I´m trying to run "maven mutliproject:deploy" on a dummy project I
> just generated with "maven genapp [complex]". The project builds fine
> with cruisecontrol but when I trry to deploy I get this error:
>
> BUILD FAILED
> File...... ~\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly
> Element... maven:reactor
> Line...... 218
> Column.... 9
> Unable to obtain goal [multiproject:deploy-callback] --
> ~\.maven\cache\maven-xdoclet-plugin-1.2\plugin.jelly:5746:81:
> <taskdef> taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
> Total time: 13 seconds
>
> What´s missing and how do I get it?
>
> Thanks & Regards,
>
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
[m102] multiproject:deploy fails
Posted by Christian Schlaefcke <cs...@wms-network.de>.
Hi Folks,
I´m trying to run "maven mutliproject:deploy" on a dummy project I just
generated with "maven genapp [complex]". The project builds fine with
cruisecontrol but when I trry to deploy I get this error:
BUILD FAILED
File...... ~\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly
Element... maven:reactor
Line...... 218
Column.... 9
Unable to obtain goal [multiproject:deploy-callback] --
~\.maven\cache\maven-xdoclet-plugin-1.2\plugin.jelly:5746:81: <taskdef>
taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
Total time: 13 seconds
What´s missing and how do I get it?
Thanks & Regards,
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m2] Assembly-plugin & Manifest.mf
Posted by "J. Matthew Pryor" <jm...@mobiquity.net>.
I am building eclipse plugins, and with Eclipse 3.1 these are essentially
OSGI bundles
OSGI works from entries in the manifest, in particular Bundle-Classpath
attribute
I have a Mojo that reads the dependencies & updates the Bundle-Classpath of
the created artifact (a jar in this case).
What I then need to do is include all the dependent jars inside the main
artifact (exploded or not)
Obviously the assembly plugin suits my needs very well here, as it does all
the work, but it also adds its own Manifest.
I guess I saw an assembly simply as a 'superjar' but basically the same
artifact as the project is meant to produce, just one that includes
(transitively) all the dependent classes.
Does that make sense?
Matthew
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Wednesday, July 20, 2005 5:28 PM
> To: Maven Users List; jmp@mobiquity.net
> Subject: Re: [m2] Assembly-plugin & Manifest.mf
>
> I don't think this is intended - can you provide us with a
> small test case that exhibits the behaviour and what you were
> expecting so we can determine whether it is a
> misunderstanding or a defect?
>
> Thanks,
> Brett
>
> On 7/20/05, J. Matthew Pryor <jm...@mobiquity.net> wrote:
> > Perhaps I do not understand the purpose of the assembly
> plug-in, but
> > as it works in alpha-3, the "assembled" jar gets a new MANIFEST.MF
> > which is basically empty (and not the MANIFEST.MF from the
> created artifact).
> >
> > Maven-jar-plugin writes a lot of stuff to the MANIFEST (and I am
> > writing an Eclipse PDE plugin that augments that), but sadly it
> > doesn't get copied to the assembled jar.
> >
> > Is this intended?
> >
> > Should I move this to the dev list?
> >
> > Thanks,
> > Matthew
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Assembly-plugin & Manifest.mf
Posted by Brett Porter <br...@gmail.com>.
I don't think this is intended - can you provide us with a small test
case that exhibits the behaviour and what you were expecting so we can
determine whether it is a misunderstanding or a defect?
Thanks,
Brett
On 7/20/05, J. Matthew Pryor <jm...@mobiquity.net> wrote:
> Perhaps I do not understand the purpose of the assembly plug-in, but as it
> works in alpha-3, the "assembled" jar gets a new MANIFEST.MF which is
> basically empty (and not the MANIFEST.MF from the created artifact).
>
> Maven-jar-plugin writes a lot of stuff to the MANIFEST (and I am writing an
> Eclipse PDE plugin that augments that), but sadly it doesn't get copied to
> the assembled jar.
>
> Is this intended?
>
> Should I move this to the dev list?
>
> Thanks,
> Matthew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org