Re: building and installing a source only jar
You could do this with the install-file [1] goal of the maven install plugin :) -Deng [1] http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html EJ Ciramella wrote: Ok, maybe I'm wrong - what's the easiest way to install this source jar in your local repository? Say the developer doesn't have the actual source from perforce -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 10:56 AM To: Maven Users List Subject: RE: building and installing a source only jar And use the -DuniqueVersion=false - I'm all set! Thanks Tim! -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 10:50 AM To: Maven Users List Subject: Re: building and installing a source only jar Hi, try adding the classifier property: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dclassifier=sources -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false -Tim EJ Ciramella schrieb: Yep, I found the source:jar plugin just moments after sending my original email. The problem I have now is when I install to our internal remote repository using the following command, I have two problems: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false 1 - It's changing the name of the jar file, I'd like to keep the name as shown above: Uploading: file:\\build.corp.upromise.com\maven2/lty/lty-utils/1.0-SNAPSHOT/lty-uti ls-1.0-20070815.142846-2.jar Why won't it keep "sources" in the name. 2 - How do I control the version number at deploy time? We'd like to do something similar to what repo1 has/does where the sources are sitting next to the actual binary versions. -Original Message- From: Maria Odea Ching [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 2:57 AM To: Maven Users List Subject: Re: building and installing a source only jar EJ Ciramella wrote: Is there any way to build a source only jar and install that to our internal remote repository? Try 'mvn source:jar install' for this, and.. We're trying to get more modular with our builds and would like to still allow eclipse users to hop to the source of a particular dependency. Even after I'm able to build a source only jar, is there an easy way to get that down loaded? 'mvn eclipse:eclipse -DdownloadSources=true' HTH, Deng - 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] - 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] - 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]
RE: building and installing a source only jar
Ok, maybe I'm wrong - what's the easiest way to install this source jar in your local repository? Say the developer doesn't have the actual source from perforce -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 10:56 AM To: Maven Users List Subject: RE: building and installing a source only jar And use the -DuniqueVersion=false - I'm all set! Thanks Tim! -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 10:50 AM To: Maven Users List Subject: Re: building and installing a source only jar Hi, try adding the classifier property: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dclassifier=sources -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false -Tim EJ Ciramella schrieb: > Yep, I found the source:jar plugin just moments after sending my > original email. > > The problem I have now is when I install to our internal remote > repository using the following command, I have two problems: > > mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils > -Dpackaging=jar -Dversion=1.0-SNAPSHOT > -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central > -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false > > 1 - It's changing the name of the jar file, I'd like to keep the name as > shown above: > > Uploading: > file:\\build.corp.upromise.com\maven2/lty/lty-utils/1.0-SNAPSHOT/lty-uti > ls-1.0-20070815.142846-2.jar > > Why won't it keep "sources" in the name. > > 2 - How do I control the version number at deploy time? > > > We'd like to do something similar to what repo1 has/does where the > sources are sitting next to the actual binary versions. > > -Original Message- > From: Maria Odea Ching [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 15, 2007 2:57 AM > To: Maven Users List > Subject: Re: building and installing a source only jar > > EJ Ciramella wrote: >> Is there any way to build a source only jar and install that to our >> internal remote repository? >> > > Try 'mvn source:jar install' for this, and.. > >> >> We're trying to get more modular with our builds and would like to > still >> allow eclipse users to hop to the source of a particular dependency. >> >> Even after I'm able to build a source only jar, is there an easy way > to >> get that down loaded? >> >> > > 'mvn eclipse:eclipse -DdownloadSources=true' > > > HTH, > Deng > > - > 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: building and installing a source only jar
On 8/15/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > Yep, I found the source:jar plugin just moments after sending my > original email. > > The problem I have now is when I install to our internal remote > repository using the following command, I have two problems: > > mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils > -Dpackaging=jar -Dversion=1.0-SNAPSHOT > -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central > -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false Consider configuring so that 'mvn deploy ...' will deploy snapshots without this extra step. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: building and installing a source only jar
And use the -DuniqueVersion=false - I'm all set! Thanks Tim! -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 10:50 AM To: Maven Users List Subject: Re: building and installing a source only jar Hi, try adding the classifier property: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dclassifier=sources -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false -Tim EJ Ciramella schrieb: > Yep, I found the source:jar plugin just moments after sending my > original email. > > The problem I have now is when I install to our internal remote > repository using the following command, I have two problems: > > mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils > -Dpackaging=jar -Dversion=1.0-SNAPSHOT > -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central > -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false > > 1 - It's changing the name of the jar file, I'd like to keep the name as > shown above: > > Uploading: > file:\\build.corp.upromise.com\maven2/lty/lty-utils/1.0-SNAPSHOT/lty-uti > ls-1.0-20070815.142846-2.jar > > Why won't it keep "sources" in the name. > > 2 - How do I control the version number at deploy time? > > > We'd like to do something similar to what repo1 has/does where the > sources are sitting next to the actual binary versions. > > -Original Message- > From: Maria Odea Ching [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 15, 2007 2:57 AM > To: Maven Users List > Subject: Re: building and installing a source only jar > > EJ Ciramella wrote: >> Is there any way to build a source only jar and install that to our >> internal remote repository? >> > > Try 'mvn source:jar install' for this, and.. > >> >> We're trying to get more modular with our builds and would like to > still >> allow eclipse users to hop to the source of a particular dependency. >> >> Even after I'm able to build a source only jar, is there an easy way > to >> get that down loaded? >> >> > > 'mvn eclipse:eclipse -DdownloadSources=true' > > > HTH, > Deng > > - > 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] - 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]
Re: building and installing a source only jar
Hi, try adding the classifier property: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dclassifier=sources -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false -Tim EJ Ciramella schrieb: Yep, I found the source:jar plugin just moments after sending my original email. The problem I have now is when I install to our internal remote repository using the following command, I have two problems: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false 1 - It's changing the name of the jar file, I'd like to keep the name as shown above: Uploading: file:\\build.corp.upromise.com\maven2/lty/lty-utils/1.0-SNAPSHOT/lty-uti ls-1.0-20070815.142846-2.jar Why won't it keep "sources" in the name. 2 - How do I control the version number at deploy time? We'd like to do something similar to what repo1 has/does where the sources are sitting next to the actual binary versions. -Original Message- From: Maria Odea Ching [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 2:57 AM To: Maven Users List Subject: Re: building and installing a source only jar EJ Ciramella wrote: Is there any way to build a source only jar and install that to our internal remote repository? Try 'mvn source:jar install' for this, and.. We're trying to get more modular with our builds and would like to still allow eclipse users to hop to the source of a particular dependency. Even after I'm able to build a source only jar, is there an easy way to get that down loaded? 'mvn eclipse:eclipse -DdownloadSources=true' HTH, Deng - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: building and installing a source only jar
Yep, I found the source:jar plugin just moments after sending my original email. The problem I have now is when I install to our internal remote repository using the following command, I have two problems: mvn deploy:deploy-file -DgroupId=lty -DartifactId=lty-utils -Dpackaging=jar -Dversion=1.0-SNAPSHOT -Dfile=lty-utils-1.0-SNAPSHOT-sources.jar -DrepositoryId=central -Durl=file:\\build.corp.upromise.com\maven2 -Dgeneratepom=false 1 - It's changing the name of the jar file, I'd like to keep the name as shown above: Uploading: file:\\build.corp.upromise.com\maven2/lty/lty-utils/1.0-SNAPSHOT/lty-uti ls-1.0-20070815.142846-2.jar Why won't it keep "sources" in the name. 2 - How do I control the version number at deploy time? We'd like to do something similar to what repo1 has/does where the sources are sitting next to the actual binary versions. -Original Message- From: Maria Odea Ching [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 2:57 AM To: Maven Users List Subject: Re: building and installing a source only jar EJ Ciramella wrote: > Is there any way to build a source only jar and install that to our > internal remote repository? > Try 'mvn source:jar install' for this, and.. > > We're trying to get more modular with our builds and would like to still > allow eclipse users to hop to the source of a particular dependency. > > Even after I'm able to build a source only jar, is there an easy way to > get that down loaded? > > 'mvn eclipse:eclipse -DdownloadSources=true' HTH, Deng - 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]
Re: building and installing a source only jar
EJ Ciramella wrote: Is there any way to build a source only jar and install that to our internal remote repository? Try 'mvn source:jar install' for this, and.. We're trying to get more modular with our builds and would like to still allow eclipse users to hop to the source of a particular dependency. Even after I'm able to build a source only jar, is there an easy way to get that down loaded? 'mvn eclipse:eclipse -DdownloadSources=true' HTH, Deng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: building and installing a source only jar
Hi, have a look at the maven-source-plugin[1] and possibly the maven-javadoc-plugin[2] and configure the maven-eclipse-plugin as shown here [3]. -Tim [1] http://maven.apache.org/plugins/maven-source-plugin/ [2] http://maven.apache.org/plugins/maven-javadoc-plugin/ [3] http://maven.apache.org/plugins/maven-eclipse-plugin/examples/attach-library-sources.html EJ Ciramella schrieb: Is there any way to build a source only jar and install that to our internal remote repository? We're trying to get more modular with our builds and would like to still allow eclipse users to hop to the source of a particular dependency. Even after I'm able to build a source only jar, is there an easy way to get that down loaded? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
