Nabble - Maven - Users

SNAPSHOT comparison between local and remote repositories

2009-11-12T21:31:23Z

I notice that every SNAPSHOt file is checked at the remote repository for
teh latest version, everytime it is given as a dependency.
( This doesnt happen when the <repository> in settings.xml doesnt enable
<snapsot> )

( My snapshots doesnt have any build number or anything ( Eg -
xxxxxx-SNAPSHOT ) )
But Im confused about how maven can make any comparison between local and
remote repositoties in order to deduce which one is teh latest.
What if I have build teh artifact locally so that my local version is newer
than the one in remote repository ?

Is maven comparing the some kind of timestamps ? ( If true then it has to
assume that the clocks of both machines are in sync )

--sony

Re: How to fix the java.net repository relocation

2009-11-12T19:48:02Z

> Let me explain the situation, before that I would say this is a kind of a
> bug in maven, simply because maven does not skip taking an artifact if one
> of the maven repo sends a 301(MOVED PERMANANTLY) and it simply take that
> message and write it as the pom file. Simply if the maven repo sends 404 it
> skip that repo and go for another, but here with 301 it just dump the
> message as the pom file and later on this failes.

Maven does follow the redirects, but if the redirects send you off to
an html page then you can have trouble.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: -DskipTests=true gets ignored

2009-11-12T16:43:37Z

OK, so flip the assumptions I made in my earlier profile. Then, you
could change the profile to "skip-tests" and the reverse would happen.
Change the name of the profile to "sandbox". Now, when you do "mvn
-Psandbox install" you'll get no tests, but a regular "mvn install"
would include all your tests.

It may require another profile to handle your second condition. The
notion that a single profile can somehow read your mind and know whether
it should or should not run "certain" tests just won't fly. That'll
require an extra profile added to your build. So, you might end up with
a build command line that looks like...

mvn -Psandbox,no-externals install

Otherwise, the same semantics in your pom.xml apply. It's just a matter
of setting up a default condition that you can override in your profile.

Dave

Yaakov Chaikin wrote:

> Well, the thing is that I have a couple of requirements:
>
> 1) When doing mvn install all tests should run (without specifying a profile)
> 2) When doing mvn install -DskipTests=true, no tests should run
> 3) When doing mvn install -P sandbox, no tests should run
> 4) When doing mvn install -P sandbox, only some of the modules should
> run their tests (the ones that don't hit any outside resources like a
> DB).
>
> How would I do that?
>
> Thanks for your help!
>
> Yaakov.
>
> On Thu, Nov 12, 2009 at 5:49 PM, David C. Hicks <dhicks@...> wrote:
>
>> I generally use a Profile when I want to do something of this nature.
>> So, for your case, you might have something like...
>>
>> <properties>
>> � �<skipTests>true</skipTests>
>> </properties>
>>
>> <profiles>
>> � �<profile>
>> � � � <id>run-tests</id>
>> � � � <properties>
>> � � � � �<skipTests>false</skipTests>
>> � � � </properties>
>> � �</profile>
>> </profiles>
>>
>> Then by simply calling Maven with the profile activated, you can run the
>> tests...
>>
>> mvn -Prun-tests clean install
>>
>>
>> Yaakov Chaikin wrote:
>>
>>> Right... I figured that... But why? Isn't something on the
>>> command-line supposed to trump it all?
>>>
>>> Any suggestions on how to correct this?
>>>
>>> Thanks,
>>> Yaakov.
>>>
>>>
>>> On Thu, Nov 12, 2009 at 5:23 PM, David C. Hicks <dhicks@...> wrote:
>>>
>>>
>>>> I think it's an order-of-evaluation problem. �I suspect that your
>>>> -DskipTests=true is getting overridden by the <property> in your pom.xml.
>>>>
>>>> Yaakov Chaikin wrote:
>>>>
>>>>
>>>>> Ok,
>>>>>
>>>>> Checked documentation, googled. Still not understanding why the
>>>>> following is happening.
>>>>>
>>>>> I have a multi-module project. In the root pom.xml, I have:
>>>>> <properties>
>>>>> � <skipTests>true</skipTests>
>>>>> <properties>
>>>>>
>>>>>
>>>>> In my child pom.xml I have the following:
>>>>>
>>>>> <properties>
>>>>> � �<skipTests>${skipSelfContainingTests}</skipTests>
>>>>> <properties>
>>>>>
>>>>> In my settings.xml, I have this:
>>>>> <properties>
>>>>> � <skipSelfContainingTests>false</skipSelfContainingTests>
>>>>> </properties>
>>>>>
>>>>> When I do mvn help:effective-pom on the child module, it does show
>>>>> that my skipTests=false. However, when I do mvn help:effective-pom
>>>>> -DskipTests=true, the effective pom STILL shows up with
>>>>> skipTests=false!
>>>>>
>>>>> What am I doing wrong here?
>>>>>
>>>>> Thanks,
>>>>> Yaakov.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>>> For additional commands, e-mail: users-help@...
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: -DskipTests=true gets ignored

2009-11-12T16:34:04Z

On Thu, 12 Nov 2009 17:29:28 -0500, Yaakov Chaikin wrote:

> Right... I figured that... But why? Isn't something on the command-line
> supposed to trump it all?

Put the properties first: mvn -DskipTests=true install
That worked for me.

Holger

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Archetype creation w/ metadata

2009-11-12T15:21:37Z

So, I've managed to fix my duplicated directory issue. Apparently I do not need fully qualified path's in my pom file like I thought I did.

I still cannot get maven to recognize my archetype-metadata.xml file though.

Thanks for your time!

Matthew Runo
Software Engineer, Zappos.com
mruno@... - 702-943-7833

On Nov 12, 2009, at 10:48 AM, Matthew Runo wrote:

