dion2004/05/04 23:16:27
Modified:eclipse/xdocs changes.xml
eclipse/src/plugin-test maven.xml
Log:
Use assert taglib for plugin tests
Revision ChangesPath
1.16 +1 -0 maven-plugins/eclipse/xdocs/changes.xml
Index: changes.xml
I was thinking about something like this.
I vas trying to build a plugin that should as a site postGoal
It works this way:
For ecah *-report.xml file in target/generated-doc it search a coresponding
stylesheet (jsl in plugin-resources) and applies it.
It then concat the result of all those
brett 2004/05/05 00:18:51
Modified:xdocsTag: MAVEN-1_0-BRANCH development-process.xml
navigation.xml
Added: maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH index.xml
Removed: xdocs/reference/plugins Tag: MAVEN-1_0-BRANCH index.xml
Log:
doco
brett 2004/05/05 00:27:57
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
project.xml
maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.xml
Log:
reporting
Revision ChangesPath
No revision
No
brett 2004/05/05 00:29:28
Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
Log:
logging
Revision ChangesPath
No revision
No revision
1.70.4.43 +2 -1
brett 2004/05/05 00:34:38
Modified:.project.xml project.properties
xdocsnavigation.xml faq.fml
Removed: .README.txt
xdocsindex.html
Log:
site updates
Revision ChangesPath
1.20 +1 -1
brett 2004/05/05 00:36:03
Added: xdocsindex.xml
Log:
site updates
Revision ChangesPath
1.1 maven-plugins/xdocs/index.xml
Index: index.xml
===
?xml version=1.0?
!--
/*
brett 2004/05/05 00:38:31
Modified:xdoc plugin.jelly plugin.properties
xdoc/src/plugin-resources site.jsl
xdoc/xdocs changes.xml faq.fml
Log:
o exclude fml files in copy
o easier use of classic that always works
Revision ChangesPath
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266
Here is an overview of the issue:
The following comment has been added to this issue:
Author: nicolas de loof
Created: Wed, 5 May 2004 3:54 AM
Body:
Just notice class mocking support is an optional extension to easymock, also in 1.1
version
http://easymock.org/Downloads.html
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 5 May 2004 4:04 AM
Done.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-103
Here is an
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 5 May 2004 4:05 AM
Done. The next time, could you use the correct project under Jira (MAVENUPLOAD). Thanks
-
View the issue:
The following comment has been added to this issue:
Author: nicolas de loof
Created: Wed, 5 May 2004 4:13 AM
Body:
Sorry, didn't see they're is a dedicated project (they're so much maven-xxx !)
-
View this
The following comment has been added to this issue:
Author: Christian Stein
Created: Wed, 5 May 2004 4:17 AM
Body:
Is there any workaround for this?
-
View this comment:
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 5 May 2004 4:35 AM
Body:
Yup I have read that document which details what you have to do if you are using cvsnt
client to connect to a cvs server. This is a different problem though, this
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 05, 2004 2:14 AM
To: Maven Developers List
Subject: RE: xdoc with custom templates and/or navigation
On Tue, 2004-05-04 at 20:07, Brett Porter wrote:
The wiki has instructions on submitting
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 5 May 2004 5:26 AM
Body:
Just checked http://javacvs.netbeans.org/issues/show_bug.cgi?id=39662 it says its just
an informational message, but it does not explain why I do not get any
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Wed, 5 May 2004 6:45 AM
Changes:
Fix Version changed to 1.0-rc3
-
For a full history of the issue, see:
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216
Here is an overview of the issue:
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Wed, 5 May 2004 6:50 AM
fixed for non standard types. No need to add :tld etc to the end of the id (current
legacy ID parser doesn't handle that consistently anyway).
brett 2004/05/05 04:00:59
Modified:artifact project.xml
changelog project.xml
linkcheck project.xml
multiproject project.xml
pom project.xml
release project.xml
xdoc project.xml
Log:
brett 2004/05/05 04:01:05
Modified:maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH changes.xml
xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
change log
Revision ChangesPath
No revision
No revision
1.1.2.2 +2 -0
brett 2004/05/05 04:02:44
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
DependencyClasspathBuilder.java
Log:
PR: MAVEN-1265
dependency path setting for non-classpath dependencies
Revision ChangesPath
No revision
brett 2004/05/05 04:02:54
Modified:xdocsindex.xml
Log:
add mevenide link
Revision ChangesPath
1.2 +10 -2 maven-plugins/xdocs/index.xml
Index: index.xml
===
RCS file:
brett 2004/05/05 04:04:10
Modified:src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml
Log:
test for getDependencyPath
Revision ChangesPath
No revision
No revision
1.43.4.14 +15 -0
brett 2004/05/05 04:04:36
Added: maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH navigation.xml
maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.properties
Log:
update jelly tag site
Revision ChangesPath
No revision
No
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1267
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1268
Here is an overview of the issue:
The following issue has been updated:
Updater: nicolas de loof (mailto:[EMAIL PROTECTED])
Date: Wed, 5 May 2004 7:31 AM
Changes:
Attachment changed to ibiblio.txt
-
For a full history of the issue,
Hi all,
Regardless of this patche fixing the bug or not, I think we could go a
step further on the Eclipse project/nature/builder support. Let me
explain better.
For the case of 'less intrusive' Eclipse plugins (like Checkstyle), I
think the patch is fine. But that is not enough for plugins
brett 2004/05/05 05:04:28
Modified:.project.xml project.properties
plugin-parent project.xml
Log:
doco updates
Revision ChangesPath
1.21 +10 -0 maven-plugins/project.xml
Index: project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJXR-12
Here is an overview of the issue:
On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
Jason!
It's not just a question of the theme.
Some organization have already their own standards which define precisly how
their intranet pages are looking.
Often thy have alredy hundreds of pages with spcific layout
which is completly
Michal, you hit it right on. If we do not give it a look and feel to match
our corporate standards our Technical Steering Commitee will see the
product as not being appropriate to use.
We all know this is technically wrong, but perception is reality when the
business people in the company are
brett 2004/05/05 06:05:55
Modified:.build-bootstrap.xml maven.xml project.properties
project.xml
maven-jelly-tags/src/java/main/org/apache/maven/jelly/tags/maven
MavenTag.java MavenTagLibrary.java
Sorry but our firewall setup here does not allow us to use CVS on the
internet (port blocked).
I did it to get a custom menu layout. Are there options to do this that I
missed?
Regards,
Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel:
brett 2004/05/05 06:19:14
Modified:maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.xml
Log:
fix images
Revision ChangesPath
No revision
No revision
1.1.2.5 +2 -2 maven/maven-jelly-tags/project.xml
Index: project.xml
Mauro Talevi wrote:
Mark,
separating maven repositories by organizations sort of defeates the
point of putting them in a common unique place such as ibiblio.
That is, once could two different url, say
dist.apache.org
dist.codehaus.org
and those can be set on the client side as the maven repos
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 5 May 2004 9:35 AM
Body:
I am not sure if it is because of the upgrade to 3.6 (I don't think it is since
according to their issue log it fixes the problem that I am experiencing with
I'll go for the test case now,
I'm sorry, but being newbie is a bit unfamiliar for me testing maven plugin
I'll submit a patch for the test case if I manage to get one :)
[EMAIL PROTECTED] wrote:
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 4 May
On Wed, 2004-05-05 at 08:53, Mark R. Diggory wrote:
I think its a great idea to have other organizations who wish to rsync
use the script. But this should be a decision within those groups, if
you are a member of that groups and you object, you should take it up
with that group. The rsync
I am trying to alter what is in the Navigation Menu. I would like this to
be controlled programmatically (Jelly script) to still have consistency
with project sites generated.
Regards,
Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel:
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 05, 2004 4:30 PM
To: Maven Developers List
Subject: RE: xdoc with custom templates and/or navigation
On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote:
Is there a recommended way to
Mark R. Diggory wrote:
No, you missunderstood me, we're not breaking up the repository, its
still all one, just organizing it better for management purposes, the
directory structure is not different virtual machines.
maven.ibibilio.org/apache/project
maven.ibibilio.org/codehaus/project
same
On Wed, 2004-05-05 at 10:54, [EMAIL PROTECTED] wrote:
I am trying to alter what is in the Navigation Menu. I would like this to
be controlled programmatically (Jelly script) to still have consistency
with project sites generated.
I've added programmatic control to the new xdoc plugin so this
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1269
Here is an overview of the issue:
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 5 May 2004 12:03 PM
Body:
Perhaps adding a schema check for the project.xml file will at least highlight that
there is a problem with the file.
jvanzyl 2004/05/05 09:52:40
Log:
o this won't be a core plugin but it is the first plugin that will be
reactor aware and I need to be able to generate IDEA 4 project files
to work :-)
The modules for IDEA 4 map nicely to a nest hierarchy of maven projects
so I'm working
The following issue has been updated:
Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
Date: Wed, 5 May 2004 1:19 PM
Comment:
Adds tests for the functionallity of the previous patch
Changes:
Attachment changed to test-patch.txt
I submited a patch that adds tests for the builders and natures,
I made the tests separated because I think that the test shuold include
some validation over the expected contents of the generated file
I don't know how to do this with jelly yet...
Miguel Griffa wrote:
I'll go for the test case
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270
Here is an overview of the issue:
Hi all,
Does anyone know how can I assert() that a file contains a given string
in jelly?
What I want to do is this:
I have a test case and I want to ensure that the file contains a given
string somewhere
Thanks in advance
--
Miguel Griffa
Software Architect
Technisys.NET The First Digital
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Wed, 5 May 2004 2:49 PM
Body:
I think the problem is :
This problem is due to a bad directory structure.
You merged the build process and the project definition in the same structure.
root
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Wed, 5 May 2004 2:58 PM
Body:
Oups sorry.
The best way is :
root
|--project.xml (run multiproject from here, you don't need deps))
|--master
| |--project.xml
|--subproject1
|
The following comment has been added to this issue:
Author: Cameron Fieber
Created: Wed, 5 May 2004 3:09 PM
Body:
the structure is as you described in the first case, however the top level project.xml
doesn't define any dependencies, it is just used to define the build structure,
Hi
I don't think (excuse me all for giving my opinion like this being
so unknown) supporting eclipse plugins directy should be added to maven.
This would be a lot of work and little payoff. I think that the current
plugin shuold be improved to support all data for .project and
.classpath
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Wed, 5 May 2004 3:28 PM
Body:
OK, for resolve your problem, you can run :
maven -Dgoal=clean,jar:install multiproject:goal
this command line do a clean and a jar:install for each subproject, so
jvanzyl 2004/05/05 13:33:30
Modified:maven-plugins/maven-idea-plugin project.xml
Log:
Revision ChangesPath
1.2 +0 -13 maven-components/maven-plugins/maven-idea-plugin/project.xml
Index: project.xml
jvanzyl 2004/05/05 13:45:08
Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
Log:
o take the source directories from the model. we want to use relative paths
so reach into the model for the unexpanded paths.
On Wed, 2004-05-05 at 15:52, Emmanuel Venisse wrote:
Jason,
Could you do it more generic?
You hardcode the java version and sources directories. I think isn't usable
for future users.
Good eye, I whipped that one off quick. I took the source directories
from the model. For the java version
jvanzyl 2004/05/05 13:51:03
Modified:maven-plugins/maven-idea-plugin project.xml
maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
Log:
o use the java.version system property. i'm sure we could configure this
The following comment has been added to this issue:
Author: thierry lach
Created: Wed, 5 May 2004 4:53 PM
Body:
eclipse.dependencyfalse/eclipse.dependency could be useful to explicitly bypass
specific jar files
My specific situation is that I am building a war file to run
The following issue has been updated:
Updater: thierry lach (mailto:[EMAIL PROTECTED])
Date: Wed, 5 May 2004 4:53 PM
Comment:
Alternate patch.
Changes:
Attachment changed to classpath.jelly.patch
jvanzyl 2004/05/05 15:56:58
Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
Log:
o cleaning up before writing out the project file using the xml writer in order to
create a reactor aware mode that can write out
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Wed, 5 May 2004 7:08 PM
Comment:
It's a good point, but it won't be fixed in 1.0 unfortunately
Changes:
Fix Version changed to 1.1
Jason, should these plugins have their own package? Isn't
org.apache.maven.plugin going to hit a namespace conflict at some point?
- Brett
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 May 2004 6:46 AM
To: Maven Developers List
Subject: Re: cvs
I'm a little confused on this thread. The fast xdoc plugins sounds good and
using *Mesh sounds like a neat idea, but I still don't understand why we
need things to conform to a certain XHTML output format.
Surely the inputs are the page body (xdoc), the navigation (xml), and
perhaps some other
On Wed, 2004-05-05 at 19:18, Brett Porter wrote:
I'm a little confused on this thread. The fast xdoc plugins sounds good and
using *Mesh sounds like a neat idea, but I still don't understand why we
need things to conform to a certain XHTML output format.
Surely the inputs are the page body
Fair enough, so all that is needed is a way to register/deregister your xdoc
- xhtml handler as part of the site plugin, for example.
- Brett
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 May 2004 9:40 AM
To: Maven Developers List
Subject: RE:
On Wed, 2004-05-05 at 19:46, Brett Porter wrote:
Fair enough, so all that is needed is a way to register/deregister your xdoc
- xhtml handler as part of the site plugin, for example.
Yes the site plugin, or something akin to it will handled all the
optional munging and various hooks. I myself
jvanzyl 2004/05/05 17:19:41
Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
Added: maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaWriter.java
Log:
dion2004/05/05 18:14:20
Modified:plugin plugin.jelly
Log:
Fix comments about expected attributes
Revision ChangesPath
1.36 +1 -1 maven-plugins/plugin/plugin.jelly
Index: plugin.jelly
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 5 May 2004 9:49 PM
Body:
create-cvspass creates the file where the changelog plugin expects it, in
${user.home}. That's the point of it.
If you want to create it somewhere else, use maven.xml
dion2004/05/05 18:56:05
Modified:changelog/xdocs goals.xml changes.xml
Log:
Fix bad goals documentation
Revision ChangesPath
1.3 +23 -7 maven-plugins/changelog/xdocs/goals.xml
Index: goals.xml
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 5 May 2004 9:56 PM
Body:
I fixed the documented goals
-
View this comment:
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 5 May 2004 9:57 PM
Body:
BTW, the changelog plugin does NOT use your installed client to perform CVS
operations. So any issues with the CVSNT client are irrelevant
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 5 May 2004 9:58 PM
Body:
Can you run
maven -X maven-changelog-plugin:report
and post the output?
-
View this comment:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271
Here is an overview of the issue:
The following issue has been updated:
Updater: Christian Stein (mailto:[EMAIL PROTECTED])
Date: Thu, 6 May 2004 12:45 AM
Comment:
Complete console output.
Changes:
Attachment changed to maven+eclipse.txt
The following issue has been updated:
Updater: Christian Stein (mailto:[EMAIL PROTECTED])
Date: Thu, 6 May 2004 12:46 AM
Comment:
Debugging console. (-X)
Changes:
Attachment changed to maven_-X_eclipse.txt
The following comment has been added to this issue:
Author: Christian Stein
Created: Thu, 6 May 2004 12:52 AM
Body:
Created an issue, as my problem differs from this one:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271
The following comment has been added to this issue:
Author: Christian Stein
Created: Thu, 6 May 2004 12:57 AM
Body:
Why cactus? See excerpt from maven_-X_eclipse.txt:
[...]
Using projectPropertiesFile:
...\.maven\plugins\cactus-maven-1.6dev-20040226\project.properties
Using
82 matches
Mail list logo
