Re: How to specify local dependency in maven2

[Samuel Le Berrigaud]

Not that I know of. And I believe there is not.

The maven way of managing dependencies is to declare those in the POM (or to
get them transitively for maven2), using libraries from a directory would go
against that.

Hope it helps.
SaM

On Tue, Mar 4, 2008 at 6:36 PM, Dipankar Ghosal <
[EMAIL PROTECTED]> wrote:

>
>
> Thanks Samuel..
>
> However is there any way to include all libraries that are present in a
> particular folder.
> Say i have 20 odd jars in C:\lib folder?
>
>
>
> Samuel Le Berrigaud wrote:
> >
> > Hi,
> >
> > you would have to use the system scope. See the system dependencies
> > section
> > at
> >
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> > .
> >
> > However I would recommend you create a private repository internally to
> > your
> > company so that you can more easily share those dependencies with your
> > team.
> > This way those dependencies will work the same way as any other maven
> > dependency. Consistency is good.
> >
> > SaM
> >
> > On Tue, Mar 4, 2008 at 6:00 PM, Dipankar Ghosal <
> > [EMAIL PROTECTED]> wrote:
> >
> >>
> >> I have a WebSphere Portlet project which uses many IBM jars(Available
> at
> >> installation directory in local system).
> >>
> >> I need to use these jars while performing maven build.
> >>
> >> How do i specify the location of the jars so that maven uses the jars
> >> from
> >> local location rather than download from remote repository.
> >>
> >> Is there any option like specifying the local jars in
> >> project.properties(available in maven 1.1)
> >> 
> >> #
> >> # Register local jar files to maven. This prevents maven from
> >> # trying to download these dependencies
> >> #
> >> 
> >> maven.jar.wps = ${wps.home}/wps.jar
> >> maven.jar.jsr168-api = ${wps.home}/shared/app/jsr168-api.jar
> >>
> >> Any help will be appreciated
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821419.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]
> >>
> >>
> >
> >
> > --
> > Samuel Le Berrigaud
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821761.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]
>
>


-- 
Samuel Le Berrigaud

Re: How to specify local dependency in maven2

[Dipankar Ghosal]

Thanks Samuel..

However is there any way to include all libraries that are present in a
particular folder.
Say i have 20 odd jars in C:\lib folder?



Samuel Le Berrigaud wrote:
> 
> Hi,
> 
> you would have to use the system scope. See the system dependencies
> section
> at
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> .
> 
> However I would recommend you create a private repository internally to
> your
> company so that you can more easily share those dependencies with your
> team.
> This way those dependencies will work the same way as any other maven
> dependency. Consistency is good.
> 
> SaM
> 
> On Tue, Mar 4, 2008 at 6:00 PM, Dipankar Ghosal <
> [EMAIL PROTECTED]> wrote:
> 
>>
>> I have a WebSphere Portlet project which uses many IBM jars(Available at
>> installation directory in local system).
>>
>> I need to use these jars while performing maven build.
>>
>> How do i specify the location of the jars so that maven uses the jars
>> from
>> local location rather than download from remote repository.
>>
>> Is there any option like specifying the local jars in
>> project.properties(available in maven 1.1)
>> 
>> #
>> # Register local jar files to maven. This prevents maven from
>> # trying to download these dependencies
>> #
>> 
>> maven.jar.wps = ${wps.home}/wps.jar
>> maven.jar.jsr168-api = ${wps.home}/shared/app/jsr168-api.jar
>>
>> Any help will be appreciated
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821419.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]
>>
>>
> 
> 
> -- 
> Samuel Le Berrigaud
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821761.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 specify local dependency in maven2

[Samuel Le Berrigaud]

Hi,

you would have to use the system scope. See the system dependencies section
at
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
.

However I would recommend you create a private repository internally to your
company so that you can more easily share those dependencies with your team.
This way those dependencies will work the same way as any other maven
dependency. Consistency is good.

SaM

On Tue, Mar 4, 2008 at 6:00 PM, Dipankar Ghosal <
[EMAIL PROTECTED]> wrote:

>
> I have a WebSphere Portlet project which uses many IBM jars(Available at
> installation directory in local system).
>
> I need to use these jars while performing maven build.
>
> How do i specify the location of the jars so that maven uses the jars from
> local location rather than download from remote repository.
>
> Is there any option like specifying the local jars in
> project.properties(available in maven 1.1)
> 
> #
> # Register local jar files to maven. This prevents maven from
> # trying to download these dependencies
> #
> 
> maven.jar.wps = ${wps.home}/wps.jar
> maven.jar.jsr168-api = ${wps.home}/shared/app/jsr168-api.jar
>
> Any help will be appreciated
> --
> View this message in context:
> http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821419.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]
>
>


-- 
Samuel Le Berrigaud

How to specify local dependency in maven2

[Dipankar Ghosal]

I have a WebSphere Portlet project which uses many IBM jars(Available at
installation directory in local system).

I need to use these jars while performing maven build.

How do i specify the location of the jars so that maven uses the jars from
local location rather than download from remote repository.

Is there any option like specifying the local jars in
project.properties(available in maven 1.1)

# 
# Register local jar files to maven. This prevents maven from
# trying to download these dependencies
#

maven.jar.wps = ${wps.home}/wps.jar
maven.jar.jsr168-api = ${wps.home}/shared/app/jsr168-api.jar

Any help will be appreciated
-- 
View this message in context: 
http://www.nabble.com/How-to-specify-local-dependency-in-maven2-tp15821419s177p15821419.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]

one build per cpu (continuum 1.1)

[deckrider]

Hi,

We have a 4-cpu machine on which we run continuum 1.1.  Unfortunately,
it only runs one build at a time.  How can we run up to 4 builds at a
time?

Thanks!

Dependency Plugin

[Shakun Gupta]

Hi All,
I am using the maven dependency plugin v 2.0. I wanted to copy the 
dependency jars to an external folder. I tried two approaches:
1. I added the configuration for dependency-plugin in the pom.xmls of 
the modules and when I ran the "dependency:copy-dependencies" task along 
with the corresponding life cycle goal at the parent level, the 
dependencies were not copied at the external folder location but were 
copied at the default location. (target/dependency).
2. I added all the project dependencies to the parent. And gave the 
dependency-plugin configuration in the parent pom with the life cycle 
goal as package. And to avoid inheritance, I modified poms of modules 
with setting the lifecycle goal as deploy. So, when I ran the 
"dependency:copy-dependencies" goal along with life cycle goal package 
at the parent level, the task is also called in the modules and 
thankfully the dependencies are not copied again.


