JAVADOC-plugin: include comments from local dependent projects

2010-02-01 Thread Andrey Razumovsky
Hello,

Imagine I have two projects, A and B. Both are mine projects and aren't
published anywhere on the internet (don't have url). A is referenced from B.
Classes from B inherit a lot from classes from A.
The goal is to build docs for B, and include there only B sources. But also
I want comments for B methods to be automatically inherited from A docs.
Currently I've been unable to do that.
When I specify links to local storage of A docs, links are created, but
docs are not inherited.
When I specify sourcepath to storage of A src, docs are inherited, but
classes from A are included in docs as well (unwanted). Trying to exclude
them with excludePackageNames results in losing docs inheritance.

BTW I used to solve the problem with Ant once:
javadoc ... sourcepath=src/main/java;${A.LOCATION}/src/main/java
packagenames=B.PACKAGE.* /

How can I do that with Maven?

Thanks in advance,
Andrey


Automatic updates from repository

2010-02-01 Thread Andrey Razumovsky
Hello,

In our company we've got a local repository. There's an artifact (packaged
as POM or as JAR), which is deployed by me and used by other projects. It is
changing frequently, so we don't want referencing POM to change often (i.e.
version changes rarely). Now it seems new versions are not downloaded by
referencing projects automatically at build time. Is it because I haven't
specified SNAPSHOT postfix? If yes, is there a way to allow automatic
changes detection without SNAPSHOT postfix?

Thanks,
Andrey


Implementing an installer, which is maven-based

2010-02-01 Thread Dmitry Katsubo
Hi all!

Sorry, that my question seems to have been asked in maven user list
http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c2fbbcb49-65d3-4258-906f-e252372e9...@massol.net%3e
but I have the situation, similar to that. I hope you can help me, as
you might know what are the latest approaches to that.

I have some service, packaged as .WAR, which is completely build by
maven. However, this .WAR file requires customization: I need to package
it in different ways, depending on user input. Basically, user should
himself select the components, he would like to add to WAR, and define
some simple configuration for these components. After the packaging the
installer should optionally launch tomcat (or jetty) and start a WAR
application.

I need to write the installer, that:
1. Asks user for the list of components (=checkboxes)
2. For each component, asks for the configuration options (then to be
saved as .property file)
3. Package everything from steps 1 and 2 into WAR file. Dependences
should be fetched from publicly available maven repository.
4. Optionally launch tomcat (or jetty) in a background
5. Maybe execute some other script, depending on choices in 1 (like
demo application).

Let me know, if there is a universal solution for that.

Thanks in advance for any hint.

-- 
With best regards,
Dmitry

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Implementing an installer, which is maven-based

2010-02-01 Thread Stephen Connolly
have you tried izpack-maven-plugin?

2010/2/1 Dmitry Katsubo dm...@mail.ru

 Hi all!

 Sorry, that my question seems to have been asked in maven user list

 http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c2fbbcb49-65d3-4258-906f-e252372e9...@massol.net%3e
 but I have the situation, similar to that. I hope you can help me, as
 you might know what are the latest approaches to that.

 I have some service, packaged as .WAR, which is completely build by
 maven. However, this .WAR file requires customization: I need to package
 it in different ways, depending on user input. Basically, user should
 himself select the components, he would like to add to WAR, and define
 some simple configuration for these components. After the packaging the
 installer should optionally launch tomcat (or jetty) and start a WAR
 application.

 I need to write the installer, that:
 1. Asks user for the list of components (=checkboxes)
 2. For each component, asks for the configuration options (then to be
 saved as .property file)
 3. Package everything from steps 1 and 2 into WAR file. Dependences
 should be fetched from publicly available maven repository.
 4. Optionally launch tomcat (or jetty) in a background
 5. Maybe execute some other script, depending on choices in 1 (like
 demo application).

 Let me know, if there is a universal solution for that.

 Thanks in advance for any hint.

 --
 With best regards,
 Dmitry

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Maven and WTP integration

2010-02-01 Thread Martin Schayna

Hi all,

we have pretty large project, successfully mavenized with Maven 2,
split into several module projects under one parent pom. We are using
m2eclipse plugin in Eclipse 3.5.

Project tree looks like:

parent/ (pom project)
 +-- lib-core/ (jar project)
 +-- lib-web/  (jar project, with shared webapp folder)
 +-- app1/ (war project)
 +-- app2/ (war project)
 +-- app3/ (war project)

parent project serves as agregator, its pom.xml defines common settings.
lib-web project depends on lib-core project, application projects depend
on both lib projects. All projects share same version, we are releasing
all applications at once through parent pom.

For everyday develepment we use SNAPSHOT postfix in version, dependecies
on module projects are specified as project dependencies, so changes
in library projects in Eclipse cause rebuild dependent application
projects. Snapshots are disabled in our repository (Archiva).

But when I try setup WTP support through maven-eclipse-plugin goal
eclipse:eclipse and some necessary changes in Eclipse, publishing to
Tomcat creates only WEB-INF/lib folder with (correct) out-of-project
jar dependencies and WEB-INF/classes folder with CURRENT project
classes. No binaries from project dependencies lib-core and lib-web.

I have tried to change org.eclipse.wst.common.component file in many ways,
e.g. dependent-module, but without success.

Another weird thing: when I try to include resources from shared webapp
folder from lib-web project and use relative source-path like this:

   wb-resource deploy-path=/
source-path=../lib-web/src/main/webapp/

publish can't copy subfolders content to Tomcat. Must explicitly specified:

   wb-resource deploy-path=/btns
source-path=../lib-web/src/main/webapp/btns/
   wb-resource deploy-path=/icons
source-path=../lib-web/src/main/webapp/icons/
   wb-resource deploy-path=/imgs
source-path=../lib-web/src/main/webapp/imgs/
   ...

Please, what is the right WTP setup for multi modules configuration with 
project

dependencies and shared resources? Or is there any documentation for file
org.eclipse.wst.common.component?

I'm going little bit crazy... thank God debugging with Jetty works like 
a charm,
either with shared resources (must hack with 
WebAppContext.setResourceBase() in

starter class).

Thanks a lot.

Martin Schayna



Re: Maven and WTP integration

2010-02-01 Thread Antonio Petrelli
2010/2/1 Martin Schayna martin.scha...@abra.eu:
 we have pretty large project, successfully mavenized with Maven 2,
 split into several module projects under one parent pom. We are using
 m2eclipse plugin in Eclipse 3.5.

What version? I am a happy user of the 0.9.9 development version, it
seems that versions prior to this are not compatible with Eclipse 3.5.
Update site: http://m2eclipse.sonatype.org/update-dev/

HTH
Antonio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven and WTP integration

2010-02-01 Thread Manuel Grau
Hi Martin,

My setup is similar to yours. Enter each appN folder and type this:

mvn -Dwtpversion=2.0 eclipse:m2eclipse

