[jira] Created: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
Add ability to attach generated .sar to the project, even if classifier is not specifed
--------------------------------------------------------------------------------------- Key: MJBOSSPACK-32 URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 Project: Maven 2.x JBoss Packaging Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Elias Ross I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>foo-proj</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jboss-packaging-maven-plugin</artifactId> <version>2.1</version> <executions> <execution> <goals> <goal>sar</goal> </goals> </execution> </executions> <configuration> <primaryArtifact>false</primaryArtifact> <excludeAll>true</excludeAll> </configuration> </plugin> </plugins> </build> However, this does not "install" the plugin, e.g. by calling "mvn install" you get: [INFO] [jar:jar] [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar [INFO] [jboss-packaging:sar {execution: add-package}] [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar [INFO] [install:install] [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Updated: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MJBOSSPACK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Ross updated MJBOSSPACK-32: --------------------------------- Attachment: patch.diff Patch for functionality requested. Not sure how to test this but works for me. > Add ability to attach generated .sar to the project, even if classifier is not specifed > --------------------------------------------------------------------------------------- > > Key: MJBOSSPACK-32 > URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 > Project: Maven 2.x JBoss Packaging Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Elias Ross > Attachments: patch.diff > > > I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.example</groupId> > <artifactId>foo-proj</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>jar</packaging> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <version>2.1</version> > <executions> > <execution> > <goals> > <goal>sar</goal> > </goals> > </execution> > </executions> > <configuration> > <primaryArtifact>false</primaryArtifact> > <excludeAll>true</excludeAll> > </configuration> > </plugin> > </plugins> > </build> > However, this does not "install" the plugin, e.g. by calling "mvn install" you get: > [INFO] [jar:jar] > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar > [INFO] [jboss-packaging:sar {execution: add-package}] > [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar > [INFO] [install:install] > [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... > To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Updated: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MJBOSSPACK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MJBOSSPACK-32: -------------------------------- Description: I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>foo-proj</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jboss-packaging-maven-plugin</artifactId> <version>2.1</version> <executions> <execution> <goals> <goal>sar</goal> </goals> </execution> </executions> <configuration> <primaryArtifact>false</primaryArtifact> <excludeAll>true</excludeAll> </configuration> </plugin> </plugins> </build> However, this does not "install" the plugin, e.g. by calling "mvn install" you get: [INFO] [jar:jar] [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar [INFO] [jboss-packaging:sar {execution: add-package}] [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar [INFO] [install:install] [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... To attach, you can obviously include the "classifier" but I don't see the need for this. was: I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>foo-proj</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jboss-packaging-maven-plugin</artifactId> <version>2.1</version> <executions> <execution> <goals> <goal>sar</goal> </goals> </execution> </executions> <configuration> <primaryArtifact>false</primaryArtifact> <excludeAll>true</excludeAll> </configuration> </plugin> </plugins> </build> However, this does not "install" the plugin, e.g. by calling "mvn install" you get: [INFO] [jar:jar] [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar [INFO] [jboss-packaging:sar {execution: add-package}] [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar [INFO] [install:install] [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... To attach, you can obviously include the "classifier" but I don't see the need for this. Fix Version/s: 2.2 > Add ability to attach generated .sar to the project, even if classifier is not specifed > --------------------------------------------------------------------------------------- > > Key: MJBOSSPACK-32 > URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 > Project: Maven 2.x JBoss Packaging Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Elias Ross > Fix For: 2.2 > > Attachments: patch.diff > > > I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.example</groupId> > <artifactId>foo-proj</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>jar</packaging> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <version>2.1</version> > <executions> > <execution> > <goals> > <goal>sar</goal> > </goals> > </execution> > </executions> > <configuration> > <primaryArtifact>false</primaryArtifact> > <excludeAll>true</excludeAll> > </configuration> > </plugin> > </plugins> > </build> > However, this does not "install" the plugin, e.g. by calling "mvn install" you get: > [INFO] [jar:jar] > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar > [INFO] [jboss-packaging:sar {execution: add-package}] > [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar > [INFO] [install:install] > [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... > To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Assigned: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MJBOSSPACK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier reassigned MJBOSSPACK-32: ----------------------------------- Assignee: Paul Gier > Add ability to attach generated .sar to the project, even if classifier is not specifed > --------------------------------------------------------------------------------------- > > Key: MJBOSSPACK-32 > URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 > Project: Maven 2.x JBoss Packaging Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Elias Ross > Assignee: Paul Gier > Fix For: 2.2 > > Attachments: patch.diff > > > I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.example</groupId> > <artifactId>foo-proj</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>jar</packaging> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <version>2.1</version> > <executions> > <execution> > <goals> > <goal>sar</goal> > </goals> > </execution> > </executions> > <configuration> > <primaryArtifact>false</primaryArtifact> > <excludeAll>true</excludeAll> > </configuration> > </plugin> > </plugins> > </build> > However, this does not "install" the plugin, e.g. by calling "mvn install" you get: > [INFO] [jar:jar] > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar > [INFO] [jboss-packaging:sar {execution: add-package}] > [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar > [INFO] [install:install] > [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... > To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MJBOSSPACK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197269#action_197269 ] Paul Gier commented on MJBOSSPACK-32: ------------------------------------- Instead of adding the extra parameter, the plugin now automatically attaches an artifact that is not the primary project artifact. Does that work for you? This is fixed in [r11091|http://fisheye.codehaus.org/changelog/mojo/trunk/mojo?cs=11091]. > Add ability to attach generated .sar to the project, even if classifier is not specifed > --------------------------------------------------------------------------------------- > > Key: MJBOSSPACK-32 > URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 > Project: Maven 2.x JBoss Packaging Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Elias Ross > Fix For: 2.2 > > Attachments: patch.diff > > > I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.example</groupId> > <artifactId>foo-proj</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>jar</packaging> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <version>2.1</version> > <executions> > <execution> > <goals> > <goal>sar</goal> > </goals> > </execution> > </executions> > <configuration> > <primaryArtifact>false</primaryArtifact> > <excludeAll>true</excludeAll> > </configuration> > </plugin> > </plugins> > </build> > However, this does not "install" the plugin, e.g. by calling "mvn install" you get: > [INFO] [jar:jar] > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar > [INFO] [jboss-packaging:sar {execution: add-package}] > [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar > [INFO] [install:install] > [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... > To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Closed: (MJBOSSPACK-32) Add ability to attach generated .sar to the project, even if classifier is not specifed
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MJBOSSPACK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier closed MJBOSSPACK-32. ------------------------------- Resolution: Fixed > Add ability to attach generated .sar to the project, even if classifier is not specifed > --------------------------------------------------------------------------------------- > > Key: MJBOSSPACK-32 > URL: http://jira.codehaus.org/browse/MJBOSSPACK-32 > Project: Maven 2.x JBoss Packaging Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Elias Ross > Assignee: Paul Gier > Fix For: 2.1.1 > > Attachments: patch.diff > > > I have an artifact that's primarily a .sar file but is used by other projects as a .jar dependency. Thus I have the following configuration: > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.example</groupId> > <artifactId>foo-proj</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>jar</packaging> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-packaging-maven-plugin</artifactId> > <version>2.1</version> > <executions> > <execution> > <goals> > <goal>sar</goal> > </goals> > </execution> > </executions> > <configuration> > <primaryArtifact>false</primaryArtifact> > <excludeAll>true</excludeAll> > </configuration> > </plugin> > </plugins> > </build> > However, this does not "install" the plugin, e.g. by calling "mvn install" you get: > [INFO] [jar:jar] > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar > [INFO] [jboss-packaging:sar {execution: add-package}] > [INFO] Assembling JBoss packaging foo-proj in c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT > [INFO] Building jar: c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.sar > [INFO] [install:install] > [INFO] Installing c:\src\workspace\foo\proj\target\foo-proj-1.0-SNAPSHOT.jar to ... > To attach, you can obviously include the "classifier" but I don't see the need for this. -- 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 from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