So, I wanted to ask a few things:
1. How can I disable the copying of dependency jars in the default 
folder (I don't need these jars).
2. In the first approach, Is the dependency plugin expected to work like 
that or it is a bug. Also, how can I achieve the task that I want using 
that approach.
3. In the second approach, how can I override the parent pom so that 
copy-dependency task is not called.
4. Also, please let me know which approach is better. To give 
dependencies at the parent level or at each module level.


Regards,
Shakun

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

Re: Release process

[Wendy Smoak]

On Mon, Mar 3, 2008 at 7:29 PM, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> There is 6 Tomcat 5.5 sandboxes, all of them running on RHE 6. There is a
>  load balancer in front of them and we need to release every app on all of
>  them. I am looking for the best practices to manage the releases.

This is more deployment (and configuration management) than "release".

Take a look at Lokahi, currently in the ASF Incubator:
http://incubator.apache.org/lokahi/

-- 
Wendy

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

Re: Release process

[Wayne Fay]

I'd probably ask this question on the Tomcat or possibly Cargo lists.
I won't claim to have expertise in these matters. Perhaps someone else
on the list will have advice.

Wayne

On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> There is 6 Tomcat 5.5 sandboxes, all of them running on RHE 6. There is a
> load balancer in front of them and we need to release every app on all of
> them. I am looking for the best practices to manage the releases.
>
> On Mon, Mar 3, 2008 at 9:23 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > What app server? How many? On what kind of equipment/operating
> > systems? This is not a trivial problem to solve, IME.
> >
> > Wayne
> >
> > On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > > I know that we can use cargo to push the code to one instance of Tomcat;
> > but
> > > could it push the application to multiple instances simultaneously?
> > Besides
> > > is it a good idea to hot-deploy in production environment?
> > >  any feedback is appreciated.
> > >
> > > On Mon, Mar 3, 2008 at 8:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > >
> > > > Potentially, the Cargo M2 plugin could help automate some of this for
> > you.
> > > >
> > > > Wayne
> > > >
> > > > On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > > > > Hi everybody,
> > > > > First I all I want to apologies for off topic question. It is not
> > really
> > > > a
> > > > > maven related question, but I thought I may get some feedback.
> > > > > We need a tool to release our web-based application in production
> > > > sandboxes.
> > > > > We have multiple sandboxes which are load-balanced with a CISCO
> > > > appliance.
> > > > > We use Maven to build the artifact and searching for a good approach
> > to
> > > > > automate release process under these sandboxes. The ideal solution
> > will
> > > > be a
> > > > > maven plugin to handle it all.
> > > > >
> > > > > Thanks in advance for any advise.
> > > > >
> > > > > -regards,
> > > > > Arash
> > > > > --
> > > > > You can not depend on your eyes when your imagination is out of
> > focus.
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > You can not depend on your eyes when your imagination is out of focus.
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> You can not depend on your eyes when your imagination is out of focus.
>

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

Re: Release process

[Arash Bizhan zadeh]

There is 6 Tomcat 5.5 sandboxes, all of them running on RHE 6. There is a
load balancer in front of them and we need to release every app on all of
them. I am looking for the best practices to manage the releases.

On Mon, Mar 3, 2008 at 9:23 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:

> What app server? How many? On what kind of equipment/operating
> systems? This is not a trivial problem to solve, IME.
>
> Wayne
>
> On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > I know that we can use cargo to push the code to one instance of Tomcat;
> but
> > could it push the application to multiple instances simultaneously?
> Besides
> > is it a good idea to hot-deploy in production environment?
> >  any feedback is appreciated.
> >
> > On Mon, Mar 3, 2008 at 8:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >
> > > Potentially, the Cargo M2 plugin could help automate some of this for
> you.
> > >
> > > Wayne
> > >
> > > On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > > > Hi everybody,
> > > > First I all I want to apologies for off topic question. It is not
> really
> > > a
> > > > maven related question, but I thought I may get some feedback.
> > > > We need a tool to release our web-based application in production
> > > sandboxes.
> > > > We have multiple sandboxes which are load-balanced with a CISCO
> > > appliance.
> > > > We use Maven to build the artifact and searching for a good approach
> to
> > > > automate release process under these sandboxes. The ideal solution
> will
> > > be a
> > > > maven plugin to handle it all.
> > > >
> > > > Thanks in advance for any advise.
> > > >
> > > > -regards,
> > > > Arash
> > > > --
> > > > You can not depend on your eyes when your imagination is out of
> focus.
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > You can not depend on your eyes when your imagination is out of focus.
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

Re: Release process

[Wayne Fay]

What app server? How many? On what kind of equipment/operating
systems? This is not a trivial problem to solve, IME.

Wayne

On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> I know that we can use cargo to push the code to one instance of Tomcat; but
> could it push the application to multiple instances simultaneously? Besides
> is it a good idea to hot-deploy in production environment?
>  any feedback is appreciated.
>
> On Mon, Mar 3, 2008 at 8:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > Potentially, the Cargo M2 plugin could help automate some of this for you.
> >
> > Wayne
> >
> > On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > > Hi everybody,
> > > First I all I want to apologies for off topic question. It is not really
> > a
> > > maven related question, but I thought I may get some feedback.
> > > We need a tool to release our web-based application in production
> > sandboxes.
> > > We have multiple sandboxes which are load-balanced with a CISCO
> > appliance.
> > > We use Maven to build the artifact and searching for a good approach to
> > > automate release process under these sandboxes. The ideal solution will
> > be a
> > > maven plugin to handle it all.
> > >
> > > Thanks in advance for any advise.
> > >
> > > -regards,
> > > Arash
> > > --
> > > You can not depend on your eyes when your imagination is out of focus.
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> You can not depend on your eyes when your imagination is out of focus.
>

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

Re: How to deploy ears to application instead of repository?

[Wendy Smoak]

On Mon, Mar 3, 2008 at 6:57 PM, gotama <[EMAIL PROTECTED]> wrote:

>  What I'd like to do is use Maven to scp some ear artifacts to my server's
>  JBoss deploy directory - not to a repository. How can I do this? When I use
>   the ear is in fact scp'd, but with everything else
>  related to a repository... html files and in a path of
>  .../com/mycomp/project/.
>
>  How can I use Maven to simply copy ears - retreived from the local
>  repository, and scp them to a specific directory on a remote server?

Take a look at Cargo:  http://cargo.codehaus.org/

(Or you could do something as simple as exec-maven-plugin + a shell script.)

-- 
Wendy

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

Re: Release process

[Arash Bizhan zadeh]

I know that we can use cargo to push the code to one instance of Tomcat; but
could it push the application to multiple instances simultaneously? Besides
is it a good idea to hot-deploy in production environment?
 any feedback is appreciated.

On Mon, Mar 3, 2008 at 8:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:

> Potentially, the Cargo M2 plugin could help automate some of this for you.
>
> Wayne
>
> On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> > Hi everybody,
> > First I all I want to apologies for off topic question. It is not really
> a
> > maven related question, but I thought I may get some feedback.
> > We need a tool to release our web-based application in production
> sandboxes.
> > We have multiple sandboxes which are load-balanced with a CISCO
> appliance.
> > We use Maven to build the artifact and searching for a good approach to
> > automate release process under these sandboxes. The ideal solution will
> be a
> > maven plugin to handle it all.
> >
> > Thanks in advance for any advise.
> >
> > -regards,
> > Arash
> > --
> > You can not depend on your eyes when your imagination is out of focus.
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

How to deploy ears to application instead of repository?

[gotama]

What I'd like to do is use Maven to scp some ear artifacts to my server's
JBoss deploy directory - not to a repository. How can I do this? When I use
 the ear is in fact scp'd, but with everything else
related to a repository... html files and in a path of
.../com/mycomp/project/.

How can I use Maven to simply copy ears - retreived from the local
repository, and scp them to a specific directory on a remote server?

Thanks...

-- 
View this message in context: 
http://www.nabble.com/How-to-deploy-ears-to-application-instead-of-repository--tp15818671s177p15818671.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: TextMate Maven Bundle.

[Luke Daley]

On 04/03/2008, at 11:13 AM, John Casey wrote:

Cool, you don't by any chance support auto-completion of sections  
of the
pom, do you? I was thinking of something like the behavior of the  
'(' and
'{' characters, for things like  and  (these are  
the ones

that I always mess up the end tags on, since they're
singular-followed-by-plural...like \n)


I don't explicitly, but the XML bundle has good support for this.  
Just type course) and you will get what I think you want.


Nice to see someone working on this, though. I'm a big fan of  
TextMate. :-)


Be sure to let me know of any features you would like.

LD.

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

Re: TextMate Maven Bundle.

[John Casey]

Cool, you don't by any chance support auto-completion of sections of the
pom, do you? I was thinking of something like the behavior of the '(' and
'{' characters, for things like  and  (these are the ones
that I always mess up the end tags on, since they're
singular-followed-by-plural...like \n)

Nice to see someone working on this, though. I'm a big fan of TextMate. :-)

-john

On Mon, Mar 3, 2008 at 7:45 PM, Luke Daley <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> A Maven bundle for the popular Mac OS text editor TextMate  macromates.com/> is now available from the central bundle repository
> .
>
> This bundle allows you to invoke Maven from within TextMate with a
> few simple keystrokes. It also colorises mvn's output (one example
> being the highlighting of test failure notices) which is surprisingly
> handy. It also scopes key pom sections to allow you to navigate your
> poms with ease.
>
> I also have an APT bundle in the works  Bundles/trunk/Review/Bundles/Almost%20Plain%20Text%20(APT).tmbundle>
> that makes writing APT documents significantly easier. If this
> interests you, please be sure to give it a try and let me know of
> issues and missing features.
>
> Cheers,
>
> LD.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
John Casey
---
Maven Developer (http://maven.apache.org)
---
Blog: http://www.ejlife.net/blogs/buildchimp

Re: Release process

[Wayne Fay]

Potentially, the Cargo M2 plugin could help automate some of this for you.

Wayne

On 3/3/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> Hi everybody,
> First I all I want to apologies for off topic question. It is not really a
> maven related question, but I thought I may get some feedback.
> We need a tool to release our web-based application in production sandboxes.
> We have multiple sandboxes which are load-balanced with a CISCO appliance.
> We use Maven to build the artifact and searching for a good approach to
> automate release process under these sandboxes. The ideal solution will be a
> maven plugin to handle it all.
>
> Thanks in advance for any advise.
>
> -regards,
> Arash
> --
> You can not depend on your eyes when your imagination is out of focus.
>

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

Release plugin question

[Randall Fidler]

Hello,

 

  Using the release plugin if you wanted to assemble your project
BEFORE it rolls over the next SNAPSHOT, how would you accomplish that?

 

For instance:

 

When you do a release:prepare then release:perform and then
assembly:assembly (to run a customer assembler) instead of ending up
with artifacts at, let's say PROJECT-1.0_B0, I end up with an assembly
that is referencing PROJECT-1.0_B1-SNAPSHOT, which is the next version
in line.  From what I can tell this makes sense and at the time the
assembly runs, the version has moved to the next SNAPSHOT.

 

I did see a note that you can tie actions to the relase plugin to do
BEFORE it submits - would you simply put assembly goal in there?  Is
that location referencing between prepare and perform or before it
submits prepare changes or... where?

 

So, just to recap... I'm trying to get my assembly to play with the
PROJECT-1.0_b0 version and not the PROJECT-1.0_b1-SNAPSHOT version.

 

Thanks for any help!

 

Randall

TextMate Maven Bundle.

[Luke Daley]

Hi all,

A Maven bundle for the popular Mac OS text editor TextMate macromates.com/> is now available from the central bundle repository  
.


This bundle allows you to invoke Maven from within TextMate with a  
few simple keystrokes. It also colorises mvn's output (one example  
being the highlighting of test failure notices) which is surprisingly  
handy. It also scopes key pom sections to allow you to navigate your  
poms with ease.


