My experience is that the Eclipse plugin does setup intra-project dependencies properly. so long as you run 'mvn eclipse:eclipse' from the root of the project (as opposed to running it for each module individually). If I have a project with moduleA and moduleB, and moduleB depends on moduleA, I will get an Eclipse project dependency (as opposed to a dependency on the M2_REPO/.../moduleA-1.0.jar) when I run 'mvn eclipse:eclipse' from the root of the project.

In what way is the eclipse plugin not creating these dependencies properly for you?

-Max

Brad Davis wrote:
Because the eclipse plugin doesn't properly set up intra project relationships it would be nice to have an explicit build step that could generate and deploy javadoc and source jars, even for snapshot releases.

Brad


----- Original Message ----- From: "Stephen Duncan" <[EMAIL PROTECTED]>
To: "Maven Users List" <users@maven.apache.org>
Sent: Friday, June 09, 2006 6:11 PM
Subject: Re: Maven 2 sources/javadocs installation question


You can simply run mvn -DperformRelease=true install

This will build source & javadoc jars & install them. No configuration option.

-Stephen

On 6/9/06, Matt Wheeler <[EMAIL PROTECTED]> wrote:


Never mind my last email.  I moved the plugin under build outside of
profiles and added a package phase, and it works now.


Matt W.

------------------------------------------------------------------------------


NOTICE: This email message is for the sole use of the
 intended recipient(s) and may contain confidential and
 privileged information. Any unauthorized review, use,
 disclosure or distribution is prohibited. If you are not the
 intended recipient, please contact the sender by reply email
 and destroy all copies of the original message.




------------------------------------------------------------------------------





---------- Forwarded message ----------
From: "Matt Wheeler" <[EMAIL PROTECTED]>
To: users@maven.apache.org
Date: Fri, 09 Jun 2006 09:45:29 -0600
Subject: Maven 2 sources/javadocs installation question


I have a project that I run install on to install the project and all of its sub project's main artifacts in the local repository. However, I would also like to "automatically" install the sources and the javadocs as well. I can generate these using sources:jar and javadoc:jar commands, however, I cannot get them to be automatically generated using the profile section in the pom
that is shown in the documentation under "Introduction to the POM" at
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html.
 What would I need to do to make that example work?

Also, even if I coudl get the profile to generate the source and javadoc
jars, I am not sure how to install them.  I assume that I could use
install:install-file, but I woudl really like a more automated way if there is one. I have tried to install them manually, but the problem is that I can't get it to install in the same directory as the projects main artifact.
 For instance, say my project artifact is in
.m2/repository/org/whatever/2.0-SNAPSHOT/stack-code-2.0-SNAPSHOT.jar.
 Well, if I then run a commond something like:

mvn install:install-file -DartifactId=stack-code -DgroupId=org.lds.stack
-Dpackaging=jar -Dversion=2.0-SNAPSHOT
-Dfile=D:/Projects/Stack/stack-code/target/stack-code-2.0-SNAPSHOT-sources.jar

Then, it overwrites the projects main artifact stack-code-2.0-SNAPSHOT.jar. However, if I change the version to 2.0-SNAPSHOT-sources, then it put the jar (this time with the correct name stack-code-2.0-SNAPSHOT-sources) out in the repository, but under a 2.0-SNAPSHOT-sources directory instead of under the 2.0-SNAPSHOT directory with the main artifact. I am am seeing sources placed correctly on ibiblio however, so I am just wondering what I am doing
wrong, or if there is an easier way to accomplish this?

Thanks,

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




--
Stephen Duncan Jr
www.stephenduncanjr.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]


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

Reply via email to