> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 08:03
> To: Maven Developers List
> Subject: RE: Moving Plugins
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 08/10/2003 03:39:23
PM:
>
> > Hi Jason,
> >
> > I'm fine with moving the fol
dion2003/10/07 23:07:27
Modified:ant project.xml
Log:
Ready for release
Revision ChangesPath
1.21 +10 -1 maven-plugins/ant/project.xml
Index: project.xml
===
RCS file: /home/cvs/mav
dion2003/10/07 23:07:00
Modified:ant/xdocs navigation.xml
Log:
Add download dir
Revision ChangesPath
1.4 +3 -0 maven-plugins/ant/xdocs/navigation.xml
Index: navigation.xml
===
RCS file
dion2003/10/07 23:04:36
Added: ant/src/announcements 1.5.ann
Log:
Ready for release
Revision ChangesPath
1.1 maven-plugins/ant/src/announcements/1.5.ann
Index: 1.5.ann
===
The
dion2003/10/07 23:02:45
maven-plugins/ant/src/announcements - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 08/10/2003 03:39:23 PM:
> Hi Jason,
>
> I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
> statcvs and actually all the other remaining plugins... I still don't
> understand why we need to keep any plugin at all in maven core. They
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Wed, 8 Oct 2003 1:16 AM
Applied today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-909
Here is an overvie
dion2003/10/07 22:54:22
Modified:ant/src/plugin-resources/templates build.jelly
ant project.xml
ant/xdocs changes.xml
Log:
MAVEN-909
Revision ChangesPath
1.4 +13 -11maven-plugins/ant/src/plugin-resources/templates/build.jel
Hi Jason,
I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
statcvs and actually all the other remaining plugins... I still don't
understand why we need to keep any plugin at all in maven core. They can
be downloaded for bootstrapping (in the same way as all the other jars
are).
dion2003/10/07 22:17:38
Added: .KEYS
Log:
Add gpg KEYS file for signing
Revision ChangesPath
1.1 maven/KEYS
Index: KEYS
===
pub 1024D/C9725F3B 2003-10-07 Dion Gillard
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-909
Here is an overview of the issue:
--
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Wed, 8 Oct 2003 12:25 AM
No freakin' jira way to change the fix version once resolved ;-(
-
View the issue:
http://jira.codehaus.org/secu
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-907
Here is an overview of the issue:
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Wed, 8 Oct 2003 12:24 AM
Fix applied today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-907
Here is an ov
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Wed, 8 Oct 2003 12:22 AM
There's a property for this.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-903
He
dion2003/10/07 22:02:11
Modified:src/plugins-build/plugin plugin.jelly
Log:
Fix for MAVEN-907.
Add plugin:uninstall goal
Revision ChangesPath
1.23 +9 -5 maven/src/plugins-build/plugin/plugin.jelly
Index: plugin.jelly
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 8 Oct 2003 12:22 AM
Body:
There are lots of things that need to be done with this plugin.
It currently takes the source file and produces a single output file.
If you want to specify the output
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-908
Here is an overview of the issue:
--
Last 500 lines of a clean bootstrap build of maven at 20031007-2200
[exec]
/home/tirsen/.maven/repository/commons-digester/jars/commons-digester-1.4.1.jar
[exec]
/home/tirsen/.maven/repository/commons-logging/jars/commons-logging-1.0.1.jar
[exec]
/home/tirsen/.maven
Something I noticed that needs to be done is some of the touchstone tests
(eg sea) need to be converted to the newer plugin test projects. I don't
believe they are called from the core touchstone-tests, but they still refer
to something not available, and its not really great having tests around
th
Just to clarify, where are the non-core plugins being moved to? Are they no
longer going to be part of the maven src tree?
Thanks!
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 07, 2003 1:09 PM
> To: Maven Developers List
> Subject: Moving
Howdy,
Just another push. If you have plugins that are non-core and you want me
to move them over let me know. I think I'm looking at Vincent and
Emmanuel as the next candidates :-)
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new relig
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-907
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Tue, 7 Oct 2003 6:30 PM
Comment:
Thanks for the detailed report Joe.
Since there is a workaround, leaving to fix in 1.1
Anyone got Mac OS X and willing/able to debug this?
Changes:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-906
Here is an overview of the issue:
--
Ant doesn't know anything about ${pom.id} (which is where comes
from), and Maven/Jelly doesn't know anything about replace.properties so
never attempts to evaluate expressions in it.
What you probably want to do is in your jelly script:
But having not used I don't know whether that will pick i
The following comment has been added to this issue:
Author: Arik Kfir
Created: Tue, 7 Oct 2003 5:20 PM
Body:
Oh I'm not sure I'm up for that - I've just began learning Maven as a user. I believe
it will take me a while before I will get sufficiently fluent with Maven's internals.
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-905
Here is an overview of the issue:
--
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Tue, 7 Oct 2003 3:00 PM
Done. Thanks
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-901
Here is an overvi
vmassol 2003/10/07 12:38:00
Modified:src/plugins-build/cactus project.xml
src/plugins-build/cactus/xdocs features.xml changes.xml
Log:
Added documentation for the cactus.bundle property. This fixes MAVEN-901
Revision ChangesPath
1.44 +6 -1 maven/s
Hi all
We have been struggling with this problem an entire day now, so here goes:.
We would like to perform the following replace
with replace.properties containing:
@[EMAIL PROTECTED]
But, @project.id@ does not get replaced with the actual value of the
variable pom.id but with the string "${pom
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-904
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Per Olesen
Created: Tue, 7 Oct 2003 1:18 PM
Body:
Oops, of course I ment "target/generated-xdocs/faq.xml" as output and not .fml :-)
-
View the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-903
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Charlie Dobbie
Created: Tue, 7 Oct 2003 1:12 PM
Body:
I've replicated this as far as I understand it. I added a dependency on a (randomly
chosen) 800KB jar file, invoked "maven test:prepare-filesystem", and it started th
The following comment has been added to this issue:
Author: Charlie Dobbie
Created: Tue, 7 Oct 2003 12:50 PM
Body:
(Apologies, accidental submit before ready.)
** Incomplete download of JAR file not recognised as such **
I suffered a flakey network connection for a few days, an
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-902
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Charlie Dobbie
Created: Tue, 7 Oct 2003 12:37 PM
Body:
Clarification/correction:
The launch configuration exists in a file named XXX.launch, where XXX is the name of
the launch configuration as defined in Eclipse. So th
The following issue has been updated:
Updater: Dominik Dahlem (mailto:[EMAIL PROTECTED])
Date: Tue, 7 Oct 2003 9:36 AM
Comment:
* fixed multiproject issue.
* added the ability to ignore packages.
* improved a little the layout.
* cleaned up/documented the plugin.jelly.
ToDos:
- che
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-901
Here is an overview of the issue:
--
jvanzyl 2003/10/07 04:17:15
Modified:xdocssun-licensing-journey.xml
Log:
o Geir provides a ray of hope!
Revision ChangesPath
1.15 +7 -0 maven/xdocs/sun-licensing-journey.xml
Index: sun-licensing-journey.xml
The following comment has been added to this issue:
Author: fabrizio giustina
Created: Tue, 7 Oct 2003 6:27 AM
Body:
this is already fixed in my patch for MAVEN-797, could someone commit it?
-
View the issue:
ht
42 matches
Mail list logo
