thanks, that fixed it.

The problem I now have is that I'm deploying artifacts of type 'example' which are zip files.

Deploying: D:\codeczar\maven-ejbgen-plugin\target\maven-ejbgen-plugin-1.0-example.zip-->codeczar/exa
mples/maven-ejbgen-plugin-1.0.example


so, my filename
maven-ejbgen-plugin-1.0-example.zip
gets changed to
maven-ejbgen-plugin-1.0.example

Found the code in DefaultArtifactDeployer:

/**
* Return file extension for given type
* @todo Dirty hack Repository Layout Service from maven-new should be used
* @return extension for given type
*/
private String extensionForType(String type)
{
if (type.equals("ejb"))
{
return "jar";
}
else if (type.equals("plugin"))
{
return "jar";
}
else if (type.equals("uberjar"))
{
return "jar";
}
return type;
}


Is there a workaround for this? I'm not sure I follow the reasoning for why you'd need to change the extension when deploying? isn't that left to the plugin that created the artifact? war, ejb, jar, ear etc? I guess it's not a problem to have zip files with a .example extension as long as they're to be accessed programatically, but I was thinking of having links to my 'example' artifacts so they could be downloaded.

thanks
Nathan


Maczka Michal wrote:


-----Original Message-----
From: Nathan Coast [mailto:[EMAIL PROTECTED]
Sent: Friday, May 28, 2004 3:05 PM
To: Maven Users
Subject: deploy:artifact confusion


Hi,

I have some code in a plugin:



There are two plugins artifact plugin an ddeploy plugin which are mostly
overlapping.

This is using deploy plugin:


<deploy:artifact artifact="${maven.build.dir}/${maven.final.name}-example.zip"
type="example"
assureDirectoryCommand="mkdir -p"
siteCommand="cd @deployDirectory@;chmod -R g+u *;"
/>


I placed the following in build.properties



Those are settings for artifact plugin


maven.repo.list=R1

#settings for repository 'R1'
maven.repo.R1=ftp://ftp.codeczar.com
maven.repo.R1.username=*********
maven.repo.R1.password=*********
maven.repo.R1.directory=/usr/ngasi/contexts/codeczar/codeczar/maven



[...]

I know this is very confusing - but soon it will be unified (after 1.0
release)

Michal

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to