> Hello folks!
>
> I hope this makes sense, as I'm about out of ideas as to how to go about getting my archetype to work as needed. I have two outstanding issues that I can't seem to squash.
>
> 1. When I use my archetype to make a project, I get an extra directory and I'm not sure how... Here's the resulting directory structure, when I create my app from /Users/mruno:
>
> test-app
> - pom.xml
> ^ src
> -- all the stuff under src is properly placed
> ^ Users
> - ^ mruno... and so on, to create an empty "resources" directory under /Users/mruno/test/src/main/resources and /Users/mruno/test/src/test/resources
>
> I've no idea how or why these two empty directories are being created. When I check out the archetype from / I do not get this directory, leading me to think it's some sort of path issue.
>
> 2. I need to ask the user for some input to customize the project before Velocity goes through and does its variable replacement. I've tried making an archetype-metadata.xml but it seems like this file is ignored. How can I make maven use that file? I have created an archetype.xml as well, and it seems to be used. I've attached both files here:
>
> --= archetype.xml =--
> <?xml version="1.0" encoding="UTF-8"?><archetype>
> <id>site-manager-app</id>
> <sources>
> <source filtered="true">src/main/java/TestControl.java</source>
> </sources>
> <testSources>
> <source filtered="true">src/test/java/TestControlTest.java</source>
> </testSources>
> <resources>
> <resource filtered="true">src/main/resources/build.properties</resource>
> <resource filtered="true">src/main/resources/log4j.xml</resource>
> <resource filtered="true">src/test/resources/build.properties</resource>
> <resource filtered="true">src/main/webapp/WEB-INF/web.xml</resource>
> <resource filtered="true">src/main/webapp/WEB-INF/spring-security.xml</resource>
> <resource filtered="true">src/main/webapp/WEB-INF/spring-servlet.xml</resource>
> </resources>
> <siteResources>
> <resource filtered="false">src/main/webapp/WEB-INF/freemarker/header.ftl</resource>
> <resource filtered="false">src/main/webapp/WEB-INF/freemarker/login.ftl</resource>
> <resource filtered="false">src/main/webapp/WEB-INF/freemarker/macros/library.ftl</resource>
> <resource filtered="false">src/main/webapp/WEB-INF/freemarker/test.ftl</resource>
> </siteResources>
> </archetype>
>
> --= archetype-metadata.xml =--
> <?xml version="1.0" encoding="UTF-8"?>
> <archetype-descriptor name="site-manager-app" partial="true">
> <id>site-manager-app</id>
> <requiredProperties>
> <requiredProperty key="name">
> <defaultValue>My Sample Application</defaultValue>
> </requiredProperty>
> <requiredProperty key="description" />
> </requiredProperties>
> <fileSets>
> <fileSet packaged="true" encoding="UTF-8">
> <directory>./src/main/java</directory>
> <includes>
> <include>**/*.java</include>
> </includes>
> </fileSet>
> <fileSet packaged="true" encoding="UTF-8">
> <directory>./src/test/java</directory>
> <includes>
> <include>**/*.java</include>
> </includes>
> </fileSet>
> <fileSet encoding="UTF-8">
> <directory>./src/main/webapp/WEB-INF</directory>
> <includes>
> <include>**/*.xml</include>
> </includes>
> </fileSet>
> <fileSet encoding="UTF-8">
> <directory>./src/main/resources</directory>
> <includes>
> <include>**/*.xml</include>
> <include>**/*.properties</include>
> </includes>
> </fileSet>
> <fileSet encoding="UTF-8">
> <directory>./src/test/resources</directory>
> <includes>
> <include>**/*.xml</include>
> <include>**/*.properties</include>
> </includes>
> </fileSet>
> <fileSet encoding="UTF-8">
> <directory>./src/main/webapp/WEB-INF/freemarker</directory>
> <includes>
> <include>*.ftl</include>
> <include>**/*.ftl</include>
> </includes>
> </fileSet>
> </archetype-descriptor>
>
> I really appreciate your time and help! Forgive me if I'm making silly mistakes... so far as I can tell though, I'm not.
>
> Matthew Runo
> Software Engineer, Zappos.com
> mruno@... - 702-943-7833
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: -DskipTests=true gets ignored

2009-11-12T15:21:23Z

Well, the thing is that I have a couple of requirements:

1) When doing mvn install all tests should run (without specifying a profile)
2) When doing mvn install -DskipTests=true, no tests should run
3) When doing mvn install -P sandbox, no tests should run
4) When doing mvn install -P sandbox, only some of the modules should
run their tests (the ones that don't hit any outside resources like a
DB).

How would I do that?

Thanks for your help!

Yaakov.

On Thu, Nov 12, 2009 at 5:49 PM, David C. Hicks <dhicks@...> wrote:

> I generally use a Profile when I want to do something of this nature.
> So, for your case, you might have something like...
>
> <properties>
> <skipTests>true</skipTests>
> </properties>
>
> <profiles>
> <profile>
> <id>run-tests</id>
> <properties>
> <skipTests>false</skipTests>
> </properties>
> </profile>
> </profiles>
>
> Then by simply calling Maven with the profile activated, you can run the
> tests...
>
> mvn -Prun-tests clean install
>
>
> Yaakov Chaikin wrote:
>> Right... I figured that... But why? Isn't something on the
>> command-line supposed to trump it all?
>>
>> Any suggestions on how to correct this?
>>
>> Thanks,
>> Yaakov.
>>
>>
>> On Thu, Nov 12, 2009 at 5:23 PM, David C. Hicks <dhicks@...> wrote:
>>
>>> I think it's an order-of-evaluation problem. I suspect that your
>>> -DskipTests=true is getting overridden by the <property> in your pom.xml.
>>>
>>> Yaakov Chaikin wrote:
>>>
>>>> Ok,
>>>>
>>>> Checked documentation, googled. Still not understanding why the
>>>> following is happening.
>>>>
>>>> I have a multi-module project. In the root pom.xml, I have:
>>>> <properties>
>>>> <skipTests>true</skipTests>
>>>> <properties>
>>>>
>>>>
>>>> In my child pom.xml I have the following:
>>>>
>>>> <properties>
>>>> <skipTests>${skipSelfContainingTests}</skipTests>
>>>> <properties>
>>>>
>>>> In my settings.xml, I have this:
>>>> <properties>
>>>> <skipSelfContainingTests>false</skipSelfContainingTests>
>>>> </properties>
>>>>
>>>> When I do mvn help:effective-pom on the child module, it does show
>>>> that my skipTests=false. However, when I do mvn help:effective-pom
>>>> -DskipTests=true, the effective pom STILL shows up with
>>>> skipTests=false!
>>>>
>>>> What am I doing wrong here?
>>>>
>>>> Thanks,
>>>> Yaakov.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: -DskipTests=true gets ignored

