You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tim Meighen (JIRA)" <ji...@codehaus.org> on 2007/02/20 03:07:52 UTC
[jira] Created: (MEJB-25) Classifiers do not work during deploy
phase
Classifiers do not work during deploy phase
-------------------------------------------
Key: MEJB-25
URL: http://jira.codehaus.org/browse/MEJB-25
Project: Maven 2.x Ejb Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Tim Meighen
Attachments: classifier-test.tar.gz
Classifiers work fine during a mvn install, but during mvn deploy the build fails. I believe that this is due to the artifact being added as an attachment without building the "non-classifier" version (i.e. there is no artifact defined).
I've attached a sample project to demonstrate. You will need to fill in the URL to your snapshot repo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEJB-25) Classifiers do not work during deploy
phase
Posted by "Tim Meighen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88000 ]
Tim Meighen commented on MEJB-25:
---------------------------------
Here's the output from a "mvn deploy":
[INFO]------------------------------------------------------------------------
[ERROR]BUILD ERROR
[INFO]------------------------------------------------------------------------
[INFO]Error deploying artifact: /Users/tmeighen/classifier-test/target/classes (No such file or directory)
[INFO]------------------------------------------------------------------------
[INFO]Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: /Users/tmeighen/classifier-test/target/classes (No such file or directory)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:635)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)
at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:257)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying artifact: /Users/tmeighen/classifier-test/target/classes (No such file or directory)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610)
... 10 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: /Users/tmeighen/classifier-test/target/classes (No such file or directory)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:95)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
... 12 more
Caused by: java.io.FileNotFoundException: /Users/tmeighen/classifier-test/target/classes (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:820)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:74)
... 13 more
[INFO]------------------------------------------------------------------------
[INFO]Total time: 2 seconds
[INFO]Finished at: Mon Feb 19 18:02:21 PST 2007
[INFO]Final Memory: 63M/115M
[INFO]------------------------------------------------------------------------
> Classifiers do not work during deploy phase
> -------------------------------------------
>
> Key: MEJB-25
> URL: http://jira.codehaus.org/browse/MEJB-25
> Project: Maven 2.x Ejb Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Tim Meighen
> Attachments: classifier-test.tar.gz
>
>
> Classifiers work fine during a mvn install, but during mvn deploy the build fails. I believe that this is due to the artifact being added as an attachment without building the "non-classifier" version (i.e. there is no artifact defined).
> I've attached a sample project to demonstrate. You will need to fill in the URL to your snapshot repo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEJB-25) Classifiers do not work during deploy
phase
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MEJB-25.
-------------------------------
Resolution: Won't Fix
See issue in the deploy plugin.
> Classifiers do not work during deploy phase
> -------------------------------------------
>
> Key: MEJB-25
> URL: http://jira.codehaus.org/browse/MEJB-25
> Project: Maven 2.x Ejb Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Tim Meighen
> Attachments: classifier-test.tar.gz
>
>
> Classifiers work fine during a mvn install, but during mvn deploy the build fails. I believe that this is due to the artifact being added as an attachment without building the "non-classifier" version (i.e. there is no artifact defined).
> I've attached a sample project to demonstrate. You will need to fill in the URL to your snapshot repo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira