Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1256
Here is an overview of the issue:
---
At the moment, the relationship is the wrong way around - the release plugin
should contact the SCM. That's my fault. I didn't want to mess with the
existing release plugin other than to reuse the POM transformer inside
there.
Jason is currently working on the release process as well, so I think w
I am not very clear about this: so we use the scm plugin for performing
releases? But not the release plugin, right? What's the goal? To modify
and use the release plugin in the future? (makes more sense to me - the
name is great!).
I'm asking because I was planning to work on the release process
Sorry, same thing as before. I was in changes mode, but I really meant
release.
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Monday, 3 May 2004 3:53 PM
> To: 'Maven Developers List'
> Subject: RE: Little glitches in rc2 release process
>
>
> Brett,
>
>
> > A bug in the changes plugin, already fixed.
>
> What's the relationship with the changes plugin?
>
Sorry, I meant release plugin.
scm:prepare-release utilises changes to transform changes and release to
transform the POM.
- Brett
Brett,
What's the relationship with the changes plugin?
Thanks
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 03 May 2004 01:20
> To: 'Maven Developers List'
> Subject: RE: Little glitches in rc2 release process
>
> File a bug against the changes pl
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 03 May 2004 01:23
> To: 'Maven Developers List'
> Subject: RE: Little glitches in rc2 release process
>
> > - in several plugins there are wrong tags. Here's
> > what I typically find:
>
> A bug in the changes
jvanzyl 2004/05/02 20:47:51
Modified:maven-core/src/bin classworlds.conf
Log:
o tools.jar isn't required, the compiler component should know how
to find what it needs and it does.
Revision ChangesPath
1.4 +0 -1 maven-components/maven-core/src/bin/classworld
> Vincent discussed this with dIon and me on IRC and we
> supported this change.
That's fine, but it was a reasonably large change, and it seemed like there
were unresolved issues around it reading the mailing list.
Anyway, if everyone is happy, I'm ok with it - I just wanted to make sure
everyo
On Mon, 3 May 2004 09:41:16 +1000, Brett Porter <[EMAIL PROTECTED]>
wrote:
Vincent,
Thanks for all the work you did on this. I wish I'd been around to get
in on the discussion - I think we still may have to consider how we
handle this inheritence in RC3 if it is going to break builds.
I'm a b
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1255
Here is an overview of the issue:
---
Vincent,
Thanks for all the work you did on this. I wish I'd been around to get in on
the discussion - I think we still may have to consider how we handle this
inheritence in RC3 if it is going to break builds.
I'm a bit concerned that you've jumped in and changed the maven-plugins CVS
without mu
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Sun, 2 May 2004 7:25 PM
duplicate of MPAPPSERVER-6.
You'll need to either use RC1, or build the maven core from MAVEN-1_0-BRANCH.
-
View th
On Sun, 2004-05-02 at 19:16, Brett Porter wrote:
> The memory problem is in xdoc (I guess jelly) somewhere.
Which we can remedy by using the new java version of the xdoc.
> - Brett
>
> > -Original Message-
> > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > Sent: Monday, 3 May 2004 7
> - in several plugins there are wrong tags. Here's
> what I typically find:
A bug in the changes plugin, already fixed.
> - It's missing the download link for the new version in
> navigation.xml. For example, for the 1.1 release of
> aspectwerkz plugin:
I propose we remove all of these. Use
File a bug against the changes plugin.
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Monday, 3 May 2004 12:10 AM
> To: 'Maven Developers List'
> Subject: RE: Little glitches in rc2 release process
>
>
> Here's another one:
>
> - The element has been mov
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sun, 2 May 2004 7:18 PM
Changes:
description changed from
line 77 in ArtifactListBuilder is :
artifact.setPath( new File( mavenJarProperty ).getAbsolutePath() );
this assumes
The memory problem is in xdoc (I guess jelly) somewhere.
- Brett
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Monday, 3 May 2004 7:34 AM
> To: 'Maven Developers List'
> Subject: plugin sites have been rebuilt...
>
>
> FYI, I've just rebuilt all the plug
The following comment has been added to this issue:
Author: Brett Porter
Created: Sun, 2 May 2004 6:58 PM
Body:
The fix is in the maven core, on MAVEN-1_0-BRANCH, which has not yet been merged to
HEAD.
-
View this
vmassol 2004/05/02 14:39:03
Modified:simian/xdocs index.xml
Log:
fixed broken URL
Revision ChangesPath
1.3 +1 -1 maven-plugins/simian/xdocs/index.xml
Index: index.xml
===
RCS file: /home/c
vmassol 2004/05/02 14:37:14
Modified:xdoc/xdocs changes.xml
Log:
fixed typo
Revision ChangesPath
1.45 +1 -0 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/m
FYI, I've just rebuilt all the plugin web sites.
Boy, that was long and memory hungry! I had given the JVM 512M of RAM
and it could only reach letter J of the plugins. I had to do it chunck
by chunck. We still have a memory problem somewhere it seems.
-Vincent
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-9
Here is an overview of the issue:
> -Original Message-
> From: Arnaud Heritier [mailto:[EMAIL PROTECTED]
> Sent: 02 May 2004 22:13
> To: 'Maven Developers List'
> Subject: RE: Problems with parent-plugin
>
> That's good!
> Thanks a lot.
> What you did today is very useful (in my opinion).
I'm glad you liked it, whatever
That's good!
Thanks a lot.
What you did today is very useful (in my opinion).
#Arnaud
> -Message d'origine-
> De : Vincent Massol [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 2 mai 2004 20:39
> À : 'Maven Developers List'
> Objet : RE: Problems with parent-plugin
>
> Arnaud,
>
> It sho
Arnaud,
It should build fine now. I had forgotten to exclude the newly created
plugin-parent/ dir.
It now works on my machine
Thanks
-Vincent
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: 02 May 2004 20:17
> To: 'Maven Developers List'
> Subject: RE: Prob
vmassol 2004/05/02 11:31:32
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
exclude plugin-parent/ dir from plugin build
Revision ChangesPath
No revision
No revision
1.51.2.23 +1 -1 maven/project.properties
Let me try the full bootstrap on my machine.
Thanks
-Vincent
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: 02 May 2004 20:00
> To: 'Maven Developers List'
> Subject: Problems with parent-plugin
>
> Hello Vincent,
>
> Theres a problem with commits
aheritier2004/05/02 11:05:39
Modified:.project.properties
Log:
Fix Typo
Revision ChangesPath
1.12 +1 -1 maven-plugins/project.properties
Index: project.properties
===
RCS file: /hom
Hello Vincent,
Theres a problem with commits that you did today.
When I do:
Ant f build-bootstrap.xml
I have this error:
[copy] Copying 84 files to
D:\Work\Dev\maven-1.0\bootstrap\install-phase1\plugins
[echo]
[echo] |
[echo] | BUILDING MAV
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Sun, 2 May 2004 1:35 PM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-26
Here is an overview of the
vmassol 2004/05/02 10:24:17
Modified:.project.properties
Log:
exclude the plugin-parent/ directory from the master build as it's not a real maven
project
Revision ChangesPath
1.11 +1 -0 maven-plugins/project.properties
Index: project.properties
=
vmassol 2004/05/02 10:02:09
Modified:artifact/src/main/org/apache/maven/deploy/exceptions
UnsupportedProtocolException.java
AuthenticationException.java DeployException.java
TransferFailedException.java
On Sun, 2004-05-02 at 05:17, Vincent Massol wrote:
> Forget it. I was too eager. Let's just hope we get 1.0 real soon so that
> we can start working on 1.1 :-)
Take a look at the maven.mdo file, figure out what you would like and it
can be added shortly after 1.0 and I will backport the use of the
vmassol 2004/05/02 08:04:34
Modified:artifact/src/main/org/apache/maven/deploy
RepositoryInfo.java DeployTool.java
DeployRequest.java
artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifac
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1254
Here is an overview of the issue:
---
vmassol 2004/05/02 07:50:02
Modified:plugin-parent project.xml
Log:
removed jelly taglib report from default list of reports
Revision ChangesPath
1.2 +0 -1 maven-plugins/plugin-parent/project.xml
Index: project.xml
===
vmassol 2004/05/02 07:27:09
Modified:simian project.xml
jdee project.xml
multiproject project.xml
jettyproject.xml
multichanges project.xml
xdoc project.xml
Log:
use default reports
Revision
vmassol 2004/05/02 07:23:22
Modified:.project.properties
Log:
remove properties not required for the master build
Revision ChangesPath
1.10 +3 -13 maven-plugins/project.properties
Index: project.properties
==
vmassol 2004/05/02 07:17:02
Modified:uberjar project.xml
tjdo project.xml
test project.xml
touchstone-partner project.xml
touchstone project.xml
tasklist project.xml
multiproject project.xm
vmassol 2004/05/02 07:16:25
Modified:struts project.xml
simian project.xml
jdee project.xml
shellproject.xml
jdeveloper project.xml
jdepend project.xml
linkcheck project.xml
Here's another one:
- The element has been moved to the end of the project.xml
which is not the correct place (it should be after
Thanks
-Vincent
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: 01 May 2004 12:25
> To: 'Maven Developers List'
> Subject: Lit
vmassol 2004/05/02 07:09:31
Modified:jbuilder/xdocs changes.xml
jbuilder project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.15 +1 -1 maven-plu
vmassol 2004/05/02 07:08:45
Modified:jboss/xdocs changes.xml
jbossproject.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.26 +1 -1 maven-plugin
vmassol 2004/05/02 07:06:38
Modified:javadoc/xdocs changes.xml
javadoc project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.25 +1 -1 maven-plug
vmassol 2004/05/02 07:05:57
Modified:javacc project.xml
javacc/xdocs changes.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.7 +13 -8 maven-plugi
vmassol 2004/05/02 07:05:33
Modified:javacc plugin.jelly
Log:
Binary --> Ascii
Revision ChangesPath
1.4 +90 -90maven-plugins/javacc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cv
vmassol 2004/05/02 07:04:49
Modified:java project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.22 +7 -2 maven-plugins/java/project.xml
Index: project.
vmassol 2004/05/02 07:04:08
Modified:jar project.xml
jar/xdocs changes.xml
Removed: jar/announcements 1.1.ann
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesP
vmassol 2004/05/02 07:01:09
Modified:jalopy/xdocs changes.xml
jalopy project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.9 +3 -1 maven-plugi
vmassol 2004/05/02 06:59:28
Modified:j2ee/xdocs changes.xml
j2ee project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.15 +1 -1 maven-plugins
vmassol 2004/05/02 06:57:51
Modified:idea project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.24 +13 -8 maven-plugins/idea/project.xml
Index: project.
vmassol 2004/05/02 06:55:51
Modified:html2xdoc project.xml
html2xdoc/xdocs changes.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.28 +13 -26maven-p
vmassol 2004/05/02 06:54:46
Modified:hibernate project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.26 +13 -17maven-plugins/hibernate/project.xml
Index: pr
vmassol 2004/05/02 06:53:40
Modified:gump/xdocs changes.xml
gump project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.5 +2 -1 maven-plugins
vmassol 2004/05/02 06:52:50
Modified:genapp project.xml
genapp/xdocs changes.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.23 +13 -16maven-plugi
vmassol 2004/05/02 06:49:47
Modified:file-activity/xdocs changes.xml
file-activity project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.9 +2 -0
vmassol 2004/05/02 06:48:35
Modified:ejb/xdocs changes.xml
ejb project.xml
Removed: ejb/announcements 1.3.ann
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesP
vmassol 2004/05/02 06:47:10
Modified:eclipse project.xml
Removed: eclipse/src/announcements 1.5.ann
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.28 +6 -1 ma
vmassol 2004/05/02 06:46:29
Modified:ear/xdocs changes.xml
ear project.xml
Removed: ear/announcements 1.4.ann
Log:
- inherit from the plugin-parent/project.xml POM instead of the top level one which
is reserved for the master build
- removed custom repor
vmassol 2004/05/02 06:45:38
Modified:docbook/xdocs changes.xml
docbook project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.13 +1 -1 maven-plug
vmassol 2004/05/02 06:44:56
Modified:dist project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.24 +13 -8 maven-plugins/dist/project.xml
Index: project.
vmassol 2004/05/02 06:44:07
Modified:developer-activity project.xml
developer-activity/xdocs changes.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.25
vmassol 2004/05/02 06:42:49
Modified:deploy project.xml
deploy/xdocs changes.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.21 +8 -30 maven-plugi
vmassol 2004/05/02 06:41:30
Modified:dashboard project.xml
Log:
inherit from the plugin-parent/project.xml POM instead of the top level one which is
reserved for the master build
Revision ChangesPath
1.16 +1 -10 maven-plugins/dashboard/project.xml
Index: pr
vmassol 2004/05/02 06:41:03
Modified:cruisecontrol project.xml
Log:
- inherit from the plugin-parent/project.xml POM instead of the top level one which
is reserved for the master build
- removed custom reports as we can now use the default ones from
plugin-parent/project.xml
vmassol 2004/05/02 06:40:19
Modified:console project.xml
Log:
- inherit from the plugin-parent/project.xml POM instead of the top level one which
is reserved for the master build
- removed custom reports as we can now use the default ones from
plugin-parent/project.xml
Rev
67 matches
Mail list logo