Is what I did and it works for me.

2010/2/1 Martin Schayna martin.scha...@abra.eu

 Hi all,

 we have pretty large project, successfully mavenized with Maven 2,
 split into several module projects under one parent pom. We are using
 m2eclipse plugin in Eclipse 3.5.

 Project tree looks like:

 parent/ (pom project)
  +-- lib-core/ (jar project)
  +-- lib-web/  (jar project, with shared webapp folder)
  +-- app1/ (war project)
  +-- app2/ (war project)
  +-- app3/ (war project)

 parent project serves as agregator, its pom.xml defines common settings.
 lib-web project depends on lib-core project, application projects depend
 on both lib projects. All projects share same version, we are releasing
 all applications at once through parent pom.

 For everyday develepment we use SNAPSHOT postfix in version, dependecies
 on module projects are specified as project dependencies, so changes
 in library projects in Eclipse cause rebuild dependent application
 projects. Snapshots are disabled in our repository (Archiva).

 But when I try setup WTP support through maven-eclipse-plugin goal
 eclipse:eclipse and some necessary changes in Eclipse, publishing to
 Tomcat creates only WEB-INF/lib folder with (correct) out-of-project
 jar dependencies and WEB-INF/classes folder with CURRENT project
 classes. No binaries from project dependencies lib-core and lib-web.

 I have tried to change org.eclipse.wst.common.component file in many ways,
 e.g. dependent-module, but without success.

 Another weird thing: when I try to include resources from shared webapp
 folder from lib-web project and use relative source-path like this:

   wb-resource deploy-path=/
source-path=../lib-web/src/main/webapp/

 publish can't copy subfolders content to Tomcat. Must explicitly specified:

   wb-resource deploy-path=/btns
source-path=../lib-web/src/main/webapp/btns/
   wb-resource deploy-path=/icons
source-path=../lib-web/src/main/webapp/icons/
   wb-resource deploy-path=/imgs
source-path=../lib-web/src/main/webapp/imgs/
   ...

 Please, what is the right WTP setup for multi modules configuration with
 project
 dependencies and shared resources? Or is there any documentation for file
 org.eclipse.wst.common.component?

 I'm going little bit crazy... thank God debugging with Jetty works like a
 charm,
 either with shared resources (must hack with
 WebAppContext.setResourceBase() in
 starter class).

 Thanks a lot.

 Martin Schayna




-- 
Everything should be made as simple as possible, but not simpler Albert
Einstein


RE: Automatic updates from repository

2010-02-01 Thread Ilya Kazakevich
Hello, 

Why do not you want to use SNAPSHOT?

Fixed version should never be changed but snapshot can.
You have SNAPSHOT while you develop your artifact, and when you're ready to
release it -- you give it version number.

Other artifacts may depend on your snapshot. If so -- maven knows that
snapshot could be changed and fetches new version of snapshot periodically.
But if you depend on fixed version (i.e: my-artifact-1.2.3) and you already
have it in your local repository -- maven would not fetch it again, because
it should be the same and maven knows it.

If you really want to refetch such artifact -- simply remove it from your
local repository, but that's bad idea because it breakes maven's philosophy
and brings pain in your development process.

Ilya.


-Original Message-
From: Andrey Razumovsky [mailto:razumovsky.and...@gmail.com] 
Sent: Monday, February 01, 2010 1:42 PM
To: Maven Users List
Subject: Automatic updates from repository

Hello,

In our company we've got a local repository. There's an artifact (packaged
as POM or as JAR), which is deployed by me and used by other projects. It is
changing frequently, so we don't want referencing POM to change often (i.e.
version changes rarely). Now it seems new versions are not downloaded by
referencing projects automatically at build time. Is it because I haven't
specified SNAPSHOT postfix? If yes, is there a way to allow automatic
changes detection without SNAPSHOT postfix?

Thanks,
Andrey


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Automatic updates from repository

2010-02-01 Thread Ilya Kazakevich
Hello, 

Why do not you want to use SNAPSHOT?

Fixed version should never be changed but snapshot can.
You have SNAPSHOT while you develop your artifact, and when you're ready to
release it -- you give it version number.

Other artifacts may depend on your snapshot. If so -- maven knows that
snapshot could be changed and fetches new version of snapshot periodically.
But if you depend on fixed version (i.e: my-artifact-1.2.3) and you already
have it in your local repository -- maven would not fetch it again, because
it should be the same and maven knows it.

If you really want to refetch such artifact -- simply remove it from your
local repository, but that's bad idea because it breakes maven's philosophy
and brings pain in your development process.

Ilya.


-Original Message-
From: Andrey Razumovsky [mailto:razumovsky.and...@gmail.com] 
Sent: Monday, February 01, 2010 1:42 PM
To: Maven Users List
Subject: Automatic updates from repository

Hello,

In our company we've got a local repository. There's an artifact (packaged
as POM or as JAR), which is deployed by me and used by other projects. It is
changing frequently, so we don't want referencing POM to change often (i.e.
version changes rarely). Now it seems new versions are not downloaded by
referencing projects automatically at build time. Is it because I haven't
specified SNAPSHOT postfix? If yes, is there a way to allow automatic
changes detection without SNAPSHOT postfix?

Thanks,
Andrey


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Automatic updates from repository

2010-02-01 Thread Andrey Razumovsky
Hi,

Thanks for an answer.
I don't want to use snapshot for every pom because it brings ugly postfixes
for artifacts e.g. when I deploy them to server, and i don't want to
configure new names for every artifact in my POM's deploy to server
executions.
Removing artifact from local repo isn't fine because I want automatic
updates for all developers

2010/2/1 Ilya Kazakevich kazakev...@devexperts.com

 Hello,

 Why do not you want to use SNAPSHOT?

 Fixed version should never be changed but snapshot can.
 You have SNAPSHOT while you develop your artifact, and when you're ready to
 release it -- you give it version number.

 Other artifacts may depend on your snapshot. If so -- maven knows that
 snapshot could be changed and fetches new version of snapshot periodically.
 But if you depend on fixed version (i.e: my-artifact-1.2.3) and you already
 have it in your local repository -- maven would not fetch it again, because
 it should be the same and maven knows it.

 If you really want to refetch such artifact -- simply remove it from your
 local repository, but that's bad idea because it breakes maven's philosophy
 and brings pain in your development process.

 Ilya.


 -Original Message-
 From: Andrey Razumovsky [mailto:razumovsky.and...@gmail.com]
 Sent: Monday, February 01, 2010 1:42 PM
 To: Maven Users List
 Subject: Automatic updates from repository

 Hello,

 In our company we've got a local repository. There's an artifact (packaged
 as POM or as JAR), which is deployed by me and used by other projects. It
 is
 changing frequently, so we don't want referencing POM to change often (i.e.
 version changes rarely). Now it seems new versions are not downloaded by
 referencing projects automatically at build time. Is it because I haven't
 specified SNAPSHOT postfix? If yes, is there a way to allow automatic
 changes detection without SNAPSHOT postfix?

 Thanks,
 Andrey


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
Andrey


