You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emanuel Bulic (JIRA)" <ji...@codehaus.org> on 2006/04/26 20:41:19 UTC
[jira] Created: (MNG-2240) Handling of custom lifecycle artifacts
is not working properly
Handling of custom lifecycle artifacts is not working properly
--------------------------------------------------------------
Key: MNG-2240
URL: http://jira.codehaus.org/browse/MNG-2240
Project: Maven 2
Type: Bug
Components: Artifacts and Repositories, Artifacts
Versions: 2.0.4
Reporter: Emanuel Bulic
Priority: Blocker
Attachments: output1.txt, pom.xml
I am using a custom lifecycle, resource, as follows:
<component>
<role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
<role-hint>resource</role-hint>
<implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
<configuration>
<phases>
<process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
<package>org.apache.maven.plugins:maven-jar-plugin:jar</package>
<install>org.apache.maven.plugins:maven-install-plugin:install,com.dcx.NGST:maven-bundle-plugin:install</install>
<deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
</phases>
</configuration>
</component>
<component>
<role>org.apache.maven.artifact.handler.ArtifactHandler</role>
<role-hint>resource</role-hint>
<implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
<configuration>
<extension>jar</extension>
<type>resource</type>
<packaging>resource</packaging>
<language>java</language>
<addedToClasspath>true</addedToClasspath>
</configuration>
</component>
I have a pom structure that looks like this:
app\data\production\ecuDB\ABS\01\pom.xml
app\data\production\ecuDB\ABS\02\pom.xml
app\data\production\ecuDB\ABS\03\pom.xml
app\data\production\ecuDB\ABS\04\pom.xml
app\data\production\ecuDB\ABS\05\pom.xml
app\data\production\ecuDB\ABS\06\pom.xml
app\data\production\ecuDB\ABS\07\pom.xml
Each folder in the structure contains a pom type, and references the child modules; 0X are resource type artifacts as defined above. I attached the text output of maven install on one of the resource projects, namely 01, followed by 'cd ..' and maven install on all ABS modules. Comparing the 2 runs, you will find that the 01 resource artifact has been installed with different extensions. It uses the correct .jar extension on the first run, but it defaults to .resource when build as a multiproject. It appears that the component definition isn't available, and it defaults the extension to the type value
I am also going to attach the 01/pom.xml
--
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] Updated: (MNG-2240) Handling of custom lifecycle artifacts
is not working properly
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2240:
------------------------------
Component/s: (was: Artifacts)
> Handling of custom lifecycle artifacts is not working properly
> --------------------------------------------------------------
>
> Key: MNG-2240
> URL: http://jira.codehaus.org/browse/MNG-2240
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Emanuel Bulic
> Assignee: Carlos Sanchez
> Priority: Blocker
> Attachments: output1.txt, pom.xml
>
>
> I am using a custom lifecycle, resource, as follows:
> <component>
> <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
> <configuration>
> <phases>
> <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
> <package>org.apache.maven.plugins:maven-jar-plugin:jar</package>
> <install>org.apache.maven.plugins:maven-install-plugin:install,com.dcx.NGST:maven-bundle-plugin:install</install>
> <deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
> </phases>
> </configuration>
> </component>
> <component>
> <role>org.apache.maven.artifact.handler.ArtifactHandler</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
> <configuration>
> <extension>jar</extension>
> <type>resource</type>
> <packaging>resource</packaging>
> <language>java</language>
> <addedToClasspath>true</addedToClasspath>
> </configuration>
> </component>
> I have a pom structure that looks like this:
> app\data\production\ecuDB\ABS\01\pom.xml
> app\data\production\ecuDB\ABS\02\pom.xml
> app\data\production\ecuDB\ABS\03\pom.xml
> app\data\production\ecuDB\ABS\04\pom.xml
> app\data\production\ecuDB\ABS\05\pom.xml
> app\data\production\ecuDB\ABS\06\pom.xml
> app\data\production\ecuDB\ABS\07\pom.xml
> Each folder in the structure contains a pom type, and references the child modules; 0X are resource type artifacts as defined above. I attached the text output of maven install on one of the resource projects, namely 01, followed by 'cd ..' and maven install on all ABS modules. Comparing the 2 runs, you will find that the 01 resource artifact has been installed with different extensions. It uses the correct .jar extension on the first run, but it defaults to .resource when build as a multiproject. It appears that the component definition isn't available, and it defaults the extension to the type value
> I am also going to attach the 01/pom.xml
--
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: (MNG-2240) Handling of custom lifecycle artifacts is
not working properly
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MNG-2240.
-------------------------------
Assignee: Carlos Sanchez
Resolution: Duplicate
Fix Version/s: (was: 2.1.x)
> Handling of custom lifecycle artifacts is not working properly
> --------------------------------------------------------------
>
> Key: MNG-2240
> URL: http://jira.codehaus.org/browse/MNG-2240
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts, Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Emanuel Bulic
> Assigned To: Carlos Sanchez
> Priority: Blocker
> Attachments: output1.txt, pom.xml
>
>
> I am using a custom lifecycle, resource, as follows:
> <component>
> <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
> <configuration>
> <phases>
> <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
> <package>org.apache.maven.plugins:maven-jar-plugin:jar</package>
> <install>org.apache.maven.plugins:maven-install-plugin:install,com.dcx.NGST:maven-bundle-plugin:install</install>
> <deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
> </phases>
> </configuration>
> </component>
> <component>
> <role>org.apache.maven.artifact.handler.ArtifactHandler</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
> <configuration>
> <extension>jar</extension>
> <type>resource</type>
> <packaging>resource</packaging>
> <language>java</language>
> <addedToClasspath>true</addedToClasspath>
> </configuration>
> </component>
> I have a pom structure that looks like this:
> app\data\production\ecuDB\ABS\01\pom.xml
> app\data\production\ecuDB\ABS\02\pom.xml
> app\data\production\ecuDB\ABS\03\pom.xml
> app\data\production\ecuDB\ABS\04\pom.xml
> app\data\production\ecuDB\ABS\05\pom.xml
> app\data\production\ecuDB\ABS\06\pom.xml
> app\data\production\ecuDB\ABS\07\pom.xml
> Each folder in the structure contains a pom type, and references the child modules; 0X are resource type artifacts as defined above. I attached the text output of maven install on one of the resource projects, namely 01, followed by 'cd ..' and maven install on all ABS modules. Comparing the 2 runs, you will find that the 01 resource artifact has been installed with different extensions. It uses the correct .jar extension on the first run, but it defaults to .resource when build as a multiproject. It appears that the component definition isn't available, and it defaults the extension to the type value
> I am also going to attach the 01/pom.xml
--
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] Updated: (MNG-2240) Handling of custom lifecycle artifacts
is not working properly
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2240?page=all ]
John Casey updated MNG-2240:
----------------------------
Fix Version: 2.1
> Handling of custom lifecycle artifacts is not working properly
> --------------------------------------------------------------
>
> Key: MNG-2240
> URL: http://jira.codehaus.org/browse/MNG-2240
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories, Artifacts
> Versions: 2.0.4
> Reporter: Emanuel Bulic
> Priority: Blocker
> Fix For: 2.1
> Attachments: output1.txt, pom.xml
>
>
> I am using a custom lifecycle, resource, as follows:
> <component>
> <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
> <configuration>
> <phases>
> <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
> <package>org.apache.maven.plugins:maven-jar-plugin:jar</package>
> <install>org.apache.maven.plugins:maven-install-plugin:install,com.dcx.NGST:maven-bundle-plugin:install</install>
> <deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
> </phases>
> </configuration>
> </component>
> <component>
> <role>org.apache.maven.artifact.handler.ArtifactHandler</role>
> <role-hint>resource</role-hint>
> <implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
> <configuration>
> <extension>jar</extension>
> <type>resource</type>
> <packaging>resource</packaging>
> <language>java</language>
> <addedToClasspath>true</addedToClasspath>
> </configuration>
> </component>
> I have a pom structure that looks like this:
> app\data\production\ecuDB\ABS\01\pom.xml
> app\data\production\ecuDB\ABS\02\pom.xml
> app\data\production\ecuDB\ABS\03\pom.xml
> app\data\production\ecuDB\ABS\04\pom.xml
> app\data\production\ecuDB\ABS\05\pom.xml
> app\data\production\ecuDB\ABS\06\pom.xml
> app\data\production\ecuDB\ABS\07\pom.xml
> Each folder in the structure contains a pom type, and references the child modules; 0X are resource type artifacts as defined above. I attached the text output of maven install on one of the resource projects, namely 01, followed by 'cd ..' and maven install on all ABS modules. Comparing the 2 runs, you will find that the 01 resource artifact has been installed with different extensions. It uses the correct .jar extension on the first run, but it defaults to .resource when build as a multiproject. It appears that the component definition isn't available, and it defaults the extension to the type value
> I am also going to attach the 01/pom.xml
--
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