MOJO question

[maarten roosendaal]

Hi,

In Maven 1 we had a 'wrapper' plugin that executed standard maven goals and an 
executable and also executed goals from our own custom made plugins through the 
plugin.jelly. Our projects executed Maven 1 with the goal 'custom:buildAll' and 
it was very easily changed.

What is the best way of writing the same type of 'wrapper' plugin for Maven 2?

Thanks,
Maarten




 

The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

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

POMs for Third Party Libraries

[jchuah]

What is the best way to deal with third party libraries that are not 
released as maven 2 projects?  I know about the install and deploy 
plug-ins, but I am worried about dependency management.  A lot of the 
third party libraries we use have the following problems:

1) Some of the library's dependencies are only needed for specific 
functionality (ie a db library only needs the postgres jars when used with 
postgres)
2) The library is distributed with unversioned jars
3) The library is distributed with nightly or dev build jars

So far, our solution has been to create a custom pom with all the 
dependencies marked as optional dependencies.  This negates the benefit of 
transitive dependencies, but since these are third party libraries it is 
very hard for us to tell what is truly required.  At least with optional 
dependencies, the pom file itself contains clues about the dependencies. 

For unversioned and nightly or dev build jars, we have been adding them 
with the groupId of the third party library and appending the name and 
version of the third party library to the dependency.  Does this sound 
like a good solution or does anybody have a better one?  We are trying to 
avoid losing the original jars distributed with the library.

Thanks,
Joon Chuah

automatically download dependecies

[Advait Trivedi]

I have a POM containing dependencies. I run some plugin goals which are not
bound to any lifecycle phase from this directory. Maven does not download
dependencies specified in POM. My requirement is to download all
dependencies specified in POM at this time. I understand that invoking "mvn
install" from this directory will download all the dependencies. But I don't
want to do that. I also tried antlib, but that too downloads only when I
invoke "mvn install". Is there a possible solution?

 

Thanks & Regards,

Advait Trivedi, 

Sr. Software Engineer,

Mphasis Ltd.

 

Adding a phase to maven-release-plugin

[William Ferguson]

Hi,

I have a plugin that needs to be executed either 
1) after the maven-release-plugin's scm-tag phase but before the
scm-commit-development phase OR
2) after maven-release-plugin:prepare

Option 1 is preferred as it would mean just 2 commits to the trunk
during release.
Option 2 would generate an extra commit.

I think I can see how to do option 1, but it requires modifying the
maven-release-manager.
I believe just adding a phase in components.xml and the impl for it.
But then I need to consider managing such a mod if it can't be folded
back into the plugin.
I'll probably push on this front in any case.

But in the meantime, how do I couple 2 plugin's together to achieve
option 2.
Is there some way to specify that the release-plugin should always run
before my plugin?

William

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

Re: Maven remote repository - AsyncWeb

[Wayne Fay]

If you would like to see the AsyncWeb artifacts available in the Maven
repository, submit a bug/request to the AsyncWeb development team and
ask that they make their application/library/etc available in the
Maven repo.

Wayne

On 5/22/07, jing hez <[EMAIL PROTECTED]> wrote:

Hi

I looked at maven2/org/safehaus  and I don't see AsyncWeb in Maven
remote repository.

--

Hez

AsyncWeb
http://docs.safehaus.org/display/ASYNCWEB/Home

-
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: access plugin groupId/artifactId/version from within plugin

[Jörg Schaible]

ertnutler wrote on Monday, May 21, 2007 7:03 PM:

> I have a plugin that does some generation, but I want to be
> able to print the
> groupId/artifactId/version of the plugin to the file that
> gets generated.  I
> don't see anything in the docs that addresses this, and when
> I step through
> my plugin in eclipse, the pluginContext Map is empty.
> 
> How do I get access to this information from a plugin at runtime?

You may read it as resource from META-INF/maven/plugin.xml.

- Jörg

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

Re: How to create site with just jar files?

[Wayne Fay]

Please describe (specifically) what you are trying to do, what end
results you are hoping to achieve, and someone on this list will most
likely reply back with information that may prove helpful.

Wayne

On 5/22/07, Dennis Cook <[EMAIL PROTECTED]> wrote:

Okay, so adding the  element to the POM helped get past 
the error message, but the result was did not provide what I was looking for.  I got 
a staging directory containing some template html files.  Neither the application 
library nor any of the supporting libraries were present.

 How do I get all of the libraries that make up the application into one 
location?

Dennis Cook <[EMAIL PROTECTED]> wrote:
 I am new to maven2 and trying to convert a project that is using a makefile to 
maven2. This is a simple java application, one main jar with 3 dependent 
libraries. I have gotten the build process to work up to the install goal. But 
I need to progress to the point that the application jar and its supporting 
libraries are delivered to another directory on the local (and eventually 
remote) host.
From the information I can find in the doc I think the site:stage goal is the 
one I need, but I hit an error from in this goal that I do not understand:
From the command mvn site:stage
The error:
[INFO] Error during site generation
Embedded error: C:\development\nethaggler\relay-mail\target\staging\Unnamed - 
relay-mailer:relay-mailer:jar:0.0.1\integration.html (The filename, directory 
name, or volume label syntax is incorrect)
My project has has no html files so why is it looking for this integration.html 
file?




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

Re: how to change the dependency reading order in maven 2.0.6

[Wayne Fay]

The Maven2 deploy plugin can deploy files to a Maven1 ("legacy") style
repository layout. See this page for more details, specifically the
"repositoryLayout" parameter:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html

Wayne

On 5/21/07, Kiran Kodlady <[EMAIL PROTECTED]> wrote:


Hey wayne..

U r right...
I am using layout structure similiar to maven1..


Wayne Fay wrote:
>
> It sounds like you are dealing with a Maven1 repository layout.
>
> Is that correct? Or is this a layout which just happens to be similar
> to Maven1, but has some small differences etc?
>
> Wayne
>
> On 5/21/07, Kiran Kodlady <[EMAIL PROTECTED]> wrote:
>>
>> hello...all,
>>
>> I got some interesting question here..
>>
>> At our project specific remote repository , below mentioned structure has
>> been followed for  storing a particular jar :
>>
>> es-core-->jars-->es-asynchronous-4.0.8
>>
>> But latest maven 2.0.6 requires above given jar should be placed in a
>> different way altogether i.e,
>>
>> es-core-->4.0.8 --> es-asynchronous-4.0.8
>>
>> Due to unavailability of access for changing the folder structure @
>> remote ,
>> i need to change the way how the maven works.
>> Could you please help me in solving this problem ??
>>
>> --
>> View this message in context:
>> 
http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10716821
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

--
View this message in context: 
http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10731466
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]

Maven remote repository - AsyncWeb

[jing hez]

Hi

I looked at maven2/org/safehaus  and I don't see AsyncWeb in Maven
remote repository.

--

Hez

AsyncWeb
http://docs.safehaus.org/display/ASYNCWEB/Home

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

Re: How to create site with just jar files?

[Dennis Cook]

Okay, so adding the  element to the POM helped get past 
the error message, but the result was did not provide what I was looking for.  
I got a staging directory containing some template html files.  Neither the 
application library nor any of the supporting libraries were present.
   
  How do I get all of the libraries that make up the application into one 
location?

Dennis Cook <[EMAIL PROTECTED]> wrote:
  I am new to maven2 and trying to convert a project that is using a makefile 
to maven2. This is a simple java application, one main jar with 3 dependent 
libraries. I have gotten the build process to work up to the install goal. But 
I need to progress to the point that the application jar and its supporting 
libraries are delivered to another directory on the local (and eventually 
remote) host.
>From the information I can find in the doc I think the site:stage goal is the 
>one I need, but I hit an error from in this goal that I do not understand:
>From the command mvn site:stage
The error:
[INFO] Error during site generation
Embedded error: C:\development\nethaggler\relay-mail\target\staging\Unnamed - 
relay-mailer:relay-mailer:jar:0.0.1\integration.html (The filename, directory 
name, or volume label syntax is incorrect) 
My project has has no html files so why is it looking for this integration.html 
file?

How to create site with just jar files?

[Dennis Cook]

I am new to maven2 and trying to convert a project that is using a makefile to 
maven2.  This is a simple java application, one main jar with 3 dependent 
libraries.  I have gotten the build process to work up to the install goal. But 
I need to progress to the point that the application jar and its supporting 
libraries are delivered to another directory on the local (and eventually 
remote) host.
  From the information I can find in the doc I think the site:stage goal is the 
one I need, but I hit an error from in this goal that I do not understand:
  From the command mvn site:stage
  The error:
  [INFO] Error during site generation
  Embedded error: C:\development\nethaggler\relay-mail\target\staging\Unnamed - 
relay-mailer:relay-mailer:jar:0.0.1\integration.html (The filename, directory 
name, or volume label syntax is incorrect) 
  My project has has no html files so why is it looking for this 
integration.html file?

Re: how to change the dependency reading order in maven 2.0.6

[Kiran Kodlady]

Hey wayne..

U r right...
I am using layout structure similiar to maven1..


Wayne Fay wrote:
> 
> It sounds like you are dealing with a Maven1 repository layout.
> 
> Is that correct? Or is this a layout which just happens to be similar
> to Maven1, but has some small differences etc?
> 
> Wayne
> 
> On 5/21/07, Kiran Kodlady <[EMAIL PROTECTED]> wrote:
>>
>> hello...all,
>>
>> I got some interesting question here..
>>
>> At our project specific remote repository , below mentioned structure has
>> been followed for  storing a particular jar :
>>
>> es-core-->jars-->es-asynchronous-4.0.8
>>
>> But latest maven 2.0.6 requires above given jar should be placed in a
>> different way altogether i.e,
>>
>> es-core-->4.0.8 --> es-asynchronous-4.0.8
>>
>> Due to unavailability of access for changing the folder structure @
>> remote ,
>> i need to change the way how the maven works.
>> Could you please help me in solving this problem ??
>>
>> --
>> View this message in context:
>> http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10716821
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10731466
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: A trivial question

