On Tue, 2003-11-25 at 01:03, Brett Porter wrote:
> Ok. Sounds good.
>
> You've made these changes on HEAD, right?
Yes.
> I'll make sure to include them in
> the new MAVEN-1_0-BRANCH. And then any future changes chan either be made on
> that branch, or on HEAD - in which case they don't ever get
Ok. Sounds good.
You've made these changes on HEAD, right? I'll make sure to include them in
the new MAVEN-1_0-BRANCH. And then any future changes chan either be made on
that branch, or on HEAD - in which case they don't ever get put onto the 1.0
branch, but I can live with that, as long as it is
On Tue, 2003-11-25 at 00:48, Brett Porter wrote:
> I just today saw some people asking whether Maven can be used to generate
> the gump descriptor for another Apache project. Is that what you are
> referring to, or Maven being built by gump itself?
Maven being built by gump itself. I can't imagine
On Mon, 2003-11-24 at 18:57, Brett Porter wrote:
> http://wiki.codehaus.org/maven/MavenCvs
>
> I will move MAVEN_RC2_UNSTABLE to MAVEN-1_0-BRANCH as soon as Jason is
> finished modifying the bootstrap on HEAD. The branch will include all
> changes on HEAD, except for the POMv4 stuff, and has the p
I just today saw some people asking whether Maven can be used to generate
the gump descriptor for another Apache project. Is that what you are
referring to, or Maven being built by gump itself?
I have no experience with it.
- Brett
> -Original Message-
> From: Jason van Zyl [mailto:[EMAI
Howdy,
Has anyone updated the Gump stuff lately? Can Gump even use the stuff we
generate for Maven itself? If not I was just going to nuke it as I
personally have no interest and don't see many others taking any either.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In shor
jvanzyl 2003/11/24 21:40:39
Removed: .initial-proposal.txt maven-resolution.txt
Log:
o move to xdocs/project directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROT
jvanzyl 2003/11/24 21:39:18
Added: xdocs/project initial-proposal.txt maven-resolution.txt
Log:
o these need to be converted to xdoc format so they can be displayed
for those that are curious.
Revision ChangesPath
1.1 maven/xdocs/project/initial-pro
jvanzyl 2003/11/24 21:38:16
maven/xdocs/project - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jvanzyl 2003/11/24 21:36:50
Modified:.build-bootstrap.xml project.properties
Removed: .build-bootstrap.properties
Log:
o rolling bootstrap properties into the normal project.properties
file as they are required in the build-bootstrap.xml and maven.xml
du
On Mon, 2003-11-24 at 20:20, Brett Porter wrote:
> Are they doing 1.1 only plugins? If the decision to break compatibility with
> 1.0 is made, then they do the same thing - dev their new versions on
> maven-plugins/plugin-name HEAD, and branch the old one only for 1.0
> compatible bugfixes.
>
> I
On Mon, 2003-11-24 at 20:20, [EMAIL PROTECTED] wrote:
> I still don't see how people are going to do 1.1 plugins without applying
> the same branches to maven-plugins.
>
> Shouldn't both modules have the same set of branches created?
No, we are not tying the plugins to the core, that is the whol
> So each plugin directory inside maven-plugins will have it's
> own branches?
> That's going to be very hard to manage if I'm developing on multiple
> plugins isn't it?
>
I think it's a non-issue. It should be rare that a plugin does some
development that makes it 1.1 only AND decides to main
Brett Porter <[EMAIL PROTECTED]> wrote on 25/11/2003 12:20:03 PM:
> Are they doing 1.1 only plugins? If the decision to break compatibility
with
> 1.0 is made, then they do the same thing - dev their new versions on
> maven-plugins/plugin-name HEAD, and branch the old one only for 1.0
> compatibl
Adam R. B. Jack wrote:
Noel wrote:
+1 if you mean to incubate a particular project, since it seems that you
have a set of codebases and a community to start.
However, unless it is willing to be more inclusive of other related
projects, I don't think that it should be permitted to refer to it
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 24 Nov 2003 7:35 PM
Body:
What is 'ok' for each of the reports?
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.
A subject change such as this is probably a best practice for such a case.
There are a few references around on netiquette which should help, but I
don't have any to hand.
As far as plugin development being separate, each can be released, versioned
and downloaded independantly of maven itself, so
I'm not sure the best practices of posting to mailing lists, as I'm new to
them.. it seems you pretty much have to top post all the time, right?
That said, I'm interested in your last point. How is maven plugin
development separated from the maven core, architecturally?
Thanks Alot,
Aaron
-
Are they doing 1.1 only plugins? If the decision to break compatibility with
1.0 is made, then they do the same thing - dev their new versions on
maven-plugins/plugin-name HEAD, and branch the old one only for 1.0
compatible bugfixes.
I think that would be a crazy decision to make on behalf of the
I still don't see how people are going to do 1.1 plugins without applying
the same branches to maven-plugins.
Shouldn't both modules have the same set of branches created?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Porter <[EMAIL PROTECTED]> w
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 24 Nov 2003 7:09 PM
Body:
Why is there a catch (Exception) after System.getProperty() in the patch?
That seems very undesirable.
-
Noel wrote:
> +1 if you mean to incubate a particular project, since it seems that you
> have a set of codebases and a community to start.
>
> However, unless it is willing to be more inclusive of other related
> projects, I don't think that it should be permitted to refer to itself as
> the Apach
I get a 404 on the site.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Chen, Andrew ." <[EMAIL PROTECTED]> wrote on 25/11/2003 02:53:15 AM:
> Hi,
> Some one may have done it, but since I couldn't find it, so I did it
> again...
>
> I'm using the xdocs
On Mon, 2003-11-24 at 18:57, Brett Porter wrote:
> http://wiki.codehaus.org/maven/MavenCvs
>
> I will move MAVEN_RC2_UNSTABLE to MAVEN-1_0-BRANCH as soon as Jason is
> finished modifying the bootstrap on HEAD. The branch will include all
> changes on HEAD, except for the POMv4 stuff, and has the p
http://wiki.codehaus.org/maven/MavenCvs
I will move MAVEN_RC2_UNSTABLE to MAVEN-1_0-BRANCH as soon as Jason is
finished modifying the bootstrap on HEAD. The branch will include all
changes on HEAD, except for the POMv4 stuff, and has the plugin context bug
fixed, but some parts of touchstone havin
Can someone please reply to this with a quick status on where we are at in
the process?
Thanks,
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Mon, 24 Nov 2003 3:57 PM
Body:
The collective petes have been added to the maven group by Cliff Wooley.
-
View the issue:
http:/
On Mon, 2003-11-24 at 16:39, Brett Porter wrote:
> Thanks for doing the move. All the ideas about breaking up maven.xml are
> good, especially the release stuff. We should be able to release maven with
> a standard plugin - some combination of dist, release and scm.
>
> > - plugin testing should b
> Since there are a lot more dependent jars and plugins that
> may be interesting for debugging I just ask myself how you
> all have set up your developing environment? Are you using
> the libraries in the local repository at all?
I don't go to such great lengths when I actually need to step in
That was my work... It was a little quicker and nastier than it should have
been :)
It's just an optional part of the install process for a user to avoid
downloading the lib/ directory again from the repository.
A nicer solution is probably to distribute them in
$MAVEN_HOME/repository/.../jars/..
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Mon, 24 Nov 2003 3:43 PM
Body:
Request to infrastructure has been made to add Peter Royal and Peter Donald to the
maven group so they can commit.
Thanks for doing the move. All the ideas about breaking up maven.xml are
good, especially the release stuff. We should be able to release maven with
a standard plugin - some combination of dist, release and scm.
> - plugin testing should be separated, the concern for the
> core is that the plugin
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Mon, 24 Nov 2003 3:40 PM
The maven-wagon CVS module has been setup.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Mon, 24 Nov 2003 3:35 PM
Body:
Request to infrastructure has been made for the general mailing list.
-
View the issue:
http://ji
Vincent,
Is there a way to group the plugin projects under Maven itself so that
the dashboard isn't cluttered up with all of Maven plugins?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to j
jvanzyl 2003/11/24 13:25:50
Removed: src/plugins-build Tag: MAVEN_RC1_REFACTOR .cvsignore
maven.xml project.properties project.xml
src/plugins-build/clean Tag: MAVEN_RC1_REFACTOR .cvsignore
plugin.jelly plugin.properties proj
jvanzyl 2003/11/24 13:25:14
Modified:.build-bootstrap.xml maven.xml
Log:
o bootstrap is happy
i will now look at the plugin testing mechanism and have each plugin
responsible for executing it's own tests as part of the build instead of
it being triggered by the boo
On Mon, 2003-11-24 at 16:21, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 24 November 2003 22:18
> > To: Maven Developers List
> > Subject: Some things to do in the core
> >
> > Howdy,
> >
> > After poking around a bit in the cor
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 24 November 2003 22:18
> To: Maven Developers List
> Subject: Some things to do in the core
>
> Howdy,
>
> After poking around a bit in the core maven.xml file there are
certainly
> a few things that need to be
Howdy,
After poking around a bit in the core maven.xml file there are certainly
a few things that need to be done:
- plugin site generation must be separated. This can be rolled into
maven-plugins I'm sure for the time being but it should be made possible
that a single site for a plugin can be pu
Hi,
The first pass at the move is done. All the plugins have been moved and
the bootstrap works with the plugins in their new location.
To be safe I would do a fresh checkout of maven and maven-plugins.
I will spend a few more hours cleaning some stuff up and chopping the
core maven.xml file up
jvanzyl 2003/11/24 13:06:23
Modified:.build-bootstrap.xml
Log:
o all appears to be happy again.
Revision ChangesPath
1.210 +1 -0 maven/build-bootstrap.xml
Index: build-bootstrap.xml
==
vmassol 2003/11/24 12:46:56
Modified:plugin plugin.jelly
plugin/xdocs changes.xml
Log:
Added assert:assertEquals tag to verify if two values are equal while testing a
plugin. We probably need to use the jelly junit taglib soon or create a new one...
Revision C
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Mon, 24 Nov 2003 2:42 PM
Body:
I just checked the run.bat and shutdown.bat for 3.0.8
if "%NOPAUSE%" == "" pause
exists on both of them
I believe they copy over all of the maven jar dependencies to your local
repository (there are over 10). I presume this is so you don't have to wait
several minutes to attain a goal the first time you use Maven because those
jars are used by so many plugins.
I don't think they are especially us
What are these for exactly?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
jvanzyl 2003/11/24 12:32:37
Modified:src/bootstrap/org/apache/maven BootstrapTask.java
Log:
o don't download the file if it exists. something is wrong with timestamps again
as it's trying to download the file even though i have it locally ...
Revision ChangesPath
1.20
vmassol 2003/11/24 12:31:38
Modified:dashboard/xdocs changes.xml properties.xml
dashboard/src/plugin-resources/templates dashboard.jsl
dashboard/src/plugin-test maven.xml
dashboard plugin.properties
Log:
Added new maven.dashboard.report.sh
jvanzyl 2003/11/24 12:21:30
Removed: src/plugins-build/clean .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/clean/src/plugin-test .cvsignore maven.xml
project.xml
src
jvanzyl 2003/11/24 12:18:00
Modified:.build-bootstrap.xml maven.xml project.properties
Removed: .build-bootstrap-core.xml
Log:
o get rid of the core bootstrap
o cleanup the core maven.xml file by offloading stuff into other jelly files
as this is necessary
jvanzyl 2003/11/24 12:16:24
Modified:src/bootstrap/org/apache/maven BootstrapTask.java
Log:
o more formatting
Revision ChangesPath
1.19 +33 -59maven/src/bootstrap/org/apache/maven/BootstrapTask.java
Index: BootstrapTask.java
===
jvanzyl 2003/11/24 12:07:30
Modified:src/bootstrap/org/apache/maven BootstrapTask.java
Log:
o formatting
Revision ChangesPath
1.18 +142 -135 maven/src/bootstrap/org/apache/maven/BootstrapTask.java
Index: BootstrapTask.java
jvanzyl 2003/11/24 11:57:34
Added: .release.xml
Log:
o release/installer related jelly.
Revision ChangesPath
1.1 maven/release.xml
Index: release.xml
===
jvanzyl 2003/11/24 11:57:18
Added: .plugins-site.xml
Log:
o plugin site specific jelly. separating it to be integrated when i'm done
decomposing
our massive maven.xml file.
Revision ChangesPath
1.1 maven/plugins-site.xml
Index: plugins
epugh 2003/11/24 11:38:46
Modified:faq plugin.jelly project.xml
faq/xdocs changes.xml
Log:
Prevent FAQ plugin from crashing if there is no /xdocs directory.
Revision ChangesPath
1.12 +94 -93maven-plugins/faq/plugin.jelly
Index: plugin.j
On Mon, 2003-11-24 at 12:15, Jason van Zyl wrote:
> Howdy,
>
> Will someone be around to sanity check the bootstrap after the plugins
> move in an hour or two?
I am making progress but I discovered that the bootstrap is coupled to
the actual source location of the plugins src/plugins-build so I'm
The following issue has been updated:
Updater: Sean Timm (mailto:[EMAIL PROTECTED])
Date: Mon, 24 Nov 2003 11:55 AM
Comment:
This diff fixes the problem by setting the NOPAUSE environment variable to true. I've
also added a call to setlocal (if NT-based) to ensure that spurious va
Howdy,
Will someone be around to sanity check the bootstrap after the plugins
move in an hour or two?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in
Hello developers,
are there any recommendations how to debug Maven best? Currently I checked out maven,
maven-plugins/genapp and jakarta-commons/jelly because I try to look into some strange
behaviour of the genapp plugin. For maven and jelly I generated with an already
installed Maven my Eclip
Hi,
Some one may have done it, but since I couldn't find it, so I did it
again...
I'm using the xdocs and site generation functionality of Maven extensively
now for project website. However, I have trouble validating, and editing
xdoc files. The site build stops if the xdoc is not valid, and the
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEAR-10
Here is an overview of the issue:
---
The following comment has been added to this issue:
Author: Vincent Massol
Created: Mon, 24 Nov 2003 2:39 AM
Body:
Kevin and Archimedes,
I'd like to apply your patch. Is your patch working with *all* version of JBoss or is
it specific to a specific version only. Namely, will it w
The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Mon, 24 Nov 2003 2:35 AM
Changes:
Fix Version changed to 1.4
-
For a full history of the issue, see:
63 matches
Mail list logo