I also have an APT bundle in the works   
that makes writing APT documents significantly easier. If this  
interests you, please be sure to give it a try and let me know of  
issues and missing features.


Cheers,

LD.

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

Release process

[Arash Bizhan zadeh]

Hi everybody,
First I all I want to apologies for off topic question. It is not really a
maven related question, but I thought I may get some feedback.
We need a tool to release our web-based application in production sandboxes.
We have multiple sandboxes which are load-balanced with a CISCO appliance.
We use Maven to build the artifact and searching for a good approach to
automate release process under these sandboxes. The ideal solution will be a
maven plugin to handle it all.

Thanks in advance for any advise.

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

Re: javax.naming.CommunicationException: Receive timed out problem

[David Blevins]

On Mar 3, 2008, at 2:21 PM, Neo Anderson wrote:

Thanks your reply. Finally I solved the problem. The problem comes  
from the wrong way to setup initial context. The correct way to do  
that is by (in my test case, e.g., HelloTest)


   protected void setUp() throws Exception{
   Hashtable env = new Hashtable();
   env.put(Context.INITIAL_CONTEXT_FACTORY,  
"org.jnp.interfaces.NamingContextFactory");

   env.put(Context.PROVIDER_URL, "localhost");
   env.put(Context.URL_PKG_PREFIXES,  
"org.jboss.naming:org.jnp.interfaces" );

   initialContext = new InitialContext(env);
   }

However, I encounter a new question. I use test case to call my ejb  
application (stateless session bean). Thus I found out when  
executing command 'mvn clean install,'  it will do test first,  
resulting failure because  the ejb artifact is still not yet  
deployed to the server. How can deploy to and launch the server  
first before the test case executed.


Thanks in advice.


OpenEJB discovers them automatically in the classpath and deploys  
them, not sure how JBoss does it.  Best refer to their docs.


-David





- Original Message 
From: VUB Stefan Seidel <[EMAIL PROTECTED]>
To: Maven Users List 
Sent: Monday, 3 March, 2008 9:49:25 PM
Subject: Re: javax.naming.CommunicationException: Receive timed out  
problem


Hi,

this is most likely not a maven problem. It seems your test tries to
connect to a remote JBoss instance but cannot contact it (not  
deployed?).


regards,

Stefan

Neo Anderson wrote:

Hi

I am new to maven. And by following http://openejb.apache.org/3.0/simple-stateless-example.html 
 I write a simple stateless session bean (ejb3) to test the jboss  
and maven,but encounter a problem. The error issues


testHelloRemote(net.sf.sample.HelloTest)  Time elapsed: 5.06 sec   
<<< ERROR!
javax.naming.CommunicationException: Receive timed out [Root  
exception is java.net.SocketTimeoutException: Receive timed out]


The way how I test is

1.) create ejb module
mvn archetype:create -DgroupId=net.sf.sample -DartifactId=hello - 
Dversion=1.0


2.) modify pom.xml (adding dependency to pom.xml and 1.5 compatible)
   
   
   
   
   maven-compiler-plugin
   
   1.5
   1.5
   
   
   
   
   
...
   
   jboss
   jboss-ejb3x
   4.0.3
   system
   ${basedir}\lib\jboss-ejb3x.jar
   
   
   jboss
   jnpserver
   1.0
   system
   ${basedir}\lib\jnpserver.jar
   
   
   jboss
   jboss-common
   1.0
   system
   ${basedir}\lib\jboss-common.jar
   

3.)  write stateless session bean

package net.sf.sample;

import javax.ejb.Stateless;

@Stateless
public class Hello implements HelloLocal, HelloRemote{
   public String echo(){
   return "hello\n";
}

package net.sf.sample;

import javax.ejb.Local;

@Local
public interface HelloLocal{
   public String echo();
}

package net.sf.sample;

import javax.ejb.Remote;

@Remote
public interface HelloRemote{
   public String echo();


4.) run mvn command

mvn clean install

What might cause this problem?

Thank you very much,

env: jboss4.2.2.GA/ maven 2.0.8 / jdk1.6.0_04






 __
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html

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



--
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]






 ___
Rise to the challenge for Sport Relief with Yahoo! For Good

http://uk.promotions.yahoo.com/forgood/

-
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: jspc precompile

[Dooing]

Ok, now I wrote a complete new mail, hope this one's what you wanted me to do 
(or should I have left this topic for now...?!)

> Ok, one questions: is the war assembled correctly (including web.xml)?

Well I think so - building a war works, and when I deploy this war into my 
tomcat server, the app works as it should.

> There must be some option to alter the default path, right??
> You saw the text in jspc maven plugin doc:
> 
> >> 
> >> ${basedir}/target/jspweb.xml
> >> ...
> >> 
> 
> There you can set the path

Nope, I don't think that's it. There you can only define were the jspweb.xml 
should be put. I would need to be able to define a custom path for the webapp 
folder.

However, as a test I changed the path to my webapp folder, and then it 
temporarily worked. However, the maven jspc plugin seeems to be VERY picky 
about the jsp code - I have a taglib directive like this:
<%@ taglib uri="http://jakarta.apache.org/struts/tags-tiles"; prefix="tiles" %>

in my jsps - the url doesn't exist, so the jspc compiler failed.
Well, I read there was a way to fix this issue - I read you had to define 
a taglib uri in the web.xml, but I tried it for about 30 minutes and didn't get 
it to work, so I decided I should leave it for the moment as it's a legacy 
project and the main task at hand is moving to Maven 2.
So I tried the jetty jspc plugin again - on the website I even found a
listing of its parameters:

http://jetty.mortbay.org/jspc-maven-plugin/jspc-mojo.html

However, using:

 ${basedir}/sr/war 

didn't help either. The only way I got this to work was if I created a 
src/webapp folder containing the web.xml.

Then it worked and compiled all JSPs as expected - without throwing the error 
the maven jspc plugin did.

No idea, maybe you got an idea how I could get to run one of the two...

In short, I would need:
The maven jspc or jetty jspc plugin working with a custom webapp folder,
if you recommend me to use the maven jspc plugin, I would need a way to either 
lower the error level, or I would need to have a way how to fix this struts tld 
error.

Thanks a lot, your help is really appreciated! :)

Stefanie
-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

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

Re: javax.naming.CommunicationException: Receive timed out problem

[Neo Anderson]

Thanks your reply. Finally I solved the problem. The problem comes from the 
wrong way to setup initial context. The correct way to do that is by (in my 
test case, e.g., HelloTest)

protected void setUp() throws Exception{
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, 
"org.jnp.interfaces.NamingContextFactory");
env.put(Context.PROVIDER_URL, "localhost");
env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces" 
);
initialContext = new InitialContext(env);
}

However, I encounter a new question. I use test case to call my ejb application 
(stateless session bean). Thus I found out when executing command 'mvn clean 
install,'  it will do test first, resulting failure because  the ejb artifact 
is still not yet deployed to the server. How can deploy to and launch the 
server first before the test case executed. 

Thanks in advice.

- Original Message 
From: VUB Stefan Seidel <[EMAIL PROTECTED]>
To: Maven Users List 
Sent: Monday, 3 March, 2008 9:49:25 PM
Subject: Re: javax.naming.CommunicationException: Receive timed out problem

Hi,

this is most likely not a maven problem. It seems your test tries to 
connect to a remote JBoss instance but cannot contact it (not deployed?).

regards,

Stefan

Neo Anderson wrote:
> Hi
> 
> I am new to maven. And by following 
> http://openejb.apache.org/3.0/simple-stateless-example.html I write a simple 
> stateless session bean (ejb3) to test the jboss and maven,but encounter a 
> problem. The error issues 
> 
> testHelloRemote(net.sf.sample.HelloTest)  Time elapsed: 5.06 sec  <<< ERROR!
> javax.naming.CommunicationException: Receive timed out [Root exception is 
> java.net.SocketTimeoutException: Receive timed out]
> 
> The way how I test is 
> 
> 1.) create ejb module
> mvn archetype:create -DgroupId=net.sf.sample -DartifactId=hello -Dversion=1.0 
> 
> 2.) modify pom.xml (adding dependency to pom.xml and 1.5 compatible)
> 
> 
> 
> 
> maven-compiler-plugin
> 
> 1.5
> 1.5
> 
> 
> 
> 
> 
> ...
> 
> jboss
> jboss-ejb3x
> 4.0.3
> system
> ${basedir}\lib\jboss-ejb3x.jar
> 
> 
> jboss
> jnpserver
> 1.0
> system
> ${basedir}\lib\jnpserver.jar
> 
> 
> jboss
> jboss-common
> 1.0
> system
> ${basedir}\lib\jboss-common.jar
> 
> 
> 3.)  write stateless session bean
> 
> package net.sf.sample;
> 
> import javax.ejb.Stateless;
> 
> @Stateless
> public class Hello implements HelloLocal, HelloRemote{
> public String echo(){
> return "hello\n";
> }
> 
> package net.sf.sample;
> 
> import javax.ejb.Local;
> 
> @Local
> public interface HelloLocal{
> public String echo();
> }
> 
> package net.sf.sample;
> 
> import javax.ejb.Remote;
> 
> @Remote
> public interface HelloRemote{
> public String echo();
> 
> 
> 4.) run mvn command
> 
> mvn clean install
> 
> What might cause this problem?
> 
> Thank you very much,
> 
> env: jboss4.2.2.GA/ maven 2.0.8 / jdk1.6.0_04
> 
> 
> 
> 
> 
> 
>   __
> Sent from Yahoo! Mail.
> A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-- 
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]






  ___ 
