Quick note before I leave for the day...
Dion mentioned last night on IRC that dashboard's plugin tests fail under
the reactor in some circumstances.
This isn't a reactor bug as such and so is not too serious. The problem is
that the reactor passes on the current context to the subproject, and th
Performing an update of maven-components ...
Updates occured, build required ...
P
maven-project/src/main/java/org/apache/maven/project/DefaultModelInheritanceAssembler.java
---
Building mboot ...
---
I spent some time trying to fix a problem in the clover plugin and I
couldn't find a working solution...
The clover plugin actually doesn't work if you set the
"maven.clover.jar" property with a registered clover jar with a version
different from the one loaded by the plugin (1.2.3). The problem i
evenisse2004/05/13 14:50:55
Added: maven-core/src/test/resources maven.xml
Log:
Add missing file
Revision ChangesPath
1.1 maven-components/maven-core/src/test/resources/maven.xml
Index: maven.xml
==
evenisse2004/05/13 14:30:51
Modified:maven-project/src/main/java/org/apache/maven/project
DefaultModelInheritanceAssembler.java
Log:
Remove double dependencies loading that cause OutOfMemory.
Revision ChangesPath
1.6 +3 -7
maven-compone
Performing an update of maven-components ...
Updates occured, build required ...
P
maven-project/src/main/java/org/apache/maven/project/DefaultModelInheritanceAssembler.java
P maven-project/src/main/java/org/apache/maven/project/MavenProject.java
---
evenisse2004/05/13 12:50:32
Modified:jbuilder plugin.jelly
Log:
Fix my latest commit.
Revision ChangesPath
1.23 +0 -2 maven-plugins/jbuilder/plugin.jelly
Index: plugin.jelly
===
RCS file: /
trygvis 2004/05/13 12:26:49
Modified:maven-project/src/main/java/org/apache/maven/project
DefaultModelInheritanceAssembler.java
Log:
o Putting back dependency inheritance.
Revision ChangesPath
1.5 +8 -2
maven-components/maven-project/sr
trygvis 2004/05/13 12:25:59
Modified:maven-project/src/main/java/org/apache/maven/project
MavenProject.java
Log:
o Javadoc updates.
Revision ChangesPath
1.7 +5 -5
maven-components/maven-project/src/main/java/org/apache/maven/project/Mav
> -Original Message-
> From: Kristopher Brown
[mailto:[EMAIL PROTECTED]
> Sent: 13 May 2004 18:28
> To: Maven Developers List
> Subject: RE: Inter-plugin dependancy best practices
>
> Hi,
>
> Thanks for your swift response, however, I think the word "dependancy"
> possibly confused my p
On Thu, 2004-05-13 at 12:02, Miguel Griffa wrote:
> Hi all
> Is there any place I can get some info on building maven 2
No, and there won't be until the first alpha is released. It's not for
public consumption.
> I'd like to know at least whith CVS projects to fetch... (if different
> from curre
Hi,
Thanks for your swift response, however, I think the word "dependancy"
possibly confused my point. I'm not talking about a plugin being
dependant on another, more about how plugins affect shared variables.
It's hard for me to explain it, that's why I used the example of
maven.compile.src.set.
I will do webserver as well. I don't think there are any issues there but it is
worth a closer look on my part. Same timeline...
-Peter
Brett Porter wrote:
Ok, sounds good to me. It's really good to see you owning this process
because it's how its meant to be!
Will you do webserver at the same
Hi all
Is there any place I can get some info on building maven 2
I'd like to know at least whith CVS projects to fetch... (if different
from current)
Thanks in advance
--
Miguel Griffa
Software Architect
Technisys.NET "The First Digital e-nabler"
Transactional Solutions
Miami +1 305 357 8109
M
Hi Kristopher,
> -Original Message-
> From: Kristopher Brown
[mailto:[EMAIL PROTECTED]
> Sent: 13 May 2004 17:18
> To: [EMAIL PROTECTED]
> Subject: Inter-plugin dependancy best practices
>
> Hi,
>
> How should plugin developers indicate that a plugin is inter-dependant
> on anther plugin
Hi,
How should plugin developers indicate that a plugin is inter-dependant
on anther plugin? Some have suggested a registering mechanism like that
used by the site report. Another way is by modifying a shared variable.
For example, maven.compile.src.set can be used by plugins to make other
plug
ok I'll try to test it.
Arnaud
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi 13 mai 2004 14:08
> À : Maven Developers List
> Objet : RE: [jelly] move to dom4j-1.5-beta-2 ?
>
>
> "Heritier Arnaud" <[EMAIL PROTECTED]> wrote on 13/05/2004
> 05
The repo plugin already has this defined for licenses.
--
dIon Gillard, Multitask Consulting
Maczka Michal <[EMAIL PROTECTED]> wrote on 13/05/2004 10:20:32 PM:
>
>
> > Ok, so we'll just have a standard extension of "license" and we'll use
> > the form:
> >
> > -.license
> >
> > If this is c
I wanted to take a second and let everyone know how much I appreciate
all the kind words, not to mention the explicit vote of confidence. :-)
I look forward to working with you all. I think maven represents a
breakthrough in codebase management, and I'm excited to be a part of it.
-john
On Wed,
brett 2004/05/13 06:00:06
Modified:jar project.xml
jar/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.5
Revision ChangesPath
1.25 +6 -1 maven-plugins/jar/project.xml
Index: project.xml
===
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 13, 2004 2:37 PM
> To: Maven Developers List
> Subject: RE: standard name for license file
>
>
> On Thu, 2004-05-13 at 08:20, Maczka Michal wrote:
> >
> > > Ok, so we'll just have a standard ext
On Thu, 2004-05-13 at 08:20, Maczka Michal wrote:
>
> > Ok, so we'll just have a standard extension of "license" and we'll use
> > the form:
> >
> > -.license
> >
> > If this is cool then I will update the repo plugin to produce this
> > format for the upload bundles.
> >
>
>
> Last question
> Ok, so we'll just have a standard extension of "license" and we'll use
> the form:
>
> -.license
>
> If this is cool then I will update the repo plugin to produce this
> format for the upload bundles.
>
Last question: where do you want to keep a file containing licenses? in
/licenses fol
On Thu, 2004-05-13 at 03:23, Rafal Krzewski wrote:
> Another "fascinating but evil" scripting thingy? ;-)
>
> Where do I find more info?
>From John or myself on IRC for now.
> http://marmalade.codehaus.org/
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10528
>
> are not very informat
dion2004/05/13 05:25:07
Added: .maven.xml
Log:
Add test-all local goal
Revision ChangesPath
1.6 +5 -10 maven-plugins/maven.xml
-
To unsubscribe, e-mail: [EMAIL PROTECT
On Thu, 2004-05-13 at 03:05, Rafal Krzewski wrote:
> Vincent Massol wrote:
>
> > Isn't it possible that a dual-license project has the dual license
> > defined in a single license file? Does it have to be in 2 files?
>
> I'd go with a single file. It's just a text file so people can put in
> wha
On Thu, 2004-05-13 at 05:22, Heritier Arnaud wrote:
> Why must we replace Jelly ??
>
> Isn't it better to correct/enhance it
The short answer is no, it's not. It's not being maintained by its
creator and someone would have to burn it to the ground and rebuild it
to make it decent.
>
> Arna
dion2004/05/13 05:08:12
Modified:aspectj/src/plugin-test project.properties
Log:
Fix plugin tests failing under jdk1.3
Revision ChangesPath
1.2 +1 -0 maven-plugins/aspectj/src/plugin-test/project.properties
Index: project.properties
=
"Heritier Arnaud" <[EMAIL PROTECTED]> wrote on 13/05/2004 05:15:19 PM:
> +1
>
> We have effectively several problems with entities in maven plugins
> due to problems in Jelly/Dom4J.
>
> It can be a good think if we can do this before maven 1.0 RC3.
>
> Arnaud
I don't think that's possible.
L
On Thu, 2004-05-13 at 00:50, Arnaud Heritier wrote:
>
> > I think you're reaching an interesting point here.
> >
> > The developer information should be retrieved from an external
> > repository, this being an LDAP or a simple global XML file shared by all
> > projects.
> >
> > Otherwise yo
brett 2004/05/13 04:38:21
Modified:multiproject project.xml
multiproject/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.3
Revision ChangesPath
1.26 +2 -2 maven-plugins/multiproject/project.xml
Index: project.xml
=
brett 2004/05/13 04:33:44
Modified:plugin project.xml
Log:
remove redundant HEAD version
Revision ChangesPath
1.34 +0 -5 maven-plugins/plugin/project.xml
Index: project.xml
===
RCS file
brett 2004/05/13 04:12:01
Modified:plugin project.xml
plugin/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.4
Revision ChangesPath
1.33 +7 -4 maven-plugins/plugin/project.xml
Index: project.xml
=
brett 2004/05/13 04:07:57
Modified:multichanges project.xml
Added: jira/xdocs changes.xml
nsis/xdocs changes.xml
Log:
missing documentation elements
Revision ChangesPath
1.1 maven-plugins/jira/xdocs/changes.xml
Index: changes
brett 2004/05/13 03:15:56
Modified:maven-jelly-tags/src/java/main/org/apache/maven/jelly/tags/maven
Tag: MAVEN-1_0-BRANCH ReactorTag.java
src/conf Tag: MAVEN-1_0-BRANCH defaults.properties
src/java/org/apache/maven/jelly Tag: MAVEN-
Why must we replace Jelly ??
Isn't it better to correct/enhance it
Arnaud
> -Message d'origine-
> De : Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi 13 mai 2004 09:23
> À : Maven Developers List
> Objet : Re: cvs commit:
> maven-components/maven-core/src/test/java/org/a
dion2004/05/13 01:48:57
Modified:dashboard/src/plugin-test project.properties
Log:
Stop plugin tests from failing under jdk 1.3
Revision ChangesPath
1.12 +1 -0 maven-plugins/dashboard/src/plugin-test/project.properties
Index: project.properties
==
+1
We have effectively several problems with entities in maven plugins due to problems in
Jelly/Dom4J.
It can be a good think if we can do this before maven 1.0 RC3.
Arnaud
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 12 mai 2004 23:38
[EMAIL PROTECTED] wrote:
o adding John Casey's patch which adds support for maven.xml processing in
maven2 using marmlade which is a Jelly replacement.
+
+
+ marmalade
+ marmalade-core
+ 0.1
+
+
+ marmalade
+ marmalade-el-ognl
+
Vincent Massol wrote:
Isn't it possible that a dual-license project has the dual license
defined in a single license file? Does it have to be in 2 files?
I'd go with a single file. It's just a text file so people can put in
what they need. For example an explaination what parts of the software
a
40 matches
Mail list logo
