Hi,
there's only a per-artifact transformation possible right now with one
layout pattern.
You cannot apply a custom pattern on just a subset of artifacts, that
would require several enhancements.
thanks,
Robert
On Mon, 06 Feb 2017 15:15:18 +0100, Rolf Rosenbaum, sdbn Solutions GmbH
wro
Hi,
> I add this plugin to my project ,but it doesn't work ,the generated
> jar package doesn't contain dependcy jars
The maven-jar-plugin does not aggregate dependencies.
To do that, check out these plugins:
* http://maven.apache.org/plugins/maven-assembly-plugin/
* https://maven.apache.org/p
Hey,
It is good news! Thanks again.
BR,
Csaba
Hi,
the VOTE for a fixed version maven-jar-plugin will be finished within a
few days which includes this fix..
so only a few days to live with this remporary solution.
Kind regards
Karl Heinz Marbaise
On 6/8/16 11:48 PM, Csaba Kozák wrote:
Hey Karl,
Updating plexus-archiver seems to do the
Hey Karl,
Updating plexus-archiver seems to do the trick.
On 29 May 2016 at 15:21, Karl Heinz Marbaise wrote:
> Hi,
>
> I have checked a setup with -Xmx32m ...which will not work...but if you
> increase to -Xmx40m it will work...
>
> Kind regards
> Karl Heinz Marbaise
> On 5/29/16 3:11 PM, Karl
Hi,
I have checked a setup with -Xmx32m ...which will not work...but if you
increase to -Xmx40m it will work...
Kind regards
Karl Heinz Marbaise
On 5/29/16 3:11 PM, Karl Heinz Marbaise wrote:
Hi,
On 5/26/16 9:13 PM, WonderCsabo wrote:
Hey,
After i updated the maven-jar-plugin to version 3.
Hi,
On 5/26/16 9:13 PM, WonderCsabo wrote:
Hey,
After i updated the maven-jar-plugin to version 3.0.0, i started to see
these problems on my CI build:
https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473
I can verify that this only happens with 3.0.0.
Could you please t
This issue has been fixed in plexus archiver, which has not been released
yet.
Kristian
Hey,
After i updated the maven-jar-plugin to version 3.0.0, i started to see
these problems on my CI build:
https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473
I can verify that this on
Please file a ticket at https://issues.apache.org/jira/browse/MJAR
Provide as much details (Maven version, JDK, OS, etc) as possible and
preferably a project to reproduce.
/Anders
On Thu, May 26, 2016 at 9:13 PM, WonderCsabo wrote:
> Hey,
>
> After i updated the maven-jar-plugin to version 3.0
Thanks a lot!
will wait for the updated version :)
not sure how plugin in eclipse can be updated with snapshot version :(
On Mon, May 23, 2016 at 11:44 AM, Karl Heinz Marbaise
wrote:
> Hi Maxim,
>
> I've already created an issue for m2e:
>
> https://github.com/tesla/m2eclipse-mavenarchiver/issue
Hi Maxim,
I've already created an issue for m2e:
https://github.com/tesla/m2eclipse-mavenarchiver/issues/8
Kind regards
Karl Heinz Marbaise
On 5/23/16 5:54 AM, Maxim Solodovnik wrote:
Hello Karl,
do I need to create JIRA issue? or maybe you can point me to the correct
tracker I can file issu
Hello Karl,
do I need to create JIRA issue? or maybe you can point me to the correct
tracker I can file issue against m2e?
On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
>
> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>
>> I got following errors in eclipse:
>>
>>
>> org.apa
Awesome, case closed :)
On Sun, 22 May 2016 00:05:49 +0200, Dan Tran wrote:
I just checked appassembler source, this plugin does populate project
artifact if it is found. This mean i just need to configure the
appassembler to run at package phase. It works
-D
On Sat, May 21, 2016 at 12:40 PM
I just checked appassembler source, this plugin does populate project
artifact if it is found. This mean i just need to configure the
appassembler to run at package phase. It works
-D
On Sat, May 21, 2016 at 12:40 PM, Dan Tran wrote:
> that would be awesome. appassembler-m-p should copy the pri
that would be awesome. appassembler-m-p should copy the primary jar to its
lib directory. However, this also means it must run at package phase in
order to see the jar-plugin output
-D
On Sat, May 21, 2016 at 1:39 AM, Robert Scholte
wrote:
> Hi Dan,
>
> So if I've correct the appassemble-maven-
Hi Dan,
So if I've correct the appassemble-maven-plugin assumes all jars are
already put in the /lib directory by another plugin. I think it is more
correct to let the plugin pull its libraries to this folder instead.
WDYT?
Robert
On Fri, 20 May 2016 22:26:45 +0200, Dan Tran wrote:
I m
Hi Dan,
On 5/20/16 10:26 PM, Dan Tran wrote:
I meant appassemble-maven-plugin.
Ah sorry could have imagined that myself...
very likely the error is from the fix of
https://issues.apache.org/jira/browse/MJAR-198
For now, I will need to use antrun to copy the local primary jar to the
place I
I meant appassemble-maven-plugin.
very likely the error is from the fix of
https://issues.apache.org/jira/browse/MJAR-198
For now, I will need to use antrun to copy the local primary jar to the
place I need. Maybe, appassemble should do this for me
btw, if have RPM module but does invocation o
Hi Dan,
On 5/20/16 10:04 PM, Dan Tran wrote:
Hi Robert,
According to the jar plugin source outputDirectory is not read only. that
is why I can change the default value.
here is my use case
- Start out of jar module with a profile to create the RPM
- In the profile, use assembler-maven-pl
2016 22:05
Subject: Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Robert,
According to the jar plugin source outputDirectory is not read only. that
is why I can change the default value.
here is my use case
- Start out of jar module with a profile to create the RPM
- In the profile
Hi Robert,
According to the jar plugin source outputDirectory is not read only. that
is why I can change the default value.
here is my use case
- Start out of jar module with a profile to create the RPM
- In the profile, use assembler-maven-plugin to create staging
distribution
- since
Dan,
outputDirectory has become a readonly parameter.
The reason is that you can set it with . Does
that work for you?
thanks,
Robert
On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise
wrote:
Hi Dan,
On 5/20/16 7:16 AM, Dan Tran wrote:
Hi
My jar project can also create RPM via
Hi,
On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
I got following errors in eclipse:
org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
/openmeetings-core line 1 Maven Configuration Problem
comm
Hi Dan,
On 5/20/16 7:16 AM, Dan Tran wrote:
Hi
My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
throws this error
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
(project-jar-for-docker) on project xxx: You have to use a classifier
to at
sorry about the noise, my pom also calls
org.apache.maven.plugins
maven-jar-plugin
project-jar-for-rpm
package
jar
${rpm.staging.directory}/lib
I got following errors in eclipse:
org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
/openmeetings-core line 1 Maven Configuration Problem
command line build works as expected
On Fri, May 20, 20
Hi Nick,
Nick Stolwijk wrote:
> Hi Folks,
>
> I found a little curiosity in the maven jar plugin.
>
> if you specify includes and the skipIfEmpty property a jar is still
> created and attached while it only has a pom file in it. I would have
> expected that the creation of the jar was skipped i
Hi,
I think I faced something similar, some time ago, but not absolutely sure,
here is what I remember:
works by testing if directory is present, so if
src/test/java is present (no matter if empty or not)
jar will be created.
hope it helps
tonio
On Mon, Apr 28, 2014 at 6:12 AM, Nick Stolw
If you use the bundle style in your pom, then its bnd
that does the actual jar creation, and NOT the traditional jar plugin.
We hit this same issue awhile ago when including compiled coffee-script into
our jars, just putting them directly in target/classes doesn't "just work".
Mark
On 13/08/20
i est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: R
27;information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>> From: tommybsvens...@me.com
&g
>> Most likely the "bundle" packaging does not include META-INF for some
>> reason. I would talk to the Apache Felix people about this issue so
>> they can resolve it in their code.
>
> This is working as designed, as covered in the FAQ:
Thanks Stuart. This is a good thing to keep in mind for when
On 12 Aug 2012, at 03:54, Wayne Fay wrote:
>> I'm also using the Apache Felix bundle-plugin which allows for:
>>
>>bundle
>
> This is not a packaging delivered by Apache Maven. Thus you can
> "blame" whoever is making this packaging available to you.
>
>> That is, I can use either or o
> I'm also using the Apache Felix bundle-plugin which allows for:
>
> bundle
This is not a packaging delivered by Apache Maven. Thus you can
"blame" whoever is making this packaging available to you.
> That is, I can use either or of "bundle" or "jar" for packaging. However when
> i use:
ni.
> From: tommybsvens...@me.com
> Subject: Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! -
> Problem solved
> Date: Sat, 11 Aug 2012 18:56:43 +0200
> To: users@maven.apache.org
>
> I finally found the source of this problem! Or close to it at least. I hav
I finally found the source of this problem! Or close to it at least. I have
managed to get my META-INF/persistence.xml included in the jar, but I'm unsure
what is to blame :-).
I'm also using the Apache Felix bundle-plugin which allows for:
bundle
This due to the following configuratio
> I was hoping for a "Well, thats easy, just do ..." :-). But you are of course
> right
> Wayne, I need to isolate what is causing this. Thanks.
If META-INF/persistence.xml was not even showing up in target, then we
might be able to provide a simple "recipe" to solve it. But that is
not the case
Which packaging do have? Can you post your POM?
Am 21.07.2012 22:51 schrieb "Tommy Svensson" :
> Hello maven fans,
>
> I've become slightly balder today. I've been tearing my hair over why JPA
> keeps insisting it cannot find my persistence unit. Everything in my
> persistence.xml file is correct
I was hoping for a "Well, thats easy, just do ..." :-). But you are of course
right Wayne, I need to isolate what is causing this. Thanks.
/Tommy
22 jul 2012 kl. 05:30 skrev Wayne Fay:
>> Maven just refuses to include META-INF/persistence.xml in the jar no matter
>> what I do! It resides in src
> Maven just refuses to include META-INF/persistence.xml in the jar no matter
> what I do! It resides in src/main/resources/META-INF. After building it is
> also
> in target/classes/META-INF along with MANIFEST.MF, but it is missing in the
> jar file.
Try a very simple test...
Run "mvn archetype:
Remove config.properties from your server jar project!
Put it in src/main/resources of the war project (as you would for any Maven
project).
/Anders
On Fri, Mar 5, 2010 at 15:34, maven apache wrote:
> 2010/3/5 Anders Hammar
>
> > Generally, read files from the classpath.
> > So, remove the con
2010/3/5 Anders Hammar
> Generally, read files from the classpath.
> So, remove the config.properties form your server project. For any unit
> tests you can put a config.properties under src/test/resources (will be on
> the test class path). The add the config.properties to you war project so
> t
Generally, read files from the classpath.
So, remove the config.properties form your server project. For any unit
tests you can put a config.properties under src/test/resources (will be on
the test class path). The add the config.properties to you war project so
that it will be added to the webapp'
Stephen Duncan Jr wrote:
> I see that http://jira.codehaus.org/browse/MJAR-28 was "fixed" in the 2.3
> release. From my perspective, this seems to have broken things, including a
> viable working system I had using 2.2.
>
> In 2.3 I have several SNAPSHOT dependencies, but when I build a jar with
Clicked on send before pasting the link:
http://jira.codehaus.org/browse/MJAR-61
Tomas Darbois
-Message d'origine-
De : Thomas Darbois
Envoyé : mercredi 23 avril 2008 11:00
À : 'Maven Users List'
Objet : RE: Maven Jar plugin 2.0 : ClassPath in manifest
Well i ve found t
Well i ve found the Jira that is linked to that problem :
Tomas Darbois
Edifixio Grenoble - Projet ScorWare
04 76 29 89 27
[EMAIL PROTECTED]
-Message d'origine-
De : Thomas Darbois [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 23 avril 2008 10:10
À : Maven Users List
Objet : RE:
I would
prefer to avoid that).
And indeed I forget yesterday to put the maven version I'm using.
It's maven 2.0.8.
Tomas Darbois
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lee Meador
Envoyé : mardi 22 avril 2008 19:34
À : Mave
I'm not real familiar with that part of maven, but ...
Did you try adding a to the pom for "test" to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto project. You could try copying them from
"Wendy Smoak" <[EMAIL PROTECTED]> wrote on 03/01/2008 09:54:25 PM:
> On Sat, Mar 1, 2008 at 7:50 PM, <[EMAIL PROTECTED]> wrote:
> > The following POM works as expected when run by itself (it uses
> > org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as
part of
> > a multi-module
On Sat, Mar 1, 2008 at 7:50 PM, <[EMAIL PROTECTED]> wrote:
> The following POM works as expected when run by itself (it uses
> org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as part of
> a multi-module build it uses
> org.apache.maven.plugins:maven-jar-plugin:2.2:jar. Does anyo
Thanks Wendy. I was using the version 2.0 and the fix was available in
the version 2.1. I also tried by not giving the version number so that
maven can use the latest version but it was giving errors.
Now, everything is fine.
Regards,
Shakun
Wendy Smoak wrote:
On Wed, Feb 27, 2008 at 5:08 AM,
On Wed, Feb 27, 2008 at 5:08 AM, Shakun Gupta <[EMAIL PROTECTED]> wrote:
> I am using Maven 2, and i added the configuration of jar-plugin and
> war-plugin. I am able to assemble the war at a different place using
> outputDirectory property. But, this does not work with jar-plugin. I
> have re
please ignore this thread - issue resolved
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in E-Mails. Any views and
opinions expressed may be personal to the sender and are not necessarily those
of Eurobase. Eurobase
maybe you should use maven-assembly-plugin
http://maven.apache.org/plugins/maven-assembly-plugin/
Rex
On Feb 19, 2008 11:53 AM, Julien FOROT <[EMAIL PROTECTED]> wrote:
> Hi !
>
> I want to make 2different jars from the same source folder. So I made
> this structure :
>
> - jar
>-- pom.xml
>
Julien FOROT schrieb:
> Hi !
>
> I want to make 2different jars from the same source folder. So I made
> this structure :
>
> - jar
>-- pom.xml
>-- src
>-- heavyJar
>--- pom.xml
>-- lightJar
> --- pom.xml
>
> I want that the heavy and light Jar used the folder src as
>
Forget this last post. I was trying to include integration tests in the
same module and that was a bad idea.
-Original Message-
From: Matthew Shaw [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 13 February 2008 11:37 AM
To: Maven Users List
Subject: MAVEN-JAR-PLUGIN
Hi there,
I am trying
age -
> Wrom: CONEUQZAAFXISHJEXXIMQZUIVOTQNQEM
> To: "Maven Users List"
> Sent: Monday, January 28, 2008 8:06 PM
> Subject: Re: maven-jar-plugin location
>
>
> > Try mvn -U to force Maven to check for plugin updates.
> >
> > Wayne
> >
> &g
008 8:06 PM
Subject: Re: maven-jar-plugin location
> Try mvn -U to force Maven to check for plugin updates.
>
> Wayne
>
> On 1/28/08, Martin Gainty <[EMAIL PROTECTED]> wrote:
> > I see the following error while building with maven-2.0.8
> >
> > [INFO] The plu
Try mvn -U to force Maven to check for plugin updates.
Wayne
On 1/28/08, Martin Gainty <[EMAIL PROTECTED]> wrote:
> I see the following error while building with maven-2.0.8
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-jar-plugin' does not exist
> or
> no valid version could be found
>
Maybe you could set the settings to
target/resources/META-INF/MANIFEST.MF (or whatever the right path is), and then
use maven filtering to transform the "template" in src/main/resources into the
form you want.
Regards,
Simon
Julien CARSIQUE <[EMAIL PROTECTED]> schrieb:
> Sorry, I didn't
Sorry, I didn't list all the tests I've done.
I tried what you suggest, the result is a jar containing a new manifest
with the wanted manifest entries from pom.xml but without all the
content of the manifest present in src/main/...
While doing this, I'm trying to manage with the buildnumber pl
Try removing the entry and see what happens when
there's a file present in that location, and what happens when there's
not (check target to see what ends up in the JAR). By default, Maven
looks for the file in that location, and uses it if its there, or
generates one if there's not.
I'm honestly
It's here:
http://jira.codehaus.org/browse/MJAR-30
pdelaney wrote:
Hello;
I am building an executable jar file and I am trying to remove my
database.properties file from the jar because I want to control the
properties outside of the jar file.
In my build I execute mvn package I have the mav
Thanks for you reply.
2007/9/25, Wayne Fay <[EMAIL PROTECTED]>:
>
> The other approach of course is to change your JAVA_HOME and use the
> jdk4 compiler to run your Java process. Then everything will match up
> and you won't need any extra configuration.
>
> Wayne
>
> On 9/25/07, Tim Kettler <[EM
The other approach of course is to change your JAVA_HOME and use the
jdk4 compiler to run your Java process. Then everything will match up
and you won't need any extra configuration.
Wayne
On 9/25/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> this is because the compilation of the sources
Hi,
this is because the compilation of the sources (compiler-plugin) and the
packaging (jar-plugin) is done in two steps. Even if you fork the
compiler, the jar-plugin execution isn't forked and thus runs under the
java version you invoked maven with.
You can override the maven generated en
My problem is not on jdk version.
I just want to test maven.
And when you use the fork mode in compiler the jdk's manifest entry is not
correct.
So I want to know how to get the correct value in manifest.
Thanks
--
CletteBou
clettebou.miniville.fr
2007/9/25, Jim Sellers <[EMAIL PROTECTED]>:
>
>
Do you just need to compile to 1.4 or do you actually need to use a
different jdk (sun vs ibm)?
If you just need 1.4, this might help:
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
Jim
On 9/25/07, Guillaume Boucherie <[EMAIL PROTECTED]> wrote
Vote for http://jira.codehaus.org/browse/MJAR-82 :)
With kind regards,
Geoffrey De Smet
Tim Kettler schreef:
This is currently not possible with the jar-plugin , but it sounds like
a useful feature. The assembly-plugin has an option for dependency-sets
called 'outputFileNameMapping' [1] where
alright, sounds like a good idea. just wanted to ensure that it is not a
configuration error from my side.
Tim Kettler wrote:
>
> This is currently not possible with the jar-plugin , but it sounds like
> a useful feature. The assembly-plugin has an option for dependency-sets
> called 'output
This is currently not possible with the jar-plugin , but it sounds like
a useful feature. The assembly-plugin has an option for dependency-sets
called 'outputFileNameMapping' [1] where you can specify the format of
the filenames. Something similar would be useful for the format of the
classpath
yes, for a workaround i did this too. but hoped there would be a tweak in
maven-jar-plugin, so artifactId could standalone because information of
a.b.c.d is already provided. this way i could avoid duplication.
Michael McCallum-3 wrote:
>
> i name my projects
>
> a.b.c
> a.b.c.d
>
> that way
i name my projects
a.b.c
a.b.c.d
that way all the aggregations never have clashes... I only wish library
providers would to the same... it seems all the simple things are overlooked
On Monday 27 August 2007 22:25, aldana wrote:
> hi,
>
> maven amongst others is using groupId to avoid name clash
On 8/12/07, Greg Morgan <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Zarick Lau wrote:
> >> You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10.
> >
> > Thanks! I believe so !!
> >
> >> Someone needs to update the maven-jar-plugin/maven-arc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zarick Lau wrote:
>> You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10.
>
> Thanks! I believe so !!
>
>> Someone needs to update the maven-jar-plugin/maven-archiver to use a
>> later version of plexus-archiver.
>
> Need to c
On 8/10/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
> Zarick Lau wrote:
> > Dear users and developers,
> >
> > I have a module with this files
> > /src/main/resources/META-INF/persistence.xml
> > /src/main/resources/log4j.xml
> >
> > In the pom, I have set true for the maven-jar-plugin
> > After pac
Zarick Lau wrote:
> Dear users and developers,
>
> I have a module with this files
> /src/main/resources/META-INF/persistence.xml
> /src/main/resources/log4j.xml
>
> In the pom, I have set true for the maven-jar-plugin
> After package as a jar, the log4j.xml is listed but
> META-INF/persistence.x
Hi Zhang,
All MANIFEST.MF files that contain lines longer than 72 bytes are invalid,
according to the Jar Manifest specification.
That's why the plugin splits them, which is the only way to create a valid
manifest.
And no, AFAIK, you can not force the plugin to create invalid manifest
files.
Her
On Fri, 2007-06-08 at 16:21 +0800, 張旭 wrote:
> Dear friends,
> I have encountered a strange problem when specify custom manifest file when
> using the maven-jar-plugin.
> I've a very very long line in the manifest file that maybe have hundreds
> columns.
> It seems that the plug-in will automatica
I had to do this a while back so it might have changed in a more
recent build, but when I had something like this, I just had to
specify my own complete MANIFEST.MF file and tell Maven to use it
instead of generating one. You either took the Maven-generated
Manifest or built your own entirely (at
[EMAIL PROTECTED]
> Sent: Tuesday, 25 July, 2006 02:37
> To: users@maven.apache.org
> Subject: Re: maven-jar-plugin: include/exclude functionality?
>
>
>
> Simon Kitching-2 wrote:
> >
> > I need to build 3 jars from the classes created by a
> module; a "full&qu
Simon Kitching-2 wrote:
>
> I need to build 3 jars from the classes created by a module; a "full"
> jar and two jars that contain subsets of the available classes.
>
If you need to build 3 different jars (not taking into account javadoc and
sources jar) from a single module, it's probably that
Not sure where on the web you can currently find it, but if you pull
down the code from SVN to your local box and then run "mvn site", it
should build the SNAPSHOT site on your local box for viewing etc...
Wayne
On 7/6/06, Sebastien Cesbron <[EMAIL PROTECTED]> wrote:
Hi,
Is there a place where
On 7/6/06, Sebastien Cesbron <[EMAIL PROTECTED]> wrote:
Hi,
Is there a place where it is possible to see snapshot documentation ?
I search the maven jar plugin last snapshot documentation to see if it
is more verbose on jar signing.
best is to look at the code...
http://svn.apache.org/viewvc/
Hi Ben,
You can checkout the jar plugin from svn and install it locally. Here's
the url:
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin
Thanks,
Odea
ben short wrote:
I get the following error while trying to build the maven repository
manager. Any ideas where i can get
Oops wrong plugin
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/
This is the correct location.
On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
Here
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin/
Just checkout the code and run "mvn install".
Here
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin/
Just checkout the code and run "mvn install".
On 5/20/06, ben short <[EMAIL PROTECTED]> wrote:
Alexandre,
Thanks for the reply, the emails i posted dint show in my inbox for some
reason, so i assumed that they didnt get
Alexandre,
Thanks for the reply, the emails i posted dint show in my inbox for some
reason, so i assumed that they didnt get sent properly.
Do you know where i can get the snapshots from?
Ben
On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
By the way, don't post three mails about th
By the way, don't post three mails about the same thing. It's a bit annoying
On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
I had the same error, there is definitly something wrong in Maven
2.0.4 with remote snapshots repositories. Install it manually and
everything work fine.
On 5/20
I had the same error, there is definitly something wrong in Maven
2.0.4 with remote snapshots repositories. Install it manually and
everything work fine.
On 5/20/06, ben short <[EMAIL PROTECTED]> wrote:
I get the following error while trying to build the maven repository
manager. Any ideas where
It works. manifestFile is a var under MavenArchiveConfiguration so
it needs to be declared under
org.apache.maven.plugins
maven-jar-plugin
META-INF/MANIFEST.MF
MavenArchiveConfiguration
- sachin
On Mar 17, 2006, at 8:3
I've opened MNG-2156 on this.
- sachin
On Mar 16, 2006, at 8:02 PM, Sachin Patel wrote:
Yes, this is exactly what I have. I took a quick peak at the
plugin code and I didn't see any reference to specifying a
manifestFile either.
...
org.apache.maven.plugins
maven-jar-p
Yes, this is exactly what I have. I took a quick peak at the plugin
code and I didn't see any reference to specifying a manifestFile either.
...
org.apache.maven.plugins
maven-jar-plugin
META-INF/MANIFEST.MF
org.apache.maven.plugins
maven-jar-plugin
/path/to/MANIFEST.MF
According to the documentation, this should work. Is it what you have
in your pom.xml file?
On 3/16/06, Sachi
Adding the following manifestFile element failed to work for me as I
get the following error..
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT
Cause: Cannot find setter nor field in
org.apache.maven.archiver.ManifestConfiguration for
this is my pom, it works fine!
org.apache.maven.plugins
maven-jar-plugin
And I think to add custom entries, you need to write them in a base
manifest file wich you specify to be added to the generated manifest
file.
You just need to add this line to your plugin configuration :
/path/to/MANIFEST.MF
On 12/30/05, Alexandre Poitras
>From your example, I am guessing you are looking for a way to specify
the classpath.
If that the case, you work too hard. Maven is all about laziness and
of course it can generate the class path for you :
org.apache.maven.plugins
maven-jar-plugin
98 matches
Mail list logo