Re: Automatic updates from repository

2010-02-01 Thread Aleksey Didik

I will write a mail in Russian to your gmail account.
It will be more useful to speak about this problem.

Aleksey Didik.

01.02.2010 17:06, Andrey Razumovsky пишет:

Hi,

Thanks for an answer.
I don't want to use snapshot for every pom because it brings ugly postfixes
for artifacts e.g. when I deploy them to server, and i don't want to
configure new names for every artifact in my POM's deploy to server
executions.
Removing artifact from local repo isn't fine because I want automatic
updates for all developers

2010/2/1 Ilya Kazakevichkazakev...@devexperts.com

   

Hello,

Why do not you want to use SNAPSHOT?

Fixed version should never be changed but snapshot can.
You have SNAPSHOT while you develop your artifact, and when you're ready to
release it -- you give it version number.

Other artifacts may depend on your snapshot. If so -- maven knows that
snapshot could be changed and fetches new version of snapshot periodically.
But if you depend on fixed version (i.e: my-artifact-1.2.3) and you already
have it in your local repository -- maven would not fetch it again, because
it should be the same and maven knows it.

If you really want to refetch such artifact -- simply remove it from your
local repository, but that's bad idea because it breakes maven's philosophy
and brings pain in your development process.

Ilya.


-Original Message-
From: Andrey Razumovsky [mailto:razumovsky.and...@gmail.com]
Sent: Monday, February 01, 2010 1:42 PM
To: Maven Users List
Subject: Automatic updates from repository

Hello,

In our company we've got a local repository. There's an artifact (packaged
as POM or as JAR), which is deployed by me and used by other projects. It
is
changing frequently, so we don't want referencing POM to change often (i.e.
version changes rarely). Now it seems new versions are not downloaded by
referencing projects automatically at build time. Is it because I haven't
specified SNAPSHOT postfix? If yes, is there a way to allow automatic
changes detection without SNAPSHOT postfix?

Thanks,
Andrey


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


 


   



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Very mysterious checkstyle failure

2010-02-01 Thread Benson Margulies
On only one of our many build machines, we're suffering from:

Embedded error:
/basis/users/nightly/autobuild/clients/nightly-trunk-2010013119/rlp/rlp/source/java/obj/amd64-glibc23-gcc40/site/checkstyle.html
(No such file or directory)

Note that we redirect the target directory in our builds. Any advice
before I file a JIRA?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven and WTP integration

2010-02-01 Thread Martin Schayna

Eclipse Platform 3.5.1
Eclipse WST/JST 3.1.1
m2eclipse 0.9.9 (but very same with stable 0.9.8)
Maven 2.0.9
Java 1.6.0_14

When I try to append WTP support into war application project by this

$ mvn -Dwtpversion=2.0 eclipse:m2eclipse

and then:

run Eclipse,
convert WTP configuration (Ctrl+1 QuickFix),
add Maven dependecies to WTP (Ctrl+1 QuickFix),
setup server Tomcat (in Server view),
publish application to Tomcat (in Server view),
run server

ClassNotFoundException throws.

When I look into folder wtpwebapps in workspace Tomcat structure, I see 
that

publish operation was not complete:
- WEB-INF/classes contains current project classes (OK)
- WEB-INF/lib contains all dependent out-of-project jars (OK)
- there aren't binaries of dependent jar projects from my workspace (NOT OK)
- there aren't resources of shared webapps folder from other project in 
my workspace (NOT OK)


After some tricky editing of file 
.settings/org.eclipse.wst.common.component
I'm able to publish shared webapps folder, but not for jar project 
dependencies...


Any ideas?

Thank you

Martin Schayna



Antonio Petrelli wrote:

2010/2/1 Martin Schayna martin.scha...@abra.eu:
  

we have pretty large project, successfully mavenized with Maven 2,
split into several module projects under one parent pom. We are using
m2eclipse plugin in Eclipse 3.5.



What version? I am a happy user of the 0.9.9 development version, it
seems that versions prior to this are not compatible with Eclipse 3.5.
Update site: http://m2eclipse.sonatype.org/update-dev/

HTH
Antonio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

  


Re: Maven and WTP integration

2010-02-01 Thread Antonio Petrelli
2010/2/1 Martin Schayna martin.scha...@abra.eu:
 run Eclipse,
 convert WTP configuration (Ctrl+1 QuickFix),
 add Maven dependecies to WTP (Ctrl+1 QuickFix),

Why all of this stuff? Does not your Checkout as Maven project work?
If you do it in the POM project, it should download and create all
subprojects automatically.
This works with Subclipse (Subversion), I don't know with others.

Antonio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Implementing an installer, which is maven-based

2010-02-01 Thread Dmitry Katsubo
Stephen Connolly wrote on 01/02/2010 11:50:
 have you tried izpack-maven-plugin?

Hi Stephan!

I had a look at IzPack shortly, and as I understood, IzPack creates an
installer for your maven project. So, your maven targets artifacts have
to be packaged before creating an installation. What I ideally need is:

1. Create a lightweight installator, that will not contain any maven
artifacts (or, if not possible, contain all of them).
2. When end user launches the installator, it is asked for some input,
which is saved as .property file.
3. Installator then fetches only the artifacts needed (selected by user
+ those which are obligatory), and replaces the property file(s) in
those artifacts. Finally it creates ready to-use WAR package.

If you have an example of above -- give me a link, please. That would be
great!

Right now I see the only way is to create a temporary maven project and
after doing steps (1) and (2) launch maven to complete the packaging.

-- 
With best regards,
Dmitry

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Automatic updates from repository

2010-02-01 Thread Wayne Fay
 I don't want to use snapshot for every pom because it brings ugly postfixes
 for artifacts e.g. when I deploy them to server, and i don't want to
 configure new names for every artifact in my POM's deploy to server
 executions.

Maven is opinionated and doesn't care about what you think is ugly.

 Removing artifact from local repo isn't fine because I want automatic
 updates for all developers

Versions never change once published is a central tenet of Maven. You
should be using Snapshots, period. There is no other work around.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven Release Plugin Fix

2010-02-01 Thread Vach, Matthias
Hi maven-release-plugin committer,

