Re: Profile - activeByDefault in Maven 3.0
Jorg, Thanks for the reply. Thanks for the tip on help:activeprofiles - it shows "dev" - so maybe I have a different problem. I created a simple set of projects using archetype:generate - a parent project and a child project for a multimodule project, parent builds child. I ran some tests with and without the -Pdev setting. It seems to only work if I specify the -Pdev setting, what am I missing here? Thanks, Todd In the parent pom I have com.test parent pom 1.0-SNAPSHOT parent http://maven.apache.org dev child In the child I have parent com.test 1.0-SNAPSHOT com.loftware.test child 1.0-SNAPSHOT childparent http://maven.apache.org junit junit 3.8.1 test When I run "mvn clean install" - I get the following C:\dev\maven3test\parent>mvn clean install [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building parent 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ parent --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ parent --- [INFO] Installing C:\dev\maven3test\parent\pom.xml to C:\dev\maven\repo\com\test\parent\1.0-SNAPSHOT\parent-1.0-SNAPSHOT .pom [INFO] [INFO] BUILD SUCCESS [INFO] When, I run "mvn clean install -Pdev" i get C:\dev\maven3test\parent>mvn clean install -Pdev [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] parent [INFO] childparent [INFO] [INFO] [INFO] Building parent 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ parent --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ parent --- [INFO] Installing C:\dev\maven3test\parent\pom.xml to C:\dev\maven\repo\com\test\parent\1.0-SNAPSHOT\parent-1.0-SNAPSHOT .pom [INFO] [INFO] [INFO] Building childparent 1.0-SNAPSHOT [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ childparent --- [INFO] Building jar: C:\dev\maven3test\parent\childparent\target\childparent-1.0-SNAPSHOT.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ childparent --- [INFO] Installing C:\dev\maven3test\parent\childparent\target\childparent-1.0-SNAPSHOT.jar to C:\dev\maven\repo\com\loft ware\test\childparent\1.0-SNAPSHOT\childparent-1.0-SNAPSHOT.jar [INFO] Installing C:\dev\maven3test\parent\childparent\pom.xml to C:\dev\maven\repo\com\loftware\test\childparent\1.0-SN APSHOT\childparent-1.0-SNAPSHOT.pom [INFO] [INFO] Reactor Summary: [INFO] [INFO] parent SUCCESS [0.484s] [INFO] childparent ... SUCCESS [1.965s] [INFO] [INFO] BUILD SUCCESS [INFO] Running "mvn help:activeprofiles" gives me C:\dev\maven3test\parent>mvn help:active-profiles [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building parent 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ parent --- [INFO] Active Profiles for Project 'com.test:parent:pom:1.0-SNAPSHOT': The following profiles are active: - dev (source: settings.xml) [INFO] [INFO] BUILD SUCCESS [INFO] running "mvn active-profile -Pdev" gives me C:\dev\maven3test\parent>mvn help:active-profiles -Pdev [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] parent [INFO] childparent [INFO] [INFO] [INFO] Building parent 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ parent --- [INFO] Active Profiles for Project 'com.test:parent:pom:1.0-SNAPSHOT': The following profil
Profile - activeByDefault in Maven 3.0
Hi All, I am currently upgrading to maven 3 from 2. I have a settings.xml that I have been using for a couple of years now. It has a profile in it called "dev" it looks something like this: dev true When I run "mvn clean install" in 2.0 it used this profile and all was well. Now when I run against Maven 3.0 this profile is not active. I have to run "mvn clean install -Pdev" to activate it. I have searched online and tried several things, the only thing that seemed to work was . Does this setting no longer work??? Thanks, Todd -- View this message in context: http://maven.40175.n5.nabble.com/Profile-activeByDefault-in-Maven-3-0-tp5043324p5043324.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
Reactor:resume goal
I am trying to resume a multimodule project that is nested. I want to resume from a project that is in a project that is one level deep from the top level. I would assume that I would use "from" to say what folder to start from and "fromArtifact" to say what project to start. This doesn't seem to work. It doesn't like both the settings at once. If I leave off the folder and just do the artifact. It tells me that I can't specify both the folder and the artifact. The folder that it thinks it is using is "null", so it is taking a default. I can't figure out a way to get it so "fromArtifact" is accepted. Level1ProjectFolder Level2ProjectFolder Level2Project mvn org.apache.maven.plugins:maven-reactor-plugin:1.0:resume -Dfrom=leve2ProjectFolder -DfromArtifact=level2Project Does anyone know how to make this work? Thanks, Todd
RE: Maven and Subversion.
I am still working through the discussion - just wanted to say thanks for the feedback. Todd - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven and Subversion.
I am wondering if anyone has a good solution to the following issue. I have a multi module maven configuration ( a pom that runs multiple poms underneath it.). I made it a multi module project because the sub projects are very similar and it is convenient to run them all from one pom. However, I need each of these sub projects to be versioned independently. In subversion, you need to make trunk, tags, and branches folders for each project to do this. This breaks the multi module directory structure for Maven as it requires the pom to be in the top level folder for each of the sub projects. Does anyone have a solution as to the best way to make this work, or am I stuck with not using the multi module project in Maven? Thanks, Todd
RE: dependency Classifier not honored?
I am not sure what happened, but the problem disappeared. I checked out a new
sandbox and all seems to be well.
-Original Message-
From: Todd Patch
Sent: Tuesday, September 15, 2009 3:09 PM
To: users@maven.apache.org
Subject: RE: dependency Classifier not honored?
Hi Stephen,
That is actually how I got it into the repository. The only manual
step that I took was to copy the artifact and change the name while
troubleshooting.
Todd
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, September 14, 2009 10:51 AM
To: Maven Users List
Subject: Re: dependency Classifier not honored?
Do not copy files into your repository by hand... use mvn install:install-file
otherwise you will hit these kinds of problems
-Stephen
P.S.
I do not know if this is _all_ you need to do to fix your issue, but
it is at least some of what you need to do
2009/9/14 :
> Hi,
>
>I have setup the following dependency in my POM:
>
>
>com.adobe.flex.sdk
>datavisualization_rb
>${flex.sdk.version}
>en_US
>swc
>
>
> I placed the artifact in my repo
>
> C:\dev\maven\repo\com\adobe\flex\sdk\datavisualization_rb\3.2.0.3958 and the
> name of the artifact is "datavisualization_rb-3.2.0.3958-en_US.swc" .
>
> When I run, I get the following error:
>
> Error start
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>mvn install:install-file -DgroupId=com.adobe.flex.sdk
> -DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
>mvn deploy:deploy-file -DgroupId=com.adobe.flex.sdk
> -DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc -
> Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
> com.adobe.flex.sdk:datavisualization_rb:swc:3.2.0.3958
>
> - Error End -
>
> I went into the repo and changed the name of the artifact to
> "datavisualization_rb-3.2.0.3958.swc" and ran it again. This time it was
> successful.
>
> Does the classifier not work in Maven 2.2.1 or am I doing it wrong?
>
> Thanks,
>
> Todd
>
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: dependency Classifier not honored?
Hi Stephen,
That is actually how I got it into the repository. The only manual
step that I took was to copy the artifact and change the name while
troubleshooting.
Todd
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, September 14, 2009 10:51 AM
To: Maven Users List
Subject: Re: dependency Classifier not honored?
Do not copy files into your repository by hand... use mvn install:install-file
otherwise you will hit these kinds of problems
-Stephen
P.S.
I do not know if this is _all_ you need to do to fix your issue, but
it is at least some of what you need to do
2009/9/14 :
> Hi,
>
>I have setup the following dependency in my POM:
>
>
>com.adobe.flex.sdk
>datavisualization_rb
>${flex.sdk.version}
>en_US
>swc
>
>
> I placed the artifact in my repo
>
> C:\dev\maven\repo\com\adobe\flex\sdk\datavisualization_rb\3.2.0.3958 and the
> name of the artifact is "datavisualization_rb-3.2.0.3958-en_US.swc" .
>
> When I run, I get the following error:
>
> Error start
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>mvn install:install-file -DgroupId=com.adobe.flex.sdk
> -DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
>mvn deploy:deploy-file -DgroupId=com.adobe.flex.sdk
> -DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc -
> Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
> com.adobe.flex.sdk:datavisualization_rb:swc:3.2.0.3958
>
> - Error End -
>
> I went into the repo and changed the name of the artifact to
> "datavisualization_rb-3.2.0.3958.swc" and ran it again. This time it was
> successful.
>
> Does the classifier not work in Maven 2.2.1 or am I doing it wrong?
>
> Thanks,
>
> Todd
>
-
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
dependency Classifier not honored?
Hi,
I have setup the following dependency in my POM:
com.adobe.flex.sdk
datavisualization_rb
${flex.sdk.version}
en_US
swc
I placed the artifact in my repo
C:\dev\maven\repo\com\adobe\flex\sdk\datavisualization_rb\3.2.0.3958 and the
name of the artifact is "datavisualization_rb-3.2.0.3958-en_US.swc" .
When I run, I get the following error:
Error start
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.adobe.flex.sdk
-DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.adobe.flex.sdk
-DartifactId=datavisualization_rb -Dversion=3.2.0.3958 -Dpackaging=swc -
Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
com.adobe.flex.sdk:datavisualization_rb:swc:3.2.0.3958
- Error End -
I went into the repo and changed the name of the artifact to
"datavisualization_rb-3.2.0.3958.swc" and ran it again. This time it was
successful.
Does the classifier not work in Maven 2.2.1 or am I doing it wrong?
Thanks,
Todd
RE: mvn jetty:run and dbunit conflict?
Yes, I just tried it. This has the same outcome, the dependency is not loaded and the app fails when launched in jetty. -Original Message- From: mknut...@baselogic.com [mailto:mknut...@baselogic.com] On Behalf Of Mick Knutson Sent: Wednesday, August 12, 2009 9:13 AM To: Maven Users List Subject: Re: mvn jetty:run and dbunit conflict? Have you tried setting them to test? --- Thank You... Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Wed, Aug 12, 2009 at 8:58 AM, toddp2 wrote: > > Hi, > > I have a sample web app where I am using the dbunit-maven-plugin to load > data into a database and the maven-jetty-plugin to run it in jetty. I am > issuing the following command to build and deploy the web app. > mvn clean install jetty:run. My issue is with some dependencies that I > have > set as runtime. If I comment out the dbunit plugin all > works > fine - jetty starts up and I can test. When I add the dbunit plugin to the > mix, my app has errors when jetty starts up. I looked at the classpath > differences between the two runs and I found that all my dependencies > marked > with scope runtime were not being loaded when the dbunit plugin was used. > I > removed the runtime scope, with dbunit active and it fixed the problem. My > question is why would dbunit stop these dependencies from being loaded at > runtime? > > Thanks, > > Todd > -- > View this message in context: > http://www.nabble.com/mvn-jetty%3Arun-and-dbunit-conflict--tp24935948p24935948.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
How do you clean the site files from the deploy location?
Hello, I am using the site plugin to publish the reports for my project to a local web server. I am able to get it to deploy correctly, but I noticed that it does not deploy cleanly. 1) It does not clean out what was already there. I found maven 1.x had a maven.site.deploy.clean property, but this does not work in maven 2.x. 2) It copies the site information for the projects as it is building so the site has broken links until the build is complete. What is the recommended way to handle these issues with the current plugin? Thanks, Todd