[Wayne Fay]

Are you using Maven1 or Maven2? As for your "problem downloading
files" -- are you behind a web proxy? If so, you will need to
configure it before the automatic downloading of files will be
successful.

Wayne

On 5/21/07, Hernani Cerqueira <[EMAIL PROTECTED]> wrote:

Hello all,

I use maven for a while, but I always had a problem with downloading files
from ibiblio, so, every time i need a file, i download it manualy and put it
on my local repository. I had a quite big repository, until the unexpected
happened. My hard disk failed and i lost all that work... Now I don't want to
download all those files again, and i want to set up a diferent repository. I
googled for a while, and i found out that i have to set the
maven.repo.remote, but i have no clue where... Wath should i edit?

-
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: Build error with weblogic-maven-plugin

[Murugan, Vellaichamy]

Hi,
I have used this version 2.9.0-20061221.203929-8 of 
weblogic-maven-plugin it is working perfectly. 
Regard's
Murugan

-Original Message-
From: Ole-Martin Mørk [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 21, 2007 2:37 PM
To: Maven Users List
Subject: Re: Build error with weblogic-maven-plugin

Hi Scott.

Have you seen any progress on this issue?

If I run the command manually, outside of maven, it works ok. I run it like
this:
java -Xmx1024m -classpath
c:\bea92\weblogic92\server\lib\weblogic.jar;c:\bea92\jdk150_04\lib\tools.jar
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
weblogic.appc
target/myArtifact-version.war -verbose -classpath 

The classpath argument is exactly the one that is used in the
weblogic-plugin.

I tried to rewrite your plugin to run the appc.main method like above, but I
still get the NoClassDefError on the XmlException class. I guess that the
problem is that the classpath in which the plugin is running crashes with
the classpath needed by appc. Is there any way to fork the appc process?

2007/4/13, Doug Tanner <[EMAIL PROTECTED]>:
>
> Answer, you may need more dependencies than me...:
>
> 
> org.codehaus.mojo
> weblogic-maven-plugin
> 2.9.0-SNAPSHOT
> 
>
> ${basedir}/../../jar/broker.war
> true
> 
> 
> 
> package
> 
> appc
> 
> 
> 
> 
> 
>
> weblogic
>
> xbean
> 9.2.0
> 
> 
>
> weblogic
>
> wlxbean
> 9.2
> 
> 
>
> weblogic
>
> weblogic-container-binding
> 9.2
> 
> 
>
> com.sun
>
> tools
> 1.5.0
> 
> 
> 
>
> Doug Tanner
>
>
> > -Original Message-
> > From: Doug Tanner [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 13, 2007 7:09 AM
> > To: Maven Users List
> > Subject: RE: Build error with weblogic-maven-plugin
> >
> > I found this issue,
> >
> http://jira.codehaus.org/browse/MOJO-585?page=com.atlassian.jira.plugin.
> > system.issuetabpanels:all-tabpanel, while researching my problem.  I
> > have tried placing a dependency on the ${WL_HOME}/server/lib/xbean.jar
> > in my pom, scoped as both system and provided (yes it is in my local
> > repo), but I am still receiving the same error.  I even see it in my
> > output classpath during compilation, so how can it still be throwing a
> > NoClassDefFoundError?  Has anyone had success implementing the
> > weblogic-maven-plugin, specifically version 2.9.0-SNAPSHOT?
> >
> > Thanks,
> >
> > Doug Tanner
> >
> >
> > > -Original Message-
> > > From: Scott Ryan [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ryan
> > > Sent: Thursday, April 12, 2007 10:03 AM
> > > To: Maven Users List
> > > Subject: Re: Build error with weblogic-maven-plugin
> > >
> > > Yes that is a bug I am working on.  I have some free days over then
> > > next week or so and hope to have a solution.  There are many jars
> > > that need to be included in the APPC and I am trying to find a good
> > > way to include them all without forcing you to load all the jars to
> > > your repository.   I am also testing with 10 as well.  I hope to
> have
> > > some good news later this week.  Let me know if there is anything
> > > else you need.
> > >
> > > Scott
> > > On Apr 12, 2007, at 7:36 AM, Doug Tanner wrote:
> > >
> > > > I am using the 2.9.0-SNAPSHOT.  After building my war, I wish to
> > > > precompile all my JSPs for faster response times.  As I understand
> > it,
> > > > the weblogic-maven-plugin goal weblogic:appc is what I need to use
> > > > to do
> > > > this.  However, I am getting a no class def found error.  From the
> > > > output of my build I get the following lines, edited to remove
> > > > non-essential information:
> > > >
> > > >
> > > >
> > > > [INFO] Weblogic APPC processing beginning for artifact
> > > > c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
> > > >
> > > > [INFO]  Detailed Appc settings information AppcMojo[
> > > >
> > > >  basicClientJar = false
> > > >
> > > >  forceGeneration = true
> > > >
> > > >  keepGenerated = true
> > > >
> > > >  lineNumbers = false
> > > >
> > > >  inputArtifactPath =
> > > > c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
> > > >
> > > >  outputArtifactPath = null
> > > >
> > > >  artifacts = [

A trivial question

[Hernani Cerqueira]

Hello all,

I use maven for a while, but I always had a problem with downloading files 
from ibiblio, so, every time i need a file, i download it manualy and put it 
on my local repository. I had a quite big repository, until the unexpected 
happened. My hard disk failed and i lost all that work... Now I don't want to 
download all those files again, and i want to set up a diferent repository. I 
googled for a while, and i found out that i have to set the 
maven.repo.remote, but i have no clue where... Wath should i edit?

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

Re: CVS parameters

[Wayne Fay]

I'm not clear -- is this response not sufficient and you're asking for
more help, or do you have things working?

If you still need help, I'd suggest looking at example pom.xml files
for some open source projects to see how they have configured their
SCM. Here's a few links:
http://svn.plexus.codehaus.org/browse/plexus/trunk/pom.xml?r=1500
http://vmgump.apache.org/gump/public/jline/jline/gump_file/pom.xml.html
http://fisheye1.cenqua.com/browse/wsmo4j/ext/pom.xml?r=1.4

If you're having specific problems, tell us what you've done, what
specifically isn't working, what error messages you're receiving, etc.

Wayne

On 5/21/07, Jon Strayer <[EMAIL PROTECTED]> wrote:

On 5/21/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> This is pretty well-documented on the website:
> http://maven.apache.org/scm/cvs.html


I assume that's true if you already know the answer.  Trust me when I tell
you that after spending hours reading the site and searching through mailing
list archives it's not clear to me.


Wayne
>
> On 5/21/07, Jon Strayer <[EMAIL PROTECTED]> wrote:
> > I'm getting this error when I try to update my project:
> > [ERROR] No CVS root is set. Check your  information in the
> POM.
> >
> > Where in the POM do I set the CVS Root?
> > How can I specify the user id and password outside of the POM?
> >
> > --
> > Esse Quam Videre
> > To Be, rather than to Seem
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Esse Quam Videre
To Be, rather than to Seem



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

Re: CVS parameters

[Jon Strayer]

On 5/21/07, Wayne Fay <[EMAIL PROTECTED]> wrote:


This is pretty well-documented on the website:
http://maven.apache.org/scm/cvs.html



I assume that's true if you already know the answer.  Trust me when I tell
you that after spending hours reading the site and searching through mailing
list archives it's not clear to me.


Wayne


On 5/21/07, Jon Strayer <[EMAIL PROTECTED]> wrote:
> I'm getting this error when I try to update my project:
> [ERROR] No CVS root is set. Check your  information in the
POM.
>
> Where in the POM do I set the CVS Root?
> How can I specify the user id and password outside of the POM?
>
> --
> Esse Quam Videre
> To Be, rather than to Seem
>

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





--
Esse Quam Videre
To Be, rather than to Seem

Re: Fw: Assistance required - why doesn't my index.html get generated when generating my site?

[Ian Rowlands]

"I have been told that an index.html should be generated, and it is not."

I know how to generate it with a site.xml, but it should be necessary.


Regards,

Ian Rowlands






Ian Rowlands <[EMAIL PROTECTED]> writes:

Hello Ian,
>
> Any suggestions? Is there any other information that I can provide which
> would help diagnosis?
>

Did you try adding a site.xml descriptor inside the src/site
directory ? I think this is mandatory for multi-modules projects
(FIXME).

Here is some very simple example:

In the parent:



 
  
  
 


In the modules:



 
  
  
 


Of course, you could add a custom index.xxx file, for example
src/site/apt/index.apt or src/site/xdoc/index.xdoc.

HTH
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com





Disclaimer: The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material
from your computer.
Privacy: If you are responding to this email or providing personal
information to the SRO for the purposes of one of the Acts it administers,
such information is used only for the purpose for which it was collected
( administration of SRO legislation ) and is protected by the Information
Privacy Act 2000 and secrecy provisions contained in legislation
administered by SRO. It is not disclosed otherwise than in accordance with
the law. If you would like a copy of the SRO Privacy Policy please refer to
SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a
copy.


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

Re: using emma on maven 2

[romale]

I created a new Maven2 plugin for EMMA.

You can download my current work here:
http://jira.codehaus.org/browse/MOJO-762

I advise a lot of people to try this plugin and give me feedback. I hope to
create an official EMMA plugin backed by the Mojo Project.

Tell me what you think about it!

Alexandre.


Lakthinda Ranasinghe wrote:
> 
> Hi all
> 
> I would like to know how to use emma on maven 2. I found
> "maven-emma-plugin-0.5.jar" file in the following path.
> http://repo1.maven.org/maven2/emma/maven-emma-plugin/0.5/.
> 
> I tried to change the maven config file "setting.xml" and the "pom.xml"
> file in my project folder as below in order to use emma plugin.
> 
> ---setting.xml---
> 
>   emma
>   Emma Plugin Repository
>   
> http://repo1.maven.org 
>   maven2.emma
>   maven-emma-plugin
>   0.5
> 
> 
> 
> But I got the following error message:
> 
> 
> .
> Downloading:
> http://repo1.maven.org/maven2/emma/maven-emma-plugin/0.5/maven-emma-plug
> in-0.5.pom
> .
> .
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
> 
> 
> Project ID: maven2.emma:maven-emma-plugin
> 
> Reason: POM 'maven2.emma:maven-emma-plugin' not found in repository:
> Unable to d
> ownload the artifact from any repository
> 
>   maven2.emma:maven-emma-plugin:pom:0.5
> 
> from the specified remote repositories:
>   emma (http://repo1.maven.org)
>   .
> 
> ThanX in advance.
> 
> Lakthinda
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/using-emma-on-maven-2-tf3762890s177.html#a10728646
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: Why doesn't my index.html get generated when generating my site?

[Mac Systems]

Hello,

out of a sudden i ran into the same Issue tonight.
As i my last changes to my pom where not that big i think i found the
problem:

In my POM i have :


...
  
 org.apache.maven.plugin
 maven-project-info-reports-plugin

 ...there i had listed which reports should be listed.

...

If i remove the org.apache.maven.plugin completely from 
my POM i get again an index.html.

The issue was also happening for my subprojects.

I using maven 2.0.6

Hope this Helps,
Jens



I have been told that an index.html should be generated, and it is not.
This is an issue because it is a multi-module project, and links on the
"parent" project all link to the index.html of the sub-projects.  So
without the index.html nobody can navigate the site correctly.

Any reason why the index.html is not being generated?

Thanks,

Ian



Eric Redmond
Fri, 27 Apr 2007 23:46:50 -0700

I don't understand your problem - it looks like it is working... you
haven't
added any files and the default reports are generating. And?

Eric

On 4/27/07, Ian Rowlands <[EMAIL PROTECTED]> wrote:


I'm using Maven 2.0.5.  My sites have no customisation (which I
won't do
until I get this to work).  I am getting the following
generated:
Apart from subdirectories, I get:
checkstyle.html (plus checkstyle.rss)
cpd.html and cpd.xml
dependencies.html
integration.html
issue-tracking.html
jdepend-report.html
pmd.html and pmd.xml
project-info.html
project-reports.html
surefire-report.html

I'm using version 2.0-beta-5 of the web site plugin.

Any suggestions on how to get this to work?

Thanks,

Ian





--
Eric Redmond
http://www.sonatype.com


  



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

Re: Using Maven to build a release distribution

[Alexander Sack]

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

-aps

On 5/21/07, Bryant Harris <[EMAIL PROTECTED]> wrote:


Hi,
  I'm new to Maven and have begun experimenting with breaking my project
into jars and WARs and EJBs etc.  It seems like Maven is great for this.

  Is Maven also typically used for assembling a distribution, which
might include jars, javadocs, source jars, licensing, samples, etc.  Or
would this be something you'd still use ant for?  Apologies if this is a
well-worn question that I just haven't found the answer for yet.

Bryant

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





--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson

Re: CVS parameters

[Wayne Fay]

You may also find some info on this page useful:
http://docs.codehaus.org/display/MAVENUSER/Continuous+Integration

Specifically, the sections ".cvspass file creation" and "Configure
settings.xml file".

Wayne

On 5/21/07, Wayne Fay <[EMAIL PROTECTED]> wrote:

This is pretty well-documented on the website:
http://maven.apache.org/scm/cvs.html

Wayne

On 5/21/07, Jon Strayer <[EMAIL PROTECTED]> wrote:
> I'm getting this error when I try to update my project:
> [ERROR] No CVS root is set. Check your  information in the POM.
>
> Where in the POM do I set the CVS Root?
> How can I specify the user id and password outside of the POM?
>
> --
> Esse Quam Videre
> To Be, rather than to Seem
>



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

Using Maven to build a release distribution

[Bryant Harris]

Hi,
 I'm new to Maven and have begun experimenting with breaking my project 
into jars and WARs and EJBs etc.  It seems like Maven is great for this.


 Is Maven also typically used for assembling a distribution, which 
might include jars, javadocs, source jars, licensing, samples, etc.  Or 
would this be something you'd still use ant for?  Apologies if this is a 
well-worn question that I just haven't found the answer for yet.


Bryant

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

Re: CVS parameters

[Wayne Fay]

This is pretty well-documented on the website:
http://maven.apache.org/scm/cvs.html

Wayne

On 5/21/07, Jon Strayer <[EMAIL PROTECTED]> wrote:

I'm getting this error when I try to update my project:
[ERROR] No CVS root is set. Check your  information in the POM.

Where in the POM do I set the CVS Root?
How can I specify the user id and password outside of the POM?

--
Esse Quam Videre
To Be, rather than to Seem



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

CVS parameters

[Jon Strayer]

I'm getting this error when I try to update my project:
[ERROR] No CVS root is set. Check your  information in the POM.

Where in the POM do I set the CVS Root?
How can I specify the user id and password outside of the POM?

--
Esse Quam Videre
To Be, rather than to Seem

RE: Issue with dependency plugin, unpack goal

[Brian E. Fox]

In some cases, Maven will look in the reactor projects and find
artifacts that haven't been installed. In my opinion, it shouldn't do
this. Things should have to be located in the local repo to be shared
amongst projects. The dependency plugin specifically does not look in
the reactors (at least for copy/unpack) but someone recently wrote an
issue for this. 

-Original Message-
From: Varghese C V [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 21, 2007 8:26 AM
To: Maven Users List
Subject: Re: Issue with dependency plugin, unpack goal

Thank you, Maria for your reply.

I was just trying various variations of the dependency.
First I tried putting the version in the dependency-plugin configuration
and no dependency elements defined.
That didnt work. Specifying my-app:1.0-SNAPSHOT in dependency &
dependencyManagement elements did not work either.

I have noticed that it works when I do the 'mvn install'. It does not
work with I try with 'mvn package'. dependencies before the
dependency-plugin can find it.

Here is another issue report that seems to suggest the same. 
http://jira.codehaus.org/browse/MNG-740.

Lesson learnt : Only install and above life cycle phases works in
multi-module maven builds if you have inter-project dependencies.
I am not sure why though. Reactor artifacts are not 'seen' by other
artifacts during a multi-module package. Install works cause the
artifacts are now in the local repository.

What do you think?

regards
Varghese



Maria Odea Ching wrote:
> Hi,
>
> I think what you have here is just a configuration problem.
>
> The  that you have in your my-dep-app module 
> should be on the parent pom, not in the my-dep-app pom.
> That's why the dependency's version here --> [INFO] Configured
> Artifact: com.mycomp.app:my-app:?:jar cannot be resolved, no version 
> can be found on the parent pom when it looked there.
>
> -Deng
>
> Varghese C V wrote:
>> (Sorry, my earlier mail had a Re: in the subject by mistake, hence 
>> 'am reposting the issue with the correct subject title.)
>>
>> I have a parent project which has two modules 'my-app' and 
>> 'my-dep-app' (both created by the archetype-create example). The 
>> 'my-dep-app' project wants the 'my-app' dependency to be unpacked 
>> into its target\classes folder. I am trying to merge the classes of 
>> multiple model projects before I can run the jibx xml binding 
>> compiler on them.
>>
>> This way I need only one jibx binding factory for a group of related 
>> models. The error 'Failed to resolve artifact' and the fact that it 
>> works when installed in the local repository suggests that reactor 
>> artifacts are not checked to resolve the dependency. Is this a 
>> multi-module problem?
>>
>> I would like to point out that looks very similar to a resolved 
>> dependency plugin issue (http://jira.codehaus.org/browse/MDEP-44),
>> except that I dont use the assembly plugin as shown in the test case.
>>
>> Any help is appreciated.
>>
>> Maven : 2.0.6
>> Maven dependency plugin : 2.0 alpha 4
>>
>> This is the output I get. PFA the poms(Zip attachments are getting
>> rejected)
>>
>> *
>> 
>>
>>
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO]   my-app
>> [INFO]   my-dep-app
>> [INFO]   My-apps parent pom
>>
>> [INFO]
>> -
>> ---
>>
>>
>> [INFO] Building my-app
>> [INFO]task-segment: [package]
>>
>> [INFO]
>> -
>> ---
>>
>>
>> ...
>> [INFO] [jar:jar]
>>
>> [INFO] Building jar: 
>> C:\test\mvn\dependency-unpack-test\my-app\target\my-app-1.0-SNAPSHOT.
>> jar
>> [INFO]
>> -
>> ---
>>
>>
>> [INFO] Building my-dep-app
>> [INFO]task-segment: [package]
>>
>> [INFO]
>> -
>> ---
>>
>>
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [dependency:unpack {execution: default}] [INFO] Configured 
>> Artifact: com.mycomp.app:my-app:?:jar
>>
>> [INFO]
>> -
>> ---
>>
>> [ERROR] BUILD ERROR
>>
>> [INFO]
>> -
>> ---
>>
>> [INFO] Failed to resolve artifact.
>>
>> GroupId: com.mycomp.app
>> ArtifactId: my-app
>> Version: 1.0-SNAPSHOT
>>
>> Reason: Unable to download the artifact from any repository
>>
>> Try downloading the file manually from the project website.
>>
>> Then, install it using the command:
>>  mvn install:install-file -DgroupId=com.mycomp.app
-DartifactId=my-app \
>>  -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>>
>>
>> com.mycomp.app:my-app:jar:1.0-SNAPSHOT
>>
>> from the specified remote repositories:
>> central (http://repo1.maven.org/mave

Re: [REPOST] "Can't canonicalize system path" with goal eclipse:eclipse

[Wayne Fay]

If you are reasonably convinced its a bug, please go file a bug in
JIRA against the proper component (in this case, the eclipse plugin).

And if you want it fixed (quickly), I'd suggest you pull the plugin
code down, adjust as needed, and contribute it back to be included in
a future release of this plugin.

Wayne

On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:

Wayne,
So far removing ${basedir} works with the following goals
   clean, eclipse:eclipse, package, and war:inplace.

As to "Why do you need it?". Consistency with other path references in
the pom.


If, as it appears, the war plugin uses different rules related to the
prefixing a path with ${basedir}, then I consider it a bug. (just my $0.02)

Paul Spencer


Wayne Fay wrote:
> Remove the ${basedir} from the ?
>
> Why do you need it?
>
> Wayne
>
> On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
>> I get a "Can't canonicalize system path" error using the goal
>> eclispse:eclipse when
>> the  of the maven-war-plugin starts with ${basedir}.
>> If I remove the
>> ${basedir}, the build is successful.
>>
>>
>> maven-eclipse-plugin verion 2.3
>> maven-war-plugin verion 2.0.2
>>
>>
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Can't canonicalize system path:
>> C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>>
>> Embedded error: The filename, directory name, or volume label syntax is
>> incorrect
>> [INFO]
>> 
>> [DEBUG] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Can't
>> canonicalize system path:
>> C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> 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: Can't
>> canonicalize system path:
>> C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>> at
>> org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:77)
>> at
>> 
org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:89)
>>
>> at
>> 
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:142)
>>
>> at
>> 
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:97)
>>
>> at
>> 
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:671)
>>
>> at
>> 
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:402)
>>
>> at
>> 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>>
>> at
>> 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>>
>> ... 16 more
>> Caused by: java.io.IOException: The filename, directory name, or volume
>> label syntax is incorrect
>> at java.io.WinNTFileSystem.canonicalize0(Native Method)
>> at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
>> at java.io.File.getCanonicalPath(File.java:513)
>> at
>> org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:73)
>> ... 23 more
>> [INFO]
>> ---

Re: [REPOST] "Can't canonicalize system path" with goal eclipse:eclipse

[Paul Spencer]

Wayne,
So far removing ${basedir} works with the following goals
   clean, eclipse:eclipse, package, and war:inplace.

As to "Why do you need it?". Consistency with other path references in 
the pom.



If, as it appears, the war plugin uses different rules related to the 
prefixing a path with ${basedir}, then I consider it a bug. (just my $0.02)


Paul Spencer


Wayne Fay wrote:

Remove the ${basedir} from the ?

Why do you need it?

Wayne

On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:

I get a "Can't canonicalize system path" error using the goal
eclispse:eclipse when
the  of the maven-war-plugin starts with ${basedir}.
If I remove the
${basedir}, the build is successful.


maven-eclipse-plugin verion 2.3
maven-war-plugin verion 2.0.2


[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Can't canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp

Embedded error: The filename, directory name, or volume label syntax is
incorrect
[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can't
canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) 


at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 


at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:324)
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: Can't
canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:77)
at
org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:89) 