2009-11-12T14:49:18Z

I generally use a Profile when I want to do something of this nature.
So, for your case, you might have something like...

<properties>
<skipTests>true</skipTests>
</properties>

<profiles>
<profile>
<id>run-tests</id>
<properties>
<skipTests>false</skipTests>
</properties>
</profile>
</profiles>

Then by simply calling Maven with the profile activated, you can run the
tests...

mvn -Prun-tests clean install

Yaakov Chaikin wrote:

> Right... I figured that... But why? Isn't something on the
> command-line supposed to trump it all?
>
> Any suggestions on how to correct this?
>
> Thanks,
> Yaakov.
>
>
> On Thu, Nov 12, 2009 at 5:23 PM, David C. Hicks <dhicks@...> wrote:
>
>> I think it's an order-of-evaluation problem. I suspect that your
>> -DskipTests=true is getting overridden by the <property> in your pom.xml.
>>
>> Yaakov Chaikin wrote:
>>
>>> Ok,
>>>
>>> Checked documentation, googled. Still not understanding why the
>>> following is happening.
>>>
>>> I have a multi-module project. In the root pom.xml, I have:
>>> <properties>
>>> <skipTests>true</skipTests>
>>> <properties>
>>>
>>>
>>> In my child pom.xml I have the following:
>>>
>>> <properties>
>>> <skipTests>${skipSelfContainingTests}</skipTests>
>>> <properties>
>>>
>>> In my settings.xml, I have this:
>>> <properties>
>>> <skipSelfContainingTests>false</skipSelfContainingTests>
>>> </properties>
>>>
>>> When I do mvn help:effective-pom on the child module, it does show
>>> that my skipTests=false. However, when I do mvn help:effective-pom
>>> -DskipTests=true, the effective pom STILL shows up with
>>> skipTests=false!
>>>
>>> What am I doing wrong here?
>>>
>>> Thanks,
>>> Yaakov.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[ANN] Apache Source-Release Assembly Descriptor 1.0.2 Released

2009-11-12T14:48:00Z

The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.2.

This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build output) that
are the subject of an ASF release vote.

The new version of the descriptor fixes the erroneous exclusion of some
file types like IDE files from the source archive even if those files
are located in the src/ directory tree of a project, i.e. denote actual
project sources (e.g. required for unit testing).

http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/

This new descriptor will eventually be incorporated into the Apache
Parent POM. If you want to try out the source-release descriptor in the
meantime, you can include a configuration like the following:

<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>

<dependencies>
<dependency>
<groupId>org.apache.apache.resources</groupId>

<artifactId>apache-source-release-assembly-descriptor</artifactId>
<version>1.0.2</version>
</dependency>
<dependency>

<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-utils</artifactId>
<version>2.0.1</version>
</dependency>
</dependencies>

<executions>
<execution>
<id>source-release</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>source-release</descriptorRef>
</descriptorRefs>
<tarLongFileMode>gnu</tarLongFileMode>
<runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>

Enjoy,

The Maven Team

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: -DskipTests=true gets ignored

2009-11-12T14:29:28Z

Right... I figured that... But why? Isn't something on the
command-line supposed to trump it all?

Any suggestions on how to correct this?

Thanks,
Yaakov.

On Thu, Nov 12, 2009 at 5:23 PM, David C. Hicks <dhicks@...> wrote:

> I think it's an order-of-evaluation problem. I suspect that your
> -DskipTests=true is getting overridden by the <property> in your pom.xml.
>
> Yaakov Chaikin wrote:
>> Ok,
>>
>> Checked documentation, googled. Still not understanding why the
>> following is happening.
>>
>> I have a multi-module project. In the root pom.xml, I have:
>> <properties>
>> <skipTests>true</skipTests>
>> <properties>
>>
>>
>> In my child pom.xml I have the following:
>>
>> <properties>
>> <skipTests>${skipSelfContainingTests}</skipTests>
>> <properties>
>>
>> In my settings.xml, I have this:
>> <properties>
>> <skipSelfContainingTests>false</skipSelfContainingTests>
>> </properties>
>>
>> When I do mvn help:effective-pom on the child module, it does show
>> that my skipTests=false. However, when I do mvn help:effective-pom
>> -DskipTests=true, the effective pom STILL shows up with
>> skipTests=false!
>>
>> What am I doing wrong here?
>>
>> Thanks,
>> Yaakov.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: -DskipTests=true gets ignored

2009-11-12T14:23:25Z

I think it's an order-of-evaluation problem. I suspect that your
-DskipTests=true is getting overridden by the <property> in your pom.xml.

Yaakov Chaikin wrote:

> Ok,
>
> Checked documentation, googled. Still not understanding why the
> following is happening.
>
> I have a multi-module project. In the root pom.xml, I have:
> <properties>
> <skipTests>true</skipTests>
> <properties>
>
>
> In my child pom.xml I have the following:
>
> <properties>
> <skipTests>${skipSelfContainingTests}</skipTests>
> <properties>
>
> In my settings.xml, I have this:
> <properties>
> <skipSelfContainingTests>false</skipSelfContainingTests>
> </properties>
>
> When I do mvn help:effective-pom on the child module, it does show
> that my skipTests=false. However, when I do mvn help:effective-pom
> -DskipTests=true, the effective pom STILL shows up with
> skipTests=false!
>
> What am I doing wrong here?
>
> Thanks,
> Yaakov.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

-DskipTests=true gets ignored

2009-11-12T14:20:41Z

Ok,

Checked documentation, googled. Still not understanding why the
following is happening.

I have a multi-module project. In the root pom.xml, I have:
<properties>
<skipTests>true</skipTests>
<properties>

In my child pom.xml I have the following:

<properties>
<skipTests>${skipSelfContainingTests}</skipTests>
<properties>

In my settings.xml, I have this:
<properties>
<skipSelfContainingTests>false</skipSelfContainingTests>
</properties>

When I do mvn help:effective-pom on the child module, it does show
that my skipTests=false. However, when I do mvn help:effective-pom
-DskipTests=true, the effective pom STILL shows up with
skipTests=false!

What am I doing wrong here?

Thanks,
Yaakov.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Personal property substitution in m2

