How can I remove a SA from Serv

[youhaodeyi]

I use mvn jbi:projectDeploy command to deploy my SA to ServiceMix. Where does
ServiceMix put the SA? How can I remove it?
-- 
View this message in context: 
http://www.nabble.com/How-can-I-remove-a-SA-from-Serv-tp15911973s177p15911973.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: How can I download all the packages from a remote repository?

[youhaodeyi]

Can I write the dependency with wildcard characters? For example, 


 *
 *
  ...


Then I will download all the packages from the repository.


Brian E Fox wrote:
> 
> Get a repository manager (proximity/nexus/archiva/artifactory) to act as
> a local proxy. Scraping the entire repository is not being a friendly
> netizen and will probably get your ip blocked. There are much better
> ways.
> 
> -Original Message-
> From: youhaodeyi [mailto:[EMAIL PROTECTED] 
> Sent: Friday, March 07, 2008 10:15 PM
> To: users@maven.apache.org
> Subject: How can I download all the packages from a remote repository?
> 
> 
> Can I download all the packages from a remote repository to my local
> repository? For example, there is a repository:
> http://repo1.maven.org/maven2/,  I want to download all the content to
> my
> local repository. I want to do this for that I have limitation for
> accessing
> Internet, so I need to do this one time to get as much packages as
> possible.
> -- 
> View this message in context:
> http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-
> repository--tp15910759s177p15910759.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-repository--tp15910759s177p15911893.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mvn environment variable in debian etch

[Heinrich Nirschl]

On Fri, Mar 7, 2008 at 11:38 PM, Érico Teixeira <[EMAIL PROTECTED]> wrote:
> I trying to set mvn environment variable in etch
>
>  I already have JAVA_HOME configured in /etc/profile as
>  follows :
>
>  JAVA_HOME=/opt/java/jdk1.6.0_04
>  JRE_HOME=/opt/jre1.6.0_04
>  M2_HOME=/opt/apache-maven-2.0.8
>  M2=$M2_HOME/bin
>  PATH=$PATH:$JAVA_HOME/bin
>  PATH=$PATH:$M2
>  export PATH
>
>  javac command is ok
>
>  running echo $JAVA_HOME I have:
>  /opt/java/jdk1.6.0_04
>
>  running echo $M2 variable I have:
>  /opt/apache-maven-2.0.8/bin
>
>  when I run mvn in console I receive the error :
>  Error: JAVA_HOME is not defined correctly.
>   We cannot execute java
>

You need to export these variables, e.g.:

export JAVA_HOME

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I download all the packages from a remote repository?

[Wendy Smoak]

On Fri, Mar 7, 2008 at 9:59 PM, youhaodeyi <[EMAIL PROTECTED]> wrote:

>  I use this command to download:
>
>  rsync -avz http://repo1.maven.org/maven2/ ./

As others have mentioned, you'd be much better off running a
repository manager app (Archiva, Artifactory, Proximity) and filling
it up with the things you actually need.

If you really must get the whole thing, check the bottom of this page,
it looks like you can rsync from one of the mirrors:
http://maven.apache.org/guides/mini/guide-mirror-settings.html

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I download all the packages from a remote repository?

[youhaodeyi]

I use this command to download:

rsync -avz http://repo1.maven.org/maven2/ ./

and got the error:

http: Unknown Host
rsh.exe: can't establish connection
rsync: read error: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at
/tmp/rsync-2.5.6/io.c(177)


Wayne Fay wrote:
> 
> For the repo1.maven.org repo, you should use rsync to pull it down.
> But realistically, this is very bad idea, as "central" is like 10gb
> and 98% of it is stuff you will never use. So you will spend an
> enormous amount of time, bandwith, and disk space for things you don't
> need.
> 
> Instead, you should consider a proxy/repo solution like Archiva,
> Proximity, etc.
> 
> Wayne
> 
> On 3/7/08, youhaodeyi <[EMAIL PROTECTED]> wrote:
>>
>> Can I download all the packages from a remote repository to my local
>> repository? For example, there is a repository:
>> http://repo1.maven.org/maven2/,  I want to download all the content to my
>> local repository. I want to do this for that I have limitation for
>> accessing
>> Internet, so I need to do this one time to get as much packages as
>> possible.
>> --
>> View this message in context:
>> http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-repository--tp15910759s177p15910759.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-repository--tp15910759s177p15911327.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to use buildnumber-maven-plugin

[Dirk Olmes]

Rex Huang wrote:

when I use buildnumber-maven-plugin,
it generate the buildnumber as below:
buildNumber: 137261 at timestamp: 1204813937453

but I want to change the timestamp's format, configuration as below:


org.codehaus.mojo
buildnumber-maven-plugin


validate

create




{0,date,EEE MMM d HH:mm z }

timestamp




but result is :
buildNumber: Thu Mar 6 15:32 CET 2008 at timestamp: 1204813943453

not as my expect:
buildNumber: 137261 at timestamp: Thu Mar 6 15:32 CET 2008

Why?


That's simply not supported. You can format "the build number" which is 
either the svn repository version or the timestamp. See 
http://jira.codehaus.org/browse/MOJO-988 and hope for the best that it 
ever will get applied ...


-dirk

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: artifacts build fine on their own but fail in multi-module build

[Stuart McCulloch]

On 08/03/2008, shea <[EMAIL PROTECTED]> wrote:
>
>
> Hi Stuart,
>
> Thanks for your reply - I think this explains the problem.
>
> If I understand correctly, the workaround you are proposing is that I
> unpack
> the contents of the "a" jar into "a/target/classes" during the package
> phase
> (using antrun or dependency-plugin unless there is another approach)?
> Alternatively, I suppose I could use antrun to copy the classes for "a"
> into
> "a/target/classes" before packaging and  thereby use the default
> "classesDirectory" for the jar plugin...same difference I think.


correct - btw, you can use "mvn -X install" to see the compilation classpath
used during a build - it also produces a lot of other debug, so best pipe it
to
a file and search thru it later for classpath entries

thanks,
>
> Shea.
>
>
> Stuart McCulloch-3 wrote:
> >
> > On 06/03/2008, shea <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> Hello,
> >>
> >> I have a multi-module build that is essentially:
> >>
> >> jars---a
> >>  b
> >>  c
> >>
> >> Where jars is a directory that contains a parent/multimodule pom.xmlthat
> >> builds a pom-type artifact called "jars-parent". a, b, and c are each
> >> sub-directories within the jars directory with their own poms.  a, b,
> and
> >> c,
> >> all have jars-parent as their parent.  They are referenced as modules
> in
> >> jars-parent's pom.xml in the same order.
> >>
> >> The problem arises in a situation when "c" depends on "a" for example.
> >> If
> >> I
> >> build each of the submodules independently in the the order "a, b, c",
> >> everything is fine.  however, when I do a "mvn install" from the jars
> >> directory, "a" and "b" build fine, but compilation of "c" fails - not
> an
> >> artifact resolution problem, but a compilation problem. This is in
> spite
> >> of
> >> the fact that "a" was built and installed to my local repo just fine.
> >>
> >> The only unusual thing I am doing is that "a" doesn't actually compile
> >> anything - it just packages some existing class files using the jar
> >> plugin.
> >> (this is part of an ant conversion - don't get me started :,( )
> >>
> >> I have had other multi-module build work just fine, but I am hoping
> >> somebody
> >> can point out some potential gotchas that I am overlooking.
> >
> >
> > This is due to a "feature" in the MavenProject class when running
> > a reactor (ie. multi-module) compilation.  Normally when it builds
> > the compilation classpath, it will use the location of the artifact in
> > the local maven repository - and your setup will work fine.
> >
> > However, with a reactor build you may be running "mvn compile"
> > and not installing artifacts, so there's code inside MavenProject
> > (addArtifactPath) that changes the compilation classpath to use:
> >
> >/
> >
> > instead of the location of the local repository - I think the reason
> > for this is because you want to compile against the latest code
> > and the jar in the repository may be stale if you're not doing an
> > "install" at the same time as "compile"
> >
> > unfortunately this doesn't work so well with projects that create
> > artifacts without populating "target/classes" because then the
> > compilation classpath will contain the empty directory, not the
> > actual artifact with the classes :(
> >
> > the safest workaround I've found is to unpack the contents of
> > the jar to the build.outputDirectory during the packaging phase
> > so the classes are found where MavenProject expects them
> >
> > a potential fix for the MavenProject class might be to add the
> > outputDirectory before the artifact's location in the local repo,
> > rather than replacing it in the compilation classpath - however
> > this is a rather central part of Maven so modifying its behavior
> > should be done very carefully...
> >
> > HTH
> >
> > Thanks,
> >>
> >> Shea.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15863045.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Cheers, Stuart
> >
> >
>
>
> --
> View this message in context:
> http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15901229.html
>
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Cheers, Stuart

RE: How can I download all the packages from a remote repository?

[Brian E. Fox]

Get a repository manager (proximity/nexus/archiva/artifactory) to act as
a local proxy. Scraping the entire repository is not being a friendly
netizen and will probably get your ip blocked. There are much better
ways.

-Original Message-
From: youhaodeyi [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 10:15 PM
To: users@maven.apache.org
Subject: How can I download all the packages from a remote repository?


Can I download all the packages from a remote repository to my local
repository? For example, there is a repository:
http://repo1.maven.org/maven2/,  I want to download all the content to
my
local repository. I want to do this for that I have limitation for
accessing
Internet, so I need to do this one time to get as much packages as
possible.
-- 
View this message in context:
http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-
repository--tp15910759s177p15910759.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I download all the packages from a remote repository?

[Wayne Fay]

For the repo1.maven.org repo, you should use rsync to pull it down.
But realistically, this is very bad idea, as "central" is like 10gb
and 98% of it is stuff you will never use. So you will spend an
enormous amount of time, bandwith, and disk space for things you don't
need.

Instead, you should consider a proxy/repo solution like Archiva, Proximity, etc.

Wayne

On 3/7/08, youhaodeyi <[EMAIL PROTECTED]> wrote:
>
> Can I download all the packages from a remote repository to my local
> repository? For example, there is a repository:
> http://repo1.maven.org/maven2/,  I want to download all the content to my
> local repository. I want to do this for that I have limitation for accessing
> Internet, so I need to do this one time to get as much packages as possible.
> --
> View this message in context: 
> http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-repository--tp15910759s177p15910759.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How can I download all the packages from a remote repository?

[youhaodeyi]

Can I download all the packages from a remote repository to my local
repository? For example, there is a repository:
http://repo1.maven.org/maven2/,  I want to download all the content to my
local repository. I want to do this for that I have limitation for accessing
Internet, so I need to do this one time to get as much packages as possible.
-- 
View this message in context: 
http://www.nabble.com/How-can-I-download-all-the-packages-from-a-remote-repository--tp15910759s177p15910759.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

Please file a jira and attach your pom (better if you can make it
reproducible)

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 9:05 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?

here is a blocker with mvn 2.0.8
>mvn -e --debug install

[DEBUG]   xerces:xercesImpl:jar:2.8.1
[GC [DefNew: 3968K->0K(4032K), 0.0073060 secs] 34845K->31546K(262080K),
0.007430
0 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0091788 secs] 35514K->32406K(262080K),
0.009302
3 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3960K->0K(4032K), 0.0091827 secs] 36367K->33217K(262080K),
0.009303
7 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0087908 secs] 37185K->34039K(262080K),
0.008909
8 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0044061 secs] 38007K->34357K(262080K),
0.004521
0 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0081681 secs] 38325K->35118K(262080K),
0.008291
0 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandlermar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0068601 secs] 39086K->35756K(262080K),
0.006984
1 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandleraar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.M

RE: sharing properties between modules

[EJ Ciramella]