at
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:142) 


at
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:97) 


at
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:671) 


at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:402) 


at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) 


... 16 more
Caused by: java.io.IOException: The filename, directory name, or volume
label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
at java.io.File.getCanonicalPath(File.java:513)
at
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:73)
... 23 more
[INFO]


Paul Spencer

-
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: [REPOST] "Can't canonicalize system path" with goal eclipse:eclipse

[Wayne Fay]

Remove the ${basedir} from the ?

Why do you need it?

Wayne

On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:

I get a "Can't canonicalize system path" error using the goal
eclispse:eclipse when
the  of the maven-war-plugin starts with ${basedir}.
If I remove the
${basedir}, the build is successful.


maven-eclipse-plugin verion 2.3
maven-war-plugin verion 2.0.2


[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Can't canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp

Embedded error: The filename, directory name, or volume label syntax is
incorrect
[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can't
canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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: Can't
canonicalize system path:
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:77)
at
org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:89)
at
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:142)
at
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:97)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:671)
at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:402)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: java.io.IOException: The filename, directory name, or volume
label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
at java.io.File.getCanonicalPath(File.java:513)
at
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:73)
... 23 more
[INFO]


Paul Spencer

-
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: Add and Label Artifact in SCM after Release:Perform

[Steven Rowe]

Hi Neil,

