Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=18491
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11530status=1
Staging repo:
Just following
http://maven.apache.org/developers/release/maven-plugin-release.html
and Staging the latest documentation.
The stage completed successfully and its been a few hours since but
the staging documentation is still not available.
I have not verified the folder permissions to 0775 and
-1 non binding
MENFORCER-117 is not fixed as although the site links to the page now - the
page is useless (it is a cut and paste of requiredPLugin versions with only the
title changed).
snip file=requireNoRepositories.apt.vm
Require No Repositories
This rule enforces that all plugins have
On Fri, Jul 6, 2012 at 6:49 PM, Nord, James jn...@nds.com wrote:
-1 non binding
MENFORCER-117 is not fixed as although the site links to the page now - the
page is useless (it is a cut and paste of requiredPLugin versions with only
the title changed).
snip
On Fri, Jul 6, 2012 at 6:49 PM, Nord, James jn...@nds.com wrote:
-1 non binding
MENFORCER-117 is not fixed as although the site links to the page now - the
page is useless (it is a cut and paste of requiredPLugin versions with only
the
title changed).
snip
hi frnds,
Is it possible to create war and jar files with single pom.xml file.
i have to create jar file for my project along with war.
please help me on this if know how to do it.
Regrds.
Siva
--
View this message in context:
hi,
you can use maven assembly plugin to create the war for instance and let
maven jar plugin create the jar. Another way is to define maven war plugin
and maven jar plugin then use maven build helper plugin to attach both
artifacts
so yes that's possible
- Romain
2012/7/6 sivarenati
2012/7/5 Hervé BOUTEMY herve.bout...@free.fr:
+1
IMHO, we should have a site to document the artifact, even if minimal, since
these resources artifacts are not really accessible
Minimal site started: see
http://people.apache.org/~olamy/maven/apache-resource-bundles/
Will be sync here:
2012/7/6 Barrie Treloar baerr...@gmail.com:
Just following
http://maven.apache.org/developers/release/maven-plugin-release.html
and Staging the latest documentation.
The stage completed successfully and its been a few hours since but
the staging documentation is still not available.
I have
Yes, although it's not good practice. One project should only produce
one main artifact.
To have the maven-war-plugin create an additional jar artifact with
the java classes, have a look at this config parameter:
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
While it might be possible it is a bad idea that will cause your problems
most likely... why do you want to do that?
manfred
On Fri, July 6, 2012 12:18 pm, Anders Hammar wrote:
Yes, although it's not good practice. One project should only produce
one main artifact.
To have the
Yes, that's what I meant. It is much better to have two modules - one
jar project and one war project (with a dependency to the jar
artifact).
/Anders
On Fri, Jul 6, 2012 at 9:59 PM, Manfred Moser manf...@mosabuam.com wrote:
While it might be possible it is a bad idea that will cause your
Hi all Maven people,
I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.2
We solved 11 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=18392
There are still three issues in JIRA related to fluido:
Hi!
Some users of the Android Maven plugin are having trouble with the
compilation because the android.jar that includes all classes from harmony
is on the classpath together with the Oracle JDK.
When method signatures between the two differ e.g. like mentioned here
There are two things I'm thinking of, not sure if they will work:
1. Use toolchains [1]
2. Specify a compilerId, which would also mean writing the implementation
for it. [2] [3]
-Robert
[1] http://maven.apache.org/guides/mini/guide-using-toolchains.html
[2]
Hi,
I'd like to propose Tony Chemit as a committer.
He is active on Mojo for long time now.
He proposed some patches time ago and recently some more (I'm a bit
boring applying his patches: it probably means it's time to have him
here :-) ).
Here my +1.
Vote open for 72H.
Thanks
--
Olivier Lamy
Thanks... I will look into this.
On Fri, July 6, 2012 2:28 pm, Robert Scholte wrote:
There are two things I'm thinking of, not sure if they will work:
1. Use toolchains [1]
2. Specify a compilerId, which would also mean writing the implementation
for it. [2] [3]
-Robert
[1]
+1
On 07/07/2012, at 7:28 AM, Olivier Lamy wrote:
Hi,
I'd like to propose Tony Chemit as a committer.
He is active on Mojo for long time now.
He proposed some patches time ago and recently some more (I'm a bit
boring applying his patches: it probably means it's time to have him
here :-) ).
+1
-Lukas
On Fri, Jul 6, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to propose Tony Chemit as a committer.
He is active on Mojo for long time now.
He proposed some patches time ago and recently some more (I'm a bit
boring applying his patches: it probably means
+1
Hervé
- Mail original -
De: Lukas Theussl ltheu...@apache.org
À: Maven Developers List dev@maven.apache.org
Envoyé: Samedi 7 Juillet 2012 04:34:16
Objet: Re: [VOTE] Tony Chemit as Apache Maven committer
+1
-Lukas
On Fri, Jul 6, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org
+1
Den 6. juli 2012 kl. 23:28 skrev Olivier Lamy ol...@apache.org:
Hi,
I'd like to propose Tony Chemit as a committer.
He is active on Mojo for long time now.
He proposed some patches time ago and recently some more (I'm a bit
boring applying his patches: it probably means it's time to have
21 matches
Mail list logo