Rise to the challenge for Sport Relief with Yahoo! For Good  

http://uk.promotions.yahoo.com/forgood/

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

Re: exec plugin info needed

[Wayne Fay]

The root cause of your error is:
Caused by: java.lang.NoClassDefFoundError: javax/jms/MessageListener

You should probably add a dependency to the javax jms artifact, or to
the Geronimo jms spec artifact (easier).

Wayne

On 1/24/08, Daniele De Francesco <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've got to get working maven-exec-plugin.
>
> I know I have somewhere a classpath problem or a configuration onebut I
> cannot find it yet...
>
> Ok then, my environment is like this: Windows XP 5.1,x86, maven 2.0.8, Java
> version: 1.5.0_10
>
> here's the command I'm issuing:
>
> mvn -e -Dmaven.test.skip=true clean install exec:java
>
> and here's mvn stacktrace:
>
> []
>
> [INFO] [exec:java]
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] null
>
> [INFO]
> 
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Defa
> ultLifecycleExecutor.java:564)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:493)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (Defau
> ltLifecycleExecutor.java:463)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLi
> fecycleExecutor.java:143)
>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)
> Caused by: org.apache.maven.plugin.MojoExecutionException
>at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java
> :318)
>at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPlugi
> nManager.java:447)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Defa
> ultLifecycleExecutor.java:539)
>... 16 more
> Caused by: java.lang.NoClassDefFoundError: javax/jms/MessageListener
>at java.lang.ClassLoader.defineClass1(Native Method)
>at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>at java.security.SecureClassLoader.defineClass(
> SecureClassLoader.java:12
> 4)
>at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>at java.security.AccessController.doPrivileged(Native Method)
>at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:264)
>at java.lang.Thread.run(Thread.java:595)
> [INFO]
> 
> [INFO] Total time: 13 seconds
> [INFO] Finished at: Thu Jan 24 12:38:28 CET 2008
> [INFO] Final Memory: 8M/25M
> [INFO]
> 
>
>
> the plugin config is like this (obviously I tried many configs but the
> result is, suspiciously, always the same)
>  [...]
>
>org.codehaus.mojo
>exec-maven-plugin
>1.1-beta-1
>
>
>java
>it.sogei.gwb.ailclient.AILInterface
> 
>-
> Djava.security.policy=ailinterface.policy -
> Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -
> Djava.naming.provider.url=jnp://localhost:1099 -
> Djava.naming.factory.url.pkgs=org.jboss.naming.client -
> Dj2ee.clientName=ailclient
>-jar
>-classpath
>
>${project.build.directory}/ailclient-

Re: Locking down to only use Archiva ... except for encumbered JARs

[Julian Dunn]

That worked -- thanks.

- Julian 
 
>>> "Wendy Smoak" <[EMAIL PROTECTED]> 03/03/08 4:24 PM >>> 
On Mon, Mar 3, 2008 at 2:19 PM, Julian Dunn <[EMAIL PROTECTED]>
wrote:

>  I have set up Archiva to have two repositories:
...
>  However, if I put * for the default
repository,
>  the restricted repo will never be consulted for jars like
activation,
>  jta, etc. -- M2 will simply complain that those JARs are not found.
>
>  Is there a way to fix this?

Try adding a mirror for the restricted repo, in addition to the one
that says mirrorOf=*.

-- 
Wendy

Re: Misleading error message in Maven2? If not where are .jar files?

[Wayne Fay]

Or just use the Geronimo spec jars:
http://repo1.maven.org/maven2/geronimo-spec/geronimo-spec-jms/1.1-rc4/

  geronimo-spec
  geronimo-spec-jms
  1.1-rc4

Wayne

On 2/29/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 29, 2008 at 9:09 PM, lanchez <[EMAIL PROTECTED]> wrote:
>
> >  I went to the following URL : http://java.sun.com/products/jms/docs.html
> >  to download a jar to put in the repo but at this URL there are only PDF
> >  files (no reference impl's).
>
> There's one link for the specification, and another that says
> "Download the version 1.1 API Documentation, ___Jar___ and Source".
> The latter should have what you're looking for.
>
> There's more info about Sun jars, here:
> http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
>
> --
> 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: Problem providing project version via system property

[Wayne Fay]

You should be using the release plugin which will rewrite the
 tag along with SNAPSHOTs until you are ready for a final
release etc.

As you've discovered, the ${final.version} thing is a bad idea and
doesn't really work. If you check the archives, you'll see similar
posts from other people who have tried this before and eventually ran
into problems, and the advice given to them is also "use release
plugin".

Wayne

On 3/3/08, Singh, Manish <[EMAIL PROTECTED]> wrote:
> Problem definition:
> I have projects A,B,C,D,E
> A,B and C are packaged together for application Y
> A, D and E are packaged together for application Z
>
> There is a parent project, Y defined whose pom includes A,B and C as
> modules.
> Thus A,B and C all point to Y as parent.
>
> Similarly there is a parent project, Z defined whose pom includes A, D
> and E as modules.
> Now D and E both point to Z as parent, but A as mention above is
> pointing to Y as parent.
>
> When I do builds for parent projects Y or Z, everything builds fine.
> But when I try doing the build for just D or E it fails complaining
> about could not download artifact for G:Y:jar:${final.version} (trust
> me, I have the system property defined)
>
> A,B,C,D and E all belong to same GroupId G.
>
> Project version in all my poms looks something like this,
> ${final.version}
> Build done is fine with this system provided property but the installed
> poms in local repository also keep this string as is and does not
> replace actual version before creating those pom files in local
> repository when I run mvn install.
>
> I think my problem would be resolved if those poms had actual version
> numbers in them.
>
> Does anyone know why the installed pom does not get actual version
> number and how to fix it?
> Or any other solution to my problem above?
>
> Thanks,
> Manish
>
> Y
> Z--|
>|--A
>|--B
>|--C
>|--D
>|--E
>

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

RE: maven-dependency-plugin not unpacking properly

[EJ Ciramella]

This page shows 2.0-alpha-4


http://maven.apache.org/plugins/index.html

I have it working using version 2.0 of the plugin. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:39 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I added an IT for this, it's working ok: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin
/src/it/filterunpack/?pathrev=633266

Look at the pom to see how to use it. (should be the same for unpack
goal too)

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:20 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

Are you running this from the command line like mvn dependency:unpack /
unpack-dependencies or is it bound to a phase in your pom? If it's from
the CLI, you may be seeing this maven bug:
MNG-3401 (also see first faq entry in the dependency plugin faq)

I'm not sure where you see 2.0-alpha-4 because the main site says 2.0:
http://maven.apache.org/plugins/maven-dependency-plugin/

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

Ahhh - very true.  But at the "entry" point for the dependency docs, it
specifies "2.0-alpha-4".

Please fix. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:55 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The version specific docs are a new thing, but what it does say is this:

excludes

A comma separated list of file patterns to exclude when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.excludes}

includes

A comma separated list of file patterns to include when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.includes}

Notice the @since part.

I'll create a test project to double check this functionality.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:41 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

-
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]

Problem providing project version via system property

[Singh, Manish]

Problem definition:
I have projects A,B,C,D,E
A,B and C are packaged together for application Y
A, D and E are packaged together for application Z

There is a parent project, Y defined whose pom includes A,B and C as
modules.
Thus A,B and C all point to Y as parent.

Similarly there is a parent project, Z defined whose pom includes A, D
and E as modules.
Now D and E both point to Z as parent, but A as mention above is
pointing to Y as parent.

When I do builds for parent projects Y or Z, everything builds fine.
But when I try doing the build for just D or E it fails complaining
about could not download artifact for G:Y:jar:${final.version} (trust
me, I have the system property defined)

A,B,C,D and E all belong to same GroupId G.

Project version in all my poms looks something like this,
${final.version}
Build done is fine with this system provided property but the installed
poms in local repository also keep this string as is and does not
replace actual version before creating those pom files in local
repository when I run mvn install.

I think my problem would be resolved if those poms had actual version
numbers in them.

Does anyone know why the installed pom does not get actual version
number and how to fix it?
Or any other solution to my problem above?

Thanks,
Manish

Y
Z--|
|--A
|--B
|--C
|--D
|--E

RE: maven-dependency-plugin not unpacking properly

[Brian E. Fox]

I added an IT for this, it's working ok: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin
/src/it/filterunpack/?pathrev=633266

Look at the pom to see how to use it. (should be the same for unpack
goal too)

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:20 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

Are you running this from the command line like mvn dependency:unpack /
unpack-dependencies or is it bound to a phase in your pom? If it's from
the CLI, you may be seeing this maven bug:
MNG-3401 (also see first faq entry in the dependency plugin faq)

I'm not sure where you see 2.0-alpha-4 because the main site says 2.0:
http://maven.apache.org/plugins/maven-dependency-plugin/

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