My approach for a similar issue was to create a plugin with the
necessary functionality, then add the goal to the configuration for
maven-release-plugin in my POM, e.g.:


  maven-release-plugin
  
deploy site-deploy myplugin:mygoal


Since I didn't know how to get the release tag directly from the release
plugin, I had my new plugin read in the release.properties file that
release:prepare generates.

Steve

Hall, Neil (CBC) wrote:
> We are in the process of converting our build lifecycle from using ANT to 
> Maven and are using Subversion as a SCM repository.  Our desire is to version 
> in SCM the project source and Pom.xml.  However, not the "Target" directory.  
> This is already working by using the release:prepare and release:perform 
> goals.  We are able to perform a complete build, label the source in SCM and 
> move our artifacts to our Proximity repository.  
> 
> Our problem:
> However, after the release:perform, we desire to add the project artifact 
> (ProjectName.war) in our Subversion repository (without the version number), 
> tag the artifact, and copy the artifact to a specific directory (Tomcat 
> webapps).  Can anyone provide assistance how to perform this task?  Lastly, 
> if a new goal is necessary, any recommendation how to bind this new goal to 
> the lifecycle to run after the release:perform?  
> 
> Any assistance is appreciated.  Thanks in advance...
> 
> Regards,
> Neil Hall
> 
> Confidentiality Notice:
> 
> This e-mail is intended only for the personal and confidential use of the 
> individual to whom it is addressed and may contain information that is 
> privileged, confidential and protected by law. If you are not the intended 
> recipient, you are hereby notified that any use or disclosure of this 
> information is strictly prohibited. If you have received this message in 
> error, please notify the sender immediately by reply e-mail and delete the 
> original message. Your compliance is appreciated.  


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

M2: Portability and

[Chris Helck]

Hi,

I'm having problems with portability and I can't seem to solve it
without replicating a lot of details in every pom I have. 

I have three environments I build from:
Development:Uses ibiblio, and internal development repo.
Creates web sites on internal machine. All developers use this.
Production: Uses protected internal production repo. Does
not create web site. Runs on specific machine on a isolated network.
Staged: An emulation of the Production environment
available to development. Used to test builds before handover.

I've created three profiles, but I don't know how to handle the
 section. It can't go into settings.xml
nor profiles.xml. If I put it into a parent pom it does not show up when
I run "mvn help:effective-pom". The only solution is to put it into
every single pom on my system. This seems wrong.

I took a look at how other projects (JXR Doxia) handle this. They put
 in the parent POM, but in the  section,
not the  section. This doesn't work for me, I can't have
development and production builds getting mixed up.

Can anyone help or shed some light on this?

Thanks,
Christopher Helck


 

**
This communication and all information (including, but not limited to,
 market prices/levels and data) contained therein (the "Information") is
 for informational purposes only, is confidential, may be legally
 privileged and is the intellectual property of ICAP plc and its affiliates
 ("ICAP") or third parties. No confidentiality or privilege is waived or
 lost by any mistransmission. The Information is not, and should not
 be construed as, an offer, bid or solicitation in relation to any
 financial instrument or as an official confirmation of any transaction.
 The Information is not warranted, including, but not limited, as to
 completeness, timeliness or accuracy and is subject to change
 without notice. ICAP assumes no liability for use or misuse of the
 Information. All representations and warranties are expressly
 disclaimed. The Information does not necessarily reflect the views of
 ICAP. Access to the Information by anyone else other than the
 recipient is unauthorized and any disclosure, copying, distribution or
 any action taken or omitted to be taken in reliance on it is prohibited. If
 you receive this message in error, please immediately delete it and all
 copies of it from your system, destroy any hard copies of it and
 notify the sender.
**

access plugin groupId/artifactId/version from within plugin

[ertnutler]

I have a plugin that does some generation, but I want to be able to print the
groupId/artifactId/version of the plugin to the file that gets generated.  I
don't see anything in the docs that addresses this, and when I step through
my plugin in eclipse, the pluginContext Map is empty.

How do I get access to this information from a plugin at runtime?
-- 
View this message in context: 
http://www.nabble.com/access-plugin-groupId-artifactId-version-from-within-plugin-tf3791561s177.html#a10722807
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: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?

[Emmanuel Venisse]

You must readd all projects

Emmanuel

Shaun Barriball a écrit :

We're just trying the upgrade to 1.1 now from 1.0.3.
Is there an upgrade path for this which preserves the database or do we have
to re-install all projects from scratch? 1.1 isn't mentioned on
http://maven.apache.org/continuum/upgrade.html.

Regards,
Shaun. 


