RE: cvs commit: maven/src/plugins-build/artifact/src/plugin-resources/templates manifest.vm
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 6:18 AM
To: [EMAIL PROTECTED]
Subject: Re: cvs commit: maven/src/plugins-build/artifact/src/plugin-
resources/templates manifest.vm
Generic code for:
- deployment of artifact to remote repositry
- installaton of artifact to local repository
This seems like code that is duplicating the repository and deploy
plugins. Why do we want a third way of doing this
This one is developed in pure Java + supports deployment to various types
of repositories. Soon it will support deployment to multiple repositories.
And I think it is easier to use it then other ones + the code is more
centralized. I hope to test it with junit. This was rather hard in case of
old plugins.
Can you please change the others to use this code if it works?
It is not yet fully finished. Once I will be sure that it works I am
planning to change other plugins.
For the moment I use war plugin as demonstration how this is supposed
to work from the point of other plugins, so if any body has some remarks...
let me know.
FYI:
package org.apache.maven.artifact.deployer.deploy;
is meant to be refactored. I think the best will be to make a sister
component of fetch in maven-new.
This code is not depending on any maven apis, and can be possibly reused
like does fetch component.
Package org.apache.maven.artifact.deployer;
Contains higher level API, which uses maven API and it is supposed to be
used in plugins.
[OT]
I am thinking about deploying java sources and javadocs to repository.
Any idea about naming convention of those artifacts? With maven-new it
will be easy to control, with maven-old it is not so easy.
I am thinking about:
/${groupId}/apis/${artitifactId}_api-${version}.jar (for javadocs)
/${groupId}/srcs/${artitifactId}_src-${version}.jar (for sources).
Any better ideas?
Other question is where is the best place for such functionality?
I think for javadoc it is javadoc plugin. But for sources?
Any hints what else can we deploy?
Other idea:
We have;
jar:jar
war:war
ear:ear
etc..
Wouldn't it be more consistent to have:
jar:archive
war:archive
ear:archive
javadoc:archive
java:src-archive
etc?
regards
Michal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact/src/plugin-resources/templates manifest.vm
michal 2003/06/16 07:26:02
Added: src/plugins-build/artifact project.properties
plugin.properties .cvsignore project.xml
plugin.jelly
src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer
MavenAuthenticationInfo.java
DefaultArtifactDeployer.java DeployBean.java
ArtifactDeployer.java
src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer/deploy
SshDeployer.java HttpDeployer.java
AbstractDeployer.java Deployer.java
GenericAuthenticationInfo.java
AuthenticationInfo.java FtpDeployer.java
src/plugins-build/artifact/src/plugin-resources/templates
manifest.vm
Log:
Generic code for:
- deployment of artifact to remote repositry
- installaton of artifact to local repository
- manifest generation
Revision ChangesPath
1.1 maven/src/plugins-build/artifact/project.properties
Index: project.properties
===
# ---
# P R O J E C T P R O P E R T I E S
# ---
1.1 maven/src/plugins-build/artifact/plugin.properties
Index: plugin.properties
===
# ---
# P L U G I N P R O P E R T I E S
# ---
maven.artifact.manifest.extensions.add=false
maven.artifact.manifest.basedir=${plugin.dir}/plugin-resources/templates
maven.artifact.manifest.template=manifest.vm
1.1 maven/src/plugins-build/artifact/.cvsignore
Index: .cvsignore
===
target
velocity.log
maven.log
1.1 maven/src/plugins-build/artifact/project.xml
Index: project.xml
===
?xml version=1.0 encoding=UTF-8?
project
extend${basedir}/../project.xml/extend
pomVersion3/pomVersion
idmaven-artifact-plugin/id
nameMaven Artifact Plug-in/name
currentVersion1.0/currentVersion
description/
shortDescriptionJava Project Management Tools/shortDescription
urlhttp://maven.apache.org/reference/plugins/artifact//url
siteDirectory/www/maven.apache.org/reference/plugins/artifact//siteDirectory
repository
connectionscm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:maven/src/plugins-build/artifact//connection
urlhttp://cvs.apache.org/viewcvs/maven/src/plugins-build/artifact//url
/repository
developers/
dependencies
dependency
groupIdmaven/groupId
artifactIdmaven/artifactId
versionSNAPSHOT/version
typejar/type
/dependency
dependency
groupIdcommons-io/groupId
artifactIdcommons-io/artifactId
version20030203.000550/version
typejar/type
/dependency
dependency
groupIdcommons-net/groupId
artifactIdcommons-net/artifactId
version1.0.0/version
typejar/type
/dependency
dependency
groupIdcommons-httpclient/groupId
artifactIdcommons-httpclient/artifactId
version2.0-beta1/version
typejar/type
/dependency
dependency
groupIdjsch/groupId
artifactIdjsch/artifactId
version0.0.9/version
typejar/type
/dependency
dependency
groupIdcommons-jelly/groupId
artifactIdcommons-jelly/artifactId
version20030310.073407/version
urlhttp://jakarta.apache.org/commons/jelly//url
typejar/type
/dependency
dependency
groupIdcommons-jelly/groupId
artifactIdcommons-jelly-tags-velocity/artifactId
version20030303.205659/version
typejar/type
/dependency
dependency
groupIdvelocity/groupId
artifactIdvelocity/artifactId
version1.3/version
typejar/type
/dependency
/dependencies
/project
1.1 maven/src/plugins-build/artifact/plugin.jelly
Index: plugin.jelly
===
?xml version=1.0?
project
xmlns:j=jelly:core
xmlns:define=jelly:define
xmlns:ant=jelly:ant
xmlns:velocity=jelly:velocity
define:taglib uri=artifact
!-- For times the same bean is used. --
