Howdy,
I just finished a tiny goal to create a little bundle that could be
pushed somewhere for checking and subsequent deployment to ibiblio.
I was thinking that a simple and secure way to check things would be to:
- include a pointer to an md5 file for the bundle inside the bundle and
the loc
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Tue, 6 Jan 2004 9:42 PM
First little attempt at creating a bundle is done.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.j
jvanzyl 2004/01/06 19:24:12
Modified:repository plugin.jelly
Log:
o add goal to create an artifact upload bundle
Revision ChangesPath
1.23 +24 -1 maven-plugins/repository/plugin.jelly
Index: plugin.jelly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPREPO-4
Here is an overview of the issue:
---
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Tue, 6 Jan 2004 7:36 PM
Fixed in 1.4-SNAPSHOT
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAVADOC-17
Here is
dion2004/01/06 17:20:19
Modified:javadoc/xdocs changes.xml properties.xml index.xml
javadoc plugin.jelly
Log:
Apply MPJAVADOC-17
Revision ChangesPath
1.17 +3 -0 maven-plugins/javadoc/xdocs/changes.xml
Index: changes.xml
===
jvanzyl 2004/01/06 16:02:24
Modified:announcement/xdocs changes.xml
Log:
adding change
Revision ChangesPath
1.2 +5 -0 maven-plugins/announcement/xdocs/changes.xml
Index: changes.xml
===
RC
jvanzyl 2004/01/06 16:01:43
Modified:jnlp/xdocs changes.xml
Log:
adding change
Revision ChangesPath
1.6 +4 -0 maven-plugins/jnlp/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cv
jvanzyl 2004/01/06 16:00:55
Modified:javadoc/xdocs changes.xml
Log:
adding change
Revision ChangesPath
1.16 +4 -0 maven-plugins/javadoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /h
jvanzyl 2004/01/06 15:59:46
Modified:xdoc/xdocs changes.xml
Log:
adding change
Revision ChangesPath
1.29 +6 -2 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cv
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-23
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Tue, 6 Jan 2004 6:04 PM
Changes:
Version changed to 1.0-rc1
Fix Version changed to 1.1
-
For
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1109
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Stephen Colebourne (mailto:[EMAIL PROTECTED])
Date: Tue, 6 Jan 2004 5:53 PM
Comment:
Patch from base to improve the javadoc plugin documentation
Changes:
Attachment changed to MavenJavadocPatch.txt
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAVADOC-17
Here is an overview of the issue:
---
The following comment has been added to this issue:
Author: Stephen Colebourne
Created: Tue, 6 Jan 2004 5:48 PM
Body:
maven.javadoc.locale is a recognised property for the javadoc plugin
-
View the issue:
http:/
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Tue, 6 Jan 2004 4:54 PM
The need for ${pom} interpolation of properties has been removed. The
tag is now being used to provide a default value.
--
On Tue, 2004-01-06 at 17:11, Brett Porter wrote:
> Yes, I agree - I was just talking about this specific case - testing that
> pom interpolation in properties still works as it used to. Its probably a
> core thing, but the specific case of maven.xdoc.version is worth adding to
> xdoc's plugin:test.
jvanzyl 2004/01/06 14:18:49
Modified:jnlp plugin.jelly
Log:
o formatting
Revision ChangesPath
1.17 +6 -6 maven-plugins/jnlp/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/mave
> You're right that the docs suck and this would be one way to try and
> enforce it. If there are no public properties then that would have to be
> explicitly stated too.
>
I am all for not only explicitly stating public properties(+1) but also for
a) stating public goals
b) expressing constrains
jvanzyl 2004/01/06 14:14:15
Modified:jnlp plugin.jelly
Log:
o defaults need to be set before anything happens. jnlp file came out wonky.
Revision ChangesPath
1.16 +4 -3 maven-plugins/jnlp/plugin.jelly
Index: plugin.jelly
==
I'm all about saving everyone work :) Adding code to two different places
sucks as much as trying to find the differences later.
This is actually a good reason to get the component code in sync and
integrated reasonably soon so that they don't fall behind because there
isn't really a way to merge
Yes, I agree - I was just talking about this specific case - testing that
pom interpolation in properties still works as it used to. Its probably a
core thing, but the specific case of maven.xdoc.version is worth adding to
xdoc's plugin:test.
- Brett
> -Original Message-
> From: Jason van
On Tue, 2004-01-06 at 17:05, Brett Porter wrote:
> Merging the branch wouldn't be much fun with this addition happening in both
> places - it might be best to keep them to just the branch and they'll come
> through with the first merge from there.
No problem, I'll let you be the merge kingpin! :-)
On Tue, 2004-01-06 at 17:03, Brett Porter wrote:
> Ok. If we clean up all our plugins, can we make sure there is a test
> somewhere to prove it still works?
There has to be tests for all plugins. I've started making an xmlunit
tool for all plugins that spew xml.
> Otherwise users find the bugs a
Merging the branch wouldn't be much fun with this addition happening in both
places - it might be best to keep them to just the branch and they'll come
through with the first merge from there.
Nothing has changed on HEAD for a while except for the POMv4 stuff, and that
will move anyway with the in
Ok. If we clean up all our plugins, can we make sure there is a test
somewhere to prove it still works? Otherwise users find the bugs and we have
to spend longer on future RC's. I guess that means a touchstone test for it,
or maybe xdoc plugin:test.
Thanks,
Brett
> -Original Message-
> Fr
jvanzyl 2004/01/06 14:02:40
Modified:jnlp plugin.jelly plugin.properties
Log:
o using maven:property and removing use of ${pom} in the plugin properties
with emmanuel's permission.
Revision ChangesPath
1.15 +8 -1 maven-plugins/jnlp/plugin.jelly
Inde
On Tue, 2004-01-06 at 16:56, Brett Porter wrote:
> Jason,
>
> Even if this is deprecated behaviour, it needs to continue working for 1.0
> doesn't it?
Yup, it does. I'm just cleaning up our plugins.
> - Brett
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Jason,
Even if this is deprecated behaviour, it needs to continue working for 1.0
doesn't it?
- Brett
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 7 January 2004 7:49 AM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugins/announcem
[quote]
maybe we could expand the
project/properties to include optional descriptions and default values
and we could easily generate doco for that.
[/quote]
+20 for that vote! I would love to see the default values for properties
and attributes right in the doco, and standardized across all plugi
On Tue, 2004-01-06 at 16:36, Jason van Zyl wrote:
> > I think we need something more. Making it mandatory for the plugin to
> > work would be better I think.
>
> Currently there is no real way to distinguish between a public property
> and a private one even though in most cases they are almost a
On Tue, 2004-01-06 at 16:26, Vincent Massol wrote:
> The problem is that, as you know, documentation is far from reality...
> :-)
That is now the problem of the plugin developers, but I agree it has
been a problem in the past.
> Just look at existing plugin documentation and you'll see that the
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 06 January 2004 22:12
> To: Maven Developers List
> Subject: RE: cvs commit: maven-plugins/announcement plugin.properties
>
> On Tue, 2004-01-06 at 15:52, Vincent Massol wrote:
> > Hi Jason,
> >
> > There was on
Jason,
I'm not sure I understand the commit message below. AFAIK the
aspectwerkz plugin is working fine and its tests are passing. It was
excluded by Brett as a test was failing when he tried to bootstrap
Maven, but I have fixed it shortly thereafter. I did not remove the
exclusion though.
Thanks
On Tue, 2004-01-06 at 15:52, Vincent Massol wrote:
> Hi Jason,
>
> There was one nice benefit of having properties defined in
> plugin.properties: it was clearly stating what properties where public
> and what were private. By removing them you are removing this "feature".
>
> How can we restore
On Tue, 2004-01-06 at 15:52, Vincent Massol wrote:
> Hi Jason,
>
> There was one nice benefit of having properties defined in
> plugin.properties: it was clearly stating what properties where public
> and what were private. By removing them you are removing this "feature".
>
> How can we restore
Hi Jason,
There was one nice benefit of having properties defined in
plugin.properties: it was clearly stating what properties where public
and what were private. By removing them you are removing this "feature".
How can we restore this?
Thanks
-Vincent
> -Original Message-
> From: [EMA
jvanzyl 2004/01/06 12:48:47
Modified:announcement plugin.properties
Log:
o property is gleaned within the plugin using the pom directly.
Revision ChangesPath
1.2 +1 -1 maven-plugins/announcement/plugin.properties
Index: plugin.properties
jvanzyl 2004/01/06 12:48:07
Modified:announcement/src/plugin-resources announcement.jsl
Log:
o use maven:property to glean a default instead of relying on interpolation
of ${pom} values in the plugin properties files.
Revision ChangesPath
1.4 +2 -2 maven-pl
On Tue, 2004-01-06 at 13:58, Steve Garcia wrote:
> > > Now, if project B's pom is stored in the local repo with no
> > properties
> > > resolved (i.e. the pom file is not the interpolated
> > version) then project
> > > A needs to have definitions for these properties. This would not be
> > > p
jvanzyl 2004/01/06 11:57:53
Modified:src/java/org/apache/maven/jelly/tags/maven Tag:
MAVEN-1_0-BRANCH PropertyTag.java
Log:
o keeping up with HEAD
Revision ChangesPath
No revision
No revision
1.4.2.2 +0 -4
jvanzyl 2004/01/06 11:57:04
Modified:src/java/org/apache/maven/jelly/tags/maven PropertyTag.java
Log:
o the usage blurp blows up the jelly doc plugin because it tries to treat
it as a plugin ...
Revision ChangesPath
1.5 +0 -4
maven/src/java/org/apache/mave
> > Now, if project B's pom is stored in the local repo with no
> properties
> > resolved (i.e. the pom file is not the interpolated
> version) then project
> > A needs to have definitions for these properties. This would not be
> > possible unless the properties files are also made
> availabl
jvanzyl 2004/01/06 10:51:51
Added: src/java/org/apache/maven/jelly/tags/maven Tag:
MAVEN-1_0-BRANCH PropertyTag.java
Log:
o keeping branch up-to-date with HEAD
Revision ChangesPath
No revision
No revision
1
jvanzyl 2004/01/06 10:47:25
Modified:xdoc/src/plugin-resources site.jsl
Log:
o use the new maven:property tag in order to determine the value of
maven.xdoc.version so that we don't need to refer to the pom within
the plugin.properties.
Revision ChangesPath
1.46
jvanzyl 2004/01/06 10:42:11
Modified:src/java/org/apache/maven/jelly/tags/maven PropertyTag.java
Log:
o add setting for var property
Revision ChangesPath
1.4 +5 -0
maven/src/java/org/apache/maven/jelly/tags/maven/PropertyTag.java
Index: PropertyTag.java
jvanzyl 2004/01/06 10:31:33
Modified:.project.properties
Log:
o remove aspectwerkz from the bootstrap due to failing deps
It's fine to add plugins with missing deps for a short time, but please have
the courtesy to remove it from the main build if the deps are goin
> -Original Message-
> From: Ben Walding [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 05, 2004 1:44 PM
> To: Maven Developers List
> Subject: Re: cvs commit:
> maven-components/maven-model/src/test/org/apache/maven/model
> DependencyTest.java
>
>
> Jason van Zyl wrote:
>
> >On Sun, 2
jvanzyl 2004/01/06 10:19:48
Modified:src/java/org/apache/maven/jelly/tags/maven PropertyTag.java
Log:
o just check for null, someone might want an empty string.
Revision ChangesPath
1.3 +1 -1
maven/src/java/org/apache/maven/jelly/tags/maven/PropertyTag.java
jvanzyl 2004/01/06 10:18:33
Modified:src/java/org/apache/maven/jelly/tags/maven PropertyTag.java
Log:
o allow the option of specifying the name the property should be retrieved
with in the MavenJellyContext.
Revision ChangesPath
1.2 +14 -2
maven/src/java/or
jvanzyl 2004/01/06 10:09:57
Modified:src/java/org/apache/maven/jelly/tags/maven
MavenTagLibrary.java
Log:
o adding the property tag to the library.
Revision ChangesPath
1.14 +2 -1
maven/src/java/org/apache/maven/jelly/tags/maven/MavenTag
jvanzyl 2004/01/06 10:09:14
Added: src/java/org/apache/maven/jelly/tags/maven PropertyTag.java
Log:
o adding a property tag which allows the specification of a default value.
Revision ChangesPath
1.1
maven/src/java/org/apache/maven/jelly/tags/maven/Pro
jvanzyl 2004/01/06 10:05:22
Modified:xdoc/src/plugin-resources site.jsl
Log:
o adding jelly maven tag library for use
Revision ChangesPath
1.45 +2 -1 maven-plugins/xdoc/src/plugin-resources/site.jsl
Index: site.jsl
jvanzyl 2004/01/06 10:00:02
Modified:xdoc/src/plugin-resources site.jsl
Log:
o removing glossary cruft
Revision ChangesPath
1.44 +0 -15 maven-plugins/xdoc/src/plugin-resources/site.jsl
Index: site.jsl
===
jvanzyl 2004/01/06 09:58:47
Modified:xdoc/src/plugin-resources site.jsl
Log:
o change log plugin takes care of its own transformation now and has for
a while. Just getting rid of the cruft that's grown in here.
Revision ChangesPath
1.43 +0 -45 maven-plugins/x
jvanzyl 2004/01/06 09:54:01
Modified:xdoc/src/plugin-resources site.jsl
Log:
o task list plugin doesn't require any transformation from the xdoc plugin.
Revision ChangesPath
1.42 +0 -1 maven-plugins/xdoc/src/plugin-resources/site.jsl
Index: site.jsl
=
jvanzyl 2004/01/06 09:46:06
Modified:xdoc/src/plugin-resources site.jsl
Log:
o fixing typo
Revision ChangesPath
1.41 +1 -1 maven-plugins/xdoc/src/plugin-resources/site.jsl
Index: site.jsl
===
Hi Jason,
For me it looks ok, so go ahead.
I just moved our project (at work) to maven, so expect some more patches
when I hit some trouble :)
Mvgr,
Martin
On Tue, 2004-01-06 at 16:29, Jason van Zyl wrote:
> On Wed, 2003-12-17 at 20:34, Martin van den Bemt wrote:
> > I'll have a look tomorrow..
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-74
Here is an overview of the issue:
--
On Wed, 2003-12-17 at 20:34, Martin van den Bemt wrote:
> I'll have a look tomorrow..
Martin,
Is everything now functioning properly with the changes to the FAQ
plugin? I'm ready to make a little release whenever you give the thumbs
up.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.ze
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPARTIFACT-7
Here is an overview of the issue:
---
dion2004/01/06 04:05:33
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
Simian can be included again
Revision ChangesPath
No revision
No revision
1.51.2.6 +1 -3 maven/project.properties
Index: project.
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Tue, 6 Jan 2004 3:02 AM
Clover wasn't needed. Test case renamed so that it ran. Upgraded to ant 1.6
-
View the issue:
http://jira.codehau
dion2004/01/06 00:46:25
Modified:simian project.xml
simian/xdocs changes.xml
Log:
Upgrade to ant 1.6
tests now run and succeed
Revision ChangesPath
1.21 +1 -1 maven-plugins/simian/project.xml
Index: project.xml
=
dion2004/01/06 00:41:00
Added: simian/src/test/org/apache/maven/simian SimianLogTest.java
Removed: simian/src/test/org/apache/maven/simian
SimianLogTestCase.java
Log:
Rename test class so that it is run
Revision ChangesPath
1.1
dion2004/01/06 00:40:17
Modified:simian maven.xml
Log:
Remove unneeded clover plugin dependency
Revision ChangesPath
1.4 +0 -2 maven-plugins/simian/maven.xml
Index: maven.xml
===
RCS
dion2004/01/06 00:25:32
Added: src/test/touchstone-build/src/reactor-build/failProperty/success-1
Tag: MAVEN-1_0-BRANCH .cvsignore
src/test/touchstone-build/src/reactor-build/resources/subproject
Tag: MAVEN-1_0-BRANCH .
brett 2004/01/06 00:25:22
Modified:maven-model-tools project.xml
maven-model-tools/src/java/org/apache/maven/model
DefaultModelUnmarshaller.java
Log:
more deprecation warnings
Revision ChangesPath
1.8 +1 -1 maven-compone
brett 2004/01/06 00:18:26
Modified:maven-model/src/test/org/apache/maven/model ModelTest.java
Log:
improve test coverage
Revision ChangesPath
1.5 +11 -1
maven-components/maven-model/src/test/org/apache/maven/model/ModelTest.java
Index: ModelTest.java
=
brett 2004/01/06 00:16:44
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
fix null pointer exception
Revision ChangesPath
1.17 +2 -2
maven-components/maven-model/src/java/org/apache/maven/model/Model.java
Index: Model.java
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Tue, 6 Jan 2004 2:23 AM
fixed again, full bootstrap works
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1107
brett 2004/01/06 00:07:03
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenConstants.java MavenUtils.java
Log:
PR: MAVEN-1107
Add / to paths, use correct classloader for maven.jar
Revision ChangesPath
No revision
73 matches
Mail list logo