-Original Message-
From: Jeffery, Mark [mailto:[EMAIL PROTECTED] 
Sent: 21 May 2007 11:38

To: [EMAIL PROTECTED]
Subject: RE: Project build order for multiple Maven 2 projects -
Alphabetical by Project Name?

Yeah.I am battling with the same thing

http://jira.codehaus.org/browse/CONTINUUM-998


Should be fixed in 1.1-alpha-#

Jeff

-Original Message-
From: Shaun Barriball [mailto:[EMAIL PROTECTED]
Sent: 21 May 2007 11:41
To: [EMAIL PROTECTED]
Subject: Project build order for multiple Maven 2 projects - Alphabetical by
Project Name?

Hi all,
We've been using Continuum (1.0.3) successfully as part of our automated
build and deploy for 6 months or so.
We have one big issue which I'd appreciate input on.

We have a large software system with 15 or so separate Maven 2 projects
(assume for simplicity Project A, Project B and Project C) which each have
sub-modules. Assume the dependency tree is:
A -> depends on C -> depends on B (for example). These dependencies are
expressed using Maven 2 dependency hierarchy.

The "Build All" function on Continuum appears to ignore any Maven 2
dependency hierarchy and simply builds them in alphabetical order of the
Project Name. This therefore builds the above example out of order - often
resulting in build failures.

* Should continuum 'understand' the dependency tree? I've read some material
which implies this should potentially be the case
(http://jira.codehaus.org/browse/CONTINUUM-39).

* If not, is there a way to organise the build order for "Build All"
above
and beyond altering the project names with "1.", "2." etc (which is
obviously undesirable)?


All help appreciated.
Regards,
Shaun.


To read FirstRand Bank's Disclaimer for this email click on the following
address or copy into your Internet browser: 
https://www.fnb.co.za/disclaimer.html 


If you are unable to access the Disclaimer, send a blank e-mail to
[EMAIL PROTECTED] and we will send you a copy of the
Disclaimer.

Re: Integration tests in a separate moule

[Wendy Smoak]

On 5/21/07, Arnaud Jeansen <[EMAIL PROTECTED]> wrote:


My problem is that I can't make these integration tests compile in the
"test" phase of the "integtesttomcat" module. These tests depend on the
classes from foowar/src/main/java (to compile test classes looking like
web services clients, I need the classes defining my model). When I run
the mvn install, the tests will not compile because they will fail to
see the main classes (lots of "Symbol not found")

...

If anyone can take some time to pitch in some suggestions, I would be
very grateful


I'd move the java code out of the webapp into a separate module, and
have both the webapp and the integration tests module depend on it.

--
Wendy

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

Integration tests in a separate moule

[Arnaud Jeansen]

Hi,

I have been trying for two days to get a nice integration module, but I
have been mostly bumping my head into a thick wall.

My project is a simple EAR (no EJB), that I organized as shown in the
"Better Builds" PDF :


Structure :

foo
foowar/
src/
main/
test/
pom.xml
fooear/
pom.xml
deploytomcat/
pom.xml
integtesttomcat/
src/
it/
pom.xml
pom.xml


Modules :

Foowar : contains main code, webapp resources and unit tests. Build this
into a war file

Fooear : depends on foowar and wraps the war in a ear (just adding a
META-INF/application.xml)

Deploytomcat : takes the war and deploy it to a tomcat server using
cargo (pretty default 
configuration taken from the cargo tutorial)

Integtesttomcat : comes after deploytomcat in the parent pom "modules"
section, the goal is to run the "test" phase with my integration tests
(using integtesttomcat/src/it). These tests require that the application
is properly deployed, they will basically test the webservices.



My problem is that I can't make these integration tests compile in the
"test" phase of the "integtesttomcat" module. These tests depend on the
classes from foowar/src/main/java (to compile test classes looking like
web services clients, I need the classes defining my model). When I run
the mvn install, the tests will not compile because they will fail to
see the main classes (lots of "Symbol not found")

I have been trying to add the main classes to the test compile by :
- adding my war file as a dependency in the integtestomcat/pom.xml
- adding an outputDirectory in the build section of
integtestomcat/pom.xml (hoping the test compile would add this to the
classpath) : 

${basedir}/../foowar/src/target


I ran out of new ideas a few hours ago, and google, mailinglist archive
and "better builds" did not help me since.

If anyone can take some time to pitch in some suggestions, I would be
very grateful


Thank you all,
Arnaud Jeansen
Ce message et ses pièces jointes (le "message") est destiné à l'usage
exclusif de son destinataire.
Si vous recevez ce message par erreur, merci d'en aviser immédiatement
l'expéditeur  et de le détruire ensuite. Le présent message  pouvant
être altéré à notre insu,  CALYON Crédit Agricole CIB
ne peut pas être engagé par son contenu. Tous droits réservés.

This message and/or any  attachments (the "message") is intended for
the sole use of its addressee.
If you are not the addressee, please immediately notify the sender and
then destroy the message.  As this message and/or any attachments may
have been altered without our knowledge,  its content  is not legally
binding on CALYON Crédit Agricole CIB. All rights reserved.

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

Re: jaxb2-maven-plugin

[Steven Rowe]

Hi Vidya,

You will probably get a quicker response from the Mojo Project mailing
lists for questions about Mojo Project plugins:

   

Steve

Vidya Mahavadi wrote:
> Hi,
> 
> I am using jaxb2-maven-plugin and in the application I would like to 
> validate the xml. And for that I would like to include schema in the 
> artifact. 
> Is it possible to configure the plugin for that?
> 
> Regards,
> Vidya
> 
> This e-mail is subject to a disclaimer, available at
> http://www.rmb.co.za/web/elements.nsf/online/disclaimer-communications.html
> 
> 


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

RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?

[Shaun Barriball]

We're just trying the upgrade to 1.1 now from 1.0.3.
Is there an upgrade path for this which preserves the database or do we have
to re-install all projects from scratch? 1.1 isn't mentioned on
http://maven.apache.org/continuum/upgrade.html.

Regards,
Shaun. 

-Original Message-
From: Jeffery, Mark [mailto:[EMAIL PROTECTED] 
Sent: 21 May 2007 11:38
To: [EMAIL PROTECTED]
Subject: RE: Project build order for multiple Maven 2 projects -
Alphabetical by Project Name?

Yeah.I am battling with the same thing

http://jira.codehaus.org/browse/CONTINUUM-998


Should be fixed in 1.1-alpha-#

Jeff

-Original Message-
From: Shaun Barriball [mailto:[EMAIL PROTECTED]
Sent: 21 May 2007 11:41
To: [EMAIL PROTECTED]
Subject: Project build order for multiple Maven 2 projects - Alphabetical by
Project Name?

Hi all,
We've been using Continuum (1.0.3) successfully as part of our automated
build and deploy for 6 months or so.
We have one big issue which I'd appreciate input on.

We have a large software system with 15 or so separate Maven 2 projects
(assume for simplicity Project A, Project B and Project C) which each have
sub-modules. Assume the dependency tree is:
A -> depends on C -> depends on B (for example). These dependencies are
expressed using Maven 2 dependency hierarchy.

The "Build All" function on Continuum appears to ignore any Maven 2
dependency hierarchy and simply builds them in alphabetical order of the
Project Name. This therefore builds the above example out of order - often
resulting in build failures.

* Should continuum 'understand' the dependency tree? I've read some material
which implies this should potentially be the case
(http://jira.codehaus.org/browse/CONTINUUM-39).

* If not, is there a way to organise the build order for "Build All"
above
and beyond altering the project names with "1.", "2." etc (which is
obviously undesirable)?


All help appreciated.
Regards,
Shaun.


To read FirstRand Bank's Disclaimer for this email click on the following
address or copy into your Internet browser: 
https://www.fnb.co.za/disclaimer.html 

If you are unable to access the Disclaimer, send a blank e-mail to
[EMAIL PROTECTED] and we will send you a copy of the
Disclaimer.

AW: How configure to Multiproject Site references

[Jens Hohl]

Hello,

ist me (mac) from other mail Adress:

Actually I have some problems to get this really working.
I tried mvn site:run which results that the 'master' Website
Is available through localhost. But I have same problems
To reference to the sub-projects.
In my site.xml I link via relative path like this:




http://maven.apache.org/images/apache-maven-project.png
http://maven.apache.org/


http://maven.apache.org/images/maven-small.gif










--

The generated Site links like this to the Subprojekts:

   
  Project1


All result in a 404 Error.


Anyone can help me, may I need some complete other solution for that ?
Actually I think how to structure this to deploy on a Webserver ...


Regards,
Jens



-Ursprüngliche Nachricht-
Von: vgpande [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 21. Mai 2007 16:31
An: users@maven.apache.org
Betreff: Re: How configure to Multiproject Site references


Hi

when you run the "mvn site" for Maven2 at the application root level, the
command is executed to generate the site at application root level.



James Abley-2 wrote:
> 
> On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> actually i wonder how to generate an  Site for an Multiproject ?
>>
>> The (Master) Project Site will be generated for all my Modules but i do
>> not know
>> how to link to each module's site ?
>>
>>
>> Project:
>>
>> pom.xml
>> |
>> |
>>  >Module A
>> pom.xml
>> -> target/site/index.html
>>  >Module B
>> pom.xml
>> -> target/site/index.html
>>  >Module C
>> pom.xml
>> -> target/site/index.html
>>
>>
>> regards,
>> Jens Hohl
>>
> 
> I've used the  element in each module's pom.
> 
> ../../Module A/target/site/
> 
> It works fine for builds locally.
> 
> Cheers,
> 
> James
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-configure-to-Multiproject-Site-references-tf3787163s177.html#a10719982
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: Use of ${version} in published pom

[Wendy Smoak]

On 5/21/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:

The pom :
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/cargo/cargo-core-api-generic/0.9/cargo-core-api-generic-0.9.pom

Contains some ${version}.  I looked in the parent poms, but there is no
explicit property with this name.

Where does this value comes from?  Is it a standard property implicitely
defined?


${version} is the same as ${project.version} or ${pom.version}

I usually look here for info on properties:
  http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide

--
Wendy

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

Re: [m2] Problem extending a MOJO: incongruency in default @parameter value

[Steven Rowe]

Hi Alessio,

I'm a Maven newbie, and am only responding because no one else has...

I have seen a couple of messages to the effect that plugin extension is
not supported by the Maven architecture.

See this thread for a couple of workarounds:

  

Also, though this particular question is more about Maven than any one
plugin, it may be useful for you to ask questions about Mojo Project
plugins on the Codehaus Mojo Project mailing lists:

  

Steve

Alessio Pace wrote:
> Hi,
> 
> I'm trying to write a MOJO as an extension of the "exec-maven-plugin", the
> only purpose of it is to allow application specific parameter names in the
> pom, instead of the various  tags.
> 
> So, my project has the exec-maven-plugin as a , and subclasses
> one of the classes of the former
> plugin (specifically, the ExecJavaMojo class). Code compiles and builds but
> strangely, a default parameter value declared as such in the original MOJO:
> 
> /* @parameter expression="${exec.includeProjectDependencies}"
> default-value="true"
> */
> private boolean includeProjectDependencies;
> 
> has value *false* when it is evaluated in mysubclass!! No manipulations are
> made on that field by the super class, it's only read in order to do
> something or something else.
> 
> I can't really explain what happens, can someone give me a clue?
> 
> Thanks in advance,
> 


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

Re: How to install library into repository?

[jesseliu]

You should install(deploy) the jar file into your company repository which 
is shared with your team. 
maven deploy command line seems like:(assuming on Windows OS)
mvn deploy:deploy-file -DgroupId=com.toedter.calendar
 -DartifactId=jcalendar -Dversion=1.3.2 -Dpackaging=jar -
Dfile=c:\path\to\jar\jcalendar-1.3.2.jar" -Durl=\\192.168.1.10
\path\to\company\repository

In case your team member add the company repository to the maven config 
file, maven can automatically download the jcalendar-1.3.2.jar into local 
repository from company repository.




On Mon, 21 May 2007 16:30:26 +0200, Jansen Werner wrote
> Hi everybody,
> 
> we would like to use jcalendar (http://www.toedter.com/en/jcalendar/)
>  in our project. But it isn't available from the central repository.
> 
> Maven suggests adding it to the local repository:
> 
> "Then, install it using the command: 
> mvn install:install-file -DgroupId=com.toedter.calendar
> -DartifactId=jcalendar \
> -Dversion=1.3.2 -Dpackaging=jar -Dfile=jcalendar-1.3.2.jar"
> 
> But I don't want to install it in every developer's local repository.
> How can I add this library to our site-local repository in a maven way?
> 
> Regards,
> 
> Werner
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


--
Powered By Open WebMail Project (http://openwebmail.org)


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

Re: How to install library into repository?

[Wayne Fay]

This is well documented on the Maven site:
http://maven.apache.org/guides/mini/guide-deploying-3rd-party-jars.html

Wayne

On 5/21/07, Jansen Werner <[EMAIL PROTECTED]> wrote:

Hi everybody,

we would like to use jcalendar (http://www.toedter.com/en/jcalendar/) in
our project. But it isn't available from the central repository.

Maven suggests adding it to the local repository:

"Then, install it using the command:
mvn install:install-file -DgroupId=com.toedter.calendar
-DartifactId=jcalendar \
-Dversion=1.3.2 -Dpackaging=jar -Dfile=jcalendar-1.3.2.jar"


But I don't want to install it in every developer's local repository.
How can I add this library to our site-local repository in a maven way?

Regards,

Werner

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

Use of ${version} in published pom

[Gilles Scokart]

The pom :
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/cargo/cargo-core-api-generic/0.9/cargo-core-api-generic-0.9.pom

Contains some ${version}.  I looked in the parent poms, but there is no
explicit property with this name.

Where does this value comes from?  Is it a standard property implicitely
defined?  


Gilles Scokart
-- 
View this message in context: 
http://www.nabble.com/Use-of-%24%7Bversion%7D-in-published-pom-tf3790660s177.html#a10720048
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: how to use the same jar in the maven repository but in another java version?

[Jo Vandermeeren]

Hi,

If you are making multiple artifacts from one module, you should definitely
use classifiers for the build artifacts.
Otherwise, they get mixed up and you end up with garbage.

You can configure the maven-jar-plugin or the maven-assembly-plugin to add
classifiers to the artifacts when their profiles are active.

There's some decent material on the sonatype website that explains it:
http://www.sonatype.com/book/profiles.html#Classifiers

Cheers
Jo

On 5/21/07, emerson cargnin <[EMAIL PROTECTED]> wrote:


Hi all

I'm using maven 1.1.
I have two multi-build projects that depend on same jars. But one is
to be compiled in 1.4 and the other in 1.5.  The thing is that the 1.4
one  tries to dowload from the maven repository, as it has a newer
date (as it was run by cruisecontrol) and ends up having
incompatibility. Besides disabling cruisecontrol to upload the
generated files, how could I manage this sharing of jar in two
different versions?

thanks
emerson

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

Re: How configure to Multiproject Site references

[vgpande]

Hi

when you run the "mvn site" for Maven2 at the application root level, the
command is executed to generate the site at application root level.



James Abley-2 wrote:
> 
> On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> actually i wonder how to generate an  Site for an Multiproject ?
>>
>> The (Master) Project Site will be generated for all my Modules but i do
>> not know
>> how to link to each module's site ?
>>
>>
>> Project:
>>
>> pom.xml
>> |
>> |
>>  >Module A
>> pom.xml
>> -> target/site/index.html
>>  >Module B
>> pom.xml
>> -> target/site/index.html
>>  >Module C
>> pom.xml
>> -> target/site/index.html
>>
>>
>> regards,
>> Jens Hohl
>>
> 
> I've used the  element in each module's pom.
> 
> ../../Module A/target/site/
> 
> It works fine for builds locally.
> 
> Cheers,
> 
> James
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-configure-to-Multiproject-Site-references-tf3787163s177.html#a10719982
Sent from the Maven - Users mailing list archive at Nabble.com.


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

How to install library into repository?

[Jansen Werner]

Hi everybody,

we would like to use jcalendar (http://www.toedter.com/en/jcalendar/) in
our project. But it isn't available from the central repository. 

Maven suggests adding it to the local repository:

"Then, install it using the command: 
mvn install:install-file -DgroupId=com.toedter.calendar
-DartifactId=jcalendar \
-Dversion=1.3.2 -Dpackaging=jar -Dfile=jcalendar-1.3.2.jar"


But I don't want to install it in every developer's local repository.
How can I add this library to our site-local repository in a maven way?

Regards,

Werner

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

[REPOST] "Can't canonicalize system path" with goal eclipse:eclipse

[Paul Spencer]

I get a "Can't canonicalize system path" error using the goal 
eclispse:eclipse when
the  of the maven-war-plugin starts with ${basedir}. 
If I remove the

${basedir}, the build is successful.


maven-eclipse-plugin verion 2.3
maven-war-plugin verion 2.0.2


[INFO] 


[ERROR] BUILD ERROR
[INFO] 

[INFO] Can't canonicalize system path: 
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp


Embedded error: The filename, directory name, or volume label syntax is 
incorrect
[INFO] 


[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can't 
canonicalize system path: 
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)
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: Can't 
canonicalize system path: 
C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
at 
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:77)
at 
org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:89)
at 
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:142)
at 
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:97)
at 
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:671)
at 
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:402)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

... 16 more
Caused by: java.io.IOException: The filename, directory name, or volume 
label syntax is incorrect

at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
at java.io.File.getCanonicalPath(File.java:513)
at 
org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:73)

... 23 more
[INFO] 



Paul Spencer

-
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: pom as dependency

[Wayne Fay]

This should work. Check your dependency scopes.

How do you know "it isn't taking it"? What's the test which is failing?

Wayne

On 5/21/07, zalym <[EMAIL PROTECTED]> wrote:


hi,

i have 5 modules and a pom.  I want to use these 5 modules in my war.  i
want to include the pom as a dependency but it isn't taking it.  i have to
include the modules rather for it to work.

Appreciate any help.

--Saleem
--
View this message in context:
http://www.nabble.com/pom-as-dependency-tf3788997s177.html#a10715116
Sent from the Maven - Users mailing list archive at Nabble.com.


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




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

Re: how to change the dependency reading order in maven 2.0.6

[Wayne Fay]

It sounds like you are dealing with a Maven1 repository layout.

Is that correct? Or is this a layout which just happens to be similar
to Maven1, but has some small differences etc?

Wayne

On 5/21/07, Kiran Kodlady <[EMAIL PROTECTED]> wrote:


hello...all,

I got some interesting question here..

At our project specific remote repository , below mentioned structure has
been followed for  storing a particular jar :

es-core-->jars-->es-asynchronous-4.0.8

But latest maven 2.0.6 requires above given jar should be placed in a
different way altogether i.e,

es-core-->4.0.8 --> es-asynchronous-4.0.8

Due to unavailability of access for changing the folder structure @ remote ,
i need to change the way how the maven works.
Could you please help me in solving this problem ??

--
View this message in context:
http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10716821
Sent from the Maven - Users mailing list archive at Nabble.com.


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




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

how to use the same jar in the maven repository but in another java version?

[emerson cargnin]

Hi all

I'm using maven 1.1.
I have two multi-build projects that depend on same jars. But one is
to be compiled in 1.4 and the other in 1.5.  The thing is that the 1.4
one  tries to dowload from the maven repository, as it has a newer
date (as it was run by cruisecontrol) and ends up having
incompatibility. Besides disabling cruisecontrol to upload the
generated files, how could I manage this sharing of jar in two
different versions?

thanks
emerson

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

Surefire systemClassLoader option

[Grant Ingersoll]

I am having some trouble with class loading in tests.  For some tests  
in my set of tests, the only way the pass via M2 is if I set  
useSystemClassLoader to true per http://jira.codehaus.org/browse/ 
SUREFIRE-106.  On the other hand, some other subset of tests only  
pass if useSystemClassLoader is false.


One thing I see that is strange is, when useSystemClassLoader is  
true, my target/classes directory occurs before target/test-classes  
in the classpath, meaning the resources in src/main/resources are  
resolved before the ones in src/test/resources.


Has anyone else run into this or have suggestions on what to do?

Thanks,
Grant


--
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org/tech/lucene.asp

Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ 
LuceneFAQ




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

Re: Optional Runtime Dependencies

[Martin Jericho]

"Required for compilation" is compile which is the
default so you don't need to specify it.

"Optional at runtime" is true

That will force your users to declare this dependency in their own
projects if they want it.  This is how we handle the Cargo depdendency
in Shale Test, because there is one class that needs Cargo to compile,
but not everyone who uses Shale Test will want to use Cargo with it.

* http://svn.apache.org/repos/asf/shale/framework/trunk/shale-test/pom.xml


Just to make sure I have this right, you are now saying I should use 
"compile" scope with the optional flag, and not the "runtime" scope?


This is still completely non-intuitive, and the dependency tables are 
confusing enough even without adding the "optional" dimension.


Wouldn't it be much more intuitive to express it something like this:

...

or, since there seems to be a convention not to use attributes for some 
reason, like this:



   ...
   required
   optional


where the default values for both compile-time and runtime are "required" 


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

Enabling a profile disables an other

[gc134728]

Hey maven users,

When I enable a profile using mvn clean install -PbuildCon It disables an
other profile that has an activation active by default.


...

  true

...


Is this a bug in maven or correct?

Thx for any assitance,
Y. Van Steen
Agfa Connectivity Engineer
---
Scarlet ADSL20, 20 Mbits down, 1 Mbits up, 60 GB volume, http://www.scarlet.be/


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

Re: Optional Runtime Dependencies

[Wendy Smoak]

On 5/21/07, Martin Jericho <[EMAIL PROTECTED]> wrote:


So you are saying that to indicate that a dependency is required for
compilation and optional for runtime, I simply set it with the scope
"runtime" and and "optional" flag.

This seems to completely contradict the documentation, which says of the
runtime scope: "this scope indicates that the dependency is not required for
compilation, but is for execution".


And when you put it that way, I think so, too. :)  Let's start over.

"Required for compilation" is compile which is the
default so you don't need to specify it.

"Optional at runtime" is true

That will force your users to declare this dependency in their own
projects if they want it.  This is how we handle the Cargo depdendency
in Shale Test, because there is one class that needs Cargo to compile,
but not everyone who uses Shale Test will want to use Cargo with it.

* http://svn.apache.org/repos/asf/shale/framework/trunk/shale-test/pom.xml

Though at this point you may not believe anything I say!  By far the
easiest way to sort this  out is to construct an example and look at
the output of "mvn install -X' which is what I should have done before
answering that early on a weekend morning.


I will add the dependency as you have described, but it looks to me like the
whole maven scoping mechanism and/or documentation needs a complete overhaul
as it is a confusing mess at the moment.


I opened an issue to add some discussion of "optional" to the
dependency mechanism page.  In particular I think the table that tries
to explain when various dependencies will be available is confusing.

--
Wendy

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

Re: Issue with dependency plugin, unpack goal

[Varghese C V]

Thank you, Maria for your reply.

I was just trying various variations of the dependency.
First I tried putting the version in the dependency-plugin configuration 
and no dependency elements defined.
That didnt work. Specifying my-app:1.0-SNAPSHOT in dependency & 
dependencyManagement elements did not work either.


I have noticed that it works when I do the 'mvn install'. It does not 
work with I try with 'mvn package'. dependencies before the 
dependency-plugin can find it.


Here is another issue report that seems to suggest the same. 
http://jira.codehaus.org/browse/MNG-740.


Lesson learnt : Only install and above life cycle phases works in 
multi-module maven builds if you have inter-project dependencies.
I am not sure why though. Reactor artifacts are not 'seen' by other 
artifacts during a multi-module package. Install works cause the

artifacts are now in the local repository.

What do you think?

regards
Varghese



Maria Odea Ching wrote:

Hi,

I think what you have here is just a configuration problem.

The  that you have in your my-dep-app module 
should be on the parent pom, not in the my-dep-app pom.
That's why the dependency's version here --> [INFO] Configured 
Artifact: com.mycomp.app:my-app:?:jar cannot be resolved, no version 
can be found on the parent pom when it looked there.


-Deng

Varghese C V wrote:
(Sorry, my earlier mail had a Re: in the subject by mistake, hence 
'am reposting the issue with the correct subject title.)


I have a parent project which has two modules 'my-app' and 
'my-dep-app' (both created by the archetype-create example). The 
'my-dep-app' project wants the 'my-app' dependency to be unpacked 
into its target\classes folder. I am trying to merge the classes of 
multiple model projects before I can run the jibx xml binding 
compiler on them.


This way I need only one jibx binding factory for a group of related 
models. The error 'Failed to resolve artifact' and the fact that it 
works when installed in the local repository suggests that reactor 
artifacts are not checked to resolve the dependency. Is this a 
multi-module problem?


I would like to point out that looks very similar to a resolved 
dependency plugin issue (http://jira.codehaus.org/browse/MDEP-44), 
except that I dont use the assembly plugin as shown in the test case.


Any help is appreciated.

Maven : 2.0.6
Maven dependency plugin : 2.0 alpha 4

This is the output I get. PFA the poms(Zip attachments are getting 
rejected)


* 



[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   my-app
[INFO]   my-dep-app
[INFO]   My-apps parent pom

[INFO] 
 



[INFO] Building my-app
[INFO]task-segment: [package]

[INFO] 
 



...
[INFO] [jar:jar]

[INFO] Building jar: 
C:\test\mvn\dependency-unpack-test\my-app\target\my-app-1.0-SNAPSHOT.jar 
[INFO] 
 



[INFO] Building my-dep-app
[INFO]task-segment: [package]

[INFO] 
 



[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: com.mycomp.app:my-app:?:jar

[INFO] 



[ERROR] BUILD ERROR

[INFO] 



[INFO] Failed to resolve artifact.

GroupId: com.mycomp.app
ArtifactId: my-app
Version: 1.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
 mvn install:install-file -DgroupId=com.mycomp.app -DartifactId=my-app \
 -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file


com.mycomp.app:my-app:jar:1.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2)



[INFO] 



[INFO] For more information, run Maven with the -e switch

[INFO] 



[INFO] Total time: 4 seconds
[INFO] Finished at: Fri May 18 15:32:07 GST 2007
[INFO] Final Memory: 7M/13M

[INFO] 
 
* 





  com.zafinlabs.project.miRevenue.hdfc.impl
  4.0.0
  myApps
  1.0-SNAPSHOT
  pom
  My-apps parent pom
  
my-app
my-dep-app
  



http://maven.apache.org/POM

how to change the dependency reading order in maven 2.0.6

[Kiran Kodlady]

hello...all,

I got some interesting question here..

At our project specific remote repository , below mentioned structure has
been followed for  storing a particular jar :

es-core-->jars-->es-asynchronous-4.0.8

But latest maven 2.0.6 requires above given jar should be placed in a
different way altogether i.e,

es-core-->4.0.8 --> es-asynchronous-4.0.8

Due to unavailability of access for changing the folder structure @ remote ,
i need to change the way how the maven works. 
Could you please help me in solving this problem ?? 

-- 
View this message in context: 
http://www.nabble.com/how-to-change-the-dependency-reading-order-in-maven-2.0.6-tf3789581s177.html#a10716821
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: Optional Runtime Dependencies

[Martin Jericho]

Thanks for your response Wendy, but this still isn't clear to me at all.
Are you saying I have to add two dependency elements for each library, 
once

with a scope of compile, and once with a scope of runtime but with the
optional flag set?  Doesn't the compile scope imply runtime dependency as
well?


Yes.  Just runtime scope should do it for you, since it will also be
available for compilation.


So you are saying that to indicate that a dependency is required for 
compilation and optional for runtime, I simply set it with the scope 
"runtime" and and "optional" flag.


This seems to completely contradict the documentation, which says of the 
runtime scope: "this scope indicates that the dependency is not required for 
compilation, but is for execution".


I will add the dependency as you have described, but it looks to me like the 
whole maven scoping mechanism and/or documentation needs a complete overhaul 
as it is a confusing mess at the moment.



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

Re: Specify Context Path for WAR project in Maven2

[Geir Gullestad Pettersen]

Thanks, that did wonders!

2007/5/21, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:



Try the   MyWebAppName
in the POM.

/U

-- Original message --
From: geirgp <[EMAIL PROTECTED]>
>
> When I use the jboss plugin to deploy my war project to the app server
the
> context path is set to /{artifactId}-{version}/ which also happens if I
use
> the tomcat plugin to do the same thing. Is there a way to override and
> specify this context path instead of using the default?
> --
> View this message in context:
>
http://www.nabble.com/Specify-Context-Path-for-WAR-project-in-Maven2-tf3787384s1
> 77.html#a10710709
> 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: Issue with dependency plugin, unpack goal

[Maria Odea Ching]

Hi,

I think what you have here is just a configuration problem.

The  that you have in your my-dep-app module 
should be on the parent pom, not in the my-dep-app pom.
That's why the dependency's version here --> [INFO] Configured Artifact: 
com.mycomp.app:my-app:?:jar cannot be resolved, no version can be found 
on the parent pom when it looked there.


-Deng

Varghese C V wrote:
(Sorry, my earlier mail had a Re: in the subject by mistake, hence 'am 
reposting the issue with the correct subject title.)


I have a parent project which has two modules 'my-app' and 
'my-dep-app' (both created by the archetype-create example). The 
'my-dep-app' project wants the 'my-app' dependency to be unpacked into 
its target\classes folder. I am trying to merge the classes of 
multiple model projects before I can run the jibx xml binding compiler 
on them.


This way I need only one jibx binding factory for a group of related 
models. The error 'Failed to resolve artifact' and the fact that it 
works when installed in the local repository suggests that reactor 
artifacts are not checked to resolve the dependency. Is this a 
multi-module problem?


I would like to point out that looks very similar to a resolved 
dependency plugin issue (http://jira.codehaus.org/browse/MDEP-44), 
except that I dont use the assembly plugin as shown in the test case.


Any help is appreciated.

Maven : 2.0.6
Maven dependency plugin : 2.0 alpha 4

This is the output I get. PFA the poms(Zip attachments are getting 
rejected)


* 



[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   my-app
[INFO]   my-dep-app
[INFO]   My-apps parent pom

[INFO] 
 



[INFO] Building my-app
[INFO]task-segment: [package]

[INFO] 
 



...
[INFO] [jar:jar]

[INFO] Building jar: 
C:\test\mvn\dependency-unpack-test\my-app\target\my-app-1.0-SNAPSHOT.jar 
[INFO] 
 



[INFO] Building my-dep-app
[INFO]task-segment: [package]

[INFO] 
 



[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: com.mycomp.app:my-app:?:jar

[INFO] 



[ERROR] BUILD ERROR

[INFO] 



[INFO] Failed to resolve artifact.

GroupId: com.mycomp.app
ArtifactId: my-app
Version: 1.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
 mvn install:install-file -DgroupId=com.mycomp.app -DartifactId=my-app \
 -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file


com.mycomp.app:my-app:jar:1.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2)



[INFO] 



[INFO] For more information, run Maven with the -e switch

[INFO] 



[INFO] Total time: 4 seconds
[INFO] Finished at: Fri May 18 15:32:07 GST 2007
[INFO] Final Memory: 7M/13M

[INFO] 
 
* 





  com.zafinlabs.project.miRevenue.hdfc.impl
  4.0.0
  myApps
  1.0-SNAPSHOT
  pom
  My-apps parent pom
  
my-app
my-dep-app
  



http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  com.mycomp.app
  my-app
  jar
  1.0-SNAPSHOT
  my-app
  http://maven.apache.org
  

  junit
  junit
  3.8.1
  test

  

  



http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  com.mycomp.app
  my-dep-app
  jar
  1.0-SNAPSHOT
  my-dep-app
  http://maven.apache.org
  


  com.mycomp.app
  my-app
  ${project.version}


  
  

  junit
  junit
  3.8.1
  test


  com.mycomp.app
  my-app

  
  

Re: Build error with weblogic-maven-plugin

[Ole-Martin Mørk]

Hi Scott.

Have you seen any progress on this issue?

If I run the command manually, outside of maven, it works ok. I run it like
this:
java -Xmx1024m -classpath
c:\bea92\weblogic92\server\lib\weblogic.jar;c:\bea92\jdk150_04\lib\tools.jar
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
weblogic.appc
target/myArtifact-version.war -verbose -classpath 

The classpath argument is exactly the one that is used in the
weblogic-plugin.

I tried to rewrite your plugin to run the appc.main method like above, but I
still get the NoClassDefError on the XmlException class. I guess that the
problem is that the classpath in which the plugin is running crashes with
the classpath needed by appc. Is there any way to fork the appc process?

2007/4/13, Doug Tanner <[EMAIL PROTECTED]>:


Answer, you may need more dependencies than me...:


org.codehaus.mojo
weblogic-maven-plugin
2.9.0-SNAPSHOT


${basedir}/../../jar/broker.war
true



package

appc






weblogic

xbean
9.2.0



weblogic

wlxbean
9.2



weblogic

weblogic-container-binding
9.2



com.sun

tools
1.5.0




Doug Tanner


> -Original Message-
> From: Doug Tanner [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 13, 2007 7:09 AM
> To: Maven Users List
> Subject: RE: Build error with weblogic-maven-plugin
>
> I found this issue,
>
http://jira.codehaus.org/browse/MOJO-585?page=com.atlassian.jira.plugin.
> system.issuetabpanels:all-tabpanel, while researching my problem.  I
> have tried placing a dependency on the ${WL_HOME}/server/lib/xbean.jar
> in my pom, scoped as both system and provided (yes it is in my local
> repo), but I am still receiving the same error.  I even see it in my
> output classpath during compilation, so how can it still be throwing a
> NoClassDefFoundError?  Has anyone had success implementing the
> weblogic-maven-plugin, specifically version 2.9.0-SNAPSHOT?
>
> Thanks,
>
> Doug Tanner
>
>
> > -Original Message-
> > From: Scott Ryan [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ryan
> > Sent: Thursday, April 12, 2007 10:03 AM
> > To: Maven Users List
> > Subject: Re: Build error with weblogic-maven-plugin
> >
> > Yes that is a bug I am working on.  I have some free days over then
> > next week or so and hope to have a solution.  There are many jars
> > that need to be included in the APPC and I am trying to find a good
> > way to include them all without forcing you to load all the jars to
> > your repository.   I am also testing with 10 as well.  I hope to
have
> > some good news later this week.  Let me know if there is anything
> > else you need.
> >
> > Scott
> > On Apr 12, 2007, at 7:36 AM, Doug Tanner wrote:
> >
> > > I am using the 2.9.0-SNAPSHOT.  After building my war, I wish to
> > > precompile all my JSPs for faster response times.  As I understand
> it,
> > > the weblogic-maven-plugin goal weblogic:appc is what I need to use
> > > to do
> > > this.  However, I am getting a no class def found error.  From the
> > > output of my build I get the following lines, edited to remove
> > > non-essential information:
> > >
> > >
> > >
> > > [INFO] Weblogic APPC processing beginning for artifact
> > > c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
> > >
> > > [INFO]  Detailed Appc settings information AppcMojo[
> > >
> > >  basicClientJar = false
> > >
> > >  forceGeneration = true
> > >
> > >  keepGenerated = true
> > >
> > >  lineNumbers = false
> > >
> > >  inputArtifactPath =
> > > c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
> > >
> > >  outputArtifactPath = null
> > >
> > >  artifacts = [..., bf.webapps:common:jar:SNAPSHOT:compile,...]
> > >
> > >  project Packaging = war
> > >
> > >  verbose = true]
> > >
> > > [INFO] Using Classpath
> > > ...;\maven\localRepository\bf\webapps\common\SNAPSHOT\common-
> > > SNAPSHOT.ja
> > > r;...
> > >
> > > Created working directory:
> > > c:\DOCUME~1\dtanner\LOCALS~1\Temp\appcgen_broker.war
> > >
> > > [ERROR] Exception encountered during APPC processing
> > >
> > > weblogic.utils.compiler.ToolFailureException:
> com/bea/xml/XmlException
> > >
> > >
> > >
> > > This error does not sh

Re: How configure to Multiproject Site references

[James Abley]

On 20/05/07, Mac Systems <[EMAIL PROTECTED]> wrote:

Hello,

actually i wonder how to generate an  Site for an Multiproject ?

The (Master) Project Site will be generated for all my Modules but i do
not know
how to link to each module's site ?


Project:

pom.xml
|
|
 >Module A
pom.xml
-> target/site/index.html
 >Module B
pom.xml
-> target/site/index.html
 >Module C
pom.xml
-> target/site/index.html


regards,
Jens Hohl



I've used the  element in each module's pom.

../../Module A/target/site/

It works fine for builds locally.

Cheers,

James

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

pom as dependency

[zalym]

hi,

i have 5 modules and a pom.  I want to use these 5 modules in my war.  i
want to include the pom as a dependency but it isn't taking it.  i have to
include the modules rather for it to work.

Appreciate any help.

--Saleem
-- 
View this message in context: 
http://www.nabble.com/pom-as-dependency-tf3788997s177.html#a10715116
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: QALab Main Report shows a blank index page

[Rémy Sanlaville]

Hi Suchitra,

Now, I can give an example. You have to check for the version of the plugins
(I think, some have new version) and change the configuration for your
context :

   
   

   [...]

   
   
   
   org.apache.maven.plugins
   maven-checkstyle-plugin
   2.1
   
   
   checkstyle
   pre-site
   
   checkstyle
   
   
   
   

   
   
   
   org.codehaus.mojo
   findbugs-maven-plugin
   1.0-SNAPSHOT
   
   
   findbugs
   pre-site
   
   findbugs
   
   
   
   
   true
   
   

   
   
   
   org.apache.maven.plugins
   maven-pmd-plugin
   
   
   pmd
   pre-site
   
   pmd
   cpd
   
   
   
   
   
   ${basedir}/src/main/pmd/your-pmd-rules.xml

   
   true
   1.5
   xml
   
   

   
   
   
 org.codehaus.mojo
 cobertura-maven-plugin
 
   
 cobertura
 pre-site
 
   cobertura

 
   
 xml
 html
  

  

  
   
   

   
   

   [...]

   
   

   net.objectlab
   mvn-qalab-plugin
   2.2
   
 
   
   report-merge-chart
   report-movers-all
   
 
   
   
   true
   50
   
   

   
   
   
  org.codehaus.mojo
  cobertura-maven-plugin
  2.1-SNAPSHOT
   

   
   
   
   org.apache.maven.plugins
   maven-checkstyle-plugin
   2.1
   

   
   
   
   org.apache.maven.plugins
   maven-pmd-plugin
   
   1.5
   
   xml
   true
   iso-8859-1
   100
   
   

   

I haven't try simian because it is non-open source.

HTH,

Rémy

Re: Merge assemblies across projects?

[Arnaud Bailly]

Mark Diggory <[EMAIL PROTECTED]> writes:

> Hello List,
>

Hello Mark,

> I have a couple projects (each with their own assemblies) as modules
> of a current project.  Is there a way I can have their generated
> assemblies merged when I call assembly:assembly?
>

I don't think it is possible to do assembly merging simply. What I
usually do, for example to generate a source or binary distribution of
some project, is generate assembly in the toplevel project only, or in
a project that depends on all others. Here is an example for project
patchwork to assemble sources:



  src
  
zip
tar.gz
  
  false
  

  
oqube.patchwork:patchwork-bytes
oqube.patchwork:patchwork-control
oqube.patchwork:patchwork-ui
oqube.patchwork:patchwork-main
oqube.patchwork:patchwork-maven-plugin
oqube.patchwork:patchwork-it
  
  
patchwork/${artifactId}
  

  
  
   
 
  
  pom.xml
  
  
  patchwork/
  
   
 src
  patchwork/src
  
  


Here is another example that  assembles all dependent jars into a
single dir:




  test-bin
  
dir
  
  
 
  target
  
  
*.jar
  
 
 
 
 
  
   
  
 


HTH
-- 
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com


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

Re: Fw: Assistance required - why doesn't my index.html get generated when generating my site?

[Arnaud Bailly]

Ian Rowlands <[EMAIL PROTECTED]> writes:

Hello Ian,
>
> Any suggestions? Is there any other information that I can provide which
> would help diagnosis?
>

Did you try adding a site.xml descriptor inside the src/site
directory ? I think this is mandatory for multi-modules projects
(FIXME).  

Here is some very simple example:

In the parent:



 
  
  
 


In the modules:



 
  
  
 


Of course, you could add a custom index.xxx file, for example
src/site/apt/index.apt or src/site/xdoc/index.xdoc.

HTH
-- 
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com


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