Ok, here's the first poke, you can't override filters with profile
properties in settings.xml (or can you and I don't know how?) .

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 8:59 PM
To: Maven Users List
Subject: RE: sharing properties between modules

I'm not sure if I've stumbled upon a solution or a hack (I've been
pounding away at this problem on and off for quite some time).

Here it is - please poke some holes in this:

1 - In some project pom (doesn't have to be related to anything), have
filter files set up.  In my case, I've named them after what I wanted
(so stackdefaults-filter.properties and crimson-filter.properties).
2 - Attach an assembly to put the resulting zip file into your local
repository.
3 - use Dependency:unpack to pull down this set of filters
4 - use a profile in the child poms to choose other filters if I'd like
5 - profit

I'd love to hear some feed back where this could possibly fall apart,
but so far, I can list all the filters in the poms and they override
from top to bottom.





-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 7:13 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Yeah, the first paragraph below doesn't work.  I created a pom that not
only has a properties section (with one property) but also has a profile
with the same property.

In another pom, I put a dependency on this first pom and tried
processing resources on a file that has this same one property.  Then on
the command line of this second pom, I type "mvn process-resources
-P" but it doesn't change the property inside
the one file with the one property (I can see it's getting "processed"
from src to target, the token isn't being expanded tho).

As far as that second example, it went right over my head.  Are you
suggesting that this property file should be completed manually and
installed in our repository?  My test project is really small (one file)
all truth be told, with ATG config files counted, we have hundreds.  The
one really tricky piece is for local development, people need to be able
to apply the profiles they have locally (in their settings.xml files).
The other part to this is we combine mulitple profiles to get a final
deployment configuration.  So it'd be something like:

Mvn install -Pbase,StackDefaults,serverclass

Where "base" contains things like memory settings for the compiler and
java docs/unit testing.
"StackDefaults" contains things like where java home is for all the
stacks
"serverclass" contains things specific to say an app server versus a db
server

I like this - more ideas!  I'm pouring over the documentation trying to
find something that allows this kind of "put in one place, share all
over" type treatment of properties.

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:51 PM
To: Maven Users List
Subject: RE: sharing properties between modules

I don't actually know if dependency POMs look at their profiles'
 elements or not. I guess not, from what you're
describing. Have you tried invoking the profile explicitly when you run
Maven? (e.g. "mvn -P profileName deploy") The dependency POM's profiles
may still be available, even if they're not auto-activated.

Also, I think Wayne was suggesting actually writing config files with
the properties, packaging them into an archive, and then using that as a
dependency. (Sorry, Wayne, if I'm misunderstanding your advice.) Many
frameworks will allow you to do an #include-style import of settings
from other files, so perhaps you could have your bottom-level projects
depend on that archive, and point to its config files.

~DVA

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:28 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So there's no way to keep the properties in various profiles (all within
a pom) and just put a dependency on that pom (I think the dependency
part works, but it doesn't seem to pick up the activated profile)? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:24 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not

Re: [POLL] Why are you not able to use the most recent maven release?

[Martin Gainty]

here is a blocker with mvn 2.0.8
>mvn -e --debug install

[DEBUG]   xerces:xercesImpl:jar:2.8.1
[GC [DefNew: 3968K->0K(4032K), 0.0073060 secs] 34845K->31546K(262080K),
0.007430
0 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0091788 secs] 35514K->32406K(262080K),
0.009302
3 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3960K->0K(4032K), 0.0091827 secs] 36367K->33217K(262080K),
0.009303
7 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0087908 secs] 37185K->34039K(262080K),
0.008909
8 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0044061 secs] 38007K->34357K(262080K),
0.004521
0 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0081681 secs] 38325K->35118K(262080K),
0.008291
0 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandlermar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0068601 secs] 39086K->35756K(262080K),
0.006984
1 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandleraar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworl

RE: sharing properties between modules

[EJ Ciramella]

I'm not sure if I've stumbled upon a solution or a hack (I've been
pounding away at this problem on and off for quite some time).

Here it is - please poke some holes in this:

1 - In some project pom (doesn't have to be related to anything), have
filter files set up.  In my case, I've named them after what I wanted
(so stackdefaults-filter.properties and crimson-filter.properties).
2 - Attach an assembly to put the resulting zip file into your local
repository.
3 - use Dependency:unpack to pull down this set of filters
4 - use a profile in the child poms to choose other filters if I'd like
5 - profit

I'd love to hear some feed back where this could possibly fall apart,
but so far, I can list all the filters in the poms and they override
from top to bottom.





-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 7:13 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Yeah, the first paragraph below doesn't work.  I created a pom that not
only has a properties section (with one property) but also has a profile
with the same property.

In another pom, I put a dependency on this first pom and tried
processing resources on a file that has this same one property.  Then on
the command line of this second pom, I type "mvn process-resources
-P" but it doesn't change the property inside
the one file with the one property (I can see it's getting "processed"
from src to target, the token isn't being expanded tho).

As far as that second example, it went right over my head.  Are you
suggesting that this property file should be completed manually and
installed in our repository?  My test project is really small (one file)
all truth be told, with ATG config files counted, we have hundreds.  The
one really tricky piece is for local development, people need to be able
to apply the profiles they have locally (in their settings.xml files).
The other part to this is we combine mulitple profiles to get a final
deployment configuration.  So it'd be something like:

Mvn install -Pbase,StackDefaults,serverclass

Where "base" contains things like memory settings for the compiler and
java docs/unit testing.
"StackDefaults" contains things like where java home is for all the
stacks
"serverclass" contains things specific to say an app server versus a db
server

I like this - more ideas!  I'm pouring over the documentation trying to
find something that allows this kind of "put in one place, share all
over" type treatment of properties.

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:51 PM
To: Maven Users List
Subject: RE: sharing properties between modules

I don't actually know if dependency POMs look at their profiles'
 elements or not. I guess not, from what you're
describing. Have you tried invoking the profile explicitly when you run
Maven? (e.g. "mvn -P profileName deploy") The dependency POM's profiles
may still be available, even if they're not auto-activated.

Also, I think Wayne was suggesting actually writing config files with
the properties, packaging them into an archive, and then using that as a
dependency. (Sorry, Wayne, if I'm misunderstanding your advice.) Many
frameworks will allow you to do an #include-style import of settings
from other files, so perhaps you could have your bottom-level projects
depend on that archive, and point to its config files.

~DVA

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:28 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So there's no way to keep the properties in various profiles (all within
a pom) and just put a dependency on that pom (I think the dependency
part works, but it doesn't seem to pick up the activated profile)? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:24 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not an intended
recipient, please notify the sender and delete this message immediately.
Any views expressed in this message are those of the sender, not those
of any entity within the KBC Financial Products group of companies
(together referred to as "KBC FP"). 

This message does not create any obligation, contr

RE: [POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

I've been working through that list and I grabbed some of the serious
artifact/repo issues as well as the highest voted issues from all groups
for the .10 release. The plan most likely will be to fix the regressions
and the most popular issues for 2.0.x but it is unlikely that all of
those will get fixed; the edge cases and improvement issues will
probably get bumped to 2.1 at some point. The 2.0.x branch should start
to become very refined in scope of issues being fixed once 2.1 is
closing in. Naturally people will still use 2.0.x for sometime so we'll
be supporting it, but splitting the effort will only slow down the
overall progress. (typical release management stuff yada yada)

The moral is to vote for the issues you most want fixed, and call out
loudly regressions and blockers to updating as those are the priority.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Friday, March 07, 2008 8:11 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?

There are about 110 bugs slated in the "2.0.x" release category. As I
watch
2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not
touched.
My recommendation -- and hope -- is that someone could schedule a 2.0.11
and
2.0.12 based on 25 (swag) issues respectively from that big list. Those
are
the issues, it appears, that are long-standing and have been reported
early.


Paul

On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:

> On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox
<[EMAIL PROTECTED]>
> wrote:
>
> >  If this is the case for you, please reply and state the version
you're
> >  using and why (preferably referring to a Jira). We will use this
> >  information to prioritize issues for 2.0.10 and beyond.
>
> Some time after 2.0.5, Maven seems to have lost the ability to deal
> with multiple repositories containing different versions of the same
> plugin.
>
> For example:
> * a 'third-party' repository with maven-whatever-plugin version 1.0
final
> * a 'sandbox' repository with maven-whatever-plugin version
2.0-alpha-1
>
> I think someone brought this up on the dev list recently as a problem
> when trying to test a staged plugin release-- it would be the same
> situation, with the latest release of the plugin in the 'central' repo
> and the staged one in some other repo.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

It's the first I've heard but doesn't mean much. I have tested staged
plugins recently (including your staged stage plugin) and didn't see
anything.

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 8:25 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?

On Fri, Mar 7, 2008 at 6:09 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:

> Wendy: What happens in this case? Does it grab the wrong one or just
>  die? Is there a Jira?

Not sure if it's in JIRA, sorry.  It does not just pick the wrong one,
it dies with an error (and probably with corrupted local metadata.)

I briefly tried to reproduce it at home at some point in the past, but
wasn't able to (so I didn't open an issue.)  It's possible that
there's just something wrong in the repos at work, but whatever it is,
2.0.5 can deal with it and 2.0.7 can't.

We do have a couple of patches on top of the 2.0.5/2.0.7 tags, so
that's another possible culprit if no one else is seeing this.

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[EJ Ciramella]

Yep, I did that - I personally have build our codeline with 2.0.5 - 8
and most recently, 2.1.

The prab is when I upgrade myself and the build cluster, then when
someone tries to build locally and they didn't upgrade and I get this
angry horde with torches and pitchforks.
 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 8:13 PM
To: Maven Users List
Subject: RE: [POLL] Why are you not able to use the most recent maven
release?

Ok that's fair. If it ain't broke, don't fix it. 

Have you tried your builds on newer versions to make sure it would work?
There have been some differences between 2.0.5 & 2.0.6 that could
require prep work (and you may discover issues you didn't know you had):
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:48 PM
To: Maven Users List
Subject: RE: [POLL] Why are you not able to use the most recent maven
release?

We're currently stuck on 2.0.5 - the problem is getting an entire
organization to upgrade.  Aside from the, "it works better" response,
typically, there needs to be a financial reason explaining why we are
asking everyone to stop what they are doing and upgrade.

 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 4:45 PM
To: Maven Users List
Subject: [POLL] Why are you not able to use the most recent maven
release?

I get the sense that lots of people are using older versions of Maven
due to various regressions.  As we get closer to 2.1 alpha, we need to
ensure that we identify the regressions across the 2.0 line so that we
can make sure they are fixed in 2.1 and so that users can upgrade to a
recent 2.0.x before trying out 2.1.

 

If this is the case for you, please reply and state the version you're
using and why (preferably referring to a Jira). We will use this
information to prioritize issues for 2.0.10 and beyond.

 

Thanks.

 

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How do I access Tomcat 5x Manager from cargo

[Clifton]

This was the dumbest laziest question I've ever posted. All I had t do was
look in the tomcat base dir/conf/tomcat-users.xml to figure it out. By
default it uses admin with an empty password.

Clifton wrote:
> 
> What is the default "manager" username/password used by cargo when you
> have it download and install tomcat 5x? I get the container to start with
> the plugin set but it's totally useless if I can't deploy to it. Is there
> a better way to go about what I'm doing? I have a multi-module project
> with a couple of webapps and a J2ME midlet that needs deploying on a
> separate OTA Java webapp. The OTA is managed outside of the multi-module
> webapp. Right now I add the cargo plugin tag to the multi-module root pom
> with the zipurlinstaller stuff and I can get it to launch. I'm looking to
> be able to deploy the OTA to this launched instace from a separate cmd
> window and having no luck. Any suggestions?
> 
> 
> Clifton wrote:
>> 
>> I've killed about 45 minutes on a project that's way overdue. I'm
>> desparately trying to get cargo:start to allow cargo:deploy from
>> submodules in the same project. I run cargo:start and browse the
>> manager/html context from my browser and I'm prompted for authentication.
>> I've tried various username password combos and I can not view the
>> manager page. I've tried setting either/or and both
>> cargo.remote.username/cargo.remote.password, and cargo.servlet.users in
>> my pom but this doesn't work at all. I've even tried accessing manager
>> remotely after setting these properties. What am I doing wrong?
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-do-I-access-Tomcat-5x-Manager-from-cargo-tp15761449s177p15910015.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Why are you not able to use the most recent maven release?

[Wendy Smoak]

On Fri, Mar 7, 2008 at 6:09 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:

> Wendy: What happens in this case? Does it grab the wrong one or just
>  die? Is there a Jira?

Not sure if it's in JIRA, sorry.  It does not just pick the wrong one,
it dies with an error (and probably with corrupted local metadata.)

I briefly tried to reproduce it at home at some point in the past, but
wasn't able to (so I didn't open an issue.)  It's possible that
there's just something wrong in the repos at work, but whatever it is,
2.0.5 can deal with it and 2.0.7 can't.

We do have a couple of patches on top of the 2.0.5/2.0.7 tags, so
that's another possible culprit if no one else is seeing this.

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

Ok that's fair. If it ain't broke, don't fix it. 

Have you tried your builds on newer versions to make sure it would work?
There have been some differences between 2.0.5 & 2.0.6 that could
require prep work (and you may discover issues you didn't know you had):
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:48 PM
To: Maven Users List
Subject: RE: [POLL] Why are you not able to use the most recent maven
release?

We're currently stuck on 2.0.5 - the problem is getting an entire
organization to upgrade.  Aside from the, "it works better" response,
typically, there needs to be a financial reason explaining why we are
asking everyone to stop what they are doing and upgrade.

 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 4:45 PM
To: Maven Users List
Subject: [POLL] Why are you not able to use the most recent maven
release?

I get the sense that lots of people are using older versions of Maven
due to various regressions.  As we get closer to 2.1 alpha, we need to
ensure that we identify the regressions across the 2.0 line so that we
can make sure they are fixed in 2.1 and so that users can upgrade to a
recent 2.0.x before trying out 2.1.

 

If this is the case for you, please reply and state the version you're
using and why (preferably referring to a Jira). We will use this
information to prioritize issues for 2.0.10 and beyond.

 

Thanks.

 

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Knowing what artifact I need?

[Brian E. Fox]

The m2e plugin has an index of central that comes with it. It can also
access index updates and internal repo indexes via Nexus (proximity
replacement)

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:31 PM
To: Maven Users List
Subject: RE: Knowing what artifact I need?

Olivier:

I'm don't think those are quite what I'm talking about: I put
org.springframework.ejb into the search fields, and didn't get any
results (what I'm hoping this would return would be "spring-remote.jar",
which is where that package is). Am I using it wrong?

Brian:

Do you have any idea where the plugin gets its information from? Are
they keeping some kind of extra-fancy repository-plus?

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not an intended
recipient, please notify the sender and delete this message immediately.
Any views expressed in this message are those of the sender, not those
of any entity within the KBC Financial Products group of companies
(together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise,
on the part of KBC FP. It is not an offer (or solicitation of an offer)
of, or a recommendation to buy or sell, any financial product. Any
prices or other values included in this message are indicative only, and
do not necessarily represent current market prices, prices at which KBC
FP would enter into a transaction, or prices at which similar
transactions may be carried on KBC FP's own books. The information
contained in this message is provided "as is", without representations
or warranties, express or implied, of any kind. Past performance is not
indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

Wendy: What happens in this case? Does it grab the wrong one or just
die? Is there a Jira?

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 7:22 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?

On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:

>  If this is the case for you, please reply and state the version
you're
>  using and why (preferably referring to a Jira). We will use this
>  information to prioritize issues for 2.0.10 and beyond.

Some time after 2.0.5, Maven seems to have lost the ability to deal
with multiple repositories containing different versions of the same
plugin.

For example:
* a 'third-party' repository with maven-whatever-plugin version 1.0
final
* a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1

I think someone brought this up on the dev list recently as a problem
when trying to test a staged plugin release-- it would be the same
situation, with the latest release of the plugin in the 'central' repo
and the staged one in some other repo.

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Why are you not able to use the most recent maven release?

[Paul Benedict]

There are about 110 bugs slated in the "2.0.x" release category. As I watch
2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not touched.
My recommendation -- and hope -- is that someone could schedule a 2.0.11 and
2.0.12 based on 25 (swag) issues respectively from that big list. Those are
the issues, it appears, that are long-standing and have been reported early.


Paul

On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:

> On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]>
> wrote:
>
> >  If this is the case for you, please reply and state the version you're
> >  using and why (preferably referring to a Jira). We will use this
> >  information to prioritize issues for 2.0.10 and beyond.
>
> Some time after 2.0.5, Maven seems to have lost the ability to deal
> with multiple repositories containing different versions of the same
> plugin.
>
> For example:
> * a 'third-party' repository with maven-whatever-plugin version 1.0 final
> * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1
>
> I think someone brought this up on the dev list recently as a problem
> when trying to test a staged plugin release-- it would be the same
> situation, with the latest release of the plugin in the 'central' repo
> and the staged one in some other repo.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [POLL] Why are you not able to use the most recent maven release?

[Wendy Smoak]

On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:

>  If this is the case for you, please reply and state the version you're
>  using and why (preferably referring to a Jira). We will use this
>  information to prioritize issues for 2.0.10 and beyond.

Some time after 2.0.5, Maven seems to have lost the ability to deal
with multiple repositories containing different versions of the same
plugin.

For example:
* a 'third-party' repository with maven-whatever-plugin version 1.0 final
* a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1

I think someone brought this up on the dev list recently as a problem
when trying to test a staged plugin release-- it would be the same
situation, with the latest release of the plugin in the 'central' repo
and the staged one in some other repo.

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Why are you not able to use the most recent maven release?

[Barrie Treloar]

On Sat, Mar 8, 2008 at 9:18 AM, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> We're currently stuck on 2.0.5 - the problem is getting an entire
>  organization to upgrade.  Aside from the, "it works better" response,
>  typically, there needs to be a financial reason explaining why we are
>  asking everyone to stop what they are doing and upgrade.

You should be ok to mix, as long as you dont get bitten by outstanding bugs.

We moved to 2.0.7 to get the proxy:* stuff happening.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[EJ Ciramella]

Yeah, the first paragraph below doesn't work.  I created a pom that not
only has a properties section (with one property) but also has a profile
with the same property.

In another pom, I put a dependency on this first pom and tried
processing resources on a file that has this same one property.  Then on
the command line of this second pom, I type "mvn process-resources
-P" but it doesn't change the property inside
the one file with the one property (I can see it's getting "processed"
from src to target, the token isn't being expanded tho).

As far as that second example, it went right over my head.  Are you
suggesting that this property file should be completed manually and
installed in our repository?  My test project is really small (one file)
all truth be told, with ATG config files counted, we have hundreds.  The
one really tricky piece is for local development, people need to be able
to apply the profiles they have locally (in their settings.xml files).
The other part to this is we combine mulitple profiles to get a final
deployment configuration.  So it'd be something like:

Mvn install -Pbase,StackDefaults,serverclass

Where "base" contains things like memory settings for the compiler and
java docs/unit testing.
"StackDefaults" contains things like where java home is for all the
stacks
"serverclass" contains things specific to say an app server versus a db
server

I like this - more ideas!  I'm pouring over the documentation trying to
find something that allows this kind of "put in one place, share all
over" type treatment of properties.

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:51 PM
To: Maven Users List
Subject: RE: sharing properties between modules

I don't actually know if dependency POMs look at their profiles'
 elements or not. I guess not, from what you're
describing. Have you tried invoking the profile explicitly when you run
Maven? (e.g. "mvn -P profileName deploy") The dependency POM's profiles
may still be available, even if they're not auto-activated.

Also, I think Wayne was suggesting actually writing config files with
the properties, packaging them into an archive, and then using that as a
dependency. (Sorry, Wayne, if I'm misunderstanding your advice.) Many
frameworks will allow you to do an #include-style import of settings
from other files, so perhaps you could have your bottom-level projects
depend on that archive, and point to its config files.

~DVA

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:28 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So there's no way to keep the properties in various profiles (all within
a pom) and just put a dependency on that pom (I think the dependency
part works, but it doesn't seem to pick up the activated profile)? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:24 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not an intended
recipient, please notify the sender and delete this message immediately.
Any views expressed in this message are those of the sender, not those
of any entity within the KBC Financial Products group of companies
(together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise,
on the part of KBC FP. It is not an offer (or solicitation of an offer)
of, or a recommendation to buy or sell, any financial product. Any
prices or other values included in this message are indicative only, and
do not necessarily represent current market prices, prices at which KBC
FP would enter into a transaction, or prices at which similar
transactions may be carried on KBC FP's own books. The information
contained in this message is provided "as is", without representations
or warranties, express or implied, of any kind. Past performance is not
indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[Allen, Daniel]

I don't actually know if dependency POMs look at their profiles'
 elements or not. I guess not, from what you're
describing. Have you tried invoking the profile explicitly when you run
Maven? (e.g. "mvn -P profileName deploy") The dependency POM's profiles
may still be available, even if they're not auto-activated.

Also, I think Wayne was suggesting actually writing config files with
the properties, packaging them into an archive, and then using that as a
dependency. (Sorry, Wayne, if I'm misunderstanding your advice.) Many
frameworks will allow you to do an #include-style import of settings
from other files, so perhaps you could have your bottom-level projects
depend on that archive, and point to its config files.

~DVA

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:28 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So there's no way to keep the properties in various profiles (all within
a pom) and just put a dependency on that pom (I think the dependency
part works, but it doesn't seem to pick up the activated profile)? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:24 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [ANN] Maven Assembly Plugin 2.2-beta-2 Released

[Mark Diggory]

We are having problems with mavenn 2.0.8 and maven-assebly-plugin-2.2-beta-2
we can't seem to resolve the new ${modules.artifactId} properties...

for instance...




*:war:*



org.dspace:dspace-oai-webapp


false
webapps
   ${module.artifactId
}

fails to return the name of the current module being processed. This is with
a fresh download of maven 2.0.8 and a fresh recreation of my local
repository that I tested today.  All the modules get dumped over top of
eachother and are not separated by their artifactId.  If I remove the
outputFileNameMapping, they do get separated and the documented default

 ${module.artifactId}-${module.version}${dashClassifier?}.${module.extension
}.

gets used appropriately.

thanks for any advice,
-Mark

On Fri, Feb 29, 2008 at 4:04 PM, John Casey <[EMAIL PROTECTED]> wrote:

> The Maven team is pleased to announce the release of the Maven
> Assembly Plugin, version 2.2-beta-2
>
> This plugin is used to build custom archives, such as those used to
> distribute project releases.
>
> http://maven.apache.org/plugins/maven-assembly-plugin/
>
> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration (recommended):
>
> 
>  org.apache.maven.plugins
>  maven-assembly-plugin
>  2.2-beta-2
> 
>
>
> Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2
>
> (See: http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11126&styleName=Text&version=14027)
>
>
> ** Bug
> * [MASSEMBLY-121] - Custom manifest attributres are ignored.
> * [MASSEMBLY-129] - BaseDirectory Ignored When Including a
> Repository
> * [MASSEMBLY-156] - appendAssemblyId cannot be false
> * [MASSEMBLY-162] - In a multiproject environment, assembly
> takes wrong dependencies
> * [MASSEMBLY-163] - In a multiproject environment Assembly
> causes many unneded rebuilds
> * [MASSEMBLY-178] - filtering doesn't read filter files
> * [MASSEMBLY-179] - Assembled jar includes artifact names in path
> * [MASSEMBLY-180] - A bug in artifact filtering ( maven-common-
> artifact-filters )
> * [MASSEMBLY-183] - assembly:attached does not work with filter-
> ERROR: Cannot override read-only parameter
> * [MASSEMBLY-184] - components are not interpolated - i.e., $
> {params} are not substituted
> * [MASSEMBLY-188] - manifestEntries are not set in resulting jar
> * [MASSEMBLY-189] - plugin not correctly interpolating POM
> variables like project.build.directory
> * [MASSEMBLY-194] - unnecessary dependency expansion regression
> * [MASSEMBLY-195] - unpackOptions ignored
> * [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no
> longer included in
> * [MASSEMBLY-208] - Assembly plugin does not resolve version
> ranges correctly
> * [MASSEMBLY-210] - repository does not include the parent pom
> * [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong
> targetNamespace
> * [MASSEMBLY-214] - java.lang.NullPointerException: version was
> null for junit:junit
> * [MASSEMBLY-221] - Filtering doesn't work when a file matches
> both a  and a 
> * [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor
> interpolation
> * [MASSEMBLY-223] - 2-nd  element of
> : doesn't work
> * [MASSEMBLY-225] - Not a v4.0.0 POM
> * [MASSEMBLY-226] - Filters as read-only parameter can break the
> assembly build of a multi-module project
> * [MASSEMBLY-232] - NPE - MASSEMBLY-222 fix broken?
> * [MASSEMBLY-233] - Custom ContainerDescriptorHandler
> integration tests don't work in Maven 2.0.7
> * [MASSEMBLY-234] - Artifacts not deployed
> * [MASSEMBLY-235] - dependencySet ignores dependency management
> * [MASSEMBLY-250] - Trunk of assembly plugin broken and not in
> synch with deployed 2.2-beta2-SNAPSHOT ?
> * [MASSEMBLY-254] - Not a v4.0.0 POM Still an Issue
> * [MASSEMBLY-257] - OutOfMemoryError when assembling large
> binary file
> * [MASSEMBLY-262] - unit fail in trunk on windows (need upgrade
> of plexus-utils)
> * [MASSEMBLY-266] - Property expansion does not work for $
> {project.build.finalName} in descriptor file
> * [MASSEMBLY-277] - NullPointerException
> * [MASSEMBLY-282] - Fix failing IT no-appendAssemblyId-no-
> classifier
>
> ** Improvement
> * [MASSEMBLY-136] - outputDirectory to support absolute paths
> * [MASSEMBLY-142] - Should be able to use artifact version as
> variable in 
> * [MASSEMBLY-152] - Support Ant token
> * [MASSEMBLY-154] - FileSet does not support filtering
> * [MASSEMBLY-182] - document behavior when two sources selected
> for single archived file
> * [MASSEMBLY-258] - Sync usage guide with Maven standard
> directory layout
> * [MASSEMBLY-261] - Use plexus-archiver 1.0-alpha-10
> * [MASSEMBLY-267] 

RE: sharing properties between modules

[EJ Ciramella]

So there's no way to keep the properties in various profiles (all within
a pom) and just put a dependency on that pom (I think the dependency
part works, but it doesn't seem to pick up the activated profile)? 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:24 PM
To: Maven Users List
Subject: RE: sharing properties between modules

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

On 3/7/08, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> The problem is that there is already a parent pom defined for say, app
1
> listed below.  App 2 lives off in its own structure with no parent
> defined (and can't use app 1's parent pom as it would break
> config/deploy related items).
>
> Is there a way I can just have a "config" project (sort of like
> "config") that would place properties into the
> local repository for use in other, non-related projects?
>
> -Original Message-
> From: Allen, Daniel [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:48 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> If you're talking about just properties and not any code or classes,
> then perhaps you could just use variables and filtering in the
> configuration files, and then have a profile that's used in both
builds?
>
> I would suggest perhaps a sort of token parent project whose POM
doesn't
> really contain anything except for a  element that defines
> these shared values, and then they will be available for 
> elements in your projects' POMs. Of course, I'm still new at this, so
> I'd say get a second opinion on that.
>
> ~Dan Allen
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:47 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> So we have app1 and it has a property like, db.username.  App2 needs
to
> connect to the same database, but doesn't share a parent.
>
> For example, app1 loads data into a db, app2 displays said data via a
> website.  There is no common/shared code other than the data access
> layer.
>
> How would you do a "grand parent" type dependency?
>
> --
> This message may contain confidential, proprietary, or legally
> privileged information. No confidentiality or privilege is waived by
any
> transmission to an unintended recipient. If you are not an intended
> recipient, please notify the sender and delete this message
immediately.
> Any views expressed in this message are those of the sender, not those
> of any entity within the KBC Financial Products group of companies
> (together referred to as "KBC FP").
>
> This message does not create any obligation, contractual or otherwise,
> on the part of KBC FP. It is not an offer (or solicitation of an
offer)
> of, or a recommendation to buy or sell, any financial product. Any
> prices or other values included in this message are indicative only,
and
> do not necessarily represent current market prices, prices at which
KBC
> FP would enter into a transaction, or prices at which similar
> transactions may be carried on KBC FP's own books. The information
> contained in this message is provided "as is", without representations
> or warranties, express or implied, of any kind. Past performance is
not
> indicative of future returns.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[EJ Ciramella]

Wait, package what?  99% of our properties are stored in profiles.

When we want to generate the configuration for a particular stack, we
use the -P, convention. 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 6:12 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

On 3/7/08, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> The problem is that there is already a parent pom defined for say, app
1
> listed below.  App 2 lives off in its own structure with no parent
> defined (and can't use app 1's parent pom as it would break
> config/deploy related items).
>
> Is there a way I can just have a "config" project (sort of like
> "config") that would place properties into the
> local repository for use in other, non-related projects?
>
> -Original Message-
> From: Allen, Daniel [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:48 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> If you're talking about just properties and not any code or classes,
> then perhaps you could just use variables and filtering in the
> configuration files, and then have a profile that's used in both
builds?
>
> I would suggest perhaps a sort of token parent project whose POM
doesn't
> really contain anything except for a  element that defines
> these shared values, and then they will be available for 
> elements in your projects' POMs. Of course, I'm still new at this, so
> I'd say get a second opinion on that.
>
> ~Dan Allen
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:47 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> So we have app1 and it has a property like, db.username.  App2 needs
to
> connect to the same database, but doesn't share a parent.
>
> For example, app1 loads data into a db, app2 displays said data via a
> website.  There is no common/shared code other than the data access
> layer.
>
> How would you do a "grand parent" type dependency?
>
> --
> This message may contain confidential, proprietary, or legally
> privileged information. No confidentiality or privilege is waived by
any
> transmission to an unintended recipient. If you are not an intended
> recipient, please notify the sender and delete this message
immediately.
> Any views expressed in this message are those of the sender, not those
> of any entity within the KBC Financial Products group of companies
> (together referred to as "KBC FP").
>
> This message does not create any obligation, contractual or otherwise,
> on the part of KBC FP. It is not an offer (or solicitation of an
offer)
> of, or a recommendation to buy or sell, any financial product. Any
> prices or other values included in this message are indicative only,
and
> do not necessarily represent current market prices, prices at which
KBC
> FP would enter into a transaction, or prices at which similar
> transactions may be carried on KBC FP's own books. The information
> contained in this message is provided "as is", without representations
> or warranties, express or implied, of any kind. Past performance is
not
> indicative of future returns.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: sharing properties between modules

[Wayne Fay]

Sure. Just package it as a jar, and use the dependency plugin to
unpack its contents where you need them in your related projects.

Wayne

On 3/7/08, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> The problem is that there is already a parent pom defined for say, app 1
> listed below.  App 2 lives off in its own structure with no parent
> defined (and can't use app 1's parent pom as it would break
> config/deploy related items).
>
> Is there a way I can just have a "config" project (sort of like
> "config") that would place properties into the
> local repository for use in other, non-related projects?
>
> -Original Message-
> From: Allen, Daniel [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:48 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> If you're talking about just properties and not any code or classes,
> then perhaps you could just use variables and filtering in the
> configuration files, and then have a profile that's used in both builds?
>
> I would suggest perhaps a sort of token parent project whose POM doesn't
> really contain anything except for a  element that defines
> these shared values, and then they will be available for 
> elements in your projects' POMs. Of course, I'm still new at this, so
> I'd say get a second opinion on that.
>
> ~Dan Allen
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 5:47 PM
> To: Maven Users List
> Subject: RE: sharing properties between modules
>
> So we have app1 and it has a property like, db.username.  App2 needs to
> connect to the same database, but doesn't share a parent.
>
> For example, app1 loads data into a db, app2 displays said data via a
> website.  There is no common/shared code other than the data access
> layer.
>
> How would you do a "grand parent" type dependency?
>
> --
> This message may contain confidential, proprietary, or legally
> privileged information. No confidentiality or privilege is waived by any
> transmission to an unintended recipient. If you are not an intended
> recipient, please notify the sender and delete this message immediately.
> Any views expressed in this message are those of the sender, not those
> of any entity within the KBC Financial Products group of companies
> (together referred to as "KBC FP").
>
> This message does not create any obligation, contractual or otherwise,
> on the part of KBC FP. It is not an offer (or solicitation of an offer)
> of, or a recommendation to buy or sell, any financial product. Any
> prices or other values included in this message are indicative only, and
> do not necessarily represent current market prices, prices at which KBC
> FP would enter into a transaction, or prices at which similar
> transactions may be carried on KBC FP's own books. The information
> contained in this message is provided "as is", without representations
> or warranties, express or implied, of any kind. Past performance is not
> indicative of future returns.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[EJ Ciramella]

The problem is that there is already a parent pom defined for say, app 1
listed below.  App 2 lives off in its own structure with no parent
defined (and can't use app 1's parent pom as it would break
config/deploy related items).

Is there a way I can just have a "config" project (sort of like
"config") that would place properties into the
local repository for use in other, non-related projects?

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:48 PM
To: Maven Users List
Subject: RE: sharing properties between modules

If you're talking about just properties and not any code or classes,
then perhaps you could just use variables and filtering in the
configuration files, and then have a profile that's used in both builds?

I would suggest perhaps a sort of token parent project whose POM doesn't
really contain anything except for a  element that defines
these shared values, and then they will be available for 
elements in your projects' POMs. Of course, I'm still new at this, so
I'd say get a second opinion on that.

~Dan Allen

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:47 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So we have app1 and it has a property like, db.username.  App2 needs to
connect to the same database, but doesn't share a parent.

For example, app1 loads data into a db, app2 displays said data via a
website.  There is no common/shared code other than the data access
layer.

How would you do a "grand parent" type dependency?

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not an intended
recipient, please notify the sender and delete this message immediately.
Any views expressed in this message are those of the sender, not those
of any entity within the KBC Financial Products group of companies
(together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise,
on the part of KBC FP. It is not an offer (or solicitation of an offer)
of, or a recommendation to buy or sell, any financial product. Any
prices or other values included in this message are indicative only, and
do not necessarily represent current market prices, prices at which KBC
FP would enter into a transaction, or prices at which similar
transactions may be carried on KBC FP's own books. The information
contained in this message is provided "as is", without representations
or warranties, express or implied, of any kind. Past performance is not
indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[Allen, Daniel]

If you're talking about just properties and not any code or classes,
then perhaps you could just use variables and filtering in the
configuration files, and then have a profile that's used in both builds?

I would suggest perhaps a sort of token parent project whose POM doesn't
really contain anything except for a  element that defines
these shared values, and then they will be available for 
elements in your projects' POMs. Of course, I'm still new at this, so
I'd say get a second opinion on that.

~Dan Allen

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 5:47 PM
To: Maven Users List
Subject: RE: sharing properties between modules

So we have app1 and it has a property like, db.username.  App2 needs to
connect to the same database, but doesn't share a parent.

For example, app1 loads data into a db, app2 displays said data via a
website.  There is no common/shared code other than the data access
layer.

How would you do a "grand parent" type dependency?

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [POLL] Why are you not able to use the most recent maven release?

[EJ Ciramella]

We're currently stuck on 2.0.5 - the problem is getting an entire
organization to upgrade.  Aside from the, "it works better" response,
typically, there needs to be a financial reason explaining why we are
asking everyone to stop what they are doing and upgrade.

 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 4:45 PM
To: Maven Users List
Subject: [POLL] Why are you not able to use the most recent maven
release?

I get the sense that lots of people are using older versions of Maven
due to various regressions.  As we get closer to 2.1 alpha, we need to
ensure that we identify the regressions across the 2.0 line so that we
can make sure they are fixed in 2.1 and so that users can upgrade to a
recent 2.0.x before trying out 2.1.

 

If this is the case for you, please reply and state the version you're
using and why (preferably referring to a Jira). We will use this
information to prioritize issues for 2.0.10 and beyond.

 

Thanks.

 

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: sharing properties between modules

[EJ Ciramella]

So we have app1 and it has a property like, db.username.  App2 needs to
connect to the same database, but doesn't share a parent.

For example, app1 loads data into a db, app2 displays said data via a
website.  There is no common/shared code other than the data access
layer.

How would you do a "grand parent" type dependency?


-Original Message-
From: Olivier Dehon [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 4:50 PM
To: Maven Users List
Subject: Re: sharing properties between modules

Maybe they can share a grand-parent?

If they share properties, they are surely related somehow, no?

-Olivier

On Fri, 2008-03-07 at 16:50 -0500, EJ Ciramella wrote:
> How are people sharing common (truly) properties between two detached
> modules.  
>  
> Example, module A and module B need foo=bar.  It's imperative that
both
> modules have the same resolution yet they don't share a parent.
>  
> How do you put foo=bar in one place and see to it that both get it
> resolved (without putting it in settings.xml etc).


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mvn environment variable in debian etch

[�rico]

I trying to set mvn environment variable in etch 

I already have JAVA_HOME configured in /etc/profile as
follows :

JAVA_HOME=/opt/java/jdk1.6.0_04
JRE_HOME=/opt/jre1.6.0_04
M2_HOME=/opt/apache-maven-2.0.8
M2=$M2_HOME/bin
PATH=$PATH:$JAVA_HOME/bin
PATH=$PATH:$M2
export PATH

javac command is ok

running echo $JAVA_HOME I have:
/opt/java/jdk1.6.0_04

running echo $M2 variable I have:
/opt/apache-maven-2.0.8/bin

when I run mvn in console I receive the error :
Error: JAVA_HOME is not defined correctly.
  We cannot execute java







  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Knowing what artifact I need?

[Allen, Daniel]

Olivier:

I'm don't think those are quite what I'm talking about: I put
org.springframework.ejb into the search fields, and didn't get any
results (what I'm hoping this would return would be "spring-remote.jar",
which is where that package is). Am I using it wrong?

Brian:

Do you have any idea where the plugin gets its information from? Are
they keeping some kind of extra-fancy repository-plus?

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[POLL] Why are you not able to use the most recent maven release?

[Brian E. Fox]

I get the sense that lots of people are using older versions of Maven
due to various regressions.  As we get closer to 2.1 alpha, we need to
ensure that we identify the regressions across the 2.0 line so that we
can make sure they are fixed in 2.1 and so that users can upgrade to a
recent 2.0.x before trying out 2.1.

 

If this is the case for you, please reply and state the version you're
using and why (preferably referring to a Jira). We will use this
information to prioritize issues for 2.0.10 and beyond.

 

Thanks.

 

 

Re: sharing properties between modules

[Olivier Dehon]

Maybe they can share a grand-parent?

If they share properties, they are surely related somehow, no?

-Olivier

On Fri, 2008-03-07 at 16:50 -0500, EJ Ciramella wrote:
> How are people sharing common (truly) properties between two detached
> modules.  
>  
> Example, module A and module B need foo=bar.  It's imperative that both
> modules have the same resolution yet they don't share a parent.
>  
> How do you put foo=bar in one place and see to it that both get it
> resolved (without putting it in settings.xml etc).


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

sharing properties between modules

[EJ Ciramella]

How are people sharing common (truly) properties between two detached
modules.  
 
Example, module A and module B need foo=bar.  It's imperative that both
modules have the same resolution yet they don't share a parent.
 
How do you put foo=bar in one place and see to it that both get it
resolved (without putting it in settings.xml etc).

RE: Knowing what artifact I need?

[Brian E. Fox]

The new M2E plugin demoed [1] a few weeks ago had this built in and was
very sweet. They said it would be released soon.

[1] http://blogs.sonatype.com/jvanzyl/2008/02/10/120268422.html

-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 4:18 PM
To: Maven Users List
Subject: Knowing what artifact I need?

Hi all.

I have a general sort of question about writing POMs. When figuring out
what dependencies I need, I frequently come up against the fact that the
web at large refers to package names when talking about class usage,
whereas Maven refers to the name of the jar file that it comes in. So
sometimes I have to go searching for what the proper artifactId is, even
if I know where I could go and manually download the JAR file. For
example, using Spring, I was getting ClassNotFoundExceptions for
org.springframework.scripting.[various classes].  But the artifact that
I needed was not called scripting, it was called spring-support.

This isn't a huge deal, just some extra time on Google, but it would be
convenient if there were some kind of database that mapped actual Java
packages to the names of the JAR artifacts that contain them. 

Does anything like that exist currently?
~Dan Allen

-- 
This message may contain confidential, proprietary, or legally
privileged information. No confidentiality or privilege is waived by any
transmission to an unintended recipient. If you are not an intended
recipient, please notify the sender and delete this message immediately.
Any views expressed in this message are those of the sender, not those
of any entity within the KBC Financial Products group of companies
(together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise,
on the part of KBC FP. It is not an offer (or solicitation of an offer)
of, or a recommendation to buy or sell, any financial product. Any
prices or other values included in this message are indicative only, and
do not necessarily represent current market prices, prices at which KBC
FP would enter into a transaction, or prices at which similar
transactions may be carried on KBC FP's own books. The information
contained in this message is provided "as is", without representations
or warranties, express or implied, of any kind. Past performance is not
indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Knowing what artifact I need?

[Olivier Dehon]

You can try repository indexes like:
http://mvnrepository.com
or
http://mvnindex.org

-Olivier
On Fri, 2008-03-07 at 16:18 -0500, Allen, Daniel wrote:
> Hi all.
> 
> I have a general sort of question about writing POMs. When figuring out
> what dependencies I need, I frequently come up against the fact that the
> web at large refers to package names when talking about class usage,
> whereas Maven refers to the name of the jar file that it comes in. So
> sometimes I have to go searching for what the proper artifactId is, even
> if I know where I could go and manually download the JAR file. For
> example, using Spring, I was getting ClassNotFoundExceptions for
> org.springframework.scripting.[various classes].  But the artifact that
> I needed was not called scripting, it was called spring-support.
> 
> This isn't a huge deal, just some extra time on Google, but it would be
> convenient if there were some kind of database that mapped actual Java
> packages to the names of the JAR artifacts that contain them. 
> 
> Does anything like that exist currently?
> ~Dan Allen
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Knowing what artifact I need?

[Allen, Daniel]

Hi all.

I have a general sort of question about writing POMs. When figuring out
what dependencies I need, I frequently come up against the fact that the
web at large refers to package names when talking about class usage,
whereas Maven refers to the name of the jar file that it comes in. So
sometimes I have to go searching for what the proper artifactId is, even
if I know where I could go and manually download the JAR file. For
example, using Spring, I was getting ClassNotFoundExceptions for
org.springframework.scripting.[various classes].  But the artifact that
I needed was not called scripting, it was called spring-support.

This isn't a huge deal, just some extra time on Google, but it would be
convenient if there were some kind of database that mapped actual Java
packages to the names of the JAR artifacts that contain them. 

Does anything like that exist currently?
~Dan Allen

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven Assembly for MultiModule project

[Brian E. Fox]

Check out the free book[1], this can be read in a few hours and should
get you up to speed quickly.

[1] http://www.sonatype.com/book

-Original Message-
From: krishnan.1000 [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 1:14 PM
To: users@maven.apache.org
Subject: Re: Maven Assembly for MultiModule project


Hi Wayne,

I can not help it. I just joined a project to replace a guy who left the
project. So I am on an accelerated learning curve.

Thanks,

Karthik

Wayne Fay wrote:
> 
> It sounds like you're jumping in to complex builds with Maven2 without
> really understanding how things work at a basic level. As an example
> of this, you're running mvn install:install-file etc on what seems to
> be a Maven project -- so you really only need to type "mvn install".
> The same thing goes for your comment about "adding dependencies in all
> the pom.xml even if they have been specified in the parent." So I
> think you've skipped some important steps in your learning process.
> 
> I would go back to the beginning and work your way through Better
> Builds With Maven (free pdf book from devzuz.com) and Maven: The
> Definitive Guide (from sonatype.com). The books are organized such
> that you start out learning how Maven works internally (generally),
> and then they lead through some basic examples and finally take you
> through much more involved examples.
> 
> You should be able to do this in just 1 or 2 days, and I think you
> really need to invest this time now rather than attempting to hack
> your poms and assemblies just to make it work.
> 
> Wayne
> 
> On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>
>>  
>>
>>   
>>maven-compiler-plugin
>>2.1-20080129.223043-7
>>
>>  1.5
>>  1.5
>>
>>  
>>  
>> 
>>org.apache.maven.plugins
>>maven-surefire-plugin
>>2.4
>>
>>  
>>testng.xml
>>  
>>
>>  
>>  
>>maven-assembly-plugin
>>
>>  
>>jar-with-dependencies
>>  
>>  
>>
>>  true
>>  com.jbe.core.Foo
>>
>>  
>>
>>  
>>
>>  
>>
>> 
>>../pom.xml
>>0.1
>>foo-foo
>>foo
>>  
>>
>> I also find that I have to include foo-b in my foo's pom.xml in order
to
>> compile even though, foo-a is dependent on foo-b and therefore must
>> compile
>> foo-b before foo-a.
>> 
>>  
>>  foo
>>  foo-a
>>  ${project.version}
>>  compile
>>
>> 
>>  foo
>>  foo-b
>>  ${project.version}
>>  compile
>> 
>> /dependencies>
>>
>> In addition, I have to add dependencies in all the pom.xml even if
they
>> have
>> been specified in the parent pom.xml.
>>
>> Thanks,
>>
>> Karthik Krishnan
>>
>>
>>
>> krishnan.1000 wrote:
>> >
>> > Hi Wayne,
>> >
>> > I am sorry Wayne. I should have been more specific on the post. To
>> answer
>> > your first comment,  and I do not wish to sound rude, but if I knew
>> what I
>> > was doing wrong, I would not have posted in the first place.
>> >
>> > 2. I am trying to assemble a jar of module Foo and Bar . I wish
that I
>> > create an executable jar with a defined main class and a classpath
>> added
>> > to MANIFEST.MF. So basically i want the to create foo.jar and
bar.jar
>> > containing all the dependencies.
>> >
>> > 3. I find  that if i make the changes in Foo-A or FooB java
classes,
>> and
>> > if i execute a mvn assembly:assembly, it does not build the FOO-A
or
>> FOO-B
>> > in the .m2 repository before building Foo and Bar successfully
again I
>> > have to get around that by doing the following
>> >
>> > mvn install:install-file
>> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar
>> -DgroupId=project
>> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar
-DgeneratePOM=true,
>> the
>> > solution I found by doing a search on one of the posts.
>> >
>> > and again for foo-b. I would like to avoid that and just have mvn
>> > assembly:assembly do all this before creating foo.jar and bar.jar.
>> >
>> >
>> >
>> > Wayne Fay wrote:
>> >>
>> >> This list really works better if you post what you've done and
then
>> >> tell us why its not working the way you wanted, or an error
message
>> >> you got, etc. Looking at what you sent, I have no idea if it is
>> >> working how you expect or not.
>> >>
>> >> Sending your pom and assembly.xml file is probably not going to
give
>> >> you the results you are hoping for. So, send a reply and be more
clear
>> >> about what you've got vs what you want etc.
>> >>
>> >> Wayne
>> >>
>> >> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I am a Maven newbie and I hope this is not a stupid question.  I
am
>> >>> trying
>> >>> to create two Maven assembly jars for modules Foo and Bar. My
project
>> --
>> >>> |
>> >>> |--- Bar
>> >>> |--- Foo
>> >>> |Foo-A
>> >>> |

Re: How do I supress repository update?

[Wayne Fay]

Declare the repositories you are using in settings.xml and set update
flag to "never".

Other options are mvn -o to run offline, or mvn -npu to suppress
plugin updates. Run mvn -h to see more choices.

Wayne

On 3/7/08, X23G8c <[EMAIL PROTECTED]> wrote:
>
> I am making changes to the build process.  In order to isolate problems due
> to these changes from problems due to upgrading repository, I would like
> things arranged so that maven postpones its repository check cycle
> indefinitely.  Then, once I am happy with the updates, I would like to force
> the repository check to run so that I know that the build works with the
> latest components.
>
> How would I do this?
>
> --
> View this message in context: 
> http://www.nabble.com/How-do-I-supress-repository-update--tp15902255s177p15902255.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How do I supress repository update?

[X23G8c]

I am making changes to the build process.  In order to isolate problems due
to these changes from problems due to upgrading repository, I would like
things arranged so that maven postpones its repository check cycle
indefinitely.  Then, once I am happy with the updates, I would like to force
the repository check to run so that I know that the build works with the
latest components.

How would I do this?

-- 
View this message in context: 
http://www.nabble.com/How-do-I-supress-repository-update--tp15902255s177p15902255.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Assembly for MultiModule project

[krishnan.1000]

Hi Wayne,

I can not help it. I just joined a project to replace a guy who left the
project. So I am on an accelerated learning curve.

Thanks,

Karthik

Wayne Fay wrote:
> 
> It sounds like you're jumping in to complex builds with Maven2 without
> really understanding how things work at a basic level. As an example
> of this, you're running mvn install:install-file etc on what seems to
> be a Maven project -- so you really only need to type "mvn install".
> The same thing goes for your comment about "adding dependencies in all
> the pom.xml even if they have been specified in the parent." So I
> think you've skipped some important steps in your learning process.
> 
> I would go back to the beginning and work your way through Better
> Builds With Maven (free pdf book from devzuz.com) and Maven: The
> Definitive Guide (from sonatype.com). The books are organized such
> that you start out learning how Maven works internally (generally),
> and then they lead through some basic examples and finally take you
> through much more involved examples.
> 
> You should be able to do this in just 1 or 2 days, and I think you
> really need to invest this time now rather than attempting to hack
> your poms and assemblies just to make it work.
> 
> Wayne
> 
> On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>
>>  
>>
>>   
>>maven-compiler-plugin
>>2.1-20080129.223043-7
>>
>>  1.5
>>  1.5
>>
>>  
>>  
>> 
>>org.apache.maven.plugins
>>maven-surefire-plugin
>>2.4
>>
>>  
>>testng.xml
>>  
>>
>>  
>>  
>>maven-assembly-plugin
>>
>>  
>>jar-with-dependencies
>>  
>>  
>>
>>  true
>>  com.jbe.core.Foo
>>
>>  
>>
>>  
>>
>>  
>>
>> 
>>../pom.xml
>>0.1
>>foo-foo
>>foo
>>  
>>
>> I also find that I have to include foo-b in my foo's pom.xml in order to
>> compile even though, foo-a is dependent on foo-b and therefore must
>> compile
>> foo-b before foo-a.
>> 
>>  
>>  foo
>>  foo-a
>>  ${project.version}
>>  compile
>>
>> 
>>  foo
>>  foo-b
>>  ${project.version}
>>  compile
>> 
>> /dependencies>
>>
>> In addition, I have to add dependencies in all the pom.xml even if they
>> have
>> been specified in the parent pom.xml.
>>
>> Thanks,
>>
>> Karthik Krishnan
>>
>>
>>
>> krishnan.1000 wrote:
>> >
>> > Hi Wayne,
>> >
>> > I am sorry Wayne. I should have been more specific on the post. To
>> answer
>> > your first comment,  and I do not wish to sound rude, but if I knew
>> what I
>> > was doing wrong, I would not have posted in the first place.
>> >
>> > 2. I am trying to assemble a jar of module Foo and Bar . I wish that I
>> > create an executable jar with a defined main class and a classpath
>> added
>> > to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
>> > containing all the dependencies.
>> >
>> > 3. I find  that if i make the changes in Foo-A or FooB java classes,
>> and
>> > if i execute a mvn assembly:assembly, it does not build the FOO-A or
>> FOO-B
>> > in the .m2 repository before building Foo and Bar successfully again I
>> > have to get around that by doing the following
>> >
>> > mvn install:install-file
>> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar
>> -DgroupId=project
>> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true,
>> the
>> > solution I found by doing a search on one of the posts.
>> >
>> > and again for foo-b. I would like to avoid that and just have mvn
>> > assembly:assembly do all this before creating foo.jar and bar.jar.
>> >
>> >
>> >
>> > Wayne Fay wrote:
>> >>
>> >> This list really works better if you post what you've done and then
>> >> tell us why its not working the way you wanted, or an error message
>> >> you got, etc. Looking at what you sent, I have no idea if it is
>> >> working how you expect or not.
>> >>
>> >> Sending your pom and assembly.xml file is probably not going to give
>> >> you the results you are hoping for. So, send a reply and be more clear
>> >> about what you've got vs what you want etc.
>> >>
>> >> Wayne
>> >>
>> >> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I am a Maven newbie and I hope this is not a stupid question.  I am
>> >>> trying
>> >>> to create two Maven assembly jars for modules Foo and Bar. My project
>> --
>> >>> |
>> >>> |--- Bar
>> >>> |--- Foo
>> >>> |Foo-A
>> >>> |--- Foo-B
>> >>>
>> >>>
>> >>> This is my project structure. In this project, FOO-A is dependent on
>> >>> Foo-B
>> >>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
>> >>> jars
>> >>> for both the for both Foo and Bar modules. Can you please help me?
>> >>>
>> >>> My project pom is as follows.
>> >>>

RE: Archetypes and plugins

[Brian E. Fox]

The archetype packaging brings its own lifecycle bindings, but you
should be able to bind things normally. If you are trying to do this
during create-from-project, it probably isn't possible.

-Original Message-
From: Ian Godman [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 06, 2008 4:56 PM
To: users@maven.apache.org
Subject: Archetypes and plugins

I am working on an Archetype and would like to run a plugin to perform
tasks
during the create process.

Initially this is the eclipse plugin to make an eclipse project but I
also
need to do some other processing using an as yet unwritten plugin.

Is this possible? Any alternatives?

Ian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven upgrade breaks testcases

[Brian E. Fox]

Check the release notes for 2.0.8, one change to tests was that the classpath 
now puts test stuff first.

-Original Message-
From: Arash Bizhan zadeh [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 11:25 AM
To: Maven Users List
Subject: Maven upgrade breaks testcases

I upgraded maven from 2.0.5 to 2.0.8 and faced a big surprise. My test cases
does not run anymore! The error message is :

org.hibernate.HibernateException: createCriteria is not valid without active
transaction
at
org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke
(ThreadLocalSessionContext.java:297)
at $Proxy6.createCriteria(Unknown Source)
at ca.cbc.whatson.dao.ProgramHome.findByName(ProgramHome.java:198)
at ca.cbc.whatson.util.DigestTestXSL.getEpisodes(DigestTestXSL.java
:181)
at ca.cbc.whatson.test.dao.FeedData.feedEpisodes(FeedData.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java
:604)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:470)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830)
at org.testng.internal.TestMethodWorker.invokeTestMethods(
TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java
:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:678)
at org.testng.TestRunner.privateRun(TestRunner.java:624)
at org.testng.TestRunner.run(TestRunner.java:495)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:300)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275)
at org.testng.SuiteRunner.run(SuiteRunner.java:190)
at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792)
at org.testng.TestNG.runSuitesLocally(TestNG.java:765)
at org.testng.TestNG.run(TestNG.java:699)
at org.apache.maven.surefire.testng.TestNGExecutor.run(
TestNGExecutor.java:74)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)

It was working perfectly file with 2.0.5! I guess that it is happened
because of an upgrade in one of the plugins, but I don't know how to find
out which version of the plugins are used and how.
Could somebody help me?


-- 
You can not depend on your eyes when your imagination is out of focus.

excluding files from jar doesn't work completely well - maven-jar-plugin 2.2

[Patrizio Munzi]

Hi All,

I'm trying to exclude some files from the built jar by using the 
maven-jar-plugin exclude feature.


Here's my configuration:


   **/*.properties
   **/*.xml
   **/*.xsd


Although all the specified files are actually excluded from the deployed 
jar, the directory paths of the excluded files are still created into 
the jar.


I mean, if I have the following files under the resources directory:

resources/log4j.properties
resources/xml/file.xml
resources/xml/schema/schema.xsd

These files won't be included in the built jar, but I'll still have the 
following path into it:


resources/xml/schema/

Is anyone aware of this problem with the maven-jar-plugin...?

Thanks.

Cheers
   Patrizio

--

*Patrizio Munzi*
Product Engineer
Viale Bruno Buozzi, 19 - 00197 Roma (Italy)
tel: +39 06 4543 3540
fax: +39 06 4543 3587
mobile: +39 393 7195 164
mail: [EMAIL PROTECTED] 
web: http://www.eris4.com 
skype: eris4_munzi 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: artifacts build fine on their own but fail in multi-module build

[shea]

Hi Stuart,

Thanks for your reply - I think this explains the problem.

If I understand correctly, the workaround you are proposing is that I unpack
the contents of the "a" jar into "a/target/classes" during the package phase
(using antrun or dependency-plugin unless there is another approach)? 
Alternatively, I suppose I could use antrun to copy the classes for "a" into
"a/target/classes" before packaging and  thereby use the default
"classesDirectory" for the jar plugin...same difference I think.

thanks,

Shea.

Stuart McCulloch-3 wrote:
> 
> On 06/03/2008, shea <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello,
>>
>> I have a multi-module build that is essentially:
>>
>> jars---a
>>  b
>>  c
>>
>> Where jars is a directory that contains a parent/multimodule pom.xml that
>> builds a pom-type artifact called "jars-parent". a, b, and c are each
>> sub-directories within the jars directory with their own poms.  a, b, and
>> c,
>> all have jars-parent as their parent.  They are referenced as modules in
>> jars-parent's pom.xml in the same order.
>>
>> The problem arises in a situation when "c" depends on "a" for example. 
>> If
>> I
>> build each of the submodules independently in the the order "a, b, c",
>> everything is fine.  however, when I do a "mvn install" from the jars
>> directory, "a" and "b" build fine, but compilation of "c" fails - not an
>> artifact resolution problem, but a compilation problem. This is in spite
>> of
>> the fact that "a" was built and installed to my local repo just fine.
>>
>> The only unusual thing I am doing is that "a" doesn't actually compile
>> anything - it just packages some existing class files using the jar
>> plugin.
>> (this is part of an ant conversion - don't get me started :,( )
>>
>> I have had other multi-module build work just fine, but I am hoping
>> somebody
>> can point out some potential gotchas that I am overlooking.
> 
> 
> This is due to a "feature" in the MavenProject class when running
> a reactor (ie. multi-module) compilation.  Normally when it builds
> the compilation classpath, it will use the location of the artifact in
> the local maven repository - and your setup will work fine.
> 
> However, with a reactor build you may be running "mvn compile"
> and not installing artifacts, so there's code inside MavenProject
> (addArtifactPath) that changes the compilation classpath to use:
> 
>/
> 
> instead of the location of the local repository - I think the reason
> for this is because you want to compile against the latest code
> and the jar in the repository may be stale if you're not doing an
> "install" at the same time as "compile"
> 
> unfortunately this doesn't work so well with projects that create
> artifacts without populating "target/classes" because then the
> compilation classpath will contain the empty directory, not the
> actual artifact with the classes :(
> 
> the safest workaround I've found is to unpack the contents of
> the jar to the build.outputDirectory during the packaging phase
> so the classes are found where MavenProject expects them
> 
> a potential fix for the MavenProject class might be to add the
> outputDirectory before the artifact's location in the local repo,
> rather than replacing it in the compilation classpath - however
> this is a rather central part of Maven so modifying its behavior
> should be done very carefully...
> 
> HTH
> 
> Thanks,
>>
>> Shea.
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15863045.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Cheers, Stuart
> 
> 

-- 
View this message in context: 
http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15901229.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven upgrade breaks testcases

[Arash Bizhan zadeh]

I upgraded maven from 2.0.5 to 2.0.8 and faced a big surprise. My test cases
does not run anymore! The error message is :

org.hibernate.HibernateException: createCriteria is not valid without active
transaction
at
org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke
(ThreadLocalSessionContext.java:297)
at $Proxy6.createCriteria(Unknown Source)
at ca.cbc.whatson.dao.ProgramHome.findByName(ProgramHome.java:198)
at ca.cbc.whatson.util.DigestTestXSL.getEpisodes(DigestTestXSL.java
:181)
at ca.cbc.whatson.test.dao.FeedData.feedEpisodes(FeedData.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java
:604)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:470)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830)
at org.testng.internal.TestMethodWorker.invokeTestMethods(
TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java
:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:678)
at org.testng.TestRunner.privateRun(TestRunner.java:624)
at org.testng.TestRunner.run(TestRunner.java:495)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:300)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275)
at org.testng.SuiteRunner.run(SuiteRunner.java:190)
at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792)
at org.testng.TestNG.runSuitesLocally(TestNG.java:765)
at org.testng.TestNG.run(TestNG.java:699)
at org.apache.maven.surefire.testng.TestNGExecutor.run(
TestNGExecutor.java:74)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)

It was working perfectly file with 2.0.5! I guess that it is happened
because of an upgrade in one of the plugins, but I don't know how to find
out which version of the plugins are used and how.
Could somebody help me?


-- 
You can not depend on your eyes when your imagination is out of focus.

Re: Maven Assembly for MultiModule project

[Wayne Fay]

It sounds like you're jumping in to complex builds with Maven2 without
really understanding how things work at a basic level. As an example
of this, you're running mvn install:install-file etc on what seems to
be a Maven project -- so you really only need to type "mvn install".
The same thing goes for your comment about "adding dependencies in all
the pom.xml even if they have been specified in the parent." So I
think you've skipped some important steps in your learning process.

I would go back to the beginning and work your way through Better
Builds With Maven (free pdf book from devzuz.com) and Maven: The
Definitive Guide (from sonatype.com). The books are organized such
that you start out learning how Maven works internally (generally),
and then they lead through some basic examples and finally take you
through much more involved examples.

You should be able to do this in just 1 or 2 days, and I think you
really need to invest this time now rather than attempting to hack
your poms and assemblies just to make it work.

Wayne

On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>
>  
>
>   
>maven-compiler-plugin
>2.1-20080129.223043-7
>
>  1.5
>  1.5
>
>  
>  
> 
>org.apache.maven.plugins
>maven-surefire-plugin
>2.4
>
>  
>testng.xml
>  
>
>  
>  
>maven-assembly-plugin
>
>  
>jar-with-dependencies
>  
>  
>
>  true
>  com.jbe.core.Foo
>
>  
>
>  
>
>  
>
> 
>../pom.xml
>0.1
>foo-foo
>foo
>  
>
> I also find that I have to include foo-b in my foo's pom.xml in order to
> compile even though, foo-a is dependent on foo-b and therefore must compile
> foo-b before foo-a.
> 
>  
>  foo
>  foo-a
>  ${project.version}
>  compile
>
> 
>  foo
>  foo-b
>  ${project.version}
>  compile
> 
> /dependencies>
>
> In addition, I have to add dependencies in all the pom.xml even if they have
> been specified in the parent pom.xml.
>
> Thanks,
>
> Karthik Krishnan
>
>
>
> krishnan.1000 wrote:
> >
> > Hi Wayne,
> >
> > I am sorry Wayne. I should have been more specific on the post. To answer
> > your first comment,  and I do not wish to sound rude, but if I knew what I
> > was doing wrong, I would not have posted in the first place.
> >
> > 2. I am trying to assemble a jar of module Foo and Bar . I wish that I
> > create an executable jar with a defined main class and a classpath added
> > to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
> > containing all the dependencies.
> >
> > 3. I find  that if i make the changes in Foo-A or FooB java classes, and
> > if i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B
> > in the .m2 repository before building Foo and Bar successfully again I
> > have to get around that by doing the following
> >
> > mvn install:install-file
> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project
> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the
> > solution I found by doing a search on one of the posts.
> >
> > and again for foo-b. I would like to avoid that and just have mvn
> > assembly:assembly do all this before creating foo.jar and bar.jar.
> >
> >
> >
> > Wayne Fay wrote:
> >>
> >> This list really works better if you post what you've done and then
> >> tell us why its not working the way you wanted, or an error message
> >> you got, etc. Looking at what you sent, I have no idea if it is
> >> working how you expect or not.
> >>
> >> Sending your pom and assembly.xml file is probably not going to give
> >> you the results you are hoping for. So, send a reply and be more clear
> >> about what you've got vs what you want etc.
> >>
> >> Wayne
> >>
> >> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I am a Maven newbie and I hope this is not a stupid question.  I am
> >>> trying
> >>> to create two Maven assembly jars for modules Foo and Bar. My project --
> >>> |
> >>> |--- Bar
> >>> |--- Foo
> >>> |Foo-A
> >>> |--- Foo-B
> >>>
> >>>
> >>> This is my project structure. In this project, FOO-A is dependent on
> >>> Foo-B
> >>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
> >>> jars
> >>> for both the for both Foo and Bar modules. Can you please help me?
> >>>
> >>> My project pom is as follows.
> >>>
> >>> 
> >>>Bar
> >>>Foo
> >>>Foo-A
> >>>Foo-B
> >>>  
> >>>
> >>>  
> >>>
> >>>  log4j
> >>>  log4j
> >>>  1.2.13
> >>>  compile
> >>>
> >>>
> >>>..
> >>>  
> >>>
> >>>  
> >>>
> >>>  
> >>>maven-assembly-plugin
> >>>
> >>>  
> >>>assembly.xml
> >>>  
> >>>  gnu
> >>>

Re: [ANN] Sonar 1.1 Released : Quality Management Dashboard

[John Quinn]

It's working fine for me

On Fri, Mar 7, 2008 at 10:19 AM, CORUM, M E [AG/1000] <
[EMAIL PROTECTED]> wrote:

> It looks like that link doesn't work. Let us know when the site is back
> up.
>
> Mike
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Freddy Mallet
> Sent: Friday, March 07, 2008 7:54 AM
> To: users@maven.apache.org
> Subject: [ANN] Sonar 1.1 Released : Quality Management Dashboard
>
> The Sonar team is pleased to announce the release of Sonar 1.1.
>
> Sonar is a new Open Source (LGPL) Quality Management Dashboard hosted by
> Codehaus to monitor java projects.
>
> If you only work on few java projects, we highly encourage people to take
> a
> look or keep using great Open Source tools like Maven Dashboard, XRadar
> and
> QALab but if you want to keep control on 10, 50, 100 or more java
> projects,
> Sonar could be a more suitable solution to fit enterprise's needs.
>
> The particularity of Sonar is to aggregate all quality data in a central
> database. This database is populated through a Maven plugin which doesn't
> required any change to your pom file.
>
> Take a look at http://sonar.hortis.ch to get a very quick idea of the
> current functionalities or challenge our 2 minutes installation guide if
> you
> want to get more.
>
> Sonar is sponsored by Hortis, a Swiss IT company based in Geneva and
> specialized in agile methodologies
>
> Enjoy,
>
> --
> The Sonar team
>
>
> -
> This e-mail message may contain privileged and/or confidential
> information, and is intended to be received only by persons entitled to
> receive such information. If you have received this e-mail in error, please
> notify the sender immediately. Please delete it and all attachments from any
> servers, hard drives or any other media. Other use of this e-mail by you is
> strictly prohibited.
>
>
> All e-mails and attachments sent and received are subject to monitoring,
> reading and archival by Monsanto, including its subsidiaries. The recipient
> of this e-mail is solely responsible for checking for the presence of
> "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts
> no liability for any damage caused by any such code transmitted by or
> accompanying this e-mail or any attachment.
>
> -
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: [ANN] Sonar 1.1 Released : Quality Management Dashboard

[CORUM, M E [AG/1000]]

It looks like that link doesn't work. Let us know when the site is back up.

Mike

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Freddy Mallet
Sent: Friday, March 07, 2008 7:54 AM
To: users@maven.apache.org
Subject: [ANN] Sonar 1.1 Released : Quality Management Dashboard

The Sonar team is pleased to announce the release of Sonar 1.1.

Sonar is a new Open Source (LGPL) Quality Management Dashboard hosted by
Codehaus to monitor java projects.

If you only work on few java projects, we highly encourage people to take a
look or keep using great Open Source tools like Maven Dashboard, XRadar and
QALab but if you want to keep control on 10, 50, 100 or more java projects,
Sonar could be a more suitable solution to fit enterprise's needs.

The particularity of Sonar is to aggregate all quality data in a central
database. This database is populated through a Maven plugin which doesn't
required any change to your pom file.

Take a look at http://sonar.hortis.ch to get a very quick idea of the
current functionalities or challenge our 2 minutes installation guide if you
want to get more.

Sonar is sponsored by Hortis, a Swiss IT company based in Geneva and
specialized in agile methodologies

Enjoy,

--
The Sonar team

-
This e-mail message may contain privileged and/or confidential information, and 
is intended to be received only by persons entitled to receive such 
information. If you have received this e-mail in error, please notify the 
sender immediately. Please delete it and all attachments from any servers, hard 
drives or any other media. Other use of this e-mail by you is strictly 
prohibited.


All e-mails and attachments sent and received are subject to monitoring, 
reading and archival by Monsanto, including its subsidiaries. The recipient of 
this e-mail is solely responsible for checking for the presence of "Viruses" or 
other "Malware". Monsanto, along with its subsidiaries, accepts no liability 
for any damage caused by any such code transmitted by or accompanying this 
e-mail or any attachment.
-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: property substitution in site files?

[Wendy Smoak]

On Wed, Oct 18, 2006 at 3:48 PM, pjungwir <[EMAIL PROTECTED]> wrote:

>  I am trying to generate some site files using the .apt format. (I'm not
>  wedded to that format, but I'm starting there since it's the easiest.) I was
>  hoping to do something like this:
>   ${project.name}

See 'Filtering' at the bottom of
http://maven.apache.org/plugins/maven-site-plugin/usage.html

(Name the file whatever.apt.vm, and it will first filter, then convert
from apt to html.  Requires maven-site-plugin 2.0-beta-6.)

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Multi module questions

[robert . egan]

I have multi-module project. If I execute a phase from the topmost module 
(mvn compile or mvn install) the reactor runs it for all the submodules 
and then the topmost module.

But it does not seem to be happening for a non-phase goal (specifically 
mvn scm:update). My questions are 1) Is this the correct behavior or am I 
doing something wrong and 2) If I want to propogate scm:update to my 
submodules, how would I do it?


Thanks
Robert Egan
--
This email message and any attachments may contain confidential, 
proprietary or non-public information.  The information is intended solely 
for the designated recipient(s).  If an addressing or transmission error 
has misdirected this email, please notify the sender immediately and 
destroy this email.  Any review, dissemination, use or reliance upon this 
information by unintended recipients is prohibited.  Any opinions 
expressed in this email are those of the author personally.

[ANN] Sonar 1.1 Released : Quality Management Dashboard

[Freddy Mallet]

The Sonar team is pleased to announce the release of Sonar 1.1.

Sonar is a new Open Source (LGPL) Quality Management Dashboard hosted by
Codehaus to monitor java projects.

If you only work on few java projects, we highly encourage people to take a
look or keep using great Open Source tools like Maven Dashboard, XRadar and
QALab but if you want to keep control on 10, 50, 100 or more java projects,
Sonar could be a more suitable solution to fit enterprise's needs.

The particularity of Sonar is to aggregate all quality data in a central
database. This database is populated through a Maven plugin which doesn't
required any change to your pom file.

Take a look at http://sonar.hortis.ch to get a very quick idea of the
current functionalities or challenge our 2 minutes installation guide if you
want to get more.

Sonar is sponsored by Hortis, a Swiss IT company based in Geneva and
specialized in agile methodologies

Enjoy,

--
The Sonar team

reusing developers settings

[Dooing]

Hi, 

in my parent pom, I defined all developers of our company. Now in each 
subproject, I would like to mention the developers of just this project - 
without redefining each developer setting. I tried:


DEVELOPER_ID



but this just printed "DEVELOPER_ID", without name and email, on the site.

Any ideas how this can be done without having to metion the entire information 
of a developer, for each subproject he's involved?

Thanks in advance,

Stefanie
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Validating version selections

[deckrider]

I'm doing this from memory but I think the site plugin produces such a report.



On 3/6/08, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> That's what I tried initially, but it doesn't complaine about where
> exactly the mis-matched  versions are (as well as being bound to the
> verify stage).
>
> Did I miss the boat a bit here?
>
> -Original Message-
> From: deckrider [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2008 9:57 PM
> To: Maven Users List
> Subject: Re: Validating version selections
>
> Perhaps a pom depending on those other projects?  Then you could run
> the dependency plugin against it.
>
>
>
> On 3/6/08, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> > Is there a standalone type plugin one can use to verify that multiple
> > projects are using the same set of dependencies?
> >
> > I'd love to use something like dependency-analyze, but I want to
> compare
> > two different deployable units (rather than having each deployable
> unit
> > validate it's own set of dependencies).
> >
>
>
> --
> ASCII ribbon campaign:
> ()  against HTML email
> /\  against Microsoft attachments
> Information:  http://www.expita.com/nomime.html
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
Information:  http://www.expita.com/nomime.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Build Issues with Maven

[Lukas Theussl]

The artifacts are in the repo, did you add 
http://source.sakaiproject.org/maven/ to maven.repo.remote? What command 
are you running and what is the full error message you get (the message 
below is not one that I recognize from m1.1, it should say 'The build 
cannot continue because of the following unsatisfied dependency:'...)?


-Lukas


new_to_sakai wrote:

Hi,
I'm building SAKAI(2.4) using Maven 1.1 . When I try to build the SAKAI,
I get the following error :

Unable to download Dependencies for Tomcat 5.5.23 :zip from the site
http://source.sakaiproject.org/maven

Unable to download Dependencies for sakai2.2:plugin  from the site
http://source.sakaiproject.org/maven
 Can anyone please help me out :



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Failed to resolve artifact - jar of pomfile

[[EMAIL PROTECTED]]

Jan Torben Heuer schrieb:
> Hi,
>
> I have a project with a dependency to a pom file:
>
> But maven always want to download the corresponding jar-file - although
> pom
> How does maven determine if it is a pom or jar (or war) or whatever? Could
> the metadata.xml be wrong?
>
>
> Here the details:
> 
> org.openrdf.elmo
> elmo
> 1.0-SNAPSHOT
> 
>
> Repository:
> http://repo.aduna-software.org/maven2/snapshots/org/openrdf/elmo/elmo/1.0-SNAPSHOT/
>
> metadata:
> 
>
> 
>   org.openrdf.elmo
>   elmo
>   1.0-SNAPSHOT
>   
> 
>   0
> 
> 20080303184953
>   
> 
>
>
>
> Any ideas? I could specify pom in the dependency, but then the
> problem occurs with transitive dependencies...
>
>   
problem occurs with transitive dependencies

What transitive dependencies? Your elmo.pom file doesn't declare any
dependencies.

It does declare some dependencyManagement stuff, but as far as I know,
dependencyManagement only has effects within a pom and its children, and
is ignored when in a pom that is a *dependency*.

Regards,
Simon


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

assembly.xml of mixed and not unpacked as expected

[torsten . reinhard]

Hi, 

I have an assembly.xml file with mixed  and  like:

http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/assembly-1.0.0.xsd"; xmlns="
http://maven.apache.org/POM/4.0.0";>


  zip

false





src/main/config


**/*.properties






 ${basedir}/src/main/config/update-db2.bat
true


 ${basedir}/src/main/config/update-db2.sh
true




The created zip-File looks o.k., there´s no path in it. I could extract it 
with Winzip and all files come to the same directory.

But when I extract the zip with dependency:unpack the  files go 
to the configured outputDirectory, 

C:\delivery\version\Install/Datenbank/UpdateDB\*.properties

but the  files go to my current root directory !!!

S:\*.bat
S:\*.sh

Here´s the pom.xml snippet to unpack the stuff:


maven-dependency-plugin

  
  
unpack
package

  unpack




 com.gide.gdcams
 gdcams-updatedb
 ${version}
  zip
 
${gdcams.delivery_dir}/${productVersion}/Install/Datenbank/UpdateDB
  


  
 

 

=> Why is there a difference ?
=>  What´s the secret behind packing files into a zip with  or with 
 ?

All I want, is packing some filtered files in a multi-module build, and 
unzipping them later while delivery.


Thanx, torsten

Re: Failed to resolve artifact - jar of pomfile

[Stuart McCulloch]

On 07/03/2008, Jan Torben Heuer <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a project with a dependency to a pom file:
>
> But maven always want to download the corresponding jar-file - although
> pom
> How does maven determine if it is a pom or jar (or war) or whatever? Could
> the metadata.xml be wrong?
>
>
> Here the details:
> 
> org.openrdf.elmo
> elmo
> 1.0-SNAPSHOT
> 


afaik maven assumes the type of the dependency is jar unless you specify
otherwise
so you would need to use pom to add a dependency to a pom
project

Repository:
>
> http://repo.aduna-software.org/maven2/snapshots/org/openrdf/elmo/elmo/1.0-SNAPSHOT/
>
> metadata:
> 
>
> 
>   org.openrdf.elmo
>   elmo
>   1.0-SNAPSHOT
>   
> 
>   0
> 
> 20080303184953
>   
> 
>
>
>
> Any ideas? I could specify pom in the dependency, but then
> the
> problem occurs with transitive dependencies...


if so then they also need to be updated to use the correct  in their
dependencies

Jan
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Cheers, Stuart

Failed to resolve artifact - jar of pomfile

[Jan Torben Heuer]

Hi,

I have a project with a dependency to a pom file:

But maven always want to download the corresponding jar-file - although
pom
org.openrdf.elmo
elmo
1.0-SNAPSHOT


Repository:
http://repo.aduna-software.org/maven2/snapshots/org/openrdf/elmo/elmo/1.0-SNAPSHOT/

metadata:



  org.openrdf.elmo
  elmo
  1.0-SNAPSHOT
  

  0

20080303184953
  




Any ideas? I could specify pom in the dependency, but then the
problem occurs with transitive dependencies...

Jan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: artifacts build fine on their own but fail in multi-module build

[Stuart McCulloch]

On 06/03/2008, shea <[EMAIL PROTECTED]> wrote:
>
>
> Hello,
>
> I have a multi-module build that is essentially:
>
> jars---a
>  b
>  c
>
> Where jars is a directory that contains a parent/multimodule pom.xml that
> builds a pom-type artifact called "jars-parent". a, b, and c are each
> sub-directories within the jars directory with their own poms.  a, b, and
> c,
> all have jars-parent as their parent.  They are referenced as modules in
> jars-parent's pom.xml in the same order.
>
> The problem arises in a situation when "c" depends on "a" for example.  If
> I
> build each of the submodules independently in the the order "a, b, c",
> everything is fine.  however, when I do a "mvn install" from the jars
> directory, "a" and "b" build fine, but compilation of "c" fails - not an
> artifact resolution problem, but a compilation problem. This is in spite
> of
> the fact that "a" was built and installed to my local repo just fine.
>
> The only unusual thing I am doing is that "a" doesn't actually compile
> anything - it just packages some existing class files using the jar
> plugin.
> (this is part of an ant conversion - don't get me started :,( )
>
> I have had other multi-module build work just fine, but I am hoping
> somebody
> can point out some potential gotchas that I am overlooking.


This is due to a "feature" in the MavenProject class when running
a reactor (ie. multi-module) compilation.  Normally when it builds
the compilation classpath, it will use the location of the artifact in
the local maven repository - and your setup will work fine.

However, with a reactor build you may be running "mvn compile"
and not installing artifacts, so there's code inside MavenProject
(addArtifactPath) that changes the compilation classpath to use:

   /

instead of the location of the local repository - I think the reason
for this is because you want to compile against the latest code
and the jar in the repository may be stale if you're not doing an
"install" at the same time as "compile"

unfortunately this doesn't work so well with projects that create
artifacts without populating "target/classes" because then the
compilation classpath will contain the empty directory, not the
actual artifact with the classes :(

the safest workaround I've found is to unpack the contents of
the jar to the build.outputDirectory during the packaging phase
so the classes are found where MavenProject expects them

a potential fix for the MavenProject class might be to add the
outputDirectory before the artifact's location in the local repo,
rather than replacing it in the compilation classpath - however
this is a rather central part of Maven so modifying its behavior
should be done very carefully...

HTH

Thanks,
>
> Shea.
>
>
>
> --
> View this message in context:
> http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15863045.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Cheers, Stuart

Re: property substitution in site files?

[VUB Stefan Seidel]

Hi Krish,

what you want is absolutely ok with maven. Paul was talking about the 
apt format for the site documentation. I think this was just not made to 
include maven properties.

See http://maven.apache.org/doxia/references/apt-format.html
Curly braces mean anchor, not property.

Stefan

dasarikm wrote:

Hey Paul,
 Did you resolve this issue.
I have a parent pom and I want the properties in parent to be substituted in
the child's pom when I do mvn install.
Is it possible.

Thanks
Krish

pjungwir wrote:

Hello,

I am trying to generate some site files using the .apt format. (I'm not
wedded to that format, but I'm starting there since it's the easiest.) I
was hoping to do something like this:

  ${project.name}

${project.description}


But that doesn't work. The curly braces disappear, but the properties
aren't replaced. So I guess maven doesn't do property substitution before
processing these files, huh? Is there a switch to turn that on? Should I
just hack it by running my site files through a resource filter?

Thanks,
Paul






--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Installing multiple files in the local repository using mvn istall?

[Stuart McCulloch]

On 06/03/2008, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> Is there a way to install multiple jars in the local repository using
> the mvn install:install-file command?


yes, use a script

Thanks,
> Venkat
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-- 
Cheers, Stuart

Re: Maven plugin API - how do I find the File for the artifact of current project?

[Stuart McCulloch]

On 05/03/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Thanks Martin.
> I want a File object or a path to the project's target artifact.
> I have managed to calculate the target artifact myself using
> project.getArtifact() and project.getBuild().getOutputDirectory() but
> thought that there may be a simple and more robust API that I haven't
> noticed.


if the artifact has been built in this particular build invocation then:

project.getArtifact().getFile()

will give you its location - but note that if you run your plugin on its
own, outside of an actual "mvn package", then this will return null.

alternatively you can use the following scheme:

   project.getBuild().getDirectory() + '/' + project.getBuild().getFinalName()
+ ...etc...

although finding the actual extension used for a given artifact type
is a bit tricky, and you might also need to add a classifier section.

part of this is because maven doesn't really mind where the artifact
is written to - because "mvn install" will run the packaging phase,
which means the relevant packaging plugin (jar, etc.) will have set
the artifact file - if you just run "mvn install:install" you'll see it
fail...

FYI, you can also use the "localRepository" component:

/**
 * Local Repository.
 *
 * @parameter expression="${localRepository}"
 * @required
 * @readonly
 */
private ArtifactRepository localRepository;

to find the location of an artifact inside the current local repository:

   localRepository.getBasedir() + '/' + localRepository.pathOf( artifact )

and there are other components to resolve an artifact in repositories.

I'm writing a plugin that assembles certain artifacts into one zip so
> they may be easily installed on another machine.
> I need this in order to have downloadables for certain open source
> projects, and thus enable users, without using maven repositories, to
> download a library artifact and its dependencies in a simple manner. The
> zip will also contain scripts to install the artifacts into the local
> repo.


hmm, well this sounds exactly like the maven-assembly-plugin:

   http://maven.apache.org/plugins/maven-assembly-plugin

which lets you create distributions, etc. from maven projects

there's also the maven-dependency-plugin which can copy
collections of artifacts / project dependencies to a location.

HTH

-Original Message-
> From: Martin Gainty [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 05, 2008 3:04 PM
> To: Maven Users List
> Subject: Re: Maven plugin API - how do I find the File for the artifact
> of current project?
>
> Good Morning Daniel-
>
> org.apache.maven.model.Build has no accessors/mutators or methods which
> manipulate Artifact
>
> the getArtifact() method is present in 2.0.x version of
> org.apache.maven.project.MavenProject.java
>   public Artifact getArtifact()
> {
> return artifact;
> }
> e.g.
> org.apache.maven.project.MavenProject project = new
> org.apache.maven.project.MavenProject();
> Artifact artifact=project.getArtifact();
>
> We could provide more assistance if you could tell us what you're
> attempting
> to accomplish
>
> Martin--
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, March 05, 2008 7:15 AM
> Subject: Maven plugin API - how do I find the File for the artifact of
> current project?
>
>
>
> Hi.
> I looked for all kinds of APIs in org.apache.maven.project.MavenProject
> but did not find any API to give me the file/filename for the build's
> output artifact.
> The project.getArtifact() returns an Artifact object that describes the
> artifact. I can use it to calculate what is the artifact, but there must
> be a simpler way to get it.
> Also, the Build object returned by project.getBuild() has no such
> method.
>
> Thanks for your answers ...
>
> Daniel
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Cheers, Stuart

Re: Wiping out a dependency from an internal repository

[Papapara Tudu]

[EMAIL PROTECTED] wrote:
> 
> Do you mean deleting stuff from the ~/.m2/repository directorty on the
> same computer you are running maven from?
> ...
> Maybe you should think carefully about whether you really need to do any
> of this though..
> 

Actually all of this is related to my problem with picking up the correct
snapshot which I described in this thread:
http://www.nabble.com/Problem-with-snapshots-td15709789s177.html
As I still haven't resolved that problem, what I'm going to do is delete the
whole snapshot dependency from my local repository (first I thought of
deleting it from the internal repository, but now I've noticed it's enogh
just to delete it from the local one) at the beginning of the build and then
the newest version of the snapshot will be downloaded from the internal
repository. 

It's a brutal workaround, but since I cannot get the common approach to
work, I need to restort to this.

Cheers,
Papapara Tudu


-- 
View this message in context: 
http://www.nabble.com/Wiping-out-a-dependency-from-an-internal-repository-tp15873175s177p15891117.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Antwort: RE: dependency:copy always creates new timestamp

[torsten . reinhard]

http://jira.codehaus.org/browse/MDEP-154




"Brian E. Fox" <[EMAIL PROTECTED]> 
05.03.2008 17:04
Bitte antworten an
"Maven Users List" 


An
"Maven Users List" 
Kopie

Thema
RE: dependency:copy always creates new timestamp






Currently no. I use the plexus-utils copyFile which copies the stream 
contents. To copy the file and preserve the timestamp would require some 
changes. Can you file a jira?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 05, 2008 7:00 AM
To: users@maven.apache.org
Subject: dependency:copy always creates new timestamp

Hi, 

to create the delivery version of our whole system, I use 
"dependency:copy" and "dependency:copy-dependencies" 
to copy the jars, ears, wars and so on from our internal repository into a 

defined directory structure.


Install
Module-A
xyz.war
Module-B
xyz.ear
Documentation
*.doc

Every time I start the "delivery build", the copied artifacts get new 
timestamps - although the version hasn´t changed in between.

I couldn´t find any property "keep original timestamp" to set for the 
goals "copy" or "copy-dependencies".

Is there a way?


Thanx, Torsten

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Try to run install before eclipse:eclipse

[Martin Höller]

Hi!

On Thursday 06 March 2008 Brian E. Fox wrote:
> This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing
> this on 2.0.8 or earlier?

Actually it was 2.0.7. I'll try it with 2.0.8 as soon as I can and report 
back if there are still problems.

- martin
-- 
Martin Höller   | [EMAIL PROTECTED]
*x Software + Systeme   | http://www.xss.co.at/
Karmarschgasse 51/2/20  | Tel: +43-1-6060114-30
A-1100 Vienna, Austria  | Fax: +43-1-6060114-71


signature.asc
Description: This is a digitally signed message part.