The following comment has been added to this issue:
Author: Geoffrey
Created: Mon, 5 Jul 2004 3:02 AM
Body:
"depend" is Ant slang,
"prereqs" is the appropriate term for Maven :)
-
View this comment:
http://jira.c
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 5 Jul 2004 3:08 AM
Closing as per Gary's comment.
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4
Here is an ov
The following comment has been added to this issue:
Author: Vincent Massol
Created: Mon, 5 Jul 2004 3:08 AM
Body:
Hi Gary,
In my latest round of patches I've removed the public propety maven.announcement.file.
It is recommended to use the default value. The reason is that this fi
Hi folks,
after waiting for 5 months to have my patch applied, I want to nag the list, to have
somebody of the committers to look and apply that patch:
http://jira.codehaus.org/browse/MPXDOC-80.
It solves the problem for custom themes in a multiproject environment, because the css
have current
evenisse2004/07/05 01:05:28
Modified:jalopy project.xml
jalopy/xdocs changes.xml
Log:
Use Jalopy 1.0b11
Revision ChangesPath
1.36 +3 -3 maven-plugins/jalopy/project.xml
Index: project.xml
==
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Mon, 5 Jul 2004 4:21 AM
Done.
-
View the issue:
http://jira.codehaus.org/browse/MPJALOPY-4
Here is an overview of the issue:
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 5 Jul 2004 8:02 AM
Body:
1) plugin:generate-properties is not removed, is changed. The old one generated
properties.xml to be used as a start point. The new one generate the plugin.properties
We use a seperate project for all objects that are common between the
client and server classes, which includes the rmi stub...
(which is a post goal to java:compile btw). Not too much classes in the
project though, but it works well. (the common.jar has no external
dependencies at all).
Mvgr,
Mar
dion2004/07/05 05:39:38
Modified:nsis/xdocs customizing.xml changes.xml
nsis/src/plugin-resources/templates project.jelly
Log:
MPNSIS-6. Add project url to constants
Revision ChangesPath
1.6 +4 -3 maven-plugins/nsis/xdocs/customizing.xml
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Mon, 5 Jul 2004 8:39 AM
Fixed in 1.1
-
View the issue:
http://jira.codehaus.org/browse/MPNSIS-6
Here is an overview of the issue:
---
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 5 Jul 2004 8:56 AM
Body:
Does this cause any problems?
-
View this comment:
http://jira.codehaus.org/browse/MPNSIS-1?page=com
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPANT-17
Here is an overview of the issue:
-
Key: M
dion2004/07/05 06:05:45
Modified:nsis/src/plugin-resources/templates setup.jelly
Log:
Fix some comments
Revision ChangesPath
1.14 +2 -3 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly
Index: setup.jelly
==
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Mon, 5 Jul 2004 9:12 AM
Body:
Carlos missed some files yesterday when he added this :
+
+
+
+
+
+
+
+
+
+
--
Hello Carlos !
Can you add these files on CVS :
${maven.build.dest}/directory-1/file1.properties
${maven.build.dest}/file2.properties
${maven.test.dest}/directory-1/file1.properties
${maven.test.dest}/file2.properties
An issue was opened by Dion (MPANT-17)
Thanks.
> -Message d'origine-
dion2004/07/05 06:20:37
Modified:nsis/src/plugin-resources/templates project.jelly
nsis/xdocs changes.xml
Log:
Use pom.organization.name instead of pom.organization
Revision ChangesPath
1.9 +3 -3 maven-plugins/nsis/src/plugin-resources/templa
Those files are already there. They're in the src/plugin-test/src directory.
I think the changes to maven.xml were wrong.
The lines:
were added by carlos, and I think they're not valid.
Instead of checking the build.xml contains relative files, he added
some relative pat
dion2004/07/05 06:34:40
Modified:ant/src/plugin-test maven.xml
Log:
Undo relative path stuff
Revision ChangesPath
1.7 +5 -12 maven-plugins/ant/src/plugin-test/maven.xml
Index: maven.xml
=
Mmm, yesterday I've run the tests and succeeded.
I'm gonna check if I missed something.
Don't worry I'll take a look now.
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 05, 2004 3:32 PM
> To: Maven Developers List
> Subject: Re: RE : cvs commit:
The following comment has been added to this issue:
Author: Geoffrey
Created: Mon, 5 Jul 2004 9:36 AM
Body:
I installed rc4 to a custom directory and my MAVEN_HOME was wrongly set with a double
\ (slash) instead of one. Found it after a short while by checking the MAVEN_HOME, but
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPHIBERNATE-7
Here is an overview of the issue:
-
K
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPTEST-36
Here is an overview of the issue:
-
Key:
epugh 2004/07/05 07:29:24
Modified:hibernate/src/plugin-test maven.xml
Log:
Restore cleaning after tests are run
Revision ChangesPath
1.3 +1 -1 maven-plugins/hibernate/src/plugin-test/maven.xml
Index: maven.xml
=
epugh 2004/07/05 07:29:55
Modified:hibernate/xdocs changes.xml
hibernate/src/plugin-test project.properties
Log:
MPHIBERNATE-7 plugin:test fails. Provide complete path versus relative
Revision ChangesPath
1.17 +1 -0 maven-plugins/hibernate/xdoc
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Mon, 5 Jul 2004 10:30 AM
Fixed.. I only tested by running from src/plugin-test the testPlugin goal.. Now I
know about the plugin:test goal!
--
epugh 2004/07/05 07:32:10
Modified:eclipse/src/plugin-test maven.xml
Log:
Remove test
Revision ChangesPath
1.6 +0 -11 maven-plugins/eclipse/src/plugin-test/maven.xml
Index: maven.xml
===
epugh 2004/07/05 07:33:05
maven-plugins/cruisecontrol/src/plugin-test - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
epugh 2004/07/05 07:33:08
Added: cruisecontrol/src/plugin-test .cvsignore
Log:
Ignore eclipse generated files.
Revision ChangesPath
1.1 maven-plugins/cruisecontrol/src/plugin-test/.cvsignore
Index: .cvsignore
===
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-23
Here is an overview of the issue:
-
K
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-24
Here is an overview of the issue:
-
K
The following comment has been added to this issue:
Author: Miguel Griffa
Created: Mon, 5 Jul 2004 11:07 AM
Body:
It would be nice that the banner also has information about which tests failed, so you
can jump right to the that test report
-
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Mon, 5 Jul 2004 11:13 AM
Body:
Additionally if the deployment creates new directoryies, they are not writable by the
group! This is quite critical!
-
The following comment has been added to this issue:
Author: Michal Maczka
Created: Mon, 5 Jul 2004 1:34 PM
Body:
Are you aware of any ftp commands which can help?
IMO there is not much we can do about it using capabilities of ftp protocol.
The following comment has been added to this issue:
Author: Gary Gregory
Created: Mon, 5 Jul 2004 2:28 PM
Body:
Clearly it is important to remain backwards compatible.
If other plugins want to point to this generated file, should they not use the
poperty value anyway instead of
carlos 2004/07/05 11:44:47
Modified:ant/src/plugin-test maven.xml
Log:
Fixed test for issue MPANT-17
Revision ChangesPath
1.8 +17 -2 maven-plugins/ant/src/plugin-test/maven.xml
Index: maven.xml
Fixed, now test fails with previous version and succeeds with latest.
Sorry, it was a stupid error.
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 05, 2004 3:32 PM
> To: Maven Developers List
> Subject: Re: RE : cvs commit:
> maven-plugins/ant/
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPANT-17
Here is an overview of the issue:
-
Key: M
brett 2004/07/05 13:54:26
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
AntProjectBuilder.java
Log:
basedir must be absolute
Revision ChangesPath
No revision
No revision
1.6.4.4 +1 -1 mave
brett 2004/07/05 13:58:49
Modified:.Tag: MAVEN-1_0-BRANCH maven.xml
Log:
fix seed repo generation, add plugin install profile generation for later use
Revision ChangesPath
No revision
No revision
1.97.2.30 +38 -4 maven
Fixed in CVS. and now load the plugin if necessary.
I'll add a test on the way in for :set and then post some more info - looks like
we can ditch those stupid dependency handles though.
The fix is something like the last straw the PluginManager camel's back can
take, but it's still holding :)
P
brett 2004/07/05 14:01:49
Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml
xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
and initial
brett 2004/07/05 14:03:37
Modified:linkcheck/src/main/org/apache/maven/linkcheck/validation
HTTPLinkValidator.java
Log:
PR: MPLINKCHECK-14
only show stack trace when in debug mode
Revision ChangesPath
1.12 +3 -2
maven-plugins/linkche
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPLINKCHECK-14
Here is an overview of the issue:
-
brett 2004/07/05 14:07:19
Modified:jira project.xml
jira/xdocs changes.xml
jxr project.xml
jxr/xdocs changes.xml
latexproject.xml
latex/xdocs changes.xml
latkaproject.xml
epugh 2004/07/05 14:26:29
Modified:jbuilder plugin.jelly
Log:
use maven:pluginVar to retrieve reference to junit
Revision ChangesPath
1.24 +4 -9 maven-plugins/jbuilder/plugin.jelly
Index: plugin.jelly
epugh 2004/07/05 14:28:05
Modified:test plugin.jelly
Log:
don't need test:eclipse secret goal, Eclipse uses maven:pluginVar to
retrieve JUnit dependency.
Revision ChangesPath
1.34 +0 -4 maven-plugins/test/plugin.jelly
Index: plugin.jelly
=
You forgot to add the xml taglib to the project.xml.
Now 'maven testPlugin' fails from the ant\src\plugin-test directory.
On 5 Jul 2004 18:44:47 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> carlos 2004/07/05 11:44:47
>
> Modified:ant/src/plugin-test maven.xml
> Log:
> Fix
The synonym is the official method of doing this.
pluginVar is deprecated.
- Brett
Quoting [EMAIL PROTECTED]:
> epugh 2004/07/05 14:26:29
>
> Modified:jbuilder plugin.jelly
> Log:
> use maven:pluginVar to retrieve reference to junit
>
> Revision ChangesPath
> 1.24
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 6 Jul 2004 12:27 AM
Body:
Some projects, e.g. Maven, use NSIS but don't use dist to create the contents.
I'm happy for this to be a user driven thing rather than the NSIS plugin forcing you
to
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPTEST-37
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVA-23
Here is an overview of the issue:
-
Key:
The following issue has been updated:
Updater: Olaf Müller (mailto:[EMAIL PROTECTED])
Date: Tue, 6 Jul 2004 2:06 AM
Comment:
change state
Changes:
Attachment changed to wget.txt
-
For a full his
The following comment has been added to this issue:
Author: Geoffrey
Created: Tue, 6 Jul 2004 2:49 AM
Body:
Ah k :) Close this issue then please.
Is there a particular reason that Maven doesn't just override the dist goal to make
its binary distribution?
-
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 6 Jul 2004 2:58 AM
Body:
History and lack of time
-
View this comment:
http://jira.codehaus.org/browse/MPNSIS-3?page=comm
54 matches
Mail list logo