There is an issue for the maven-release-plugin 
(http://jira.codehaus.org/browse/MRELEASE-495) which is prerequisite for the 
osgi-release-plugin (patch https://issues.sonatype.org/browse/TYCHO-214).

Do you plan to take care for that issue? If not now, when do you plan to take 
care?

Regards Matthias



Re: JAVADOC-plugin: include comments from local dependent projects

2010-02-01 Thread Ron Wheeler

Andrey Razumovsky wrote:

Hello,

Imagine I have two projects, A and B. Both are mine projects and aren't
published anywhere on the internet (don't have url). A is referenced from B.
Classes from B inherit a lot from classes from A.
The goal is to build docs for B, and include there only B sources. But also
I want comments for B methods to be automatically inherited from A docs.
Currently I've been unable to do that.
When I specify links to local storage of A docs, links are created, but
docs are not inherited.
When I specify sourcepath to storage of A src, docs are inherited, but
classes from A are included in docs as well (unwanted). Trying to exclude
them with excludePackageNames results in losing docs inheritance.

BTW I used to solve the problem with Ant once:
javadoc ... sourcepath=src/main/java;${A.LOCATION}/src/main/java
packagenames=B.PACKAGE.* /

How can I do that with Maven?

Thanks in advance,
Andrey

  
Are you sure that you would not be happier with more small library 
projects that create JARs dependencies for the main projects?
Combined with interfaces and implementations, you should get a decent 
set of docs plus a set of code that is easier to maintain.


Ron

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Plugin for updating external XML file content

2010-02-01 Thread Ilya Kazakevich
Hi all,

I have a slightly weird situation: I need to update contents of some
external XML file each time I do deploy.
I wonder if there is a plugin that could be installed in deploy phase and
do that for me?

Plugin should be able to replace some token in text file for example or
something like that. 

Thanks. 


Ilya Kazakevich




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Plugin for updating external XML file content

2010-02-01 Thread Aleksey Didik

I don't see anything with this functionality.
May be better to use /maven-antrun-plugin/ and write necessary ant script.

Best regards,
Aleksey.

01.02.2010 19:42, Ilya Kazakevich ?:

Hi all,

I have a slightly weird situation: I need to update contents of some
external XML file each time I do deploy.
I wonder if there is a plugin that could be installed in deploy phase and
do that for me?

Plugin should be able to replace some token in text file for example or
something like that.

Thanks. 


Ilya Kazakevich




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

   




Re: Plugin for updating external XML file content

2010-02-01 Thread Aleksey Didik

But I have found this one:

http://code.google.com/p/maven-replacer-plugin/

01.02.2010 19:42, Ilya Kazakevich пишет:

Hi all,

I have a slightly weird situation: I need to update contents of some
external XML file each time I do deploy.
I wonder if there is a plugin that could be installed in deploy phase and
do that for me?

Plugin should be able to replace some token in text file for example or
something like that.

Thanks. 


Ilya Kazakevich




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

   



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Plugin for updating external XML file content

2010-02-01 Thread Ilya Kazakevich
Thanks.
Actually, I wanna get rid of ant in our project, but this can work.

We are also looking at xml-maven-plugin. We can generate XML file each time
using XSL while passing information we need to insert as parameters. 


Ilya. 

-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru] 
Sent: Monday, February 01, 2010 6:51 PM
To: Maven Users List
Subject: Re: Plugin for updating external XML file content

I don't see anything with this functionality.
May be better to use /maven-antrun-plugin/ and write necessary ant script.

Best regards,
Aleksey.

01.02.2010 19:42, Ilya Kazakevich ?:
 Hi all,

 I have a slightly weird situation: I need to update contents of some 
 external XML file each time I do deploy.
 I wonder if there is a plugin that could be installed in deploy 
 phase and do that for me?

 Plugin should be able to replace some token in text file for example 
 or something like that.

 Thanks.   

 
 Ilya Kazakevich




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Plugin for updating external XML file content

2010-02-01 Thread Ilya Kazakevich
Excelent!

Thanks, Aleksey.
 

-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru] 
Sent: Monday, February 01, 2010 6:53 PM
To: Maven Users List
Subject: Re: Plugin for updating external XML file content

But I have found this one:

http://code.google.com/p/maven-replacer-plugin/

01.02.2010 19:42, Ilya Kazakevich пишет:
 Hi all,

 I have a slightly weird situation: I need to update contents of some 
 external XML file each time I do deploy.
 I wonder if there is a plugin that could be installed in deploy 
 phase and do that for me?

 Plugin should be able to replace some token in text file for example 
 or something like that.

 Thanks.   

 
 Ilya Kazakevich




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Plugin for updating external XML file content

2010-02-01 Thread Gorham-Engard, Frank
What do you see as the value of completely eliminating ant use from your Maven 
project. I see ant as a tool that is supported and may be appropriate for some 
situations.
To have a policy that rules out a useful tool seems counterproductive.

!-- Frank Gorham-Engard →

-Original Message-
From: Ilya Kazakevich [mailto:kazakev...@devexperts.com] 
Sent: Monday, February 01, 2010 10:57 AM
To: 'Maven Users List'
Subject: RE: Plugin for updating external XML file content

Thanks.
Actually, I wanna get rid of ant in our project, ...


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Plugin for updating external XML file content

2010-02-01 Thread Ilya Kazakevich
Hello Frank.

Using too many tools could make project too complicated. I saw a project
with maven, ant and .bat files. It was tricky:)
If something could be solved using maven only -- we should do so. Ant-script
at least requires ant to be installed on platform.
If something cannt be solved using existing maven plugins -- we should make
decision between creating maven plugin and using ant script, because ant
script is better than shell script for example (because of its
cross-platform nature). But I am sure that 99% of our issues could be solved
using maven only. But that’s my imho, and its probably not a best practice.


-Original Message-
From: Gorham-Engard, Frank [mailto:frank_gorham-eng...@cable.comcast.com]
Sent: Monday, February 01, 2010 7:20 PM
To: Maven Users List
Subject: RE: Plugin for updating external XML file content

What do you see as the value of completely eliminating ant use from your
Maven project. I see ant as a tool that is supported and may be appropriate
for some situations.
To have a policy that rules out a useful tool seems counterproductive.

!-- Frank Gorham-Engard →

-Original Message-
From: Ilya Kazakevich [mailto:kazakev...@devexperts.com]
Sent: Monday, February 01, 2010 10:57 AM
To: 'Maven Users List'
Subject: RE: Plugin for updating external XML file content

Thanks.
Actually, I wanna get rid of ant in our project, ...


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Mysterious download failure sequence

2010-02-01 Thread Benson Margulies
Friends don't let friends design a separate pluginRepository set, and
then produce completely mysterious messages that neglect to mention
that a failure related to looking for something in it.

In other words, this happens when you add the repo to repositories
instead of pluginRepositories and then try to find a plugin in it.

I'm only using jvnet because the non-jvnet animal sniffer won't work
for me at all, and the jvnet one does.



