Re: Help for Maven Migration
I had trouble here. Can you provide an example of your CURL for artifactory? Is it generating the pom for you automatically? On Thu, Nov 7, 2013 at 3:43 AM, Andy wrote: > Also +1, I had 198 deps and did exactly this earlier this year in just a > morning using Artifactory API : http://www.jfrog.com/ > confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI- > DeployArtifact > > Andy. > > > On 06.11.2013 23:35, Ron Wheeler wrote: > >> +1. >> >> On 06/11/2013 3:57 PM, Wayne Fay wrote: >> >>> I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? >>> Most likely, no, you should not do this. >>> >>> Instead spend the time to match each Jar file up to an equivalent Jar >>> file deployed in Central. For Jars which do not exist in Central or >>> those with modified contents, you can consider uploading them to your >>> private Artifactory instead - but I would deploy under a GAV that >>> somehow specifies "this is our internal version of the artifact" so >>> you can keep track of them easily and hopefully get rid of them in >>> most instances in the future. >>> >>> Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the EASIEST way to generate the POM for the dependencies? Is there a single command that can do this? Is there a MVN command that will do this for me? >>> You only have 130 dependencies. This seems like a lot, but it honestly >>> is not. This is a 1-time job you need to perform and then you never >>> need to do it again. Find 1-2 days in your schedule and just start the >>> work - you will be done sooner than you realize. >>> >>> All other "solutions" to this problem have their own set of related >>> problems. You are simply kicking the can down the road a bit if you do >>> not complete this work today, and do it the right way. >>> >>> Wayne >>> >> ** > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Help for Maven Migration
Also +1, I had 198 deps and did exactly this earlier this year in just a morning using Artifactory API : http://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-DeployArtifact Andy. On 06.11.2013 23:35, Ron Wheeler wrote: +1. On 06/11/2013 3:57 PM, Wayne Fay wrote: I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? Most likely, no, you should not do this. Instead spend the time to match each Jar file up to an equivalent Jar file deployed in Central. For Jars which do not exist in Central or those with modified contents, you can consider uploading them to your private Artifactory instead - but I would deploy under a GAV that somehow specifies "this is our internal version of the artifact" so you can keep track of them easily and hopefully get rid of them in most instances in the future. Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the EASIEST way to generate the POM for the dependencies? Is there a single command that can do this? Is there a MVN command that will do this for me? You only have 130 dependencies. This seems like a lot, but it honestly is not. This is a 1-time job you need to perform and then you never need to do it again. Find 1-2 days in your schedule and just start the work - you will be done sooner than you realize. All other "solutions" to this problem have their own set of related problems. You are simply kicking the can down the road a bit if you do not complete this work today, and do it the right way. Wayne ** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help for Maven Migration
+1. On 06/11/2013 3:57 PM, Wayne Fay wrote: I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? Most likely, no, you should not do this. Instead spend the time to match each Jar file up to an equivalent Jar file deployed in Central. For Jars which do not exist in Central or those with modified contents, you can consider uploading them to your private Artifactory instead - but I would deploy under a GAV that somehow specifies "this is our internal version of the artifact" so you can keep track of them easily and hopefully get rid of them in most instances in the future. Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the EASIEST way to generate the POM for the dependencies? Is there a single command that can do this? Is there a MVN command that will do this for me? You only have 130 dependencies. This seems like a lot, but it honestly is not. This is a 1-time job you need to perform and then you never need to do it again. Find 1-2 days in your schedule and just start the work - you will be done sooner than you realize. All other "solutions" to this problem have their own set of related problems. You are simply kicking the can down the road a bit if you do not complete this work today, and do it the right way. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help for Maven Migration
> I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? Most likely, no, you should not do this. Instead spend the time to match each Jar file up to an equivalent Jar file deployed in Central. For Jars which do not exist in Central or those with modified contents, you can consider uploading them to your private Artifactory instead - but I would deploy under a GAV that somehow specifies "this is our internal version of the artifact" so you can keep track of them easily and hopefully get rid of them in most instances in the future. > Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the > EASIEST way to generate the POM for the dependencies? Is there a single > command that can do this? Is there a MVN command that will do this for me? You only have 130 dependencies. This seems like a lot, but it honestly is not. This is a 1-time job you need to perform and then you never need to do it again. Find 1-2 days in your schedule and just start the work - you will be done sooner than you realize. All other "solutions" to this problem have their own set of related problems. You are simply kicking the can down the road a bit if you do not complete this work today, and do it the right way. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help for Maven Migration
On 06/11/2013 2:46 PM, Manfred Moser wrote: Imho you should not just upload all the jars. Instead find out the exact version of what they are by doing a shasum of the jars and use the checksum search in Nexus or on Central to identify the jars. http://search.maven.org/#advancedsearch%7Cgav Only upload the ones you can not identify.. and even for those it might be better to upgrade to a known artifact version.. where you can manfred Once you have sorted out the known jars and added them as dependencies to your poms, you can make up poms for the other jars with arbitrary GAV designations and load them into your Maven repo and refer to them by the GAV that you specified. If you can safely combine jars (no overlapping files or classes inside them), then you could build composite jars and add them to your repo. This may become a headache if you ever find out what one jar contains and want to extract it out and upgrade it or patch a class. You will have to extract it out and then rebuild the composite jar with a new version 130 is pretty big but not a lot bigger than what we have but we know the ancestry of our jars which makes it a bit easier to manage. We combine a lot of jars into composite jars. This makes it a bit easier to control the versions of shared utilities since they are never included in our module poms by their own GAV. Once we decide what version of log4j we will use, we don't worry about getting an old one by mistake - takes a few "exclusions" to protect ourselves from third parties using old versions. You may have to be careful to make sure that your orphan jars do not conflict with libraries included in third party jars. If you don't know that you have an old log4j in your 130 jars, for example, you could cause a problem if you also depend on a library that needs the latest version of log4j - MethodNotFound at run-time. Ron I am trying to figure out the best way to migrate over and use Maven for Dependency Management. My question is : I have about 130 Jars in the Project we are a large project. I have Artifactory set up. SOme of the JARs I don't even have versions for as they have been around for years. A few we have even modified. I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? I have figured out for a single JAR I can deploy the artifact like so mvn deploy:deploy-file -e -Durl=http://repo.dotcms.com/artifactory/dotcms-DrepositoryId=dotcms -Dfile=Tidy.jar -Dversion=ukv -DgroupId=com.dotcms.lib -Dpackaging=jar -DartifactId=Tidy Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the EASIEST way to generate the POM for the dependencies? Is there a single command that can do this? Is there a MVN command that will do this for me? In the end I need a POM that people will point to that will have all the libs for compile time because they will be building plugins in our system - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help for Maven Migration
Imho you should not just upload all the jars. Instead find out the exact version of what they are by doing a shasum of the jars and use the checksum search in Nexus or on Central to identify the jars. http://search.maven.org/#advancedsearch%7Cgav Only upload the ones you can not identify.. and even for those it might be better to upgrade to a known artifact version.. where you can manfred > I am trying to figure out the best way to migrate over and use Maven for > Dependency Management. > > My question is : I have about 130 Jars in the Project we are a large > project. I have Artifactory set up. SOme of the JARs I don't even have > versions for as they have been around for years. A few we have even > modified. > > I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? > I have figured out for a single JAR I can deploy the artifact like so > mvn deploy:deploy-file -e > -Durl=http://repo.dotcms.com/artifactory/dotcms-DrepositoryId=dotcms > -Dfile=Tidy.jar -Dversion=ukv > -DgroupId=com.dotcms.lib -Dpackaging=jar -DartifactId=Tidy > > Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the > EASIEST way to generate the POM for the dependencies? Is there a single > command that can do this? Is there a MVN command that will do this for me? > > In the end I need a POM that people will point to that will have all the > libs for compile time because they will be building plugins in our system > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Help for Maven Migration
I am trying to figure out the best way to migrate over and use Maven for Dependency Management. My question is : I have about 130 Jars in the Project we are a large project. I have Artifactory set up. SOme of the JARs I don't even have versions for as they have been around for years. A few we have even modified. I want to know Should I just deploy my entire WEB-INF/lib to Artifactory? I have figured out for a single JAR I can deploy the artifact like so mvn deploy:deploy-file -e -Durl=http://repo.dotcms.com/artifactory/dotcms-DrepositoryId=dotcms -Dfile=Tidy.jar -Dversion=ukv -DgroupId=com.dotcms.lib -Dpackaging=jar -DartifactId=Tidy Deploying my entire WEB-INF/lib seems easiest to me BUT then what is the EASIEST way to generate the POM for the dependencies? Is there a single command that can do this? Is there a MVN command that will do this for me? In the end I need a POM that people will point to that will have all the libs for compile time because they will be building plugins in our system
Re: maven migration
Hi Karl Heinz Marbaise, How are doing... I installed nexus repository.i created hosted repository and added all artifacts. How to add maven plugins to repository.i added maven-resource-plugin. it could ask the org.apache and org.codehaus.plexes ...some time it shows maven-parent-18.pom My aim is using only company repository.(These repository contains jar+pluings) Plz help me. Regards, chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5136233.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Hi , I created hosted repository and uploaded project related artifacts. how to add the plugins(goal) like clean,complier and war(maven-war-plugin). I added directly org.apache.maven.plugins as groupid id. while run the application it gives classnotfound exceptions .org.apache.maven.shared.filterexception this is my settings.xml file http://maven.apache.org/SETTINGS/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd";> public admin admin123 nexus * http://localhost:8081/nexus/content/groups/public/ jdk-1.6 1.6 nexus repository http://repository true false repository http://repository true false nexus jdk-1.6 Thanks & Regards, chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5119127.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Hi, if you installed the nexus as repo manager the default configuration of Nexus contains already configured Maven Central, SNAPSHOT and RELEASE repositories ...so usually for the first step no real change in the configuration is needed Only the settings.xml has to be changed for working with the Nexus...which can be found in the documentation: http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5119047.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Hi Anders, How are you doing... I created repository using nexus and upload the all artifacts.all dependency jars are downloading from repository but maven plugins are not. how to add the plugins to repository. -->added plugins to repository like clean,compiler ,resource and war plugin Unable to download this jar from repo. -->How to configure internal repository and maven central repositoyr.In maven central repository browser remote showing artifacts and browser stroage shows empty. Plz help me Thanks & Regards, Chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5118750.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Maven 3 cannot use legacy Maven 1 repositories. You need a repo manager to convert it to Maven 2/3 layout. /Anders On Wed, Dec 21, 2011 at 13:52, chandrasheker wrote: > we are not using any Repository managers.my company repository is working > according maven1. > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5091818.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
we are not using any Repository managers.my company repository is working according maven1. -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5091818.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Hi, are you using some kind of Repository Manager in your company like Nexus, Artifactory or Archiva ? If not the first step is to install one...Nexus supports Maven 1 as well (please check the docs...i'm not 100% sure..)... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5091807.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven migration
Hi, I am migrating the maven from maven 1.0.2 to maven 3.0.3.my company repository is working fine in maven 1.0.2 version,but not in maven 3.I am still using maven 1.0.2 related company repository.It is unable to connect the company repository(maven 3),it is pointing the maven central repo.plz help me what are the changes required in repository as well as settings.xml. Thanks & Regards, chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5091757.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven migration plugin 1.0 released
Hi all guys, a friend of mine and I, have developed a little maven plugin that provides the capability to manage database schema changes, via myBatis<http://www.mybatis.org/> Migration Schema tool. It can create a new migration script, apply one or more scripts managed into the migration repository to database, undo actions to database and create a SQL migration script. For more information on maven-migration-plugin, visit the project home page<http://www.99soft.org/projects/maven-migration-plugin/1.0/> . All modules are available on Maven Central Repository<http://repo1.maven.org/maven2/com/googlecode/maven-migration-plugin/> . Feedback, suggestions for improvement and contributions are always welcome via the issue tracker<http://www.99soft.org/projects/maven-migration-plugin/1.0/issue-tracking.html> . Thanks in advice Simone Tripodi and Marco Speranza on behalf of the maven-migration-plugin community -- Marco Speranza
Re: Ant to Maven migration
Hi Shalini, You can! But then you are really not using Maven. You are just using Maven to invoke your Ant. I recommend you read more about Maven to really understand how you can do it effectively using Maven. After you have read the basics you can look at this http://maven.apache.org/guides/mini/guide-webapp.html Thanks, Kalpak Hi, I have a build.xml for my project. War file is generated using ant. Is it possible to convert my project to maven project using maven ant run plugin. Please help me out. Regards, Shalini. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Ant to Maven migration
Many things are technically possible. But likely not the best way. If you have a not too complicated project, I would suggest creating correctly Maven structured project(s) using proper Maven plugins (like the war plugin). Will make your Maven life easier in the long run and you get a standardized structure, which Maven is much about. /Anders On Wed, May 5, 2010 at 06:23, wrote: > Hi, > > > > I have a build.xml for my project. War file is generated using ant. > > Is it possible to convert my project to maven project using maven ant > run plugin. > > Please help me out. > > > > Regards, > > Shalini. > > > > > > > Please do not print this email unless it is absolutely necessary. > > The information contained in this electronic message and any attachments to > this message are intended for the exclusive use of the addressee(s) and may > contain proprietary, confidential or privileged information. If you are not > the intended recipient, you should not disseminate, distribute or copy this > e-mail. Please notify the sender immediately and destroy all copies of this > message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of viruses. The > company accepts no liability for any damage caused by any virus transmitted > by this email. > > www.wipro.com >
Ant to Maven migration
Hi, I have a build.xml for my project. War file is generated using ant. Is it possible to convert my project to maven project using maven ant run plugin. Please help me out. Regards, Shalini. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Looking for advice on unraveling a particularly nasty Ant->Maven migration
Ah-ha - that would do the trick. I knew there'd be something fairly obvious I was missing. =) A. On Fri, Apr 24, 2009 at 10:40 AM, Stan Devitt wrote: > Can you move D to A and use an assembly to build the external jar you > want? > > > > - > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
RE: Looking for advice on unraveling a particularly nasty Ant->Maven migration
Can you move D to A and use an assembly to build the external jar you want? - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Looking for advice on unraveling a particularly nasty Ant->Maven migration
Hi all - I'm working on moving a sizeable multimodule project from Ant to Maven, and have, along the way, run into a number of annoying circular dependency problems. This project was set up using some custom Ant tasks/targets for inter-module dependency management and unit testing, which worked nicely in that context but have resulted in the problems I'm facing now. The current situation I've got is that all of the modules get compiled before any of the unit tests are run, so there are a number of cases where module A depends on module B for A's tests to run, but B depends on A to compile before it can compile. We've been able to resolve most of those cases by moving code around, reworking tests slightly, etc, but we've still got one particularly nasty set remaining, and I'm not sure how to fix it. In this case, we've got module A, and then modules B, C, and D. Modules B, C, and D are test harnesses (or related code) for module A, and depend on module A's classes to compile, while module A depends on B, C, and D to run its tests. B and C seem like their source can just be moved to A/src/test/java, but module D's jar is also packaged in a bundle that's used in some automated testing outside of the build. Any ideas on how I can streamline this insanity? =) A.
Re: Maven migration and future
Habib Ragelhassi wrote: We are about to migrate to Maven. Our source code(million of line of source) is monolithic and does not fit at all Maven conventions and is not modular at all. 1-I wounder wether any standard migration strategy to speed-up the component driven approch in order to mavenize such huge amount of source code? Do you know such adventure in the software industry? Having completed a year long exercise in this, combining jars, ears, wars, and Eclipse plugins, the basic advice is small steps, slowly. The payoff is huge - we are capable of cutting a release and deploying it in under 30 minutes, while other projects schedule deployments that take whole weekends. Personally, I know that Spring framework was migrated by using a gradual approach( no source move, just "empty" maven modules with just pom.xml files). But Spring is not that big in term of source code. That's the approach, the size of the source code doesn't really matter. Resign yourself that it will take a while, and constantly reevaluate your progress as you move through your code. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Maven migration and future
Hi, We are about to migrate to Maven. Our source code(million of line of source) is monolithic and does not fit at all Maven conventions and is not modular at all. 1-I wounder wether any standard migration strategy to speed-up the component driven approch in order to mavenize such huge amount of source code? Do you know such adventure in the software industry? Personally, I know that Spring framework was migrated by using a gradual approach( no source move, just "empty" maven modules with just pom.xml files). But Spring is not that big in term of source code. 2- The second thing that I miss is the future of Maven. Where do you want to lead us? what Maven 3 will implement? Thanks in advance. Best regards Habib Ragelhassi Software Engineer: Software Development eXtended team Sales & e-Commerce Platforms Amadeus IT Group SA (+33) 04 97 15 45 83 [EMAIL PROTECTED] www.amadeus.com
maven migration - including jars for the build?
Hi, We have a project that I want to migrate to maven, however at the moment it is not possible to convert it completely. Is it possible to define in the pom to: include the source directories: module1/src/ module2/src/ and the jars in /lib/ for the build? Then I could create a jar of the project now and split the project into several modules with dependencies later. Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
