Attached artifacts are transformed to be of same type as the main artifact .
----------------------------------------------------------------------------
Key: MNG-1597
URL: http://jira.codehaus.org/browse/MNG-1597
Project: Maven 2
Type: Bug
Components: maven-artifact
Versions: 2.0
Environment: Maven 2.0 on windows XP
Reporter: Olivier Berlanger
In my project I defined, for example, source assembly like following:
...
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.0</version>
<configuration>
<descriptorId>src</descriptorId>
</configuration>
</plugin>
...
When I try to install the sources in my local repository using following
command:
mvn assembly:assembly install:install
The sources assembly are correclty generated in my target directory, but when
they are installed as attached artifacts they are renamed and transformed to be
of the same type as the main artifact.
You can clearly see it in the install:install log info:
[INFO] [assembly:assembly]
[INFO] Building tar :
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.tar.gz
[INFO] Building tar :
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.tar.bz2
[INFO] Building zip:
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.zip
[INFO]
----------------------------------------------------------------------------
[INFO] Building Tiny Workflow - Core
[INFO] task-segment: [install:install]
[INFO]
----------------------------------------------------------------------------
[INFO] [install:install]
[INFO] Installing
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT.jar
to
C:\Development\Maven2Repository\org\tinyWorkflow\TinyWorkflow-Core\1.0-SNAPSHOT\TinyWorkflow-Core-1.0-SNAPSHOT.jar
[INFO] Installing
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.tar.gz
to
C:\Development\Maven2Repository\org\tinyWorkflow\TinyWorkflow-Core\1.0-SNAPSHOT\TinyWorkflow-Core-1.0-SNAPSHOT-src.jar
[INFO] Installing
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.tar.bz2
to
C:\Development\Maven2Repository\org\tinyWorkflow\TinyWorkflow-Core\1.0-SNAPSHOT\TinyWorkflow-Core-1.0-SNAPSHOT-src.jar
[INFO] Installing
C:\Development\Theseos\TinyWorkflow-Core\trunk\target\TinyWorkflow-Core-1.0-SNAPSHOT-src.zip
to
C:\Development\Maven2Repository\org\tinyWorkflow\TinyWorkflow-Core\1.0-SNAPSHOT\TinyWorkflow-Core-1.0-SNAPSHOT-src.jar
The problem is that the 3 sources files (zip, tar.gz, tra.bz2) are renamed with
the same name, so they are overwritten in the repository.
In addition they are transformed to be a jar but they are not valid jar files
(because they have no manifest).
The problem is worse when your main artifact type is war because then
everything is transformed to .war files (and eclipse refuse to link sources
from a war).
It seems to be a general problem of the attached artifacts because you have the
same behavior when you build attached artifacts with jar:jar.
In general the secondary artifacts (sources, bundles ... ) are not of the same
type as the main artifact.
In particular for our projects exporting a War or a Ear, we need to have a
secondary artifact that is a jar file with only complied classes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
