brett 2005/04/05 23:21:16
Modified:maven-core pom.xml
Log:
rename the assembly plugin
Revision ChangesPath
1.29 +1 -1 maven-components/maven-core/pom.xml
Index: pom.xml
===
RCS file: /hom
brett 2005/04/05 23:20:42
Modified:maven-plugins pom.xml
Removed: maven-plugins/maven-assemble-plugin .cvsignore build.sh
pom.xml
maven-plugins/maven-assemble-plugin/src/main/java/org/apache/maven/plugin/assemble
Ass
brett 2005/04/05 23:20:07
Log:
rename to assembly
Status:
Vendor Tag: ASF
Release Tags: INIT
N maven-components/maven-plugins/maven-assembly-plugin/.cvsignore
N maven-components/maven-plugins/maven-assembly-plugin/build.sh
N maven-components/maven-plugins/maven-ass
issues to resolve on the packaging vs type mismatch
---
Key: MNG-257
URL: http://jira.codehaus.org/browse/MNG-257
Project: m2
Type: Task
Components: design
Reporter: Brett Porter
Fix For: 1.0-alpha-2
ok,
With 12 +1's and 3 +0's, the lists will be merged. You will probably
hear from someone when this happens.
I will get this under way by changing the JIRA notifications.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
>I'm in the same situation :-)
>
>
Did nobody read my response to that? Anyway, I guess these all count as
+0's?
>
>
>> - rough planning for m2. First alpha, first beta, planned 1.0 and their
>>contents
>>
>>
>
>I think such roadmap would be important for Maven 1.1 as well.
>
>
JIRA is
On Tue, 2005-04-05 at 18:00 +0200, Vincent Massol wrote:
> I feel a bit like Eric which is why I've not answered to the vote so far
> (I'm still unsure whether it's a good idea or not).
I'm in the same situation :-)
> - rough planning for m2. First alpha, first beta, planned 1.0 and their
> con
[
http://jira.codehaus.org/browse/MPJCOVERAGE-18?page=comments#action_31625 ]
Julie Cowart commented on MPJCOVERAGE-18:
-
This fix doesn't actually appear to have been applied to CVS.
> Inner/anonymous classes report uncomplete
> ---
[ http://jira.codehaus.org/browse/MPECLIPSE-86?page=comments#action_31622 ]
Morten Kristiansen commented on MPECLIPSE-86:
-
I just found out that Eclipse ProjectSet files also can contain Subversion
data. I await submitting the patch until th
Author: evenisse
Date: Tue Apr 5 14:29:56 2005
New Revision: 160226
URL: http://svn.apache.org/viewcvs?view=rev&rev=160226
Log:
Fix NullPointerException when version isn't define.
Modified:
maven/maven-1/core/trunk/src/java/org/apache/maven/repository/AbstractArtifact.java
Modified:
maven
JAVA_HOME is set to invalid directory
-
Key: MAVEN-1588
URL: http://jira.codehaus.org/browse/MAVEN-1588
Project: maven
Type: Bug
Versions: 1.0.2
Environment: Win XP Professional, SP2, j2eesdk-1_4_01_2005Q1-windows
Repo
New eclipse:projectset goal
---
Key: MPECLIPSE-86
URL: http://jira.codehaus.org/browse/MPECLIPSE-86
Project: maven-eclipse-plugin
Type: New Feature
Reporter: Morten Kristiansen
Priority: Trivial
I have (soon) created a patch for a ne
Author: trygvis
Date: Tue Apr 5 10:33:47 2005
New Revision: 160203
URL: http://svn.apache.org/viewcvs?view=rev&rev=160203
Log:
o Adding project properties to configure the version, package with version and
model file parameters.
o Adding jpox goals.
Added:
maven/maven-1/plugins-sandbox/tru
Distribution:
http://www.codehaus.org/~maven/m2/m2-20050405.131155.tar.gz
Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050405.131155.txt
I think that sounds great. Please submit one via the JIRA site for the
Eclipse plugin. We should also move this conversation over to
[EMAIL PROTECTED]
Eric
On Apr 5, 2005, at 12:35 PM, Morten Kristiansen wrote:
Have you given this any more thought Eric? If you like, I can submit a
patch fo
deploy should force clean
-
Key: MNG-253
URL: http://jira.codehaus.org/browse/MNG-253
Project: m2
Type: New Feature
Reporter: Brett Porter
interesting use case for lifecycles - like to see what everyone thinks.
I think there could be a
I feel a bit like Eric which is why I've not answered to the vote so far
(I'm still unsure whether it's a good idea or not).
Some points:
- I see the ML merge as a good way to talk about m2 and dispel the urban
legends that have started to accumulate around it.
- I agree that an official statem
maven-archiver should be able to include the snapshot version/build number
--
Key: MNG-251
URL: http://jira.codehaus.org/browse/MNG-251
Project: m2
Type: New Feature
Reporter: Brett Porter
Eric Pugh wrote:
> +0
>
> I think we need to address somewhere what M2 is. I talk to new people
> all the time, and when they hear Maven2, they get nervous.. They
> start wondering why learn M1 if M2 is coming down the pike.. And, for
> early adopters, they need to know that M2 isn't baked the
+0
I think we need to address somewhere what M2 is. I talk to new people
all the time, and when they hear Maven2, they get nervous.. They
start wondering why learn M1 if M2 is coming down the pike.. And, for
early adopters, they need to know that M2 isn't baked the way M1 is,
and that thing
[ http://jira.codehaus.org/browse/MNG-249?page=comments#action_31607 ]
Brett Porter commented on MNG-249:
--
I think this is possible, and a good idea.
the compile phase does not require the resources of the other projects - just
their classes. So when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Brett Porter wrote:
> Some time back, m2-dev@maven.apache.org was established for all Maven
> 2.x related traffic. The purpose of this was to reduce the noise on
> [EMAIL PROTECTED]
>
> As components of m2 will be used in Maven 1.x, and as m2 beco
[ http://jira.codehaus.org/browse/MAVEN-1587?page=history ]
Brett Porter updated MAVEN-1587:
Fix Version: (was: 1.1)
1.1-beta-1
Version: (was: 1.1-beta-1)
1.0.2
> Obsolete links in org.apache.maven.cli.Ap
[ http://jira.codehaus.org/browse/MAVEN-1586?page=history ]
Brett Porter closed MAVEN-1586:
---
Resolution: Fixed
done, thanks
> doc: main.class should be mainclass
> ---
>
> Key: MAVEN-1586
> URL: http:
Author: brett
Date: Tue Apr 5 07:51:53 2005
New Revision: 160180
URL: http://svn.apache.org/viewcvs?view=rev&rev=160180
Log:
PR: MAVEN-1586
fix typo
Modified:
maven/maven-1/core/trunk/xdocs/using/jar.xml
Modified: maven/maven-1/core/trunk/xdocs/using/jar.xml
URL:
http://svn.apache.org/view
Project and module files should use relative paths true
---
Key: MPIDEA-25
URL: http://jira.codehaus.org/browse/MPIDEA-25
Project: maven-idea-plugin
Type: Improvement
Environment: Maven 1.0.2
Reporter: Wim Debl
make m2 shell script find home when it is a symlink
---
Key: MNG-247
URL: http://jira.codehaus.org/browse/MNG-247
Project: m2
Type: Bug
Reporter: Brett Porter
Priority: Trivial
Fix For: 1.0-alpha-2
the m1
Invalid form feed NCR ( ) generated.
-
Key: MPLICENSE-2
URL: http://jira.codehaus.org/browse/MPLICENSE-2
Project: maven-license-plugin
Type: Bug
Environment: Windows XP, SP2, Maven V 1.02, Jdk 1.4.2_05-b04.
Reporter: Achi
[
http://jira.codehaus.org/browse/MPJCOVERAGE-25?page=comments#action_31601 ]
Nascif A. Abousalh-Neto commented on MPJCOVERAGE-25:
Hi Charles,
I tested the new plugin and it worked nicely (after I manually installed the
dependencies
Update to CheckStyle 4.0-beta
-
Key: MPCHECKSTYLE-32
URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-32
Project: maven-checkstyle-plugin
Type: New Feature
Versions: 2.6
Reporter: Archimedes Trajano
To allow support for JDK5
+1
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Tuesday
+1
davidv
Brett Porter wrote:
Some time back, m2-dev@maven.apache.org was established for all Maven
2.x related traffic. The purpose of this was to reduce the noise on
[EMAIL PROTECTED]
As components of m2 will be used in Maven 1.x, and as m2 becomes the
primary platform going forward, I think it w
Author: evenisse
Date: Tue Apr 5 06:03:50 2005
New Revision: 160168
URL: http://svn.apache.org/viewcvs?view=rev&rev=160168
Log:
Fix extension for external site.
Modified:
maven/maven-1/plugins/trunk/jnlp/plugin.jelly
maven/maven-1/plugins/trunk/jnlp/xdocs/changes.xml
Modified: maven/mav
+1
> primary platform going forward, I think it would be beneficial for
> everyone to be working together, and getting the full picture. I also
>From my point of view, it will sound good to send a small email (or an html
document) to describe "how to: getting started with m2" i.e.:
* the new envi
+1.
Will
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 1:20 AM
To: Maven Developers List
Subject: [vote] bring m2-dev back to dev@maven.apache.org
Some time back, m2-dev@maven.apache.org was established for all Maven 2.x
related traffic
+1
On Apr 5, 2005 3:19 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Some time back, m2-dev@maven.apache.org was established for all Maven
> 2.x related traffic. The purpose of this was to reduce the noise on
> [EMAIL PROTECTED]
>
> As components of m2 will be used in Maven 1.x, and as m2 becomes
+1
On Apr 5, 2005 7:19 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Some time back, m2-dev@maven.apache.org was established for all Maven
> 2.x related traffic. The purpose of this was to reduce the noise on
> [EMAIL PROTECTED]
>
> As components of m2 will be used in Maven 1.x, and as m2 becomes
+1
Arnaud
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 5 avril 2005 07:20
> À : Maven Developers List
> Objet : [vote] bring m2-dev back to dev@maven.apache.org
>
> Some time back, m2-dev@maven.apache.org was established for
> all Maven 2.x relat
[ http://jira.codehaus.org/browse/MPCLOVER-34?page=history ]
Vincent Massol closed MPCLOVER-34:
--
Fix Version: 1.9
Resolution: Cannot Reproduce
Assign To: Vincent Massol
Works for me.
> Specifying the license file should only be done onc
On Tue, 5 Apr 2005, Brett Porter wrote:
+1
> [ ] +1, move all m2-dev mails back to [EMAIL PROTECTED]
> [ ] +0
> [ ] -1, Keep them seperate (give reasons)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mai
[ http://jira.codehaus.org/browse/MPCLOVER-31?page=comments#action_31593 ]
Olivier Jacob commented on MPCLOVER-31:
---
Yes I ran into a problem too, but could not find a fix immediatly :\
> Add PDF report support
> --
>
>
+1
Emmanuel
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Tuesday, April 05, 2005 7:19 AM
Subject: [vote] bring m2-dev back to dev@maven.apache.org
> Some time back, m2-dev@maven.apache.org was established for all Maven
> 2.x related t
Vincent Massol wrote:
Hi Siegfried,
The current solution is to have different sections for different
needs. To my knowledge this is the only solution that currently exists.
What you are really asking it seems is a generic way to express that you do
not want a specific report for a specific project
[ http://jira.codehaus.org/browse/MPCLOVER-34?page=comments#action_31592 ]
Wim Deblauwe commented on MPCLOVER-34:
--
ok, go ahead. I probably did something wrong because I re-tested this and now
it seems to work fine. I have only been using Maven for
+1
--
Trygve
On Tue, 2005-04-05 at 15:19 +1000, Brett Porter wrote:
> Some time back, m2-dev@maven.apache.org was established for all Maven
> 2.x related traffic. The purpose of this was to reduce the noise on
> [EMAIL PROTECTED]
>
> As components of m2 will be used in Maven 1.x, and as m2 becom
45 matches
Mail list logo
