I don't really agree that downloading sourcesjavadoc should be
standard, but I do think it should be possible. I hacked the eclipse
plugin into something that can download sourcesjavadocs on demand for
the dependencies of a given project and will upload it to JIRA
tomorrow.
Tom
On 4/27/06,
I created a new feature request in the JIRA instance for Maven 2
(http://jira.codehaus.org/browse/MNG-2248). You guys can add comments
to it if you want to. This is the first time I've created a JIRA log
so I hope I did it right.
On 4/27/06, Wayne Fay [EMAIL PROTECTED] wrote:
Discussions like
I agree with both Jamie and Aaron -- getting the sources and/or javadocs if
they are available should definately be a part of the standard grab that
downloading from a repository should do.
-Jim Moore
Aaron Freeman wrote:
I agree with Jamie. Since the ability to build javadoc and source
Discussions like these are great, but please make sure they result in
a JIRA Enhancement request (or two) so the Maven Dev group can track,
discuss, and perhaps even implement them.
Otherwise the issues raised in these conversations will never be addressed.
And I'll generally agree that sources
to get the source into your repository then you need to attache the
source plugin to the package phase as below. this will then
automatically generate the sources and deploy them.
plugin
artifactIdmaven-source-plugin/artifactId
version2.0/version
executions
If you execute 'mvn eclipse:eclipse -DdownloadSources=true', an
Eclipse project will be generated with sources or javadocs attached.
While you may not want the related project files (.project
.classpath) this will have the side effect of downloading what you
need into your local repository.
Tom
Tom Huybrechts wrote:
If you execute 'mvn eclipse:eclipse -DdownloadSources=true', an
Eclipse project will be generated with sources or javadocs attached.
Thanks, Tom. I've started using that
flag. However, a surprising number
of packages on ibiblio don't include
source or javadoc archives.
The Eclipse plugin will (or should) only download javadocs if the
sources are not available. Makes sense for Eclipse, since it will
extract the javadocs from the sources if needed.
Tom
On 4/26/06, gdub [EMAIL PROTECTED] wrote:
gdub wrote:
gdub wrote:
I have the source and
javadoc
Tom Huybrechts wrote:
The Eclipse plugin will (or should)
only download javadocs if the
sources are not available. Makes
sense for Eclipse, since it will
extract the javadocs from the sources if needed.
Ah. I see. I deleted a source
archive and it did indeed attach
the javadoc archive
So what you all are saying is that the eclipse:eclipse
-DdownloadSources=true command is the only way to get Maven to copy
source jars into the local repository. So if you already have .project
and .classpath file, the there is no way to get the sources in the
local repository without messing up
On 4/26/06, Aaron Freeman [EMAIL PROTECTED] wrote:
So what you all are saying is that the eclipse:eclipse
-DdownloadSources=true command is the only way to get Maven to copy
source jars into the local repository. So if you already have .project
and .classpath file, the there is no way to get
Jamie Bisotti wrote:
On 4/26/06, Aaron Freeman [EMAIL PROTECTED] wrote:
So what you all are saying is that the eclipse:eclipse
-DdownloadSources=true command is the only way to get Maven to copy
source jars into the local repository. So if you already have .project
and .classpath file, the
I agree with Jamie. Since the ability to build javadoc and source jars
is a built in part of the maven deploy plugin, it doesn't make sense
that the only way to get maven to download them is using an eclipse
specific plugin. What if people want to use these source files for
other things or with
13 matches
Mail list logo