Ahhh - very true.  But at the "entry" point for the dependency docs, it
specifies "2.0-alpha-4".

Please fix. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:55 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The version specific docs are a new thing, but what it does say is this:

excludes

A comma separated list of file patterns to exclude when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.excludes}

includes

A comma separated list of file patterns to include when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.includes}

Notice the @since part.

I'll create a test project to double check this functionality.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:41 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

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


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


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


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


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


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


-

RE: maven-dependency-plugin not unpacking properly

[Brian E. Fox]

Are you running this from the command line like mvn dependency:unpack /
unpack-dependencies or is it bound to a phase in your pom? If it's from
the CLI, you may be seeing this maven bug:
MNG-3401 (also see first faq entry in the dependency plugin faq)

I'm not sure where you see 2.0-alpha-4 because the main site says 2.0:
http://maven.apache.org/plugins/maven-dependency-plugin/

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 3:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

Ahhh - very true.  But at the "entry" point for the dependency docs, it
specifies "2.0-alpha-4".

Please fix. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:55 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The version specific docs are a new thing, but what it does say is this:

excludes

A comma separated list of file patterns to exclude when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.excludes}

includes

A comma separated list of file patterns to include when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.includes}

Notice the @since part.

I'll create a test project to double check this functionality.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:41 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

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


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


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


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


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


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


-
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: javax.naming.CommunicationException: Receive timed out problem

[David Blevins]

Right, this is not a maven thing.  JBoss didn't start.  Simply put  
JBoss doesn't do embedded testing like OpenEJB does, they require a  
lot more setup and configuration to get going.  There are a lot of  
JBoss (or Glassfish, etc.) users who use OpenEJB for their build time  
testing as it's a lot simpler and faster and the tests ultimately  
aren't vendor specific anyway.  One of the benefits of developing  
against an open standard, you can use the best tool for the specific  
job.


-David

On Mar 3, 2008, at 5:49 AM, VUB Stefan Seidel wrote:


Hi,

this is most likely not a maven problem. It seems your test tries to  
connect to a remote JBoss instance but cannot contact it (not  
deployed?).


regards,

Stefan

Neo Anderson wrote:

Hi
I am new to maven. And by following http://openejb.apache.org/3.0/simple-stateless-example.html 
 I write a simple stateless session bean (ejb3) to test the jboss  
and maven,but encounter a problem. The error issues  
testHelloRemote(net.sf.sample.HelloTest)  Time elapsed: 5.06 sec   
<<< ERROR!
javax.naming.CommunicationException: Receive timed out [Root  
exception is java.net.SocketTimeoutException: Receive timed out]

The way how I test is 1.) create ejb module
mvn archetype:create -DgroupId=net.sf.sample -DartifactId=hello - 
Dversion=1.0 2.) modify pom.xml (adding dependency to pom.xml and  
1.5 compatible)

   
   
   
   
   maven-compiler-plugin
   
   1.5
   1.5
   configuration>

   
   
   
...
   
   jboss
   jboss-ejb3x
   4.0.3
   system
   ${basedir}\lib\jboss-ejb3x.jar
   
   
   jboss
   jnpserver
   1.0
   system
   ${basedir}\lib\jnpserver.jar
   
   
   jboss
   jboss-common
   1.0
   system
   ${basedir}\lib\jboss-common.jar
   
3.)  write stateless session bean
package net.sf.sample;
import javax.ejb.Stateless;
@Stateless
public class Hello implements HelloLocal, HelloRemote{
   public String echo(){
   return "hello\n";
}package net.sf.sample;
import javax.ejb.Local;
@Local
public interface HelloLocal{
   public String echo();
}
package net.sf.sample;
import javax.ejb.Remote;
@Remote
public interface HelloRemote{
   public String echo();
4.) run mvn command
mvn clean install
What might cause this problem?
Thank you very much,
env: jboss4.2.2.GA/ maven 2.0.8 / jdk1.6.0_04
 __
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
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]





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

RE: maven-dependency-plugin not unpacking properly

[EJ Ciramella]

Ahhh - very true.  But at the "entry" point for the dependency docs, it
specifies "2.0-alpha-4".

Please fix. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:55 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The version specific docs are a new thing, but what it does say is this:

excludes

A comma separated list of file patterns to exclude when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.excludes}

includes

A comma separated list of file patterns to include when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.includes}

Notice the @since part.

I'll create a test project to double check this functionality.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:41 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

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


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


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


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


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


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


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

RE: maven-dependency-plugin not unpacking properly

[Brian E. Fox]

The version specific docs are a new thing, but what it does say is this:

excludes

A comma separated list of file patterns to exclude when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.excludes}

includes

A comma separated list of file patterns to include when unpacking the
artifact. i.e. **\/*.xml,**\/*.properties

* Type : java.lang.String
* Since : 2.0-alpha-5
* Required : No
* Expression : ${mdep.unpack.includes}

Notice the @since part.

I'll create a test project to double check this functionality.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:41 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

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


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


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


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


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


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

Re: Why is the parent pom upload compulsory ?

[Olivier Lamy]

Hi,
inline.

2008/3/3, MATHUS Baptiste <[EMAIL PROTECTED]>:
> Hi all,
>
>  I'm evaluating continuum 1.1.
Cool :-)
>  We've been using the 1.0 for some months now, and consider migrating mostly 
> for the group management feature.
>  In fact, we're about to add more and more projects, and displaying them all 
> in the same view seems quite unreasonnable.
>  I just tried adding one of our project and there seems to have a problem 
> with the parent pom. The thing I don't get is why it's needed.
>  Is the "installation" feature related to this problem ? I didn't configure 
> any "installation", should I configure my maven installation ? Doesn't 
> continuum just use the path/environment it's running in by default ?


Yep continuum will use default user settings (PATH, JAVA_HOME etc...)

>
>  In fact, even if I empty the local repository and run mvn package from the 
> project directory, the parent pom will be downloaded just fine.
>  The mvn command is configured correctly, so why doesn't continuum just use 
> the same configuration ?
This parent pom should be available in a repo, you have to declare
this repo in the settings.xml (~/.m2/settings.xml)
>
>  Maybe we had to do the same thing with continuum 1.0 and I don't remember it 
> ? In fact, I managed to do the build by uploading the parent pom, but it 
> doesn't seem straightforward to me.
>  I also noticed that if I add the parent pom as a project, then delete it. 
> Then adding a project that uses this parent pom works fine.
>  I guess there should be a part in the doc explaining this behaviour :).

When you add the parent pom in continuum, mvn install it in the local
repo.That's why it's available for other builds.

>  I tried to find some doc about it, but didn't find a lot.
>
>  Any advice greatly appreciated :).
>
>  Thanks a lot.
>  Cheers.
>
>
>  -- Baptiste
>
>

RE: maven-dependency-plugin not unpacking properly

[EJ Ciramella]

The docs are for this particular version yet they include this option
(and still it doesn't work).

 

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:40 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

-
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: when will maven 2.0.9 be officially released?

[Raphaël Piéroni]

This page is now up to date.

Raphaël.

2008/3/2, Brett Porter <[EMAIL PROTECTED]>:
> I agree with Wendy.
>
>  You could also whip up a test case using these instructions:
>  http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test
>  as it'll give you a head start on being included in a release.
>
>
>  - Brett
>
>
>  On 03/03/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>  > On Sun, Mar 2, 2008 at 1:28 PM, Andrew Robinson
>  >
>  > <[EMAIL PROTECTED]> wrote:
>  >
>  > > No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug.
>  >  >  2.1 fixed the problem. The earlier releases ran plugins and plugin
>  >  >  executions in random order due to improper use of HashMap.
>  >  >
>  >  >  It is really easy to reproduce the problem. I had 3 executions of the
>  >  >  maven SQL plugin and they ran out of order in JDK 1.6 and are fine in
>  >  >  2.1. JDK 1.5 worked fine as well, so it definitely seems like it was a
>  >  >  collections use bug.
>  >  >
>  >  >  Perhaps MNG-2784 was only a partial fix?
>  >
>  >
>  > No idea, but it looks like all the related issues are closed.  It's
>  >  likely nothing further will happen unless an issue gets reopened or a
>  >  new issue is raised.  (It's also possible there's a technical reason
>  >  the fix for 2.1 can't be backported to 2.0.)
>  >
>  >  Have you tried 2.0.9-SNAPSHOT?  If you can't find an open issue that
>  >  describes the problem you're still having with 2.0.x, I'd open
>  >  another.  Worst case, it might get closed as WONTFIX with an
>  >  explanation...
>  >
>  >
>  >  --
>  >
>  > Wendy
>  >
>  >  -
>  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  >  For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >
>
>
>
> --
>
> Brett Porter
>  Blog: http://blogs.exist.com/bporter/
>
>  -
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: maven-dependency-plugin not unpacking properly

[EJ Ciramella]

2.0-alpha-4

I'm guessing I need to ditch the alpha part now? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:23 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

-
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: maven-dependency-plugin not unpacking properly

[Brian E. Fox]

What version of the plugin are you using? This is only available in 2.0.

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 2:09 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

-
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: maven-dependency-plugin not unpacking properly

[EJ Ciramella]

I initially only had the includes, but I'm getting everything out of the
artifact.

Any other suggestions? 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 1:14 PM
To: Maven Users List
Subject: RE: maven-dependency-plugin not unpacking properly

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

-
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: maven-dependency-plugin not unpacking properly

[Brian E. Fox]

The plexus archiver component code works like this:

return isIncluded( name ) && !isExcluded( name );

So basically the excludes **/* is overriding the includes. Most likely
you only want **/common.properties