2009-11-12T14:07:58Z

You are right, it does not. That's too bad because my pom.xml already defined a client.id property.

System properties work fine, as does forcing the profile with -P, as does using profiles.xml (not checked in) at the top of the project directory.

Thanks for pointing me in the right direction, Anders.

Jeff

Anders Hammar wrote:

No, I don't think so. You can trigger a profile based on a property, but I
don't think that works for a property defined in a project's pom. Please try
and report back!

/Anders

On Thu, Nov 12, 2009 at 22:00, Jeff French <jeff@mdbconsulting.com> wrote:

>
> Thanks, Anders. That worked great, and I did include defaults in pom.xml.
>
> Is there a way to choose a profile based on the project? Some properties,
> like the specific database name used for testing, will differ not only by
> developer, but also by project.
>
> Oh, and Paul, I agree. Upon retrospect it was a lame subject line. :-)
>
>
> Anders Hammar wrote:
> >
> > Each user defining this property through a profile in his/her
> settings.xml
> > is the way to go. However, best practice is to have default values of the
> > properties defined in the project's pom. The project should NOT rely on
> > configuration in settings.xml.
> >
> > /Anders
> >
> > On Thu, Nov 12, 2009 at 04:17, Jeff French <jeff@mdbconsulting.com>
> wrote:
> >
> >>
> >> I'm finally getting the chance to migrate some of our m1 projects to m2,
> >> and
> >> am wondering about the m2 way to do the following.
> >>
> >> During our m1 test phase we replace macros such as @db.host@ in some
> >> config
> >> files. The maven.xml file has a goal which defines some filters, and
> >> individual developers can set properties such as db.host in their
> >> build.properties file in the project root.
> >>
> >> I'd like the same end result in m2 - that developers can use their local
> >> database for testing. After Googling and looking at examples, it seems
> >> that
> >> defining a profile in settings.xml might be the way to go, but that
> seems
> >> like overkill for the simple macro replacement I'm trying to do. Is
> there
> >> a
> >> better way to handle this in m2?
> >>
> >> Thanks for any pointers.
> >>
> >> Jeff
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26312742.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26326318.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: Using the Maven Deploy Plugin

2009-11-12T13:47:39Z

I will check out that location to see what I find.

In the meantime, I tried http, but then I get the following:

[INFO] Error deploying artifact: Failed to transfer file: http://myserver:8081/nexus/content/repositories/myRepo/<blah blah>. Return code is: 400

Any idea why this might be?

Thanks.

-----Original Message-----
From: Jamie Whitehouse [mailto:Jamie.Whitehouse@...]
Sent: Thu 11/12/2009 3:40 PM
To: Maven Users List
Subject: RE: Using the Maven Deploy Plugin

No, it's http that you want.

Since you used file initially you'll probably see your artifacts on your
local disk in a directory like
myserver:8081/nexus/content/repositories/myRepo/

-----Original Message-----
From: Neil Chaudhuri [mailto:nchaudhuri@...]
Sent: Thursday, November 12, 2009 4:32 PM
To: Maven Users List
Subject: RE: Using the Maven Deploy Plugin

As illuminating as that link is, I have my pom setup in precisely that
fashion. The only difference is that I am not using either scp or sftp
as my protocol because they are not appropriate in my case.

Is file: the correct protocol since the server is not secure?

Thanks.

-----Original Message-----
From: Stevo Slavic [mailto:sslavic@...]
Sent: Thu 11/12/2009 3:14 PM
To: Maven Users List
Subject: Re: Using the Maven Deploy Plugin

http://maven.apache.org/pom.html#Repository

Regards,
Stevo.

On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri <
nchaudhuri@...> wrote:

> We have an internal Maven repository that I can view in my browser at
> http://myserver:8081/nexus/content/repositories/myRepo/. I am simply
> trying to upload my generated WAR file to this repository. I have set
> up credentials in settings.xml, and my pom is set up as follows:
>
> <repository>
> <id>my-maven-repo</id>
> <name>Internal Maven Repository</name>
>
> <url>file://myserver:8081/nexus/content/repositories/myRepo/</url>
> </repository>
>
>
> This work great and I get a BUILD SUCCESSFUL message.
>
> The problem is that when I go back to
> http://myserver:8081/nexus/content/repositories/myRepo/, I can't see

it.
>
> Any ideas as to what is going on here?
>
> Thanks.
>

-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

RE: Using the Maven Deploy Plugin

2009-11-12T13:40:54Z

No, it's http that you want.

Since you used file initially you'll probably see your artifacts on your
local disk in a directory like
myserver:8081/nexus/content/repositories/myRepo/

-----Original Message-----
From: Neil Chaudhuri [mailto:nchaudhuri@...]
Sent: Thursday, November 12, 2009 4:32 PM
To: Maven Users List
Subject: RE: Using the Maven Deploy Plugin

As illuminating as that link is, I have my pom setup in precisely that
fashion. The only difference is that I am not using either scp or sftp
as my protocol because they are not appropriate in my case.

Is file: the correct protocol since the server is not secure?

Thanks.

-----Original Message-----
From: Stevo Slavic [mailto:sslavic@...]
Sent: Thu 11/12/2009 3:14 PM
To: Maven Users List
Subject: Re: Using the Maven Deploy Plugin

http://maven.apache.org/pom.html#Repository

Regards,
Stevo.

On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri <
nchaudhuri@...> wrote:

it.
>
> Any ideas as to what is going on here?
>
> Thanks.
>

-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

RE: Using the Maven Deploy Plugin

2009-11-12T13:31:30Z

As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case.

Is file: the correct protocol since the server is not secure?

Thanks.

-----Original Message-----
From: Stevo Slavic [mailto:sslavic@...]
Sent: Thu 11/12/2009 3:14 PM
To: Maven Users List
Subject: Re: Using the Maven Deploy Plugin

http://maven.apache.org/pom.html#Repository

Regards,
Stevo.

On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri <
nchaudhuri@...> wrote:

> We have an internal Maven repository that I can view in my browser at
> http://myserver:8081/nexus/content/repositories/myRepo/. I am simply
> trying to upload my generated WAR file to this repository. I have set up
> credentials in settings.xml, and my pom is set up as follows:
>
> <repository>
> <id>my-maven-repo</id>
> <name>Internal Maven Repository</name>
>
> <url>file://myserver:8081/nexus/content/repositories/myRepo/</url>
> </repository>
>
>
> This work great and I get a BUILD SUCCESSFUL message.
>
> The problem is that when I go back to
> http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it.
>
> Any ideas as to what is going on here?
>
> Thanks.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Using the Maven Deploy Plugin

2009-11-12T13:14:19Z

http://maven.apache.org/pom.html#Repository

Regards,
Stevo.

On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri <
nchaudhuri@...> wrote:

> We have an internal Maven repository that I can view in my browser at
> http://myserver:8081/nexus/content/repositories/myRepo/. I am simply
> trying to upload my generated WAR file to this repository. I have set up
> credentials in settings.xml, and my pom is set up as follows:
>
> <repository>
> <id>my-maven-repo</id>
> <name>Internal Maven Repository</name>
>
> <url>file://myserver:8081/nexus/content/repositories/myRepo/</url>
> </repository>
>
>
> This work great and I get a BUILD SUCCESSFUL message.
>
> The problem is that when I go back to
> http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it.
>
> Any ideas as to what is going on here?
>
> Thanks.
>

Re: Personal property substitution in m2

2009-11-12T13:11:58Z

No, I don't think so. You can trigger a profile based on a property, but I
don't think that works for a property defined in a project's pom. Please try
and report back!

/Anders

On Thu, Nov 12, 2009 at 22:00, Jeff French <jeff@...> wrote:

>
> Thanks, Anders. That worked great, and I did include defaults in pom.xml.
>
> Is there a way to choose a profile based on the project? Some properties,
> like the specific database name used for testing, will differ not only by
> developer, but also by project.
>
> Oh, and Paul, I agree. Upon retrospect it was a lame subject line. :-)
>
>
> Anders Hammar wrote:
> >
> > Each user defining this property through a profile in his/her
> settings.xml
> > is the way to go. However, best practice is to have default values of the
> > properties defined in the project's pom. The project should NOT rely on
> > configuration in settings.xml.
> >
> > /Anders
> >
> > On Thu, Nov 12, 2009 at 04:17, Jeff French <jeff@...>
> wrote:
> >
> >>
> >> I'm finally getting the chance to migrate some of our m1 projects to m2,
> >> and
> >> am wondering about the m2 way to do the following.
> >>
> >> During our m1 test phase we replace macros such as @db.host@ in some
> >> config
> >> files. The maven.xml file has a goal which defines some filters, and
> >> individual developers can set properties such as db.host in their
> >> build.properties file in the project root.
> >>
> >> I'd like the same end result in m2 - that developers can use their local
> >> database for testing. After Googling and looking at examples, it seems
> >> that
> >> defining a profile in settings.xml might be the way to go, but that
> seems
> >> like overkill for the simple macro replacement I'm trying to do. Is
> there
> >> a
> >> better way to handle this in m2?
> >>
> >> Thanks for any pointers.
> >>
> >> Jeff
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26312742.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26326318.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: Personal property substitution in m2

2009-11-12T13:00:05Z

Thanks, Anders. That worked great, and I did include defaults in pom.xml.

Is there a way to choose a profile based on the project? Some properties, like the specific database name used for testing, will differ not only by developer, but also by project.

Oh, and Paul, I agree. Upon retrospect it was a lame subject line. :-)

Anders Hammar wrote:

Each user defining this property through a profile in his/her settings.xml
is the way to go. However, best practice is to have default values of the
properties defined in the project's pom. The project should NOT rely on
configuration in settings.xml.

/Anders

On Thu, Nov 12, 2009 at 04:17, Jeff French <jeff@mdbconsulting.com> wrote:

>
> I'm finally getting the chance to migrate some of our m1 projects to m2,
> and
> am wondering about the m2 way to do the following.
>
> During our m1 test phase we replace macros such as @db.host@ in some
> config
> files. The maven.xml file has a goal which defines some filters, and
> individual developers can set properties such as db.host in their
> build.properties file in the project root.
>
> I'd like the same end result in m2 - that developers can use their local
> database for testing. After Googling and looking at examples, it seems that
> defining a profile in settings.xml might be the way to go, but that seems
> like overkill for the simple macro replacement I'm trying to do. Is there a
> better way to handle this in m2?
>
> Thanks for any pointers.
>
> Jeff
> --
> View this message in context:
> http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26312742.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Using the Maven Deploy Plugin

2009-11-12T12:30:41Z

We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows:

<repository>
<id>my-maven-repo</id>
<name>Internal Maven Repository</name>
<url>file://myserver:8081/nexus/content/repositories/myRepo/</url>
</repository>

This work great and I get a BUILD SUCCESSFUL message.

The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it.

Any ideas as to what is going on here?

Thanks.

Re: Multi Module Project Assembly plugin

2009-11-12T11:47:45Z

I have attached my parent pom.xml and one of my modules pom.xml.
Please take a look.

Thanks.

On 11/12/09, Anders Hammar <anders@...> wrote:

> You mus be doing something wrong. If the plugin is bound correctly, it will
> be executed.
> If you post the pom snippet we might spot the issue.
>
> /Anders
>
> On Thu, Nov 12, 2009 at 19:25, Stephanie Johnson
> <jstephanie11@...>wrote:
>
>> Thanks for your suggestion Anders. But that doesnt seem to work. If I
>> associate my assembly plugin to package phase or install phase and run
>> mvn install or mvn package - it does not build my assemblies.
>>
>> I tried running mvn install first and then running mvn
>> assembly:assembly. This generates following error.
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to create assembly: Artifact: blaw blaw (included by
>> module) does not have an artifact with a file. Please ensure the
>> package phase is run before the assembly is generated.
>>
>> This is weird because all the dependencies are built installed and ready
>> to
>> use.
>>
>> Thanks.
>>
>> On 11/11/09, Anders Hammar <anders@...> wrote:
>> > You should bind the assembly plugin to an appropriate phase (such as
>> > 'package'). The, you only need to run
>> > mvn install
>> >
>> > /Anders
>> >
>> > On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson
>> > <jstephanie11@...>wrote:
>> >
>> >> All,
>> >>
>> >> I am using Maven 2.0.9 to build a multi module project. I have defined
>> the
>> >> assembly plugin in my parent pom. I can get my assemblies built using
>> >>
>> >> mvn install assembly:assemly
>> >>
>> >> This command runs the tests twice, once during install phase and
>> >> another
>> >> during assembly. I tried assembly:single but it throws an error. Any
>> help
>> >> to
>> >> fix get my assemblies built without running the tests twice is much
>> >> appreciated.
>> >>
>> >> Thanks.
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>

