$ mvn --version
Maven version: 2.0.7
Java version: 1.5.0_13
OS name: linux version: 2.6.22-14-generic arch: i386
Configuring mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' --
Configuring mojo
'org.apache.maven.plugins:maven-assembly-plugin:2.1:single' --
Configuring mojo
Nope, there's no javadoc or anything suspect. You'll have to take a
closer look.
But anyway, I was thinking of utting the docs in the release profile
so it only gets generated at release time. Does that make sense to
others?
- Brett
On 25/03/2008, at 3:50 PM, Joakim Erdfelt wrote:
$
On 24/03/2008, Benson Margulies [EMAIL PROTECTED] wrote:
I defined a new Mojo by extending AbstractCompilerMojo from the
maven-compiler-plugin.
It doesn't work, because the @component annotation for the compiler
manager
on AbstractCompilerMojo doesn't happen.
Obviously, it works in the
Cool! So can we get a release of the new maven-artifact bits out in
the next week or two?
--jason
On Mar 24, 2008, at 1:12 AM, Jason van Zyl wrote:
Oleg is back from Russian, I have his CLA now and that's what was
blocking the release. The release of 2.1-alpha-1 as well.
On 23-Mar-08,
Hokay.. I've had a bit more time for this.
I've re-rolled the patch against SVN, as I'm worried that the JIRA
issue was being confused with various different versions flying around
and changes happening in the test code.
Could someone try it against their local copy and see if the ITs work
the
just curious..
does this mean maven actually never worked fro japanese or chinese developers?
Milos
On Fri, Mar 21, 2008 at 8:15 PM, Benjamin Bentmann
[EMAIL PROTECTED] wrote:
Hi,
There are still several code spots in Maven that rely on the platform's
default encoding when processing text
C:\maven2example\maven2example_webappmvn package
[INFO] Scanning for projects...
[INFO]
[INFO] Building maven2example_webapp Maven Webapp
[INFO]task-segment: [package]
[INFO]
does this mean maven actually never worked fro japanese or chinese
developers?
It depends: As long as one sticks to US-ASCII when editing source files and
uses a platform encoding that has US-ASCII as a subset (UTF-8, Latin-X,
...), you won't notice Maven's misbehavior. Also, using Non-ASCII
Ah. So one might imagine someone refactoring things so that all the injected
fields of AbstractCompilerMojo were protected, so that an extending class in
another plugin could have parallel annotations.
On 24/03/2008, Benson Margulies [EMAIL PROTECTED] wrote:
Ah. So one might imagine someone refactoring things so that all the
injected
fields of AbstractCompilerMojo were protected, so that an extending class
in
another plugin could have parallel annotations.
while that might look ok at
AFAIK, the problem doesn't show for japanese nor chinese developers: even in
Japan or China, platform encoding on Unix or Windows is ASCII based,
precisely to avoid problems on simple ascii characters
like Benjamin says, the encoding issue is more subtle
There is one situation I know for this
It might be a good idea to run CI with IBM JDK even on more common
hardware. For example, I could not build maven with IBM JDK last time I
tried. I did not have much time to investigate, but it looked like IBM
JDK could not read modello's pom.xml as UTF-8.
--
Regards,
Igor
Hervé BOUTEMY
This looks like a misconfiguration of your pom. Please use the user list
for these questions as you will find a much larger audience who may have
seen this before.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 8:00 AM
To:
I will JIRA a request to make the AbstractCompilerMojo into a component.
On Mon, Mar 24, 2008 at 10:12 AM, Stuart McCulloch
[EMAIL PROTECTED] wrote:
On 24/03/2008, Benson Margulies [EMAIL PROTECTED] wrote:
Ah. So one might imagine someone refactoring things so that all the
injected
Hi,
It seems there are currently two places in JIRA to fill in issues regarding
documentation:
- the components Documentation: * in project MNG and
- the project MNGSITE
Is this situation by design, i.e. are the projects/components intended for
different purposes/audiences, or could we move
I think it's easier for the users to find if it's a component of MNG
rather than separate. So I would suggest we move MNGSITE over to MNG.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 11:39 AM
To: Maven Developers List
Subject: Where
I need with Maven command get jar with properties files(only with properties
files).
What i need add in my pom.xml?
(for example in the same directory with pom.xml I have aaa.properties and
bbb.properties, and need jar with both files)
Tanks!!!
--
View this message in context:
Where the source of the wiring information comes from and how it's
used in Plexus is completely decoupled.
What you see for Plexus components does not necessarily hold true for
Mojos because the intent is to allow the client, in this case the Mojo
system, to define its own APIs and wiring
Put them in src/main/resources and it should happen by default.
-Original Message-
From: PashaOvechkin [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 11:53 AM
To: dev@maven.apache.org
Subject: How to build properties JAR
I need with Maven command get jar with properties
have 2 files.
a.properties and b.properties.
Need to merge both and result will added in new created file c.properties.
How can I do it in my pom.xml?
For example - run : mvn deploy - and this action do concatenation and delpoy
file to repository...
Thanks!
--
View this message in context:
There isn't anything to concat properties files that I know of. This was
discussed last week on the users list, please use that for non maven
development questions.
Thanks,
Brian
-Original Message-
From: PashaOvechkin [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 11:57 AM
To:
Brian answered but read the getting started guide:
http://maven.apache.org/guides/getting-started/index.html
On 24-Mar-08, at 8:53 AM, PashaOvechkin wrote:
I need with Maven command get jar with properties files(only with
properties
files).
What i need add in my pom.xml?
(for example in
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:46 PM
To: Maven Developers List
Subject: [vote] release plugin tools 2.4.1
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:13 PM
To: Maven Developers List
Subject: [vote] release maven-reporting-impl 2.0.4.1
The old version 2.0.4 is trying to use an obsolete method in the
plugin-plugin tools. This was
Jason,
It seems to me, and I'm likely to be confused, that what we have here is a
collision of maven and plexus.
The maven-compiler-plugin is a thin wrapper on the plexus compiler system.
The plexus compiler system uses the plexus component model to add new
compilers. So, adding a new compiler
+1
-Lukas
Brian E. Fox wrote:
The old version 2.0.4 is trying to use an obsolete method in the
plugin-plugin tools. This was removed in 1.0-alpha-10 of the
doxia-site-render and causes problems with newer plugin tools and 2.0.9.
This release was cut from the old 2.0.4 tag because it's 2 years
+1
-Lukas
Brian E. Fox wrote:
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore compatibility. This release is dependent on the
maven-reporting-impl-2.0.4.1 release and 2.0.9 is dependent on this
release.
Staged at:
+1
On 24-Mar-08, at 9:10 AM, Brian E. Fox wrote:
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:13 PM
To: Maven Developers List
Subject: [vote] release maven-reporting-impl 2.0.4.1
The old version 2.0.4 is trying to use an
+1
On 24-Mar-08, at 9:10 AM, Brian E. Fox wrote:
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:46 PM
To: Maven Developers List
Subject: [vote] release plugin tools 2.4.1
There were several regressions in the 2.4 release.
+1
On Mon, Mar 24, 2008 at 11:21 AM, Jason van Zyl [EMAIL PROTECTED] wrote:
+1
On 24-Mar-08, at 9:10 AM, Brian E. Fox wrote:
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:13 PM
To: Maven Developers List
+1
--
Olivier
2008/3/24, Brian E. Fox [EMAIL PROTECTED]:
Anyone else?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:46 PM
To: Maven Developers List
Subject: [vote] release plugin tools 2.4.1
There were several regressions in
-1
I tried to use this via maven-plugin-plugin from your staging repo. The
plugin was downloaded correctly, but the reporting-impl wasn't. At first
I thought that there was something wrong with my config, but it turned
out it wasn't.
The 2.0.4.1 pom [1] doesn't have a groupId specified,
Nice catch. I knew I didn't want to use the new parent for a reason but
it was a disaster trying to get everything updated correctly.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 2:04 PM
To: Maven Developers List
Subject: Re: [vote]
Restaged, only the group Id has changed back to
org.apache.maven.reporting. The original was out for 3 days, this vote
will be for an additional 24 hours given the small change.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 5:13 PM
To: Maven
Dears
Could you please help me to include folder *.svn *with all its
content to resulting file like jar?
Actually I need this only within resources (folder:
*src/main/resources*), so, if you try to specify include pattern
in *maven-resources-plugin *settings - it does not work.
On Mon, Mar 24, 2008 at 12:42 PM, Yuriy Krymlov [EMAIL PROTECTED] wrote:
Could you please help me to include folder *.svn *with all its
content to resulting file like jar?
Actually I need this only within resources (folder:
*src/main/resources*), so, if you try to specify include
Hi,
I leave another 24 hours for anyone to raise an objection
on me closing these issues for the invoked reasons.
Regards,
Raphaël
2008/3/17, Raphaël Piéroni [EMAIL PROTECTED]:
Hi guys,
I would like to close some issues.
Some [1] because the release of the archetype plugin version
On Mon, Mar 24, 2008 at 1:48 PM, Raphaël Piéroni
[EMAIL PROTECTED] wrote:
I leave another 24 hours for anyone to raise an objection
on me closing these issues for the invoked reasons.
Please don't think you need to call a vote for this sort of thing,
we're not that formal. :)
If you have
+1
Working fine now. Thanks Brian!
Brian E. Fox wrote:
Restaged, only the group Id has changed back to
org.apache.maven.reporting. The original was out for 3 days, this vote
will be for an additional 24 hours given the small change.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL
+1
Brian E. Fox wrote:
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore compatibility. This release is dependent on the
maven-reporting-impl-2.0.4.1 release and 2.0.9 is dependent on this
release.
Staged at:
Maybe we should close them all and see which ones the users really want ;-)
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 4:54 PM
To: Maven Developers List
Subject: Re: [VOTE] [Archetype] Closing some issues
On Mon, Mar 24, 2008 at 1:48 PM,
I like the idea: easier to do than having access to a Z/OS box (anyone able to
deploy a CI on a Z/OS box?), even if every aspect is not covered (for example
it doesn't fail if encoding parameter has not been set in compiler plugin)
But if we do so on a whole CI server, I fear the havoc will be
But if we do so on a whole CI server, I fear the havoc will be bigger than
expected
I surely did not mean to do this immediately for the main CI builds. Given
Maven's current state, it's some future goal. Maybe we could setup a
secondary CI build job for this, such that people working on the
I can setup an alternate build for Maven. What java options do I need to
set to change the encoding?
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 6:12 PM
To: Maven Developers List
Subject: Re: Maven and File Encoding
But if we do so
I can setup an alternate build for Maven.
Cool, thanks Brian.
What java options do I need to set to change the encoding?
Setting the system property file.encoding should do:
-Dfile.encoding=UTF-16
either via MAVEN_OPTS or directly on the java command line.
Benjamin
I disagree. For ourselves, as well as our users, having a separate issue
tracker for the site is a good thing. MNG is currently a *large* heap of
issues and different (JIRA) component, and I believe it's difficult for
a user to grasp. MNG is in my world about Maven - the application, and
that
Yah, I actually agree with Dennis. I prefer them separate so I can
track runtime problems with Maven versus what we say about the runtime.
On 24-Mar-08, at 4:25 PM, Dennis Lundberg wrote:
I disagree. For ourselves, as well as our users, having a separate
issue tracker for the site is a good
Right now there are approximately 4 times more issues in MNG under
documentation categories than there is in MNGSITE, so I think my hunch
about the users is right. If you want a report, just exclude
documentation...
But whatever I don't care as long as it's easy and _obvious_. It took me
over a
On 24-Mar-08, at 4:42 PM, Brian E. Fox wrote:
Right now there are approximately 4 times more issues in MNG under
documentation categories than there is in MNGSITE, so I think my hunch
about the users is right. If you want a report, just exclude
documentation...
So where they put it and where
But whatever I don't care as long as it's easy and _obvious_.
Adding a description to the JIRA project MNG, that provides a hyperlink to
MNGSITE and some hinting words might further help to direct users to the
right place.
It took me over a minute to find the right project (and I knew that it
I renamed the site so it shows up next to Maven 2. It still gets drowned
out in the noise. Are we still actively working on the Maven 1.x plugin
stuff? Why not move these issues to a subcomponent of the Maven 1
project? Failing that, we should rename them so they come after Maven 2
stuff.
This is a good summary of the current operation. I need to think more on
the 2.1 impl, but this is a good start.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 5:41 PM
To: Maven Developers List
Subject: Please Comment: Maven 2.1 Plugin and
It's setup and also running the Its.
https://ci.sonatype.org/job/Maven-2.0.x-ITs-UTF-16/3/console
Assuming I didn't mess up the config (you can see the execution at the
beginning of the console output) it seems to be running without any
errors so far.
-Original Message-
From: Benjamin
Hi,
I have been scratching my head on this one for awhile.
We have an applet which the class files are packaged up into a JAR file.
This JAR file is then packaged up inside a WAR file which then gets
packaged in an EAR file so that it can be deployed onto Websphere
Application Server 6.1 (our
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\s.thotakomuraiahc:
C:\cd maven2example
C:\maven2examplecd maven2example_webapp
C:\maven2example\maven2example_webappmvn package
[INFO] Scanning for projects...
[INFO]
When I am using tomcat 6.0 I am facing problem with
container.ContainerException any one help me for solution
In my build script how to run the server and how to past the war file in
target tomcat 6.0 folder how to run the server and stop the server with
maven2 build script
Thanks Regards,
I found that one of my dependencies bundles some source in the jar... the
compiler plugin compiles it and it ends up in my artifact. Has anyone see
this before?
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
57 matches
Mail list logo