--Brian

-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 12:01 PM
To: users@maven.apache.org
Subject: maven-dependency-plugin not unpacking properly

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

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

Re: Jsp precompile

[Wayne Fay]

Stefanie, take a look at the mail headers (I'm certain , in particular
In-Reply-To:
In-Reply-To: <[EMAIL PROTECTED]>
This tells mail clients "all of these emails are related, so you
should organize them as such."

You can see this data in the gmx.net web interface by clicking the
little envelope in the top-right corner above ins Adressbuch which has
the tooltip label Ausdruck der Header-Informationen, just below Hilfe.

Please create a BRAND NEW email every time you want to start a new
topic by simply creating a new email to the Maven Users list. DO NOT
reply to another one, unless you want to continue that discussion.

Wayne

On 3/3/08, Martin Höller <[EMAIL PROTECTED]> wrote:
> On Monday 03 March 2008 wrote [EMAIL PROTECTED]:
> > >  firstly, and again: Do NOT just reply to a random message from the
> > >
> > > mailing list when you start a new topic. Write a NEW MAIL to the
> > > mailing list.
> >
> > I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed
> > the topic. So it should be a new topic, shouldn't it??
>
> No it shouldn't! Have a look at
> http://www.nabble.com/how-do-i-generate-my-first-maven-2.x-project--to15773087s177.html
> to see how most proper mail clients show this thread.
>
> > I can't image the
> > mail adress would "remember" what it was last used to, right???
>
> As Stefan wrote, there are mail header fields that reference previous mails
> from this thread, so just don't use the reply button if you do not reply.
>
> thx,
> - 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
>
>

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

Re: ftp://ibiblio.org/pub/packages/maven2 wiped out?

[Carlos Sanchez]

http://maven.apache.org/guides/mini/guide-mirror-settings.html

On Mon, Mar 3, 2008 at 2:00 AM, Jan Torben Heuer
<[EMAIL PROTECTED]> wrote:
> Martin Gainty wrote:
>
>  > both ftp and http sites for maven2 appear 'down'
>
>  Are there information available? When will maven2 come back? Is there a
>  backup repository?
>
>
>
>  Jan
>
>
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

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

maven-dependency-plugin not unpacking properly

[EJ Ciramella]

Is anyone else able to use the unpack-dependencies plugin goal and
specify, say, a single file?
 

**/*
common.properties
 
I've tried everything I can think of (all kinds of patterens and what
not), but this doesn't work at all.

Re: Jsp precompile

[Martin Höller]

On Monday 03 March 2008 wrote [EMAIL PROTECTED]:
> >  firstly, and again: Do NOT just reply to a random message from the
> >
> > mailing list when you start a new topic. Write a NEW MAIL to the
> > mailing list.
>
> I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed
> the topic. So it should be a new topic, shouldn't it??

No it shouldn't! Have a look at 
http://www.nabble.com/how-do-i-generate-my-first-maven-2.x-project--to15773087s177.html
 
to see how most proper mail clients show this thread.

> I can't image the 
> mail adress would "remember" what it was last used to, right???

As Stefan wrote, there are mail header fields that reference previous mails 
from this thread, so just don't use the reply button if you do not reply.

thx,
- 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.

Re: Maven2 site plugin inheritence

[Christian Kölle]

ewryan wrote:
> I define properties such as ${myVersion}, ${myArtifactId}, ${myGroupId} in
> the parent pom.  These properties are inherited by the children (as
> expected) when running goals such as clean, package, or install.
> 
> I start to see problems when I try to use the site plugin.  

Hi

I asked the very same question a while ago and got no real answer. I
tried to figure out what happened in the code. What i found out is the
following:

The site plugin handles every subproject like a normal top level
project. So it reads the pom for the subproject at first. After that it
tries to locate the pom for the parent project. For this it uses the
information of the  block in the pom.

In our case the  block in the subproject pom depends on
properties from the parent pom that is not known at this point in time
so the properties can't be resolved.

I don't see a satisfying solution for this problem. But i think we need
the knowledge of a maven (plugin) programmer here.

Cheers
Christian

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

RE: Maven2 site plugin inheritence

[Prystash,John]

I've used this workaround to get help with this issue, at least for
site-deploy, in the parent POM:

  file://${user.dir}/site

All the links in the resulting site work.  This might not help with the
inheritance issue, but it might give you a place to start from.

-Original Message-
From: ewryan [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 28, 2008 1:53 PM
To: users@maven.apache.org
Subject: Maven2 site plugin inheritence


I have a multi-module project with the following directory structure:

my-app
|
|---my-client-ui
|   |
|   |---pom.xml
|
|---my-core
|   |
|   |---pom.xml
|
|---my-common
|   |
|   |---pom.xml
|
|---pom.xml


I define properties such as ${myVersion}, ${myArtifactId}, ${myGroupId}
in the parent pom.  These properties are inherited by the children (as
expected) when running goals such as clean, package, or install.

I start to see problems when I try to use the site plugin.  I first run
the install goal to install my project's jars and poms into my local
repo(~/.m2/repository/).  I then verify that the jars and poms are in my
local repo.  When I try to run the site plugin it seems as though maven
is unable to interpret the properties defined in the parent pom.  I
receive the following output for each module:

[INFO]

[INFO] Building my-client-ui
[INFO]task-segment: [site]
[INFO]

[INFO] [site:site]
Downloading:
http://repo1.maven.org/maven2/${myGroupId}/${myArtifactId}/${myVersion}/
${myArtifactId}-${myVersion}.pom
[WARNING] Unable to load parent project from repository: Failed to
validate POM for project ${myGroupId}:${myArtifactId} at Artifact
[${myGroupId}:${myArtifactId}:pom:${myVersion}]
[INFO] Generating "Continuous Integration" report...


I've tried using site:deploy, site:run, and site:stage.  In all cases I
receive a successful build, but all sites generated contain broken
links.
(Note. parent pom's distributionManagement site
url=file:///home/eric/tmp) 

When using site:deploy, there are two issues with the site.  The first
is that none of the modules are listed for the project on the left hand
side of the screen.  The second is that when I go to the Dependence
Convergence section, the links to my project's modules are broken.  In
example, the link to my-client-ui incorrectly points to
http://www.mycompany.com/my-client-ui
when it is in fact located at file:///home/eric/tmp/my-client-ui  (Note.

http://www.mycompany.com is defined in the parent pom as the project's
url).  

site:run demonstrates the same problems as site:deploy. 

When using site:stage -DstagingDirectory=/home/eric/tmp, there are again
two issues w/ the site.  The first is the same, none of the modules are
listed on the left hand side of the screen.  The second is also the
same, except that the links in the Dependency Convergence section now
point to file:///home/eric/localhost/home/eric/tmp/my-client-ui.  This
is incorrect because the files are actually located at
file:///home/eric/tmp/localhost/home/eric/tmp/my-client-ui.  It is
missing the tmp directory in the url string.  

The only way I've been able to get the modules to be displayed on the
left hand side of the screen is using mvn -N site site:deploy.  In this
case, the links point to the "correct" place
(file:///home/eric/tmp/my-client-ui), but the submodule's sites are
never build because of the -N (non-recursive) flag.  Another thing to
note is that the Dependency Convergence section is totally missing from
this site.

The only way I've been able to build a site with links that resolve
properly is if I remove all instances of properties in all of my poms
and replace them with hard coded values.  In this case, the correct
links for the modules do appear on the left hand side of the screen.
The downfall to this approach is that the links in the Dependency
Convergence section now point to http://www.mycompany.com/my-client-ui.

My question is, is it possible for me to use the site plugin with
property inheritance?
--
View this message in context:
http://www.nabble.com/Maven2-site-plugin-inheritence-tp15743257s177p1574
3257.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: when will maven 2.0.9 be officially released?

[Raphaël Piéroni]

Yup, i will do it tonite,
if i have the karma on the wiki.

Raphaël

2008/3/3, Brian E. Fox <[EMAIL PROTECTED]>:
> Hi Raphael, that was something I put together back in July before the 
> archetypeNG was done. Can you update the wiki with the correct info?
>
>
>  -Original Message-
>  From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
>  Sent: Monday, March 03, 2008 6:43 AM
>  To: Maven Users List
>  Subject: Re: when will maven 2.0.9 be officially released?
>
>
> Hi Brett,
>
>  the process for using archetype is no longer revelant.
>
>  Regards,
>
>  Raphaël
>
>  2008/3/2, Brett Porter <[EMAIL PROTECTED]>:
>  > I agree with Wendy.
>  >
>  >  You could also whip up a test case using these instructions:
>  >  http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test
>  >  as it'll give you a head start on being included in a release.
>  >
>  >
>  >  - Brett
>  >
>  >
>  >  On 03/03/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>  >  > On Sun, Mar 2, 2008 at 1:28 PM, Andrew Robinson
>  >  >
>  >  > <[EMAIL PROTECTED]> wrote:
>  >  >
>  >  > > No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug.
>  >  >  >  2.1 fixed the problem. The earlier releases ran plugins and plugin
>  >  >  >  executions in random order due to improper use of HashMap.
>  >  >  >
>  >  >  >  It is really easy to reproduce the problem. I had 3 executions of 
> the
>  >  >  >  maven SQL plugin and they ran out of order in JDK 1.6 and are fine 
> in
>  >  >  >  2.1. JDK 1.5 worked fine as well, so it definitely seems like it 
> was a
>  >  >  >  collections use bug.
>  >  >  >
>  >  >  >  Perhaps MNG-2784 was only a partial fix?
>  >  >
>  >  >
>  >  > No idea, but it looks like all the related issues are closed.  It's
>  >  >  likely nothing further will happen unless an issue gets reopened or a
>  >  >  new issue is raised.  (It's also possible there's a technical reason
>  >  >  the fix for 2.1 can't be backported to 2.0.)
>  >  >
>  >  >  Have you tried 2.0.9-SNAPSHOT?  If you can't find an open issue that
>  >  >  describes the problem you're still having with 2.0.x, I'd open
>  >  >  another.  Worst case, it might get closed as WONTFIX with an
>  >  >  explanation...
>  >  >
>  >  >
>  >  >  --
>  >  >
>  >  > Wendy
>  >  >
>  >  >  -
>  >  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  >  >  For additional commands, e-mail: [EMAIL PROTECTED]
>  >  >
>  >  >
>  >
>  >
>  >
>  > --
>  >
>  > Brett Porter
>  >  Blog: http://blogs.exist.com/bporter/
>  >
>  >  -
>  >
>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  >  For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >
>

Re: javax.naming.CommunicationException: Receive timed out problem

[VUB Stefan Seidel]

Hi,

this is most likely not a maven problem. It seems your test tries to 
connect to a remote JBoss instance but cannot contact it (not deployed?).


regards,

Stefan

Neo Anderson wrote:

Hi

I am new to maven. And by following http://openejb.apache.org/3.0/simple-stateless-example.html I write a simple stateless session bean (ejb3) to test the jboss and maven,but encounter a problem. The error issues 


testHelloRemote(net.sf.sample.HelloTest)  Time elapsed: 5.06 sec  <<< ERROR!
javax.naming.CommunicationException: Receive timed out [Root exception is 
java.net.SocketTimeoutException: Receive timed out]

The way how I test is 


1.) create ejb module
mvn archetype:create -DgroupId=net.sf.sample -DartifactId=hello -Dversion=1.0 


2.) modify pom.xml (adding dependency to pom.xml and 1.5 compatible)




maven-compiler-plugin

1.5
1.5






...

jboss
jboss-ejb3x
4.0.3
system
${basedir}\lib\jboss-ejb3x.jar


jboss
jnpserver
1.0
system
${basedir}\lib\jnpserver.jar


jboss
jboss-common
1.0
system
${basedir}\lib\jboss-common.jar


3.)  write stateless session bean

package net.sf.sample;

import javax.ejb.Stateless;

@Stateless
public class Hello implements HelloLocal, HelloRemote{
public String echo(){
return "hello\n";
}


package net.sf.sample;

import javax.ejb.Local;

@Local
public interface HelloLocal{
public String echo();
}

package net.sf.sample;

import javax.ejb.Remote;

@Remote
public interface HelloRemote{
public String echo();


4.) run mvn command

mvn clean install

What might cause this problem?

Thank you very much,

env: jboss4.2.2.GA/ maven 2.0.8 / jdk1.6.0_04






  __
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html

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



--
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: Jsp precompile

[VUB Stefan Seidel]

[EMAIL PROTECTED] wrote:
 firstly, and again: Do NOT just reply to a random message from the 
mailing list when you start a new topic. Write a NEW MAIL to the mailing 
list.

I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed the topic. So 
it should be a new topic, shouldn't it?? I can't image the mail adress would 
"remember" what it was last used to, right???
--

Ok, I saw too late that the old "subject" line was wrong already.

Anyway, in most mail clients, when  you "reply" to a message, a header 
field "In-Reply-To" is set into the mail with either all (of this 
thread) or the latest message ids of the message(s) you replied to.
Then again, the mail client looks into this header field to determine 
whether the message should be displayed in the same thread or in a new 
thread. Thus, you can change the subject but the mail client will still 
think that it is the same thread because of the "In-Reply-To" header field.
In Thunderbird for example, you can click "View", "Sort By", "Threaded" 
to see what I mean.



Your web.xml needs to be in
src/main/webapp/WEB-INF, 


Well, as we are moving from Maven 1.1 I was told to first move the project as 
it is - using the (legacy) project structure in this first migration step. 
Therefore, I can't yet use src/main/webapp/WEB-INF. My web.xml
is in src/war/WEB-INF, and when it's copied to the target folder, it will be in 
/target/MY_WAR_FILE_NAME/WEB-INF.

Ok, one questions: is the war assembled correctly (including web.xml)?


There must be some option to alter the default path, right??

You saw the text in jspc maven plugin doc:



${basedir}/target/jspweb.xml
...



There you can set the path. Anyway, you wrote you didn't want to let the 
compiler plugin modify the web.xml IIUC? But then the compilation is not 
in effect, because within the web.xml the /...jsp are mapped to the 
compiled ones, so I think you will need to let that happen if you want 
to use the precompiled JSPs.




--
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: when will maven 2.0.9 be officially released?

[Brian E. Fox]

Hi Raphael, that was something I put together back in July before the 
archetypeNG was done. Can you update the wiki with the correct info?

-Original Message-
From: Raphaël Piéroni [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2008 6:43 AM
To: Maven Users List
Subject: Re: when will maven 2.0.9 be officially released?

Hi Brett,

the process for using archetype is no longer revelant.

Regards,

Raphaël

2008/3/2, Brett Porter <[EMAIL PROTECTED]>:
> I agree with Wendy.
>
>  You could also whip up a test case using these instructions:
>  http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test
>  as it'll give you a head start on being included in a release.
>
>
>  - Brett
>
>
>  On 03/03/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>  > On Sun, Mar 2, 2008 at 1:28 PM, Andrew Robinson
>  >
>  > <[EMAIL PROTECTED]> wrote:
>  >
>  > > No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug.
>  >  >  2.1 fixed the problem. The earlier releases ran plugins and plugin
>  >  >  executions in random order due to improper use of HashMap.
>  >  >
>  >  >  It is really easy to reproduce the problem. I had 3 executions of the
>  >  >  maven SQL plugin and they ran out of order in JDK 1.6 and are fine in
>  >  >  2.1. JDK 1.5 worked fine as well, so it definitely seems like it was a
>  >  >  collections use bug.
>  >  >
>  >  >  Perhaps MNG-2784 was only a partial fix?
>  >
>  >
>  > No idea, but it looks like all the related issues are closed.  It's
>  >  likely nothing further will happen unless an issue gets reopened or a
>  >  new issue is raised.  (It's also possible there's a technical reason
>  >  the fix for 2.1 can't be backported to 2.0.)
>  >
>  >  Have you tried 2.0.9-SNAPSHOT?  If you can't find an open issue that
>  >  describes the problem you're still having with 2.0.x, I'd open
>  >  another.  Worst case, it might get closed as WONTFIX with an
>  >  explanation...
>  >
>  >
>  >  --
>  >
>  > Wendy
>  >
>  >  -
>  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  >  For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >
>
>
>
> --
>
> Brett Porter
>  Blog: http://blogs.exist.com/bporter/
>
>  -
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

javax.naming.CommunicationException: Receive timed out problem

[Neo Anderson]

Hi

I am new to maven. And by following 
http://openejb.apache.org/3.0/simple-stateless-example.html I write a simple 
stateless session bean (ejb3) to test the jboss and maven,but encounter a 
problem. The error issues 

testHelloRemote(net.sf.sample.HelloTest)  Time elapsed: 5.06 sec  <<< ERROR!
javax.naming.CommunicationException: Receive timed out [Root exception is 
java.net.SocketTimeoutException: Receive timed out]

The way how I test is 

1.) create ejb module
mvn archetype:create -DgroupId=net.sf.sample -DartifactId=hello -Dversion=1.0 

2.) modify pom.xml (adding dependency to pom.xml and 1.5 compatible)




maven-compiler-plugin

1.5
1.5





...

jboss
jboss-ejb3x
4.0.3
system
${basedir}\lib\jboss-ejb3x.jar


jboss
jnpserver
1.0
system
${basedir}\lib\jnpserver.jar


jboss
jboss-common
1.0
system
${basedir}\lib\jboss-common.jar


3.)  write stateless session bean

package net.sf.sample;

import javax.ejb.Stateless;

@Stateless
public class Hello implements HelloLocal, HelloRemote{
public String echo(){
return "hello\n";
}

package net.sf.sample;

import javax.ejb.Local;

@Local
public interface HelloLocal{
public String echo();
}

package net.sf.sample;

import javax.ejb.Remote;

@Remote
public interface HelloRemote{
public String echo();


4.) run mvn command

mvn clean install

What might cause this problem?

Thank you very much,

env: jboss4.2.2.GA/ maven 2.0.8 / jdk1.6.0_04






  __
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html

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

RE: Re: ftp://ibiblio.org/pub/packages/maven2 wiped out?

[Brian E. Fox]

We don't control ibiblio, but it is only a mirror. The real location is
here: http://maven.apache.org/download.html

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jan Torben Heuer
Sent: Monday, March 03, 2008 5:01 AM
To: users@maven.apache.org
Subject: Re: ftp://ibiblio.org/pub/packages/maven2 wiped out?

Martin Gainty wrote:

> both ftp and http sites for maven2 appear 'down'

Are there information available? When will maven2 come back? Is there a
backup repository?

Jan


-
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: ftp://ibiblio.org/pub/packages/maven2 wiped out?

[VUB Stefan Seidel]

Jan Torben Heuer wrote:

Martin Gainty wrote:


both ftp and http sites for maven2 appear 'down'


Is there a
backup repository?

Yes, the one you have running locally using maven-proxy, archiva or 
proximity so that the main repo has less load.


SCNR,

Stefan

--
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: Jsp precompile

[Dooing]

 firstly, and again: Do NOT just reply to a random message from the 
> mailing list when you start a new topic. Write a NEW MAIL to the mailing 
> list.
I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed the 
topic. So it should be a new topic, shouldn't it?? I can't image the mail 
adress would "remember" what it was last used to, right???
--
>Your web.xml needs to be in
> src/main/webapp/WEB-INF, 

Well, as we are moving from Maven 1.1 I was told to first move the project as 
it is - using the (legacy) project structure in this first migration step. 
Therefore, I can't yet use src/main/webapp/WEB-INF. My web.xml
is in src/war/WEB-INF, and when it's copied to the target folder, it will be in 
/target/MY_WAR_FILE_NAME/WEB-INF.

There must be some option to alter the default path, right??

Thanks in advance,

Stefanie


-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

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

Re: Jsp precompile

[VUB Stefan Seidel]

[EMAIL PROTECTED] wrote:

Hi,



Hi,

firstly, and again: Do NOT just reply to a random message from the 
mailing list when you start a new topic. Write a NEW MAIL to the mailing 
list.



Trying to precompile Jsp's but can't get it to work.

I tried the plugins:

Maven jspc plugin:
http://mojo.codehaus.org/jspc-maven-plugin/usage.html



We're using that one too. Your web.xml needs to be in
src/main/webapp/WEB-INF, and is from there on copied automatically to 
whatever you specify in the maven-war-plugin.
Which version of the jspc-maven-plugin are you using? 1.4.6 works great 
here.


regards,

Stefan

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

Jsp precompile

[Dooing]

Hi,

Trying to precompile Jsp's but can't get it to work.

I tried the plugins:

Maven jspc plugin:
http://mojo.codehaus.org/jspc-maven-plugin/usage.html

Maven Jetty Jspc Plugin:
http://docs.codehaus.org/display/JETTY/Maven+Jetty+Jspc+Plugin

However, both don't work for me.
Maven jspc says:
[INFO] JSPC Error
Embedded error: The -uriroot option must specify a pre-existing directory

Jetty jspc says:

[INFO] : org.apache.jasper.JasperException: PWC6149: The -uriroot option must 
specify a pre-existing directory
Failure processing jsps

No idea what this means! :-( (-X or -e didn't tell me much more either)
My project layout isn't using the default, as it's a legacy project.

The jspc plugin seems to be searching for the web.xml.
The default seems to be target/web.xml, in my case its under 
target/MY_WAR_FILE_NAME/WEB-INF/web.xml.

I tried to configure the maven war plugin accordingly:

  org.apache.maven.plugins
  maven-war-plugin
  
${basedir}/target/MY_WAR_FILE_NAME/WEB-INF/web.xml
  
   

However, this didn't help either. Maybe I looking in the wrong direction??
No idea, both jspc documentations are VERY short. Other people seemed to have 
similar problems saying "The -uriroot option must specify a pre-existing 
directory" - but I couldn't find any solution to this problem on the web.

Maybe you can help out?

Thanks in advance,

Stefanie





-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

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

Re: when will maven 2.0.9 be officially released?

[Raphaël Piéroni]

Hi Brett,

the process for using archetype is no longer revelant.

Regards,

Raphaël

2008/3/2, Brett Porter <[EMAIL PROTECTED]>:
> I agree with Wendy.
>
>  You could also whip up a test case using these instructions:
>  http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test
>  as it'll give you a head start on being included in a release.
>
>
>  - Brett
>
>
>  On 03/03/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>  > On Sun, Mar 2, 2008 at 1:28 PM, Andrew Robinson
>  >
>  > <[EMAIL PROTECTED]> wrote:
>  >
>  > > No, 2.0.7 and 2.0.8 both do not work with JDK 1.6 because of this bug.
>  >  >  2.1 fixed the problem. The earlier releases ran plugins and plugin
>  >  >  executions in random order due to improper use of HashMap.
>  >  >
>  >  >  It is really easy to reproduce the problem. I had 3 executions of the
>  >  >  maven SQL plugin and they ran out of order in JDK 1.6 and are fine in
>  >  >  2.1. JDK 1.5 worked fine as well, so it definitely seems like it was a
>  >  >  collections use bug.
>  >  >
>  >  >  Perhaps MNG-2784 was only a partial fix?
>  >
>  >
>  > No idea, but it looks like all the related issues are closed.  It's
>  >  likely nothing further will happen unless an issue gets reopened or a
>  >  new issue is raised.  (It's also possible there's a technical reason
>  >  the fix for 2.1 can't be backported to 2.0.)
>  >
>  >  Have you tried 2.0.9-SNAPSHOT?  If you can't find an open issue that
>  >  describes the problem you're still having with 2.0.x, I'd open
>  >  another.  Worst case, it might get closed as WONTFIX with an
>  >  explanation...
>  >
>  >
>  >  --
>  >
>  > Wendy
>  >
>  >  -
>  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  >  For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >
>
>
>
> --
>
> Brett Porter
>  Blog: http://blogs.exist.com/bporter/
>
>  -
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [m2] Jetty 6 Plugin does not recognize custom webapp source directory

[Adrian Herscu]

Hi,

What if I have an additional webapp source folder, like:

  
org.apache.maven.plugins
maven-war-plugin

  

  src-gen/main/webapp

  
 
   

How can I tell Jetty to deploy this folder as well?

TIA,
Adrian.

Brett Porter wrote:

Hi Matt,

Check out the Jetty docs:
http://jetty.mortbay.org/jetty6/maven-plugin/howto.html

You can configure the web resources path. Unfortunately, we haven't
enabled a mechanism for the war plugin to share its configuration.

- Brett

On 1/11/06, Matt Raible <[EMAIL PROTECTED]> wrote:

I decided to try Brett's Jetty 6 HowTo this morning:

http://blogs.codehaus.org/people/brett/archives/001306_developing_with_jetty_where_have_you_been_all_my_life.html

Unfortunately, it doesn't seem to work with my custom webapp source
directory.  Here's my pom.xml:

  
maven-war-plugin

  web

  
  
org.mortbay.jetty
maven-jetty6-plugin

10
/

  

[INFO] [jetty6:run]
[INFO] Configuring Jetty for project: Equinox
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Webapp source directory C:\Source\equinox\src\main\webapp does not exist
[INFO] -
---
[INFO] For more information, run Maven with the -e switch
[INFO] -
---
[INFO] Total time: 3 minutes 25 seconds
[INFO] Finished at: Tue Jan 10 07:40:45 MST 2006
[INFO] Final Memory: 4M/8M
[INFO] -

Matt

-
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: Tool for generating an archetype catalog

[Raphaël Piéroni]

Hi,

Please add a JIRA for enhancing the crawl goal

Regards,

Raphaël

2008/3/3, Gert Vanthienen <[EMAIL PROTECTED]>:
>
>  L.S.,
>
>  I would like to create an archetype catalog for the Apache ServiceMix
>  project.  Is there a tool available for making this task a bit easier or can
>  I e.g. add a filter to the archetype:crawl goal to crawl only a part of the
>  local repository?
>
>  Thanks in advance,
>
>  Gert
>
>  -
>  ---
>  Gert Vanthienen
>  http://www.anova.be
>
> --
>  View this message in context: 
> http://www.nabble.com/Tool-for-generating-an-archetype-catalog-tp15799921s177p15799921.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: ftp://ibiblio.org/pub/packages/maven2 wiped out?

[Jan Torben Heuer]

Martin Gainty wrote:

> both ftp and http sites for maven2 appear 'down'

Are there information available? When will maven2 come back? Is there a
backup repository?

Jan


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

Tool for generating an archetype catalog

[Gert Vanthienen]

L.S.,

I would like to create an archetype catalog for the Apache ServiceMix
project.  Is there a tool available for making this task a bit easier or can
I e.g. add a filter to the archetype:crawl goal to crawl only a part of the
local repository?

Thanks in advance,

Gert

-
---
Gert Vanthienen
http://www.anova.be
-- 
View this message in context: 
http://www.nabble.com/Tool-for-generating-an-archetype-catalog-tp15799921s177p15799921.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]