<?xml version="1.0" encoding="UTF-8"?>
<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/xsd/maven-4.0.0.xsd">
<repositories>

<repository>
<id>MYREPOID</id>
<url>http://MYREPO</url>
</repository>

</repositories>

<modelVersion>4.0.0</modelVersion>
<groupId>com.MYGROUP</groupId>
<version>TRUNK</version>
<artifactId>MY_PARENT_ARTIFACT</artifactId>
<packaging>pom</packaging>
<name>MYNAME</name>

<modules>
<module>MYMODULE1</module>
<module>MYMODULE2</module>
<module>MYMODULE3</module>
<module>MYMODULE4</module>
</modules>

<dependencies>

<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.14</version>
</dependency>

</dependencies>

<build>
<plugins>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>
<configuration>
<descriptors>
<descriptor>something1.xml</descriptor>
<descriptor>something2.xml<</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<phase>verify</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>

</plugins>

</build>
</project>

<?xml version="1.0"?>

<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>
<artifactId>MY_MODULE1_ARTIFACT</artifactId>
<packaging>jar</packaging>
<name>MY_MODULE1_NAME</name>
<url>../MY_MODULE1_NAME</url>

<parent>
<groupId>com.MYGROUP</groupId>
<artifactId>MY_PARENT_ARTIFACT</artifactId>
<version>TRUNK</version>
<relativePath>../myparentpom.xml</relativePath>
</parent>

<dependencies>

<dependency>
<groupId>blah</groupId>
<artifactId>blah</artifactId>
<version>TRUNK</version>
</dependency>

</dependencies>

</project>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

mvn package + SAR + EAR

2009-11-12T11:36:48Z

Hey everyone, I have been trying to include a SAR inside an EAR, following the wiki entry here:

http://docs.codehaus.org/display/MAVENUSER/Creating+JBoss+SAR+(Service+ARchive)+Artifacts

Almost everything works as expected, except that “mvn package” fails with (depending on the mvn version) one of:

“Transitive dependency resolution for scope: test has failed for your project.”

“Failed to resolve artifact.”

I have attached the simplest project I can come up with to test this out.

Running “mvn clean package” will fail with one of the above messages. However, “mvn clean package install” will succeed. And it succeeds presumably because install will install the SAR into the local repository, allowing the ear plugin to pick it up.

This seems like a bug to me, but perhaps I’m just doing something wrong?

Regards,

Eric Wittmann

ITS, Yale University

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

sar-test.zip (3K) Download Attachment

Re: release:perform fails with "test-jar"

2009-11-12T11:19:11Z

