Mavens
I've created an ant script that pulls and builds about a dozen
dependencies for my project. Output goes to the local maven
repository. For each artifact, I create three files:
artifact-debug-1.0.jar
artifact-src-1.0.jar
artifact-doc-1.0.jar
Now I'd like to hack the Eclipse plugin to
The following comment has been added to this issue:
Author: Julien Dubois
Created: Tue, 28 Oct 2003 2:27 AM
Body:
Hi,
I had the same issue, and spent a couple of hours on it, however I haven't a clear
understanding of what caused it.
I only had this problem on one of my Windows
evenisse2003/10/28 02:55:18
maven/src/plugins-build/changelog/src/main/org/apache/maven/perforcelib - New
directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
evenisse2003/10/28 02:55:33
maven/src/plugins-build/changelog/src/test-resources/perforcelib - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
evenisse2003/10/28 02:55:47
maven/src/plugins-build/changelog/src/test/org/apache/maven/perforcelib - New
directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
evenisse2003/10/28 02:57:43
Modified:src/plugins-build/changelog/src/plugin-resources
changelog.jsl
src/plugins-build/changelog/xdocs changes.xml index.xml
navigation.xml properties.xml
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Tue, 28 Oct 2003 5:25 AM
Applied. Thanks.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-963
Here is
I'm pretty confused when looking at artifact and
deploy plugins. It seems to me, that they offer very
similar functionality. Some plugins depends on
artifact plugin (e.g. ejb, war, ear,
javadoc) and some on deploy plugin (e.g. dist).
And deploy plugin doesn't delegate its work to
artifact plugin.
dion2003/10/28 10:08:46
Added: src/java/org/apache/maven/jelly/tags/maven PluginVarTag.java
Log:
Add plugin var tag, as per MAVEN-950
Revision ChangesPath
1.1
maven/src/java/org/apache/maven/jelly/tags/maven/PluginVarTag.java
Index:
dion2003/10/28 10:09:08
Modified:src/java/org/apache/maven/jelly/tags/maven
MavenTagLibrary.java
Log:
Add plugin var tag, as per MAVEN-950
Revision ChangesPath
1.13 +2 -1
dion2003/10/28 10:13:57
Modified:src/test/touchstone-build maven.xml
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.43 +4 -4 maven/src/test/touchstone-build/maven.xml
Index: maven.xml
dion2003/10/28 10:16:41
Modified:src/plugins-build/artifact plugin.jelly
Log:
Remove unnecessary pom.getPluginContext stuff
Revision ChangesPath
1.3 +5 -18 maven/src/plugins-build/artifact/plugin.jelly
Index: plugin.jelly
dion2003/10/28 10:17:59
Modified:src/plugins-build/caller plugin.jelly
Log:
Remove unnecessary pom.getPluginContext stuff
Revision ChangesPath
1.2 +1 -1 maven/src/plugins-build/caller/plugin.jelly
Index: plugin.jelly
dion2003/10/28 10:18:26
Modified:src/plugins-build/changelog/src/main/org/apache/maven/cvslib
CvsConnection.java
Log:
Style
Revision ChangesPath
1.2 +50 -58
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Tue, 28 Oct 2003 12:44 PM
Added the tag today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-950
Here is
dion2003/10/28 10:20:58
Modified:src/plugins-build/developer-activity plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.12 +3 -3 maven/src/plugins-build/developer-activity/plugin.jelly
Index: plugin.jelly
-Original Message-
From: Dominik Roblek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 3:58 PM
To: [EMAIL PROTECTED]
Subject: deploy and artifact plugins
I'm pretty confused when looking at artifact and
deploy plugins. It seems to me, that they offer very
similar
I've successfully setup an in-house remote repository along with a
central Maven distribution provided via our source control system. At
this time, I can update a jar in the maven distribution's plugin folder,
and then when someone runs a build, they'll get the latest version
installed if they
I've successfully setup an in-house remote repository along
with a central Maven distribution provided via our source
control system. At this time, I can update a jar in the
maven distribution's plugin folder, and then when someone
runs a build, they'll get the latest version installed
Brett Porter [EMAIL PROTECTED] wrote on 29/10/2003 09:12:31 AM:
The downside of plugin:download is that it doesn't clear out every
user's
local plugin cache, so they end up with multiple versions when they
change.
The recent code changes I've made that are currently uncommitted will
only
dion2003/10/28 14:18:47
Modified:src/plugins-build/file-activity plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.12 +2 -2 maven/src/plugins-build/file-activity/plugin.jelly
Index: plugin.jelly
dion2003/10/28 14:19:59
Modified:src/plugins-build/jar plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.22 +1 -1 maven/src/plugins-build/jar/plugin.jelly
Index: plugin.jelly
dion2003/10/28 14:22:01
Modified:src/plugins-build/junit-report plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.9 +3 -3 maven/src/plugins-build/junit-report/plugin.jelly
Index: plugin.jelly
dion2003/10/28 14:23:54
Modified:src/plugins-build/jxr plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.18 +5 -10 maven/src/plugins-build/jxr/plugin.jelly
Index: plugin.jelly
dion2003/10/28 14:25:19
Modified:src/plugins-build/linkcheck plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.13 +4 -4 maven/src/plugins-build/linkcheck/plugin.jelly
Index: plugin.jelly
dion2003/10/28 14:26:07
Modified:src/plugins-build/vdoclet project.properties
Log:
allow maven site -DpluginSite=y to work
Revision ChangesPath
1.5 +1 -0 maven/src/plugins-build/vdoclet/project.properties
Index: project.properties
dion2003/10/28 14:27:03
Modified:src/plugins-build/xdoc plugin.jelly
Log:
Start using tag instead of ${pom.getPluginContext()}
Revision ChangesPath
1.52 +13 -17maven/src/plugins-build/xdoc/plugin.jelly
Index: plugin.jelly
I've successfully setup an in-house remote repository along with a
central Maven distribution provided via our source control
system. At
this time, I can update a jar in the maven distribution's plugin
folder, and then when someone runs a build, they'll get the latest
version
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-976
Here is an overview of the issue:
Any way to make it automatically download the latest? Or
would that be a snapshot?
Exactly.
It won't go out to the internet to get them unless they are listed in
maven.repo.remote.
- Brett
The following comment has been added to this issue:
Author: Jason Horne
Created: Tue, 28 Oct 2003 5:52 PM
Body:
Julien,
I've only installed and used Maven on this one machine, so I unfortunately don't have
any other experiences to share. :-P
At some point, though, I did
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-977
Here is an overview of the issue:
Last 500 lines of a clean bootstrap build of maven at 20031028-2200
[exec] +
[exec] build:
[exec] [echo] D succeeds on purpose
[exec] [echo] failure-1 failed correctly
[exec] [echo] failure-2 failed correctly
[exec
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 29 Oct 2003 12:21 AM
Already fixed in cvs.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-976
34 matches
Mail list logo