On Mon, Feb 1, 2010 at 1:49 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
 friends don't let friends use the jvnet repo

 Sent from my [rhymes with tryPod] ;-)

 On 1 Feb 2010, at 01:44, Benson Margulies bimargul...@gmail.com wrote:

 Note that it successfully gets the pom from the jvnet repo, but
 doesn't try to retrieve the jar from the same place.

 Downloading:
 http://repo1.maven.org/maven2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.pom
 [INFO] Unable to find resource 'org.jvnet:animal-sniffer:pom:1.2' in
 repository central (http://repo1.maven.org/maven2)
 Downloading:
 http://download.java.net/maven/2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.pom
 4K downloaded  (animal-sniffer-1.2.pom)
 Downloading:
 http://repo1.maven.org/maven2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.jar
 [INFO] Unable to find resource
 'org.jvnet:animal-sniffer:maven-plugin:1.2' in repository central
 (http://repo1.maven.org/maven2)

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version

2010-02-01 Thread Thomas Harris
Friday, I was able to run the 'site' build on our project. This morning, I get 
the following error:

[INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: 
Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

org.apache.maven.skins:maven-default-skin:jar:RELEASE
We've changed nothing, so something bad has occurred to something out on the 
public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows 
XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on 
all platforms here when attempting to call mvn site on our project.

I've updated this closed ticket. The ticket should be re-opened, as the same 
old problem is now occurring every 'site' build for us. Can someone please fix 
this soon? We cannot move forward on our project at this point.

http://jira.codehaus.org/browse/MNG-3139

Tom



RE: Plugin for updating external XML file content

2010-02-01 Thread Gorham-Engard, Frank
Hi Ilya
Yes, I agree, keeping it simple is a positive value.

Perhaps you haven't noticed that ant is an existing maven plugin. It is 
possible to run inline ant tasks or external scripts without having an ant 
installation on your system. Maven will get ant from the Maven repositories 
for you.

I'm just saying that I think starting a new project to create a plugin is not 
as simple as using a bit of ant script, at least for those who have a little 
ant exposure.

!-- Frank Gorham-Engard →

-Original Message-
From: Ilya Kazakevich [mailto:kazakev...@devexperts.com] 
Sent: Monday, February 01, 2010 1:08 PM
To: 'Maven Users List'
Subject: RE: Plugin for updating external XML file content

Hello Frank.

Using too many tools could make project too complicated. I saw a project
with maven, ant and .bat files. It was tricky:)
If something could be solved using maven only -- we should do so. Ant-script
at least requires ant to be installed on platform.
If something cannt be solved using existing maven plugins -- we should make
decision between creating maven plugin and using ant script, because ant
script is better than shell script for example (because of its
cross-platform nature). But I am sure that 99% of our issues could be solved
using maven only. But that’s my imho, and its probably not a best practice.


-Original Message-
From: Gorham-Engard, Frank [mailto:frank_gorham-eng...@cable.comcast.com]
Sent: Monday, February 01, 2010 7:20 PM
To: Maven Users List
Subject: RE: Plugin for updating external XML file content

What do you see as the value of completely eliminating ant use from your
Maven project. I see ant as a tool that is supported and may be appropriate
for some situations.
To have a policy that rules out a useful tool seems counterproductive.

!-- Frank Gorham-Engard →

-Original Message-
From: Ilya Kazakevich [mailto:kazakev...@devexperts.com]
Sent: Monday, February 01, 2010 10:57 AM
To: 'Maven Users List'
Subject: RE: Plugin for updating external XML file content

Thanks.
Actually, I wanna get rid of ant in our project, ...


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Plugin for updating external XML file content

2010-02-01 Thread Wayne Fay
 If something could be solved using maven only -- we should do so. Ant-script
 at least requires ant to be installed on platform.
 If something cannt be solved using existing maven plugins -- we should make

Except that you can use Ant as a Maven plugin which does not require
Ant to be installed at all...

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: JAVADOC-plugin: include comments from local dependent projects

2010-02-01 Thread Andrey Razumovsky
Sorry, but I don't understand. I already have small library (A) and main
project (B). E.g. A contains interfaces, and B implementations. The question
is: how can I build docs for B so that, if none specified, method
descriptions are inherited from A?

2010/2/1 Ron Wheeler rwhee...@artifact-software.com

 Andrey Razumovsky wrote:

 Hello,

 Imagine I have two projects, A and B. Both are mine projects and aren't
 published anywhere on the internet (don't have url). A is referenced from
 B.
 Classes from B inherit a lot from classes from A.
 The goal is to build docs for B, and include there only B sources. But
 also
 I want comments for B methods to be automatically inherited from A docs.
 Currently I've been unable to do that.
 When I specify links to local storage of A docs, links are created, but
 docs are not inherited.
 When I specify sourcepath to storage of A src, docs are inherited, but
 classes from A are included in docs as well (unwanted). Trying to exclude
 them with excludePackageNames results in losing docs inheritance.

 BTW I used to solve the problem with Ant once:
 javadoc ... sourcepath=src/main/java;${A.LOCATION}/src/main/java
 packagenames=B.PACKAGE.* /

 How can I do that with Maven?

 Thanks in advance,
 Andrey



 Are you sure that you would not be happier with more small library projects
 that create JARs dependencies for the main projects?
 Combined with interfaces and implementations, you should get a decent set
 of docs plus a set of code that is easier to maintain.

 Ron

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
Andrey


Re: Errors after upgrade to 2.2.1

2010-02-01 Thread tharrisx


We will drop the dependency reports for now. I'll just tell the developers
on our teams to use the JDepend Eclipse plugin interactively on a regular
basis until Maven gets fixed.

Of course, now, the whole site shebang is broken anyway because of some
'missing skin' error, so until that gets fixed, we can't do squat.

Tom
-- 
View this message in context: 
http://n2.nabble.com/Errors-after-upgrade-to-2-2-1-tp4401158p4496342.html
Sent from the maven users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Mysterious download failure sequence

2010-02-01 Thread Stephen Connolly

well I'll try and fix animal sniffer

Sent from my [rhymes with tryPod] ;-)

On 1 Feb 2010, at 18:15, Benson Margulies bimargul...@gmail.com wrote:


Friends don't let friends design a separate pluginRepository set, and
then produce completely mysterious messages that neglect to mention
that a failure related to looking for something in it.

In other words, this happens when you add the repo to repositories
instead of pluginRepositories and then try to find a plugin in it.

I'm only using jvnet because the non-jvnet animal sniffer won't work
for me at all, and the jvnet one does.



On Mon, Feb 1, 2010 at 1:49 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:

friends don't let friends use the jvnet repo

Sent from my [rhymes with tryPod] ;-)

On 1 Feb 2010, at 01:44, Benson Margulies bimargul...@gmail.com  
wrote:



Note that it successfully gets the pom from the jvnet repo, but
doesn't try to retrieve the jar from the same place.

Downloading:
http://repo1.maven.org/maven2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.pom
[INFO] Unable to find resource 'org.jvnet:animal-sniffer:pom:1.2' in
repository central (http://repo1.maven.org/maven2)
Downloading:
http://download.java.net/maven/2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.pom
4K downloaded  (animal-sniffer-1.2.pom)
Downloading:
http://repo1.maven.org/maven2/org/jvnet/animal-sniffer/1.2/animal-sniffer-1.2.jar
[INFO] Unable to find resource
'org.jvnet:animal-sniffer:maven-plugin:1.2' in repository central
(http://repo1.maven.org/maven2)

--- 
--

To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



plugin for cactus

2010-02-01 Thread mark babcock
Could someone point me to how to install the cactus plugin for maven?


RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version

2010-02-01 Thread Thomas Harris
I attempted the workaround listed in the ticket 
(http://jira.codehaus.org/browse/MNG-3139), namely:

1. Create a /src/site/site.xml file in the top-level maven project, containing:

[Code]
project
  skin
groupIdorg.apache.maven.skins/groupId
artifactIdmaven-default-skin/artifactId
version1.0/version
  /skin
/project
[/Code]

Now the mvn site site-deploy works, however, there is no longer any links on 
the left-side menu, contrary to what I'd expect from a workaround. So, that's a 
bunk workaround.

So, at this stage, our project is dead in the water until someone fixes the 
site plugin to get around this 'missing skin' defect. Every Hudson build fails 
with this error.

Have users experienced similar issues in the past? How long does it usually 
take for a critical fix to get deployed to the central maven repos? Should I 
start writing the ant scripts for our projects? ;)

Tom

-Original Message-
From: Thomas Harris 
Sent: Monday, February 01, 2010 1:26 PM
To: users@maven.apache.org
Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: 
Unable to determine the release version

Friday, I was able to run the 'site' build on our project. This morning, I get 
the following error:

[INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: 
Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

org.apache.maven.skins:maven-default-skin:jar:RELEASE
We've changed nothing, so something bad has occurred to something out on the 
public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows 
XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on 
all platforms here when attempting to call mvn site on our project.

I've updated this closed ticket. The ticket should be re-opened, as the same 
old problem is now occurring every 'site' build for us. Can someone please fix 
this soon? We cannot move forward on our project at this point.

http://jira.codehaus.org/browse/MNG-3139

Tom


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version

2010-02-01 Thread Dennis Lundberg
On 2010-02-01 21:24, Thomas Harris wrote:
 I attempted the workaround listed in the ticket 
 (http://jira.codehaus.org/browse/MNG-3139), namely:
 
 1. Create a /src/site/site.xml file in the top-level maven project, 
 containing:
 
 [Code]
 project
   skin
 groupIdorg.apache.maven.skins/groupId
 artifactIdmaven-default-skin/artifactId
 version1.0/version
   /skin
 /project
 [/Code]
 
 Now the mvn site site-deploy works, however, there is no longer any links 
 on the left-side menu, contrary to what I'd expect from a workaround. So, 
 that's a bunk workaround.

Which version of the Site Plugin are you using?
There is a bug in version 2.1 about missing menu links.

 So, at this stage, our project is dead in the water until someone fixes the 
 site plugin to get around this 'missing skin' defect. Every Hudson build 
 fails with this error.
 
 Have users experienced similar issues in the past? How long does it usually 
 take for a critical fix to get deployed to the central maven repos? Should I 
 start writing the ant scripts for our projects? ;)
 
 Tom
 
 -Original Message-
 From: Thomas Harris 
 Sent: Monday, February 01, 2010 1:26 PM
 To: users@maven.apache.org
 Subject: SiteToolException: ArtifactNotFoundException: The skin does not 
 exist: Unable to determine the release version
 
 Friday, I was able to run the 'site' build on our project. This morning, I 
 get the following error:
 
 [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: 
 Unable to determine the release version
 
 Try downloading the file manually from the project website.
 
 Then, install it using the command:
 mvn install:install-file -DgroupId=org.apache.maven.skins 
 -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
 -Dfile=/path/to/file
 
 Alternatively, if you host your own repository you can deploy the file there:
 mvn deploy:deploy-file -DgroupId=org.apache.maven.skins 
 -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
 -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
 
 org.apache.maven.skins:maven-default-skin:jar:RELEASE
 We've changed nothing, so something bad has occurred to something out on the 
 public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows 
 XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) 
 on all platforms here when attempting to call mvn site on our project.
 
 I've updated this closed ticket. The ticket should be re-opened, as the same 
 old problem is now occurring every 'site' build for us. Can someone please 
 fix this soon? We cannot move forward on our project at this point.
 
 http://jira.codehaus.org/browse/MNG-3139
 
 Tom
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 


-- 
Dennis Lundberg

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



relocation tags

2010-02-01 Thread EJ Ciramella
So if we've relocated a library here - and deployed once to archiva, is it too 
late to use the relocation tag?

We've corrected a bunch of group ids, and wanted to break the build.  Instead, 
by not using the relocate tags, we've gained other errors and some silent 
inclusions of the same jar (twice).




RE: relocation tags

2010-02-01 Thread EJ Ciramella
Also - how do you really leverage these tags?  Do you put it in a version of 
the module in its old location?

-Original Message-
From: EJ Ciramella [mailto:ecirame...@upromise.com] 
Sent: Monday, February 01, 2010 3:35 PM
To: users@maven.apache.org
Subject: relocation tags

So if we've relocated a library here - and deployed once to archiva, is it too 
late to use the relocation tag?

We've corrected a bunch of group ids, and wanted to break the build.  Instead, 
by not using the relocate tags, we've gained other errors and some silent 
inclusions of the same jar (twice).



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version

2010-02-01 Thread Thomas Harris
I have been using version 2.1 of the maven-site-plugin all along; When I had no 
site.xml file, I got all my menu items and they all worked. Now, without the 
site.xml file, the 'site' build fails as described. With the site.xml file 
detailed below, the 'site' build succeeds, however the resulting site has no 
links at all on the left hand side. :|

Tom


-Original Message-
From: Dennis Lundberg [mailto:denn...@apache.org] 
Sent: Monday, February 01, 2010 3:32 PM
To: Maven Users List
Subject: Re: SiteToolException: ArtifactNotFoundException: The skin does not 
exist: Unable to determine the release version

On 2010-02-01 21:24, Thomas Harris wrote:
 I attempted the workaround listed in the ticket 
 (http://jira.codehaus.org/browse/MNG-3139), namely:
 
 1. Create a /src/site/site.xml file in the top-level maven project, 
 containing:
 
 [Code]
 project
   skin
 groupIdorg.apache.maven.skins/groupId
 artifactIdmaven-default-skin/artifactId
 version1.0/version
   /skin
 /project
 [/Code]
 
 Now the mvn site site-deploy works, however, there is no longer any links 
 on the left-side menu, contrary to what I'd expect from a workaround. So, 
 that's a bunk workaround.

Which version of the Site Plugin are you using?
There is a bug in version 2.1 about missing menu links.

 So, at this stage, our project is dead in the water until someone fixes the 
 site plugin to get around this 'missing skin' defect. Every Hudson build 
 fails with this error.
 
 Have users experienced similar issues in the past? How long does it usually 
 take for a critical fix to get deployed to the central maven repos? Should I 
 start writing the ant scripts for our projects? ;)
 
 Tom
 
 -Original Message-
 From: Thomas Harris 
 Sent: Monday, February 01, 2010 1:26 PM
 To: users@maven.apache.org
 Subject: SiteToolException: ArtifactNotFoundException: The skin does not 
 exist: Unable to determine the release version
 
 Friday, I was able to run the 'site' build on our project. This morning, I 
 get the following error:
 
 [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: 
 Unable to determine the release version
 
 Try downloading the file manually from the project website.
 
 Then, install it using the command:
 mvn install:install-file -DgroupId=org.apache.maven.skins 
 -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
 -Dfile=/path/to/file
 
 Alternatively, if you host your own repository you can deploy the file there:
 mvn deploy:deploy-file -DgroupId=org.apache.maven.skins 
 -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
 -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
 
 org.apache.maven.skins:maven-default-skin:jar:RELEASE
 We've changed nothing, so something bad has occurred to something out on the 
 public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows 
 XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) 
 on all platforms here when attempting to call mvn site on our project.
 
 I've updated this closed ticket. The ticket should be re-opened, as the same 
 old problem is now occurring every 'site' build for us. Can someone please 
 fix this soon? We cannot move forward on our project at this point.
 
 http://jira.codehaus.org/browse/MNG-3139
 
 Tom
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 


-- 
Dennis Lundberg

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Any way to place a JAR so that I am guaranteed its classes get loaded first?

2010-02-01 Thread laredotornado

Hi,

I'm using an older version of Maven (1.1).  I'm having a problem whereby an
old Xalan class is somehow getting loaded into my classpath and I wish to
use the classes available through Xalan 2.7.1.  I have tried placing this
dependency 

dependencies
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.0/version
/dependency


at the top of my dependency list, however, I'm still getting the same
NoSuchMethodError (due to an older class version).  Is there anywhere I
can place my xalan jar such that I'm guaranteed its classes will get loaded
first into the classpath?

Thanks, - Dave

-- 
View this message in context: 
http://old.nabble.com/Any-way-to-place-a-JAR-so-that-I-am-guaranteed-its-classes-get-loaded-first--tp27411560p27411560.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)

2010-02-01 Thread Rick R
running mvn eclipse:eclipse used to work.. now I'm getting...

[INFO] Unable to find resource
'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT' in
repository codehaus-plugins (http://dist.codehaus.org/)
[INFO] Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as
non-aggregator.

I'm new to maven and stumped by what is going on?

-- 
Rick R


RE: relocation tags

2010-02-01 Thread EJ Ciramella
Nvm - I found this mini-site:

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

I'd love a shot at updating that tho ;-)

-Original Message-
From: EJ Ciramella [mailto:ecirame...@upromise.com] 
Sent: Monday, February 01, 2010 3:51 PM
To: users@maven.apache.org
Subject: RE: relocation tags

Also - how do you really leverage these tags?  Do you put it in a version of 
the module in its old location?

-Original Message-
From: EJ Ciramella [mailto:ecirame...@upromise.com] 
Sent: Monday, February 01, 2010 3:35 PM
To: users@maven.apache.org
Subject: relocation tags

So if we've relocated a library here - and deployed once to archiva, is it too 
late to use the relocation tag?

We've corrected a bunch of group ids, and wanted to break the build.  Instead, 
by not using the relocate tags, we've gained other errors and some silent 
inclusions of the same jar (twice).



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Any way to place a JAR so that I am guaranteed its classes get loaded first?

2010-02-01 Thread Wayne Fay
 NoSuchMethodError (due to an older class version).  Is there anywhere I
 can place my xalan jar such that I'm guaranteed its classes will get loaded
 first into the classpath?

Maybe you could put it in the endorsed folder of your JRE. Other than
that, I'm unsure of any way to guarantee it, especially not with M1.

PS- When are you migrating to M2?

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Any way to place a JAR so that I am guaranteed its classes get loaded first?

2010-02-01 Thread laredotornado

Thanks for this suggestion.  How do I locate the JRE's endorsed folder?


Wayne Fay wrote:
 
 NoSuchMethodError (due to an older class version).  Is there anywhere I
 can place my xalan jar such that I'm guaranteed its classes will get
 loaded
 first into the classpath?
 
 Maybe you could put it in the endorsed folder of your JRE. Other than
 that, I'm unsure of any way to guarantee it, especially not with M1.
 
 PS- When are you migrating to M2?
 
 Wayne
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Any-way-to-place-a-JAR-so-that-I-am-guaranteed-its-classes-get-loaded-first--tp27411560p27412370.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: JAVADOC-plugin: include comments from local dependent projects

2010-02-01 Thread Wayne Fay
 project (B). E.g. A contains interfaces, and B implementations. The question
 is: how can I build docs for B so that, if none specified, method
 descriptions are inherited from A?

There's a good chance your specific usage of the Javadoc plugin is not
currently supported. I've certainly never needed nor wanted to do what
you're doing.

Look at the source code for the m-javadoc-p and see if you can figure
out a way to patch it to support your requirement, or file a Jira and
wait for someone else to code it for you.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Any way to place a JAR so that I am guaranteed its classes get loaded first?

2010-02-01 Thread laredotornado

Actually I found it.  Placing the updated JAR there solved the problem.  Much
thanks once again!

- Dave

ps - I am anxious for our company to move to the newest version of Maven. 
Sadly this issue is out of my control right now. 



laredotornado wrote:
 
 Thanks for this suggestion.  How do I locate the JRE's endorsed folder?
 
 
 Wayne Fay wrote:
 
 NoSuchMethodError (due to an older class version).  Is there anywhere
 I
 can place my xalan jar such that I'm guaranteed its classes will get
 loaded
 first into the classpath?
 
 Maybe you could put it in the endorsed folder of your JRE. Other than
 that, I'm unsure of any way to guarantee it, especially not with M1.
 
 PS- When are you migrating to M2?
 
 Wayne
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Any-way-to-place-a-JAR-so-that-I-am-guaranteed-its-classes-get-loaded-first--tp27411560p27412782.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



antrun plugin dependency disappearance

2010-02-01 Thread Benson Margulies
I think I'm hitting an known issue, but I'm stumped in working around it.

In an aggregate POM, I've got a use of the maven-antrun-plugin that
needs custom dependencies.

They are disappearing.

The reason, I suspect, is that several of the modules that the
aggregate POM aggregates are themselves using the antrun plugin, not
specifying these dependencies. I tried to get past this by hanging the
dependencies in a pluginManagment section of the profile that turns
all of this loose, but to no avail. Maven run with -X shows that they
are gone.

Is there some more reliable workaround?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: antrun plugin dependency disappearance

2010-02-01 Thread Wayne Fay
 In an aggregate POM, I've got a use of the maven-antrun-plugin that
 needs custom dependencies.

Yes, this is a known issue. Copy your dependencies into all uses of
m-antrun-p OR figure out which one will run first and copy them there.
The Maven classloader only pays attention to the dependencies of a
plugin the FIRST time it sees the plugin.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: antrun plugin dependency disappearance

2010-02-01 Thread Brett Porter
In Maven 2, only to ensure that the first plugin declaration encountered 
(usually by putting it in the root) contains all of the desired plugin 
dependencies.

I believe that Maven 3 has already fixed the problem.

- Brett

On 02/02/2010, at 12:46 PM, Benson Margulies wrote:

 I think I'm hitting an known issue, but I'm stumped in working around it.
 
 In an aggregate POM, I've got a use of the maven-antrun-plugin that
 needs custom dependencies.
 
 They are disappearing.
 
 The reason, I suspect, is that several of the modules that the
 aggregate POM aggregates are themselves using the antrun plugin, not
 specifying these dependencies. I tried to get past this by hanging the
 dependencies in a pluginManagment section of the profile that turns
 all of this loose, but to no avail. Maven run with -X shows that they
 are gone.
 
 Is there some more reliable workaround?
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: antrun plugin dependency disappearance

2010-02-01 Thread Benson Margulies
On Mon, Feb 1, 2010 at 9:06 PM, Brett Porter br...@apache.org wrote:
 In Maven 2, only to ensure that the first plugin declaration encountered 
 (usually by putting it in the root) contains all of the desired plugin 
 dependencies.

It was in the root. However, since modules run first, the instance in
a module won, so I had to put the dependencies there.


 I believe that Maven 3 has already fixed the problem.

 - Brett

 On 02/02/2010, at 12:46 PM, Benson Margulies wrote:

 I think I'm hitting an known issue, but I'm stumped in working around it.

 In an aggregate POM, I've got a use of the maven-antrun-plugin that
 needs custom dependencies.

 They are disappearing.

 The reason, I suspect, is that several of the modules that the
 aggregate POM aggregates are themselves using the antrun plugin, not
 specifying these dependencies. I tried to get past this by hanging the
 dependencies in a pluginManagment section of the profile that turns
 all of this loose, but to no avail. Maven run with -X shows that they
 are gone.

 Is there some more reliable workaround?

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 --
 Brett Porter
 br...@apache.org
 http://brettporter.wordpress.com/





 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: antrun plugin dependency disappearance

2010-02-01 Thread Brett Porter

On 02/02/2010, at 1:46 PM, Benson Margulies wrote:

 On Mon, Feb 1, 2010 at 9:06 PM, Brett Porter br...@apache.org wrote:
 In Maven 2, only to ensure that the first plugin declaration encountered 
 (usually by putting it in the root) contains all of the desired plugin 
 dependencies.
 
 It was in the root. However, since modules run first, the instance in
 a module won, so I had to put the dependencies there.

Is the root not also the parent of the module? The only reason I said root was 
because it should be consistently inherited into the children (Which may have 
to be empty, I'm not sure if the dependencies lists are correctly merged in 
some versions either).

It's definitely fickle - the best I've found is:
- put it in build  plugins of the topmost parent that will use it (not plugin 
management)
- don't add any dependency to modules that will use it, just the additional 
configuration / executions
- make sure it is in build, not reporting for checkstyle, etc. type plugins

Anyway, glad you got it sorted.

Cheers,
Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: JAVADOC-plugin: include comments from local dependent projects

2010-02-01 Thread Jeff Jensen
Possibly what you are looking for is not a Maven related thing at all but how 
Javadoc works.  If you add
 /**
  * {...@inheritdoc}
  */
above the methods in the implementation classes that implement the interface 
methods, Javadoc copies it from the interface to the implementing class' 
generated HTML files.

Additionally, if using Java 5 or newer, the @Override annotation does the same 
thing (and is the preferred approach - no need to do both).

Then, the packaged Javadoc will have what I think you want.


-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: Monday, February 01, 2010 4:48 PM
To: Maven Users List
Subject: Re: JAVADOC-plugin: include comments from local dependent projects

 project (B). E.g. A contains interfaces, and B implementations. The question
 is: how can I build docs for B so that, if none specified, method
 descriptions are inherited from A?

There's a good chance your specific usage of the Javadoc plugin is not
currently supported. I've certainly never needed nor wanted to do what
you're doing.

Look at the source code for the m-javadoc-p and see if you can figure
out a way to patch it to support your requirement, or file a Jira and
wait for someone else to code it for you.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)

2010-02-01 Thread Anders Hammar
I'm quite sure you must have reconfigured something since last time it
worked. The plugin exists in central, and for some reason your build isn't
looking there.

Run
mvn help:effective-pom
and find the pluginRepositories section and paste it in a reply.

Also, you might want to consider locking the version of the plugin being
used. You do that in the pluginManagement section. Currently I think you
don't have a version specified, so Maven will try to get the latest
(2.8-SNAPSHOT). That may cause issues when a new version is available, which
isn't backwardscompatible for some reason. Or possibly you do have the
version set to 2.8-SNAPSHOT? You can see that as well in the effective pom.
http://maven.apache.org/pom.html#Plugin_Management
(In this case you only need to specify groupId, artifactId, and version. The
latest released version is 2.7, which exists in central.)

/Anders

On Mon, Feb 1, 2010 at 22:32, Rick R ric...@gmail.com wrote:

 running mvn eclipse:eclipse used to work.. now I'm getting...

 [INFO] Unable to find resource
 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT'
 in
 repository codehaus-plugins (http://dist.codehaus.org/)
 [INFO] Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as
 non-aggregator.

 I'm new to maven and stumped by what is going on?

 --
 Rick R



Re: Eear libraries classpath

2010-02-01 Thread Maruf Aytekin
Hi Wayne

Thanks for your response on this.


 Is this a problem; having ModuleB as ModuleB.jar in ear package? Can
 ModuleA fsee ModuleB on the classpath?

 When you tested this EAR with your target Java EE app server, what
 happened? Did things deploy and work properly, or no?

No this did not work. ModuleA did not see ModuleB untill I rename
ModuleB jar with the version number.


 If the answer is no, how do I addd dependencies to the manifest.mf
 classpath without version numbers only with the finalNames?

 I'd just keep the version numbers everywhere in the first place, and
 avoid this entire discussion. What possible reason do you have for
 removing them from some of your dependencies?

We have an ejb that is a dependency for many other modules which is
being deployed to weblogic. The reason we would like to name the ejbs
without version numbers as final name is that they are being deployed
to various of weblogic instances. We don't want to redeploy each ejbs
to it's target each time we make a release.

Regards
Maruf

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org