tried it: Did not work :-(

Olivier Lamy wrote:

> Just try with a different release plugin configuration :
>
> <preparationGoals>clean install</preparationGoals>
>
> Probably you are dealing with : http://jira.codehaus.org/browse/MRELEASE-3
>
> --
> Olivier
>
> 2009/11/12 Jamie Whitehouse <Jamie.Whitehouse@...>:
>> I have used this many times and can assure you it works.
>>
>> How are you calling the release goals? In one line or as different
>> steps?
>>
>> -----Original Message-----
>> From: Johannes Schneider [mailto:mailings@...]
>> Sent: Thursday, November 12, 2009 12:43 PM
>> To: users@...
>> Subject: release:perform fails with "<type>test-jar</type>"
>>
>> Hi,
>>
>> I have a multi module project here. It has several dependencies like
>> that:
>>
>> <dependency>
>> <groupId>com.cedarsoft.commons</groupId>
>> <artifactId>serialization</artifactId>
>> <type>test-jar</type>
>> <scope>test</scope>
>> </dependency>
>>
>> Everything works as expected (install works). But I can't release a new
>> version.
>> release:prepare runs fine, but release:perform fails with a compiler
>> error (cannot find symbol). The compiler doesn't find a class defined
>> within the test-jar.
>>
>> Can anyone given me a hint what might be wrong?
>>
>>
>>
>> Thanks,
>>
>> Johannes
>>
>>
>>
>> mvn -v
>> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version:
>> 1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux"
>> version: "2.6.31-15-generic" arch: "amd64" Family: "unix"
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>> -------------------------------------------------------------------------------------------------------------------
>> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Plugin Dependencies

2009-11-12T11:19:04Z

> parent pom in one process the plugin seems to get stuck on the plugin
> dependencies defined in the first module executed. Subsequent plugin
> dependency configurations are ignored. It feels like this is an issue with
> the underlying Maven dependency mechanism and not with the Flex-Mojos
> plugin. We're using the latest Maven 2.2.1 release.

You're right about what you're seeing, and this is how Maven2
currently works. You need to copy all your plugin deps (needed for all
executions of that plugin across all modules etc) into the "first"
declaration of that plugin which is executed -- the easiest is to just
consolidate and copy the deps to each one.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Multi Module Project Assembly plugin

2009-11-12T11:09:51Z

You mus be doing something wrong. If the plugin is bound correctly, it will
be executed.
If you post the pom snippet we might spot the issue.

/Anders

On Thu, Nov 12, 2009 at 19:25, Stephanie Johnson <jstephanie11@...>wrote:

> Thanks for your suggestion Anders. But that doesnt seem to work. If I
> associate my assembly plugin to package phase or install phase and run
> mvn install or mvn package - it does not build my assemblies.
>
> I tried running mvn install first and then running mvn
> assembly:assembly. This generates following error.
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to create assembly: Artifact: blaw blaw (included by
> module) does not have an artifact with a file. Please ensure the
> package phase is run before the assembly is generated.
>
> This is weird because all the dependencies are built installed and ready to
> use.
>
> Thanks.
>
> On 11/11/09, Anders Hammar <anders@...> wrote:
> > You should bind the assembly plugin to an appropriate phase (such as
> > 'package'). The, you only need to run
> > mvn install
> >
> > /Anders
> >
> > On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson
> > <jstephanie11@...>wrote:
> >
> >> All,
> >>
> >> I am using Maven 2.0.9 to build a multi module project. I have defined
> the
> >> assembly plugin in my parent pom. I can get my assemblies built using
> >>
> >> mvn install assembly:assemly
> >>
> >> This command runs the tests twice, once during install phase and another
> >> during assembly. I tried assembly:single but it throws an error. Any
> help
> >> to
> >> fix get my assemblies built without running the tests twice is much
> >> appreciated.
> >>
> >> Thanks.
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: Plugin Dependencies

2009-11-12T11:02:54Z

known issue. I don't recall the JIRA

2009/11/12 Tim Fulmer <tfulmer@...>:

> Hi All,
>
> We've run into a slight issue with plugin dependencies. We're using plugin
> dependencies to configure the version of Flex to use in several Flex modules
> with the Flex-Mojos plugin. The idea is we need to support two different
> versions of Flex, v3.4 and v4.0. This works fine as long as the different
> versions are run in separate Maven processes. However, when run from a
> parent pom in one process the plugin seems to get stuck on the plugin
> dependencies defined in the first module executed. Subsequent plugin
> dependency configurations are ignored. It feels like this is an issue with
> the underlying Maven dependency mechanism and not with the Flex-Mojos
> plugin. We're using the latest Maven 2.2.1 release.
>
> This affects our ability to do easy releases of the entire platform and
> complicates our module structure greatly. I have a test project available
> if that would help.
>
> Please advise,
>
> -- Tim
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Archetype creation w/ metadata

2009-11-12T10:48:39Z

Hello folks!

I hope this makes sense, as I'm about out of ideas as to how to go about getting my archetype to work as needed. I have two outstanding issues that I can't seem to squash.

1. When I use my archetype to make a project, I get an extra directory and I'm not sure how... Here's the resulting directory structure, when I create my app from /Users/mruno:

test-app
- pom.xml
^ src
-- all the stuff under src is properly placed
^ Users
- ^ mruno... and so on, to create an empty "resources" directory under /Users/mruno/test/src/main/resources and /Users/mruno/test/src/test/resources

I've no idea how or why these two empty directories are being created. When I check out the archetype from / I do not get this directory, leading me to think it's some sort of path issue.

2. I need to ask the user for some input to customize the project before Velocity goes through and does its variable replacement. I've tried making an archetype-metadata.xml but it seems like this file is ignored. How can I make maven use that file? I have created an archetype.xml as well, and it seems to be used. I've attached both files here:

--= archetype.xml =--
<?xml version="1.0" encoding="UTF-8"?><archetype>
<id>site-manager-app</id>
<sources>
<source filtered="true">src/main/java/TestControl.java</source>
</sources>
<testSources>
<source filtered="true">src/test/java/TestControlTest.java</source>
</testSources>
<resources>
<resource filtered="true">src/main/resources/build.properties</resource>
<resource filtered="true">src/main/resources/log4j.xml</resource>
<resource filtered="true">src/test/resources/build.properties</resource>
<resource filtered="true">src/main/webapp/WEB-INF/web.xml</resource>
<resource filtered="true">src/main/webapp/WEB-INF/spring-security.xml</resource>
<resource filtered="true">src/main/webapp/WEB-INF/spring-servlet.xml</resource>
</resources>
<siteResources>
<resource filtered="false">src/main/webapp/WEB-INF/freemarker/header.ftl</resource>
<resource filtered="false">src/main/webapp/WEB-INF/freemarker/login.ftl</resource>
<resource filtered="false">src/main/webapp/WEB-INF/freemarker/macros/library.ftl</resource>
<resource filtered="false">src/main/webapp/WEB-INF/freemarker/test.ftl</resource>
</siteResources>
</archetype>

--= archetype-metadata.xml =--
<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="site-manager-app" partial="true">
<id>site-manager-app</id>
<requiredProperties>
<requiredProperty key="name">
<defaultValue>My Sample Application</defaultValue>
</requiredProperty>
<requiredProperty key="description" />
</requiredProperties>
<fileSets>
<fileSet packaged="true" encoding="UTF-8">
<directory>./src/main/java</directory>
<includes>
<include>**/*.java</include>
</includes>
</fileSet>
<fileSet packaged="true" encoding="UTF-8">
<directory>./src/test/java</directory>
<includes>
<include>**/*.java</include>
</includes>
</fileSet>
<fileSet encoding="UTF-8">
<directory>./src/main/webapp/WEB-INF</directory>
<includes>
<include>**/*.xml</include>
</includes>
</fileSet>
<fileSet encoding="UTF-8">
<directory>./src/main/resources</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.properties</include>
</includes>
</fileSet>
<fileSet encoding="UTF-8">
<directory>./src/test/resources</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.properties</include>
</includes>
</fileSet>
<fileSet encoding="UTF-8">
<directory>./src/main/webapp/WEB-INF/freemarker</directory>
<includes>
<include>*.ftl</include>
<include>**/*.ftl</include>
</includes>
</fileSet>
</archetype-descriptor>

I really appreciate your time and help! Forgive me if I'm making silly mistakes... so far as I can tell though, I'm not.

Matthew Runo
Software Engineer, Zappos.com
mruno@... - 702-943-7833

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: release:perform fails with "test-jar"

2009-11-12T10:26:18Z

in different steps

Jamie Whitehouse wrote:

> I have used this many times and can assure you it works.
>
> How are you calling the release goals? In one line or as different
> steps?
>
> -----Original Message-----
> From: Johannes Schneider [mailto:mailings@...]
> Sent: Thursday, November 12, 2009 12:43 PM
> To: users@...
> Subject: release:perform fails with "<type>test-jar</type>"
>
> Hi,
>
> I have a multi module project here. It has several dependencies like
> that:
>
> <dependency>
> <groupId>com.cedarsoft.commons</groupId>
> <artifactId>serialization</artifactId>
> <type>test-jar</type>
> <scope>test</scope>
> </dependency>
>
> Everything works as expected (install works). But I can't release a new
> version.
> release:prepare runs fine, but release:perform fails with a compiler
> error (cannot find symbol). The compiler doesn't find a class defined
> within the test-jar.
>
> Can anyone given me a hint what might be wrong?
>
>
>
> Thanks,
>
> Johannes
>
>
>
> mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version:
> 1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Default locale: en_US, platform encoding: UTF-8 OS name: "linux"
> version: "2.6.31-15-generic" arch: "amd64" Family: "unix"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
>
> -------------------------------------------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Multi Module Project Assembly plugin

2009-11-12T10:25:56Z

Thanks for your suggestion Anders. But that doesnt seem to work. If I
associate my assembly plugin to package phase or install phase and run
mvn install or mvn package - it does not build my assemblies.

I tried running mvn install first and then running mvn
assembly:assembly. This generates following error.

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to create assembly: Artifact: blaw blaw (included by
module) does not have an artifact with a file. Please ensure the
package phase is run before the assembly is generated.

This is weird because all the dependencies are built installed and ready to use.

Thanks.

On 11/11/09, Anders Hammar <anders@...> wrote:

> You should bind the assembly plugin to an appropriate phase (such as
> 'package'). The, you only need to run
> mvn install
>
> /Anders
>
> On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson
> <jstephanie11@...>wrote:
>
>> All,
>>
>> I am using Maven 2.0.9 to build a multi module project. I have defined the
>> assembly plugin in my parent pom. I can get my assemblies built using
>>
>> mvn install assembly:assemly
>>
>> This command runs the tests twice, once during install phase and another
>> during assembly. I tried assembly:single but it throws an error. Any help
>> to
>> fix get my assemblies built without running the tests twice is much
>> appreciated.
>>
>> Thanks.
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: release:perform fails with "test-jar"

2009-11-12T10:06:02Z

Just try with a different release plugin configuration :

<preparationGoals>clean install</preparationGoals>

Probably you are dealing with : http://jira.codehaus.org/browse/MRELEASE-3

--
Olivier

2009/11/12 Jamie Whitehouse <Jamie.Whitehouse@...>:

--
Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

RE: release:perform fails with "test-jar"

2009-11-12T10:01:09Z

I have used this many times and can assure you it works.

How are you calling the release goals? In one line or as different
steps?

-----Original Message-----
From: Johannes Schneider [mailto:mailings@...]
Sent: Thursday, November 12, 2009 12:43 PM
To: users@...
Subject: release:perform fails with "<type>test-jar</type>"

Hi,

I have a multi module project here. It has several dependencies like
that:

<dependency>
<groupId>com.cedarsoft.commons</groupId>
<artifactId>serialization</artifactId>
<type>test-jar</type>
<scope>test</scope>
</dependency>

Everything works as expected (install works). But I can't release a new
version.
release:prepare runs fine, but release:perform fails with a compiler
error (cannot find symbol). The compiler doesn't find a class defined
within the test-jar.

Can anyone given me a hint what might be wrong?

Thanks,

Johannes

mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version:
1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Default locale: en_US, platform encoding: UTF-8 OS name: "linux"
version: "2.6.31-15-generic" arch: "amd64" Family: "unix"

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Plugin Dependencies

2009-11-12T09:55:55Z

Hi All,

We've run into a slight issue with plugin dependencies. We're using plugin
dependencies to configure the version of Flex to use in several Flex modules
with the Flex-Mojos plugin. The idea is we need to support two different
versions of Flex, v3.4 and v4.0. This works fine as long as the different
versions are run in separate Maven processes. However, when run from a
parent pom in one process the plugin seems to get stuck on the plugin
dependencies defined in the first module executed. Subsequent plugin
dependency configurations are ignored. It feels like this is an issue with
the underlying Maven dependency mechanism and not with the Flex-Mojos
plugin. We're using the latest Maven 2.2.1 release.

This affects our ability to do easy releases of the entire platform and
complicates our module structure greatly. I have a test project available
if that would help.

Please advise,

-- Tim

release:perform fails with "test-jar"

2009-11-12T09:43:29Z

Hi,

I have a multi module project here. It has several dependencies like that:

<dependency>
<groupId>com.cedarsoft.commons</groupId>
<artifactId>serialization</artifactId>
<type>test-jar</type>
<scope>test</scope>
</dependency>

Everything works as expected (install works). But I can't release a new
version.
release:prepare runs fine, but release:perform fails with a compiler
error (cannot find symbol). The compiler doesn't find a class defined
within the test-jar.

Can anyone given me a hint what might be wrong?

Thanks,

Johannes

mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_16
Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.31-15-generic" arch: "amd64" Family: "unix"

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Using property name/value to activate profile

2009-11-12T08:14:32Z

> Is the case dismissed now or do I need to hire a lawyer? :-)

