> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 08:34
> To: Maven Developers List
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/05/2004 04:14:03
PM:
>
> > Several things:
> > - when yo
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/05/2004 04:14:03 PM:
> Several things:
> - when you talk about "refactoring out", do you mean refactor out within
> the Ant project or copy-paste the code somewhere else?
Initially into the Maven code base. But later on, sharing with Ant would
be
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Tue, 4 May 2004 2:17 AM
done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-102
Here is an overview o
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 07:55
> To: 'Maven Developers List'
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> > Sent: 04 May
The following issue has been updated:
Updater: Jonas Boner (mailto:[EMAIL PROTECTED])
Date: Tue, 4 May 2004 2:02 AM
Changes:
Attachment changed to project.xml
-
For a full history of the issue, see:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-102
Here is an overview of the issue:
--
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 03:47
> To: [EMAIL PROTECTED]
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
>
>
> > It's easy to solve, don't code th
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 02:29:27 PM:
[snip]
> Read what was written, it is the POJO. The Plugin, AbstractPlugin,
> PluginExecutionRequest and PluginExecutionResponse are the 3k of
> dependencies mentioned in the previous email. The PluginExecutionRequest
> still have
On Mon, 2004-05-03 at 22:55, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 12:17:13 PM:
>
> [snip good stuff]
>
> > No, if you actually looked at code you'll see it's not. There are tests
> > for the 4 varieties and even the fourth variety only requires a 3k dep
vmassol 2004/05/03 13:51:23
Modified:.project.properties
Log:
merge change related to excluding the new plugin-parent dir from 1.0 BRANCH
Revision ChangesPath
1.60 +1 -1 maven/project.properties
Index: project.properties
==
The following comment has been added to this issue:
Author: Miguel Griffa
Created: Mon, 3 May 2004 5:54 PM
Body:
This bug shoudl be changed to invalid
HEAD doesn't compile at the moment, but the 1.0 brach exists only in maven and not in
maven-plugins.
The problem was due to try co
Hello guys !
I tried to generate a maven dist but I had this error :
test-context-switch:
touchstone-partner:test-context-switch:
build:start:
touchstone:test-context-switch-dummy:
[echo] testing differing plugin contexts
BUILD FAILED
File.. file:/D:/Work/Dev/maven-1.0/maven.xml
E
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1257
Here is an overview of the issue:
---
The following issue has been updated:
Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
Date: Mon, 3 May 2004 6:10 PM
Comment:
A patch that adds info about current compilation state in HEAD and 1.0 branch in
building instructions
Changes:
Attachment changed to patc
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 3 May 2004 6:23 PM
Marked as won't fixed as you suggested. Thanks
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
Date: Mon, 3 May 2004 6:42 PM
Comment:
This adds a property to allow more build commands on the project description file, the
documentation is also updated
Changes:
Attachment c
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-101
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Tim Shadel (mailto:[EMAIL PROTECTED])
Date: Mon, 3 May 2004 6:43 PM
Comment:
POM for JBlanket. Not sure if a separate one is needed for maven-jblanket-plugin.
Changes:
Attachment changed to project.xml
brett 2004/05/03 16:51:22
Modified:xdoc plugin.properties
xdoc/src/plugin-resources site.jsl ui.properties
xdoc/xdocs faq.fml
Added: xdoc/src/plugin-resources/css maven-classic.css
Log:
add classic stylesheet
Revision ChangesPath
Hi,
I've added a classic theme to the XDOC plugin that pretty much fits the old
look so that we don't have to impose that change on users that liked the old
one. I did this by merging tigris.css and maven.css into maven-classic.css.
It can be used like so:
maven -Dmaven.xdoc.theme.url=./style/mav
brett 2004/05/03 16:55:40
Modified:xdoc/xdocs changes.xml
Log:
change log
Revision ChangesPath
1.46 +1 -0 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/m
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-101
Here is an overview of the issue:
---
brett 2004/05/03 16:59:42
Modified:.Tag: MAVEN-1_0-BRANCH project.xml
maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.xml
Log:
move jellydoc report to tags subproject as they are all we care about
Revision ChangesPath
No revision
brett 2004/05/03 16:59:02
Modified:src/java/org/apache/maven/cli Tag: MAVEN-1_0-BRANCH App.java
Log:
display more error reporting on this error return
Revision ChangesPath
No revision
No revision
1.37.4.24 +7 -1 maven/src/jav
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1258
Here is an overview of the issue:
---
aheritier2004/05/03 17:18:10
Modified:ant project.xml
ant/src/plugin-resources/templates build.jelly
ant/xdocs changes.xml
Log:
MPANT-14 fix
Revision ChangesPath
1.35 +10 -0 maven-plugins/ant/project.xml
Index: project.xml
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Mon, 3 May 2004 8:19 PM
build template is modified to use the targetPath if defined.
-
View the issue:
http://jira.codehaus.org/secure/
The following comment has been added to this issue:
Author: Mivz
Created: Mon, 3 May 2004 8:29 PM
Body:
I have the same problem, using Win2k. But when I use cygwin/bash, it still does the
same. No error, no time out, it just hangs.
However, the ssh session is started. It's receive
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-26
Here is an overview of the issue:
-
Hello Brett.
The style seems good.
I'm ++1 for the classic one.
However there's a problem. The style isn't applied for files that
aren't in the docs directory.
This problem is due to the fact that in the generated html (from
maven site) there's:
...
@impo
Thanks. I'll have to think about it some more... Maybe instead of using .url
we need a new property to select internal styles that can take relativePath
into consideration.
- Brett
> -Original Message-
> From: Arnaud Heritier [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 4 May 2004 11:00 AM
The following comment has been added to this issue:
Author: Dan Tran
Created: Mon, 3 May 2004 8:36 PM
Body:
Emmanuel,
Did you mean I have finished uploading all the patch?
If so, the answer is no.
I would like very much to add my enhancement to generate EJB and WEB modules info f
Was a failing test case created for this?
It would be nice, since we have plugin tests for the ant plugin to have
added the tests and made sure they succeed.
Who said it: "Fixing a bug without a failing test is asking someone to
break it later"
--
dIon Gillard, Multitask Consulting
[EMAIL PR
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
> It's easy to solve, don't code things as Ant tasks. If you're doing
> something new then there is absolutely no reason to bind your code to
> Ant. Make POJO and wrap it.
Can we do the same for Maven2 then? i.e.
"It's easy to s
On Mon, 2004-05-03 at 21:46, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
>
>
> > It's easy to solve, don't code things as Ant tasks. If you're doing
> > something new then there is absolutely no reason to bind your code to
> > Ant. Make POJO and w
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 12:17:13 PM:
[snip good stuff]
> No, if you actually looked at code you'll see it's not. There are tests
> for the 4 varieties and even the fourth variety only requires a 3k dep
> which does not really have anything to do with Maven2. They are
jvanzyl 2004/05/03 11:47:01
Modified:xdocs/reference/plugins index.xml
Log:
o applying blurb by the mevenide folks.
Revision ChangesPath
1.9 +10 -2 maven/xdocs/reference/plugins/index.xml
Index: index.xml
==
aheritier2004/05/03 10:17:28
Added: plugin-parent .cvsignore
Log:
ignore target directory
Revision ChangesPath
1.1 maven-plugins/plugin-parent/.cvsignore
Index: .cvsignore
===
targ
jvanzyl 2004/05/03 08:47:08
Added: surefire/xdocs README.txt
Log:
o note about the docs
Revision ChangesPath
1.1 maven-plugins-sandbox/surefire/xdocs/README.txt
Index: README.txt
===
jvanzyl 2004/05/03 08:46:19
maven-plugins-sandbox/surefire/xdocs - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jvanzyl 2004/05/03 06:57:45
Log:
o The first backport of a maven2 plugin into maven1. Surefire is a test
testing tool based on SuiteRunner.
Status:
Vendor Tag: ASF
Release Tags: INIT
N maven-plugins-sandbox/surefire/.cvsignore
N maven-plugins-sandbox/surefire/plugi
Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Mon, 3 May 2004 6:48 AM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-100
Here is an overview of t
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-100
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Mon, 3 May 2004 3:28 AM
Body:
I'm totally agree with you for OSS scm.
CVS : netbeans or eclipse library
svn : ??? I'll search it
For commercial SCM, it isn't possible because it suppose we use a
The following comment has been added to this issue:
Author: Ben Walding
Created: Mon, 3 May 2004 3:12 AM
Body:
Please read: http://maven.apache.org/repository-upload.html and provide the required
info.
Primarily, my concern (apart from the missing bits and pieces) is what is the
46 matches
Mail list logo