We'll let it go this time. ;-)

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Using property name/value to activate profile

2009-11-12T08:02:33Z

On Thu, Nov 12, 2009 at 10:06 AM, Wayne Fay <waynefay@...> wrote:
>> Ok, I'll share what exactly is going on with everyone else...
>>
>> The maven docs says this about activating profiles through a property:
>
> Just to be clear... you emailed this list BEFORE looking at the
> documentation?? Next time, RTFM (and run a couple searches at Google)
> first, OK? ;-)

:-) Sweet advise! Thanks.

But just so you are clear... No, I didn't email the list BEFORE
looking at documentation. I just missed (or didn't pay enough
attention to) the word "system" in front of the word "properties" when
trying to figure out what I was doing wrong. I also didn't realize
that properties that I specified right in the pom.xml OR the
settings.xml were not ending up as system properties.

And yes, I did Google it.

Besides, the second I realized my mistake, I immediately emailed the
list so no one would waste their time answering and others would have
the benefit of learning something from my mistake.

Is the case dismissed now or do I need to hire a lawyer? :-)

Regards,
Yaakov.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Apache 3 pom moved

2009-11-12T07:52:38Z

> already downloaded apache-3.pom the build continues without any trouble. But
> I think the problem here is that as I use the Axis2 1.4.1 version and not
> the newest snapshot and the 1.4.1 version is already in the repo so the
> change should be made there, no? Isn't this issue affecting anybody that
> tries to use an Axis2 maven plugin that is not the current version?

That's a fine idea, except that Maven repos are write-once storage. So
the poms "cannot" be "fixed" once released -- only a newer version can
be produced which has the new, correct values in it.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...